Fedora Core 4, Windows XP and Grub

[war59312 0]

Hey,

 

I finally got F4 booting.

 

Even manged to update the kernal and updated gnome to 2.12.1.

 

Now the only problem is getting winows xp to boot from gurb.

 

At the moment when slecting windows xp in grub it just opens grub as if I just typed in grub. Where you can only use grub commands. Know what I mean?

 

Well here is my grub config:

 

Code:

# grub.conf generated by anaconda## Note that you do not have to rerun grub after making changes to this file# NOTICE:  You have a /boot partition.  This means that#          all kernel and initrd paths are relative to /boot/, eg.#          root (hd2,0)#          kernel /vmlinuz-version ro root=/dev/hdf4#          initrd /initrd-version.img#boot=/dev/hdf1default=2timeout=5splashimage=(hd2,0)/grub/splash.xpm.gz#hiddenmenutitle Fedora Core (2.6.15-1.1831_FC4)        #root (hd2,0)        root (hd0,0)        kernel /vmlinuz-2.6.15-1.1831_FC4 ro root=LABEL=/        initrd /initrd-2.6.15-1.1831_FC4.imgtitle Fedora Core - Old (2.6.11-1.1369_FC4)        #root (hd2,0)        root (hd0,0)        #kernel /vmlinuz-2.6.11-1.1369_FC4 ro root=LABEL=/ rhgb quiet        kernel /vmlinuz-2.6.11-1.1369_FC4 ro root=/dev/hdf4        initrd /initrd-2.6.11-1.1369_FC4.imgtitle Windows XP        rootnoverify (hd0,0)        chainloader +1

[danleff 0]

If possible, please post the contents of your /boot/grub/device.map file.

 

What I want to see is what the assignments are for your hard drives.

 

You have an external pci raid controller card, correct?

 

[war59312 0]

Hey,

 

It's an internal pci raid controller card.

 

And here is my device.map:

 

Code:

(fd0)   /dev/fd0(hd0)   /dev/hdb(hd1)   /dev/hde(hd2)   /dev/hdf

Thanks again,

 

Will

[dan7 0]

Dear friends,

 

I have two hard drives in my computer and installed

Windows XP with FAT format on the first hard drives (hda)

and installed FC4 on the second hard drives and installed

GRUB on MBR of the hda. The default OS is set to XP.

When the system was rebooted, the GRUB menu showed up and

tried to run XP, but it did not run XP and came back

to the GRUB menu. But if FC4 is picked, FC4 runs ok.

What wrong is it?

 

Thank you in advance for any help.

 

[danleff 0]

Oopps! I meant to say;

 

You have a pci raid controller card, not an onboard raid controller, correct?

 

Notice that your hard drive designations are different than expecetd, due to the raid card.

 

(fd0) /dev/fd0

(hd0) /dev/hdb

(hd1) /dev/hde

(hd2) /dev/hdf

 

 

Where, in a totally ide system w/o a raid card, it would be something like;

 

(fd0) /dev/fd0

(hd0) /dev/hda

(hd1) /dev/hdb

(hd2) /dev/hdc

 

The drive orders are also interesting in Grub. The difference is based on how the raid card affects the drive order.

 

Can you post the output of;

 

fdisk -l

 

Do this as root user in a console screen.

 

In Fedora, you may need to do;

 

/sbin/fdisk -l

 

Remember, this is the letter L (small case), not the number 1 after fdisk.

 

This will tell us where the Windows installation is, as seen by Fedora.

[danleff 0]

dan7

 

I assume that you have the drives jumpered correctly, are using ide drives (not sata or raid) and that the installation was set up to boot your hda drive (HDD0 in the bios) first when you did the installation of Fedora?

 

Can you post the /boot/grub/menu.lst and /boot/grub/device.map file contents by any chance?

 

What motherboard is this, or the make and model of the system?

[war59312 0]

Hey,

 

Yes it's a pci raid controller card.

 

Here is fdisk -l output as requested:

 

