Richard Fish <[EMAIL PROTECTED]> writes:
[...]
>>If you get a GRUB command line but no selection menu, you can think GRUB
>>*is installed* on the MBR but just doesn't know your configuration.
>>
>>
> Indeed. Getting a grub command line is definitely not right for what
> you describe...it means it doesn't find (at boot time) your config file
> at all. What does the setup(hd0) command output? At a minimum I think
> you should get a text based menu.
Harry does:
grub> root (hd0,0)
Filesystem type is ext2fs, partition type 0x83
(-HP its actually ext3fs.. but this is it because I have no other ext?fx
partitions)
Harry does:
grub> setup (hd0)
Checking if "/boot/grub/stage1" exists... no
Checking if "/grub/stage1" exists... yes
Checking if "/grub/stage2" exists... yes
Checking if "/grub/e2fs_stage1_5" exists... yes
Running "embed /grub/e2fs_stage1_5 (hd0)"... 22 sectors are
embedded.
succeeded
Running "install /grub/stage1 (hd0) (hd0)1+22 p (hd0,0)/grub/stage2
/grub/menu
.lst"... succeeded
Done.
> Maybe you can compare against what I have? (Note, I filtered the file
> listings to just show the important files/links...)
>
> carcharias root # cat /boot/grub/grub.conf
> default 0
> timeout 5
> splashimage=(hd0,0)/grub/splash.xpm.gz
>
> title Linux
> kernel (hd0,0)/vmlinuz-2.6 root=/dev/sys/root
> video=radeonfb:[EMAIL PROTECTED] noapic quiet
> initrd (hd0,0)/initrd-2.6
>
> title Safe
> kernel (hd0,0)/vmlinuz-safe root=/dev/system/root
> video=radeonfb:[EMAIL PROTECTED] noapic 1
> initrd (hd0,0)/initrd-safe
As an aside [ I don't want to change thread subject here ]
I don't understand what your setup is doing or what some of the
appended stuff is.
Would you mind writing me a reply about that privately or in a new
thread if you have time. I'll include my mail address here in case
Gmane obfuscates it in the headers.
[EMAIL PROTECTED]
Actually a new thread might be more appropriate since I suspect there
are probably a few other readers who would be interested in that.
Mabye something line:
Subject: Grub.conf examples and meaning
> carcharias root # ls -l /boot
> lrwxrwxrwx 1 root root 1 Feb 13 14:25 boot -> .
> drwx------ 2 root root 4096 Mar 27 18:12 grub
> -rw------- 1 root root 691790 Mar 12 20:35 initrd-2.6
> -rw------- 1 root root 691790 Mar 12 20:35 initrd-safe
> -rw-r--r-- 1 root root 1602901 Mar 29 08:52 vmlinuz-2.6
> -rw-r--r-- 1 root root 1608822 Mar 13 11:08 vmlinuz-safe
> carcharias root # ls -l /boot/grub
> total 1140
> -rw------- 1 root root 197 Aug 27 2004 default
> -rw------- 1 root root 45 Aug 24 2004 device.map
> -rw------- 1 root root 11136 Feb 26 01:47 e2fs_stage1_5
> -rw------- 1 root root 384 Mar 27 18:12 grub.conf
> lrwxrwxrwx 1 root root 9 Feb 13 14:25 menu.lst -> grub.conf
> -rw------- 1 root root 33856 Feb 26 01:47 splash.xpm.gz
> -rw------- 1 root root 512 Feb 26 01:47 stage1
> -rw------- 1 root root 134632 Feb 26 01:47 stage2
> -rw------- 1 root root 12712 Feb 26 01:47 xfs_stage1_5
I don't have the `default' file or the `boot -> .' symlink.
Another poster in this thread has mentioned he has no boot -> .
symlink and his setup works ok. So I'm going to reboot first witout
it .. if it fails like it has been doing then I'll include it and try
again. At leasts then I'll have some more diffinitive clues.
> grub> root (hd0,0)
> Filesystem type is xfs, partition type 0x83
>
> grub> setup (hd0)
> Checking if "/boot/grub/stage1" exists... yes
> Checking if "/boot/grub/stage2" exists... yes
> Checking if "/boot/grub/xfs_stage1_5" exists... yes
> Running "embed /boot/grub/xfs_stage1_5 (hd0)"... 25 sectors are embedded.
> succeeded
> Running "install /boot/grub/stage1 (hd0) (hd0)1+25 p
> (hd0,0)/boot/grub/stage2 /boot/grub/menu.lst"... succeeded
> Done.
>
> And reboot...and hey, wait a minute, my system won't reboot!!!
>
> That install line above turns out to be wrong. It should not have
> "/boot" in the path for stage2. I think maybe the xfs_stage_1_5 doesn't
> understand sybolic links. Removing the link from /boot/boot to /boot
> and re-running grub gives me:
As you can see from the included output above.. My addressing is
right.
=== two reboots later ===
Well I learned one thing:
First reboot, I got the black screen console syle grub command line
again like I've been getting.
I then created a /boot/boot -> . symlink.
On that reboot I got the splash screen, but still just a grub command
line. So I know now what that /boot/boot -> does.
However, my main problem still remains... I'm not getting the normal
bootup screen... and can not see the reason.
--
[email protected] mailing list
