All,

I am currently booting SuSE & XP just fine. I also can boot Fedora, but only from CD.

If you are successfully booting SuSE & Fedora, and using SuSE as the boot OS, could you please post your menu.lst file. I'd like add Fedora to my menu.lst, but I don't know what to put down.

Thanks,

Herkdrvr

I use Slackware, but I don't think there should be much differenence in the menu.lst with Suse. Below is a part of my menu.lst.

lba32
prompt
default 0
color red/black light-blue/black
timeout 10
title Slackware
root (hd0,0)
kernel /boot/vmlinuz root=/dev/hda1 vga=788 ro
title FedoraCore
root (hd1,0)
kernel /boot/vmlinuz root=/dev/hdb1 ro rhgb
initrd /boot/initrd.img

make sure, you point to the right hard drive partition, kernel and initrd image.

Redazz,

Thanks for the reply. I tried adjusting my menu.lst, but it gives me an "Error 15, file not found." Here's what I did.

I know for a fact that Fedora lives on /dev/hda2. I booted Fedora from the CD as root, and then went into the boot directory. I found two vmlinuz files and two initrd files, the only difference being the suffix ".smp" at the end of them.

Here's how I chose to adjust my menu.lst file:

title Fedora Core
root (hd2,0)
kernel /boot/vmlinuz-2.6.8-1.541 root=/dev/hda2 ro rhgb
initrd /boot/initrd-2.6.8-1.541.img

What am I missing here?

Thanks again!

Herk

If / is on hda2, then this is hd0,1 (not hd2,0).

The first digit is the adapter, the second the partition (both starting from 0)

Abisk,

Thank you so much for your reply. I think that Windows XP is on hd0,1. Here is an exerpt of my menu.lst file:

###Don't change this comment - YaST2 identifier: Original name: linux###
title Linux
kernel (hd1,1)/boot/vmlinuz root=/dev/sdb2 vga=0x31a splash=silent . desktop resume=/dev/sdb1 showopts
initrd (hd1,1)/boot/initrd

###Don't change this comment - YaST2 identifier: Original name: windows###
title Windows
root (hd0,1)
chainloader +1


What I'd like to do is point it correctly to Fedora, which I know is on /dev/hda2. I just don't know what specifically to add to my menu.lst file.

Any additional help you can provide will be appreciated.

Regards,

Herk

Maybe this link will help you to match the drive:

http://portal.suse.com/sdb/en/2002/0..._overview.html

The output of fdisk -l will show all recognized drives/partitions.

Also, the file /boot/grub/device.map shows you how disks are adressed.

If you show me this way, on which partition you have FC2, we could figure it out together.

With the information you provided so far, I still claim that hd0,1 is hda2 !

Abisko,

Here is the contents of my /boot/grub/device.map:

(hd0) /dev/sda
(hd1) /dev/sdb
(hd2) /dev/hda
(fd0) /dev/fd0

Also, here's what I got when I opened my partitioner. I'll show the Device and type along with mount if appropriate:

/dev/hda WD400BB-75CLB0
/dev/hda1 Linux Native
/dev/hda2 Linux Native
/dev/hda3 Linux Swap
/dev/sda ST3120026AS
/dev/sda1 Dell Utility
/dev/sda2 HPFS/NTFS Mount: /windows/D
/dev/sda3 Win 95 Fat LBA Mount: /windows/E
/dev/sdb WDC WD360GD-00FN
/dev/sdb1 Linux swap Mount: swap
/dev/sdb2 Linux native Mount: /

Hopefully this will give you the information you need to help address my problem. Once again, THANK YOU so much!

Regards,

Herk

OK, we are down to two possibilities:

I appologize, you were right with hd2 (I was almost sure that IDE devices are recognized first). And I guess it's SuSE on sdb2.

Fedora is either on hd2,0 (hda1) or hd2,1 (hda2). So try hd2,1 (as you said it's on hda2).

Okay, I'll try that. I'll let you know how it goes. Probably in about 8 hours--I'm really tired.

Have a great day, and I'll let you know the results.

Thank you for your time and expertise.

With much appreciation,

Herk

Oh, I almost forgot, should I include the numbers after "vmlinuz" as it's shown in my file system, or just the word "vmlinuz"?

Herk

Well, I couldn't wait to try the new syntax. I unfortunately got the same error. Here's what it said:

hd2,1 file type is ext2fs, partition type 0x83

kernel /boot/vmlinuz-2.6.8-1.541 root=/dev/hda2 ro rhgb

Error 15: File not found

There's got to be something small, yet crucial, that I am skipping.

Any thoughts? Thanks again.

Herk

I don't know if suse and fedore use slightly different grub-versions.

As you might have seen, suse doesn't use the root-option, instead they write the hdd directly in the path.
I suggest to have a try on this entry:

title Fedora Core
kernel (hd2,1)/boot/vmlinuz-2.6.8-1.541 root=/dev/hda2 ro rhgb
initrd (hd2,1)/boot/initrd-2.6.8-1.541.img

Be sure that the filenames match the existing files. If you find links like 'vmlinuz' and 'initrd' in the boot directory, you can use these also, but check the link target first.

hda2 is equivalent to hd0,1 on grub. You should put in the full kernel name in menu.lst, but what I tend to do is to create a symlink to the kernel that I want to use, as vmlinuz, so that if I upgrade, it I don't have to fiddle about with grub settings. you would create the symlink from your /boot directory as follows,

ln -s vmlinuz-version vmlinuz

do the same for the corresponding initrd-version image because Fedora uses the initrd image.

That was my first guess, too, but not in this case. It seems that a S-ATA controller comes first. In the device.map, this place has been taken by sda and since there is a sdb too, hda comes in third place.

I see, I have never used S-ATA, so I assumed it was the same as normal IDE. Thanks for the info coz I am gonna build a S-ATA based pc soon and I probably would have run into problems without this info.