Bug 812026 - Windows 8 Preview & Fedora 17 Alpha: "BOOTMGR is missing"
Summary: Windows 8 Preview & Fedora 17 Alpha: "BOOTMGR is missing"
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: 17
Hardware: i686
OS: Windows
unspecified
urgent
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-12 14:53 UTC by ng0177
Modified: 2012-04-16 16:10 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-04-16 16:10:46 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description ng0177 2012-04-12 14:53:07 UTC
Hi, on a laptop:

Windows 8 preview on the IDE HDD and

Fedora 17 Alpha on the USB HDD 2nd partition (boot)

have installed successfully. However, I am getting the message "BOOTMGR is missing" when swichting with F12 during boot to Fedora (Windows starts up fine).

I am almost there and not too savy i.e. a straightfoward fix is appreciated.

Thank you!

Comment 1 Bill Nottingham 2012-04-12 15:25:07 UTC
Moving to grub2, as a starting point for people versed in debugging these issues.

Comment 2 ng0177 2012-04-16 16:10:46 UTC
The problem turned out not to be related to booting but is of general nature:

Installation of Fedora17 Alpha on a laptop:

A LiveUSB had to be burned with a litte tool, the CD never worked (Windows7/8 burning is very confusing).

The BIOS had to be changed to accept USB as a boot option

F12 needed to pressed during start up

F17A hangs during installation during formatting ext4 file systems waiting for probably non-existent drives. Alt-F4 interrupts and re-continues with the installation.

F17A is dead slow and gives a wrong impression for the dead fast F16 64-bit performance.

F17A has Gnome 3.3 and fixes a problem with adjusting the screen brightness and should be considered as an update for F16!

I am impressed overall with F16 and glad to have switched.


Note You need to log in before you can comment on or make changes to this bug.