Dennis HilkLinux diagnosticsDE

AMD graphics

AMD Navi 10

Navi 10 graphics: use the family ID to organize initialization, rendering and DisplayPort evidence.

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 numeric pair 1002:731f is mapped to CHIP_NAVI10. The source name is a silicon family and does not distinguish all retail cards that reuse it. If only a monitor disappears, preserve the connector and link-training messages separately from the GPU execution log.

Curated identifiers
pci 1002:731f

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 checked amdgpu graphics implementation declares Navi 10 firmware. Firmware loading occurs before a userspace rendering test can establish acceleration. A DisplayPort link problem after a modeset can coexist with a healthy render device; inspect the connector evidence before treating every black screen as a GPU reset.

  • amdgpu — kernel driver/module candidate

Detected, bound, operational: learn the difference

Firmware

Host-loaded firmware required

The reviewed amdgpu engine declares the listed images. They are examples for this family, not a complete package manifest. Use the exact firmware request from the running kernel to identify a missing file; a file merely existing on disk does not establish successful loading.

Checked examples or filename branches, not a complete installation list:

  • amdgpu/navi10_pfp.bin
  • amdgpu/navi10_rlc.bin

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 Navi 10 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

Read the first amdgpu initialization or engine-failure messages, including the requested firmware filename and any recovery that follows. 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.

Limitations & related issues

A successful PCI match cannot guarantee link bandwidth, EDID validity or API availability. The source snapshot is not a minimum-supported-kernel claim and does not validate any specific monitor/cable combination.

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.