On Tue, Feb 03, 2009 at 03:07:00PM +0100, Petr Vanek wrote:
> >> It's a good guess... does mount say that it's still ro?  
> i have flashed u-boot and it starts OK. reflashed qi and have the
> problem again. interestingly enough i tried to boot fso from nor menu
> once and then qi was able to boot it ok afterwards. so i am not sure
> what exactly happens there for the first time...

   Perhaps this is the same initscripts bug that was introduced with
OM2008.9, causing it to fail to boot if you upgraded from OM2008.8 with opkg
instead of installing a new image? The bug is that /etc/init.d/udev tries to
write to the rootfs before it has been remounted rw. Example patch which I
use to get OM2008 going after the upgrade:

--- /mnt/flash/etc/init.d/udev~ 2008-11-24 04:20:49.000000000 +0100
+++ /mnt/flash/etc/init.d/udev  2008-11-25 11:28:14.000000000 +0100
@@ -53,12 +53,16 @@
+# rootfs might be read only at this point
 make_extra_nodes() {
   if [ "$(echo /lib/udev/devices/*)" != "/lib/udev/devices/*" ]; then
     cp -a /lib/udev/devices/* /$1/
   elif [ -f "/lib/udev/devices.tar.gz" ]; then
-    tar -C /lib/udev -zxf "/lib/udev/devices.tar.gz"
-    cp -a /lib/udev/devices/* /$1/
+#    tar -C /lib/udev -zxf "/lib/udev/devices.tar.gz"
+#    cp -a /lib/udev/devices/* /$1/
+    tar -C /$1/ -zxf "/lib/udev/devices.tar.gz"
+    mv /$1/devices/* /$1/
+    rmdir /$1/devices
   [ -e /etc/udev/links.conf ] || return 0

(You'd get a message something like 'tar: Unable to open devices'.)

> the trouble is that i don't know how to change the ro flag for qi (i

   The rootfs should always be mounted ro at first.

Rask Ingemann Lambertsen
Danish law requires addresses in e-mail to be logged and stored for a year

Openmoko community mailing list

Reply via email to