BIOS Update and Zorin updates - no boot

Updated my gigabyte motherboard BIOS (UEFI) the other day and did a Zorin apt update and my machine stopped booting. It was random because after a hard reset it would boot normally. Soft reset from menu resulted in the splash screen hanging.

With a bit of luck I determined that it was a nvidia graphics hang as I noticed the splash screen change resolution then hang.

I was using nvidia 570 driver before the update so I rolled back to 550 with my GT 1030 card. This worked and the hang was gone. It maybe coincidence the BIOS update and apt system update but it seems ok now.

I saw a similar thread the other day but cant find it now but that was with an AMD card and presumably drivers in the kernel. Just funny how it was similar result.

Anyone able to explain why 550 works and 570 doesn't?

Not for certain, but 570 was not well-received. It was the first driver to support the 50 series GPUs and a lot of complaints were had. Even windows users were known to roll back to 565. I've had better results with 575 than 570 personally, so you might give that a try.

3 Likes

Interesting. I am running a dual boot Zorin and Solus. Solus is on 570 with the same card the developers reported problems on Solus with 575. Meanwhile 575 I cant see on the Zorin list.

1 Like

I agree, thats why I'm still on the 555 driver, cause 570 is known garbage. It will be while before the 576 driver gets released to Linux, I think it might be better from what I'm hearing from Windows users.

I've been holding off updating my Nvidia driver for far too long, due to many Nvidia driver related issues, over the first half of the year, so it would be nice if Nvidia could get their head in the game, instead of concerning themselves with global domination, through the use of AI.


1 Like

If by "Zorin list," you mean the additional drivers tab of software and updates, Zorin tends to be slower to add drivers. You can add the graphics-drivers PPA to address this:

sudo add-apt-repository ppa:graphics-drivers/ppa

I believe a refresh with that PPA added should make the driver available, but I tended to go the whole way in the console. Instructions here:

These days I actually use the drivers supplied directly by Nvidia, though there are more steps and it takes a bit longer as it actually builds the kernel modules directly on your system. (This will require updating gcc, the GNU C Compiler on Zorin 17, but it's easy and a link in the instructions covers how.) The faster your computer is, the less of a nuisance that would be. I recommend this method only for people who want the absolute latest drivers on their own terms, or total control over which version you're on, as it bypasses package management altogether:

1 Like

Thanks for that. I cant remember if I followed that tutorial in the past to change to 570 using the graphics repository. But for some reason either the motherboard BIOS update or repository update messed up the 570 driver and switching back to 550 fixed it. 576 maybe in the additional drivers list I dont remember.

2 Likes

Personally I avoid proprietary drivers as they cause me more problems than solve them, but understand that those who game need them.

1 Like

Could it be that You maybe got a Kernel Update? When You installed the 570 Driver, did You install the dkms Package with it?

I would suggest to reinstall the 570 Driver and see if it then works again. To do that:

sudo apt purge nvidia*

to remove all installed Nvidia Driver.

sudo apt autoremove

To remove File and Data Rests. But take a Look at the List of the Stuff what will be removed before You remove it!

sudo apt install nvidia-driver-570 nvidia-dkms-570

to install the Driver again.

Because You are using a Nvidia Graphics, I guess Your System runs in X11, yes?

Yes I am running Plasma X11. Think I will just leave 550 on as it works ok.

2 Likes

When that works for You, that is totally fine.

1 Like