Erik Grootjans wrote:
HI,
After installing FC6 I cannot boot Windows XP.
(Fedora 6 boots OK)
Booting XP I get the grub commands
rootnoverify (hd0,1)
chainloader +1
on screen and a black screen and thats it.
How can i get Windows XP to get booted by grub again?
Thanks
Erik
===========================
Additional info:
===========================
The file grub.conf seems to be ok.
cat grub.conf
# 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 /vmlincat grub.conf
# 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/hda
default=1
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.18-1.2798.fc6xen)
root (hd0,0)
kernel /xen.gz-2.6.18-1.2798.fc6
module /vmlinuz-2.6.18-1.2798.fc6xen ro
root=/dev/VolGroup00/LogVol00
rhgb quiet
module /initrd-2.6.18-1.2798.fc6xen.img
title Windows XP
rootnoverify (hd0,1)
chainloader +1uz-version ro root=/dev/VolGroup00/LogVol00
Is the information above actually in the file? It looks scrambled after
chainloader +1 - Anyway, other than the scrambled file and the wrapping,
I have no idea. The basics look alright to me.
Jim
# initrd /initrd-version.img
#boot=/dev/hda
default=1
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.18-1.2798.fc6xen)
root (hd0,0)
kernel /xen.gz-2.6.18-1.2798.fc6
module /vmlinuz-2.6.18-1.2798.fc6xen ro
root=/dev/VolGroup00/LogVol00
rhgb quiet
module /initrd-2.6.18-1.2798.fc6xen.img
title Windows XP
rootnoverify (hd0,1)
chainloader +1
--------------------
uitput fdisk option p:
fdisk /dev/hda
The number of cylinders for this disk is set to 14593.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/hda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 1 13 104391 83 Linux
/dev/hda2 * 14 5750 46078200 7 HPFS/NTFS
/dev/hda3 5750 7283 12315240 f W95 Ext'd (LBA)
/dev/hda4 7284 14593 58717575 8e Linux LVM
/dev/hda5 5750 6515 6146248+ 7 HPFS/NTFS
/dev/hda6 6515 7152 5118088+ b W95 FAT32
Command (m for help): q
--
Aren't we lucky our documentation is so sparse noone can accuse us of being
inconsistent? 8)
- Rusty Russell on linux-kernel
