Overview & identity
168c:003e resolves through QCA6174_2_1_DEVICE_ID in the source. The PCI table and runtime chip checks cover several hardware revisions, so the macro name alone does not fix a revision.
- Curated identifiers
pci 168c:003e
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
ath10k_pci is the transport candidate. Firmware and board-data directories depend on the detected hardware revision; keep the board identity from the initialization log.
ath10k_pci— kernel driver/module candidate
Firmware
Host-loaded firmware required
The checked firmware directory or filename is family/revision specific. The complete requested files and board data must be read from the running system.
Checked examples or filename branches, not a complete installation list:
ath10k/QCA6174/hw2.1/*ath10k/QCA6174/hw3.0/*
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 ath10k_pci 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
An ath10k module or PCI match does not validate OEM calibration data. Use actual failed filenames and board-key messages instead of choosing a board file by marketing name.
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: pci.c
Reviewed upstream source
- Linux source: hw.h
Reviewed upstream source
- Linux source: pci_ids.h
Reviewed upstream source
line 2367 - Linux Wireless: read wireless link state
Project or distribution documentation
- Linux source: Makefile
Reviewed upstream source
line 28