-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/10/2010 01:04 AM, Martin Jansa wrote: >> On Fri, Jan 8, 2010 at 3:08 PM, Martin Jansa <[email protected]> wrote: >>> Correct fix will be announced later > > This is it! > > Now for shr-u, shr-t will have it later.. > > New version of update-alternatives-cworth is built in our feeds, so > please install/upgrade it with > > opkg update > (from this point be warned that lots of fso stuff was upgraded and its > not tested as much as it should be, so upgrade only selected packages if > you really need working phone now, but there is also shr-settings/mokonnect > fix with newer EFL libs) > > opkg install update-alternatives-cworth > (even if you removed this one before) > > it should write lenghty output about merging /usr/lib/ipkg/alternatives > to /usr/lib/opkg/alternatives. > > Then read that lengthy output and especially if you've removed some package > with > alternative of higher priority from image after flashing it (If you have > no idea what I'm takling about.. then you probably didn't). > > If you have already installed busybox-1.15 then you can fix symlinks by > reinstalling it with > opkg install -force-reinstall busybox, but version 1.15 was removed from > feeds (because it triggered this whole problem) so you need to downgrade > it to same 1.13* from feeds (not sure if -force-downgrade helps in > combination with -force-reinstall). > > Be carefull with busybox and don't remove it without having at least > coreutils installed (you need ls,rm,mv etc ..). > > If you've already installed newer busybox and your image won't boot, > then you need to boot some other distro from uSD (if broken one is in > NAND) or you can just fix it on your desktop (if the broken one is on > uSD). First you need to check that boot is broken because of busybox > "ls -l /sbin/init" will point to "../bin/busybox" > and then fix it, update init symlink with > "ln -sf /sbin/init.sysvinit /sbin/init" > Then it should boot again and you can continue with steps above, if > you're running 2nd distro I whould use > chroot /media/where_is_broken_distro and fix it all, before rebooting. > > If everything works ok again and your /usr/lib/ipkg/alternatives doesn't > exist you can remove update-alternatives-cworth. > > Cheers, >
Thanks for your extensive instructions. However I've still some questions. First let me explain what I did already: - - Last Friday I did an upgrade of SHR-U on NAND which resulted in an non-bootable phone. - - I installed an alternative distro (hackable:1) on uSD to boot my phone again (the hackable:1 instructions with two partitions did not work for me, so I flashed qi and installed hackable:1 on one large ext2 partition on uSD) - - I mounted the SHR-U file system in flash/NAND on /mnt/flash. - - With chroot I fixed the links as described above. Current situation: - - My FreeRunner is now able to boot SHR-U from NAND again. - - I tried to upgrade update-alternatives-cworth, but it is uptodate. version: update-alternatives-cworth - 0.99.154-r3.0.4 so I did not see the lengthy output as mentioned above (maybe they were in the initial upgrade that broke the boot process?) - - I do have a directory: /usr/lib/ipkg/alternatives - - I also do have a directory: /usr/lib/opkg/alternatives - - Busybox version: busybox - 1.15.3-r23.0.4 - - I don't have coreutils installed Now my questions: 1. Should I install coreutils? 2. Should I upgrade/downgrade or whatever busybox? 3. Should I remove update-alternatives-cworth? 4. Do I have to do anything else? Kind regards, Jan Vlug. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAktJuCwACgkQvuFuLCp9giCa2gCfaXwrKANwYKBvLrxvr6360mrr PLsAnArMWpSxhCQL91XvjB4BIkb9g/a/ =18E6 -----END PGP SIGNATURE----- _______________________________________________ Shr-devel mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-devel
