Re: [Angstrom-devel] Images are all broken

2012-03-08 Thread Christophe Aeschlimann
On 07.03.2012 15:04, Koen Kooi wrote: Does your kernel have these options enabled: http://dominion.thruhere.net/koen/cms/recommended-kernel-config-options-for-a-modern-angstrom-system ? It does now... Thank you ! This solved most of the issues but I still get : Dependency failed. Aborted

Re: [Angstrom-devel] Images are all broken

2012-03-08 Thread Gary Thomas
On 2012-03-08 05:36, Gary Thomas wrote: On 2012-03-08 05:30, Christophe Aeschlimann wrote: On 07.03.2012 15:04, Koen Kooi wrote: Does your kernel have these options enabled: http://dominion.thruhere.net/koen/cms/recommended-kernel-config-options-for-a-modern-angstrom-system ? It does

Re: [Angstrom-devel] Images are all broken

2012-03-08 Thread Ulf Samuelsson
You can at time rlogin even if you do not get a prompt. also, NFS mounting will give you access to logs onthe NFS host. Best Regards Ulf Samuelsson 4 mar 2012 kl. 13:48 skrev Gary Thomas g...@mlbassoc.com: All of the recent images I've built (for beaglebone at least) fail on boot with these

Re: [Angstrom-devel] Images are all broken

2012-03-08 Thread Gary Thomas
On 2012-03-08 12:20, Ulf Samuelsson wrote: You can at time rlogin even if you do not get a prompt. also, NFS mounting will give you access to logs onthe NFS host. I can't log in - no services get started because the postinst functions have not run and the system is not fully configured. See

[Angstrom-devel] Stuck at Started udev Coldplug all Devices

2012-03-08 Thread Eric Bénard
Hi, (sorry for the double post, I initaly sent it to Angstrom's user list instead of devel list). while testing angstrom images on a Cortex A8 (i.MX53 QSB), I found that systemd-gnome-image stays stucked (at least for one night) on : Starting udev Coldplug all The kernel is a 2.6.35 with all

Re: [Angstrom-devel] Stuck at Started udev Coldplug all Devices

2012-03-08 Thread Koen Kooi
Op 8 mrt. 2012, om 20:57 heeft Eric Bénard het volgende geschreven: Hi, (sorry for the double post, I initaly sent it to Angstrom's user list instead of devel list). while testing angstrom images on a Cortex A8 (i.MX53 QSB), I found that systemd-gnome-image stays stucked (at least for