Re: [SLUG] Cannot boot puter

From: Bob File (bobpat@earthlink.net)
Date: Sat Nov 29 2003 - 09:40:21 EST


> This is my grub menu.lst
>
> timeout 10
> color black/cyan yellow/cyan
> i18n (hd0,2)/grub/messages
> altconfigfile (hd0,2)/grub/menu.once
> default 0
>
> title linux
> kernel (hd0,2)/vmlinuz root=/dev/hda1 noapic devfs=mount hdc=ide-scsi
> resume=/dev/hda5 acpi=ht
> initrd (hd0,0)/initrd.img
>
> title floppy
> root (fd0)
> chainloader +1
>
> title failsafe
> kernel (hd0,0)/vmlinuz root=/dev/hda1 noapic failsafe devfs=nomount
> hdc=ide-scsi resume=/dev/hda5 acpi=ht
> initrd (hd0,0)/initrd.img
When grub starts, you can edit things on the fly. IOW, interrupt the boot
sequence and edit each line in the config you are trying to use. When the
grub menu starts up, press "e" for edit and grub will show you the lines in
the highlighted choice. Highlight one of the lines and press e for edit again
and the current line is now displayed in a line editor for editing. Note that
grub also has command line completion. For instance:
edit the first line and erase it back to : kernel (hd0,2)/
then press tab and grub will search the location for likely file names to
complete the line with. Once you have found a combo that works, you can edit
menu.lst and grub will use the edited file next time around. You don't have
to initialize it like you do LiLo. HTH
The installer used absolute paths, but you can also use relative. Here is an
example from my menu.lst:
title Linux on Dragon (SuSe)
        root (hd1,0)
        kernel /vmlinuz ro root=/dev/hdb4 hdc=ide-scsi
        initrd /initrd

You may have another problem with the ram disk; I'm afraid I can't help much
there. You may be able to discard the initrd line and get a boot, then try
and snoop around to find it or run the mkinitrd command by hand.

-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.



This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 18:26:09 EDT