**** BEGIN LOGGING AT Wed Dec 12 02:59:57 2007
Dec 12 04:02:37 <summatusmentis> dcordes_: no, it won't even try.... it just boots into opie, and won't go through the flashing process
Dec 12 04:03:19 <CoreDump> well, you didn't trigger the update then
Dec 12 04:03:55 <CoreDump> what was it again? C+D+Reset or something like that
Dec 12 04:05:47 <summatusmentis> yeah, exactly
Dec 12 04:06:04 <summatusmentis> CoreDump: I was following your flashing instructions ;-)
Dec 12 04:06:17 <CoreDump> heh
Dec 12 04:06:22 <CoreDump> well, AC is plugged in?
Dec 12 04:06:25 <summatusmentis> yes
Dec 12 04:06:41 <summatusmentis> I think the issue is, the current OS on there doesn't know when the batter door is unlocked
Dec 12 04:07:06 <CoreDump> the OS has nothing to do with the flashing process
Dec 12 04:07:21 <CoreDump> it's a bootloader thing
Dec 12 04:07:59 <summatusmentis> I don't know, it wasn't recognizing the fact that the battery door was unlocked
Dec 12 04:08:28 <CoreDump> kernel problem or defective battery switch are my guesses
Dec 12 04:12:56 <CoreDump> http://openzaurus.berlios.de/Collie/Install
Dec 12 04:24:11 <JJ_Reimer> !logs
Dec 12 04:24:11 <cdbot2> Channel logs for #angstrom are archived at:
Dec 12 04:24:12 <cdbot2> http://hentges.net/tmp/logs/irc/%23angstrom
Dec 12 04:24:13 <cdbot2> Live-logs are available at
Dec 12 04:24:14 <cdbot2> http://hentges.net/tmp/logs/irc/livelogs/%23angstrom.livelog
Dec 12 04:24:16 <cdbot2> See ?? help-logs for usage instructions
Dec 12 05:11:55 <CoreDump> now that was a dist-upgrade from hell
Dec 12 09:26:34 <ant|work771> good morning
Dec 12 14:36:42 <ffc> Does anyone know what RTPROT_MIP is?
Dec 12 14:38:59 <koen> heh, googling for that  yields a file that's called Fix-kernel-header-check.patch
Dec 12 14:40:18 <koen> ffc: try applying http://redhat.lcs.mit.edu/pub/usagi/usagi/patch/mipv6/umip-0.4/daemon/patch/all-in-one/mipv6-daemon-umip-0.4.diff to umap 0.4
Dec 12 14:43:20 <ffc> yes, I've seen it
Dec 12 14:43:35 <ffc> it seems that RPROT_MIP is not supported or something
Dec 12 14:45:54 <Sketch> hmm
Dec 12 14:46:21 <Sketch> ipkg fails to fork wget when i try to ipkg update/ and won't install a local ipkg either
Dec 12 14:46:59 <Sketch> rebooting does not fix it...
Dec 12 14:47:07 <Sketch> any ideas?
Dec 12 14:48:55 <koen> not without error messages
Dec 12 14:49:02 <koen> my crystal ball is in repairs
Dec 12 14:53:59 <ffc> koen: apply .diff in WORK directory?
Dec 12 15:02:40 <koen> ffc: in SRC_URI would be the usual place
Dec 12 15:03:19 <Sketch> when i try to install a local package, i get:
Dec 12 15:03:21 <Sketch> ipkg: fork failed
Dec 12 15:03:26 <Sketch> Segmentation fault
Dec 12 15:03:40 <Sketch> when i try to do an an ipkg update it's fork: failed to exec wget <options> ...
Dec 12 15:03:46 <Sketch> i don't have problems running anything else, just ipkg it seems
Dec 12 15:04:37 <Sketch> just figured i'd ask if there are any known common causes before i just give up and reinstall ;)
Dec 12 15:04:42 <CoreDump> Sketch: rm /var/lib/ipkg/* and try to install a local package
Dec 12 15:06:19 <Sketch> same thing
Dec 12 15:06:36 <CoreDump> time to reinstall =)
Dec 12 15:06:49 <Sketch> indeed ;)
Dec 12 15:06:55 <Sketch> i was going to try a newer image anyway ;)
Dec 12 15:07:23 <Sketch> hmm, actually, i just straced it, last thing before it fails is cannot allocate memory
Dec 12 15:07:53 <Sketch> i have 27mb free (-cache), 15mb free physical...
Dec 12 15:08:07 <Sketch> seems like it ought to be sufficient...
Dec 12 15:08:22 <CoreDump> It sounded like going OOM yes
Dec 12 15:08:46 <CoreDump> usually that is due to overly large feed lists 
Dec 12 15:08:58 <CoreDump> (hence the rm /v/l/i/*)
Dec 12 16:43:47 <summatusmentis> CoreDump: ping
Dec 12 16:43:59 <summatusmentis> ~collie
Dec 12 16:48:08 <summatusmentis> ok, if I understand this correctly, there is a 16MB flash space on the collie, which is where the kernel is stored. Then we have 64 MB of storage, in which we can put rootfs, correct?
Dec 12 16:48:43 <summatusmentis> however, if we do that, there is no ram available
Dec 12 16:52:28 <CoreDump> no
Dec 12 16:52:37 <summatusmentis> no?
Dec 12 16:52:52 <CoreDump> we have ~1Mb for kernel, ~15Mb for rootfs, and 64MB of RAM
Dec 12 16:53:21 <CoreDump> you can create RAM disks by selecting a proper kernel
Dec 12 16:53:24 <summatusmentis> and how much for rootfs on the poodle?
Dec 12 16:53:34 <CoreDump> ugh
Dec 12 16:53:48 <CoreDump> around 20Mb IIRC but I'm not sure
Dec 12 16:54:03 <CoreDump> also, Poodle has a /home partition
Dec 12 16:54:35 <summatusmentis> so, unless the X11 image gets substantially shrunk down, rootfs on external media is really the only way X11 is doable
Dec 12 16:54:51 <CoreDump> probably, yes
Dec 12 16:55:24 <summatusmentis> alright, so as a tester, I should be working on testing console image
Dec 12 16:55:44 <summatusmentis> because X11 is too big
Dec 12 16:55:55 <CoreDump> or go for root-on-sd
Dec 12 16:58:07 <summatusmentis> using altboot? or something like kexec?
Dec 12 16:58:40 <CoreDump> a kernel with built-in sd driver and modified CMDLINE
Dec 12 16:59:49 <summatusmentis> ok, thanks. it's been so long since I've worked with collie
Dec 12 17:27:04 <ffc> koen: I put the patch you gave me on the mipv6_2.0.2.bb file (in SRCURI)
Dec 12 17:27:14 <ffc> but when I try to bitbake mipv6
Dec 12 17:27:26 <koen> it's for umip, not mipl
Dec 12 17:27:33 <ffc> there are error applying the patch
Dec 12 17:28:04 <ffc> oh.. well, I've said nothing then :-(
Dec 12 17:28:30 <summatusmentis> koen: is there a timeframe that Angstrom is trying to release within?
Dec 12 17:28:45 <koen> the plan is "before xmas 2007"
Dec 12 17:29:21 <summatusmentis> lol, ok, so < 2 weeks... it's unlikely then that collie will be supported by that time?
Dec 12 17:29:34 <koen> that's up to the machine mentors
Dec 12 17:29:42 <koen> if they sign of on it...
Dec 12 17:29:44 <summatusmentis> of which there are none
Dec 12 17:32:18 <ffc> is umip on Angstrom's packages list?
Dec 12 17:32:24 <koen> not yet
Dec 12 17:32:32 <koen> I just learned about it yesterday :)
Dec 12 17:32:37 <ffc> :-P
Dec 12 18:43:29 <mimecar> hi
Dec 12 18:45:52 <barnarda> hello
Dec 12 18:46:13 <mimecar> hi barnarda
Dec 12 19:36:04 <mimecar> hi guys
Dec 12 20:09:48 <scops> hello there. i have just a question to angstrom on a collie... : the x11 images are 20mb big...  how can i use them?
Dec 12 20:10:05 <mimecar> you can't
Dec 12 20:10:26 <mimecar> only minimal image fits on collie actually (at least 2 weeks ago)
Dec 12 20:11:07 <scops> hmmm ok... and i must install the x11 as rootfs?
Dec 12 20:11:07 <koen> minimal, console and minimal-gpe are all smaller than 14MB
Dec 12 20:11:09 <scops> on sd?
Dec 12 20:11:35 <mimecar> minimal image fits on flash memory
Dec 12 20:11:48 <mimecar> if you want use X11, you must use the system on the sd
Dec 12 20:11:57 <koen> mimecar: nonsense
Dec 12 20:12:00 <mimecar> i don't know if sd works
Dec 12 20:12:13 <koen> [21:11] koen: minimal, console and minimal-gpe are all smaller than 14MB
Dec 12 20:12:38 <scops> can i flash minimal-gpe and install apps on sd?
Dec 12 20:13:08 <scops> (cardfs dont work right on oz i think... does it work right on angstrom?!)
Dec 12 20:13:11 <koen> if you want to install apps on sd you must use root on sd
Dec 12 20:13:40 <koen> so you want to flash altboot-console-image and put x11-image on sd
Dec 12 20:13:46 <mimecar> koen: is the collie kernel patched with sd driver ?
Dec 12 20:13:57 <koen> mimecar: yes it is
Dec 12 20:14:42 <barnarda> That's why I love angstrom. I can use my 2GB SD card, unlike sharp rom :P
Dec 12 20:15:02 <koen> later all
Dec 12 20:15:02 <mimecar> barnarda: it worked on openzaurus also 
Dec 12 20:15:49 <scops> yes... and on my collie gpe/oz works nicely... only die filemanger dont work right here (some libproblem...)
Dec 12 20:15:53 <barnarda> OZ switched to angstrom, so I like to stay current ;)
Dec 12 20:16:13 <scops> i want it too... do you use a collie barnarda ?
Dec 12 20:16:26 <barnarda> I use poodle, actually
Dec 12 20:17:10 <scops> ok... so you cant give me a step by step guide for a collie? ;) (with altboot... i tryed it but it dont worked with the image of 11.dec...
Dec 12 20:17:13 <scops> )
Dec 12 20:17:28 <mimecar> check frist sd 
Dec 12 20:17:40 <mimecar> scops: what was the image you tested ?
Dec 12 20:17:43 <scops> (i couldnt install the rootfs on sd... dont worked... on oz i use it in this config)
Dec 12 20:17:52 <scops> i used the altboot console image
Dec 12 20:18:11 <mimecar> then, you haven't angstrom on flash ?
Dec 12 20:18:23 <barnarda> Haven't gotten around to testing altboot, yet, so not sure how to help ya. Sorry :)
Dec 12 20:18:42 <scops> i have it on flash... as console/altboot, mimecar 
Dec 12 20:18:55 <scops> ehm... had ;) at the moment i switched back to oz
Dec 12 20:18:59 <mimecar> ok, i've an image to test
Dec 12 20:19:03 <mimecar> but i hadn't time
Dec 12 20:20:25 <scops> i will wait till a proper release.... i think... till then i will stay with oz/altboot... 
Dec 12 20:20:56 <scops> any netbook pro users here?
Dec 12 20:20:57 <scops> :)
Dec 12 20:22:14 <scops> ok i must go... thanks... cya :)
Dec 12 20:22:31 <mimecar> byes...
Dec 12 20:22:39 <barnarda> take care
Dec 12 20:25:38 <mimecar> hi summatusmentis
Dec 12 20:30:41 <mimecar> bye...
Dec 12 20:31:56 <dcordes> barnarda, afaik you can even use SDHC, can't you?
Dec 12 20:32:09 * dcordes thought about getting an 8gb one for testing purpose
Dec 12 20:33:13 <barnarda> Not that I'm aware of. As it is, it appears to be running as mmc
Dec 12 20:36:43 <barnarda> I guess that's normal? (My 1GB appears the same.)
Dec 12 20:41:52 <dcordes> barnarda, http://www.oesf.org/forum/index.php?showtopic=23959&hl=sdhc see #14 
Dec 12 20:42:14 <dcordes> it's a cacko person but obviously Z is sdhc capable hardware wise
Dec 12 20:42:42 * barnarda drools. :)
Dec 12 20:42:55 <dcordes> 16gb dude
Dec 12 20:43:27 <dcordes> I want one badly!
Dec 12 20:46:45 <dcordes> I will just order one and make it work if it doesn't
Dec 12 20:47:38 <dcordes> whoops 100 euros
Dec 12 20:48:22 <barnarda> hehe
Dec 12 20:49:57 <dcordes> somebody with huge sd card/zaurus present?
Dec 12 20:54:10 <summatusmentis> huge != 1GB
Dec 12 21:18:13 <hvontres|work> dcordes: except that the card in question was a 16GB CF card :)
Dec 12 21:20:22 <dcordes> haha thanks hvontres|work 
Dec 12 21:26:00 <hvontres|work> barnada: have you tried any of the new poodle images yet?
Dec 12 21:27:43 <hvontres|work> barnarda: I'd be interested in feedback on my new altboot menu in 
Dec 12 21:28:08 <hvontres|work> barnarda: 
Dec 12 21:28:24 <barnarda> Checking it out as we speak, prepping my SD card ;)
Dec 12 21:30:24 <dcordes> hvontres|work, at the weekend I will reflesh akita. Will tell you what I think then. Do you have a changelog or something?
Dec 12 21:31:26 <hvontres|work> dcordes: unfortunately I only have a version for poodle so far... still very experimental. The biggest change was adding a curses front end to pick items.
Dec 12 21:32:52 <hvontres|work> barnarda: check out the images at http://www.angstrom-distribution.org/unstable/unsupported-images/poodle/20071130/
Dec 12 21:32:53 <dcordes> cool. I'm happy that it works at all since XorA|pissedoff and others made it recognize the sd cards again in 2.6.22 or was it 23
Dec 12 21:36:54 * hvontres|work wonders what pissed off XorA|pissedoff 
Dec 12 21:37:05 <XorA|pissedoff> hvontres|work: got burgled
Dec 12 21:37:26 <hvontres|work> XorA|pissedoff: bugger...
Dec 12 21:37:40 <XorA|pissedoff> hvontres|work: no great loss, just a pain in the ass
Dec 12 21:39:26 <dcordes> XorA|pissedoff, they broke your house?
Dec 12 21:39:44 <XorA|pissedoff> dcordes: door broken, tv missing, no great issues, Im insured
Dec 12 21:40:07 <dcordes> bah those bitches
Dec 12 21:40:19 <hvontres|work> XorA|pissedoff: At least they didn't get the Legos :)
Dec 12 21:40:34 <XorA|pissedoff> hvontres|work: yeah then all hell would have descended on scotland
Dec 12 21:40:37 <dcordes> haha just wanted to ask if the zauri were save
Dec 12 21:40:50 * dcordes ducks
Dec 12 21:41:06 <dcordes> were you at thome while they broke?
Dec 12 21:41:47 <dcordes> a friend of mine got burgled while he was asleep. they searched whole flat
Dec 12 21:46:47 <XorA|pissedoff> dcordes: no, no-one home
Dec 12 21:47:06 <barnarda> hvontres? Just want to check, I rename the whole Angstrom-* image to rootfs.tar.gz and it should be able to install from the altboot menu, right?
Dec 12 21:47:29 <barnarda> my archive manager is hiccuping at the root part
Dec 12 21:52:26 <hvontres|work> barnarda: do you have a card reader? I have been untaring the rootfs on my pc so far. Havent tried installing from the menu....
Dec 12 21:53:22 <barnarda> hehe, okay :) Will go the old CLI route
Dec 12 22:04:43 <dcordes> does somebody what happened to the scripts that made wifi reconnect on clamshell wakeup?
Dec 12 22:48:37 <DaedalusX> heyas
Dec 12 22:55:27 <barnarda> Hello DaedalusX, sorry, was nose down in testing
Dec 12 22:55:40 <DaedalusX> no worries
Dec 12 22:55:44 <DaedalusX> barnarda, what's up?
Dec 12 22:57:06 <barnarda> Poodle circus :)
Dec 12 22:57:39 <ajehuk> Hi folks, quick question, I have a hx4700 that I promarily use with familiar (flashed to the device) but have been playing with Gentoo (booting from CF) and waned to give booting Angstrom from the CF a try, now I can do it if I use the gentoo zImage but not with any of the Angstrom zImages (using those available in the "autobuild" section atm) the error I see is VFS: Cannot open root device "hda2" or unknown-block (2,0).
Dec 12 22:58:09 <ajehuk> any advice, I may have been a little opaque in phrasing that question...
Dec 12 23:02:57 <barnarda> Not familiar with that device, but you said you're using the zImage? (just the zImage?)
Dec 12 23:04:58 <barnarda> There's a 'startup.txt' that might be able to help there. Sounds like the rootfs needs to be extracted to the 2nd partition (ext2) of the CF card
Dec 12 23:07:40 <ajehuk> Yeah, sorry I was unclear, Im using the zImage plus a params file in /boot on hda1 with Angstrom image extracted to the second partiion (and refrenced in the params file) its basically the same setup I used for booting gentoo,I assume (big mistake potentially) the params file is being read as the root delay specified is being honoured and it is 'trying' to find the specified root filesystem as specified.
Dec 12 23:08:57 <ajehuk> Ignore the I assume part, I meant to say I assume that the set up I am using should work for Gentoo/Familiar/Angstrom etc.. <-- although thats a big assumption to make..
Dec 12 23:09:33 <barnarda> I would backup the gentoo stuff, repartion the card with a FAT partition with the MaRET executable, the zImage, and the startup.txt file from the directory. Add a 2nd partition of ext2 with the rootfs tarball extracted to it
Dec 12 23:09:34 <ajehuk> it does work for Gentoo/Familiar, and partially for Angstrom, just not if I use the zImage provided...
Dec 12 23:10:08 <barnarda> might be able to copy the settings from the startup.txt to the param file
Dec 12 23:10:29 <ajehuk> (just looking up MaRET)
Dec 12 23:11:02 <barnarda> Its a Linux bootloader for WinCE (http://handhelds.org/wiki/MaRET)
Dec 12 23:11:18 <ajehuk> I dont have Wince on the device...
Dec 12 23:11:40 <barnarda> sorry, was reading from the startup.txt :) not sure what all is in the parm file for familiar
Dec 12 23:12:18 <barnarda> Try using the cmdline from the startup.txt in place of the param file
Dec 12 23:18:54 <ajehuk> looking at the startup.txt in the ftp directory where I got the Angstrom files from the only difference is linuxargs (in the param file) becomes cmdline, and that doesnt work, (it boots into familiar on the flash and dosnt see any of the alternative boot options) so I assume my params file syntax was correct...
Dec 12 23:20:09 <ajehuk> am I right in saying that the boot process is something like sdg>zImage>$distribution? because that would suggest that the zImage is used properly and either doesnt have ext2 support... or uses a different device naming scheme for CF cards (as opposed to hda2)
Dec 12 23:20:29 <barnarda> Do you just have the one partition on the CF card?
Dec 12 23:21:15 <ajehuk> No, 2, 1 FAT boot partition used by the SDG bootloader and one EXT2 partion with the OS image extracted to it (fsck'd and fine).
Dec 12 23:21:49 <ajehuk> i.e. the first partition contains the zimage and the params file with boot options. (not the sdg bootloader itself)
Dec 12 23:22:39 * barnarda hrms. "what are the boot options?"
Dec 12 23:22:58 <ajehuk> Im using set linuxargs root=/dev/hda2 rw console=tty0
Dec 12 23:23:05 <ajehuk> rootdelay=5
Dec 12 23:23:35 <ajehuk> (and just tried with: set cmdline "root=/dev/hda2 rootdelay=10 console=ttyS0,115200n8 console=tty0" )
Dec 12 23:24:18 <ajehuk> changing linuxargs to cmdline causes the boot options to be ignored (the flash is booted) 
Dec 12 23:25:25 <hvontres|work> ajehuk: what kernel are you running? I had issues with 2.6.23 and rootdelay. you might want to try rootwait instead
Dec 12 23:25:44 <ajehuk> 2.6.21
Dec 12 23:26:06 <ajehuk> hvontres ^^ it is waiting....
Dec 12 23:26:56 <hvontres|work> ajehuk: hmm, not sure then... unless that kernel has pcmcia support compiled as a module...
Dec 12 23:26:58 <ajehuk> and it boots with a gentoo 2.6.21-hh12 kernel, just not the Angstrom 2.6.21hh19
Dec 12 23:27:14 <ajehuk> causing the obvious module hilarity obviously.
Dec 12 23:28:17 * ajehuk tries rootwait anyway....
Dec 12 23:31:53 <hvontres|work> ajehuk: actually, I think that option only exists in 2.6.23+
Dec 12 23:31:55 <ajehuk> interestingly the rootwait option is ignored.... but same problem, the root device is wrong or not findable...
Dec 12 23:32:09 <ajehuk> hvontres|work - yeah its ignored with this kernel.
Dec 12 23:33:15 <hvontres|work> ajehuk: you might want to take a look at the defconfig file for the angstrom kernel to see what was built as a module....
Dec 12 23:36:37 <ajehuk> hvontres|work - where would I find it if its an autobuild image I am using? there's no source in the image and no defconfig file in the ../kernel/arch/arm.. directory (although I dont think there should be...) 
Dec 12 23:40:40 <ajehuk> Actually if I can get a defconfig fro both the gentoo and angstrom kernels then I might be closer to solving this... (or maybe I shouldnt try and multiboot my ipaq at all, I have forgotten why I wanted too already (other than its interesting of course))
Dec 12 23:46:00 <hvontres|work> ajehuk: http://www.openembedded.org/repo/org.openembedded.dev/packages/linux/linux-handhelds-2.6/hx4700/defconfig
Dec 12 23:47:45 <ajehuk> cheers hvontres|work
Dec 13 00:11:02 <ajehuk> re the defconfig It looks like the configuration used is the same in all important aspects, or at least as far as I can tell (some changes but in networking,irda etcc not used at this stage of the boot process... is it likley that the way I should be refering to the second partition of the CF is different at this stage? Im using /dev/hda2... (also tried refering to the label but that doesnt seem to work either...). I'm g
Dec 13 00:11:04 <ajehuk> zimage and params on the CF card and the image extracted to /dev/mmcblk0p1.  If anyone can think of anything else I'd be grateful (I'd rather use the SD card as removable media...
Dec 13 00:11:10 <ajehuk> )
Dec 13 00:28:32 <ajehuk> OK so I cant boot to CF or SD using the Angstrom zImage in conjunction with a params file when they are sat in /boot on the first partition of a CF card.  The params file is read and the zImage loaded but I always get the error, VFS: cannot open root device "mmcblk0p1" [or "hda2" for CF] or unknown-block(254,1) [or (0,2) for CF].
Dec 13 00:28:40 <ajehuk> I can boot to Angstrom if I do the whole thing in flash.  I can boot to Gentoo and Familiar on an external CF card using the method I detailed earlier... the CF card and SD card appear to be detected (judging by stdout).  Should there be somthing in addition to the zImage and params in /boot? 
Dec 13 00:28:49 <ajehuk> I really cant quite figure out what is happening here, I am assuming that the SDG botloader loads the zImage and that should find and continue to boot the image on the CF or SD card (it boots the flash if the params file doesnt tell it where root is).  So is it the naming of the devices? any further suggestions?
Dec 13 01:45:44 <ajehuk> OK I'm giving up trying to boot angstrom from the CF, is there any way to utilise the CF space for applications? (the goal being to have a little more space for applications than is available in internal flash..)
**** ENDING LOGGING AT Thu Dec 13 02:59:56 2007