Code:

Disk /dev/hdb: 61.4 GB, 61471162368 bytes255 heads, 63 sectors/track, 7473 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytes   Device Boot      Start         End      Blocks   Id  System/dev/hdb1   *           1        7473    60026841    7  HPFS/NTFSDisk /dev/hde: 80.0 GB, 80026361856 bytes255 heads, 63 sectors/track, 9729 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytes   Device Boot      Start         End      Blocks   Id  System/dev/hde1   *           1        8414    67585423+   7  HPFS/NTFS/dev/hde2            8415        9728    10554705    f  W95 Ext'd (LBA)/dev/hde5            8415        9728    10554673+   7  HPFS/NTFSDisk /dev/hdf: 120.0 GB, 120034123776 bytes255 heads, 63 sectors/track, 14593 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytes   Device Boot      Start         End      Blocks   Id  System/dev/hdf1   *           1          13      104391   83  Linux/dev/hdf2            1276        1393      947835   82  Linux swap / Solaris/dev/hdf3            1394       14593   106029000    f  W95 Ext'd (LBA)/dev/hdf4              14        1275    10137015   83  Linux/dev/hdf5            1394       14593   106028968+   7  HPFS/NTFSPartition table entries are not in disk order

 

Thanks again,

 

Will

[dan7 0]

Hi danleff,

 

Thank you for your reply.

 

I am using a DELL Latitude C800 notebook with two ide HDs.

The primary HD had Windows 2000 and the second HD is in

a modular bay and FC4 was installed. It worked perfectly.

 

Few days ago, I upgraded the BIOS and put Windows XP

(got rid of Windows 2000) on the primary HD. When

the system rebooted, the GRUB menu was gone. And then

I re-installed FC4 on the second HD and get back the

GRUB menu. Now I can have two options - first one

runs FC4 and second is to go to Windows XP (this is

default). However, when the system try to XP, it just

quickly display

Booting 'Windows XP'

rootnoverify (hd0,0)

chainloader +1

GRUB Loading stage2...

 

and returns to the GRUB meun.

 

 

the device.map file contains:

 

(fd0) /dev/fd0

(hd0) /dev/hda

(hd1) /dev/hdc (I do not know why not hdb)

 

the menu.lst (grub.config) file contains:

 

#boot=/dev/hda

default=1

timeout=5

splashimage(hd1,0)/grub/splash.xpm.gz

hiddenmenu

title Fedora Core (2.6.11-1.1369_FC4)

root (hd1,0)

kernel /vmlinuz-2.6.11-1.1369_FC4 ro root=LABEL=/ rhgb quiet

initrd /initrd-2.6.11-1.1369_FC4.img

title Windows XP

rootnoverify (hd0,0)

chainloader +1

 

 

hda is the primary drive and has XP.

hdc is the second drive and has FC4.

I can't see anything wrong here.

The other thing could be the new BIOS version,

otherwise, I do not know what is going on here.

 

Thanks for your help.

 

 

 

 

 

 

 

 

 

[danleff 0]

Will;

 

Do you know how to edit Grub from the boot splash screen? I really need to write a web page on this to refer to!

 

I have not played with my system with a raid card in it for a while. I think that I need to try this again myself.

 

Linux is seeing the drives, I believe, in reverse order. This is not unusual. The raid card causes this.

 

If you can edit at the splash screen, you can make temp. changes to grub there, without making them final yet (writing to the menu.lst file).

 

At the splash screen, hit the "e" key on your keyboard. Bear with me, I have a Suse grub splash screen and Fedora may be different!

 

When you hit the "e" key, you should get a text based screen.

 

Loook at the bottom command options. Add two lines after the;

 

title Windows XP

 

So that it looks like the following;

 

 

title Windows XP

map (hd0) (hd2)

map (hd2) (hd0)

rootnoverify (hd0,0)

chainloader +1

 

note: As you edit each line, just hit the enter key to make the changes take.

 

If that does not work, try;

 

title Windows XP

