This error is not a result of SecureBoot being supported or not. Why is
shim unable to write to an nvram variable at runtime? That looks like a
problem with the firmware's UEFI implementation.
I believe we also should only be setting MokListRT, if MokList is also
set. Were you prompted to enroll a MOK key on this system (unfriendly
blue screen), and did you do so?
The most likely cause for Ubuntu to prompt to you to enroll MOK is if
you have nvidia driver packages installed; but your bug report shows
that you are using nouveau drivers and there is no nvidia kernel module
loaded. Did you previously try to install the nvidia binary drivers?
** Changed in: shim (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Invalid
** Changed in: mokutil (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867092
Title:
Failed to set MokListRT: Invalid Parameter
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867092/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
