Frans Pop wrote: > On Monday 10 July 2006 03:56, Nick Phillips wrote: > >> I did; the daily booted and installed (don't have the date of the >> daily to hand at the moment) but the kernel installed during the >> installation did not boot. >> > > That can be explained because the installed kernel is currently not the > same as that used by the installer when installing testing. > > You should be able to solve that by using the rescue mode of the installer > (boot using 'rescue'). You will be asked to select the partition that has > the root filesystem of the installed system. > After that, the best thing to do is switch to VT2, 'chroot /target', mount > other filesystems you need (you need at least 'mount none /sys -t sysfs', > and of course /boot, /usr, etc. if these are separate). > Then, download (wget) the 2.6.16 kernel image package from unstable and > install it using 'dpkg -i <package name>'. > >
Yep, that's basically what I did, except for the moment I've used a custom kernel copied over on a USB key, but I'll try the standard one when I get a chance. BTW it seems you actually have to mount the filesystems on /target before you chroot, otherwise /dev in the chroot doesn't have the right devices, which means you can't mount them. I can't remember whether I actually did that or used dpkg with --root in the end. >> I'll file another report when I get the install finished. >> > > Not really needed, unless you have other issues you'd like to report. If > not, just follow up to this one. > OK, will let you know - will probably try a reinstall fairly soon. Cheers, Nick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
