# Secure Boot Notice

**URL:** <https://universal-blue.discourse.group/t/secure-boot-notice/405>\
**Category:** Bazzite\
**Tags:** announcements\
**Created:** [January 11, 2024, 5:05am UTC](https://universal-blue.discourse.group/t/secure-boot-notice/405 "2024-01-11T05:05:10Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![TriMoon](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/trimoon/32/589_2.png) [@TriMoon](https://universal-blue.discourse.group/u/TriMoon)\
**Post date:** [January 15, 2024, 1:12pm UTC](https://universal-blue.discourse.group/t/secure-boot-notice/405/7 "2024-01-15T13:12:44Z")

</div>

Hi, just some feedback from me.  
(Fresh user on here AND Fedora)

After a lot of strugling with the “Universal Blue” network installer in SecureBoot via Ventoy, which needed the TPM to be disabled:

1. Completely unable to start the installer via.Ventoy, I had to write the uBlue iso to an USB stick and boot off of that.
2. I choose the Kionite with latest nVidia drivers, which at last installed.  
_(You guys really need a progress bar that shows progress while downloading 😉)_
3. I completed the install with the reboots for the MOK enrolment successfully.
4. And now comes the **BUG** …

The nVidia drivers were REJECTED due to missing keys in the MOK…  
I checked the enrolled keys and noticed 2 new keys, BOTH of these keys were added as a single MOK enrollment:

1. The key for akmods.
2. Some key with just numbers as CN.

So with some knowledge from my past reading on the subject, i thought Hell why not check the key on the running system:

```auto
sudo mokutil --test-key /etc/pki/akmods/certs/akmods-ublue.der

```

Which revealed that it was NOT enrolled, so it must be a different one as the one enrolled by the installer.  
So out of curiosity i enrolled the above key using:

```auto
sudo mokutil --import /etc/pki/akmods/certs/akmods-ublue.der

```

And what ya guess, after a reboot to complete the enrollment, the nVidia driver was accepted…  
Although I see the below errors, a few times, in `dmesg` output:

```auto
[drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset. Error code: -22
[drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0

```

These get repeated when the screensaver kicks in and the user returns to the display…

---

_[View the full topic](https://universal-blue.discourse.group/t/secure-boot-notice/405)._