Linux Hardware & Driver Explorer
Know your hardware.
Understand your drivers.
Start with a hardware report. Separate identity, binding and initialization, then follow the evidence into Linux Fix Lab.
Identify my hardware
Use a relevant excerpt from lspci, lsusb, inxi or lshw. Numeric IDs make identification more reliable; a reported product label is not enough.
Up to 2 million characters, 20,000 lines and 512 devices. Long lines are shortened with a notice. Raw reports are not stored. A language change discards private data and keeps only the chosen public profile and diagnostic position.
The default summary excludes raw report lines, labels, serials, MACs and hostnames. Redaction is best effort; review a redacted excerpt before giving it to anyone.
Review redacted excerpt
How to collect read-only input
Run one command manually. Tools may need installation; complete descriptors or hardware details can require elevated privileges. Reports can contain private identifiers even with redaction options.
lspci -nnklsusbinxi -Fxxxzlshw -numericSource-backed hardware profiles
Curated chip and device families, alongside explicit generic class profiles. This is not a complete PCI/USB database or a compatibility certification.
155 profiles
No curated profile matches this filter. Shorten the term or clear the category. An unknown ID is not proof of unsupported hardware.
- AMD graphics
AMD Tahiti / Southern Islands
An older AMD graphics family whose Linux binding can depend on the Southern Islands driver-selection policy.
- AMD graphics
AMD Bonaire / Sea Islands
Bonaire graphics with a reviewed mobile ID and an explicit radeon/amdgpu CIK selection boundary.
- AMD graphics
AMD Polaris 10
A Polaris-family match that deliberately keeps shared silicon identity separate from the retail RX model.
- AMD graphics
AMD Vega 10
Vega 10 graphics with a family-level identity and separate graphics/compute firmware observations.
- AMD graphics
AMD Navi 10
Navi 10 graphics: use the family ID to organize initialization, rendering and DisplayPort evidence.
- AMD graphics
AMD Sienna Cichlid graphics family
A Sienna Cichlid table match whose firmware uses the source codename rather than the retail product label.
- AMD graphics
AMD Renoir integrated graphics
An AMD APU graphics function where shared system memory and multi-GPU selection need their own context.
- AMD graphics
AMD GC 12.0 IP-discovery graphics context
A source-backed graphics-block context for modern amdgpu reports; no exact Radeon product is inferred.
- NVIDIA graphics
NVIDIA GeForce GTX 750 Ti reference
A GTX 750 Ti reference ID: establish the existing Nouveau or NVIDIA owner before discussing module flavors.
- NVIDIA graphics
NVIDIA GeForce GTX 980 reference
A checked GTX 980 ID with separate evidence for a working display, kernel binding and 3D acceleration.
- NVIDIA graphics
NVIDIA GeForce GTX 1080 reference
A GTX 1080 reference where a driver/library mismatch and an Xid bus-loss report require different evidence.
- NVIDIA graphics
NVIDIA GeForce GT 1030 reference
A checked GT 1030 reference that leaves memory variants and hybrid-GPU routing to actual board/runtime evidence.
- NVIDIA graphics
NVIDIA GeForce RTX 2080 reference
An RTX 2080 reference with explicit distinctions between vendor module policy, GSP documentation and Nouveau binding.
- NVIDIA graphics
NVIDIA GeForce RTX 3080 reference
A checked RTX 3080 ID for correlating driver-version, initialization and PCIe error reports without inferring a board defect.
- NVIDIA graphics
NVIDIA GeForce RTX 4090 reference
An RTX 4090 reference: GSP version and endpoint/parent link observations add context beyond a supported-chip row.
- NVIDIA graphics
NVIDIA GeForce RTX 5090 reference
A checked RTX 5090 reference with the vendor-documented Blackwell module-flavor boundary and explicit local-evidence limits.
- Intel graphics
Intel Ivy Bridge GT2 mobile
Mobile Ivy Bridge GT2: an i915 table match does not identify the laptop or the renderer an application selected.
- Intel graphics
Intel Haswell GT2 desktop
Haswell desktop GT2 with a clear boundary between early framebuffer output, i915 binding and accelerated applications.
- Intel graphics
Intel Broadwell GT2 ULT
Broadwell GT2 ULT: preserve integrated-display and optional discrete-rendering roles without inferring an OEM notebook.
- Intel graphics
Intel Skylake GT2 desktop
Skylake desktop GT2 with source-backed DMC examples and separate interpretation of GPU hangs and display-power warnings.
- Intel graphics
Intel Ice Lake graphics
An Ice Lake family match with independent kernel binding, firmware-component and connector/EDID checkpoints.
- Intel graphics
Intel Tiger Lake graphics
Tiger Lake appears in i915 and Xe tables; the runtime owner determines which initialization and hang interpretation applies.
- Intel graphics
Intel Alder Lake-P graphics
Alder Lake-P graphics with checked i915/Xe candidates and a DMC filename/fallback distinction.
- Intel graphics
Intel DG2 G10 desktop graphics
DG2 G10 desktop graphics: separate a shared driver-table match from microcontroller initialization and Vulkan discovery.
- Chipsets & PCIe
PCIe root-port context
A topology and native-service context; bridge class alone does not establish an exact motherboard or port type.
- Chipsets & PCIe
PCIe switch-port context
Follow an upstream/downstream switch path before attributing a negotiated link or AER event to an endpoint.
- Chipsets & PCIe
PCIe Root Complex Event Collector
A class-backed RCEC context for error collection from root-complex integrated endpoints.
- Chipsets & PCIe
CXL Type-3 memory-device context
A CXL memory-class context: PCI enumeration, mailbox management and usable system memory are separate stages.
- Chipsets & PCIe
Intel VMD separate PCI domain
A table-backed Intel VMD controller profile that keeps the controller and downstream storage separate.
- Chipsets & PCIe
Intel client VMD controller
A table-backed Intel VMD controller profile that keeps the controller and downstream storage separate.
- Chipsets & PCIe
Intel ICH9 SMBus
A motherboard SMBus host profile with controller-level evidence and passive adapter inspection.
- Chipsets & PCIe
Intel Kaby Lake PCH-H SMBus
A motherboard SMBus host profile with controller-level evidence and passive adapter inspection.
- Chipsets & PCIe
AMD KERNCZ/FCH SMBus
A motherboard SMBus host profile with controller-level evidence and passive adapter inspection.
- Chipsets & PCIe
Intel Sunrise Point MEI function
A checked Management Engine host interface: driver binding does not reveal every firmware client or management feature.
- Chipsets & PCIe
AMD Secure Processor / CCP PCI function
A checked AMD secure-processor function whose crypto and virtualization features depend on separate configuration.
- Chipsets & PCIe
AMD PMC platform sleep context
A module/platform context for AMD s2idle coordination; it is not an exact PCI product-ID match.
- 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.
- Ethernet & networking
Intel 82540EM
A classic Intel gigabit controller handled by e1000. This identity is also frequently presented by virtual machines, so a PCI match does not prove that a physical Intel card is installed.
- Ethernet & networking
Intel 82574L
This discrete Intel controller belongs to the e1000e family. Its numeric identity is useful when an old desktop or server adapter has a misleading human-readable PCI label.
- Ethernet & networking
Intel I217-LM
An Intel PCH LAN generation handled by e1000e. Treat it as a platform-integrated network function; a generic PCI adapter description does not identify the motherboard wiring or management configuration.
- Ethernet & networking
Intel I210 copper
The copper I210 controller is an igb device, including in embedded systems and add-in cards. Linux source distinguishes it from I210 fiber, SerDes and flashless variants.
- Ethernet & networking
Intel I350 copper
I350 copper network functions use igb. Multiport adapters expose separate PCI functions, so identifying one function is not the same as identifying the complete card.
- Ethernet & networking
Intel I225-LM
A newer Intel copper controller generation matched by igc. The verified identifier distinguishes I225-LM from I225-V, I226 and blank-NVM entries in the same driver family.
- Ethernet & networking
Intel 82599 SFP family
An ixgbe 82599 physical-function identity with a pluggable-media path. It is useful for separating an SFP/cable negotiation problem from absence of the network driver.
- Ethernet & networking
Intel X550-T
The X550-T copper path uses ixgbe alongside several other high-speed Intel families. Verify the X550-specific identity instead of choosing configuration solely from the shared module name.
- Ethernet & networking
Intel 700-series SFP function (1572)
This SFP identity belongs to the i40e 700-series family. Its source symbol uses XL710 wording, so the profile keeps a family label rather than asserting an exact retail X710 card model.
- Ethernet & networking
Intel E810-C QSFP function
The E810-C QSFP physical function uses ice. Its DDP package is a separate host-loaded component from the firmware stored on the network adapter.
- Ethernet & networking
Realtek RTL8168 family
Many RTL8168 revisions share one PCI pair. The in-tree candidate is r8169 despite the different final digits; exact revision and PHY behavior require more than the numeric PCI identity.
- Ethernet & networking
Realtek RTL8125 family
The RTL8125 family is handled by the in-tree r8169 driver in this snapshot. Its 2.5-gigabit family capability must be separated from the speed negotiated with a particular switch.
- Ethernet & networking
Realtek RTL8126 family
This RTL8126 family entry exists in the pinned r8169 source. The profile records that source support without inventing a minimum distribution kernel or a tested hardware result.
- Ethernet & networking
Broadcom BCM5720
This NetXtreme/Tigon3 controller identity uses tg3. It is different from the NetXtreme II and NetXtreme-E generations, even when an OEM inventories all of them simply as Broadcom Ethernet.
- Ethernet & networking
Broadcom/QLogic BCM57711
The BCM57711 NetXtreme II generation uses bnx2x and host-loaded initialization firmware. This is a different software path from tg3 gigabit controllers and newer bnxt_en devices.
- Ethernet & networking
Broadcom BCM57414 NetXtreme-E
The BCM57414 NetXtreme-E physical function is handled by bnxt_en. Its source board description spans 10/25-gigabit Ethernet, but current link speed still comes from negotiation and the installed media.
- Ethernet & networking
Mellanox ConnectX-3 / MT27500 family
ConnectX-3 is a core adapter family with a separate Ethernet driver layer. A visible Mellanox PCI function alone does not show whether its configured port is operating as Ethernet or another supported fabric.
- Ethernet & networking
Mellanox ConnectX-4 family
ConnectX-4 belongs to mlx5_core rather than the older mlx4 family. Keep physical-function identification, Ethernet interface creation and optional RDMA operation as separate checks.
- Ethernet & networking
Aquantia/Marvell AQC107
The AQC107 copper controller is an atlantic device. Multi-rate copper capability and the PCIe host connection are separate links, so both can limit a real transfer independently.
- Ethernet & networking
Marvell Yukon 88E8056
This Yukon generation uses sky2. The distinct driver family matters on older motherboards where similar Marvell names can otherwise be confused with skge or newer high-speed controllers.
- Ethernet & networking
Realtek RTL8153 USB Ethernet family
RTL8153-based USB Ethernet uses r8152, even though the chip name ends in 8153. USB transport speed and Ethernet link speed must be inspected separately when a dock feels slow.
- Ethernet & networking
ASIX AX88179 USB Ethernet
The AX88179 USB network controller uses ax88179_178a on its documented vendor-specific interface. A USB ID alone identifies the controller path, not a whole docking station or its negotiated USB generation.
- Storage controllers
Generic PCI AHCI SATA controller
A documented protocol-family profile for a PCI function reporting AHCI class 010601. It offers useful driver context without pretending the class identifies an exact chipset or SSD.
- Storage controllers
Generic PCI NVMe controller
A generic NVMe-over-PCIe protocol profile derived from class 010802. It intentionally stops short of naming a retail SSD because a PCI controller identity can be shared by multiple marketed drives.
- Storage controllers
Intel CPT AHCI function (1c02)
This Intel CPT SATA function has a device-specific ahci entry. Its identity concerns the platform’s SATA controller, not the model of a drive connected to one of its ports.
- Storage controllers
AMD/ATI SB700/SB800 AHCI family
The upstream table labels this AMD/ATI southbridge path as SB700/800 and uses ahci. Keep that documented family scope instead of assigning a specific motherboard from a PCI database label.
- Storage controllers
JMicron JMB362 SATA function
This JMicron JMB36x SATA function is an AHCI driver match. JMicron multifunction controllers can also have a different PATA path, so controller family and individual PCI function must be kept distinct.
- Storage controllers
Silicon Image SiI3112 family
This older Silicon Image SATA controller uses sata_sil rather than ahci. Its source path is useful when a legacy add-in card appears correctly on PCI but no attached ATA device is visible.
- Storage controllers
Silicon Image SiI3132
SiI3132 uses the distinct sata_sil24 controller driver. It should not be grouped with SiI3112 merely because both devices have the Silicon Image vendor identity.
- Storage controllers
Marvell 88SE912x AHCI function (9123)
This Marvell AHCI function needs careful naming: the checked source comments its 9123 entry as 88SE9128. The profile therefore retains a family label rather than inventing an exact chip label.
- Storage controllers
ASMedia ASM1061/ASM1062 family
This ASMedia AHCI family is identified more narrowly than an arbitrary SATA controller, but its upstream comment explicitly spans ASM1061 and ASM1062. It is not a reliable exact marketed-board name.
- Storage controllers
VIA VT6421
The VT6421 is a VIA storage-controller path handled by sata_via. The upstream table describes both SATA and PATA channels, which makes the port type important when reading a mixed legacy system.
- Storage controllers
NVIDIA MCP55 SATA function (037f)
This older NVIDIA chipset SATA function uses sata_nv. NVIDIA’s presence in the PCI vendor field does not make this a graphics device or justify a GPU-driver installation.
- Storage controllers
Promise PDC2037x family (3376)
This Promise function belongs to the PDC2037x implementation of sata_promise. The shared board-family path is more defensible than deriving a precise retail adapter name from a nearby model number.
- Storage controllers
LSI SAS2008
SAS2008 is a Fusion-MPT SAS2 controller family. The pinned source handles it inside mpt3sas, while legacy mpt2sas naming can still appear in its internal driver/proc identity.
- Storage controllers
LSI/Broadcom SAS3008
SAS3008 is a newer Fusion-MPT SAS3 controller identity handled by mpt3sas. SAS port capability, an expander’s topology and each drive’s negotiated link are separate pieces of evidence.
- Storage controllers
Broadcom/LSI SAS3416
This SAS3416 identity is a distinct MPI2.6-era controller path in mpt3sas. Do not infer an exact OEM tri-mode board or the transport of attached devices solely from the controller family.
- Storage controllers
LSI/Broadcom MegaRAID Fusion function (005b)
This is the MegaRAID Fusion identity in megaraid_sas. RAID firmware can expose logical volumes whose block-device model strings do not identify the underlying physical disks.
- Storage controllers
Adaptec AAC RAID family (0285)
This Adaptec AAC pair deliberately identifies a family, not one card. The upstream table and guide list many different boards distinguished by their subsystem IDs under the same 9005:0285 pair.
- Storage controllers
Virtio block device context
A protocol/device-family context for virtio block storage in a guest. It deliberately has no exact PCI identity: virtio can use different transports and does not identify the host’s physical SSD or RAID controller.
- USB controllers & peripherals
PCI XHCI host-controller class
PCI xHCI host controllers expose USB 2 and SuperSpeed topology through one controller family.
- USB controllers & peripherals
PCI EHCI host-controller class
PCI EHCI is the USB 2 high-speed host-controller family used alongside older companion controllers.
- USB controllers & peripherals
PCI OHCI host-controller class
PCI OHCI provides a standardized USB 1.1 controller path for low- and full-speed peripherals.
- USB controllers & peripherals
PCI UHCI host-controller class
PCI UHCI is a USB 1.1 controller architecture commonly encountered on older systems and virtual machines.
- USB controllers & peripherals
USB hub class
A hub is both an upstream USB function and the branching point for downstream devices.
- USB controllers & peripherals
USB Video Class camera interfaces
UVC describes camera control and streaming interfaces, separate from any microphone in the same webcam.
- USB controllers & peripherals
USB mass storage: Bulk-Only Transport
Bulk-Only Transport carries storage commands through a USB interface before the block device appears.
- USB controllers & peripherals
USB Attached SCSI interfaces
UAS is a USB storage transport with command queues and endpoint requirements beyond the mass-storage class label.
- USB controllers & peripherals
FTDI USB serial identity 0403:6001
A USB-to-serial family match whose tty association still needs runtime evidence.
- USB controllers & peripherals
Silicon Labs default USB serial identity 10c4:ea60
A USB-to-serial family match whose tty association still needs runtime evidence.
- Audio devices
Intel Cougar Point HDA controller
A PCI HDA controller identity from Intel’s Cougar Point family, with a separately enumerated audio codec.
- Audio devices
AMD HDA controller identity 1022:1487
An AMD PCI HDA controller identity that upstream labels for X570 and related systems.
- Audio devices
Realtek ALC892 HDA codec family
An HDA codec family for analog audio; its identity must be read from the codec layer.
- Audio devices
HDA HDMI/DisplayPort audio codecs
Display audio adds a codec route whose availability depends on a connected display’s audio capabilities.
- Audio devices
USB Audio Class PCM interfaces
USB audio uses control, clock and streaming descriptors rather than a universal sound-card chipset ID.
- Audio devices
USB MIDI streaming interfaces
A MIDI interface transports musical events and can work without any PCM playback device.
- Audio devices
Ensoniq ES1371 AudioPCI family
A legacy AudioPCI controller family also encountered as emulated audio hardware.
- Audio devices
Creative EMU10K1 PCI audio family
A programmable PCI audio family whose mixer and internal routing need attention beyond PCI detection.
- Audio devices
C-Media CM8738 PCI audio family
A legacy C-Media PCI audio family with analog and revision-dependent digital routing.
- Audio devices
Intel 82801AA AC97 controller
An Intel ICH AC97 controller path, distinct from HDA and frequently emulated for guests.
- Input & other peripherals
USB HID keyboard and pointer transport
USB HID is a transport and report-description family shared by many input devices.
- Input & other peripherals
HID over I2C touchpad and touchscreen transport
An internal I2C HID path can expose touch input without any USB device entry.
- Input & other peripherals
i8042 / PS2 keyboard and pointer transport
The legacy controller exposes serio ports rather than ordinary USB interfaces.
- Input & other peripherals
Logitech Unifying receiver identity 046d:c52b
One wireless receiver can create several paired HID input devices behind a single USB identity.
- Input & other peripherals
Wacom USB tablet identity 056a:00b9
The checked tablet profile separates pen capabilities from application mapping and display geometry.
- Input & other peripherals
HID multitouch protocol family
Multitouch support is a specialized HID interpretation layered over transports such as USB or I2C.
- Input & other peripherals
ALPS PS2 touchpad protocol family
ALPS PS2 touchpads use protocol detection above serio, rather than a USB VID/PID table.
- Input & other peripherals
Xbox 360 wired USB identity 045e:028e
A wired Xbox-compatible controller identity with a vendor-specific USB protocol rather than generic keyboard HID.
- Virtual & unusual hardware
Virtio network function over modern PCI
A paravirtual network interface with a guest function driver distinct from the PCI transport.
- Virtual & unusual hardware
Virtio console and ports over modern PCI
A virtual console/port function can expose named guest-host channels rather than a physical UART.
- Virtual & unusual hardware
Virtio random-source function over modern PCI
A guest random-source device imports bytes from a host-provided backend.
- Virtual & unusual hardware
Virtio memory balloon over modern PCI
Ballooning is a guest-host memory-management function, not an ordinary RAM identification device.
- Virtual & unusual hardware
Virtio SCSI adapter over modern PCI
A virtual SCSI host adapter can present several targets behind one virtio controller.
- Virtual & unusual hardware
Virtio 9P filesystem transport over modern PCI
A 9P export is a guest-host filesystem transport with an explicit mount tag.
- Virtual & unusual hardware
Virtio GPU over modern PCI
A virtual DRM device can provide display and render capabilities without identifying the physical host GPU.
- Virtual & unusual hardware
Virtio input over modern PCI
A virtual input function receives host-provided event capabilities rather than a USB keyboard model.
- Virtual & unusual hardware
Virtio socket transport over modern PCI
Virtual sockets communicate using context IDs rather than an ordinary Ethernet interface or IP address.
- Virtual & unusual hardware
Virtio sound over modern PCI
A paravirtual audio function exposes guest ALSA streams while the physical audio backend remains on the host.
- Wi-Fi adapters
Intel Wireless 7265 family
A 7265-family PCIe radio whose original and D revisions use different firmware branches. Read the detected revision before interpreting a missing firmware message.
- Wi-Fi adapters
Intel 8265 / 8275 PCIe family
An Intel 8000-generation PCIe family that shares driver machinery while subsystem IDs distinguish several board and product names.
- Wi-Fi adapters
Intel Wireless-AC 9260 family
A PCIe 9000-generation Intel radio. Its transport and RF configuration are selected separately, which is why a family match is less precise than the detected controller details.
- Wi-Fi adapters
Intel AX200 PCIe family
A discrete Intel Wi-Fi 6 PCIe family. Wi-Fi enumeration and a combo module’s USB Bluetooth enumeration provide different evidence.
- Wi-Fi adapters
Intel AX210 PCIe family
A discrete Intel Wi-Fi 6E PCIe family with a Ty transport configuration and a GF radio selection. Radio capability and local regulatory availability remain separate.
- Wi-Fi adapters
Intel BE200-class PCIe family
A discrete Intel Wi-Fi 7 family using the GL transport and FM radio path. A Wi-Fi 7 source entry is a starting point for diagnosis, not a feature-completeness rating.
- Wi-Fi adapters
Realtek RTL8723BE
An older Realtek PCIe family using rtlwifi rather than rtw88 or rtw89. Its primary and alternate firmware names are explicitly different.
- Wi-Fi adapters
Realtek RTL8821CE
An rtw88 PCIe controller. The transport module carries the CE suffix while the shared chip firmware uses the C name.
- Wi-Fi adapters
Realtek RTL8822CE
An rtw88 8822C controller over PCIe. Normal operation and wake-on-wireless have distinct firmware declarations.
- Wi-Fi adapters
Realtek RTL8852BE
An rtw89 PCIe family whose firmware format suffix follows the driver’s supported format, not a retail adapter label.
- Wi-Fi adapters
Realtek RTL8852CE
A separate rtw89 8852C PCIe family. Similar names in the 8852B branch do not make their firmware interchangeable.
- Wi-Fi adapters
Realtek RTL8822BU USB family
An upstream rtw88 USB route for the 8822B family. USB interface descriptors participate in matching, so the product pair alone is incomplete evidence.
- Wi-Fi adapters
Atheros ath9k PCIe family (168c:002b)
A register-driven ath9k PCIe family. Unlike ath9k_htc USB devices, its reviewed path does not declare a host-loaded firmware image.
- Wi-Fi adapters
Atheros AR9271 USB family
A USB Atheros radio that loads HTC firmware before normal wireless operation. USB presence and a working Wi-Fi interface are separate stages.
- Wi-Fi adapters
Qualcomm Atheros QCA6174 family
An ath10k PCIe family requiring revision-specific firmware and board data. Board calibration is a separate input from the shared firmware image.
- Wi-Fi adapters
Qualcomm QCA6390 PCIe family
An ath11k PCIe device with an MHI/QMI-backed initialization path. A visible PCI function may still be waiting for target firmware or board data.
- Wi-Fi adapters
Qualcomm WCN6855 PCIe family
An ath11k PCIe family with separate hw2.0 and hw2.1 firmware mappings. One PCI pair does not distinguish those firmware branches.
- Wi-Fi adapters
Qualcomm QCN9274 PCIe family
A Qualcomm Wi-Fi 7 family whose reviewed kernel separates the shared ath12k core from the ath12k_wifi7 device implementation.
- Wi-Fi adapters
MediaTek MT7601U USB family
A MediaTek USB radio using its own mt7601u driver, rather than the mt76x2 or mt7921 transport modules.
- Wi-Fi adapters
MediaTek MT7612U / MT76x2 USB family
An mt76x2 USB radio whose source uses MT7662-named firmware components even when the USB family is described as MT7612U.
- Wi-Fi adapters
MediaTek MT7921 PCIe family
An MT7921-family PCIe radio. The mt7921 driver directory also contains other chip families, so its directory name is not enough to identify a device.
- Wi-Fi adapters
MediaTek MT7922 PCIe family
An MT7922-family PCIe route handled by mt7921e. A different chip family can legitimately share the same module name.
- Wi-Fi adapters
MediaTek MT7925 PCIe family
An MT7925-family PCIe device with firmware stored in a chip-specific mediatek subdirectory in the reviewed source.
- Wi-Fi adapters
MediaTek MT7921 USB family
An MT7921 family over USB, sharing firmware names with the PCIe family while using a different host transport.
- Wi-Fi adapters
Broadcom BCM4313 / BCMA Wi-Fi family
A Broadcom PCIe host exposed through BCMA to the brcmsmac wireless core. The host bridge binding and radio-driver binding are different layers.
- Wi-Fi adapters
Broadcom BCM43602 PCIe FullMAC family
A Broadcom FullMAC PCIe family with firmware and board-specific NVRAM handling. FullMAC places more wireless behavior in target firmware than brcmsmac.
- Wi-Fi adapters
Broadcom BCM4356 PCIe FullMAC family
A PCIe Broadcom FullMAC family with a checked firmware basename and a separate CLM regulatory-data declaration.
- Wi-Fi adapters
Broadcom BCM43236 USB FullMAC family
A Broadcom FullMAC radio over USB with a chip-revision-specific 43236B firmware branch and a re-enumeration stage.
- Bluetooth
USB Bluetooth HCI transport class
A generic USB interface context for Bluetooth HCI. It can explain why btusb is a candidate without pretending to identify a chipset.
- Bluetooth
Intel USB Bluetooth family (8087:0032)
An Intel USB controller route using the combined Intel setup path. Its firmware naming depends on controller version fields, not only its USB product number.
- Bluetooth
Realtek RTL8761BU-class USB Bluetooth
A Realtek USB family with a BU firmware route that differs from the UART B branch. The USB/UART distinction changes the expected filename.
- Bluetooth
MediaTek USB Bluetooth family (0e8d:0608)
A MediaTek USB Bluetooth route whose helper reads controller registers to choose a ROM-patch filename. It is not identified from a Wi-Fi PCI label.
- Bluetooth
Broadcom BCM20702B0-class USB Bluetooth
A Broadcom USB family with PatchRAM setup. Board and USB product details can influence the HCD filename chosen after controller identification.
- Bluetooth
Atheros AR3011 USB firmware-loader family
An Atheros USB identity used by the firmware loader before the normal HCI transport stage. Firmware loading can lead to USB re-enumeration.
- Bluetooth
Atheros AR3012 USB patch/sysconfig family
An Atheros USB loading path using both a ROM-version patch and a reference-clock-specific system configuration.
- Bluetooth
Bluetooth H4 UART transport context
A serial HCI transport context for an embedded Bluetooth controller. A UART-connected controller can exist without appearing in lspci or lsusb.
- Bluetooth
Bluetooth H5 three-wire UART context
A reliable three-wire UART transport context with packet sequencing and link establishment. It differs from H4 framing despite sharing the hci_uart module.
- Bluetooth
Qualcomm Bluetooth UART family context
A Qualcomm serial Bluetooth family context with vendor startup, baud-rate control and firmware/NVM loading. Its identity can come from ACPI or device tree rather than PCI/USB IDs.
- Bluetooth
Broadcom Bluetooth UART family context
A Broadcom serial Bluetooth family context using board power/reset resources and optional PatchRAM. USB Bluetooth matching does not identify this UART path.
- Bluetooth
Bluetooth SDIO HCI transport context
A generic Bluetooth HCI transport over SDIO. Embedded SDIO functions normally live outside PCI and USB inventories.
One observation at a time
Choose a hardware path. Each workflow distinguishes observations and hypotheses, shows read-only checks and links to matching Fix Lab guides.
Diagnostic topics without JavaScript
- GPU detected, binding unclear — Read the Fix Lab knowledge base
- AMDGPU firmware request failed — Read the Fix Lab knowledge base
- NVIDIA module is not usable — Read the Fix Lab knowledge base
- Intel graphics initialization — Read the Fix Lab knowledge base
- Wi-Fi adapter unavailable — Read the Fix Lab knowledge base
- Ethernet controller without usable link — Read the Fix Lab knowledge base
- PCIe speed or width below expectation — Read the Fix Lab knowledge base
- Repeated USB disconnects — Read the Fix Lab knowledge base
- NVMe timeout or controller reset — Read the Fix Lab knowledge base
- SATA CRC or link resets — Read the Fix Lab knowledge base
- Bluetooth firmware or transport — Read the Fix Lab knowledge base
- Audio controller but no usable card — Read the Fix Lab knowledge base
- Kernel module unavailable — Read the Fix Lab knowledge base
- Device disappears after suspend — Read the Fix Lab knowledge base
- Find a missing firmware payload — Read the Fix Lab knowledge base
- Windows detects it, Linux does not — Read the Fix Lab knowledge base
- Hardware or software radio block — Read the Fix Lab knowledge base
- IOMMU or PCIe initialization fault — Read the Fix Lab knowledge base
Understand the driver layers
Detected, bound, operational: three different facts
Understand PCI/USB enumeration, driver probing and runtime binding before interpreting a driver recommendation.
Kernel modules and built-in drivers
Separate module availability, kernel build configuration, loaded modules and the driver bound to one device.
Firmware requests and actual payloads
Use requested filenames and initialization evidence to distinguish firmware-loading errors from unrelated symptoms.
What a PCI or USB modalias establishes
Decode bus identifiers and interface context without mistaking a wildcard module alias for one real device.
GPU kernel drivers, firmware and userspace
Separate AMD, Intel and NVIDIA binding evidence from rendering APIs, firmware and application selection.
USB devices and interface drivers
Understand composite devices, class matching and the difference between descriptor identity and interface binding.
PCIe capability, negotiated link and topology
Read endpoint and bridge observations without treating marketing generation or a downgraded link as a unique cause.
What this catalog knows — and what it cannot prove
Understand exact IDs, qualified matches, class context, source dates and the limits of hardware compatibility claims.
Inspect firmware packaging on six distributions
Use read-only packaging checks for Debian, Ubuntu, Fedora, Arch Linux, NixOS and Gentoo without guessing an installation fix.
Private reports and public hardware links
Separate temporary local report analysis from shareable device profiles, diagnostic summaries and redacted excerpts.