Description of problem:I just installed Mageia with a KDE4 & GNOME setup using 3.3.8-desktop-2.mga2 as kernel. In GRUB, when I press Enter to boot (what should be a working Windows 8-session) Windows automatically tries to repair itself, but fails & reboots the computer. Trying to boot Windows only gets you to the repair-stage again. Version-Release number of selected component (if applicable): 0.97 How reproducible: I have managed to reproduce this all the time. Steps to Reproduce: 1. Install Windows 8 Release Preview-version. 2. Update Windows 8 to the fullest. 3. Now, burn the Mageia 2-iso to a USB-stick & start to install Mageia. 4. Delete (or uncheck) boxes for all the Testing-medias. 5. Update Mageia. 6. Boot to GRUB-menu entries & choose Windows in the list of OS'es to boot. 7. Windows will now instead of booting the environment go to repair-mode.
Created attachment 2800 [details] Here's the freshly made RESULTS.txt made by the bootscript.
Created attachment 2801 [details] Here's the list of all my medias
CC: (none) => kristoffer.grundstrom1983
Priority: Normal => HighTarget Milestone: --- => Mageia 3
Hardware: All => x86_64
Summary: Windows 8 fails too boot from GRUB => Windows 8 fails to boot from GRUB
Does the same happen with Mageia 3 alpha 1 Kristoffer ?
As root edit the following line in the last section of /boot/grub/menu.lst from: root (hd0,0) to root (hd1,0) See how that goes.
CC: (none) => zen25000
That didn't work so I changed it to this after reading a Fedora-thread related to same issue with Windows 7: title Windows 8 rootnoverify (hd1,0) makeactive map (hd0) (hd1) map (hd1) (hd0) chainloader +1
I really not see how we (as a distribution) or grub is responsible of such bugs in windows...
OK. Removing any word related to GRUB.....
Summary: Windows 8 fails to boot from GRUB => Windows 8 fails to boot in Mageia 2Source RPM: grub => (none)
yeah, more funnier than before \o/
Severity: critical => normal
(In reply to comment #8) > yeah, more funnier than before \o/ (In reply to comment #1) > Created attachment 2800 [details] > Here's the freshly made RESULTS.txt made by the bootscript. You're welcome to change the title.
(In reply to comment #5) > That didn't work so I changed it to this after reading a Fedora-thread related > to same issue with Windows 7: > > title Windows 8 > rootnoverify (hd1,0) > makeactive > map (hd0) (hd1) > map (hd1) (hd0) > chainloader +1 So that works now does it?
(In reply to comment #10) > (In reply to comment #5) > > That didn't work so I changed it to this after reading a Fedora-thread related > > to same issue with Windows 7: > > > > title Windows 8 > > rootnoverify (hd1,0) > > makeactive > > map (hd0) (hd1) > > map (hd1) (hd0) > > chainloader +1 > > So that works now does it? Nope.
You might try moving the makeactive to the bottom so it's the last command - I'm not over optitmistic, but I suspect it at least needs to be after the mapping (sorry I forgot about the mapping earlier).
(In reply to comment #12) > You might try moving the makeactive to the bottom so it's the last command - > I'm not over optitmistic, but I suspect it at least needs to be after the > mapping (sorry I forgot about the mapping earlier). No luck there either.
If I was in this situation I would now:- 1. Repair Windows so it boots directly as though Mageia was not installed. 2. Using a SuperGrub CD (not SuperGrub2) boot into Mageia. http://prdownload.berlios.de/supergrub/super_grub_disk_0.9799.iso 3. Run bootinfoscript and rename RESULTS.txt as RESULTS_win.txt 3. Go to the Boot section of mcc and re-install the Mageia bootloader to MBR. 4. Run bootinfoscript again. 5. Try to boot Windows 6. If it fails attach RESULTS.txt and RESULTS_win.txt here. It may show something useful.
(In reply to comment #14) > If I was in this situation I would now:- > 1. Repair Windows so it boots directly as though Mageia was not installed. > 2. Using a SuperGrub CD (not SuperGrub2) boot into Mageia. > http://prdownload.berlios.de/supergrub/super_grub_disk_0.9799.iso > 3. Run bootinfoscript and rename RESULTS.txt as RESULTS_win.txt > 3. Go to the Boot section of mcc and re-install the Mageia bootloader to MBR. > 4. Run bootinfoscript again. > 5. Try to boot Windows > 6. If it fails attach RESULTS.txt and RESULTS_win.txt here. > > It may show something useful. Repair Windows, HOW? The repair that Windows tries to perform doesn't do the trick as well as using the Rescue-mode reinstallation of Windows Bootloader. I could try that thou.
Does your mother board support UEFI? http://www.readwriteweb.com/enterprise/2012/05/top-10-windows-8-features-6-secure-boot.php
(In reply to comment #16) > Does your mother board support UEFI? > http://www.readwriteweb.com/enterprise/2012/05/top-10-windows-8-features-6-secure-boot.php Well, I don't know how up-to-date this page is, but I can't find any information about Secure Boot for it: http://www.asrock.com/mb/Intel/G31M-S/ Here are the updates for its BIOS: http://www.asrock.com/mb/Intel/G31M-S/?cat=Download&os=BIOS
Looks like regular PC-bios so I have no idea why it fails. What does ls show at the grub2 rescue shell? You could do it the other way round:- Re-install Windows Check it works Boot Mageia (SuperGrub disk) and install grub bootloader to the root partition NOT the MBR. Use BCD-Edit in Windows to add Mageia to the Win bootloader (Chainload into root of Mageia).
(In reply to comment #5) > That didn't work so I changed it to this after reading a Fedora-thread related > to same issue with Windows 7: > > title Windows 8 > rootnoverify (hd1,0) > makeactive > map (hd0) (hd1) > map (hd1) (hd0) > chainloader +1 in my /boot/grub/menu.lst i have the following for windows 7: title windows root (hd0,1) chainloader +1 so no makeactive. and iirc the guy who gives my thoses lines saids 'makeactive' was for windows < 7 my 2 cents
CC: (none) => grenoya
I can now update this bug & tell you that I see this issue even if I install Windows XP 32-bits.
Uefi and secure boot needs windows digital key and there is one problem,windows default keys won't boot linux so you have two choise one is you turn off secure boot or wait that mageia will buy own digital key from microsoft to support multiboot with windows and linux. It's explained in this page. http://news.cnet.com/8301-10805_3-20111545-75/microsoft-addresses-windows-8-secure-boot-issue/
CC: (none) => ozkyster
I have read all the comments and failed to see how it is supposed to be a Mageia bug, so closing.
Status: NEW => RESOLVEDCC: (none) => stormiResolution: (none) => INVALID