我的 nvidia 驱动程序有问题。进行了 apt 更新，机器在晚上关机了。开机后，我看到光标闪烁。甚至在备用磁盘上进行了完全重新安装（安装期间启用更新），情况也一样。nvidia-340 无法构建。
ubuntu-drivers autoinstall
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 305 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up nvidia-340 (340.108-0ubuntu2) ...
dpkg: error: version '-' has bad syntax: revision number is empty
dpkg: error: version '-' has bad syntax: revision number is empty
update-initramfs: deferring update (trigger activated)
INFO:Enable nvidia-340
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
Removing old nvidia-340-340.108 DKMS files...
------------------------------
Deleting module version: 340.108
completely from the DKMS tree.
------------------------------
Done.
Loading new nvidia-340-340.108 DKMS files...
Building for 5.8.0-36-generic
Building for architecture x86_64
Building initial module for 5.8.0-36-generic
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/nvidia-340.0.crash'
Error! Bad return status for module build on kernel: 5.8.0-36-generic (x86_64)
Consult /var/lib/dkms/nvidia-340/340.108/build/make.log for more information.
dpkg: error processing package nvidia-340 (--configure):
installed nvidia-340 package post-installation script subprocess returned error exit status 10
Processing triggers for libc-bin (2.31-0ubuntu9) ...
Processing triggers for initramfs-tools (0.136ubuntu6.2) ...
update-initramfs: Generating /boot/initrd.img-5.8.0-36-generic
Errors were encountered while processing:
nvidia-340
E: Sub-process /usr/bin/dpkg returned an error code (1)
nvidia-340.0.崩溃->https://controlc.com/fb556872 制作.日志->https://controlc.com/5bf2520a
答案1
恢复到 5.8.0-36-generic 以外的旧内核。
开机时按住 shift。选择较旧的内核并启动。
从那里您将拥有一台可以运行的机器并可以研究如何删除坏内核。
请记住，除非您删除坏的内核和标题，否则它会在每次重新启动时尝试使用它。
我现在也正在经历这种情况。似乎很多人都受到了影响。
答案2
是的，启动5.4内核。
如果您需要经常重启，您可以随时使用 grub-customizer 直到错误被修复：
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/191113