AMD graphics

AMD Bonaire / Sea Islands

Bonaire graphics with a reviewed mobile ID and an explicit radeon/amdgpu CIK selection boundary.

On this page
  1. Overview & identity
  2. Driver & binding
  3. Firmware
  4. Read-only diagnostics
  5. Limitations & related issues
  6. References

Overview & identity

1002:6640 carries the CHIP_BONAIRE family tag and AMD_IS_MOBILITY flag in the snapshot. The mobility flag is a driver-table observation, not proof of an exact laptop. External display routing and the relationship to another GPU still depend on the system board and the pasted PCI topology.

Curated identifiers
pci 1002:6640

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

CIK support is separately selectable for radeon and amdgpu. The candidate must be distinguished from the actual owner. For a hybrid notebook, a healthy Bonaire initialization does not mean that the desktop compositor or an individual application selected it; graphics routing needs a separate userspace observation.

  • amdgpu — kernel driver/module candidate
  • radeon — 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/bonaire_pfp.bin
  • amdgpu/bonaire_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 Bonaire / Sea Islands 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.

Read the existing family-selection policy

cat /sys/module/amdgpu/parameters/cik_support /sys/module/radeon/parameters/cik_support

This reads the selected family controls if their modules expose them. Missing files may mean a driver was not built or loaded. Values are evidence of existing policy, not an instruction to change it; the PCI driver link still decides the present owner. Reading these documented parameters normally needs no sudo.

Limitations & related issues

The table flag does not describe mux hardware, power-management behavior or OEM firmware. Treat a resume failure, a module-selection mismatch and CPU rendering as separate observations rather than assuming one CIK defect.

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.