Suddenly getting mok.c dump on every boot just before the grub menu

您所在的位置:网站首页 显示歌词好不好 Suddenly getting mok.c dump on every boot just before the grub menu

Suddenly getting mok.c dump on every boot just before the grub menu

2024-02-14 03:21| 来源: 网络整理| 查看: 265

Ever since I cleared secure boot keys from the BIOS menu I’m getting this lines of output/log dump/whatever it is called on every boot. This shows up right before it enters grub menu.

3b6fe33d77c5c8c8d930a933d08dc68567f5d131.jpeg 3b6fe33d77c5c8c8d930a933d08dc68567f5d131.jpeg1334×750 174 KB

This is on Fedora 36. I’ve been using secure boot for a while with a wifi driver module key enrolled in the MOK list. This has been my first time handling MOK key enrollment. Yesterday I did a reinstall, just switching out different Spin, but after a clean reinstall I was surprised to find out from “mokutil --list-enrolled” that the MOK key from previous installation was still there. So I ran “mokutil --export” so that I can remove it from the MOK list, but it gave me “MokListRT is empty” and no key was exported. At that time I didn’t know about “mokutil --reset” and I remembered that there’s an option to clear secure boot keys on the BIOS menu itself. Ever since I did that I keep getting this lines talking about mok.c just before the grub menu. It’s pretty long but it goes away very quickly.

Here is the video.

Sorry if it’s hard to see with all the white smearing on my screen.

Also now everytime I boot without secure boot enabled I also get this “secure boot is not enabled” screen.

Link to the photo since I’m new user

Based on what I can read from that dump it seems like there’s no error. I can boot into Fedora just fine, but I’m worried that it will be an issue later because so far I still can’t export any MOK key. Even after I did “mokutil --reset”, where it finally removed my akmods key from MOK list, I still get “MokListRT is empty” message.



【本文地址】


今日新闻


推荐新闻


CopyRight 2018-2019 办公设备维修网 版权所有 豫ICP备15022753号-3