Overview & identity
8086:2526 is an iwlwifi 9000-family entry. The controller name and bandwidth selection also use RF information; an OEM badge is not inferred from the numeric pair.
- Curated identifiers
pci 8086:2526
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
The source separates the 9000 MAC configuration from JF radio variants. Use the actual iwlwifi initialization log to distinguish an unsuccessful firmware request from later authentication failures.
iwlwifi— kernel driver/module candidate
Firmware
Host-loaded firmware required
The configuration declares these filename branches. Revision and the running driver determine the requested API file; use that exact log entry.
Checked examples or filename branches, not a complete installation list:
iwlwifi-9260-th-b0-jf-b0-*.ucode
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 selected PCI function
lspci -nnk -s BDFReplace BDF with the address from your report. Compare Kernel driver in use with Kernel modules; only the former records binding. This ordinary query normally needs no root privileges.
Read firmware metadata
modinfo -F firmware MODULEReplace MODULE with iwlwifi or the actual candidate module in your report. Metadata lists declared filenames; it does not prove a file was loaded. This query needs no root privileges.
Read existing Wi-Fi association
iw dev INTERFACE linkReplace INTERFACE with the wireless interface from iw dev. Association and rate are observations, not a throughput or firmware test. This query normally needs no root privileges.
Limitations & related issues
Presence in the PCI table does not certify every subsystem, power transition or access point. Bluetooth on a combo module is a separate controller path.
These guides are linked for relevant observations, not as known defects of every device in this family.
- Wi-Fi blocked by rfkill or airplane mode · First documented next step
- Wi-Fi driver cannot load compatible firmware · First documented next step
- Wi-Fi authentication loops or fails · First documented next step
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.
- Linux source: drv.c
Reviewed upstream source
line 470 - Linux source: 9000.c
Reviewed upstream source
- Linux source: pci_ids.h
Reviewed upstream source
line 2696 - Linux Wireless: read wireless link state
Project or distribution documentation