Dennis HilkLinux diagnosticsDE

NVIDIA graphics

NVIDIA GeForce RTX 5090 reference

A checked RTX 5090 reference with the vendor-documented Blackwell module-flavor boundary and explicit local-evidence limits.

Editorial source review: Share public profileOpen in the identification tool
On this page
  1. Overview & identity
  2. Driver & binding
  3. Firmware
  4. Read-only diagnostics
  5. Limitations & related issues
  6. References

Overview & identity

The checked vendor README has an unqualified 2B85 row labelled GeForce RTX 5090. The evidence is the versioned manufacturer table, not a guessed device number or an imported PCI-name database. The exact board and every other RTX 50-series product remain outside this match.

Curated identifiers
pci 10de:2b85

A numeric match establishes a candidate family within the reviewed evidence. Marketing names, board variants, subsystem conditions and successful operation remain separate questions.

Driver & binding

The reviewed NVIDIA module-flavor page explicitly states that Blackwell GPUs require the open flavor. That vendor statement does not establish what is installed locally. The pasted kernel owner, module version and firmware messages are needed together; Nouveau wildcard matching is not proof of an equivalent feature set for this product.

  • nouveau — kernel driver/module candidate
  • nvidia — kernel driver/module candidate

Detected, bound, operational: learn the difference

Firmware

Device/revision dependent

The checked vendor documentation locates GSP files under nvidia/580.95.05/ and gives gsp_tu10x.bin as one architecture-named example. That example is not a declaration that this particular card requests the Turing image. Exact selection depends on the active driver release and architecture; Nouveau has a separate firmware path.

Inspect firmware packaging on your distribution

Read-only diagnostics

Run one displayed command at a time. Replace uppercase placeholders with the affected device, interface or module from your own output. Commands are never executed here. Read-only output can still contain private identifiers.

Read the numeric PCI identity and binding

lspci -nnk -s BDF

Replace BDF with the address of the GeForce RTX 5090 display function. No sudo is normally required for this summary. The numeric vendor/device pair is the evidence for identity; “Kernel driver in use” is evidence of the current binding. A “Kernel modules” list is only a list of candidates.

Confirm the owner of this PCI function

readlink /sys/bus/pci/devices/BDF/driver

Use the full domain:bus:slot.function address in BDF, for example the form shown by lspci -D. This read-only symlink normally needs no elevated privileges. Its last component names the bound driver. An absent link can also mean an unbound, removed or guest-assigned function; it does not prove that no Linux driver exists.

Read initialization and failure context

journalctl -k -b --no-pager

Keep nvidia/NVRM and Nouveau messages separate and correlate them with the selected PCI function; an Xid is a runtime error report, not a driver-installation verdict. This reads the current boot only. Correlate the PCI address and timestamps before connecting a message to this GPU. Journal access depends on local group permissions; a permission error is not a hardware result.

Read the vendor-driver userspace observation

nvidia-smi --query-gpu=pci.bus_id,name,driver_version --format=csv

This read-only query requires the NVIDIA userspace utility and a working NVIDIA driver connection, but normally no sudo. Match the returned PCI bus ID to BDF. A missing command or a driver/library error is distinct from an absent GPU; this query is not suitable for a Nouveau-only binding.

Limitations & related issues

This reference profile does not advertise a minimum Linux version or claim that all distributions ship a suitable driver and firmware. A module alias, supported-chip row and functioning application are three different levels of evidence.

These guides are linked for relevant observations, not as known defects of every device in this family.

Choose a hardware diagnostic workflow · Inspect a log excerpt in Fix Lab

References

Source review records a checked implementation or document, not a reproduced hardware test. Version-specific tables do not establish a minimum kernel or guaranteed operation.