New to and using Zorin OS 18 Core for last month or so with dual monitors. Yesterday's update left me with one working monitor. firmware : 2.20.1; Kernel:Linux 6.14.0-37-generic.
I have NVIDIA graphics card and did original install with appropriate check box and dual monitors worked from the very beginning.
I'm using dual boot Windows/Zorin on two ssds. Dual monitors working in Windows.
Zorin Help has steps for installing NVIDIA drivers but I couldn't follow the steps as the choices I am supposed to see on the screen (such as 'Additional drivers' and others) are not there.
System Details Report
Report details
Date generated: 2026-01-31 17:12:48
Hardware Information:
Hardware Model: Dell Inc. XPS 8960
Memory: 32.0 GiB
Processor: Intel® Core™ i9-14900K × 32
Graphics: Intel® Graphics (RPL-S)
Disk Capacity: 4.0 TB
Software Information:
Firmware Version: 2.20.1
OS Name: Zorin OS 18 Core
OS Build: (null)
OS Type: 64-bit
Windowing System: Wayland
Kernel Version: Linux 6.14.0-37-generic
Thanks for your help, I appreciate it
I would suggest to try it with switching to Xorg. to do that, go to the Login Screen. Click there on Your Profile so that the Password Field appears. When it is appeared, you should see a Gear Icon in the bottom right Corner. Click on it and choose the Option ''Zorin Desktop on Xorg'' and then log in.
Another interesting Thing is that here stands:
but You wrote here about Nvidia:
When switched to Xorg, type in the Terminal nvidia-smi to see if it is detected. If it is, type sudo prime-select nvidia to use the Nvidia Card as primary Output.
Thank you Ponce-de-Leon. The response I got was "nvidia-smi failed because it couldn't communicate with driver. Make sure latest nvidia driver is installed and running"
An invidia driver is installed but how do I tell if it is running (or better yet make it run)?
Okay, then I would suggest the Following: First switch to Xorg. And then You could try it with uninstall the Nvidia Driver and then install it again. We should try it over the Terminal. then we get better Feedback in Case of Issues.
First type
sudo apt purge nvidia* libnvidia*
to delete all Nvidia Driver Stuff. Then type:
sudo apt autoremove
to remove File Rests. But please takke a Look at the List of the to be removed Files before You delete them. To install the Nvidia Driver again type:
Linux is totally new to me so I don't know what I am looking for when you say "take a look at the list of the to be removed files before you delete them" Is it the 'sudo apt autoremove' command that will show me the list? Or do I run a separate command to get that list? Thanks for all your help and attention to this.
When you enter the command 'sudo apt autoremove' you get a list with packages which will be removed and you are asked if you want to remove them all. Before you confirm with yes, take a look at this list.
OK did the suggested steps and still get the message "nvidia-smi failed because it couldn't communicate with driver. Make sure latest nvidia driver is installed and running"
Did a search on that. Someone pointed to disabling Secure Boot in BIOS fixed that for them. Surely not that simple.
But the question needs to be asked. In BIOS is Secure Boot and Fast Boot disabled?
Thank you Aravisian. I got a message of "changing this setting may prevent your operating system from booting or require a reinstall" That is a level of risk that is too high for me. I absolutely have to have dual monitors in Windows and dual monitors in Zorin is nice to have. So while it is very frustrating that the dual monitors worked immediately upon Zorin OS 18 install and then was disabled upon Zorin update, I think I will have to live with that.
Thank you and others so much for the help.
That message is pure scareware - and as you can see, it worked.
No, it will not have that effect. Here's how it can make that claim and not technically be lying:
Secure Boot is in place so that only Microsoft Signed packages can initialize.
If Secure Boot is disabled - and you are on Windows OS - and you get a Virus - and that virus corrupts the system to an unbootable state... Then it technically caused what that warning claims. There are far better ways to protect your system from viruses than Secure Boot and the mere act of disabling Secure boot absolutely 100% will not make your system unbootable.
Thee problem is that Microsoft is sluggish or lax about signing for Nvidia or some GnuLinux packages. And Nvidia also can be lax on their end.
That being said;
You still may say "I would prefer to not take the risk."
If Secure Boot is Enabled, we can try MOK enrollment on Zorin OS and getting a signature for Nvidia.
So the good news is - there is a good chance your "nice to have" can be had, while remaining in your comfort zone.
Thank you so much for sticking in there to educate me. I was envisioning clicking 'disable' and then upon reboot finding I had a brick on my hands. I will disable Secure Boot and let you know what happens.
4 minutes later:
That did the trick!
What better ways than Secure Boot should I employ now that SB is disabled?
Thanks again
Secure Boot is static. It operates as a bouncer at a nightclub, accepting or rejecting guests based on a list.
You're on the list or not on it. This is a narrow threat model.
A better method is dynamic:
Disable kernel features you don’t need
Unprivileged user namespaces
BPF JIT (or restrict)
Legacy filesystems
SELinux or AppArmor in enforcing mode (Zorin OS comes with AppArmor installed and already configured).
Most real-world Linux compromises occur after boot.
Staying updated using the updater or sudo apt update && sudo apt upgrade and keeping firmware updated.
Being vigilant about where you browse and what you open- This is the truest attack vector - what the user lets in.