map (hd0) (hd2)

map (hd2) (hd0)

makeactive

chainloader (hd0,0)+1

 

When you are finished, and are back to the text screen that outlines the total Windows XP lines, hit the "b" key on the keyboard. This will attempt a boot. Let us know what happens.

 

If this works, you can modify you actual menu.lst file later on in Fedora.

 

If you maker a mistake, don't worry. Hitting the esc key gets you out.

[danleff 0]

dan7

 

The modular bay does not make you swap out the cdrom drive, does it?

 

Is the boot order in the bios the same, since you updated the bios, as the old one?

 

If you don't need to swap out the cdrom drive, than hdb is the cdrom drive. Remember, this is seen as an ide drive by the bios and linux. The designation is usually;

 

hd0 = primary master drive

hd1 = primary slave drive

hd2 - secondary master drive

hd3 = secondary slave drive

 

Quote:

Few days ago, I upgraded the BIOS and put Windows XP

(got rid of Windows 2000) on the primary HD. When

the system rebooted, the GRUB menu was gone.

 

Yes, when you install any version of Windows, it overwrites the master boot record where grub resided.

 

When you installed Windows XP, did you reformat the hard drive and install Windows XP on the exact partition that Windows 2000 was on?

[dan7 0]

danleff

 

> The modular bay does not make you swap out the cdrom drive,

> does it?

 

No. I take out the floppy disk drive as I don't need it

and use the modular bay for the second HD.

 

 

> Is the boot order in the bios the same, since you

> updated the bios, as the old one?

 

The boot order is now:

1. Diskette Drive

2. CDROM Drive

3. Internal HD

4. Modular Bay HD

 

 

> If you don't need to swap out the cdrom drive,

> than hdb is the cdrom drive.

 

Thanks.

 

 

> Yes, when you install any version of Windows,

> it overwrites the master boot record where grub resided.

 

GRUB has been installed on MBR of hda when FC4 is re-installed.

I don't know why it now doesn't work.

 

 

 

> When you installed Windows XP, did you reformat

> the hard drive and install Windows XP on the exact

> partition that Windows 2000 was on?

 

Yes, I did use quick format as FAT (not NTFS) and

install XP on the exact partition.

 

It seems to me that the system runs GRUB on MBR stored

on hda, but GRUB can not find the hda1, which is XP on.

 

Thanks for your replies.

 

 

 

[war59312 0]

Hey,

 

Thanks again for your help.

 

I tried both of them and both of them freeze with:

 

Grub loading stage2

 

Take Care,

 

Will

[war59312 0]

Never mind I figured it out!

 

Thanks a lot.

[danleff 0]

...and what was the solution???? I am interested and others may be as well!

[g0kth 0]

Danleff

 

Not had much time this year so far to try and resolve my dual boot problems.

 

You sent the following message on this thread:

 

2006-01-04 10:59:12

 

g0kth, I just switched my system over to sata only. If you are still having the problem, I may be able to resolve it, as I have my drives set up close to yours.

 

Following this message I gave you an update on what I had tried, still to no avail.

 

Can you give me details of your SATA setup to see if this will help solve my problems.

 

Cheers

 

Dave.

 

[danleff 0]

This is a test message to see if text formating works correctly;

 

map (hd0) (hd1)

 

map (hd2) (hd1)

 

Ok, there is an issue. I may have overlooked an important point.

 

g0kth,

 

Please post the following, as this is getting too difficult to follow. Let's recap.

 

1. What is your current boot order, pata or sata? In the bios, the order of disk detection, is it;

 

scsi, ide...

 

or;

 

ide, scsi...?

 

2. Post your current menu.lst or grub.conf file.

 

3. Post your device.map file.

 

[g0kth 0]

Hi Danleff

 

Ok just to recap on my system I have three hard drives:

 

160GB SATA holds the Windows XP 64 OS

80GB PATA holds the Fedora Core 4 OS

3GB PATA holds all my data files - docs, pics etc

 

