Hi --
I'm trying to add Fedora 16 to a Dell Precision M6500 laptop that already has Windows 7 64-bit installed. I had forseen the need to do this and left some free disk space on one of my three internal drives (2 solid state and one SATA). The Fedora 16 installation goes off without a hitch and is clearly installing about 1225 packages that include the Windowing system I requested. I chose to do a Custom Layout and set up an 8GB swap partition and a 180GB ext4 partition for Fedora 16. After installing the Fedora distro, I went back into Windows and used Easy BCD to set up the dual boot menu. I chose grub2 for the linux entry I added, but was not able to specify the partition information (it informed me it would be automatically configured). It has produced the following entries, which I suspect is wrong:
Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device partition=\Device\HarddiskVolume2
description Windows Boot Manager
locale en-US
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {079b397c-5494-11e0-a713-a409df4d3db0}
resumeobject {079b397b-5494-11e0-a713-a409df4d3db0}
displayorder {079b397c-5494-11e0-a713-a409df4d3db0}
{079b398a-5494-11e0-a713-a409df4d3db0}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 30
displaybootmenu Yes
Windows Boot Loader
-------------------
identifier {079b397c-5494-11e0-a713-a409df4d3db0}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence {079b397d-5494-11e0-a713-a409df4d3db0}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {079b397b-5494-11e0-a713-a409df4d3db0}
nx OptIn
Real-mode Boot Sector
---------------------
identifier {079b398a-5494-11e0-a713-a409df4d3db0}
device partition=C:
path \NST\AutoNeoGrub0.mbr
description Fedora 16 Linux
In particular,I suspect the path in the Fedora 16 entry because during Fedora installation I chose not to use a master boot record, but to place the loader on the first sector of the drive. I'm a total Linux newbie (this is absolutely my first time dealing with it at all), so I of course could be wrong about all of this. But wondering has any ideas on how I can diagnose this problem and fix it.
Incidentally, what happens when I choose the Fedora boot from the boot menu is that it simply boots up to a Grub> prompt and doesn't apparently load much more than that. Among the Grub commands it informed me I could use was Boot, so I tried that but got a message back saying Kernel wasn't loaded. When I tried Kernel, it wanted a path name.
Any help would be greatly appreciated. Thanks.
Mike
I'm trying to add Fedora 16 to a Dell Precision M6500 laptop that already has Windows 7 64-bit installed. I had forseen the need to do this and left some free disk space on one of my three internal drives (2 solid state and one SATA). The Fedora 16 installation goes off without a hitch and is clearly installing about 1225 packages that include the Windowing system I requested. I chose to do a Custom Layout and set up an 8GB swap partition and a 180GB ext4 partition for Fedora 16. After installing the Fedora distro, I went back into Windows and used Easy BCD to set up the dual boot menu. I chose grub2 for the linux entry I added, but was not able to specify the partition information (it informed me it would be automatically configured). It has produced the following entries, which I suspect is wrong:
Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device partition=\Device\HarddiskVolume2
description Windows Boot Manager
locale en-US
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {079b397c-5494-11e0-a713-a409df4d3db0}
resumeobject {079b397b-5494-11e0-a713-a409df4d3db0}
displayorder {079b397c-5494-11e0-a713-a409df4d3db0}
{079b398a-5494-11e0-a713-a409df4d3db0}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 30
displaybootmenu Yes
Windows Boot Loader
-------------------
identifier {079b397c-5494-11e0-a713-a409df4d3db0}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence {079b397d-5494-11e0-a713-a409df4d3db0}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {079b397b-5494-11e0-a713-a409df4d3db0}
nx OptIn
Real-mode Boot Sector
---------------------
identifier {079b398a-5494-11e0-a713-a409df4d3db0}
device partition=C:
path \NST\AutoNeoGrub0.mbr
description Fedora 16 Linux
In particular,I suspect the path in the Fedora 16 entry because during Fedora installation I chose not to use a master boot record, but to place the loader on the first sector of the drive. I'm a total Linux newbie (this is absolutely my first time dealing with it at all), so I of course could be wrong about all of this. But wondering has any ideas on how I can diagnose this problem and fix it.
Incidentally, what happens when I choose the Fedora boot from the boot menu is that it simply boots up to a Grub> prompt and doesn't apparently load much more than that. Among the Grub commands it informed me I could use was Boot, so I tried that but got a message back saying Kernel wasn't loaded. When I tried Kernel, it wanted a path name.
Any help would be greatly appreciated. Thanks.
Mike