**** BEGIN LOGGING AT Mon Oct 05 02:59:57 2009 Oct 05 08:19:54 Are there stable images for collie? I haven't managed to boot anything useful this far. I've built almost every target with OE, and tried the unstable images available on the web, but none seem to work... Oct 05 08:20:08 They boot up to some point and then just freeze Oct 05 11:59:37 I have a funny question about OABI system call and gcc4. Is there, it seems, a project angstrom legacy for this kind of implementation. Any help will be appreciated Oct 05 12:23:45 I am running angstrom with uclibc on avr32. I am able to build and usea a console-image build Oct 05 12:24:13 there is a problem where on boot, I get: logger: can't load library 'libintl.so' \ grep: /proc/filesystems: No such file or directory Oct 05 12:24:25 the proc filesystem is not built Oct 05 12:24:44 the file libintl.so is not on the target rfs but is in the staging area Oct 05 12:25:24 if I copy it on by hand, some things are resolved but other things break so I probably need a lot more than that one file. What am I missing and how do I add it so that the target will Oct 05 12:25:33 properly create a /proc on boot? Oct 05 12:25:35 Thanks. Oct 05 12:27:04 * XorA has tried avr32 build for a while Oct 05 12:27:50 I could not get avr32 to build for the longest time but recently, it builds just fine Oct 05 12:27:59 I have most of python happily running on it Oct 05 12:28:19 nice Oct 05 12:28:30 I need to get my atngw100 our for a play sometime soon Oct 05 12:28:33 I am trying to get pylons running on it but it segfaults during the install from easy_install Oct 05 12:28:41 there is some sort of memory leak Oct 05 12:29:21 i think that it may partly be due to the system not being entirely correct, i.e. missing /proc and who knows what else Oct 05 12:30:07 is there a recipe/task that deals with /proc creation? Oct 05 12:31:13 it should be mounted from a script in /etc/init.d/* somewhere Oct 05 12:31:19 or fstab Oct 05 12:31:23 I cant remeber offhand Oct 05 12:32:29 yeah Oct 05 12:32:31 it is in the fstab Oct 05 12:32:55 but when OE builds the image, it is not capable of doing whatever it needs to do Oct 05 12:33:10 I guess mount -a failed for some reason Oct 05 12:33:17 yeah Oct 05 12:33:24 it is looking for libintl.a Oct 05 12:33:28 i mean libintl.so Oct 05 12:33:44 which is built in staging but not in the final image Oct 05 12:34:24 you could revert to busybox mount Oct 05 12:34:36 as busybox is obviously working as you can boot at all Oct 05 12:35:33 I think for historic reasons we still use util-linux-mount Oct 05 12:37:35 ok Oct 05 12:37:42 i will try that Oct 05 12:38:22 because issuing the command "mount proc -t /proc" or whatever fails also with the same message about not finding "libintl.so" Oct 05 12:44:18 California is ridiculous .... Oct 05 12:47:27 your face..... Oct 05 12:47:29 :-D Oct 05 13:02:40 heh Oct 05 13:03:01 ok going for food and coffee Oct 05 13:35:16 Does the kexecboot image play any part after the rootfs has been mounted? Oct 05 13:35:27 On a collie, that is... Oct 05 13:36:02 no Oct 05 13:38:32 That makes me wonder why the images, that the online builder claims to be stable, boot only halfways the userland Oct 05 13:38:54 from SD? Oct 05 13:38:58 Yes Oct 05 13:39:07 because the SD driver falls over Oct 05 13:39:40 Should it work with cf? Oct 05 13:39:55 it should but last time I tried, CF driver hard oopsed Oct 05 13:40:10 Well darn... Oct 05 13:40:34 thesing is worling on 2.6.31 kernels Oct 05 13:45:26 Then how about making the rootfs small enough to fit in the internal memory? Oct 05 13:55:55 console-image does Oct 05 13:56:09 otherwise someone needs to spend time squeezing the image Oct 05 13:56:33 I keep meaning to, never get round to it and my more powerful devices get precedence Oct 05 14:06:08 the online builder gives out a .tar.bz2. Do I've to create a image with a fs and extract it there? Oct 05 14:06:25 in order to flash it to the internal memory? Oct 05 14:08:34 Hmm... Or can I somehow easily modify a userland on a SD to use an older kernel with a stable SD support? Oct 05 14:09:28 older images were 2.4 kernel based Oct 05 14:09:36 makes it pain Oct 05 14:11:59 But I've an oe enviroinment set up already.. Can't I somehow inform it to build with an earlier 2.6 series kernel? Oct 05 14:13:04 Oh, and by the way, booting from a CF doesn't work for me either... Oct 05 14:49:42 Does the SD slot on collie support SDHC cards? Oct 05 15:08:50 otto_: yes Oct 05 16:59:08 I just used narcissus (which seems very impressive to me so far) to generate an unstable system for spitz. What filesystems will supported by its kernel? I was considering installing it on ext4. Oct 05 17:01:20 BitWraith: it's a 2.6.26 so no current ext4 support Oct 05 17:01:32 (and it's disabled in kernel config) Oct 05 17:02:19 ah Oct 05 17:03:05 I guess I'll stick with ext2 then (since I'm installing on an SD card, journalling is not a good idea) Oct 05 19:13:36 I generated an image with enlightenment, and some other window manager... how do I switch between the two? Do I just use an .xinitrc file, or is there a "proper" way to do it? Oct 05 19:14:11 enlightenment is acting a bit strange... it uses 60-85% CPU even while idle Oct 05 19:15:13 apparently this is what I get for clicking "unstable" in the drop down box. lol Oct 05 19:16:48 I just assumed that I would probably have to click unstable to get python 2.6, otherwise I wouldn't have bothered Oct 05 20:55:57 all: do I need to have a kernel with dss2 support in order for angstrom to boot? we are seeing X-server crashes when using such kernels. Oct 05 21:01:59 orbarron, on which platform? Oct 05 21:08:56 orbarron: you forgot NEON again Oct 05 21:09:38 Nope.. NEON is enabled.... Oct 05 21:12:43 here is what happens... I boot up my zoom2 and I am able to see angstrom for the first two boot ups (sometimes). After that the screen goes to white and it seems X-server is gone. (FYI: kernel=2.6.27 no dds2 support) Oct 05 21:13:19 had to go back to older kernel, need GFX SDK for some test... Oct 05 21:15:11 orbarron: sounds like a kernel bug Oct 05 21:15:20 orbarron: xserver just uses fbdev Oct 05 21:15:58 whiteout sounds like lcd driver didnt initialise LDCD right **** ENDING LOGGING AT Tue Oct 06 02:59:58 2009