Bug 16274 - ASUS M51AD/Win8.1 doesn't allow disabling Secure Boot
Summary: ASUS M51AD/Win8.1 doesn't allow disabling Secure Boot
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: 5
Hardware: i586 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-02 15:38 CEST by Jim Rawlings
Modified: 2015-07-02 15:43 CEST (History)
0 users

See Also:
Source RPM: MAGEAI-5-x86_64-DVD
CVE:
Status comment:


Attachments

Description Jim Rawlings 2015-07-02 15:38:00 CEST
Description of problem:
I am trying to install Mageia 5 in a dual boot mode with Windows 8.1 from the above DVD image. When the DVD loads, it goes directly to the NON-UEFI installer. I have followed the instructions to set the appropriate options in the UEFI definitions for the ASUS motherboard.
The option to disable Secure Boot is not available. It is "greyed out" and cannot be changed. I've created and Admin password and used it to access the setting with no change. 
Is there a way to get around this as it seems to be a show stopper for the installation?

Version-Release number of selected component (if applicable):

Mageai 5
How reproducible:

Happens every time.

Steps to Reproduce:
1. At the power on prompt, hit the F2 key to access the UEFI settings.
2. Go to the BOOT options.
3. Select Secure Boot.
4. OS Type is the only option available. (Set to Other OS by me on an early attempt to perform the install).
5. Hit F10 to save and exit
6. The 'traditional' installer is displayed - function keys at the bottom - with options to:
Boot Mageia 5
Install Mageia 5
Boot from Hard Disk.

Reproducible: 

Steps to Reproduce:
Comment 1 Samuel Verschelde 2015-07-02 15:43:43 CEST
Hi,

The current generation of computers must give a way to disable secure boot, so I advise to refer to your manufacturer's documentation. You might get help on our forums too. I'm confident that a solution can be found. I have myself had similar trouble (but not exactly the same) at an install party.

Since it isn't a bug in Mageia, the bugtracker is not the proper place for getting help, therefore I close it as invalid.

Status: NEW => RESOLVED
Resolution: (none) => INVALID


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