<ebaus> xiangfu: Just follow all the instructions to install debian on a SD CARD but no luck because I can not even turn on my nanonote
<ebaus> Is there any way to reset the device ?
<kyak> xiangfu: hi
<kyak> i already mentioned once, there's an empty dir bin/xburst/uboot-xburst-qi_lb60/ after openwrt build
<kyak> is there some use for it?
<xiangfu> kyak: Hi. I just back to my compile. I will try to look into today.  it's useless.
<kyak> xiangfu: thnkas!
<xiangfu> kyak: sorry for my delay work. I just found which line create this folder. now testing :)
<kyak> xiangfu: no problem!
<kyak> Mplayer runs flawlessly with -nosound
<kyak> seems that built-in mp3lib is causing problems
<xiangfu> kyak: which system ? debian or openwrt ?
<kyak> xiangfu: do you know if we can port lame or some other mp3 library?
<kyak> i mean, wouldn't it cause patent problems?
<kyak> xiangfu: openwrt
<kyak> see openwrt-packages, i commited it yesterday
<kyak> i do it like this:
<kyak> 1. prepare your avi files for Ben:
<kyak> for i in $(echo "*.avi"); do /usr/bin/mencoder -o "$i.mpg" -vf scale=320:-2 -of mpeg -ovc lavc -lavcopts vcodec=mpeg1video:vpass=1:vbitrate=200 -ofps 24000/1001 -oac lavc -lavcopts acodec=mp2:abitrate=64 "$i" && /usr/bin/mencoder -o "$i.mpg" -vf scale=320:-2 -of mpeg -ovc lavc -lavcopts vcodec=mpeg1video:vpass=2:vbitrate=200 -ofps 24000/1001 -oac lavc -lavcopts acodec=mp2:abitrate=64 "$i"; done
<kyak> (thanks tuxbrain)
<kyak> 2. play your files with Ben:
<xiangfu> kyak: we can add it to openwrt-package.git. but we can not ship the image that include mip3 library with NanoNote
<kyak> mplayer -vo sdl -vfm ffmpeg -nosound file.mpg (it only consumes 50 % CPU)
<kyak> xiangfu: i see, but we can still offer a convenient way for users to do opkg install lame?
<kyak> or they would have to build from source themselves?
<kyak> anyway, need to port lame or mpg123.. or encode sound to something else
<xiangfu> kyak: I think opkg install is ok.
<xiangfu> kyak: agree.
<kyak> xiangfu: btw, you should try fbterm+w3m -> should be able to display Chinese :)
<xiangfu> kyak: oh.. I only tried fbterm. yes. I will try it later . thanks :)
<xiangfu> kyak: it should be jfbterm.
<kyak> both work well
<qi-bot> [commit] Xiangfu Liu: remove empty folder, we copy uboot to bin/xburst http://qi-hw.com/p/openwrt-xburst/a08dad4
<qi-bot> [commit] Xiangfu Liu: remove empty folder, we copy uboot to bin/xburst http://qi-hw.com/p/openwrt-xburst/7f4d509
<xiangfu> update the commit message. :)
<xiangfu> kyak: fixed ^ :)
<kyak> xiangfu: thanks :)
<kyak> hm, i'm concerned.. playing ogg file with mplayer and libvorbis is still very slow
<kyak> in comparison to gmu, which is using the same libvorbis
<kyak> i thought there would be problems with video decoding, but it turned out that audio decoding is a bottleneck
<qi-bot> [commit] Xiangfu Liu: mtd-utils goto upstream, don't need ubi-utils anymore http://qi-hw.com/p/openwrt-packages/398002e
<kyak> xiangfu: in fact, lame is already ported in openwrt
<kyak> now to enable it in mplayer
<xiangfu> kyak: w3m compile fine after "config.full_system" build. but there is some error in a "config.minimal" build system.
<kyak> it might lack for some dependency
<xiangfu> kyak: I will test the new packages in opewnrt-xburst.git . then try to add them to config.full_system tomorrow.
<kyak> which is pulled by some other package from config.full_system
<kyak> xiangfu: ok!
<kyak> xiangfu: what was the error in config.minimal build?
<xiangfu> yes. the dependency is always hard to find out.
<kyak> need to go now, see you later
<xiangfu> kyak: see you.
<xiangfu> kyak: the error mesage: http://pastebin.com/ZhBfURbA. you can take a look when you back.
<wejp> kyak, Gmu is not using libvorbis for ogg vorbis decoding
<wejp> if mplayer uses libvorbis it has to be very slow on the nanonote
<kyak> wejp: what does gmu use then?
<wejp> tremor
<wejp> libvorbis is useless on devices without a floating point unit
<kyak> wejp: i see.. mplayer can also use tremor (by default)
<wejp> yes it can
<kyak> and it is terribly slow
<wejp> you have to enable that when compiling mplayer
<kyak> wejp: why the depenedecy for libvorbisidec in gmu?
<kyak> wejp: i did
<wejp> libvorbisidec is tremor
<kyak> hm
<kyak> mplayer has some built-in tremor
<kyak> it is not the same as libvorbisidec then?
<wejp> if it is built-in it is not the same as libvorbisidec, but is most likely derived from it, when they say it is the tremor decoder
<kyak> ok, will have to have a look
<wejp> also you should explicitly disable the normal libvorbis in mplayer
<kyak> it doesn't have "normal" libvorbis
<wejp> yes it does
<kyak> it has the tremor
<wejp> no
<kyak> hm explain please
<wejp> it can also use floating point vorbios decoding
<wejp> mplayer usually does NOT use tremor for vorbis decoding
<wejp> you can enable that, but by default it doesn't
<kyak> --disable-tremor-internal disable internal Tremor [enabled]
<kyak> enabled by default
<wejp> yes
<wejp> but it is still not used by default
<wejp> that's why i said you should disable libvorbis support
<wejp> it is useless anyway, so there is no reason to have it in mplayer on the nanonote
<kyak> ok this is clear
<wejp> same is true for other decoders like mp3 (if you are going to build that)
<kyak> how to link against libvorbisidec?
<kyak> how to make mplayer use it?
<wejp> the internal tremor should be very similar to the external libvorbisidec. i would be really surprised if it wasn't
<kyak> wejp: and another question, is there an mp3 decoder that doesn't need a fpu and therefore will work on Ben?
<wejp> yes, of course there is. mpg123 can be used in integer mode. also libmad does not use floating point at all (but is still slower than mpg123 and has a horrible api)
<kyak> wejp: i'll try again with that internal tremor.. when it was enabled, mplayer played ogg files with "ffvorbis"
<kyak> wejp: do you know if lame can be used in integer mode?
<wejp> ffvorbis doesn't sound right, but i'm note sure
<wejp> no idea for lame, probably not
<kyak> ok, thanks for th ehints
<wejp> you're welcome
<kyak> mpg123 would be useful to port anyway, also for use with gmu
<wejp> you can easily use it with gmu, but keep in mind that things with mp3 support will never be supported by the default nanonote firmware due to patent issues
<wejp> well at least as long as those patents are still valid
<kyak> i understand
<wejp> the last of the mp3 patents are going to expire in the end of 2012 in most countries, so maybe then it can be included ;)
<kyak> i;m not aiming for default firmware, but to make it available for those who wish it
<kyak> they say the world is going to end in 2012, so who cares about m3 :)
<bartbes> I do
<bartbes> if I go to hell I might as well listen to mp3s there
<kyak> you will be made listen to Spears mp3s :)
<kyak> forever
<kyak> 32 kb/s, mono
<kyak> yes, this is hell
<bartbes> you are wrong
<bartbes> hell is where you listen to full-quality uncompressed recordings of the village people
<kyak> their screams?
<wpwrak> bartbes: i thought in hell, they had karaoke ?
<wpwrak> wolfspraul: aha ! qi-bot doesn't look for cae-tools commits yet
<rafa> wolfspraul: do you have pictures of the idbg installatino day? I need to prepare the documentation with good pictures, for example, when werner used tht dremel, etc
<wolfspraul> rafa: yes I uploaded them recently, one sec
<wolfspraul> rafa: http://en.qi-hardware.com/w/index.php?title=Special:NewFiles&until=20100925153552
<wolfspraul> also the page before ("older")
<wolfspraul> I need to embed them nicely in a page...
<rafa> wolfspraul: thanks a lot
<rafa> wolfspraul: I will write some documentation about all the installation processes
<rafa> process*
<wolfspraul> wpwrak: cae-tools added
<qi-bot> [commit] Werner Almesberger: Adjust button size when switching between views. http://qi-hw.com/p/cae-tools/2997c6b
<wpwrak> wolfspraul: thanks !
<tugasoft> hello all
<tugasoft> i've been using the nanonote for a few weeks, with debian from pyneo
<tugasoft> and after a few reboot while a was trying to upgrade debian, it never powered up again
<tugasoft> did anyone encouter the same problem?
<rafa> larsc: did you do the port of the wifi SDW-823 microSD driver to 2.6.32?
<wolfspraul> wpwrak: what's the model or your Roland 3D scanner again?
<rafa> tugasoft: upgrade... software upgrade? using apt?
<wpwrak> wolfspraul: it's an MDX-15
<rafa> tugasoft: have you tried to remove usb cable and battery for a while (in order to be sure that you will not be into usbboot for example) and then to try again?
<wolfspraul> wpwrak: thanks!
<tugasoft> rafa: yes, tryed this.
<tugasoft> i was checking dmesg and lsusb at each try
<rafa> wpwrak: ah.. you have a modest MDX-15.. in china I buy cigarrettes and they will give me a mdx-15 as change if they do not have coins :)
<tugasoft> the device is not detected at all.
<rafa> tugasoft: have you tried another usb cable?
<rafa> maybe the battery needs power and you cable is not okey
<rafa> your cable
<wpwrak> rafa: ;-))))
<tugasoft> red led turns on when I  plug the usb
<wpwrak> rafa: the mdx-15 is indeed the lowest-end model they have. there's a slightly bigger one with the same features, the mdx-20. luckily, the ben has just the right size for the mdx-15 ;-)
<tugasoft> but battery seems to be empty, indeed, it doesn't even warms up
<tugasoft> do you know if it's possible to get a new motherboard for the ben?
<tugasoft> i'm working in an arduino project, and now it is blocked :(
<wpwrak> tugasoft: you should be able to run it just from usb, without battery
<rafa> tugasoft: I would try with another usb cable as well.. and yes, as wpwrak says.. you can try without battery
<tugasoft> if i plug usb only, the red led flashes very shortly and then nothing, i've tried several times
<tugasoft> haven't tried other cable
<rafa> tugasoft: so you upgraded debian by software right? with apt or something like that
<tugasoft> i will try now, thanks for the suggestion
<tugasoft> no, i just wanted to flash with new debian
<rafa> tugasoft: anyway.. you should see something in dmesg
<tugasoft> no apt-get
<tugasoft> wanted a clean install
<rafa> tugasoft: a.. so maybe boot loader or kernel is broken.. and you need to reflash again
<wpwrak> tugasoft: have you tried this ? remove usb and battery. wait 30 seconds. press and hold down the "U" button. plug usb. see if something shows up
<rafa> tugasoft: yes, wpwrak suggestion is good.
<rafa> wpwrak: if you did not flash properly bootloader.. U+button will work?
<rafa> or he will need to use the nice usbboot pins under battery?
<wpwrak> rafa: if the boot loader is broken, it won't work. but it's worth a try, considering how many difficulties people had with the pins
<rafa> yes :(
<rafa> wpwrak: some day I will try for one hour or less.. but I was thinking that nn was broken.. so you can imagine how many tries I did until it worked :D
<rafa> and I was..*
<wpwrak> rafa: yeah, it's a highly unreliable process that gets used in an unclear and disturbing situation. not a good combination.
<tugasoft> wpwrak: will try the U button
<tugasoft> and another usb cable too
<rafa> and check dmesg all the time or lsusb or whatever you use to realize that something is pluged
<tugasoft> i really loved the nanonote, and i'm requesting for a few more. but if this first one is broken i won't be allowed to buy more :(
<rafa> tugasoft: I guess that it is not broken.. maybe something was wrong when flashing.. and if it was the bootloader which is not in a good shape you will need to use the pins under battery to get usbboot and then to flash again
<rafa> tugasoft: I guess that all of us feel you feel now at least once :)
<rafa> us felt*
<wpwrak> tugasoft: also the USB port on the host can be a potential source of problems. the connectors sometimes wear out. (mini-USB surprisingly seems to be tougher. maybe because it's more fragile, so people automatically pay more attention)
<wpwrak> rafa: after a while, you get very nonchalant about electronics that pretend to be broken ;-)
<tugasoft> i've just tried to boot using the U key, then by shorting the pins under the battery, none worked.
<tugasoft> i will keep trying, but I would like to know if there is a way to know if this is broken or not
<tugasoft> tried the host usb with  a webcam and a usb hard drive, both work well
<wolfspraul> tugasoft: first order of business - relax :-)
<rafa> tugasoft: I have tried shorting pins around 30 times until it worked for me :(.. but if you know well that maybe a few tries are okey
<tugasoft> ok, I will keep trying
<wolfspraul> tugasoft: let's do this: remove battery, unplug USB cable
<rafa> tugasoft: you need to try and to know how all the stuff work
<wolfspraul> tugasoft: let me try to help you
<rafa> tugasoft: so you know which could be the problems
<wolfspraul> tugasoft: remove battery, unplug USB cable
<wolfspraul> first step
<wpwrak> rafa: did you try with that carbonized rubber ? (i would just solder the darn thing after a few misses :)
<rafa> tugasoft: there are a lot that you will learn with it ;)
<tugasoft> wolfspraul: i'm reading you, let's try again
<tugasoft> battery removed, ubs cable removed
<wolfspraul> close the nanonote, turn it upside down (so that you are looking at the open battery compartment)
<wolfspraul> you see the "usb boot pins" opening in the label there...
<tugasoft> yes, see them
<rafa> wpwrak: yes, I was trying with the carbonized rubbber.. but because it was the first time using that I was not being sure how many seconds to use it before button.. if I needed to release that before button.. a lot of questions
<wolfspraul> do you have the small carbonized rubber button that came with your NanoNote?
<wpwrak> rafa: ah yes, that adds to the confusion
<tugasoft> got the carbonized rubber
<wolfspraul> great!
<wolfspraul> your nanonote should now be lying flat (it's closed, battery compartment up), so you just put the carbonized rubber button right over the pins, and press down solidly to short the pins
<wolfspraul> you can press really firm, obviously you don't want to crush the device but other than that you can be firm.
<wolfspraul> really firm :-)
<wolfspraul> then, still holding that button down, you plug in the USB cable from the side (no need to open the nanonote, just leave it lying there with the usb boot pins shorted by pressing down)
<wolfspraul> sorry we are walking backwards a bit :-) on your host, you could have 'watch lsusb' running...
<wolfspraul> so the correct order is this:
<tugasoft> got the idea
<wolfspraul> 1. run 'watch lsusb' on your notebook/desktop
<wolfspraul> 2. plug the USB cable into the notebook/desktop already, but not into the nanonote
<wolfspraul> 3. unplug the USB cable on the nanonote side, remove the battery
<wolfspraul> 4. put device face down, press the carbonized rubber button really firm onto the usb boot pins
<wolfspraul> 5. plug the usb cable into the nanonote from the side, leaving the device closed
<tugasoft> i'm used to small electronic devices, I know how be frim yet gentle with them :)
<wolfspraul> 6. in the watch lsusb display, see whether 601a:4740 shows up
<tugasoft> firm yet gentle, sorry
<wpwrak> tugasoft: what's important here is that the contact must be made _while_ the system resets (i.e., while it starts receiving power up from usb)
<wolfspraul> if 601a:4740 does not show up, you can try to clean the usb boot pins with a bit of alcohol (just a wet cloth, no need for a whole drink for your nanonote...)
<wpwrak> tugasoft: i.e., the rubber button does not send a reset impulse or such but affects how the reset is executed
<tugasoft> wpwrak: by contact you mean short the usb boot pins?
<wpwrak> wolfspraul: pina colada ? :)
<wolfspraul> tugasoft: don't worry in my procedure everything necessary is already included
<tugasoft> scotch on the rocks for me, only
<wpwrak> tugasoft: yes. (or it would be the same for the U button i suggested earlier. wolfgang's procedure is a bit more low-level, so it works in even more desperate cases)
<wolfspraul> I owe you one if you can unbrick your NanoNote!
<tugasoft> ok, i will do the test, be back in a minute
<wolfspraul> my procedure works in all cases unless there really is a hardware defect, or the usb boot pins are unshortable
<tugasoft> got a question, my linux box has only usb 1 ports, is this an issue?
<wolfspraul> in tugasoft's case, I am 99.9% sure it's just a simple case of u-boot overwritten
<wolfspraul> his problems started after a (failed) Debian upgrade
<wolfspraul> tugasoft: shouldn't be. just use that one port.
<wpwrak> wolfspraul: i think the procedure should include also releasing the button. i suspect that a lot of people automatically think of it as a "reset button" and then diverge
<wolfspraul> fair enough. it needs to be clear that the usb boot pins need to be held short while the USB cable is plugged in.
<wpwrak> wolfspraul: (probably just software) yup. almost certainly nothing more
<wolfspraul> tugasoft: for safety, press down firmly even 1-2 seconds after plugging the usb cable in from the side
<tugasoft> \o/ yahoo!!!! it came back to life
<wolfspraul> for the pressure, I never measured but I think even 1-2kg or so should be fine
<wolfspraul> great!
<wpwrak> really needs to make the next, simpler, version of idbg :)
<tugasoft> guys I owe a beer or an orange juice for each one of you
<wolfspraul> I don't understand why so many people end up with bricked Nanos after Debian installs/upgrades.
<wolfspraul> those procedures don't seem to be very reliable...
<tugasoft> now I will (for sure) have flashing issues, but I think i will be able to handle them
<wolfspraul> tugasoft: your adrenalin can go down now first
<wolfspraul> :-)
<tugasoft> lauched a successful
<tugasoft> usbboot -c "boot"
<tugasoft> :)
<wolfspraul> Nanos may break, may die. but it's rare. and even then we replace them, of course! no worries.
<wolfspraul> from the 1000 we sold so far, we had about 5 or so genuine returns.
<wolfspraul> over time there will be more, but trust me if there is one thing I am motivated about it's customer support!
<wolfspraul> I love it!
<wolfspraul> those 5 all got a brand new NanoNote, of course.
<wpwrak> wolfspraul: did you ever find out what happened with the one where the cable seemed to be broken at the lcm side ?
<wolfspraul> wpwrak: those 5 we had were almost all 'lcm stays dark' cases
<wpwrak> wolfspraul: (customer support) worried about your karma after om ? :)
<wolfspraul> so the NanoNote boots up, you can ping/ssh into it, but screen stays dark
<wolfspraul> tugasoft: if you tell me that that's what you see I would be more worried :-)
<wolfspraul> I always loved customer support.
<wolfspraul> brings me down to earth, it's just great
<wolfspraul> wpwrak: so in those cases, I think mostly it has to do with the FPC or connector on the mainboard
<wpwrak> wolfspraul: i mean the one where the display worked intermittently when he pressed down on the lcm case. you did some support session about that one here on irc.
<wolfspraul> one time there was a little hole in the FPC
<wpwrak> oh, cute :)
<wolfspraul> wpwrak: yes sure, we just replaced it with a new one.
<wolfspraul> we have not yet done detailed analysis on this, it's currently with David in Barcelona, 'out of service'
<tugasoft> wolfspraul:
<tugasoft> got an error that says: can't read bulk data from Ingenic device:64
<wpwrak> wolfspraul: ah, okay. should be fun to find out what went wrong there.
<wolfspraul> the fpc through the hinge is definitely the #1 reason for hardware problems so far, but even then it's rare, like I said about 5 for the first 1000 we sold
<wolfspraul> tugasoft: which commands did you run in usbboot?
<wolfspraul> I only use usbboot to flash u-boot, the rest I do after booting Linux from microSD
<wpwrak> wolfspraul: i don't think 99.5% is so bad a yield. of those 5, how many were actually broken and how many just needed a re-seating of the cable ? (well, the one with the hole sound like really dead.)
<tugasoft> if i may allow myself to share my history with you, I also work in customer support, I'm  a support engineer :) for  a French company
<wolfspraul> good
<wolfspraul> a company that listens to their support engineers will be a successful company
<wolfspraul> I hope they listen to you then!
<wolfspraul> let's try to get your Nano back to life first...
<tugasoft> the have to, we do a lot of noise :)
<wolfspraul> when did you get that bulk data error?
<wolfspraul> you ran reflash_ben.sh
<wolfspraul> ?
<tugasoft> usbboot -c "boot"
<tugasoft> usbboot -c "nprog 0 openwrt-xburst-qi_lb60-u-boot.bin 0 0 -n"
<tugasoft> the second command gives me the error
<wolfspraul> hmm
<wolfspraul> if you don't mind erasing the entire NAND, try "nerase 0 4096 0 0" after the "boot" command
<wolfspraul> first turn the NanoNote off (unplug usb cable), then the usb-boot pin drill again...
<tugasoft> ok
<tugasoft> there's the output
<tugasoft> if anyone is interested
<wolfspraul> if that bulk data error is still there, maybe you need to try on another Linux machine
<wolfspraul> unfortunately yours only has 1 USB port
<wpwrak> tugasoft: did you do the nerase ?
<tugasoft> wpwrak: not yet
<wolfspraul> if you have a USB hub, you can also try to plug the NanoNote in _behind_ the USB hub. just to compare.
<rafa> tugasoft: the nerase is important I guess
<tugasoft> i will try it
<wolfspraul> rafa: but the 'bulk data' error is a usb problem
<wolfspraul> shouldn't matter nerase or not
<wpwrak> tugasoft: nerase should come before the nprog.
<wolfspraul> if you have a usb hub, try to put your NanoNote behind the usb hub
<rafa> wolfspraul: IIRC I got that messag when flashing the bootloader
<wolfspraul> if you have another Linux machine, try to run usbboot on that machine
<wpwrak> wolfspraul: so an nprog failure is reported properly, not just by "hanging" up ?
<wolfspraul> sure, tugasoft : try inserting the 'nerase' after boot first...
<rafa> wolfspraul: and then I was thinking that it was not able to check because few data is read.. or something like that
<rafa> wolfspraul: then I continue with the flashing process... kernel, rootfs
<wolfspraul> wpwrak: I have this 'usbboot' thing, I looked at the sources too much.
<rafa> and then all the read/check are okey
<rafa> wolfspraul: and finally my nn boots okey
<rafa> wolfspraul: I will try to flash to report that message
<wolfspraul> but the alternatives are not ready yet, let's see that we get tugasoft off the ground
<rafa> when flashing the first file
<tugasoft> here's the output fron nerase
<tugasoft> it ends like: Force erase, no bad block infomation!
<wpwrak> i think this looks good
<rafa> yes
<tugasoft> ok,  i will try the next step
<wpwrak> the output is indeed quite confusing ;-))
<tugasoft> got the same error :(
<wpwrak> argh :-(
<tugasoft> i will try will a newer laptop
<tugasoft> the first flash was made with a fresh debian in a newer laptopt and went well
<tugasoft> so i will have to wait until tomorrow
<wpwrak> if it's really a usb problem, changing cable or just retrying a few times can help
<tugasoft> however, you gring back my nano to life :)
<tugasoft> bring
<wpwrak> changing cable also means you unplug and replug, which occasionally also solves problems
<rafa> tugasoft: that is why I said that all of us felt that at least once :) (that our machine was broken).. I do not why you geeks do not have patience :D
<tugasoft> will try with the original cable, but it think now the problems comes from the usb host, it's a very old laptop that I use as a webserver and has and old debian install, old kernel...etc...
<tugasoft> rafa: you are 100% right
<tugasoft> geek means no patience
<tugasoft> allways full throttle
<tugasoft> :)
<wpwrak> tugasoft: (usb host) okay. sometimes, very old stuff can act a little funny indeed.
<rafa> tugasoft: ;)
<rafa> tugasoft: but then .. some guys like wolfspraul or wpwrak help to remove doubts :)
<wolfspraul> tugasoft: if you have a minute, try this
<wolfspraul> then get your nanonote into a fresh usb-boot state (0x601a:4740 showing up)
<wolfspraul> then run "xbboot -u 0x80600000 openwrt-xburst-qi_lb60-zImage-initramfs.bin"
<wolfspraul> and let us know what happens...
<wolfspraul> (maybe nothing, but since you are at it maybe you can try real quick)
<rafa> wolfspraul: did you get some way to boot a kernel with a initramfs?? I tried a time ago.. without success.. I wanted to have an initramfs with a boot menu and kexec.. to choose the system to boot and also to upgrade the rootfs of NAND or sd..
<wpwrak> wolfspraul: btw, which is the nicer one again, usbboot or xboot ?
<wolfspraul> yes sure it works sometimes (just pasted a link). but it's not robust and well documented enough yet.
<wolfspraul> xbboot is a subset, it only supports loading a binary into ram and executing it
<wpwrak> same code base ?
<wolfspraul> in the long run that's much nicer, we could have a nice rescue initramfs and then do the rest from there
<wolfspraul> some codes are reused, but mostly from scratch (xbboot is very short)
<wolfspraul> it's just a few hundred lines of code
<wpwrak> ah, nice
<rafa> wolfspraul: yes.. that was the idea I wanted to use.. an initramfs as rescue, upgrade, system chooser
<tugasoft> got no xbboot
<tugasoft> do you have a link for a .deb file?
<tugasoft> i can search by myself too
<wolfspraul> tugasoft: how did you install usbboot?
<wolfspraul> maybe you already have the xbboot binary
<wolfspraul> if not, never mind, it's just a fun test since you are here and responsive and friendly :-)
<tugasoft> wolfspraul: dpgk -i usbboot.......
<wolfspraul> are you sure you dont' have xbboot?
<wolfspraul> I think it's in the same package
<wolfspraul> just type 'xbboot' - what happens?
<tugasoft> not found
<tugasoft> but I'm curious, I want to give it a try
<tugasoft> i read about this a few days ago
<wpwrak> tugasoft: did you type  xboot   or  xbboot  ? (here on irc, you did it right, but that may be an easy typo)
<tugasoft> ok, just figured out, I got and old usbboot .deb
<tugasoft> will try tu upgrade to 201004
<wolfspraul> 201009 seems the lates
<wolfspraul> latest
<kyak> wolfspraul: does it mean we are close to having that boot menu?
<wolfspraul> which boot menu?
<wpwrak> if the usbboot is ancient, could that also cause this sort of usb error ? we know that the 201004 has a command-line parsing problem that also caught a few people.
<kyak> the one rafa mentioned, with boot choises and rescue
<wolfspraul> I think it will take more time, so 'not close'.
<kyak> but according to what you described, it already works - only needs some user interface
<wpwrak> that should be a worthwhile task for the forth aficionados. that's the sort of things forth is actually good for :)
<wolfspraul> I think it's quite buggy still.
<wolfspraul> wpwrak: I have a question about some idbg pictures
<wolfspraul> what is the difference?
<wolfspraul> it seems this one pad at the top right is mostly scratched/washed off in top3
<wolfspraul> is that on purpose?
<wolfspraul> is that what 'top3' should document?
<qi-bot> [commit] kyak: MPlayer: added mp3 support via libmad; see README http://qi-hw.com/p/openwrt-packages/a4873ed
<qi-bot> [commit] kyak: Merge branch 'master' of projects.qi-hardware.com:openwrt-packages http://qi-hw.com/p/openwrt-packages/bf179f8
<wolfspraul> or is it just a failed attempt and we can delete that picture?
<wpwrak> no. that was an etching problem
<wpwrak> not sure what it should document ;-) maybe you just snapped picture of all the boards within reach :)
<wpwrak> the boards both look usable. they're of course v1, not v2. so the contacts are different
<wolfspraul> kyak: if you are adding mp3 support please make sure it's properly disabled unless CONFIG_BUILD_PATENTED is on
<wolfspraul> I think I got those pictures from you, I just didn't know whether this 'removed pad' was intentional or not
<wpwrak> you see the different arrangement here: http://www.almesberger.net/misc/ben/idbg-v2-install.jpg
<wolfspraul> if it's not, I will delete all picture that only differ in this 'removed pad' from another picture we have
<wpwrak> ah, so i was just snapping pictures of all the boards ;-)
<tugasoft> xbboot gives this: Info - found XBurst boot device.
<tugasoft> set_addr 80002000h
<tugasoft> bulk_write successfully wrote 2484 bytes.
<tugasoft> start1 80002000h
<tugasoft> VR_GET_CPU_INFO JZ4740V1
<tugasoft> set_addr 80600000h
<tugasoft> Error writing 3825664 bytes (result -110).
<tugasoft> it repeats endlessly
<wolfspraul> hmm, OK
<wolfspraul> it uses the same stage1/stage2 as usbboot
<wolfspraul> next idea: try another Linux notebook/desktop
<wolfspraul> thanks for trying!
<kyak> wolfspraul: good point..
<tugasoft> thanks for suggesting it
<wpwrak> it could be that i made a picture of each board as it went through production, to help with analyzing problems later, if any would creep up. (such as a bad trace at a place where i can't see it)
<tugasoft> my other laptopt is in the office, so i will suspend the tests until tomorrow
<tugasoft> thank you very much for you support
<wolfspraul> kyak: ah definitely. Please help to keep mp3 out unless the BUILD_PATENTED flag is on.
<tugasoft> see you
<tugasoft> bye
<wolfspraul> it was introduced just for that purpose into OpenWrt
<wolfspraul> cu
<wolfspraul> tugasoft: thanks for you patience! cu tomorrow...
<qi-bot> [commit] kyak: MPlayer is too good not to depend on @BUILD_PATENTED http://qi-hw.com/p/openwrt-packages/cebe754
<kyak> wolfspraul: let it be the whole MPlayer so far
<kyak> maybe later it can be built with reduced options, patent-free
<wolfspraul> kyak: isn't mplayer already included in another openwrt package feed?
<larsc> nope
<wolfspraul> oh
<wolfspraul> :-)
<kyak> yes, no :)
<wolfspraul> wpwrak: ok, so we delete the pics with etching problem? at least I will add a comment that documents this as an unintentional etching problem
<wolfspraul> are those boards still functional? or broken?
<wpwrak> wolfspraul: i think you can just delete the slighly defective ones, yes. they don't show anything interesting. i think the board was still usable.
<wolfspraul> ok will delete
<wolfspraul> thanks
<kyak> wolfspraul: oh, i just noticed:
<kyak> hooks/post-update: line 24: echo: write error: Broken pipe
<kyak> after git push to openwrt-packages
<kyak> but push went fine, as well as announce here in IRC
<wolfspraul> hmm
<wolfspraul> first time I hear that
<wolfspraul> thanks for reporting
<wolfspraul> kyak: can you keep an eye on it? let's see whether it happens again, I do nothing for now :-)
<kyak> wolfspraul: sure
<kristianpaul> Is it mandatory erase all NAND when reflashing a Ben with a  new openwrt/xbusrt vesion?
<wolfspraul> no, actually we should never do that. in a perfect world the oob and bad block data would always be preserved, starting from production of the NAND chip.
<wolfspraul> but we are far from a perfect world :-)
<kristianpaul> ok so i add that to the wiki in order to advice?...
<kristianpaul> but then how to get new bad block data info?
<wolfspraul> over time as bits fail
<kristianpaul> ok
<kristianpaul> ahh
<kristianpaul> something is woring with xbusrt backfire
<kristianpaul> wrong*
<kristianpaul> or not
<kristianpaul> wait
<kristianpaul> i knew it
<kristianpaul> i donmt why in the last backfire the /etc/profile is not same as the one stored at qi_lb60/files/etc
<kristianpaul> CONFIG_DEFAULT_base-files=y
<kristianpaul> is that okay this way?
<kristianpaul> bettwe writes a mail
<kyak> what do you mean?
<kristianpaul> i built the last branch of backfire for the xbusrt
<kristianpaul> i noticed that the mgnu2x and other SDL apps not started
<kyak> you have to copy manually those files to your Ben
<kyak> these are not included into the image
<kristianpaul> i dont have too
<kristianpaul> why??
<kristianpaul> if is a the stable branch, isnt?
<kristianpaul> or where is the stable branch? (in source code not images and flashing scripts)
<kyak> i would call it development
<kristianpaul> is no sense devel an app when the source code differ with an image thats seems to be stable
<kristianpaul> at least for me
<kristianpaul> sure i can copy
<kristianpaul> but i will not
<kyak> sorry, i don't seem to understand you at all
<kristianpaul> at least you know how to tell openwrt include those files
<kristianpaul> afaik nobody does :(
<kristianpaul> back to write the mail
<kyak> btw, i have a small script
<kristianpaul> anywaay thanks for helping kyak  .)
<kyak> which i upload to Ben and run every time after flashing
<kyak> it would fetch all latest files from git and also perform some other settings via uci
<kristianpaul> oh
<kyak> this way i don't have to setup Ben manually every time after i reflash it
<kristianpaul> but why aditionals scripts, is that i cant be done in the openwrt .config?
<kristianpaul> or your script is related with the openwrt .config ?
<kyak> but i have mu very own custome settings
<kyak> *my
<kristianpaul> i see
<kristianpaul> is this script public? i'll like see it
<kyak> hm, let me check.. i'm not at home right now
<kristianpaul> oh np when you able too
<kristianpaul> s/too/to
<kyak> no, can't get it right now.. maybe in several hours
<kyak> it's pretty dumb
<kyak> it sets my tclshrc, nighskyrc, so on
<kyak> sets some useful links, enable mounting of card and ubifs (data)
<kristianpaul> please share it in the wiki if you want
<kyak> FH44 2I
<kyak> will do
<kristianpaul> wpwrak: nice but, what are the color balls for?
<kristianpaul> wpwrak: where is that STL i want try print it
<kristianpaul> looks really nice
<wpwrak> they mark the coordinate axes. green is x at 10, 20, 30 mm. blue is y. yellow is z.
<wpwrak> (stl) ah, there's one little complication :) so far, this is pov-ray only
<kristianpaul> ouch
<kristianpaul> he
<kristianpaul> okay no hurries
<wpwrak> i don't know the other formats. in theory, it shouldn't be too hard to generate them, having the pov-ray generator.
<wpwrak> of course, i'm hoping that someone already familiar with STL or such would step in :)
<kristianpaul> ah you took the pij file to pov ray?
<kristianpaul> wow this nanomap is really fast, is because qt?
<wpwrak> kristianpaul: i took the .csv files, then aligned the faces with solidify (in the cae-tools project), and finally generated .pov with solidify
<bartbes> okay, since #jlime seems to be quiet
<bartbes> can jlime mount fat32?
<kristianpaul> hmm
<kristianpaul> not sure if there is support in kernel for that
<kristianpaul> but, are you running jlime from NAND?
<bartbes> no
<bartbes> well, I am not running it at all atm
<bartbes> but I will be running it from sd
<kristianpaul> and you have othe fat in the sd
<kristianpaul> i see
<bartbes> as 3rd partition
<kristianpaul> i think is a kernel thing
<bartbes> going to use it as home, and share it between owrt and jlime
<kristianpaul> not sure is rafa enaable it
<bartbes> well, there's an easy way to find out ;)
<kristianpaul> inded
<bartbes> also, do I need the uimage?
<bartbes> it isn't mentioned in the guide
<kristianpaul> is all package in the tarball
<kristianpaul> but make sure you have last uboot
<bartbes> the wiki lied
<bartbes> 126 mb isn't enough
<bartbes> wait a sec.. it was 129..
<bartbes> ah well
<bartbes> dinenr
<bartbes> *dinner
<kristianpaul> :)
<kristianpaul> wpwrak: http://en.qi-hardware.com/wiki/File:Roland_scanning_nanonote.jpg is familiar with you?
<kristianpaul> wow long process
<wpwrak> kristianpaul: very :-)
<kristianpaul> guess cheaper?
<wpwrak> (very) familiar and long, actually :)
<wpwrak> i think it's about usd 3000 in the us these days.
<kristianpaul> :/
<kristianpaul> check this (http://wiki.makerbot.com/cyclops) is not so accurate but you think could be?
<kristianpaul> and i can buy it ;)
<kristianpaul> if i want and save some money sure
<wpwrak> i think the resolution is quite low. but yes, this sort of optical system has a number of benefits as well. e.g., you have zero contact force, you can easily change directions, and it's fast
<wpwrak> the sort of contact scan i'm using is a somewhat obsolete technology. alas, very accurate optical scanners aren't cheap either.
<wpwrak> when i bought the machine, i actually didn't care much about the scanner. i only undusted the scan head when wolfgang mentioned that he didn't have any cad data :)
<kristianpaul> hey wolfgang took great pics from shenzhen  http://en.qi-hardware.com/wiki/Special:Contributions/Wolfgang_Spraul
<qi-bot> [commit] Werner Almesberger: Added auxiliary projections to help mis-levelling with more confidence. http://qi-hw.com/p/cae-tools/a3f17c5
<qi-bot> [commit] Werner Almesberger: solidify/batcvr.sfy: found a better inclination for the top face http://qi-hw.com/p/cae-tools/f635ac9
<kristianpaul> kyak: thanks
<kyak> np!
<kristianpaul> btw xianfus respond my mail it just was need a simbolic link
<kristianpaul> xianfu*
<kristianpaul> files -> data/qi_lb60/files/
<kristianpaul> thats it !
<kyak> great!
<kristianpaul> yeah
<kyak> with libmad, mplayer is consuming only 75% CPU.. runs very nice and smooth
<kyak> stil requires some polishing, like enabling osd
<kyak> but in genral, it works!
<SiENcE> whats the best dist for nanonote?
<kristianpaul> it depens on you?
<kristianpaul> tell us yours needs
<SiENcE> i mean, where do i have good apps like mplayer aso.,  and whats the best dist to compile and develop nativ on nanonote?
<kristianpaul> jlime !
<SiENcE> but its not compatible with dingoo?
<SiENcE> dingux?
<kristianpaul> dont thinkso
<kristianpaul> because libc mainly if i remenber well
<rafa> kristianpaul: we checked and dingoo binaries run.. dont ask us why :D
<lekernel> kyak, for playing mp3s?
<kristianpaul> rafa: ah?? :O
<kristianpaul> ok
<kyak> lekernel: no, playing video with mp3 sound
<rafa> kristianpaul: no idea why
<rafa> kristianpaul: we tested the playstation emulator and that kind of stuff that dingoo has
<kristianpaul> SiENcE: great for you :)
<SiENcE> thats great
<SiENcE> :)
<kristianpaul> kyak: or playing ogv?? ;)
<rafa> SiENcE: if you want to build in nn, kristoffer, already explained what to install at : http://www.jlime.com/wiki/documentation/user/nanonote/muffinman .. "Getting Development Environment Going"
<SiENcE> rafa, thanks
<kyak> kristianpaul: if i ever see ogv file, i would try
<SiENcE> i really want to adjust my ports for dingoo to nanonote
<rafa> SiENcE: that would be great.. zear wants to do that as well I guess
<kristianpaul> kyak: lets do ti !
<kristianpaul> :)
<SiENcE> rafa, sounds good. what about an future nanonote with usb-host to use wifi?
<kristianpaul> talking about usb-host is it posible implement it with linux, larsc ?
<rafa> SiENcE: no, sorry
<SiENcE> :(
<SiENcE> thats all i want on nano, dingoo etc.
<rafa> SiENcE: there is some weird wifi SD which works
<kyak> kristianpaul: only plays sound.. i would need to enable libtheora
<kyak> luckily, it's in openwrt
<SiENcE> ah na thats no solution
<SiENcE> too expensive, too buggy
<rafa> yeah..
<rafa> SiENcE: werner is working in some kind of wifi.. making the whole stuff (hw/sw)
<kristianpaul> kyak: but the image is okay?
<SiENcE> rafa, ok
<kristianpaul> ahh just sound
<kristianpaul> sorry
<SiENcE> thanks for the infos
<SiENcE> rafa, thx. Jlime works good :)
<kristianpaul> :D
<SiENcE> :(  usb ethernet has rndis
<SiENcE> without rndis it would work also on windows
<wpwrak> SiENcE: well, it's not quite wifi. it's ieee 802.15.4, the stuff underneath things like zigbee. in terms of real-life functionality one can expect, i'd say something in the range of a wireless keyboard or a wireless remote control. of course, you'll get to run tcp/ip over the wireless link, so you can do more interesting applications than just sending a few button-presses.
<kristianpaul> wpwrak: have you in mind a usb dongle for the other side?
<kristianpaul> or something like an acess point maybe?
<wpwrak> kristianpaul: you mean something like this ? http://www.almesberger.net/misc/ben/wpan/board-100813.jpg
<wpwrak> kristianpaul: well, change the connector and rotate things. then you have a dongle.
<kristianpaul> ahh that usb is for the compter?? i tought was a debuging boarad..
<kristianpaul> hehe yes wpwrak
<SiENcE> wpwrak, but where to attach? does nano has usbhost?
<SiENcE> ah
<SiENcE> i see
<SiENcE> does jlime has mc ?
<kristianpaul> mc?
<kristianpaul> mmc?
<kristianpaul> uSD ?
<kristianpaul> yes
<SiENcE> midnight commander
<kristianpaul> ahh
<kristianpaul> sure
<kristianpaul> may be not by default but can be installed
<SiENcE> how do i install stuff on jlime?
<kristianpaul> first it al
<kristianpaul> l
<kristianpaul> opkg update
<SiENcE> sorry for my questions. its the first time using jlime
<kristianpaul> then opkg install foo
<kristianpaul> np
<SiENcE> opkg :-) ok
<kristianpaul> opkg search foo | grep boo
<kristianpaul> etc..
<SiENcE> i know
<SiENcE> i searched the name of the package manager
<kristianpaul> SiENcE: you should  join #jlime too
<kristianpaul> as others here
<SiENcE> ok
<qi-bot> [commit] kyak: MPlayer: enable OSD support http://qi-hw.com/p/openwrt-packages/2d9742e
<SiENcE> mh dingux apps dont work on jlime
<Ayla> does jlime uses uclibc?
<qi-bot> [commit] kyak: MPlayer: enable volume control via Ben volume keys http://qi-hw.com/p/openwrt-packages/7c7d365
<rafa> SiENcE: I ran psx4all in jlime from dingux
<SiENcE> mh i have to test this
<SiENcE> rafa, where is the correct manual?
<SiENcE> i cant find it
<SiENcE> rafa, ok i know this. i though there is a bigger one
<qi-bot> [commit] Werner Almesberger: Experimental alignments for solidify. http://qi-hw.com/p/ben-scans/4226d0b
<qi-bot> [commit] Werner Almesberger: Correct direction of x inclination of z0. http://qi-hw.com/p/cae-tools/5170410
<qi-bot> [commit] Werner Almesberger: Make new/run/pov/disp are now configurable when invoking make. http://qi-hw.com/p/cae-tools/ffb0d99
<qi-bot> [commit] Werner Almesberger: Moved batcvr.sfy over to ben-scans. Removing it here. http://qi-hw.com/p/cae-tools/1c183e0
<aisa> I'm trying to flash my nanonote for the first time, and I need someone to brainstorm with.
<aisa> Is anyone available to listen to my setup and offer advice?
<xiangfu> aisa: yes.
<aisa> xiangfu: I believe I might have solved my problem, but here is what I'm dealing with.
<aisa> I'm trying to flash my nanonote for the first time.  This page:
<aisa> warns not to use a linux virtual machine.
<aisa> Alas, my only computer is a mac, and I have VMWare for my linux box.
<aisa> So I have purchased a microSD card, for which I want to use to update my image.
<aisa> however, I cannot get this microSD card to mount through my virtual machine.
<aisa> so I cannot run mke2fs....
<aisa> what I have decided to do, is mount the micro sd card on my nanonote,
<aisa> and copy the latest image to the device by transfering it to my nanonote.
<aisa> then I will update my nanonote from the microsd an normal.
<aisa> If this fails, I won't be able to try again...
<aisa> because I won't have any way to read the ext2fs micro SD card except on my nanonote.
<aisa> but in this case, I will find an old computer which I can install debian on and go from there.
<aisa> I am curious why I can't update the ben NanoNote from a virtual machine.
<aisa> The wiki tells me not to, but doesn't explain why.
<mth> there is an ext2 fuse package for macports, but I don't know if it also includes mke2fs
<aisa> Good, then I can try this in preference to hunting down a computer to install linux on, if my flash fails.
<mth> alternatively, you could create a disk image of the same size as the ext2 partition and format that in the VM
<mth> and after that, shut down the VM and convert it to a raw image
<aisa> now that is a fantastic idea, then I could dd it to the micro sd.
<mth> qemu has a tool to convert between vmware image formats and raw images
<xiangfu> aisa: why we can not use VM, because the VM usb port give strange error. some VM work , some not. if you relfash in VM maybe all command success. but the NanoNote will not boot.
<wpwrak> aisa: the VM warning is probably because some VMs can get USB wrong. but if you have a fallback solution, i think you can just go ahead and give it a try. worst case is that you'll join the ranks of those fumbling with the carbonized rubber button :)
<mth> a third option would be to find a linux live CD that can boot on a Mac
<xiangfu> another option is install linux in Mac :)
<xiangfu> aisa: I remember someone success build the "xburst-tools" in mac.
<aisa> mth: a quick search reveals that there might be an ubuntu live cd that I can boot on my powerbook, this is fantastic.
<aisa> xiangfu: This is my employer's computer, and I would have a terrible time testing our software if I couldn't run Mac OS.  Without this problem, I would have already installed linux :-)
<aisa> xiangfu: I had not thought to try this, but it makes sense.
<aisa> I may eventually do that to make it easy on myself.
<xiangfu> I found a carbonized rubber button picture : http://image.itmedia.co.jp/l/im/pcuser/articles/1004/01/l_og_nano_034.jpg
<qi-bot> [commit] Xiangfu Liu: update the distribution to [unstable] http://qi-hw.com/p/xburst-tools/f1bc77a