Yes, no additional options.
I removed the old kernel and ran sudo update-bootloader, then I restarted. After restarting the graphics drivers were working and uname showed I was using the new kernel version.
However I couldn’t change system files, it seems I was booting into a readonly snapper snapshot. So then I ran snapper rollback which created a ‘writable copy’ of the system, then I rebooted. Now everything seems to be working. I also locked the kernel-default and the nvidia packages as @exception suggested.
Gotta admit some of this goes over my head and I’m not sure what happened, but hopefully things will keep working now.
Thanks a lot for the help!
Please do not follow such advice without need. Locking packages without checking the need for it, leads to issues. Better have a look when Nvidia drivers and kernel get updated if everything is in order, version wise. Only use package locks when absolutely needed. Beginners tend to throw locks like candy without thinking about and are wondering later why their system behaves strange when performing an upgrade…
1 Like
Possibly you were bitten by bug 1242144 or something similar. Since I do not use grub2-bls I cannot go any further.
Apparently that was a problem with the bootloader config and Nvidia was only the messenger telling that something (an old kernel in this case) was not as expected.
totally agree
i shared with him my post and his nvidia drivers is in sync that’s why i gave him the advice it has to be done manually until the meta packages solve things in the future like stated in a lot of posts including mine
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.