Overview
This article outlines how to use dmesg logs and kernel module commands to diagnose issues where the operating system fails to detect NVIDIA GPUs—even though they appear in the system's BMC (Baseboard Management Controller).
When to Use This
You may need this guide if:
-
nvidia-smi reports: NVRM: No NVIDIA GPU found
-
GPUs are visible in BMC or IPMI but not in the OS
-
You're seeing driver or hardware initialization errors during boot
Step 1: Check Kernel Ring Buffer (dmesg) for Errors
The dmesg command shows messages from the kernel that are helpful for low-level diagnostics.
What to Look For:
module verification failed — Indicates Secure Boot is blocking the NVIDIA kernel module.
-
No NVIDIA GPU found — The NVIDIA driver was loaded but no GPUs were detected on the PCI bus.
-
firmware: failed to load — A required firmware blob was missing.
-
ACPI: device not enabled — BIOS/UEFI settings may have disabled PCIe devices.
Step 2: Check if the NVIDIA Kernel Module is Loaded
Linux uses kernel modules (drivers) to interface with hardware like NVIDIA GPUs.
If you get output like:
→ The driver is loaded and likely functioning.
If there is no output:
The module didn’t load. Check dmesg again or try loading it manually:
Step 3: Check for Secure Boot Blocking the Driver
Secure Boot can prevent unsigned kernel modules like NVIDIA’s from loading.
Step 4: Check PCI Bus for NVIDIA Devices
This helps confirm whether the GPU is physically present and detected at the PCIe level.
If no output appears, the GPU is not even seen by the PCIe bus. Potential causes:
Check if nvidia kernel module is available:
If modinfo says "module not found", the driver installation might be corrupted or incomplete.
Related Articles
Recent Articles
KB-630208 | How to use Find and Locate to search for files in Linux
Purpose To provide Linux administrators and Field Engineers with guidance on using the find and locate utilities to efficiently search for files and directories within a Linux filesystem based on criteria such as name, type, size, timestamps, ...
KB-630164 | How to use rsync to Synchronize Files
Purpose To provide a clear and practical procedure for using the rsync utility to synchronize files and directories between local systems and remote hosts, including push and pull operations, while preserving file attributes and optimizing data ...
KB-630107 | How to create a Linux swap file
Purpose To provide Field Engineers and Linux administrators with a standardized procedure for creating, configuring, and validating a Linux swap file. This procedure helps ensure sufficient virtual memory is available when physical RAM is exhausted ...
MSI All-in-One (AIO) PC – Physical Damage Policy for Warranty Claims
MSI All-in-One (AIO) PC – Physical Damage Policy for Warranty Claims MSI's standard warranty does not cover physical or accidental damage to an All-in-One (AIO) PC. If the damage is determined to be caused by external factors rather than a ...
KB 134833 - Troubleshooting NVSM Alert NV-CPU-XX – Unrecoverable CPU Internal Error
Purpose This document provides a general troubleshooting procedure for the NVIDIA System Management (NVSM) alert NV-CPU-XX, which indicates that a CPU has reported an internal error. The article outlines how to verify whether the alert represents an ...