Dennis HilkLinux diagnosticsDE

AMD graphics

AMD Vega 10

Vega 10 graphics with a family-level identity and separate graphics/compute firmware observations.

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

1002:687f is explicitly CHIP_VEGA10 in the kernel table. It identifies the GPU family and not a promised amount of HBM, a board power budget or an exact marketed Vega SKU. A second audio function on the same slot is a separate PCI device and should not be passed to a graphics-only diagnosis.

Curated identifiers
pci 1002:687f

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

amdgpu handles the checked PCI entry. The source declares PFP and MEC firmware among several engine images; a compute-engine complaint should retain its exact engine name. A render node and a bound driver show that kernel devices exist, but do not establish that a Vulkan loader found a suitable userspace implementation.

  • 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/vega10_pfp.bin
  • amdgpu/vega10_mec.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 Vega 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 page fault and a ring timeout describe different parts of GPU execution. Neither proves that the memory chips are defective. This profile contains no validated stability result for a game, compute workload or suspend sequence.

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.