Zorin freezes in boot splash after latest kernel update (6.17.40-generic)

Hi, as many others already reported I also ran into serious issues after the last update on July 15th. When I tried to boot my system would just freeze in the boot splash animation of the Z.

Not knowing what's going on I first booted into the Live system and ran Repair Boot. Then I came across a similar sounding issue with a freeze in the boot process in the forum, suggesting to remove the quiet splash from the boot parameters, but that didn't help. Booting into recovery mode didn't help either.

Only after selecting another kernel to boot with, after reading about nvidia and kernel issues, I was able to successfully boot again. I then tried to install timeshift to be able to more easily undo changes like that. But that failed because of broken packages, namely the nvidia drivers for the kernel. I followed this thread to remove all nvidia drivers and reinstall them, simultaneously switching from nvidia-driver-580 to 535, because it's "tested". Unfortunately that did not resolve the issue either. I can only boot into the previous kernel.

I have to say this is quite upsetting.The Software Updater shouldn't just install new kernels without warning me! It took me several hours to find out what was going on, because I had already forgotten that I had installed any updates at all in my last session. The updates are so low-key and had worked until now that I installed them without paying any mind to it. It wasn't until I saw the other forum posts that it clicked. I thought my system was just suddenly broken, assuming most likely a hardware issue.

I think Ubuntu or Linux Mint (at least used to) divide updates and upgrades and would warn users that a kernel upgrade could potentially break things. I would really appreciate if Zorin could implement a similar approach.
Also, it would be nice when the Software Updater would show a history of the last installed updates (basically /var/log/apt/history.log).

Anyway, what I haven't found out yet is: How can I remove the latest kernel and prevent Zorin from upgrading to it again?

Here are my infos:

jan@mindfunk:~$ inxi -Ga
Graphics:
  Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] vendor: ZOTAC driver: nvidia
    v: 535.309.01 alternate: nvidiafb,nouveau,nvidia_drm non-free: 545.xx+
    status: current (as of 2024-04; EOL~2026-12-xx) arch: Pascal code: GP10x
    process: TSMC 16nm built: 2016-2021 pcie: gen: 3 speed: 8 GT/s lanes: 16
    ports: active: none off: DP-2,HDMI-A-1 empty: DP-1,DP-3,DVI-D-1
    bus-ID: 01:00.0 chip-ID: 10de:1c03 class-ID: 0300
  Device-2: Microdia USB Live camera driver: snd-usb-audio,uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-10.1:7
    chip-ID: 0c45:636b class-ID: 0102 serial: SN0001
  Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6
    compositor: gnome-shell v: 46.0 driver: X: loaded: nvidia
    gpu: nvidia,nvidia-nvswitch display-ID: :1 screens: 1
  Screen-1: 0 s-res: 5120x1440 s-dpi: 108 s-size: 1204x333mm (47.40x13.11")
    s-diag: 1249mm (49.18")
  Monitor-1: DP-2 pos: left res: 2560x1440 hz: 60 dpi: 109
    size: 596x335mm (23.46x13.19") diag: 684mm (26.92") modes: N/A
  Monitor-2: HDMI-0 pos: primary,right res: 2560x1440 hz: 60 dpi: 109
    size: 597x335mm (23.5x13.19") diag: 685mm (26.95") modes: N/A
  API: EGL Message: No EGL data available.
  API: OpenGL v: 4.6.0 vendor: nvidia v: 535.309.01 glx-v: 1.4
    direct-render: yes renderer: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2
    memory: 5.86 GiB

1 Like

Thanks! I also just purged the latest kernel as described here.

If Secure Boot is enabled in your BIOS settings, that can block Nvidia Drivers.
So, it may not be the kernel that is the issue.

Agreed.

That 'tested' name is slightly misleading. It means what you think - that it has been tested; but that testing is not in regards to compatibility or performance. It is an internal note that means that the drivers are passing basic code checks, is all.

1 Like

Secure Boot is not enabled as I understand it.

jan@mindfunk:~$ sudo mokutil --sb-state
SecureBoot disabled
Platform is in Setup Mode
jan@mindfunk:~$ sudo mokutil --test-key /var/lib/shim-signed/mok/MOK.der
/var/lib/shim-signed/mok/MOK.der is not enrolled

1 Like

It may be the kernel, after-all...

There is one other thing, though.
When a kernel upgrades, the Nvidia Drivers must be tied to it (Modules). If the Nvidia driver is installed without DKMS (Dynamic Kernel Module Support), then upon reboot and loading into the newer kernel, the driver will fail.

So best practice when using Nvidia is to install with DKMS.

For example:

sudo apt install nvidia-driver-580 nvidia-dkms-580

At least for the nvidia-driver-535 that I switched to the DKMS is already installed.

Another thing I just remembered: After switching to 535 I was able to get to the login, but then my keyboard stopped working! While the mouse was still fine and the keyboard had been working in the boot loader, as soon as the login screen appeared (in a much to low resolution as well) the keyboard stopped working, preventing me from logging in.

At that point; Definitely kernel.

On a bright side: Look how many things you got practice and learning with today...

Heh, yeah. I was just hoping that with Zorin I wouldn't have to practice these things so much. The Linux user experiencs has gotten a lot better in the last years. I still remember the hassle installing Debian for the first time 20 years ago. Unfortunately, issues like this will still alienate your average Windows user.

This is a fair point. You do not want a hair-raising experience when you are just trying to get things done.

On a flip-side, though... it is demonstrative of your average users power and control, rather than being controlled.
A glass can be half-empty as easily as half-filled with both statements true. But the choice you make as to which matters a great deal.

Practice, even if unexpected... makes you stronger, smarter and more capable. This does not take away from a valid feeling of frustrated - it only adds to your toolbox.

Sure, the control you have is one of the Linux biggest advantages. However, most people just want a system that works.

Thanks by the way for the quick reply!

1 Like

I don't know how you have Software & Updates setup. I always review the proposed software updates listed, before proceeding to click on [Install Now].
Kernel updates are listed under "OS Updates". By expanding that tree branch you should see any kernel updates and kernel version that will be installed. I always make a written note of that, so if anything bad happens, I can test if it relates to the new kernel by booting the previous kernel version.

1 Like

I've been thinking about this a bit. I understand that you're trying to tell me a way to prevent this in the future, by reviewing the changes before installing.

However, my point is that casual users will not do that. If Zorin is supposed to appeal to a more casual audience, then it either needs to communicate updates that might break your system better. Meaning, don't hide the relevant information behind multiple clicks while offering a single click "Install Now" option. Or don't include updates that might break your system, which is basically Kernel updates in the normal "Updater". IIRC either Ubuntu or Linux Mint distinguishes between simple software updates and Kernel/OS updates.

Don't get me wrong. I can handle issues like that, even if I might get irritated, but a casual user might just be going back to their previous OS as soon as they run into an issue like that. Especially if they then get told they should have just read the update details and figured out that this might result in an issue. (Not saying you did this here, but the "you have all the tools", "just rtfm" and "just get good" mentally is one of the reasons Linux isn't as widely adopted as it could be. And I think that's a shame. Hopefully, Zorin OS (among others) can change that :slight_smile:

1 Like