Since the latest update of the system (witch was proposed by Zorin OS) My discrete gpu passed to vga with no acceleration. Apparently this is due to nvidia drivers being updated with secureboot: the mok key is broken. This isnt normal since i just follow the steps when Zorin ask me to update the system. This mean we have a problem with secureboot cerftificate and Zorin.
Did i have to go return to another distrib ? Like Cachy OS ?
Do you have dual boot ?
Did you try to boot to older kernel ?
I have no dualboot. I dont want to load amother kernel...
Do what you want
Nourpon. Thanks for answearing.
It would help to check if it might be related to the current Kernel or not.
Because You get the MOK Key, I guess Secure Boot is enabled on Your System, right? You could disable it.
Thanks. There is a différence betwen the keys in the firmware and Zorin os. The geforce 580 driver mok key. Those have become wrong with latest update. So no more accélération...
Software (kernel) Updates have reportedly been somewhat problematic to some users of late.
So why not boot previous kernel as has been previously suggested, at least as a test.
It is an easy thing to do via grub menu> Additional Options for Zorin.
But we can't force you to do that.
I think this has to do with nvidia drivers. Since the operating system works fine. Only no acceleration.
I ran in to something similar with an update and MOK
NVIDIA + Secure Boot + MOK fix on Zorin
If your NVIDIA driver is installed but nvidia-smi says it can't communicate with the driver, and Secure Boot is enabled , check whether the NVIDIA kernel module is being blocked because the MOK key hasn't been enrolled.
You can check for the key with:
ls -l /var/lib/shim-signed/mok/MOK.der
If it exists, reboot and enter the MOK Manager when the blue screen appears:
Enroll MOK → Continue → Yes → enter your password
Then reboot normally and check:
nvidia-smi
If the NVIDIA driver loads correctly, you should see your GPU and driver information.
Don't disable Secure Boot just to get NVIDIA working — enrolling the MOK keeps Secure Boot enabled and allows the signed NVIDIA module to load.
1 Like
This isn't easy as you're saying because there is no blue screen like in setup. Just a broken Nvidia drivers proprietary check. I have enough. Perhaps this problem may be solved be disabling secureboot. But at this stade Zorin OS team should not say it is compatible with secureboot. Thanks.
1 Like
Nvidia has always had a problem with secure boot on. in the past when i had my nvidia 3050 i always had that off secure boot dont really give that much more security. but it is your machine I got away from Nvida with an amd RX 6600XT but that was my choice
Did You tried it with a Reinstall of the Driver? I would suggest the folowing way:
-
Uninstall the current Nvidia Drivers with:
sudo apt purge nvidia* libnvidia* -
Then do a
sudo apt autoremove
to remove File Rests. But check the List before You remove the Packages. -
To install the Driver again type
sudo apt install nvidia-driver-580 nvidia-dkms-580
1 Like
So. Zorin Os: could we know wheter secure boot on is compatible with Zorin. Or not ? I would realy like an answer...
Perhaps the problems are because of the A.I. commands of your other thread.
It is not so good to mix the hwe and ga kernel stack when you use proprietary nvidia drivers. I don't know if you have entered all commands of Swarfendor's post which is marked as solution and I'm not sure if it makes the issues now, but I would remove the linux-generic package (only the linux-generic one, not the linux-generic-hwe-24.04) and all 6.8 kernels from the ga stack and then remove the nvidia drivers and reinstall them as Ponce-De-Leon showed you.
Although you can use Secure Boot with Zorin, you should expect to encounter more problems.
2 Likes
I did see an online video tutorial awhile back where someone showed how to install Ubuntu while Secure boot disabled then re-enabled after install. Don't know if that wuould work with Zorin.
1 Like
That's why many distros suggest to disable it with nvidia drivers, and/or just also because secure boot is totally useless with linux and it cause problems
2 Likes
Thought I would take a look at Phoronix and stumbled on this interesting article:
https://www.phoronix.com/news/Ubuntu-26.10-Lighter-GRUB
Ubuntu with 26.10 is stripping out alternative File Systems (zfs, Btrfs, XFS, plus LUKS, LVM and RAID (but not RAID1). Anyone not wanting the options removed would have to use the non-signed GRUB.
I also read that this would in turn have an impact on the LTS updates to 26.04. This is to comply with UEFI Secure Boot compatibility.
1 Like
Did you mean:
"Anyone NOT wanting the options removed would have to use the non-signed GRUB".
1 Like