Hello, I’m using Fedora 43. Using version 42, I wanted to see how a program works under VirtualBox. The installer instructed me to install MOKITL. Of course, I entered the password I had written down in my notes, and unfortunately, the notes got lost. I wanted to uninstall the entire secure boot environment. I disabled secure boot in the BIOS. Even though I disconnected the hard drive, the MOK listing, etc., still appears. I tried uninstalling from the Fedora system, but I don’t have the Mokitl password. What can I do to go back to the way it was before installing VirtualBox?
That is a bios screen that shows up for me every time I boot/reboot.
You probably don’t want to modify anything in bios simply for that reason.
However, you ** might** be able to eliminate it if you were to enter the bios setup and reset everything to factory default. I won’t even try that since I use nvidia and VirtualBox and there is a signing key required to allow the kernel to load the modules for both. (I do use secure boot). That key would be removed by performing a factory reset of bios.
When I installed the nvidia drivers and VirtualBox I did so as rpm from the rpmfusion repos. Those packages pull in all necessary dependencies during the initial installation.
I have never seen instructions that said that, but you did not say where you obtained VB so I cannot check the instructions for validity.
1 Like
I had it disabled in the BIOS (HP 15s-fq2032nw i5-1135G7) to factory settings and I disabled safe boot and disconnected the hard drive and still this listing is shown
Install Mokutil was after the error signaled by VB
What error? I did not see an error reported by VB except you said
As I noted, that scrolling on the screen is from bios before the system even reaches grub and fedora even starts booting.
Whatever the fix is, and I don’t have a clue, would be bios related and not fedora related (although it may have been triggered by use of mokutil – possibly by performing the import of the signing key into bios). My system has been doing that, as have others I am aware off, for probably at least 2 years.
This error was shown by VB when I tried to run the emulated system. It was information related to the kernel. I don’t remember exactly, so after the failure with VB, I gave up on further VB installations (I prefer Boxes). (I remembered that it was a command related to mokutil, then there were blue screens confirming it, so how can I remove the key signature from the BIOS? I want to change the SSD drive to another one, so I would like to remove this signature to avoid complications when starting other systems, e.g. from USB.)
As Jeff said, a ‘factory restore’ might do it.
Also somtimes there is a hard reset button, and the only other alternative is a BIOS flash.
To be more precise: it is from the shim as found at https://github.com/rhboot/shim/blob/main/mok.c.
If shim detects a mok request it will invoke the mmx64.efi program which runs the blue dialog.
mokutil has an option --revoke-import to cancel an import request, and you can run mokutil --help to see the available commands.
1 Like