Dennis HilkLinux diagnosticsDE

NVIDIA graphics

NVIDIA GeForce RTX 3080 reference

A checked RTX 3080 ID for correlating driver-version, initialization and PCIe error reports without inferring a board defect.

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

10de:2206 is a checked GeForce RTX 3080 reference row. Other 3080 rows exist in the same primary source, so this match must retain its numeric pair. The selected ID is not used here to assert memory size, board revision or a specific OEM configuration.

Curated identifiers
pci 10de:2206

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

For an NVIDIA-bound device, a userspace query can report the driver version and PCI address; it does not replace the kernel binding check. GSP use is a documented vendor-driver initialization detail. Preserve a first Xid and any parent-port AER message before connecting a later application failure to the card.

  • 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 3080 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 source review contains no reproduced bus-loss, suspend or gaming test. The supported-chips list cannot distinguish a library mismatch from a firmware failure or a physical PCIe problem.

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.