Score:0

Secure boot inconsistent behavior

cn flag

I have two systems with 20.04 LTS. Secure boot is enabled on both. The behavior of the two systems is different, and I have not idea why.

System 1: Asks for a new secure boot password on each kernel update (I assume it's new, since it asks for a re-type). Why?

System 2: Never asks for anything on kernel update. Running 'mokutil --sb-state' indicates SecureBoot is enabled.

Why the difference, and how should it act?

oldfred avatar
cn flag
Does one system have a proprietary video or Wi-Fi driver? Ubuntu cannot sign proprietary drivers. So you as use have to sign the driver. Did you install driver from Ubuntu repository?
MZ_Guy avatar
cn flag
@oldfred Yes indeed it does. That explains it. I'm using proprietary AMD-Pro drivers. Is there a way to sign to enable secure boot?
oldfred avatar
cn flag
I do not use proprietary drivers, not currently use UEFI Secure Boot. https://wiki.ubuntu.com/UEFI/SecureBoot/DKMS If you have Secure Boot on, I thought it asked you to assign a MOK - machine owner key. Or then you are signing that the Software blob is Secure as Ubuntu cannot verify third party software, but a user can.
I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.