Driver & firmware fundamentals

GPU kernel drivers, firmware and userspace

Separate AMD, Intel and NVIDIA binding evidence from rendering APIs, firmware and application selection.

One GPU has several software layers

PCI enumeration, the DRM kernel driver, firmware, Mesa or vendor userspace and the application API are separate layers. A bound GPU can still produce software rendering or be the wrong selected device in a hybrid system. Record the actual PCI identity and rendering observation before selecting a package.

lspci -nnk

Open kernel code does not describe the whole stack

NVIDIA open kernel modules and proprietary kernel modules are different implementation choices with release-specific supported GPU lists. Nouveau is another driver path. Do not assume all NVIDIA generations can interchange these choices. The matching userspace release and firmware remain part of the investigation; an open kernel module does not imply every component is open source.

Family and release context stay explicit

Intel i915 and xe coverage depends on platform and driver policy. AMD source tables can use internal IP-family names that do not reveal an exact retail board. The catalog preserves those distinctions and avoids automatic force_probe, recovery or power-parameter changes. Follow the linked Fix Lab guide for the actual message you observed.

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.

Use the local identification tool