On Tue, 29 May 2007 17:47:47 +1200 Rohit Grover <[EMAIL PROTECTED]> wrote:
> Hi, > > > Can you post the entry for the default kernel build ( there'll be a line, > > probably default 0, which is the first definition ) in > > /media/root/boot/grub/menu.lst? > > The default is set to 1 (the second entry in menu.lst) and it > corresponds to Ubuntu's 2.6.20.15-generic [vanilla]. > > Entry 0 corresponds to the new kernel. > > > > > The way I reinstall is as follows: > > > > rather than grub_install... > > > > grub > > > > grub> root (hd0,0) > > grub> setup (hd0) > > grub> quit > > I tried the above as my Approach I. It didn't do the trick. The > desktop still hangs at the GRUB load message. Could I have corrupted > the stage 2 loader's bits? > > > However, the problem could well be in the init image. To fix this... > > > > mount -t proc /media/root/proc > > chroot /media/root /bin/bash > > mkinitramfs -o /boot/initrd.img-2.6.20-15-generic 2.6.20-15-generic > > (if it can't find mkinitramfs, then apt-get install initramfs-tools, and > > try again.) > > exit > > I suspect if the problem was the result of a bad init image, I'd > atleast get past the GRUB hang and there should have been some message > showing that the kernel had been loaded into memory. Don't you agree? You're using /dev/sda - scsi ( well probably sata ) drivers, which are rarely built into the kernel. The initramfs is unzipped ( iirc it's a cpio archive ), and some of the contents will provide the module required to get it to recognise the disk properly, rather than the explicit method used to read the initramfs image. You may not have the correct modules in the images, or, as you say, you may have damaged something. You can wget the contents of /boot/grub ( minus menu.lst ) from my current feisty install...2.6.20.15-generic from http://www.greengecko.co.nz/grub.tar.gz - see if they help. Steve > > Thanks a lot for responding. > > regards, > rohit.
