How to fix /boot/grub/menu.lst

[Craig White]

On Mon, 2006-01-02 at 19:09 -0500, joe wrote:
> Can someone please tell me why the /boot/grub/menu.lst entry 
> shown here and at the bottom of this message works for everything 
> except for booting the new Win4Lin kernel that I just installed? 
> The location of the kernel is correct as shown, but when I try 
> to boot with it, I get the response "file not found." 
> 
> # inserted the next lines 0512-30 ======= THIS DOES NOT WORK 
> title Mandriva Win4Lin test at hda6 - 2.6.12-12
> kernel (hd0,5)/boot/win4lin-2.6.12-12mdk root=/dev/hda6
> initrd (hd0,5)/boot/win4lin-2.6.12-12mdk.img
> 
> 
> =========
> $ df (looks like this): 
> Filesystem           1K-blocks      Used Available Use% Mounted on
> /dev/hda1             10080488   3412732   6155688  36% /
> tmpfs                   257924         0    257924   0% /dev/shm
> /dev/hda3              4032124   2426284   1401012  64% /home
> 
> =========
> $ ls -ltrG /mnt (looks like this):
> drwxr-xr-x    2 root    4096 2004-10-10 14:02 hda1     mepis /
> drwxr-xr-x    5 root    4096 2004-10-13 17:14 hda3     mepis /home 
> drwxr-xr-x    2 root    4096 2004-10-09 15:45 hda5     xandros 
> drwxr-xr-x    2 root    4096 2004-10-09 15:45 hda6     mandriva /
> drwxr-xr-x    2 root    4096 2004-10-09 15:45 hda7     mandriva /home 
> drwxr-xr-x    2 root    4096 2004-10-10 13:20 temp     
> drwxr-xr-x    2 root    4096 2004-10-09 15:45 hda8     not in use 
> drwxr-xr-x    2 root    4096 2004-10-09 15:45 hda9     not in use 
> drwxr-xr-x    2 root    4096 2005-03-25 17:55 floppy 
> drwxr-xr-x    2 root    4096 2004-10-10 14:10 cdrom 
> drwxr-xr-x    2 root    4096 2004-10-10 14:10 cdrom1 
> drwxr-xr-x    2 root    4096 2004-10-16 10:43 camera 
> drwxr-xr-x    2 root    4096 2004-11-04 09:10 sda1     usb for camera 
> drwxr-xr-x    2 root    4096 2004-10-12 16:06 hdb7     second HD
> drwxr-xr-x    2 root    4096 2004-10-12 16:06 hdb5     second HD
> drwxr-xr-x    2 root    4096 2004-10-12 16:06 hdb1     second HD
> 
> ==========
> $ cd /boot
> $ ls -ltrG (looks like this): 
> -rw-r--r--    1 root   16208 2004-03-17 20:44 mepis.bmp
> -rw-r--r--    1 root   67648 2004-05-25 09:46 memtest86.bin
> -rw-r--r--    1 root   45584 2004-05-26 14:40 config-2.6.5
> -rw-r--r--    1 root 1313776 2004-05-26 14:58 vmlinuz-2.6.5
> -rw-r--r--    1 root  561908 2004-05-26 14:58 System.map-2.6.5
> -rw-r--r--    1 root   38173 2004-05-26 15:46 config-2.4.26
> -rw-r--r--    1 root 1052237 2004-05-26 15:59 vmlinuz-2.4.26
> -rw-r--r--    1 root  411515 2004-05-26 15:59 System.map-2.4.26
> drwxr-xr-x    2 root    4096 2005-12-30 19:28 grub
> 
> ==========
> $ cat /boot/grub/menu.lst (looks like this): 
> default saved
> timeout 15
> color cyan/blue white/blue
> foreground ffffff
> background 2f5178
> # splashimage /boot/grub/mepis.xpm.gz
> 
> # inserted the next lines 0512-30 ======= THIS DOES NOT WORK 
> title Mandriva Win4Lin test at hda6 - 2.6.12-12
> kernel (hd0,5)/boot/win4lin-2.6.12-12mdk root=/dev/hda6
> initrd (hd0,5)/boot/win4lin-2.6.12-12mdk.img
> 
> # inserted the next lines 0512-28 ======= THIS WORKS 
> title Mandriva at hda6 - 2.6.12-12
> kernel (hd0,5)/boot/vmlinuz-2.6.12-12mdk root=/dev/hda6
> initrd (hd0,5)/boot/initrd-2.6.12-12mdk.img
> 
> title MEPIS at hda1, kernel 2.6.5 ======= THIS WORKS 
> kernel (hd0,0)/boot/vmlinuz-2.6.5 root=/dev/hda1 nomce psmouse.proto=imps vga=788
> savedefault
> 
> title MEPIS at hda1, kernel 2.4.26 ======= THIS WORKS 
> kernel (hd0,0)/boot/vmlinuz-2.4.26 root=/dev/hda1 nomce vga=788 hdc=ide-scsi
> hdd=ide-scsi
> savedefault
> 
> title MEMTEST
> kernel /boot/memtest86.bin
> 
> # added the next two lines 0410-09 - rev 14, 18 ======= THIS WORKS 
> title Xandros
> kernel (hd0,4)/vmlinuz root=/dev/hda5
> initrd (hd0,4)/boot/initrd-2.4.24-x1.gz
> 
> title Use a qwerty keyboard with GRUB === IS ALL THE STUFF BELOW NECESSARY? 
> setkey y y
> setkey Y Y
> setkey q q
> setkey Q Q
> ======= several dozen more 'setkey' entries follow this ======= 
----
sort of hard to tell since when you gave us the directory listing
for /boot, it didn't actually include the hd(0,5) but rather hd(0,0) so
it's not possible to tell if you have an initrd for the boot.

I don't know for certain but I don't think you are supposed to have a
space in the 'title' for a grub boot (Mandriva Win4Lin) and wonder if
chosen, if it doesn't just boot the other Mandriva boot.

Craig