I’ve installed Bazzite on the same MoBo with secure boot disabled and it installed fine. After Bazzite was installed for some time I did a ASUS UEFI update. And by doing so, ASUS decided to take away disabling secure boot and only have it on all the time.
I’ve did a clean install of Bazzite legacy with the new UEFI and now Bazzite won’t install. I’ve tried Windows UEFI and Other OS ‘standard and custom’. And get a fail in the middle of installing.
Bazzite please fix the 10xx KDE issue. I’m dead in the water right now.
Installing with Bazzite NVIDIA 10xx KDE.
Also, Bazzite NVIDIA 10xx live KDE will boot into a blank screen but it’s not locked up because Control, Alt, Delete work.
Not being able to disable Secureboot seems like a load of utter crap, I would roll back to the previous BIOS, or throw that pile of Microsoft endowed POS in the trash, these manufacturers are getting worse with pushing this garbage on to us, make sure you post exactly what motherboard you have and what Bios version you just flashed it to, so others can take warning.
There are ways of getting secureboot functioning, but not sure if it works with the nVidia based image, Ive only had it working with all Intel systems, have you tried messing with the settings in the secureboot section?
Are you able to switch to legacy boot mode? Probably called compatibility mode or something like that.
Out of curiosity, the methods in the link don’t work?
EDIT: In this case:
Method B - After Installation Method¶
Disable Secure Boot in the BIOS before proceeding, and then re-enable it after enrolling the key.
If you have already installed Bazzite then enter this command in a host terminal:
ujust enroll-secure-boot-key
If prompted to enroll the required key, then enter the password in the host terminal:
universalblue
You can now turn Secure Boot back on in the BIOS.
Use the following command to boot straight into your system’s BIOS (if supported):
ujust bios
Complete MOK enrollment at boot¶
On the next boot, you will see the blue MokManager screen:
-
Choose Enroll MOK.
-
When prompted for a password, enter:
universalblue
After the reboot, the key is enrolled and Secure Boot can remain enabled. Your system should now boot normally under Secure Boot.
I agree hole heartily and Microsoft has a strangle hold on are PCs.
I can’t roll back.
I did find out that enabling CSM got me to install and after Enrolling MOK I restarted one last time and disabled the CSM and now I’m booting into Secure Mode.
I said before I could not disable Secure Boot.
Enabling CSM made it so I can install the OS and the disable CSM to use Secure boot after installing.
“Its for your security”
For all jokes this is likely just a lazy UEFI implementation.
Motherboard Company’s when making a motherboard purchase the source code to AMI or insyde. which are companys that make UEFI implementations, and then add once they get the source code motherboard companys add their own vendor stuff to the perfectly good system like custom “RGB GAMER MENUS” and stuff.. Alot of times vendors will lazily do stuff like not allowing you to disable secureboot because “Oh well.. why would you want to do that”… And alot of motherboards(gigabyte cough cough) do alot of hacks and tricks that I wont bore you with.. This is likely just a case of incompetence.
