environment
– notebook model: Dell precision 5520
– graphics card model: M1200
– system: Ubuntu 20.04
Question
After installing the N card driver, execute NVIDIA SMI
, and an error is reported:
NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.
Solution:
Method 1
Cause: the system kernel is upgraded, resulting in the mismatch between the new version of kernel and the original graphics card driver
solution: use DKMS to generate the corresponding kernel file
View driver version
ls /usr/src | grep nvidia
For example, my result is nvidia-470.103.01
matching
sudo apt-get install dkms
sudo dkms install -m nvidia -v 470.103.01
Method 2
Reason: the same as scheme 1
solution: log in using the kernel. Then set the default to start with the kernel.
Method 3 (work for me)
Reason: the secure boot
of the BIOS is in the enable
state
Solution: enter the BIOS (generally press F2 when starting up) and turn off secure boot
it is strongly recommended that even if your secure boot
is already in disable
, it is recommended to execute it once: enable
, restart, disable
, and then restart. (this is my situation, so confused!!)
Read More:
- Failed to Connect NVIDIA Driver: NVIDIA-SMI has failed because it couldn‘t communicate with the NVIDIA driver
- [Solved] NVIDIA-SMI has failed because it couldn‘t communicate with the NVIDIA driver.
- NVIDIA SMI error after Ubuntu 20.04 restart [How to Solve]
- [Solved] Docker error: “unknown runtime specified NVIDIA” using GPU“
- [Solved] OCI runtime create failed: /usr/bin/nvidia-container-runtime did not terminate successfully: unknown
- [Solved] Error response from daemon: manifest for nvidia/cuda:latest not found: manifest unknown: manifest
- Couldn‘t create temporary archive name. [How to Solve]
- [Solved] ERROR: The kernel module failed to load, because it was not signed by a key that is trusted by the
- [Solved] TclError: couldn‘t connect to display “localhost:11.0“
- [Solved] docker Error: System has not been booted with systemd as init system (PID 1). Can‘t operate. Failed to con
- [Solved] Warning: detected “cgroupfs“ as the Docker cgroup driver. The recommended driver is “systemd“.
- cstdio [Error] ‘::fpos_t‘ has not been declared [How to Solve]
- System has not been booted with systemd as init system (PID 1). Can‘t operate
- [Solved] linux kernel load driver Error: module verification failed: signature and/or required key missing – tainting kernel
- Linux Virtual Machine Boot Container: Error response from daemon: driver failed programming external connectivity on endpoint
- [Solved] CUDA driver version is insufficient for CUDA runtime version
- How to Solve Error: Driver “kvm2“ not found
- [Solved] An unexpected error has occurred. Conda has prepared the above report.
- linux yum Error: PYCURL ERROR 6 – “Couldn’t resolve host ‘mirrorlist.centos.org’”
- [Solved] YarnClientSchedulerBackend: Yarn application has already exited with state FAILED