Created attachment 582784 [details] Several informations Description of problem: When i select the Windows 7 entry generated by Grub in the Grub menu at start up, i get a blinking cursor at the top left of the screen. Windows 7 is not loading. Version-Release number of selected component (if applicable):(GRUB) 2.00~beta4 - Fedora release 17 x64 - Windows 7 Ultimate How reproducible: Always Steps to Reproduce: 1.Install Fedora 17 on first disk (sda). 2.Have a Windows seven installed on a second disk (sdb). 3.Choose the Windows entry in the Grub menu at start up. Actual results: blinking cursor at the top left of the screen Expected results: load Windows seven Additional info: Windows is loading when i change the boot order in bios setup. Dual boot was working with Fedora 16.
*** Bug 819651 has been marked as a duplicate of this bug. ***
The short story: /dev/sdb1: UUID="1BF579B227473E24" TYPE="ntfs" ### BEGIN /etc/grub.d/30_os-prober ### menuentry "Windows 7 (loader) (on /dev/sdb1)" --class windows --class os { insmod part_msdos insmod ntfs set root='(hd1,msdos1)' search --no-floppy --fs-uuid --set=root 1BF579B227473E24 chainloader +1 } ### END /etc/grub.d/30_os-prober ### What boot loader entry worked for dual boot with f16? (I assume it is a windows limitation that it don't like being placed on a secondary drive without knowing it. Booting it might thus require some http://www.gnu.org/software/grub/manual/grub.html#drivemap tweaks. I doubt os-prober / grub2-mkconfig in general can know what is required.)
Unfortunately, I don't have the grub.conf from Fedora 16 anymore ! I just can tell you that I didn't change anything in what was generated by Grub for the Windows entry. I add this entry with device map : menuentry 'Windows_2 (loader) (on /dev/sdb1)' --class windows --class os $menuentry_id_option 'osprober-chain-1BF579B227473E24' { insmod part_msdos insmod ntfs set root='hd1,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 --hint='hd1,msdos1' 1BF579B227473E24 else search --no-floppy --fs-uuid --set=root 1BF579B227473E24 fi drivemap -s (hd0) (hd1) chainloader +1 } but Windows doesn't start at all.
Well ... nothing can be done here without an example of how the menu entry should look like ... or a specific example of some other boot loader that can boot windows in a setup where grub2 can't work. Some 'parttool' tweaking might apparently also be needed in order to please windows.
Problem resolved with the Grub update : grub2.x86_64 1:2.0-0.25.beta4.fc17 @updates-testing. Here is Grub.conf entry generated by Grub : ### BEGIN /etc/grub.d/30_os-prober ### menuentry 'Windows 7 (loader) (sur /dev/sdb1)' --class windows --class os $menuentry_id_option 'osprober-chain-1BF579B227473E24' { insmod part_msdos insmod ntfs set root='hd1,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 --hint='hd1,msdos1' 1BF579B227473E24 else search --no-floppy --fs-uuid --set=root 1BF579B227473E24 fi chainloader +1 } ### END /etc/grub.d/30_os-prober ### Windows is now loading when I choose the entry in Grub menu.
Strange. Nothing important has changed between the first beta4 package to 0.25. But if it works for you we will close it.