Under Windows XP these drives are identified as:

 

160GB - C, E & F

80GB - H

3GB - G

 

Floppy - A

CD/DVD - D

 

Under FC4 these drives are identified as:

 

160GB - sda (sda1, sda5, sda6) or hd2

80GB - hda or hd0

3GB - hdb or hd1

 

Floppy - fd0

 

 

The BIOS boot sequence is:

 

1st Boot Device - FLOPY DRIVE

2nd Boot Device - CD/DVD

3rd Boot Device - PATA 80GB (FC4)

 

The Hard Disk boot sequence is :

 

1 PATA 80GB (FC4)

2 SATA 160GB (Win XP)

3 PATA 3GB (Data)

 

Note to use Win XP at the moment I have to go into

BIOS and swap 1 & 2 of the Hard disk boot sequence

around but ultimately the boot sequence above is

what I want with the start up menu allowing me to

default to FC4 with the option to select Win XP.

 

In FC4 starting with the 'Computer' folder I select the following folders to get to grub.conf / menu.lst and the device.map:

 

Filesystem

 

boot

 

grub

 

The grub.conf file contains the following:

 

# grub.conf generated by anaconda

#

# Note that you do not have to rerun grub after making changes to this file

# NOTICE: You have a /boot partition. This means that

# all kernel and initrd paths are relative to /boot/, eg.

# root (hd0,0)

# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00

# initrd /initrd-version.img

#boot=/dev/hda1

default=0

timeout=5

splashimage=(hd0,0)/grub/splash.xpm.gz

hiddenmenu

password --md5 **********************

title Fedora Core (2.6.11-1.1369_FC4)

root (hd0,0)

kernel /vmlinuz-2.6.11-1.1369_FC4 ro root=/dev/VolGroup00/LogVol00 rhgb quiet

initrd /initrd-2.6.11-1.1369_FC4.img

title Win XP64

rootnoverify (hd1,0)

chainloader +1

 

 

The device.map file contains the following:

 

# this device map was generated by anaconda

 

(fd0) /dev/fd0

(hd0) /dev/hda

(hd1) /dev/sda

 

 

When I boot up the PC and select FC4 from the menu it loads FC4 ok, if I select Win XP it just hangs.

 

So that's the current situation. hope that makes things clearer.

 

If you need any other info let me know.

 

Cheers

 

Dave

 

[danleff 0]

Interestingly, I just had one of my sata drives go south, so i had to change my setup. This may have shown me a thing or two about the issue. this is why I had a delay in responding to this post.

 

What happens when you change the Windows entry to;

 

title Windows XP

map (hd0) (hd1)

map (hd1) (hd0)

rootnoverify (hd0,0)

chainloader +1

 

 

or;

 

title Windows XP

map (hd0) (hd1)

map (hd1) (hd0)

rootnoverify (hd1,0)

chainloader +1

 

 

If it still fails, you need to alter your boot,ini file for Windows. To do this, you need to have administrator rights to your Windows installation.

 

Right click on My Computer, Advanced tab, Startup and Recovery--settings.

 

under Default OS,==> edit. what is the boot.ini designation for Windows?

 

multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP...

 

Specifically, what is the rdisk value?

[war59312 0]

Originally posted by danleff:

Quote:

...and what was the solution???? I am interested and others may be as well!

Hello,

 

Well, I changed to this:

 

Code:

# grub.conf generated by anaconda## Note that you do not have to rerun grub after making changes to this file# NOTICE:  You do not have a /boot partition.  This means that#          all kernel and initrd paths are relative to /, eg.#          root (hd2,0)#          kernel /boot/vmlinuz-version ro root=/dev/hdf1#          initrd /boot/initrd-version.img#boot=/dev/hdf1default=0timeout=5#splashimage=(hd2,0)/boot/grub/splash.xpm.gzsplashimage=(hd0,0)/boot/grub/splash.xpm.gz#hiddenmenutitle Fedora Core (2.6.15-1.2054_FC5)        #root (hd2,0)        root (hd0,0)        kernel /boot/vmlinuz-2.6.15-1.2054_FC5 ro root=LABEL=/ rhgb quiet        initrd /boot/initrd-2.6.15-1.2054_FC5.imgtitle Windows XP        rootnoverify (hd1,0)        chainloader +1

 

