FSO unstable upgrade errors alsa-states and initscripts-openmoko

[qhaz]

arne anka wrote:
> 
>> and the feeds from . . .
>> http://downloads.freesmartphone.org/fso-unstable/feeds/
>>
>> As far as I can determine both initscripts and openmoko-initscripts are
>> coming from the same feed.
> 
> a short survey shows to me that the packages are identical, contentwise.
> i assume someone renamed initscripts because it clashes with some naming  
> conventions. iirc opkg totally lacks any means to handle this kind of  
> conflicts, you are forced to manage that manually.
> 
>> 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.
> 
> probably something went wrong in the build process? you should definitley  
> file a bug report at the fso tra
>> trac.freesmartphone.org
> 
>> 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)
> 
> well, at least the sshd should run already, fso-gpsd should be started  
> rather late.
> login to the fr and remove
> initscripts
> then do
> ls -R /etc/rc* > /tmp/alogfile
> and post content of that file, if a reboot still does not work.
> 
>>
>> Then just hangs there . . .
> 
> with the initscripts packages conflicting, there's probably some kind of  
> deadlock.
> 
>> Can you recommend any other source where I can try an FSO install?
> 
> nope. i do use debian with fso, which works different (and anyway i did  
> never flash any images).
> 
> _______________________________________________
> Openmoko community mailing list
> community at lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
> 
> 
Thanks Arne for trying to shed some light on this one.
I'll follow up with a bug report.
I can't seem to ssh into neo.  Mind you, I have flashed soooo many images in
the last couple of days, I hardly know what I have now!  Ha!  All I know is
that there is no rootfs from the FSO reps that works for me after Jan 12
release.
I'll keep picking away it, thank you for your input so far.

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