<rafa>
urandom_: it is clear for me that you did not use the bootloader from jlime right?
<urandom_>
i updated the bootloader when i flashed the latest openwrt image so i use that one
<rafa>
ah.. okey, well, perhaps you could have realized that it did not boot from fat because you did not boot from the bootloder from jlime wiki :)
<rafa>
urandom_: have you booted finally?
<urandom_>
the kernel at least, (seen jlime logo) but i think it did not find the rootfs which was on second partition
<rafa>
too weird.. perhaps that bootloader just want to mount the first partition?
<rafa>
I do not like too many different binary bootloaders around
<rafa>
perhaps I write a short mail explaining that it should work with bootloader in jlime. That thing would annoy users surely.. it is not nice to use specific files for different stuff :(
<urandom_>
why not just use the "official" qi one?
<rafa>
urandom_: the bootloader from jlime wiki was a tmp qi one, and the official one at that moment did not work for microsd
<urandom_>
also debian is booting fine from one big ext2 partitions so no need for 3 different partitions at all
<rafa>
urandom_: so if it changes going to the good way okey, but now you can not boot jlime because the "current" official one does not mount second partition
<rafa>
urandom_: try to install in debian a package with 5 or 6 dependences
<rafa>
nevermind.. I think that it is just a temporary stuff.. all the stuff would mature with the time.. and if somebody just need debian like it is then he would use the proper bootloader, if somebody needs jlime he will have to use the proper files, and so on..
<urandom_>
i am not really interested in debian, jlime seems much better for my needs
<urandom_>
just got the idea using ext2 from debian
<rafa>
urandom_: I would like to use initramfs and kexec, so we can have a general second stage bootloader for any needs..
<rafa>
so you could boot from any partition in NAND or sd, or just to do maintanence tasks from that initramfs
<rafa>
and also, it would let users to update theirs system without usbboot and all that no nice stuff
<urandom_>
well the good thing of this story is that i got epic fdisk skills now ;)
<rafa>
urandom_: haha great man
<urandom_>
yeah i would like to easy flash everything from sdcard (but thats now partly possible, at least for kernel und rootfs)
<arctanx>
rafa: your uImage is tagged -qi... are you using the same kernel config as the openwrt-xburst kerneL?
<urandom_>
now booting jlime with rootfs
<urandom_>
it takes a bit long
<arctanx>
mine's doing a fsck and generating ssh keys
<urandom_>
omg x and no crapy gmenu2x, awesome!
<arctanx>
I think it wins the long boot award
<urandom_>
rafa thanks for making jlime, it is awesome!
<urandom_>
openwrt currently looks like shit against it (but boots damn fast)
<urandom_>
wow looking movies on the ben
<urandom_>
second boot isnt that bad
<urandom_>
omg it comes without lua preinstalled! unforgiveable
<urandom_>
and no python, no ruby, no guile
<kyak>
calamarz: do you have some documention/howto about the keymouse/scummvm?
<kyak>
rafa: "Kernel panic - not syncing: No init found. Try passing init= option to kernel" when booting fresh install of Jlime...
<kyak>
btwm i had to put the uImage to /boot/ on the first ext2 partition
<kyak>
otherwise it won't boot at all
<kyak>
rafa: ok, it seems that it is no longer required to have two partitions for Jlime
<kyak>
"uboot will load "/boot/uImage" in the sd card first ext2 partition.
<kyak>
then kernel will also boot to rootfs at sd card first ext2 partition."
<kyak>
yep, got it running from a first ext2 partition
<arctanx>
Humm has anyone else run into errors compiling qt4 for the openwrt build?
<kyak>
xiangfu: you there?
<xiangfu>
kyak: hi
<kyak>
hi man
<kyak>
wanted to piont out to something.. don't know how to fix this correctly
<kyak>
in your latest commit, you removed the zImage build
<xiangfu>
kyak: yes.
<kyak>
but, have a look:
<kyak>
cp: cannot stat `/home/bas/build/openwrt-xburst/build_dir/linux-xburst_qi_lb60/linux-2.6.32.10/arch/mips/boot/compressed/zImage': No such file or directory
<kyak>
make[5]: *** [install] Error 1
<kyak>
it is still trying to install it
<kyak>
therefore, build fails
<xiangfu>
kyak: thanks for report. there is another makefile need modify.
<kyak>
no problem :) if i knew how to fix it, i would do it. But i definitely lack knowledge about the internals of build process
<calamarz>
somebody knows which is the option in the kernel to output info when booting?
<nebajoth>
what are you working on, calamarz?
<calamarz>
nebajoth: jumping from one thing to another :p
<calamarz>
now playing with bloating the kernel
<calamarz>
yesterday I finally got the keymouse working (it was only enabling mouse/uinput in the kernel)
<calamarz>
and now I'm trying to enable acpi for getting power info and suspend stuff working
<calamarz>
nebajoth: are you behind the nanohacks wordpress?
<nebajoth>
calamarz: yep
<nebajoth>
ooooh, acpi would be super nice
<urandom_>
whats that "unable to open display" error on jlime about? first time i got it i just reflashed since i thought something might have got corupted but now i got it a second time
<calamarz>
nebajoth: I thought the other day we could use an elgg there... nothing against the wordpress, in fact the theme is really nice... but I know some people that are working hard on elgg for community work (integration with wiki, task management, integration with mailin list etc...)
<wolfspraul>
lekernel: nice! do you have a download link for this video somewhere so I can convert to Ogg Theora and upload to the Qi wiki?
<wolfspraul>
do you have a higher resolution than 320x240?
<urandom_>
if somone else has problem with "unable to open display" in jlime and is booting it form one big ext2 then editing etc/muffinman-extras/00fsck.sh is the solution (just for the archive)
<calamarz>
how can the kernel boot parameters be changed? (the ones in /proc/cmdline)
<larsc>
calamarz: in uboot
<lekernel>
no higher res unfortunately... as I said on the MM list I have a rather crappy camera
<lekernel>
maybe Adam or Michael could make a better video...
<bartbes>
wow, irc really is instant :P
<bartbes>
next time try email :D
<xdpirate>
i think my nanonote is faulty
<xdpirate>
i was using it just now, and suddenly the screen faded into a complete white screen
<xdpirate>
tried taking out the battery, leaving it out, then reinserting it, it just lights up the lcd with the same completely white screen
<wolfspraul>
xdpirate: were you on battery or powered over the USB cable?
<xdpirate>
battery
<wolfspraul>
try to take the battery our and power it over USB cable
<wolfspraul>
there are two options: 1) the battery is empty 2) the batery connector does not sit very tight mechanically with the battery itself
<xdpirate>
just tried reinserting the battery, it remained off and wouldn't turn on, i'll try connecting it via usb now
<wolfspraul>
well maybe the battery is just empty?
<rafa>
urandom_: about "editing etc/muffinman-extras/00fsck.sh".. that should be done from a fresh install
<xdpirate>
i find that very weird, i just charged it a couple of days ago and haven't used the nanonote at all since
<rafa>
if somebody sees "unable to open display"
<rafa>
urandom_: then he surely already has a broken ext2, well it perhaps works, but it already has errors and he should install from scrasch
<wolfspraul>
xdpirate: let's first find the root cause
<wolfspraul>
screen turning white is typically because of loss of power
<xdpirate>
it booted via usb+usb to power adapter
<wolfspraul>
which can be low/empty battery, or sometimes the battery connector
<wolfspraul>
ok, leave it plugged in, now insert the battery and see whether the red charging LED comes on
<xdpirate>
yay, great success
<xdpirate>
thanks
<xdpirate>
probably just a low capacity on the battery
<wolfspraul>
maybe
<wolfspraul>
next thing would be to find out why it went down even though you said it was full
<wolfspraul>
battery should discharge itself only about 1% per day I think
<xdpirate>
yeah haven't used it much since last charge
<wolfspraul>
ok, first leave it connected until fully charged now
<xdpirate>
btw can i get the battery % remaining from anywhere?
<wolfspraul>
I think you can but I don't know where :-)
<xdpirate>
hehe :P
<wolfspraul>
it's not very precise because we have no coulomb counter or precise current measurements
<wolfspraul>
xdpirate: hey I saw you added a translation to the wiki, nice and thanks a lot!
<xdpirate>
urandom_, thanks
<xdpirate>
wolfspraul, hey no probs, will probably do more
<wolfspraul>
great, that would be fantastic!
<xdpirate>
wolfspraul, i just noticed that the battery compartement is abit bigger in length than the battery
<xdpirate>
so there's a bad connection there
<xdpirate>
need to find something to put in there so it sits right
<wolfspraul>
yes that is possible too
<wolfspraul>
I am not really happy with the battery connector
<wolfspraul>
you can try to pull it out a bit with a small screwdriver, bending the metal into the battery compartment. but be careful to not break anything (so maybe not :-))
<xdpirate>
850 mAh isn't all that great tho
<xdpirate>
i got a nokia battery here that's also 3.7V but it doesn't say anything about the mAh
<wolfspraul>
or you put some paper into the other side so the battery presses more firmly against the connector
<xdpirate>
yeah that was my idea aswell
<wolfspraul>
they should also work, but the nokia is even lightly narrower so you definitely need something on the other side
<xdpirate>
it's a BL-4C battery, according to the great interwebz it's only 780 mAh
<xdpirate>
another source says 720
<xdpirate>
both smaller tho
<urandom_>
it just would be nice to get some "pls load battery" message before it fades to white, would be more usefull than the new image printing lot of shit everytime i insert an sdcard
<xdpirate>
true, i never know how much battery charge is left
<wolfspraul>
yeah definitely we could be smarter about the battery running low
<xdpirate>
the LED powers off when it's fully charged right?
<urandom_>
yeah
<xdpirate>
mkay i'll leave it off and charging now then
<xdpirate>
i put a piece of cardboard from a pizza box to press the battery up against the connector
<xdpirate>
thanks for the help wolfspraul
<wolfspraul>
no problem
<wolfspraul>
thanks for your patient with our little patient
<wolfspraul>
patience :-)00000000000
<xdpirate>
:P
<xdpirate>
yeah urandom_ i tried that script
<wolfspraul>
it's a long way until software is rock stable and polished in all cases...
<wolfspraul>
years I think
<xdpirate>
doesn't work, when fully charged it told me that i had a minus 35% charge
<urandom_>
i really would prefer fixing bugs instead of reporting bugs :/
<emeb>
hmmm - using the 6/15 openwrt image and SD card is acting odd.
<emeb>
doesn't automount at boot
<emeb>
and if I eject/insert then kernel spews errors if trying to mount later.
<emeb>
only way to use it is to boot with card in and then issue 'mount /dev/mmcblk0p1 <mount point>' manually.
<xdpirate>
add that line to /etc/profile
<xdpirate>
and it'll mount at boot
<kyak>
not a good solution. it will try to mount after each login
<kyak>
better /etc/rc.local
<urandom_>
emeb i dont think they are errors, just messages
<kyak>
or /etc/fstab, if there is such :)
<emeb>
urandom_: but it doesn't actually mount when those occur. Complains about not finding valid FAT
<urandom_>
it can mount ext2 and fat16 partitions without problems for me
<emeb>
kyak: agree. rc is prolly best sinc fstab has some stuff in it about being auto generated
<emeb>
urandom_: hmm will try some more.
<urandom_>
but i gues the sd stuff on openwrt really needs some more work
<emeb>
urandom_: true, but I seem to recall the previous image worked better...
<emeb>
another question: gmu blanks the display, even if you've switched to a text term via alt+ctl+Fx. One solution is to disable blanking in gmu config
<emeb>
is there a way to poke something in /sys to turn display back on?
<larsc>
/sys/class/graphics/fb0/blank
<emeb>
larsc: thx - I figured there was something like that.
<calamarz>
sdschulze: do you mind if I put your notes about compiling debian kernel in the qi wiki?
<lunavorax>
Evening everyone !
<lunavorax>
51 people and nobody's talking ?
<calamarz>
lunavorax: we're bots :p
<lunavorax>
haha
<lunavorax>
That's what I was expecting
<lunavorax>
I have a few questions about  the os of the ben nanonote
<lunavorax>
I can't remember who told me that the flickering screen bug will be fixed soon
<lunavorax>
But again I can't remember when I read that
<lunavorax>
So I don't know if it's soon soon or already made
<kristoffer>
lol
<larsc>
lunavorax: the bug has been fixed quite some time ago. Unfortunately it hasn't made it into the current images yet :/
<lunavorax>
Oh ok
<lunavorax>
no pb
<lunavorax>
What happens when it says "Host key verification failed." when I try to connect to the ben nanonote
<lunavorax>
What have I done wrong ?
<larsc>
you have a different key for the nanonotes ip in your ~/.ssh/known_hosts
<lunavorax>
larsc, that means ? I have to delete this file and try again ?
<bartbes>
no
<bartbes>
remove the entry for that ip/hostname
<lunavorax>
hum ok bartbes
<lunavorax>
This files doesn't exist on the nanonote so i believe it's on the computer then
<larsc>
ssh should tell you which line it is when you try to connect
<bartbes>
yes, on the client
<larsc>
yes, on your host
<bartbes>
larsc: client
<lunavorax>
?
<lunavorax>
client != host, right ?
<bartbes>
the ssh client
<bartbes>
meaning, your computer
<larsc>
bartbes: depends on your point of view ;)
<lunavorax>
haha ok
<bartbes>
larsc: no, that's the client
<lunavorax>
I'll just try
<bartbes>
it's definitely the client
<bartbes>
because it's the ssh *client* which error
<larsc>
bartbes: it's the ssh client, but the usb host
<bartbes>
but we're not talking usb now are we?
<lunavorax>
Ok hum that doesn't solve the problem
<bartbes>
we're talking about a network connection
<bartbes>
but yeah, it's always point-of-view stuff
<lunavorax>
hum gentlemens
<lunavorax>
:D
<bartbes>
I'm looking through the man page
<lunavorax>
Well I should be doing the same even if i'm a noob
<bartbes>
you could try: ssh -o StrictHostKeyChecking=false <nanonote>
<bartbes>
(a temporary solution but that should work)
<lunavorax>
ok i'm trying it
<ezdagor>
Anyone know how to get the mouse to work under Debian? There is no kernel module for it.. if there is one..
<lunavorax>
hum
<ezdagor>
I used the Debian-lenny.ubi
<lunavorax>
Yes i tried to boot but it didn't worked
<lunavorax>
I much more used to debian that will be easier for me when I'll succeed to boot it
<ezdagor>
Nod.
<lunavorax>
nod ?
<ezdagor>
Yes.
<ezdagor>
Nodding my head.
<lunavorax>
ah ok
<lunavorax>
I was thinking "Nintendo optical disc"
<lunavorax>
hehe
<ezdagor>
Hehe.
<ezdagor>
Two things I haven't figured out yet... sound and the mouse..
<lunavorax>
on the nanonote ?
<ezdagor>
Matchbox works ok with the keyboard, but would be easier with a mouse.
<bartbes>
(modify usb0 to the /dev/ device where the nanonote ends up)
<bartbes>
and you're done
<bartbes>
it automagically runs the script when the device is inserted
<max_posedon>
I suggest disctro-specific solution
<max_posedon>
most distros detect and allow pre-up post-up's for ethernets
<bartbes>
udev powns!
<max_posedon>
yes, but solution to low-level imho
<urandom_>
bartbes sounds like this should be wikified, feel free to add it :)
<bartbes>
urandom_: well somebody should test it first
<lunavorax>
Ok well I just give up
<lunavorax>
It's not a problem, but it's better than messing around
<urandom_>
so someone test bartbes solution!
<lunavorax>
what solution ?
<urandom_>
how to not have to modprobe every time
<bartbes>
and not have to do the other stuff
<bartbes>
the modprobe is relatively easy
<lunavorax>
I think I've missed that
<urandom_>
lunavorax yeah you have, it will show off in the archives soon
<lunavorax>
hum ok i'll try this asap then
<lunavorax>
Is it really complex or is it just me being really incompetent ?
<urandom_>
well if it did not work for you per hand then bartbes method wll not work too
<urandom_>
its a bit complex
<lunavorax>
hum :/
<bartbes>
unless of course you failed to follow the instructions..
<lunavorax>
Well there wasn't that much instruction (!?)
<lunavorax>
Well maybe
<lunavorax>
I can't telle
<lunavorax>
tell
<lunavorax>
I'll retry another day, it's late now I'm a bit tired (and tired of it)
<tuxbrain>
calamarz, rafa: bravo, bravissimo!!!!
<tuxbrain>
I hope both openwrt and jlime has the virtual mouse thing in his respectives future releases :)
<tuxbrain>
rafa: what is the resolution+codec+bitrate recomended to play the video so smoth :)
<kristianpaul>
tuxbrain: mouse why?
<kristianpaul>
arrow akeys are perfect for small screens
<tuxbrain>
but there are a lot of soft out there that can be run with minimum porting if they have the mouse thing enabled, (I agree is better a good key driven app, but the example  scummvm
<tuxbrain>
is just to add one feature more to the nanonote
<tuxbrain>
rafa: sorry I was so impatient :) I ask on first link, I have just arrive to it , thanks
<rafa>
tuxbrain: and BTW, I think that it is not a good idea to try to have mouse pointer.. X is nice, and X works okey for 320x240.. but our idea is to have just applications useful for qwerty keyboard. But well, you can show us the mouse options :)
<tuxbrain>
kristianpaul: and where do you will connect it ? suggestions?
<rafa>
tuxbrain: you there?
<tuxbrain>
again, I agree than main apps, and news apps created with nn in mind should be qwerty driven, but have such feature enabled to test "already made soft" that was though with mouse in mind, should not harm isn't it?
<tuxbrain>
yes I am
<rafa>
some guys were able to use jlime using the current qi official bootloader, but...
<tuxbrain>
but?
<rafa>
current jlime does some little tasks in second ext2 partition
<rafa>
so they were able to boot jlime and use it
<rafa>
but after few reeboots
<rafa>
they broke their filesystems
<tuxbrain>
ups
<tuxbrain>
sounds bad
<rafa>
but they did not note that
<rafa>
tuxbrain: yes, of course
<rafa>
I just want to tell you that until we can fix that jlime works nice if you use jlime instructionts
<rafa>
I mean, people do not follow the jlime instructions, and they use their skills to boot it.. but then ... after some reboots the distributions has very weird behaviours...
<rafa>
and they complain that it works bad :)
<kristianpaul>
tuxbrain: uart, gpio
<kristianpaul>
gpio
<kristianpaul>
i think there are two free pins
<kristianpaul>
near to TP4/TP5
<tuxbrain>
kristianpaul: sure on this? I was searching for free gpio on ben to do some experiments
<kristianpaul>
i have a backlog about it
<kristianpaul>
from some weeks ago
<kristianpaul>
let me check
<kristianpaul>
why lattice release in an open source way its lm32 core
<kristianpaul>
ops
<urandom_>
nah i wasnt complaining rafa, also it works good now (even after some reboots)
<rafa>
urandom_: well, you did the proper steps... you realized that it did now work okey and you fixed it.. but other no
<tuxbrain>
I have to find some time to collect all the news , and post them in some visible place
<tuxbrain>
you are making this device shine even brighter guys
<kristianpaul>
the driver will be as the mmc in openwrt with the wrt54gl i think
<kristianpaul>
larsc:^
<larsc>
hm?
<tuxbrain>
kristianpaul: I plan to sell sack and milkymist, but I have no news from sack part, I was waiting for one of the prototypes
<tuxbrain>
kristianpaul lars, so tp35 tp36 are free to use?
<tuxbrain>
sorry larsc
<larsc>
those are connected to a flash socket which is not used
<larsc>
so you can use them, yes
<tuxbrain>
humm? so is not a quimera think to bitbang them to use as 9600 uart?
<mth>
larsc: I was thinking of reconfiguring the PLL only when scaling_max_freq changes and handle changes to scaling_cur_freq by changing the dividers
<mth>
since changing the dividers has a much lower latency
<qi-commits>
Lars-Peter Clausen: mmc: jz4740: Use bitops to modify waiting flag instead of using a spinlock http://qi-hw.com/p/qi-kernel/0483cdc
<qi-commits>
Lars-Peter Clausen: mmc: jz4740: Minor cleanups http://q
<larsc>
mth: sorry can follow you. what are scaling_max_freq and scaling_cur_freq?
<larsc>
s/can/can't/
<mth>
they're files in /sys/devices/system/cpu/cpu0/cpufreq
<tuxbrain>
mmm then maybe I can attach the gps module without loosing the hwd uart tp4/5, well step by step first I have to test the module in the hwd uart, then I will try the bitbanging thing, also , there is any other gpio free to also add on/off gps functionality?
<mth>
actually scaling_cur_freq is read-only, how it gets its value depends on the governor that is in use
<larsc>
tuxbrain: there should be at least one more
<larsc>
mth ok
<mth>
I reworked the PLL rate setting code and now I can set any frequency between 25 MHz and 500 MHz with at least 1 MHz precision
<tuxbrain>
larsc: yay!
<mth>
but every time the PLL needs a delay to restabilize
<mth>
and I found no info on how long it needs exactly
<mth>
so I'm just sticking to the value that Uli copied from Ingenic (I assume)
<mth>
which seems to work but might be on the conservative side
<mth>
32 RTC ticks, so 1 ms
<tuxbrain>
rafa: you know if there is avrdude and avr-gcc in OE repos?
<mth>
with that kind of latency, it's not possible to switch frequencies often
<larsc>
mth: there should be a bit which is set when the pll is stable
<tuxbrain>
rafa: if so I would like to change my actual debian -arduino platform to jlime-arduino :)
<mth>
yes, but I think it just indicates whether the counter reached zero, not whether it's actually stable
<mth>
otherwise, why even have a counter?
<larsc>
no idea
<mth>
also, changing dividers means we could scale just the CPU without changing the clocks of all other subsystems
<mth>
when done properly, the overhead of changing all clocks derived from the PLL could also add up to something significant
<tuxbrain>
larsc: with no rush , but when you know another free gpio(s) to be able to use please let me(us) know, with out hurry, first I have to deal with gps just connected to serial. kristianpaul larsc thank you both :)
<tuxbrain>
good night channel, time to some sleep
<mth>
the only drawback I see is that the resolution is low
<mth>
if the PLL is set to 400 MHz, the CPU can be set to 400 or 200, but nothing inbetween
<larsc>
hm
<mth>
for max CPU frequencies below 250 MHz, we could use a divider of 2 for the max speed and then 2/3 of the max speed would also be a possible setting
<mth>
but I don't think many users will cap their CPU speed at 250 MHz
<mth>
since if the frequency scaling works well, there will not be much gain over having a high max speed with a low average speed
<mth>
"bool enabled" -> there is a bool type?
<larsc>
yes
<mth>
is it a Linux thing or a newer version of the C spec?
<larsc>
i think it is in c99 or so. but it's also a linux thing
<mth>
but it's a typedef then, so things like "!!" are still needed?
<qi-commits>
Lars-Peter Clausen: RTC: JZ4740: Add common implementation for jz4740_rtc_update_irq_enable and jz4740_rtc_alarm_irq_enable http://qi-hw.com/p/qi-kernel/15c9097
<qi-commits>
Lars-Peter Clausen: RTC: JZ4740: Use dev_get_drvdata directly instead of wrapping it in dev_to_rtc http://qi-hw.com/p/qi-kernel/9e07a13
<rafa>
wolfspraul: so try to use timezone from colombia, no chat NOW!
<rafa>
wolfspraul: and again, drink their coffe, this is the best :)
<wolfspraul>
no chat now?
<wolfspraul>
why?
<wolfspraul>
I am working :-)
<rafa>
:D
<rafa>
it is time to sleep in colombia now
<rafa>
well, also in argentina.. perhaps I should go to sleep .. too tired these days
<rafa>
but first, I will try xiangfu kernel ;)
<rafa>
xiangfu: building.. it also has rootfs as /dev/ram.. so I disabled kernel command line arguments default as well
<xiangfu>
rafa: yes. I just committed it. :)
<rafa>
xiangfu: no luck with my rootfs on sd.. kernel says that it mounts rootfs, but no init found. It is there.. well, I will check tomorrow. thanks for your help
<xiangfu>
rafa: this kernel will run "/etc/preinit" as the init.