Description of problem: When starting f22_Beta_TC6 installation on Acre V15, anaconda does not load wireless adapter firmware. Version-Release number of selected component (if applicable): F22_Beta_TC6 How reproducible: Everytime Steps to Reproduce: 1. Start F22_Beta_TC6 in rescue mode 2. Type lspci -v and see that the wireless adapter is connected to the ath10k kernel module 3. ifconfig -a does not show the wireless adapter 4. dmesg shows firmware load error. Actual results: Anaconda does not configure and use the wireless adapter. Expected results: Anaconda should configure and use the wireless adapter. Additional info: lspci shows the following information: 03:00.0 Network controller: Qualcomm Atheros Killer N1525 Wireless-AC (rev 20) Subsystem: Foxconn International, Inc. Device e08e Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 50 Region 0: Memory at c4000000 (64-bit, non-prefetchable) [size=2M] Capabilities: [40] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [50] MSI: Enable+ Count=8/8 Maskable+ 64bit- Address: fee00518 Data: 0000 Masking: 00000000 Pending: 00000000 Capabilities: [70] Express (v2) Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 <64us ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <4us, L1 <64us ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+ LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Not Supported, TimeoutDis+, LTR+, OBFF Via message DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [100 v2] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr- CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn- Capabilities: [148 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb: Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff Status: NegoPending- InProgress- Capabilities: [168 v1] Device Serial Number 00-00-00-00-00-00-00-00 Capabilities: [178 v1] Latency Tolerance Reporting Max snoop latency: 3145728ns Max no snoop latency: 3145728ns Capabilities: [180 v1] L1 PM Substates L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+ PortCommonModeRestoreTime=50us PortTPowerOnTime=10us Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci dmesg shows the following information: [ 0.949348] pci 0000:03:00.0: [168c:003e] type 00 class 0x028000 [ 0.949386] pci 0000:03:00.0: reg 0x10: [mem 0xc4000000-0xc41fffff 64bit] [ 0.949590] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold [ 0.949640] pci 0000:03:00.0: System wakeup disabled by ACPI [ 4.718135] pci 0000:03:00.0: Signaling PME through PCIe PME interrupt [ 22.616014] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0 [ 22.842480] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/cal-pci-0000:03:00.0.bin failed with error -2 [ 22.842493] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/QCA6174/hw2.1/firmware-4.bin failed with error -2 [ 22.842496] ath10k_pci 0000:03:00.0: could not fetch firmware file 'ath10k/QCA6174/hw2.1/firmware-4.bin': -2 [ 22.842504] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/QCA6174/hw2.1/firmware-3.bin failed with error -2 [ 22.842506] ath10k_pci 0000:03:00.0: could not fetch firmware file 'ath10k/QCA6174/hw2.1/firmware-3.bin': -2 [ 22.842513] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/QCA6174/hw2.1/firmware-2.bin failed with error -2 [ 22.842515] ath10k_pci 0000:03:00.0: could not fetch firmware file 'ath10k/QCA6174/hw2.1/firmware-2.bin': -2 [ 22.842523] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/QCA6174/hw2.1/board.bin failed with error -2 [ 22.842526] ath10k_pci 0000:03:00.0: could not fetch board data (-2) [ 22.842528] ath10k_pci 0000:03:00.0: could not fetch firmware files (-2) [ 22.842529] ath10k_pci 0000:03:00.0: could not probe fw (-2)
I encountered a similar situation on an Aspire V17 Nitro (VN7-791G). No WiFI and no Bluetooth. This is the device: 07:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 20) Subsystem: Foxconn International, Inc. Device e08e Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx+ Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 35 Region 0: Memory at d1400000 (64-bit, non-prefetchable) [size=2M] Capabilities: [40] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [50] MSI: Enable+ Count=8/8 Maskable+ 64bit- Address: fee00518 Data: 0000 Masking: 00000000 Pending: 00000000 Capabilities: [70] Express (v2) Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 <64us ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <4us, L1 <64us ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+ LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk- ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Not Supported, TimeoutDis+, LTR+, OBFF Via message DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [100 v2] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr+ BadTLP+ BadDLLP+ Rollover- Timeout+ NonFatalErr- CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn- Capabilities: [148 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb: Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff Status: NegoPending- InProgress- Capabilities: [168 v1] Device Serial Number 00-00-00-00-00-00-00-00 Capabilities: [178 v1] Latency Tolerance Reporting Max snoop latency: 71680ns Max no snoop latency: 71680ns Capabilities: [180 v1] L1 PM Substates L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+ PortCommonModeRestoreTime=50us PortTPowerOnTime=10us Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci While searching for a solution, I came across these two threads: https://bbs.archlinux.org/viewtopic.php?id=196519 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184 I could not find any newer firmware files over at kernel.org, so I downloaded the ones provided in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184/comments/244 copied them to /usr/lib/firmware/ and I added an ath10k.conf file in /etc/modprobe.d/ with options ath10k_core skip_otp=y Wireless is working now, BT still doesn't. The following is from before the addition of the firmware files: [ 7.019027] ath10k_pci 0000:07:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0 [ 7.166269] ath10k_pci 0000:07:00.0: Direct firmware load for ath10k/cal-pci-0000:07:00.0.bin failed with error -2 [ 7.166281] ath10k_pci 0000:07:00.0: Direct firmware load for ath10k/QCA6174/hw2.1/firmware-4.bin failed with error -2 [ 7.166283] ath10k_pci 0000:07:00.0: could not fetch firmware file 'ath10k/QCA6174/hw2.1/firmware-4.bin': -2 [ 7.166290] ath10k_pci 0000:07:00.0: Direct firmware load for ath10k/QCA6174/hw2.1/firmware-3.bin failed with error -2 [ 7.166292] ath10k_pci 0000:07:00.0: could not fetch firmware file 'ath10k/QCA6174/hw2.1/firmware-3.bin': -2 [ 7.166298] ath10k_pci 0000:07:00.0: Direct firmware load for ath10k/QCA6174/hw2.1/firmware-2.bin failed with error -2 [ 7.166299] ath10k_pci 0000:07:00.0: could not fetch firmware file 'ath10k/QCA6174/hw2.1/firmware-2.bin': -2 [ 7.166306] ath10k_pci 0000:07:00.0: Direct firmware load for ath10k/QCA6174/hw2.1/board.bin failed with error -2 [ 7.166307] ath10k_pci 0000:07:00.0: could not fetch board data (-2) [ 7.166309] ath10k_pci 0000:07:00.0: could not fetch firmware files (-2) [ 7.166310] ath10k_pci 0000:07:00.0: could not probe fw (-2) And after: [ 3.687802] ath10k_pci 0000:07:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0 [ 3.834484] ath10k_pci 0000:07:00.0: Direct firmware load for ath10k/cal-pci-0000:07:00.0.bin failed with error -2 [ 3.834779] ath10k_pci 0000:07:00.0: Direct firmware load for ath10k/QCA6174/hw2.1/firmware-4.bin failed with error -2 [ 3.834781] ath10k_pci 0000:07:00.0: could not fetch firmware file 'ath10k/QCA6174/hw2.1/firmware-4.bin': -2 [ 3.834789] ath10k_pci 0000:07:00.0: Direct firmware load for ath10k/QCA6174/hw2.1/firmware-3.bin failed with error -2 [ 3.834790] ath10k_pci 0000:07:00.0: could not fetch firmware file 'ath10k/QCA6174/hw2.1/firmware-3.bin': -2 [ 5.044991] ath10k_pci 0000:07:00.0: qca6174 hw2.1 (0x05010000, 0x003405ff) fw rome-hw2.1-v211-michalk api 2 htt 3.0 wmi 4 cal otp max_sta 32 [ 5.044995] ath10k_pci 0000:07:00.0: debug 0 debugfs 1 tracing 0 dfs 0 testmode 0 [ 5.118459] ath10k_pci 0000:07:00.0 wlp7s0: renamed from wlan0 So, probably something is still missing. I'll have this laptop for a few weeks, so if you need me to do any additional tests, please let me know.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.