On 29 Apr., 21:20, Martin Michlmayr <[EMAIL PROTECTED]> wrote: > Kevin Price reported that the new initramfs-tools in testing (version > 0.92) generates a ramdisk that does not boot correctly on the NSLU2 - > it makes your system unbootable (see bug #478236). Note that this > bug only affects users of testing - users of Debian 4.0 are not > affected. > > If you run Debian testing (lenny) rather than stable (etch) on your > NSLU2, please do _not_ upgrade until a fixed package enters testing. > > If you have already upgraded but not rebooted yet, you should be able > to flash the old, working image with: > cd /boot > mv initrd.img-2.6.24-1-ixp4xx initrd.img-2.6.24-1-ixp4xx~ > mv initrd.img-2.6.24-1-ixp4xx initrd.img-2.6.24-1-ixp4xx.bak > flash-kernel > > If you have upgraded, rebooted and your NSLU2 now fails to boot, there > are two recovery options: > > 1) If your root partition is on sda1 and you run arm (rather than > armel), you can download the following image and flash it with > upslug2:http://www.cyrius.com/debian/nslu2/files/sda1-2.6.24-1.bin > > 2) If the first option doesn't work for you, you can download the > "etch" installer fromhttp://slug-firmware.net, flash it, start it, > run it until the partitioning software starts, then go back, open a > shell (last but one point in the menu) and issue the following > commands: > > ~ # mkdir /x > ~ # mount /dev/sda1 /x > ~ # mount -t proc none /x/proc > ~ # mount --bind /dev/ /x/dev > ~ # chroot /x > sh-3.1# cd /boot > sh-3.1# mv initrd.img-2.6.24-1-ixp4xx initrd.img-2.6.24-1-ixp4xx~ > sh-3.1# mv initrd.img-2.6.24-1-ixp4xx initrd.img-2.6.24-1-ixp4xx.bak > sh-3.1# > sh-3.1# flash-kernel > Flashing kernel: done. > Flashing initramfs: done. > sh-3.1# > sh-3.1# exit > ~ # umount /x/proc > ~ # umount /x/dev > ~ # umount /x > ~ # reboot > > I hope this works for you. If not, please let me know. > > Sorry for the inconveniences. > -- > Martin Michlmayrhttp://www.cyrius.com/ > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
looks like it is fixed with the 0.92a release of initramfs-tools now in the testing sources -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