I left the old ones as commented out so you can see what I changed. I Just installed Fedora Core 5 (new install) as I am sure you can tell and it did the same thing. So I had to first boot into resuce mode.

 

Then I ran the following commands in this order:

 

Code:

1.) chroot /mnt/sysimage2.) cd /boot/grub3.) cat grub.conf (just so you can see it in its current form)4.) grub-install --recheck/dev/hdf5.) grub-install /dev/hdf6.) vi grub.conf7.) push a so vi goes into insert (edit) mode8.) Now in the VI editor you change the commented out lines in the code of my grub.conf above so it matchs mine.9.) Now save the new grub.conf by pushing on your keyboard "shift + : ) then hit "w" on the keyboard. Now the new grub.conf file is saved.10.) Reboot computer and everything now works as expected

 

So I will have to do this every time until it's fixed, if it ever is.

 

Take Care and thanks again for all your help and sorry for such late reply,

 

Will

[danleff 0]

Oh my God! I can't believe that I missed this!

 

Too many posts from too many folks....

 

your original grub file;

 

root (hd0,0)

kernel /vmlinuz-2.6.15-1.1831_FC4 ro root=LABEL=/

initrd /initrd-2.6.15-1.1831_FC4.img

title Fedora Core - Old (2.6.11-1.1369_FC4)

#root (hd2,0)

root (hd0,0)

#kernel /vmlinuz-2.6.11-1.1369_FC4 ro root=LABEL=/ rhgb quiet

kernel /vmlinuz-2.6.11-1.1369_FC4 ro root=/dev/hdf4

initrd /initrd-2.6.11-1.1369_FC4.img

title Windows XP

rootnoverify (hd0,0)

chainloader +1

 

They referenced the same hard drive and partition for Fedora and Windows (red).

 

Plus, the modular bay apparently changes the sequence of how the drives are detected. So, your root= line for Fedora needed to reference exactly where the root filesystem is, with the modular bay inserted (green).

 

Nice work!!!

[war59312 0]

Thanks again.

[g0kth 0]

Danleff, You're right too many different things going on now on this topic.

 

Okay we have finally had success and I can now boot up from the PATA drive with FC4 installed, choose either FC4 or Win XP from the grub menu and run the chosen OS. So thanks for your help.

 

Just for completeness and future info I have answered your questions below:

 

You wrote:

 

What happens when you change the Windows entry to;

 

title Windows XP

map (hd0) (hd1)

map (hd1) (hd0)

rootnoverify (hd0,0)

chainloader +1

 

OUTCOME:

 

I get the following dislayed on the screen:

 

Booting 'Win XP64'

map (hd0) (hd1)

map (hd1) (hd0)

rootnoverify (hd0,0)

chainloader +1

 

GRUB _ (where _ is a flashing cursor).

 

 

You wrote:

 

or;

 

title Windows XP

map (hd0) (hd1)

map (hd1) (hd0)

rootnoverify (hd1,0)

chainloader +1

 

OUTCOME:

 

This will successfully launch the chosen OS from the grub menu.

 

 

You wrote:

 

If it still fails, you need to alter your boot,ini file for Windows.......... what is the boot.ini designation for Windows?

 

multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP...

 

Specifically, what is the rdisk value?

 

THE RDISK VALUE IS rdisk(0), the rest of the values are as listed in your question.

 

Hope that helps. Thanks again for your help and from my point of view this topic has now been resolved and can be closed.

[danleff 0]

Yep, that's the ticket! Good job!!!!

 

The problem also is that new posters are reading this thread and trying too many individual solutions suggested here at will.

 

Let's close this out and ask users with new problems to start a new post with there probles.