FSO unstable upgrade errors alsa-states and initscripts-openmoko

qhaz qhaz at bur.st
Fri Jan 16 14:13:45 CET 2009

Al Johnson wrote:
> On Thursday 15 January 2009, qhaz wrote:
>> From this site images have been posted on a fairly regular basis.  For
>> example, the current kernel image is
>> uImage-2.6.28-oe1+gitr34240a1c06ae36180dee695aa25bbae869b2aa26-r2-om-gta02.
>>bin which appeared on Jan 13th.
>> The latest rootfs image is . . .
>> openmoko-fso-image-glibc-ipk--20090115-om-gta02.rootfs.jffs2
>> which was appeared on Jan 15th.
>> I cannot boot from any rootfs from this site after their Jan 8th rootfs.
>> My FR stalls during startup before any X stuff is loaded.  The last
>> message
>> I see before it stalls says . . .
>> Starting freesmartphone.org gpsd comptibility daemon: (OK)
>> Then just hangs there . . .
> It isn't actually hung - the last init script has run, there is no X in
> those 
> images to start, so you are just seeing the last console output. I don't
> know 
> if this is intentional, but it may be part of a cleanup in preparation for 
> Milestone 5. It is a nightly build from the unstable branch after all ;0)
>> Can you recommend any other source where I can try an FSO install?
> Use the Milestone 4.1 image for something known to mostly work. Nightly
> builds 
> are pot luck - some are rather good, but not all.
> _______________________________________________
> Openmoko community mailing list
> community at lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
Hi Al, thanks for your comments too.  You are right, and I understand this
is all testing . . . but hey it's fun in the meantime.  Like you say,
Milestone 4.1 is a good backstop and the transition phase is just plain fun.


View this message in context: http://n2.nabble.com/FSO-unstable-upgrade-errors-alsa-states-and-initscripts-openmoko-tp2161084p2168064.html
Sent from the Openmoko Community mailing list archive at Nabble.com.

More information about the community mailing list