User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:76.0) Gecko/20100101 Firefox/76.0 Build Identifier: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter is recognized but is not working. I have not yet found a way to get the WiFi card to function properly. This is detected with lspci, but not activated by the system. Reproducible: Always Steps to Reproduce: 1. Boot System Actual Results: WiFi not working Expected Results: Activate Wifi and function correctly [user@localhost ~]$ lspci | grep -i wireless 01:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) [user@localhost ~]$ dmesg |grep ath10 [ 11.285490] ath10k_pci 0000:01:00.0: enabling device (0000 -> 0002) [ 11.289344] ath10k_pci 0000:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [ 11.517145] ath10k_pci 0000:01:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 144d:c14f [ 11.517148] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0 [ 11.518181] ath10k_pci 0000:01:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1 [ 11.586406] ath10k_pci 0000:01:00.0: board_file api 2 bmi_id N/A crc32 4ac0889b [ 11.714071] ath10k_pci 0000:01:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [ 11.778997] ath10k_pci 0000:01:00.0: failed to initialise regulatory: -22 [ 11.778999] ath10k_pci 0000:01:00.0: could not register to mac80211 (-22)
I THINK I have the same problem on my 'Qualcomm Atheros Communications AR9271 802.11n(0cf3:9271), it worked fine on kernel 5.6.16-200.fc31.x86_64 but not on 5.7.7-100.fc31.x86_64.
I'm seeing the same problem. My wifi device works on kernel 5.6.18-300, but not on 5.7.6 or 5.7.8. Here's what I get from lspci -vvv: 07:00.0 Ethernet controller: Qualcomm Atheros Killer E2500 Gigabit Ethernet Controller (rev 10) Subsystem: Acer Incorporated [ALI] Device 1343 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 16 Region 0: Memory at b4300000 (64-bit, non-prefetchable) [size=256K] Region 2: I/O ports at 3000 [size=128] Capabilities: <access denied> Kernel driver in use: alx Kernel modules: alx When running under 5.7.8, looking in journalctl output, here are some things that might be relevant: Jul 15 06:25:07 sikanda kernel: alx 0000:07:00.0 eth0: Qualcomm Atheros AR816x/AR817x Ethernet [7c:d3:0a:80:be:90] Jul 15 06:25:07 sikanda kernel: nvme nvme0: 12/0/0 default/read/poll queues Jul 15 06:25:07 sikanda kernel: nvme0n1: p1 p2 p3 p4 Jul 15 06:25:07 sikanda systemd-udevd[445]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. Jul 15 06:25:07 sikanda systemd-udevd[443]: Using default interface naming scheme 'v245'. Jul 15 06:25:07 sikanda kernel: pcieport 0000:00:1d.0: AER: Corrected error received: 0000:07:00.0 Jul 15 06:25:07 sikanda kernel: alx 0000:07:00.0: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Jul 15 06:25:07 sikanda kernel: alx 0000:07:00.0: AER: device [1969:e0b1] error status/mask=00000040/00002000 Jul 15 06:25:07 sikanda kernel: alx 0000:07:00.0: AER: [ 6] BadTLP Jul 15 06:25:07 sikanda kernel: pcieport 0000:00:1d.0: AER: Corrected error received: 0000:07:00.0 Jul 15 06:25:07 sikanda kernel: pcieport 0000:00:1d.0: AER: Corrected error received: 0000:07:00.0 Jul 15 06:25:07 sikanda kernel: alx 0000:07:00.0: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Jul 15 06:25:07 sikanda kernel: alx 0000:07:00.0: AER: device [1969:e0b1] error status/mask=00000040/00002000 Jul 15 06:25:07 sikanda kernel: alx 0000:07:00.0: AER: [ 6] BadTLP Jul 15 06:25:07 sikanda systemd-udevd[443]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. Jul 15 06:25:07 sikanda kernel: alx 0000:07:00.0 enp7s0: renamed from eth0 Jul 15 06:25:07 sikanda kernel: pcieport 0000:00:1d.0: AER: Corrected error received: 0000:07:00.0 Jul 15 06:25:07 sikanda kernel: alx 0000:07:00.0: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Jul 15 06:25:07 sikanda kernel: alx 0000:07:00.0: AER: device [1969:e0b1] error status/mask=00000040/00002000 Jul 15 06:25:07 sikanda kernel: alx 0000:07:00.0: AER: [ 6] BadTLP Jul 15 06:25:07 sikanda kernel: pcieport 0000:00:1d.0: AER: Multiple Corrected error received: 0000:07:00.0 However, similar items show up in journalctl under 5.6.18: ul 15 06:29:23 sikanda kernel: alx 0000:07:00.0 eth0: Qualcomm Atheros AR816x/AR817x Ethernet [7c:d3:0a:80:be:90] Jul 15 06:29:23 sikanda kernel: input: ELAN0504:00 04F3:3091 Mouse as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN0504:00/0018:04F3:3091.0001/input/input5 Jul 15 06:29:23 sikanda kernel: input: ELAN0504:00 04F3:3091 Touchpad as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN0504:00/0018:04F3:3091.0001/input/input7 Jul 15 06:29:23 sikanda kernel: hid-generic 0018:04F3:3091.0001: input,hidraw0: I2C HID v1.00 Mouse [ELAN0504:00 04F3:3091] on i2c-ELAN0504:00 Jul 15 06:29:23 sikanda systemd-udevd[514]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. Jul 15 06:29:23 sikanda kernel: nvme nvme0: pci function 0000:06:00.0 Jul 15 06:29:23 sikanda systemd-udevd[515]: Using default interface naming scheme 'v245'. Jul 15 06:29:23 sikanda systemd-udevd[515]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. Jul 15 06:29:23 sikanda kernel: pcieport 0000:00:1d.0: AER: Corrected error received: 0000:07:00.0 Jul 15 06:29:23 sikanda kernel: alx 0000:07:00.0: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Jul 15 06:29:23 sikanda kernel: alx 0000:07:00.0: AER: device [1969:e0b1] error status/mask=00000040/00002000 Jul 15 06:29:23 sikanda kernel: alx 0000:07:00.0: AER: [ 6] BadTLP Jul 15 06:29:23 sikanda kernel: pcieport 0000:00:1d.0: AER: Corrected error received: 0000:07:00.0 Jul 15 06:29:23 sikanda kernel: pcieport 0000:00:1d.0: AER: Corrected error received: 0000:07:00.0 Jul 15 06:29:23 sikanda kernel: alx 0000:07:00.0: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Jul 15 06:29:23 sikanda kernel: alx 0000:07:00.0: AER: device [1969:e0b1] error status/mask=00000040/00002000 Jul 15 06:29:23 sikanda kernel: alx 0000:07:00.0: AER: [ 6] BadTLP Jul 15 06:29:23 sikanda kernel: alx 0000:07:00.0 enp7s0: renamed from eth0 Jul 15 06:29:23 sikanda kernel: pcieport 0000:00:1d.0: AER: Corrected error received: 0000:07:00.0 Jul 15 06:29:23 sikanda kernel: alx 0000:07:00.0: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Jul 15 06:29:23 sikanda kernel: alx 0000:07:00.0: AER: device [1969:e0b1] error status/mask=00000040/00002000 Jul 15 06:29:23 sikanda kernel: alx 0000:07:00.0: AER: [ 6] BadTLP Jul 15 06:29:23 sikanda kernel: pcieport 0000:00:1d.0: AER: Corrected error received: 0000:07:00.0 Jul 15 06:29:23 sikanda kernel: alx 0000:07:00.0: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Jul 15 06:29:23 sikanda kernel: alx 0000:07:00.0: AER: device [1969:e0b1] error status/mask=00000080/00002000 Jul 15 06:29:23 sikanda kernel: alx 0000:07:00.0: AER: [ 7] BadDLLP
Hmm seems to be a problem with the chipset "driver". I hope this gets fixed soon, I don't want to upgrade my kernal at this time, due to this issue.
Try to follow this guide: https://askubuntu.com/a/718430 .There is a board.bin from 2016 that seems to work fine with my 5.7.1 kernel. I found it when my QCA6174 on redmibook suddenly stoped discovering networks (but before it worked with 5.7.1 fine, I don't know what was the reason of the beginning of this behavior).
No such luck for me but I have a sliglty diffrent device(Bus 001 Device 010: ID 0cf3:9271 Qualcomm Atheros Communications AR9271 802.11n) that uses the same package. For me on the newer kernals it does not up show on "ifconfig" and actually needs to be unplugged(it's USB) befor it works again. In fact BIOS locks up "detecting USB devices" for a good 30 secounds so I dont' know what the new kernal "does" to the device. (I think the firmware is applied each time you connect it, which is handy for allowing the firmware to easily change but does cause bugs).
Work for me in FC33.
Oh, wait this could be the same kernel version? 5.6.16-200.fc31.x86_64
I have confirmed this works for me in the latest kernel in FC33, steppenwolf, you still having this issue?
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 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.