FSO unstable upgrade errors alsa-states and initscripts-openmoko
qhaz at bur.st
Thu Jan 15 15:08:56 CET 2009
arne anka wrote:
>>> Collected errors:
>>> * Package alsa-states wants to install file /etc/asound.state
>>> But that file is already provided by package *
>>> * ERROR: The following packages conflict with initscripts-openmoko:
>>> * initscripts *
>>> Has anyone else had this problem? Or any suggestions?
>> Same errors occured on my FSO testing installation yesterday. Now my
>> freerunner refuses to boot up properly: it pauses with some init errors
>> ("respawning too fast", "no more processes left in this runlevel").
> sounds weird. i wouldn't expect a failed alsa-state package to cause those
> opkg obviouls lacks the facilities to handle diversions.
> i'd suggest to login via ssh (provided it works, of course), move
> /etc/asound.state somewhere else and reinstall alsa-state.
> afterwards compare both files.
> a second look shows the far more important
> * ERROR: The following packages conflict with initscripts-openmoko:
> * initscripts *
> that might indeed cause the behaviour.
> could you please check, if initscripts-openmoko still exists in the feed?
> maybe it was replaced by initscript -- but opkg fails to do a clean
> Openmoko community mailing list
> community at lists.openmoko.org
Hi Arne, thanks for your quick reply. Yes, initscripts-openmoko still
exists in the unstable feed and initscripts likewise. As for the
alsa-states problem, it seems I don't have an /etc/asound.state file.
I've managed to flash the
kernel but can only run it with
openmoko-fso-image-glibc-ipk--20090108-om-gta02.rootfs.jffs2 rootfs anything
later than 08/01 and I can't boot.
View this message in context: http://n2.nabble.com/FSO-unstable-upgrade-errors-alsa-states-and-initscripts-openmoko-tp2161084p2162568.html
Sent from the Openmoko Community mailing list archive at Nabble.com.
More information about the community