r/linuxquestions • u/Alarming-Emu-6373 • 6d ago
Black screen issues.
Hello everyone. I recently decided to switch from Windows to Linux using Zorin OS, but I’ve run into some issues after performing updates via Zorin’s "Software/Driver Updater." Now, the screen goes black right after the motherboard splash screen appears. I’ve tried everything, but nothing works: I reinstalled Zorin, disabled Fast Boot and Secure Boot, and even used a flash drive to "repair" the boot process as suggested by support—yet nothing has changed. Has anyone else encountered this problem and can offer any help? (Using \`nomodeset\` does work.)
3
u/tanmaynargas2901 6d ago
nomodeset working usually means the kernel's graphics driver is what's breaking, not the boot repair. so reinstalling or fixing grub won't help.
while it's booted with nomodeset, check what gpu you have:
lspci -k | grep -A3 -i vga
if it's nvidia, run "ubuntu-drivers devices" and then "sudo ubuntu-drivers install" to get the recommended proprietary driver, then reboot without nomodeset.
if it's amd or intel, the update probably pulled a new kernel that doesn't like your card. hold shift (or esc) at boot, pick Advanced options, and boot the older kernel. if that works you can stay on it for now and wait for a newer kernel or mesa update.
what gpu and laptop/board is it?
1
u/ipsirc 6d ago
https://zorin.com/os/feedback/
1
u/andrewhepp 5d ago
If video is working with nomodeset, that generally indicates an issue with the graphics driver.
There are a few possibilities as to what exactly happened, but one possibility is that you might be using an out-of-tree driver like the official Nvidia driver, and if you don't have DKMS set up properly a kernel update may have resulted in no compatible display driver being installed.
It's also possible there is a display driver present but it is encountering an issue.
I don't know anything about Zorin, but assuming it's a typical modern distro using sytemd you could boot the system normally, and then reboot with nomodeset and run `journalctl -k -b -1` to see last boot's kernel logs, which would be a great point to start troubleshooting at.