Dennis HilkLinux diagnosticsDE

AMD graphics

AMD Renoir integrated graphics

An AMD APU graphics function where shared system memory and multi-GPU selection need their own context.

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 1002:1636 entry carries CHIP_RENOIR and AMD_IS_APU. It is an integrated-graphics family match, not a precise CPU model or laptop identity. The APU flag explains why a discrete-card assumption about local video memory is inappropriate without reading the system configuration.

Curated identifiers
pci 1002:1636

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 table-backed candidate and the graphics source declares renoir firmware. On a system with another GPU, keep the render and display roles distinct: the APU may drive a panel while an application renders elsewhere. A firmware request from a different PCI address should not be assigned to Renoir just because amdgpu is shared.

  • 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/renoir_pfp.bin
  • amdgpu/renoir_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 Renoir integrated graphics 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

Neither the ID nor an AMD_IS_APU flag predicts battery life, memory reservation or suspend reliability. Firmware loading, application selection and a failed suspend callback require different evidence; no reproduced notebook-specific fix is asserted.

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.