20.04.1 LTS . Software updater (GUI application) showed kernel 5.8.0-34 as an update on 7 Jan 2021. During the update, the build for the (proprietary) nvidia driver from Ubuntu (not Nvidia) failed. I NEED the proprietary full function Nvidia driver and the Nvidia proprietary GUI that interfaces to the proprietary driver. Is there a workaround or a yet later production revision of either the Nvidia proprietary .deb package or the kernel to work with the current production Nvidia package?
I got the same error and just found out the solution. First thing I did was to uninstall the 5.8 kernel and rever to the 5.4.0-60. That however didn't solved the issue. So I realized that the
nvidia-smi
utils was stating that I had a version mismatch. So I removed all nvidia drivers and reinstalled with the correct version, that would be (on my case) 450. What I reinstalled was:After a reboot, the
nvidia-smi
util was working, but still no X. Then I found out that thexserver-xorg-video-nvidia-450
was removed, so I reinstalled and now everything is back to normal.You may need to install other packages, such as:
Hope that helps
I had the same issue. It seems like the
linux-modules-nvidia-*
packages have dependency issues. The packages do not list the corresponding kernel header packages in their dependencies, but only the kernel images. This obviously leads to a build fail.Installing the header files for the current kernel fixed the problem for me.
For Example: I had the
linux-modules-nvidia-390-generic-hwe-20.04
installed, so I installed thelinux-generic-hwe-20.04
package, which always installs the newest HWE kernel image and header files. (see here) Imho that package should be the dependency for the nvidia package.I followed the instructions above from Terrance. As given, these instructions did not work, but did enable a solution. The detailed output appears below; my guess is that the "package" explained by Terrance is not full production in that my experience is that "production" packages resolve and install all needed dependencies; this one did not. I attempted to post in this answer the full details (17kByte). Below is the actual command set that did work on 20.04.1 LTS; however, this Ask Ubuntu system will not let me post the output so that others may compare as to what the output for a working Nvidia driver system appears to be.
Having a issues post upgrade myself. Unfortunately, the timing was terrible as I had just dropped in a new laptop drive with a fresh install and picked up the update. Even after getting the 460 driver to work, I started having serious performance issues with one of the two displays when connecting my external monitor. The performance issues were significant and multiple crashes had me simply replace the original system back to kernel 5.4.0 and nvidia 450 to get the system usable again. Serious quality control issue with this update.
i faced a similar same problem 3 days ago after having applied UBUNTU 20.04 LTS updates (kernel 5.8.0.36)
I could solve the problem by using the generic GPU driver instead of NVIDIA's which is no longer supported
please see here for details : https://askubuntu.com/questions/1305862/after-an-update-and-reboot-in-ubuntu-20-04-i-can-no-longer-complete-the-boot
I faced same situation with this whole kernel thing: changing from 5.4 to 5.8 broke my virtualbox. I went back to 5.4 until everything gets fixed.
After an automatic update to 5.8.n, my Thinkpad W540 showed a white screen. I was able to boot with 5.4.n which still works perfectly. I followed the advice from Terence to install
nvidia-driver-460
. After rebooting, I was able to see 5.8.n, but the screen resolution was set to 640 x 320 and there was no other option available to change these settings.I tried everything I could think of. I attempted to install new drivers through a hugely magnified unscrollable terminal screen working blind and typing into space off-screen and found that I had no internet access. No NVIDIA drivers and no Wi-Fi.
I stopped looking for more problems as it would take too long to fix. I recommend that all users experiencing problems with 5.8.n interrupt normal boot and select the previous reliable kernel version (5.4.n for me) until this car-crash update is fixed by the people who caused it.
Sorry to be critical, but fair's fair. 5.4.n is great so the developers can get it VERY right but not this time.