> I've been using gentoo for 3 yrs now and using a grub.conf exactly as follows
> for all that time. It has <never> failed to work. I did not create
> the /boot dir with mkdir, that was done when I cp'd my bzImage
> from /usr/src/linux/arch/x86_64/boot/bzImage to /boot, and I did it that way
> because that's how the docs said to do it.
> tbill@Shooter ~ $ cat /boot/grub/grub.conf
> default 0
> timeout 10
> title=Gentoo (linux kernel 2.6.11-gentoo-r10)
> root (hd0,0)
> kernel (hd0,0)/boot/bzImage root=/dev/sda1
> If you, when you installed gentoo in the first place, placed /boot in its own
> partition, then anything you copy to that partition is going to start with
> "/boot...". How else are you going to tell the kernel to copy something to
> the boot partition when /boot is all you've mounted there? If you, as root,
> tell the system to mount the partition where you've installed grub.conf, how
> else do you specify it except as "mount /boot". I don't mean to belabor the
> point, but....
> So tell grub to look on "(hd0,0)/boot/bzImage" for the kernel to boot,
> only,since you don't have a bzImage but a genkernel, change it accordingly:
> (hd0,0)/boot/genkernel-*. I assure you that this <does not> "stop your
> system from booting fully."
> Also, since you're getting error code 15, what you have in /etc/fstab is
> completely immaterial. Grub can't even find your kernel, and grub's interest
> stops at finding the kernel, so take care of grub's errors first, then worry
> about whether your fstab is properly set up.
Actually, that reminds me that a year ago on amd64 architecture the compiled
grub did not work for me (it did compile but fail to boot) and I had
to use grub-static-0.93, which worked fine. I looked now and see that
I still use this version of grub on all my amd64 machines.
Dmitri Pogosyan Department of Physics
Associate Professor University of Alberta
tel 1-780-492-2150 412 Avadh Bhatia Physics Labs
fax 1-780-492-0714 Edmonton, AB, T6G 2J1, CANADA
firstname.lastname@example.org mailing list