**** BEGIN LOGGING AT Thu May 01 02:59:56 2008 May 01 12:48:51 hey May 01 12:49:12 hello all May 01 12:51:04 hey May 01 12:51:45 hey likewise May 01 15:24:32 yeah, angstrom runs on my collie :) May 01 15:25:34 do you think I can use the 2008 feeds? May 01 15:25:37 or is that a bad idea? May 01 15:28:27 joerg, what install kit did you use? mine always faild to flash ... zImage worked ok but i think the initrd.bin was broken May 01 15:28:49 j0wn, no install kit at all.... May 01 15:29:03 manually downloaded zimage and an altboot-jffs May 01 15:29:34 wait May 01 15:30:12 http://www.angstrom-distribution.org/unstable/autobuild/collie/ May 01 15:30:25 zImage-collie.bin May 01 15:30:55 altboot-console-image-collie.jffs2 May 01 15:34:50 you just rename that last one to initrd.bin then? May 01 15:34:58 yes May 01 15:35:11 hmm still wondering why mine failed May 01 15:35:21 il give it another go though May 01 15:57:22 j0wn, you probably flashed an initrd that was too big. May 01 15:58:10 ok this one seems to boot .. i gat the A thingy after alt boot and then nothing May 01 15:59:05 hi May 01 15:59:34 hi mickey|away May 01 15:59:40 hi mimecar May 01 15:59:44 sorry :) May 01 15:59:51 joerg, what did you select for altboot? May 01 16:00:15 xD May 01 16:01:09 j0wn, boot from sd card May 01 16:01:25 and on my sd card I untared the x11-image May 01 16:10:17 ok did you rename this one? May 01 16:12:05 ack i see May 01 16:12:07 heh May 01 16:21:51 joerg, im getting insmod failed cant access tty; May 01 16:22:37 its not loading the mmc driver May 01 16:22:43 yes.... May 01 16:22:52 that took me ages to find out the bug... May 01 16:23:07 j0wn, do you have a shell now? May 01 16:23:14 yeah May 01 16:23:21 ok May 01 16:23:22 no root though May 01 16:23:46 the problem is that not all modules required for sd access are loaded. May 01 16:23:46 oh i am root heh May 01 16:23:52 sure you are May 01 16:24:09 enter "altbootcl" at the prompt May 01 16:24:27 * CoreDump watches May 01 16:24:52 sorry May 01 16:24:54 altbootcl May 01 16:24:57 ok i got the alt boot control meny May 01 16:24:58 altbootctl May 01 16:25:05 great :) May 01 16:25:12 so go in the SD CF menu May 01 16:25:24 option 1? May 01 16:25:31 I think so May 01 16:25:50 ok i got 4 more options May 01 16:25:53 j0wn: write text you get with altboot.. May 01 16:26:09 lool May 01 16:26:15 are you all having these problems? :) May 01 16:26:25 sounds like it May 01 16:26:29 i ? May 01 16:26:40 j0wn, you have to choose the option where you can shange the kernel modules loaded May 01 16:27:19 ok thats option 2 .. ok option 2 for perm change May 01 16:27:27 absolutely May 01 16:27:48 ok what value we puuting in there? May 01 16:28:01 what is the current value? May 01 16:28:55 does'nt show it .. i have a choice of locomo_spi mmc_block mmc_spi May 01 16:29:43 im guessing its locomo as i see an error about it close to initial boot May 01 16:29:58 * CoreDump is still watching May 01 16:30:41 im guessing its prolly mmc_block May 01 16:31:20 I take it joerg has a working config. Sooooo...what is it? May 01 16:31:27 he does May 01 16:31:48 no May 01 16:31:56 ? May 01 16:31:57 the problem is that altboot uses insmod May 01 16:32:13 and insmod doesn't load dependencies automagically :P May 01 16:32:21 so it should be: May 01 16:32:23 unlike modprobe May 01 16:32:25 joerg: that is not a problem if all modules are loaded in the right order ;) May 01 16:32:32 locomo_spi mmc_core mmc_block mmc_spi May 01 16:32:53 ah im missing core May 01 16:32:58 joerg: that line works for you? May 01 16:33:07 j0wn, everybody is missing core :D May 01 16:33:13 CoreDump, yes May 01 16:33:17 hehe May 01 16:33:31 cofeineSunshine, to load mmc_block you have to load mmc_core before. May 01 16:33:39 nice, did you change anything else in the config? May 01 16:33:51 nope May 01 16:35:53 hehe seems my SD cards ext2 file system could be a little messed up May 01 16:36:13 * * mhentges has commited r81 into the altboot repository: May 01 16:36:13 * * Fix SD module loading for Collie once again, courtesy of joerg @ #angstrom May 01 16:36:21 ;) May 01 16:36:31 yeah May 01 16:36:33 thanks a lot May 01 16:37:14 CoreDump, I guess the people who maintain the collie port don't own such a machine? :P May 01 16:37:46 I mean...this is really easy to resolve. May 01 16:37:58 you do the insmod by hand then mmc_block.ko fails..... May 01 16:38:03 then you do modprobe mmc_block May 01 16:38:15 then you do lsmod and notice that it has loaded mmc_core as well. May 01 16:38:40 I'm the only one "working" on altboot, and I only have access to a spitz currently May 01 16:38:59 all of my 3 collies are dead May 01 16:39:31 he he... May 01 16:39:48 well I bought one for 40 euros on ebay a few weeks ago! May 01 16:39:51 CoreDump: mine is sleeping always May 01 16:40:26 And it doesn't help that the collie kernel guys change the kernel .config every couple of weeks heh (mmc_core used to be compiled into the kernel) May 01 16:40:57 why don't you work with a fixed kernel config? May 01 16:40:58 hmm May 01 16:41:04 I am using the "latest" 2.6.20.6 May 01 16:41:26 I do not have control over the versions used by angstrom =) May 01 16:41:57 directly no, but you can use a custom x11-image May 01 16:42:04 with a prefered version of kernel May 01 16:43:42 something odd here May 01 16:44:18 mine is trying to mount the mmc device that does not exist May 01 16:44:25 CoreDump, do you know when to expect sound support on collie 2.6? May 01 16:44:34 no idea, sorry May 01 16:44:40 j0wn, oh, that's the next problem May 01 16:44:41 the only device i have is mmcda1 May 01 16:44:49 hehe May 01 16:45:25 edit /etc/device_table May 01 16:45:25 i emailed pavel about how far he got .. he pointed me to his git release May 01 16:45:58 ive been trying to get a map as to where collie was in 2.6 what was there ( or semi there ) and what was still missing May 01 16:46:25 is there a list with funcionts doesn't work on angstrom? May 01 16:46:27 SD_DEVICE="/dev/mmcblk0p1" May 01 16:46:40 well May 01 16:46:46 vi /etc/device_table May 01 16:46:53 add these two lines: May 01 16:47:15 /dev/mmcblk0 b 640 0 0 254 0 - - - May 01 16:47:15 /dev/mmcblk0p1 b 640 0 0 254 1 - - - May 01 16:47:31 then "sync" May 01 16:47:36 and reset the device May 01 16:47:59 maybe the card is reachable under a different device file? May 01 16:48:08 hello? May 01 16:48:10 do you listen? May 01 16:49:31 ok doing it now May 01 16:49:49 the device nodes are not created May 01 16:49:53 that's the problem May 01 16:50:51 mmcda and mmcda1 are the old nodes from 2.4 times May 01 16:51:11 you can remove those two lines.... May 01 16:53:28 interesting, the other devices don't have mmcblk* in device_table as well. May 01 16:53:49 could be a udev problem where udev does not create the files but it should May 01 16:57:03 CoreDump, udev is running at that early time? May 01 16:57:11 good point May 01 16:58:16 cofeineSunshine, it is not May 01 16:58:38 CoreDump, /etc/init.d/devices creates the device nodes May 01 16:59:01 /sbin/makedevs -r / -D /etc/device_table May 01 16:59:35 well, reading the sd script, altboot itself is supposed to create the nodes May 01 17:01:15 where? May 01 17:01:18 in altboot.func? May 01 17:01:57 joerg: could you do an "ls -R /sys/block/mmcblk0/mmcblk0p1/dev for me in "init=/bin/sh? May 01 17:02:15 joerg: yes, starts at line 545 May 01 17:04:45 CoreDump, hmm? May 01 17:04:49 you mean a cat? May 01 17:05:26 I wonder if that file is actually there. If it isn't due to a driver bug for expample, then the node would not be created May 01 17:05:45 root@collie:~$ cat /sys/block/mmcblk0/mmcblk0p1/dev May 01 17:05:45 254:1 May 01 17:06:45 but the system is up at this time May 01 17:06:59 booted into gpe on the sd card May 01 17:07:04 have to go and have dinner May 01 17:07:07 see you in a few minutes May 01 17:10:15 mickeyl: greetings May 01 17:11:29 hiho May 01 17:19:21 joerg: let me know what you can find out. I'll be reading the backlog May 01 17:47:24 I'm trying to get altboot working on my Zaurus (Akita), except after direct-install to the SD card completes, altboot complains that there's nothing there to boot from. Inspection of the SD card reveals that the installation is simply untarring zImage.bin, initrd.bin, and updater.sh, instead of actually creating a filesystem May 01 17:48:20 Any idea what's going on here and how to fix it? Angstrom isn't terribly usable if I'm limited to the internal flash memory. May 01 17:50:31 loderunner: zImage... and the other files doesn't contain info for altboot May 01 17:50:50 you must download a tar.gz with the system and place it on the sd May 01 17:51:13 where would those be? http://www.angstrom-distribution.org/releases/2007.12/images/akita/ May 01 17:51:44 heh not been a big vi user on zaurus .. whats the key sequence to save and exit ! is not implimented ;) May 01 17:51:55 cancel : q May 01 17:52:07 loderunner: i don't know if you can do it with installkit only May 01 17:52:13 i used other files May 01 17:52:42 so I'd have to install to the internal flash, then copy my filesystem to an SD card, then install altboot, then use the copied file system? May 01 17:52:57 mimecar, that jusr turned off ny device May 01 17:53:18 loderunner: have you check angstrom wiki? May 01 17:53:26 thoroughly May 01 17:53:46 Nothing really seems to mention it other than the manual May 01 17:54:56 but thanks for pointing me in the right direction, at least. Maybe there's some other tarball I can download which will contain the entire filesystem. I just haven't found it yet May 01 17:59:41 loderunner: enter on the old folder May 01 17:59:52 http://www.angstrom-distribution.org/releases/2007.12/images/akita/old/Angstrom-altboot-console-image-glibc-ipk-2007.12-akita.rootfs.tar.gz May 01 18:00:27 wtf, thought I looked there before May 01 18:00:33 rootfs, yeah May 01 18:00:36 thanks mime May 01 18:00:55 I need sound :) May 01 18:01:08 i need a ferrari May 01 18:01:23 lool May 01 18:02:57 do locale works on angstrom ? May 01 18:03:11 j0wn, did you make it work? May 01 18:05:18 ive got the right node now but still no go .. i tried to manually mount it .. says that its not a valid block device May 01 18:08:06 something ist right here ... i only have mmc_core module loaded May 01 18:10:47 ok i think ive found what i did wrong May 01 18:10:50 1 sec May 01 18:14:55 hi wirelessdreamer May 01 18:19:51 ok i got all the mods now ... still not booting off of it May 01 18:22:17 thanks again mimecar, all seems to be working except sound May 01 18:22:34 i hadn't tested sound May 01 18:22:48 other thinks works ok May 01 18:22:59 joerg, still not a valid block device May 01 18:22:59 included wifi May 01 18:24:00 my SD is a 1GB Lexar May 01 18:24:08 j0wn, do a cat /proc/partitons May 01 18:24:22 j0wn, do a cat /proc/partitions May 01 18:24:34 ok May 01 18:24:42 3 entries May 01 18:25:59 block sizes are 768 1024 and 14464 May 01 18:26:30 major minor #blocks name May 01 18:26:30 31 0 768 mtdblock0 May 01 18:26:30 31 1 1024 mtdblock1 May 01 18:26:30 31 2 14464 mtdblock2 May 01 18:26:30 254 0 1992704 mmcblk0 May 01 18:26:31 254 1 1991776 mmcblk0p1 May 01 18:26:36 should look like this May 01 18:26:55 i dont have the mmc entries May 01 18:27:23 hmm May 01 18:27:43 try to repartition and format the sd card in ext2 May 01 18:28:00 you are probably missing a module. May 01 18:28:03 or try another sd card May 01 18:28:30 cofeineSunshine, have you ever checked out a git repos? May 01 18:32:24 CoreDump|backup, btw. some news for you: I booted the collie without sd card and when I insert it the /sys/block/mtdblk0 things are created automatically. May 01 18:32:35 modules loaded are May 01 18:33:08 joerg: I would need to know where the /sys/blahh path exists at "init=/bin/sh" after insmodding the modules May 01 18:33:12 mmc_spi mmc_core mmc_block and locomo_spi May 01 18:33:17 s/where/whether May 01 18:33:21 all insmode properly May 01 18:33:32 cofeineSunshine, that's what I am talking about I suppose :P May 01 18:33:35 j0wn: anything interesting from dmesg? May 01 18:34:08 cofeineSunshine, I didn't insert the sd card and let altboot boot from sd May 01 18:34:24 it loaded the modules then gave me a shell as it couldn't mount anything. May 01 18:34:30 ah May 01 18:34:56 then I checked out if /sys/bla was there. May 01 18:34:59 of course not. May 01 18:35:10 then I inserted the sd card and checked out again. May 01 18:35:14 and well....there it was. May 01 18:35:17 no nothing during loading of mmc modules May 01 18:36:21 joerg: could still be a driver problem. We need to know if the file is there when you boot with inserted SD card May 01 18:36:56 it does'nt look like its detecting the sd card at all tbh May 01 18:37:03 and the content of the file would be interesting as well May 01 18:37:37 how do you pipe on a z? May 01 18:38:08 hmm? May 01 18:38:30 create | May 01 18:38:51 * CoreDump|backup dunnos as he is lacking a Collie May 01 18:39:17 hehe May 01 18:39:27 joerg, any idea? May 01 18:41:59 god I hate burning DVDs May 01 18:46:14 j0wn, no... May 01 18:46:48 not yet May 01 18:50:45 joerg: could you apply http://rafb.net/p/aNMsaU32.html and see if it creates the nodes correctly w/o the device_table entries? May 01 18:51:23 * CoreDump will bbl May 01 18:53:19 if it does (and it works) I'll need an "ls -al" of the node May 01 18:54:57 CoreDump, I will try it out. May 01 18:55:10 right now I simply booted with init=/bin/sh May 01 18:55:27 Im gunna try an older sd card 128MB i have here May 01 18:55:28 via the altboot menu (no. 6) May 01 18:55:44 j0wn, yes, maybe that works. May 01 18:56:02 CoreDump, then I did the essential modeprobes May 01 18:56:13 and the /sys/blah is there! May 01 18:56:15 that would point to a driver issue for sure May 01 18:56:52 joerg: good, what's its content? May 01 18:57:05 254:1 of course May 01 18:59:15 then I don't see how mount_sd could fail May 01 18:59:47 what does "uname -r" say? May 01 19:00:17 ok that card mounted media/card ... seems that my 1gb card isnt supported by the mmc driver May 01 19:02:35 hmm... May 01 19:02:53 I am using a 2gb extrememory card May 01 19:03:05 on collie? May 01 19:03:06 cofeineSunshine, bad news.... May 01 19:03:12 sry May 01 19:03:26 CoreDump, bad news :) I commented the if statement out.... May 01 19:03:33 well....and it doesn't work.... May 01 19:03:41 "no such file or directory" May 01 19:03:53 it probably needs some time. May 01 19:04:35 ahh May 01 19:05:35 your script simply checks the /sys/bla file before it is created May 01 19:05:48 it is definetely there May 01 19:06:05 try http://hentges.net/tmp/altboot.func please and enable debugging May 01 19:06:05 the mknod thing failed and the scripted died May 01 19:07:19 it will run into the failsafe thing. May 01 19:08:03 I'm waiting 3 seconds after loading the modules now. If it is a timing problem, this should fix it May 01 19:08:20 ah, ok May 01 19:08:22 wait May 01 19:08:48 I have to transfer it by CF card May 01 19:16:45 CoreDump, CF doesn't work. May 01 19:17:06 heh May 01 19:17:22 well, gotta go now. cya later May 01 19:18:05 cya May 01 19:25:29 j0wn, how's it going? May 01 19:30:03 Does anyone know if there's a way to get a rootfs from a .bin installkit image? May 01 19:30:23 yes May 01 19:30:28 simple download the tar.gz :) May 01 19:30:55 There isn't an r13 version available May 01 19:31:01 Only an older version May 01 19:31:09 And in the older version, both sound and networking is broken May 01 19:31:20 which arch? May 01 19:31:26 http://www.angstrom-distribution.org/releases/2007.12/images/akita/ May 01 19:31:50 C1000 / Akita May 01 19:32:32 http://www.angstrom-distribution.org/unstable/autobuild/akita/ May 01 19:32:39 what about that one? :P May 01 19:33:27 if you don't have any success....let me know May 01 19:33:44 then I will tell you how to mount the initrd.bin image and rip the files to a tar.gz May 01 19:33:46 Either I am a moron, or whomever is in charge of the Angstrom FTP is a moron. Or perhaps a mixture of the two May 01 19:34:05 I will try that, thanks May 01 19:35:37 perhaps I will do some editting of the wiki after this is done. May 01 19:36:12 because there isn't a single damned link to that folder anywhere that I saw May 01 19:45:09 strange May 01 19:45:22 CoreDump, it WAS a timing problem....your new script works. May 01 19:50:17 joerg, im getting no boot-images found in /media/card/boot-images May 01 19:51:01 its the dropping to rootfs configuration May 01 19:51:12 *then May 01 19:52:14 right May 01 19:52:57 either untar a rootfs direcetly to the card's root May 01 19:53:25 or put it in /boot-images/ May 01 19:54:50 which one did you use? May 01 19:59:34 x11-image May 01 20:00:06 http://www.angstrom-distribution.org/unstable/autobuild/collie/x11-image-collie.tar.gz May 01 20:06:22 do I have to rename it at all? May 01 20:08:16 j0wn, if you want to put it in boot-images yes May 01 20:08:31 well its not working from the SD May 01 20:09:25 ive untar'd it to the SD but its not reading / doin it May 01 20:10:05 hmm? May 01 20:10:37 did you format the card ext2 ? May 01 20:11:47 yes May 01 20:11:53 mkfs.ext2 May 01 20:12:29 1 sec May 01 20:19:28 nope still no go May 01 20:19:45 but it mounts the card? May 01 20:19:53 yeah /media/card May 01 20:20:58 there's still a 2GB limit on the SD slot of the collie? I dont remember if it was a drier issue or hadware somehow May 01 20:21:05 driver May 01 20:21:42 im using a 128mb card ... my lexar 1gb is a no show on the device May 01 20:23:11 is collie pxa255 or 270? May 01 20:24:16 pxa270 supports sdhc with recent enough drivers, so >1gb is definately not a hw problem...dunno about pxa255 May 01 20:24:39 oh, it's the real stuff.. sa1110 :) May 01 20:24:57 sa as in StrongArm :) May 01 20:25:38 Sketch, I use a 2gb sd card on collie without any problems.... May 01 20:25:51 I also used a 2GB card on mine May 01 20:26:01 with 2.6? May 01 20:26:07 no May 01 20:27:22 hmm May 01 20:27:30 so you used the hack? May 01 20:27:59 i've used a 4gb (regular) sd on my 3100 May 01 20:28:56 the hack.. no, this was in the old days of openzaurus :) May 01 20:28:58 well the 5500's sharp 2.4 sd driver doesn't support 2gb May 01 20:29:19 ok.. then I probably did use a hack May 01 20:29:31 sharp's driver has never suppoted >1gb until the 3200 was released May 01 20:29:40 I realy dont remember.. my zaurus has been "resting" for a year at least May 01 20:29:49 http://cambuca.ldhs.cetuc.puc-rio.br/~miguel/zaurus/ May 01 20:30:09 (which is long after it was no longer a hardware limitation) May 01 20:30:46 anyway May 01 20:31:08 as the new 2.6 doesn't use the sharp drivers it should work "out of the box" everywhere :) May 01 20:36:15 did anybody ever build a custom kernel? May 01 20:37:51 I produced a "zImage" with make zImage but I am not able to flash it. May 01 20:55:37 joerg, zaurus flash scripts only take specific filenames May 01 20:55:48 in case of akita for zImage that is zImage.bin May 01 20:56:14 in case of collie it is zImage :P May 01 20:56:38 are you using the right updater? May 01 20:56:46 also updater filename May 01 20:57:01 updater? May 01 20:57:16 I put zImage on a vfat formatted CF card May 01 20:58:27 looks like I have no idea about collie flashing :) May 01 21:01:57 hehe May 01 21:02:12 dcordes, I am not talking about flashing. May 01 21:02:18 but about building a kernel image. May 01 21:02:52 "I am not able to flash it." ? May 01 21:06:27 unless collie is significantly different from the clamshells, if you are using the sharp bootloader you have to flash the kernel onto the onboard flash May 01 21:08:03 ok... May 01 21:11:19 Sketch, yes, but do I have to prepare it somehow? May 01 21:11:41 Sketch, I built a kernel.... with "make zImage" May 01 21:12:06 then I did a "cp arch/arm/boot/zImage /media/card" May 01 21:12:13 and then flashing fails. May 01 21:12:53 on the clamshells you need the updater script I mentioned above. updater.sh in case of akita May 01 21:14:40 hmm May 01 21:14:49 joerg, I just fetched http://www.angstrom-distribution.org/unstable/autobuild/collie/Angstrom-altboot-console-image-glibc-ipk-2007.12-r7-collie-installkit.tgz to see how that is done on collie. obviously you need no script and filenames are initrd.bin for initial ramdisk and zImage.bin for the kernel image May 01 21:15:33 no zImage and initrd.bin May 01 21:15:47 ok sorry can't help further. May 01 21:18:37 well May 01 21:18:51 I just wonder how the zaurus should know the rootdev etc. May 01 21:18:52 im not sure as to what happend after OZ but installing Angstrom has become troublesom May 01 21:22:22 the question is which of both should you blame more: OZ oder angstrom? May 01 21:23:42 heh May 01 21:25:19 I dont blame either tbh ... just wondering why collie seems so broken these days May 01 21:26:18 maybe its mentor is not so interested in having it working May 01 21:27:18 is that cryptic or what May 01 21:33:46 and what to say about h3900 :) May 01 21:35:03 joerg, just re-did the SD card still not finding the boot image ... why is it trying to find it in /media/card/boot-image May 01 21:35:18 its ignoring everything else on the SD May 01 21:35:38 read the altboot manual May 01 21:48:02 ok im installing through alt adv menu May 01 21:48:06 heh May 01 21:48:34 looks like this could work May 01 21:50:31 nope same result May 01 21:51:08 mounts the sd card to /media/card then dies May 01 21:51:34 altboot? maybe poke CoreDump May 01 21:54:43 hmm May 01 21:54:52 the kernel mustn't be bigger than 1 MB May 01 21:54:58 that was the problem -probably May 01 21:56:27 j0wn: if it doesn't try to b00t of an extracted filesystem, then you are missing /media/card/sbin/init May 01 21:57:04 joerg: excellent, thanks for testing May 01 21:59:13 * * mhentges has commited r82 into the altboot repository: May 01 21:59:13 * * Fix a timing problem in sd_mount as seen on collie May 01 22:16:22 CoreDump, btw. did you ever compile a kernel for collie? May 01 22:16:59 probably hundreds, yeah. But not in the past year or so ;) May 01 22:22:16 a 2.6 as well? May 01 22:30:17 hmm, don't think so May 01 22:36:03 I've started an image build for collie. Let's see how far it goes May 01 22:42:49