| Summary: | mga2 boot menu fails to dual boot Windows 7 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Kristoffer Grundström <lovaren> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | lovaren, zen25000 |
| Version: | 2 | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Attachments: |
lshw
Installation-log from installing Mageia 2 Result of the bootinfoscript |
||
|
Description
Kristoffer Grundström
2012-06-10 22:07:06 CEST
Created attachment 2446 [details]
lshw
Here's info about my hardware in this desktop-PC.
Installed kernel is: 3.3.6-desktop-2.mga2 Created attachment 2447 [details]
Installation-log from installing Mageia 2
Kristoffer Grundström
2012-06-10 22:24:53 CEST
CC:
(none) =>
kristoffer.grundstrom1983 Created attachment 2448 [details]
Result of the bootinfoscript
According to BootInfoScript output, sda2 is marked bootable and is obviously drive C, but bootmgr is on sda1. So please try this: title windows rootnoverify (hd0,0) chainloader +1 makeactive I have seen the order of the makeactive/chainloader commands make a difference in the past. CC:
(none) =>
zen25000
Barry Jackson
2012-06-10 23:02:43 CEST
Hardware:
i586 =>
x86_64
Manuel Hiebel
2012-06-25 04:37:46 CEST
Keywords:
(none) =>
NEEDINFO I don't see this issue anymore. Strange behaviour, really. closing then Status:
NEW =>
RESOLVED |