I recall odd examples from various models including an admin password needing to be set before secure boot could be disabled.
Indeed, after I set an admin password I could de-activate the secure boot mode. Thus I could set UEFI boot mode without secure boot. With these settings I booted Manjaro from the stick and invoked the Manjaro installallation program. The result is a Manjaro system on my hard disk that - hopefully - boots in UEFI mode. How can I verify that?
I remove the Manjaro stick, reboot my PC with interruption of the boot process. I set boot mode from UEFI to legacy. This results in an error, where no GRUB menu appears and neither Windows nor Manjaro can be booted.
Reboot. Again I interrupt the boot process, set Boot mode to UEFI (secure boot disabled). No GRUB menu appears. The PC boots into windows - there is no choice.
After login to Windows I can invoke the âSettingsâ > âWindows recoveryâ > ⌠> âuse deviceâ > âManjaroâ
Now the PC reboots and the GRUB menu appears. I can choose and boot Manjaro. Finally!
From that process I conclude that Manjaro is now installed in EFI mode. Is my conclusion correct?
I log into Manjaro. I run grub-instal to /dev/sda, I run grub-mkconfig -o /boot/grub/grub.cfg
Reboot. Again (boot mode UEFI) Windows is booting, i.e. grub-mkconfig did not yield the desired resultâŚ
So what can I do in order to see the GRUB menu BEFORE Windows boots?
Ubuntu supports Secure Boot out of the box.
Arch/Manjaro can support it ⌠but you must use self-signed keys, etc.
The output of this command usually indicates that the OS is currently booted using UEFI, while the absence of any output is typically indicative of a legacy boot.
To start with, set the boot priority in your BIOS. Make sure that the disk containing Manjaro (with the Grub boot loader) is set as the first boot entry. Save the BIOS, and reboot.
If you still have difficulty, there are other steps to consider.
Itâs difficult to progress without knowing whether Manjaro is actually installed in UEFI mode or not.
Did you recreate the Manjaro Installer USB to ensure that it boots in UEFI mode? The methods to do this vary depending on the method you used to create the USB.
Did you subsequently install Manjaro in UEFI mode? Complications may arise if you failed to prepare your disk with a GUID partition table (GPT). In Calamares, before you choose a partitioning method, whether the disk and system is configured as UEFI (or not) is noted at the top of the screen (if you see MBR then itâs not UEFI).
If your BIOS also allows Legacy booting (i.e., CSM is enabled in a UEFI BIOS) this procedure can allow you to boot to Grub whether Manjaro is installed as UEFI or Legacy (but, after a forced reboot). So, this conclusion is indeterminate.
My assumption is that Manjaro is still booting as MBR.
Please boot to the Live environment of the Manjaro Installer USB, and follow relevant instructions in the following guide:
Only follow directions intended for a EFI/GPT system. Naturally, the instructions rely on booting as UEFI; refer to information given in the previous thread; each OS must boot as UEFI.
Aside:- I wrote a general guide to multibooting Windows and Manjaro some time ago; Iâll link this here as it includes information which will also be beneficial (without actually following the guide).
Yes, both of these comments are true, but are irrelevant to the issue at hand as Manjaro (by default) does not support Secure Boot, and thusly it should be disabled before installing Manjaro.
Note that disabling Secure Boot at the BIOS level (as you have done) is preferable to any mechanism Windows might offer.
This appears that it might be a Windows generated screen; I canât see with your eyes, so itâs difficult to be sure.
Changing the boot priority in BIOS to have Manjaro (or possibly âLinux OSâ) appear first in the relevant section of the BIOS should ensure that Manjaroâs Grub UEFI bootloader boots first (which would then list Windows as an option).
If the Manjaro entry in BIOS is somehow missing, this can often be solved by following a guide such as Restore the GRUB bootloader (above).
In the previous thread you mentioned:
Is this still the case now?
Yes â Manjaro is likely (still) booting in Legacy mode.
No â Please show us exactly what you see.
If both Windows and Manjaro are installed using UEFI mode (no CSM) then the $ESP should contain these (top level) directories:
[ESP] -- BOOT
Manjaro
Microsoft
If the âManjaroâ directory doesnât exist in the ESP, the likelihood is high that your installation remains as a msdos/mbr based installation.
Again, as before, each OS and the installation media must all be the same type; either UEFI/GPT or MSDOS/MBR (legacy). From what you have shown, Windows boots as UEFI/GPT, but for some reason Manjaro is not.
You ask us to please explain;
Perhaps itâs time for show and tell:
1. Please show us some system information; Boot to the Manjaro Live envionment of your Manjaro Installer USB, and provide the output of:
2. Boot into your system BIOS firmware and show us your settings â specifically for Secure Boot, UEFI and Legacy/CSM and Boot Priority. Use a camera, if needed, and post clearly images.
This makes no sense at all if you installed both Windoof and Manjaro in UEFI mode.
Because your firmware still looked to the ESP set by Windoof.
This is not the recommended procedure. You should have manjaro-chrooted into Manjaro and restore the boot loader for UEFI installs.
Wrong command. Ever looked for the wiki how to restore the boot loader? Itâs so easy to find Iâm not leaving the link here, you need to learn how to do your homework.
No, Manjaro is not supporting SB. Making it possible is not the same as supporting it.
The refind-install command can be used to automatically install rEFInd (the EFI partition may need to be mounted for this to work). See the Arch wiki for more details.