Dennis HilkLinux diagnosticsDE

AMD graphics

AMD Navi 44 — RX 9050 / RX 9060 XT family

Verified Navi 44 chip-family ID; the reported RX model and board remain separate 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

The versioned pci.ids entry maps PCI 1002:7590 to Navi 44 [Radeon RX 9050 / 9060 XT]. This is a chip-family match, not an exact retail model or board match. Subsystem 148c:2437 and revision c0 are reported observations only: the checked entry does not identify that board. Missing or different subsystem data does not invalidate the chip-family ID. No memory size, power limit or board specifications are inferred.

Curated identifiers
pci 1002:7590

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 is the relevant kernel graphics driver. The checked Linux snapshot uses AMD display-class CHIP_IP_DISCOVERY fallbacks rather than a literal 7590 product row. AMD documents RX 9060 XT as RDNA4/gfx1200, but this does not identify every board carrying the shared PCI ID. Kernel driver in use is reported binding; candidate modules, initialization and stable operation are separate facts. Legacy SI/CIK radeon selection parameters do not apply to this profile.

  • amdgpu — kernel driver/module candidate

Detected, bound, operational: learn the difference

Firmware

Host-loaded firmware required

AMDGPU uses host firmware selected by the discovered IP blocks and running kernel. No per-board file list is established by this PCI ID. Inspect the exact initialization requests and loading errors; neither older Radeon firmware nor both GC 12.0 paths should be prescribed from a shared driver name. The versioned GC 12.0 source documents firmware declarations, not a complete Navi 44 package manifest.

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 AMD IP-discovery 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 PCIe link capability and negotiated status

lspci -vv -s BDF

Elevated access may be needed. Compare LnkCap with LnkSta on this function and its upstream ports. A lower link rate is an observation, not a proved crash cause. Full capability access may require administrator rights.

Read initialization, firmware and GPU/PCIe errors

journalctl -b -k --no-pager --grep='amdgpu|firmware|AER|PCIe Bus Error'

Elevated access may be needed. Correlate addresses and timestamps with this device. Successful binding alone does not prove initialization. Firmware requests and ring, VM or PCIe errors are distinct observations; absence of a final log does not identify the cause. Review private data before sharing.

Limitations & related issues

Chip identity and reported binding do not establish successful firmware loading, display initialization or operational stability. A ring timeout, PCIe error and lost device require separate evidence. Do not infer an exact PowerColor model or reproduce a hard-lock from a catalog entry.

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.