On Sun, Jan 10, 2010 at 12:17:32PM +0100, Jan Vlug wrote: > -----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
Try to opkg upgrade again.. I replied with right version of cworth, yours is still too old. Sorry for that.. > Now my questions: Good questions, thanks, I'll cc lists with answers > 1. Should I install coreutils? coreutils are needed only for people who can try to remove busybox, because without busybox AND coreutils there is no ls,mv,rm etc on your system and that's even harder to fix (well unpacking data.tar.gz from busybox|coreutils .opk to / is enough) > 2. Should I upgrade/downgrade or whatever busybox? with merged alternatives dirs you need something to trigger setting alternatives links to right targets, so you can reinstall all packages using u-a, but in most cases reinstalling busybox is usually enough (because it triggers setting of most alternatives and busybox has lowest priority there so after busybox reinstall its set to right alternative ie sysvinit instead of busybox) Only problem with that reinstall as I said before is that your version 1.15.3-r23.0.4 is not in feeds anymore (still I removed that too late). So you can downgrade to 1.13 version which is in feeds. > 3. Should I remove update-alternatives-cworth? You can remove it if you have finished this fixing session successfully > 4. Do I have to do anything else? I hope not -- uin:136542059 jid:[email protected] Jansa Martin sip:[email protected] JaMa _______________________________________________ Shr-devel mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-devel
