nuked bios when adding key(s)

[xioren]

Describe the bug

After installing and restarting, got trough bios and grub and then was met only with a black screen. I waited to see if anything would happen and after several minutes it rebooted back to bios and showed a message about writing or adding keys; I waited. It then rebooted again and at that point just booted to a black screen, no bios. This is where I am at now, bios is corrupted and pc is not bootable.

What did you expect to happen?

I expected Bazzite not to brick my pc.

Output of rpm-ostree status

n/a

Hardware

Venus series (Ryzen 9 7940HS)

Extra information or context

No response

[KyleGospo]

Did you install a deck or desktop image?

Asking to clarify if you might be seeing game mode failing to launch. We do not touch your BIOS, and MOK enrollment is a standard feature provided by your BIOS. No part of the enrollment UI is Bazzite, and our job is done after the key is handed off for potential enrollment.

[xioren]

I used the desktop image. I have (had) secure boot turned off anyway so its not even necessary to mess with enrolling keys. Maybe give the user an option to skip it? It happened automatically for me. Luckily I was able to reset CMOS and boot but It does not seem like I will be able to use Bazzite.

[KyleGospo]

The key is passworded, during MOK enrollment you have to enter the phrase in our readme, or you can hit continue to skip enrollment.

Any failure in the key itself or in decrypting it would result in skipping enrollment.

[KyleGospo]

The key is passworded, during MOK enrollment you have to enter the phrase in our readme, or you can hit continue to skip enrollment.

Any failure in the key itself or in decrypting it would result in skipping enrollment.

[xioren]

Right what I am saying is this all happened with no input from me. It was black screen --> BIOS writing keys --> brick.

[KyleGospo]

I'm sorry but I'm very not sure what's going on here. What you're describing would be a failure by your motherboard manufacturer, and not something we could fix.

[xioren]

Alright, I will close the issue.

[KyleGospo]

In the meantime if you're still willing to give this a try here's a workaround:

The key enrollment is kicked off by our ISO. You can instead install stock Fedora Kinoite or Silverblue and then rebase to Bazzite with the instructions from the website. At no point during that process will a secure boot key attempt to be enrolled.