**** BEGIN LOGGING AT Sun Dec 25 02:59:57 2011 Dec 25 10:09:56 angstrom: 03testlab  07yocto * rad0450695e 10testlab/beagleboard/eglibc/systemd-image/build-id: beagleboard: systemd-image configured for angstrom v2011.12-core using branch angstrom-staging and revision 5ae0573455a2dd173f896ec435e2794ff588795b Dec 25 10:30:30 angstrom: 03testlab  07yocto * rae7997bb59 10testlab/beagleboard/eglibc/XFCE-NetworkManager-image/build-id: beagleboard: XFCE-NetworkManager-image configured for angstrom v2011.12-core using branch angstrom-staging and revision 5ae0573455a2dd173f896ec435e2794ff588795b Dec 25 10:30:31 angstrom: 03testlab  07yocto * r9679e34f42 10testlab/beagleboard/eglibc/efl-nodm-image/build-id: beagleboard: efl-nodm-image configured for angstrom v2011.12-core using branch angstrom-staging and revision 5ae0573455a2dd173f896ec435e2794ff588795b Dec 25 10:30:31 angstrom: 03testlab  07yocto * rf2fc0387ce 10testlab/beagleboard/eglibc/systemd-GNOME-image/build-id: beagleboard: systemd-GNOME-image configured for angstrom v2011.12-core using branch angstrom-staging and revision 5ae0573455a2dd173f896ec435e2794ff588795b Dec 25 10:53:10 hello ppl Dec 25 10:53:11 http://paste.pocoo.org/show/525663/ Dec 25 10:53:19 what have I done wrong? Dec 25 11:36:54 hello, i'm trying to build the latest distro from http://www.angstrom-distribution.org/building-angstrom Dec 25 11:37:05 but i'm having problem when i start the image. Dec 25 11:37:37 the kernel boots quicklu, but when user space applications/demons start it took first time ~1h Dec 25 11:37:51 to start the desktop that is slow and unstable. Dec 25 11:40:18 what type of SD card did you use? Dec 25 11:41:06 kingston micro sd Dec 25 11:41:15 i suspect in used fs Dec 25 11:41:26 the angstrom partition was formated with ext3 Dec 25 11:41:33 ext4 did not worked Dec 25 11:41:55 which class is claimed for the kingston card? Dec 25 11:42:25 not sure, this is the card that i've received with the board. the original image worked good Dec 25 11:42:55 did the original image boot a full desktop environment? Dec 25 11:43:00 yes. Dec 25 11:43:07 the class is 4, now i see Dec 25 11:43:43 I'd prefer 6 or 10 nowadays, not because of raw speed, but because they tend to perform better at random io Dec 25 11:44:01 both desktop environments are the same? Dec 25 11:44:23 no, the original one is older angstrom. the new one is the angstrom-2010.x as i can see Dec 25 11:44:40 I suspect you're starving the system somehow Dec 25 11:44:54 the mayor problem that i see instability, that proves the starving as you noted. Dec 25 11:45:19 did you look at the serial console? Dec 25 11:45:39 serial works fine Dec 25 11:45:59 any output? OOMkiller? Dec 25 11:46:12 no, the serial console is clean. Dec 25 11:46:34 the boot process hangs a lot on "Recreating volatile..." drives Dec 25 11:46:54 I'd keep top running there to get an idea what's happening Dec 25 11:47:30 tried, the most of the time (~20% cpu) is occupied with gnome Dec 25 11:47:49 i'll try to rebuild all since during th e build process i ran out of hdd space. Dec 25 11:48:06 but, i'd like to get help how to select a version that is proven to be stable. Dec 25 11:48:45 as i can see, there are diferent targets that can be selected. but i'm not sure how to find what are all choices? Dec 25 11:48:56 MACHINE=beagleboard ./oebb.sh bitbake virtual/kernel Dec 25 11:49:07 this is obvios that is for kernel only. Dec 25 11:49:16 but how can i learn which are other options? Dec 25 11:50:07 when i installed console image, the board worked just fine, but i need gnome Dec 25 11:56:54 mini2440 support is there any in angstrom? MACHINE=mini2440 fails with unknown machine Dec 25 11:58:54 bb: you might want to join #beagle Dec 25 12:00:56 thanks Dec 25 12:01:07 dm8tbr: have any idea? Dec 25 12:03:08 s0undt3ch: no idea, not my field of expertise Dec 25 12:03:20 k. Thanks Dec 25 13:43:51 after a new build of angstrom build, the start of the user space demons/processes takes too long Dec 25 13:43:56 any idea why? Dec 25 13:44:40 there are too many lines that something is configuring: Configuring kernel-module-ircomm. **** ENDING LOGGING AT Mon Dec 26 02:59:56 2011