**** BEGIN LOGGING AT Thu Feb 25 02:59:58 2010 Feb 25 03:47:55 Hello? Feb 25 04:59:41 cgkm: Hello Feb 25 05:00:02 Good evening rockin angstrom types! Feb 25 06:44:51 question: does this message mean that i can't run the jffs2 file system that was produced by 'bitback console-image'? Feb 25 06:45:09 message: jffs2 warning: (829) jffs2_sum_write_sumnode: not enough space for summary, padsize = -137 Feb 25 06:45:39 typo above *bitbake Feb 25 16:23:25 anyone here ever have any luck with kexecboot image install on a poodle? Feb 25 16:25:00 (that's a zaurus sl-5600) Feb 25 16:26:14 been about a billion years since I saw a poodle Feb 25 16:27:25 any ancient memories about how kexecboot worked on it? Feb 25 16:28:23 heh it was long before kexecboot, but poodle is not much different from the c1000/c3x00 series Feb 25 16:28:56 c7x0 series as well Feb 25 16:30:49 I think i used kexecboot on my tosa... Feb 25 16:31:30 or at least something worked like it...it was nice to be able to boot from sd, cf or internal flash... Feb 25 16:32:01 but I can not remember how I did it.. Feb 25 16:35:54 recently i successfully flashed it with the usual files: updater.sh and zImage (from the installer kit that bitbake produced) Feb 25 16:36:03 when i couldnt boot any other rootfs from that install Feb 25 16:36:50 i reflashed with the rootfs (blahblah.jffs2 -> initrd.bin) to allow boot with that rootfs in nand Feb 25 16:37:01 only that boot freezes Feb 25 16:37:26 and i want to return it to a "simpler" state by reflashing with only zImage (and no rootfs in nand) Feb 25 16:38:08 when i reflash with only updater and zImage, i still get the the jffs2 fs available... how to remove it from system? Feb 25 16:38:30 or if i can't, then i need to troubleshoot it to get it to boot correctly. Feb 25 16:38:52 would like to wipe it if i can though, to keep it "simple" Feb 25 16:41:03 the jffs2 rootfs is mounted on /dev/mtdblock2, but i cant get to a prompt to remove it Feb 25 19:22:23 ok so here's another attempt at resolving an issue with my console-image rootfs Feb 25 19:22:55 when i unpack the console-image.tar.gz onto my target SD, there are 22 broken symlinks Feb 25 19:23:30 none appear to be dangling links Feb 25 19:23:45 (i.e. the target of link is present) Feb 25 19:24:29 do i need to go in and manually relink them? or did bitbake intentionally not link them? Feb 25 19:24:54 regardless, i am unable to boot the rootfs from the kexecboot loader on my unit Feb 25 19:25:12 (unit=zaurus sl-5600=poodle) Feb 25 19:26:00 next step is to manually reset the symlinks, but am curious why this is happening? Feb 25 19:27:39 (correction for clarity: console-image.tar.gz = console-image.rootfs.tar.gz) Feb 25 19:50:07 it is highly likely poodle support is broken Feb 25 19:50:11 no-one is working on it Feb 25 19:50:27 can you give an example of a broken link? Feb 25 19:50:47 I dont see that for any of the other 5 machines I have Feb 25 20:03:09 sure, thanks XorA. listing follows: Feb 25 20:03:15 35901 0 lrwxrwxrwx 1 root root 13 Feb 25 12:02 ./bin/lsmod -> /bin/lsmod.26 Feb 25 20:03:17 35913 0 lrwxrwxrwx 1 root root 16 Feb 25 12:02 ./bin/chattr -> chattr.e2fsprogs Feb 25 20:03:19 43826 0 lrwxrwxrwx 1 root root 9 Feb 25 12:02 ./mnt/cf -> /media/cf Feb 25 20:03:21 43827 0 lrwxrwxrwx 1 root root 10 Feb 25 12:02 ./mnt/net -> /media/net Feb 25 20:03:23 43828 0 lrwxrwxrwx 1 root root 10 Feb 25 12:02 ./mnt/ram -> /media/ram Feb 25 20:03:25 43829 0 lrwxrwxrwx 1 root root 11 Feb 25 12:02 ./mnt/card -> /media/card Feb 25 20:03:27 17948 0 lrwxrwxrwx 1 root root 23 Feb 25 12:02 ./usr/bin/scp -> /usr/sbin/dropbearmulti Feb 25 20:03:29 17951 0 lrwxrwxrwx 1 root root 23 Feb 25 12:02 ./usr/bin/ssh -> /usr/sbin/dropbearmulti Feb 25 20:03:31 17972 0 lrwxrwxrwx 1 root root 16 Feb 25 12:02 ./usr/bin/opkg -> /usr/bin/opkg-cl Feb 25 20:03:33 17992 0 lrwxrwxrwx 1 root root 23 Feb 25 12:02 ./usr/bin/dbclient -> /usr/sbin/dropbearmulti Feb 25 20:03:35 18141 0 lrwxrwxrwx 1 root root 33 Feb 25 12:02 ./usr/bin/psplash -> /usr/bin/psplash.psplash-angstrom Feb 25 20:03:37 20135 0 lrwxrwxrwx 1 root root 21 Feb 25 12:02 ./usr/lib/ConsoleKit/run-seat.d/udev-acl.ck -> /usr/libexec/udev-acl Feb 25 20:03:39 31878 0 lrwxrwxrwx 1 root root 19 Feb 25 12:02 ./sbin/init -> /sbin/init.sysvinit Feb 25 20:03:41 31893 0 lrwxrwxrwx 1 root root 13 Feb 25 12:02 ./sbin/lsmod -> /bin/lsmod.26 Feb 25 20:03:43 31894 0 lrwxrwxrwx 1 root root 14 Feb 25 12:02 ./sbin/rmmod -> /sbin/rmmod.26 Feb 25 20:03:45 31908 0 lrwxrwxrwx 1 root root 17 Feb 25 12:02 ./sbin/modprobe -> /sbin/modprobe.26 Feb 25 20:03:47 31916 0 lrwxrwxrwx 1 root root 23 Feb 25 12:02 ./sbin/makedevs -> /sbin/makedevs.makedevs Feb 25 20:03:49 31917 0 lrwxrwxrwx 1 root root 4 Feb 25 12:02 ./sbin/telinit -> init Feb 25 20:03:51 31928 0 lrwxrwxrwx 1 root root 15 Feb 25 12:02 ./sbin/depmod -> /sbin/depmod.26 Feb 25 20:03:53 31931 0 lrwxrwxrwx 1 root root 16 Feb 25 12:02 ./sbin/modinfo -> /sbin/modinfo.26 Feb 25 20:03:55 31938 0 lrwxrwxrwx 1 root root 15 Feb 25 12:02 ./sbin/insmod -> /sbin/insmod.26 Feb 25 20:03:57 11 0 lrwxrwxrwx 1 root root 12 Feb 25 12:02 ./linuxrc -> /bin/busybox Feb 25 20:03:59 this is result of executing '$ find -L . -type l -ls' Feb 25 20:04:15 they dont look broken Feb 25 20:04:28 this listing is a listing of the broken links Feb 25 20:05:49 !logs Feb 25 20:06:20 well that's embarrassing... Feb 25 20:07:19 i am too much of a noob to be embarrassed... what did i do wrong? Feb 25 20:07:39 at my level i can only be grateful for the feedback :o) Feb 25 20:07:47 sorry, I was talking about myself Feb 25 20:08:19 are you talking about the issue i posted wjward? Feb 25 20:08:36 kaz00: no, sorry Feb 25 20:09:13 kaz00: are you sure your not confusing the fact that the links reference / and therefore wont be complete until your SD is rootfs? Feb 25 20:09:40 XorA: you are a mind reader... that may very well be the case Feb 25 20:09:43 except... Feb 25 20:10:15 to truly find why it doesnt boot you will probably need a serial cable Feb 25 20:10:21 do you get the splash screen Feb 25 20:10:24 ? Feb 25 20:11:05 yes i do get the angstrom splash... Feb 25 20:11:21 so for serial access i have cd slot (=pcmcia) do i need special cable? Feb 25 20:11:37 well rm usr/bin/psplash and you will see boot messages Feb 25 20:11:42 on SD card Feb 25 20:11:51 ok ty. Feb 25 20:11:57 there is a socket under keyboard which special zaurus serial fits into Feb 25 20:12:08 they are getting quite rare now Feb 25 20:12:12 oh yes... the dock station? Feb 25 20:12:17 * Jonimus is glad his h2200 is finally fully working Feb 25 20:12:20 yes that connector Feb 25 20:12:26 cool. ok. Feb 25 20:12:33 jonimus: woohoo!!!! Feb 25 20:12:51 XorA: any Idea why the Lirc Module is not being built for my h2200? Feb 25 20:13:01 XorA: here's a question... Feb 25 20:13:04 Jonimus: lirc doesnt build with 2.6.X kernels Feb 25 20:13:12 the links that i listed as appearing broken... Feb 25 20:13:29 XorA: hmm the lirc site says it should support my device with the kernel I have... Feb 25 20:13:35 i also see relative paths for other executables in /bin e.g. pidof.sysvinit -> ../sbin/killall5 Feb 25 20:13:44 Jonimus: give it a try then, I gave up a coule of years ago Feb 25 20:14:05 kaz00: it just depends on how make install installs them Feb 25 20:14:31 my gui filemanager also lists the same links i mentioned as being broken links... which is what first clued me into that (if that is a "clue") Feb 25 20:14:36 ok Feb 25 20:14:39 XorA: well it did build so I'll try adjusting the --configure, where is what is run durring do_configure? Feb 25 20:15:00 so i will remove splash and then boot while hooked up to docking station? Feb 25 20:15:27 i may need some help accessing machine ... do i do it via terminal??? Feb 25 20:15:38 nvm I found it Feb 25 20:16:28 kaz00: you have a serial docking station? Feb 25 20:16:33 yes Feb 25 20:16:50 kaz00: then just use something like picocom -b 115200 /dev/ttyS0 Feb 25 20:16:51 ahh I need to modprobe lirc_sir Feb 25 20:16:54 well... whatever sharp came with Feb 25 20:17:03 ok will do Feb 25 20:17:11 * XorA has only ever seen usb docks :-D Feb 25 20:17:28 perhaps a silly question, but i did a 'git checkout origin/stable/2009 -b stable/2009', but under conf/distro still only see angstrom-2008.1.conf Feb 25 20:17:44 or is this more of an OE question? Feb 25 20:17:49 * kaz00 confesses he was about to ask whether it is actually usb cuz thats what plugs into computer :( Feb 25 20:18:15 no help to you then Im afraid Feb 25 20:18:30 bummer Feb 25 20:18:35 back to debug by guessing :-) Feb 25 20:18:47 us there an aftermarket cable that i can get? Feb 25 20:18:51 *is Feb 25 20:19:17 kaz00: check what linux says it is, the cable my show up as a USB to Serial Adapter Feb 25 20:19:24 thats how my device works Feb 25 20:20:51 there now it should build that driver Feb 25 20:22:10 noobtastic here. so mount doesnt show it, file manager doesnt show it, nor does dmesg... ??? Feb 25 20:23:12 dmesg has no output when you plug the usb cable in? Feb 25 20:24:21 nope. and unit is on, docking station is plugged into power adapter, unit is firmly seated in dock... usb cable plugged in... ??? Feb 25 20:24:44 power adapter is working (as i have reflashed many times lately) Feb 25 20:24:56 unplug and replug the USB cable Feb 25 20:25:23 then check dmesg Feb 25 20:25:31 ok. dmesg = nada. ? Feb 25 20:25:48 dmesg | tail says nothing new? Feb 25 20:26:00 correct. unfortunately. Feb 25 20:26:15 hmm then I'd say something is wrong with your dock :/ Feb 25 20:28:00 bummer. i only used it once years ago when it (briefly) had the hancom system on it... :( Feb 25 20:31:09 How do i tell bitbake to rebuild a packages? Feb 25 20:31:23 I added the lirc configure line but it's not rebuilding it Feb 25 20:32:28 bitbake -c clean lirc? Feb 25 20:32:33 then bitbake lirc Feb 25 20:32:40 KK thanks Feb 25 20:33:11 thanks Feb 25 20:34:04 also XorA it appears only the collie has broken lirc modules, or at least the kernel it uses has issues it appears Feb 25 20:35:01 Jonimus: they were all broken back when I tried Feb 25 20:35:09 Jonimus: I dont do zaurus anymore Feb 25 20:35:27 zaurus docks are real usb devices, not usb->serial Feb 25 20:35:40 unless you load the usb serial gadget on boot Feb 25 20:35:46 but that wont get you console Feb 25 20:35:58 hmm well it build mceusb so if I can get the sa1100 to built I'm all set Feb 25 20:38:20 bummer. seems odd that my system doesnt even see the usb dock. is there a cable that attached to the docking port on the bottom of unit? Feb 25 20:44:11 Hmm well it seems the sa1100 driver won't build... Feb 25 20:44:46 If I can't fix that then my device is basically useless :/ Feb 25 20:46:51 It looks like its a kernel config issue where lirc wants things that aren't enabled in the default kernel Feb 25 20:47:02 at least that is how it appears Feb 25 20:47:38 can you just enable them and rebuild the kernel? Feb 25 20:50:14 I think I see the issue, the lirc makefile is looking in the wrong place for auto.conf Feb 25 20:50:35 its looking in include/linux/ when its jsut in include Feb 25 20:51:11 * Jonimus tries again Feb 25 20:52:31 or wait no, its looking in the right place, and yet its not finding it :/ Feb 25 20:53:00 I guess I'll try some more this weekend, hopefully i can fix it or I'll be building on the device, which I'd rather avoid Id I can. Feb 25 21:40:19 I've been trying for about a week to get VLC working on my mini2440. No matter what version I build, I always get a seg fault in ld-linux,so.2. VLC guys said this is probably a toolchain thing; any suggestions? Feb 26 01:48:47 some (perhaps irrelevant) error messages and results from attempting to boot the console-kexecboot-rootfs from a kexecboot flashed zaurus poodle (sl-5600) Feb 26 01:49:36 if anyone thinks they might have $0.02 to offer and they are (morbidly?) curious i will do some cut & paste... Feb 26 01:50:44 with the CF wifi card removed the boot attempt hangs at: Feb 26 01:51:39 hwclock: can't open /dev/misc/rtc: No such file or directory. Feb 26 01:52:38 however with the CF wifi card in place, boot continues beyond this message and instead goes on... Feb 26 01:53:04 configuring ppp-dialin Feb 26 01:53:06 configuring dbus Feb 26 01:53:08 configuring avahi-autoipd Feb 26 01:53:10 configuring angstrom-fixup-hack Feb 26 01:53:12 configuring avahi-daemon Feb 26 01:53:14 system startup links for /etc/init.d/avahi-daemon alredy exist Feb 26 01:53:16 configuring libnss-mdns Feb 26 01:53:18 and hangs on the libnss-mdns config Feb 26 01:55:19 earlier i posted what i thought may be broken symlinks on the rootfs. after failed boot attempt of this rootfs, i noticed three additional broken symlinks in addition to the original set. these new ones are: Feb 26 01:55:45 > 2397 0 lrwxrwxrwx 1 root root 41 Feb 22 14:01 ./etc/zaurusd/mach-config-vars -> /etc/zaurusd/mach-config/mach-poodle-vars Feb 26 01:55:47 > 2398 0 lrwxrwxrwx 1 root root 46 Feb 22 14:01 ./etc/zaurusd/mach-config-funcs -> /etc/zaurusd/mach-config/mach-poodle-functions Feb 26 01:55:49 > 2393 0 lrwxrwxrwx 1 root root 20 Dec 31 1969 ./etc/resolv.conf -> /var/run/resolv.conf Feb 26 01:56:44 not much in terms of definitive results... but am hoping someone may have any thoughts/hints... ??? **** ENDING LOGGING AT Fri Feb 26 02:59:57 2010