From: Jeff Cranmer <jcranmer01@earthlink.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Grub problems
Date: Sun, 29 Oct 2006 14:53:34 -0500 (GMT-05:00) [thread overview]
Message-ID: <5422293.1162151614580.JavaMail.root@elwamui-norfolk.atl.sa.earthlink.net> (raw)
I am trying to bring up a new Linux unit (my old desktop died on Thursday).
My hardware is an ASUS M2NPV-VM motherboard, running an Athlon X2 3800+ Dual core processor.
I have a serial ATA 250GB hard drive which I am attempting to install my OS into. The hard drive maps in the bios to SATA4, and maps within Linux to /dev/sda.
I also have two other parallel IDE dard drives, connected via a raid controller (though not configured for RAID) to Drive numbers 0 and 3 on the RAID controller. These drives map to hde and hdh respectively, with a DVD writer mapping to both /dev/hda and /dev/dvdrw.
The bios is configured to boot first from the DVD (primary IDE master) then from the 250GB SATA hard drive.
swapspace is on /dev/sda2, /boot is on /dev/sda1, and root is on /dev/sda6
I am running genkernel
After I configure grub, and install grub to the mbr using grub-install, the reboot fails, with GRUB doing nothing but display the text 'GRUB'.
Evidently, either I am doing something wrong at the grub-install stage, or there is a problem with grub. I have had a similar lack of success with Fedora Core 6 and Mandriva installs (same problem).
The boot partition is an ext3 filesystem
My grub.conf file is as follows:
default=0
timeout=30
splashimage=(hd0,5)/boot/grub/splash.xpm.gz
title=Gentoo Linux 2.6.17-r8
root (hd0,5)
kernel /boot/kernel-genkernel-x86_64-2,6,17-gentoo-r8 root=/dev/ram0 init=/linuxrc ramdisk=8192 real_root=/dev/sda6 udev vga=0x318 video=vesafb:mtrr:3,ywrap doscsi
initrd /boot/initramfs-genkernel-x86_64-2.6.17-gentoo-r8
When I run grub-install /dev/sda, it reports no errors.
The device.map file contains the following
(hd0) /dev/sda
This file was generated by the fedora installation (possibly the source of the problem?).
Update:
>After a little bit of surfing, I tried the command grub-install --recheck /dev/sda
>That changed the device map file so that the /dev/sda drive mapped to hd2
>
>The full /boot/grub/device.map listing is now
>(fd0) /dev/fd0
>(hd0) /dev/hde
>(hd1) /dev/hdh
>(hd2) /dev/sda
>
>I edited the grub.conf file so that the splash image and root lines reference (hd2,5), then re-ran grub-install /dev/sda. Still no joy. On boot up, the screen stays blank for a while, then every 10 seconds or so, it adds another " GRUB" text element to the screen. No sign of any boot-up activity.
Any suggestions gratefully received, as I'm trying to get this system working by the end of the weekend.
Thanks in advance
Jeff
--
gentoo-user@gentoo.org mailing list
next reply other threads:[~2006-10-29 20:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-29 19:53 Jeff Cranmer [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-31 17:41 [gentoo-user] Re: Grub problems Jeff Cranmer
[not found] <6886922.1162153151682.JavaMail.root@elwamui-norfolk.atl.sa.earthlink.net>
2006-10-29 23:23 ` Richard Fish
2006-10-29 19:56 Jeff Cranmer
2006-10-29 20:11 ` Joe Menola
2006-10-31 17:13 ` Mick
2006-10-29 19:22 Jeff Cranmer
2006-10-29 19:48 ` Joe Menola
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5422293.1162151614580.JavaMail.root@elwamui-norfolk.atl.sa.earthlink.net \
--to=jcranmer01@earthlink.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox