Nothing on the wireless but its not surprising since the firmware file seems to be missing... did i forgot a package? tried linux-firmware without any luck. the two Gigabit port works but network seems to be slow to connect at first, sometime it takes longer and i've seen a disconnect after moving my tower a bit it also takes time to reconnect. i wonder if it could be related to the sudo command & google chrome app that also takes time to start... i have a Gigabyte motherboard Z170X-Gaming G1 with i7-6700k and 16gig of ram... 06:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32) 0d:00.0 Ethernet controller [0200]: Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller [1969:e0a1] (rev 10) 0e:00.0 Ethernet controller [0200]: Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller [1969:e0a1] (rev 10) [ 8.641135] ath10k_pci 0000:06:00.0: pci irq msi interrupts 1 irq_mode 0 reset_mode 0 [ 9.063386] ath10k_pci 0000:06:00.0: Direct firmware load for ath10k/cal-pci-0000:06:00.0.bin failed with error -2 [ 9.063921] ath10k_pci 0000:06:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2 [ 9.063923] ath10k_pci 0000:06:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2 [ 9.209430] ath10k_pci 0000:06:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/board-2.bin failed with error -2 [ 11.347297] ath10k_pci 0000:06:00.0: qca6174 hw3.2 (0x05030000, 0x00340aff sub 1a56:1535) fw WLAN.RM.2.0-00180-QCARMSWPZ-1 fwapi 4 bdapi 1 htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 features wowlan,ignore-otp,no-4addr-pad [ 11.347306] ath10k_pci 0000:06:00.0: debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [ 12.465743] ath10k_pci 0000:06:00.0 wlp6s0: renamed from wlan0 [ 22.827467] ath10k_pci 0000:06:00.0: failed to enable dynamic BW: -11 [ 28.826502] ath10k_pci 0000:06:00.0: could not suspend target (-11) [ 34.481911] ath10k_pci 0000:06:00.0: failed to set tx-chainmask: -11, req 0x3 [ 37.481548] ath10k_pci 0000:06:00.0: failed to set arp ac override parameter: -11 [ 43.481092] ath10k_pci 0000:06:00.0: could not suspend target (-11) [ 48.784436] ath10k_pci 0000:06:00.0: failed to enable dynamic BW: -11 [ 54.783932] ath10k_pci 0000:06:00.0: could not suspend target (-11) [ 60.119057] ath10k_pci 0000:06:00.0: failed to set tx-chainmask: -11, req 0x3 [ 63.118761] ath10k_pci 0000:06:00.0: failed to set arp ac override parameter: -11 [ 69.118082] ath10k_pci 0000:06:00.0: could not suspend target (-11) [ 74.433568] ath10k_pci 0000:06:00.0: failed to set tx-chainmask: -11, req 0x3 [ 77.433221] ath10k_pci 0000:06:00.0: failed to set arp ac override parameter: -11 [ 83.432603] ath10k_pci 0000:06:00.0: could not suspend target (-11) [ 88.744206] ath10k_pci 0000:06:00.0: failed to set tx-chainmask: -11, req 0x3 [ 91.743721] ath10k_pci 0000:06:00.0: failed to set arp ac override parameter: -11 [ 97.743047] ath10k_pci 0000:06:00.0: could not suspend target (-11) [ 103.058477] ath10k_pci 0000:06:00.0: failed to set tx-chainmask: -11, req 0x3 [ 106.058377] ath10k_pci 0000:06:00.0: failed to set arp ac override parameter: -11 [ 112.057758] ath10k_pci 0000:06:00.0: could not suspend target (-11) [ 117.376946] ath10k_pci 0000:06:00.0: failed to enable dynamic BW: -11 [ 123.376555] ath10k_pci 0000:06:00.0: could not suspend target (-11) [ 128.691784] ath10k_pci 0000:06:00.0: failed to set tx-chainmask: -11, req 0x3
Created attachment 200721 [details] dmesg
Created attachment 200731 [details] lspci -nnvvvv
hooked up two cable & at boot, enp14s0 was first to get ip. after switching the cable between the two(still very slow to detect cable change), enp14s0 still first to get ip. after writing these lines, enp13s0 still doen't have an ip.
I have the same wifi chipset internally on a new Samsung Notebook9Pro: lspci: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) I get the same error messages: [ 9.063921] ath10k_pci 0000:06:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2 [ 9.063923] ath10k_pci 0000:06:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2 [ 9.209430] ath10k_pci 0000:06:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/board-2.bin failed with error -2 Sometimes the interface shows up after boot and can be seen with <ifconfig -a>, sometimes it's not there at all. Sometimes it shows up in network manager but it can never find a signal, let alone connect to one. I have tried recompiling with backports-patched from the AUR. No luck. I've tried the other various firmwares available online that supposedly fix the problem (1. https://github.com/sumdog/ath10k-firmware/, and 2) https://github.com/kvalo/ath10k-firmware). No luck. I'd be happy to provide log files or assist in any way possible. Thanks for your attention to and consideration of this bug.
Created attachment 224201 [details] board-2.bin to include the new hw modules The problem seems to be like the board-2.bin is not including the with the new hw wifi module so that the default is not able used. I don't have this hardware with me, can you please help to try the attached to see if the resolve the problem you've and update?
Created attachment 224281 [details] attachment-12576-0.html Hi, Thanks for that. It did indeed work. The interface is up and searching and finding nearby signals. I will include however certain error messages from journalctl on boot FYI. Jul 18 22:52:14 manjaro-box kernel: ath10k_pci 0000:3b:00.0: failed to connect to HTC: -110 Jul 18 22:52:14 manjaro-box kernel: ath10k_pci 0000:3b:00.0: ctl_resp never came in (-110) Jul 18 22:52:14 manjaro-box kernel: ath10k_pci 0000:3b:00.0: could not probe fw (-110) Jul 18 22:52:14 manjaro-box kernel: ath10k_pci 0000:3b:00.0: could not init core (-110) Jul 18 22:52:14 manjaro-box NetworkManager[444]: <info> [1468907534.4058] supplicant: wpa_supplicant running Jul 18 22:52:14 manjaro-box NetworkManager[444]: <info> [1468907534.4030] manager: (wlan0): new 802.11 WiFi devic Jul 18 22:52:14 manjaro-box NetworkManager[444]: <info> [1468907534.4020] device (wlan0): driver supports Access Jul 18 22:52:14 manjaro-box kernel: ieee80211 phy1: Atheros AR9271 Rev:1 Jul 18 22:52:14 manjaro-box NetworkManager[444]: <info> [1468907534.4009] (wlan0): using nl80211 for WiFi device Jul 18 22:52:14 manjaro-box kernel: ath: Regpair used: 0x37 Jul 18 22:52:14 manjaro-box kernel: ath: Country alpha2 being used: GB Jul 18 22:52:14 manjaro-box kernel: ath: country maps to regdmn code: 0x37 Jul 18 22:52:14 manjaro-box kernel: ath: doing EEPROM country->regdmn map search Jul 18 22:52:14 manjaro-box kernel: ath: EEPROM indicates we should expect a country code Jul 18 22:52:14 manjaro-box kernel: ath: EEPROM regdomain: 0x833a Jul 18 22:52:14 manjaro-box kernel: ath9k_htc 1-3:1.0: FW RMW support: Off Jul 18 22:52:14 manjaro-box kernel: ath9k_htc 1-3:1.0: ath9k_htc: FW Version: 1.3 On Mon, Jul 18, 2016 at 11:59 AM, bugzilla-daemon@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=111111 > > Ryan Hsu <ryanhsu@qca.qualcomm.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| > |ryanhsu@qca.qualcomm.com > > --- Comment #5 from Ryan Hsu <ryanhsu@qca.qualcomm.com> --- > Created attachment 224201 [details] > --> https://bugzilla.kernel.org/attachment.cgi?id=224201&action=edit > board-2.bin to include the new hw modules > > The problem seems to be like the board-2.bin is not including the > with the new > hw wifi module so that the default is not able used. I don't have > this hardware > with me, can you please help to try the attached to see if the > resolve the > problem you've and update? > > -- > You are receiving this mail because: > You are on the CC list for the bug.
(In reply to linuxoso from comment #6) > Created attachment 224281 [details] > attachment-12576-0.html > > Hi, > Thanks for that. It did indeed work. The interface is up and searching > and finding nearby signals. I will include however certain error > messages from journalctl on boot FYI. Glad to hear so, but let me confirm few other things... > Jul 18 22:52:14 manjaro-box kernel: ath10k_pci 0000:3b:00.0: failed to > connect to HTC: -110 > Jul 18 22:52:14 manjaro-box kernel: ath10k_pci 0000:3b:00.0: ctl_resp > never came in (-110) > Jul 18 22:52:14 manjaro-box kernel: ath10k_pci 0000:3b:00.0: could not > probe fw (-110) > Jul 18 22:52:14 manjaro-box kernel: ath10k_pci 0000:3b:00.0: could not > init core (-110) Here you've the ath10k load failed. Are you build the ath10k as builtin module or DLKM? Myabe the full dmesg dump would help to clarify. If you're having the ath10k/QCA6174 as builtin module, have you configured CONFIG_EXTRA_FIRMWARE and CONFIG_EXTRA_FIRMWRE_DIR. > Jul 18 22:52:14 manjaro-box NetworkManager[444]: <info> > [1468907534.4058] supplicant: wpa_supplicant running > Jul 18 22:52:14 manjaro-box NetworkManager[444]: <info> > [1468907534.4030] manager: (wlan0): new 802.11 WiFi devic > Jul 18 22:52:14 manjaro-box NetworkManager[444]: <info> > [1468907534.4020] device (wlan0): driver supports Access > Jul 18 22:52:14 manjaro-box kernel: ieee80211 phy1: Atheros AR9271 Rev:1 > Jul 18 22:52:14 manjaro-box NetworkManager[444]: <info> > [1468907534.4009] (wlan0): using nl80211 for WiFi device > Jul 18 22:52:14 manjaro-box kernel: ath: Regpair used: 0x37 > Jul 18 22:52:14 manjaro-box kernel: ath: Country alpha2 being used: GB > Jul 18 22:52:14 manjaro-box kernel: ath: country maps to regdmn code: > 0x37 > Jul 18 22:52:14 manjaro-box kernel: ath: doing EEPROM country->regdmn > map search > Jul 18 22:52:14 manjaro-box kernel: ath: EEPROM indicates we should > expect a country code > Jul 18 22:52:14 manjaro-box kernel: ath: EEPROM regdomain: 0x833a > Jul 18 22:52:14 manjaro-box kernel: ath9k_htc 1-3:1.0: FW RMW support: > Off > Jul 18 22:52:14 manjaro-box kernel: ath9k_htc 1-3:1.0: ath9k_htc: FW > Version: 1.3 It seems like you've two Wlan modules on your device, one is running on ath10k and the other is running with ath9k (AR9271), the ath10k one which is supposed to run with the QCA6174, the ath9k is used for AR9271 and is assigned as wlan0. So when you're saying the scan is working is that wlan0 or the other interface?
Created attachment 224401 [details] dmesg.dump.txt Hi, Thanks for the response. I'm afraid it was the usb wifi card that uses ath9k_htc that was working. My QCA6174 still is not. Right now I have backports_patched from the Arch AUR for both firmwares as I was having trouble with ath9k_htc as well. Now that one is working well, but the QCA still nothing. If you're talking about recompiling the kernel with CONFIG_EXTRA_FIRMWARE, no I have not. I am attaching a dmesg output textfile. On Tue, Jul 19, 2016 at 9:42 AM, bugzilla-daemon@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=111111 > > --- Comment #7 from Ryan Hsu <ryanhsu@qca.qualcomm.com> --- > (In reply to linuxoso from comment #6) >> Created attachment 224281 [details] >> attachment-12576-0.html >> >> Hi, >> Thanks for that. It did indeed work. The interface is up and >> searching >> and finding nearby signals. I will include however certain error >> messages from journalctl on boot FYI. > > Glad to hear so, but let me confirm few other things... > >> Jul 18 22:52:14 manjaro-box kernel: ath10k_pci 0000:3b:00.0: failed >> to >> connect to HTC: -110 >> Jul 18 22:52:14 manjaro-box kernel: ath10k_pci 0000:3b:00.0: >> ctl_resp >> never came in (-110) >> Jul 18 22:52:14 manjaro-box kernel: ath10k_pci 0000:3b:00.0: could >> not >> probe fw (-110) >> Jul 18 22:52:14 manjaro-box kernel: ath10k_pci 0000:3b:00.0: could >> not >> init core (-110) > > Here you've the ath10k load failed. > Are you build the ath10k as builtin module or DLKM? > Myabe the full dmesg dump would help to clarify. > > If you're having the ath10k/QCA6174 as builtin module, have you > configured > CONFIG_EXTRA_FIRMWARE and CONFIG_EXTRA_FIRMWRE_DIR. > >> Jul 18 22:52:14 manjaro-box NetworkManager[444]: <info> >> [1468907534.4058] supplicant: wpa_supplicant running >> Jul 18 22:52:14 manjaro-box NetworkManager[444]: <info> >> [1468907534.4030] manager: (wlan0): new 802.11 WiFi devic >> Jul 18 22:52:14 manjaro-box NetworkManager[444]: <info> >> [1468907534.4020] device (wlan0): driver supports Access >> Jul 18 22:52:14 manjaro-box kernel: ieee80211 phy1: Atheros AR9271 >> Rev:1 >> Jul 18 22:52:14 manjaro-box NetworkManager[444]: <info> >> [1468907534.4009] (wlan0): using nl80211 for WiFi device >> Jul 18 22:52:14 manjaro-box kernel: ath: Regpair used: 0x37 >> Jul 18 22:52:14 manjaro-box kernel: ath: Country alpha2 being used: >> GB >> Jul 18 22:52:14 manjaro-box kernel: ath: country maps to regdmn >> code: >> 0x37 >> Jul 18 22:52:14 manjaro-box kernel: ath: doing EEPROM >> country->regdmn >> map search >> Jul 18 22:52:14 manjaro-box kernel: ath: EEPROM indicates we should >> expect a country code >> Jul 18 22:52:14 manjaro-box kernel: ath: EEPROM regdomain: 0x833a >> Jul 18 22:52:14 manjaro-box kernel: ath9k_htc 1-3:1.0: FW RMW >> support: >> Off >> Jul 18 22:52:14 manjaro-box kernel: ath9k_htc 1-3:1.0: ath9k_htc: FW >> Version: 1.3 > > It seems like you've two Wlan modules on your device, one is running > on ath10k > and the other is running with ath9k (AR9271), the ath10k one which is > supposed > to run with the QCA6174, the ath9k is used for AR9271 and is assigned > as wlan0. > > So when you're saying the scan is working is that wlan0 or the other > interface? > > -- > You are receiving this mail because: > You are on the CC list for the bug.
Created attachment 224411 [details] Board-2.bin includes the IDs to fix the issue The new board-2.bin is including the IDs that David reported, I just saw your dmesg and realized the HW ID you've is different from David, so that the previous one won't help with your case. Can you please try again the updated board-2.bin file and let me know if that help or not? (and of course, attaching the dmesg output if that still not working...) Also, I am seeing you're using the firmware in a version that is not likely from https://github.com/kvalo/ath10k-firmware, where do you get this firmware? Ryan
Created attachment 224421 [details] attachment-25747-0.html the new board-2.bin does work for me! :) On Wed, Jul 20, 2016 at 5:06 PM, <bugzilla-daemon@bugzilla.kernel.org> wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=111111 > > --- Comment #9 from Ryan Hsu <ryanhsu@qca.qualcomm.com> --- > Created attachment 224411 [details] > --> https://bugzilla.kernel.org/attachment.cgi?id=224411&action=edit > Board-2.bin includes the IDs to fix the issue > > The new board-2.bin is including the IDs that David reported, I just saw > your > dmesg and realized the HW ID you've is different from David, so that the > previous one won't help with your case. > > Can you please try again the updated board-2.bin file and let me know if > that > help or not? (and of course, attaching the dmesg output if that still not > working...) > > Also, I am seeing you're using the firmware in a version that is not likely > from https://github.com/kvalo/ath10k-firmware, where do you get this > firmware? > > Ryan > > -- > You are receiving this mail because: > You reported the bug. >
Created attachment 224441 [details] dmesg.dump.txt Hi, I have tried with the kvalo firmware in both the hw3.0 and hw2.1 folders. Still not working. Network manager scans for networks but never finds any (I should be able to sniff at least a few weak signals), and wifi-menu gives this output: sudo wifi-menu [sudo] password for manjaro: Scanning for networks... Could not set interface wlp59s0 flags (UP): Resource temporarily unavailable nl80211: Could not set interface 'wlp59s0' UP Could not set interface wlp59s0 flags (UP): Resource temporarily unavailable WEXT: Could not set interface 'wlp59s0' UP wlp59s0: Failed to initialize driver interface failed I'll attach another dmesg output file. The firmware I was using before could be this: wget https://github.com/sumdog/ath10k-firmware/raw/5faf5bb7c7413f9bb332693179de54cca6fff58e/ath10k/QCA6174/hw2.1/board.bin wget https://github.com/sumdog/ath10k-firmware/raw/5faf5bb7c7413f9bb332693179de54cca6fff58e/ath10k/QCA6174/hw2.1/firmware-4.bin Or it could be what was compiled from the driver backports package "backports_patched" in the AUR. (That's what finally fixed my issues with the ath9k_htc firmware.) I've kind of lost track with the mucking around trying to fix it. But the attached dmesg.txt file is with the kvalo firmware (unless the backports-patched package has changed the path of where the system is looking for the drivers. I hope this helps. Thanks for your efforts. On Wed, Jul 20, 2016 at 2:06 PM, bugzilla-daemon@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=111111 > > --- Comment #9 from Ryan Hsu <ryanhsu@qca.qualcomm.com> --- > Created attachment 224411 [details] > --> https://bugzilla.kernel.org/attachment.cgi?id=224411&action=edit > Board-2.bin includes the IDs to fix the issue > > > The new board-2.bin is including the IDs that David reported, I just > saw your > dmesg and realized the HW ID you've is different from David, so that > the > previous one won't help with your case. > > Can you please try again the updated board-2.bin file and let me know > if that > help or not? (and of course, attaching the dmesg output if that still > not > working...) > > Also, I am seeing you're using the firmware in a version that is not > likely > from https://github.com/kvalo/ath10k-firmware, where do you get this > firmware? > > Ryan > > -- > You are receiving this mail because: > You are on the CC list for the bug.
Created attachment 224831 [details] 07/21/2016, latest board-2.bin update Ouch... sorry I mess up one digit of your ID, hope this is the last shot! Let me know! Ryan
Created attachment 224881 [details] dmesg.dump.txt Hi, Thanks for your efforts. Seems to be the same. I'm attaching the dmesg output again. Also the output from my attempt to run wifi-menu/netctl is here: sudo wifi-menu [sudo] password for manjaro: Scanning for networks... Could not read interface p2p-dev-wlp59s0 flags: No such device nl80211: Could not set interface 'p2p-dev-wlp59s0' UP p2p-dev-wlp59s0: Failed to initialize driver interface failed No networks found Tomorrow, if I don't hear any results from you about the dmesg output, I'll try the kvalos firmware and your latest board-2.bin on my Arch system on the other partition, where I haven't done any previous troubleshooting. Maybe the clean slate will yield different results. On Thu, Jul 21, 2016 at 7:38 PM, bugzilla-daemon@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=111111 > > --- Comment #12 from Ryan Hsu <ryanhsu@qca.qualcomm.com> --- > Created attachment 224831 [details] > --> https://bugzilla.kernel.org/attachment.cgi?id=224831&action=edit > 07/21/2016, latest board-2.bin update > > Ouch... sorry I mess up one digit of your ID, hope this is the last > shot! > > Let me know! > > Ryan > > -- > You are receiving this mail because: > You are on the CC list for the bug.
I am not sure what is the wifi-menu/netctl that are controlling the interface. But i can see the driver is loaded correctly now, which was failed in previously. Can you firstly try scan on wlan0 (or wlp59s0?) is working or not before running the wifi-menu/netctl? [ 4.437395] ath10k_pci 0000:3b:00.0: Direct firmware load for ath10k/cal-pci-0000:3b:00.0.bin failed with error -2 [ 4.437405] ath10k_pci 0000:3b:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2 [ 4.437406] ath10k_pci 0000:3b:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2 [ 4.440241] ath10k_pci 0000:3b:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 144d:412f [ 4.440243] ath10k_pci 0000:3b:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0 [ 4.440701] ath10k_pci 0000:3b:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad crc32 75dee6c5 [ 4.506267] ath10k_pci 0000:3b:00.0: board_file api 2 bmi_id N/A crc32 e35a6c0f [ 6.627412] ath10k_pci 0000:3b:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [ 6.691531] ath: EEPROM regdomain: 0x6c [ 6.691535] ath: EEPROM indicates we should expect a direct regpair map [ 6.691543] ath: Country alpha2 being used: 00 [ 6.691544] ath: Regpair used: 0x6c [ 6.700301] ath10k_pci 0000:3b:00.0 wlp59s0: renamed from wlan0(In reply to linuxoso from comment #13) > Created attachment 224881 [details] > dmesg.dump.txt > > Hi, > Thanks for your efforts. Seems to be the same. I'm attaching the dmesg > output again. Also the output from my attempt to run wifi-menu/netctl > is here: I can see the driver is loaded correctly now, which was failed in previously. (below logs snap) So I think the driver loading issue is resolved, now might be different one... > sudo wifi-menu > [sudo] password for manjaro: > Scanning for networks... Could not read interface p2p-dev-wlp59s0 > flags: No such device > nl80211: Could not set interface 'p2p-dev-wlp59s0' UP > p2p-dev-wlp59s0: Failed to initialize driver interface > failed > No networks found p2p-dev-wlp59s0 should only be created if p2p group is created, does the wifi-menu/netctl did that for you? have you check either wpa_supplicant is running or p2p group is added? what is the output of ifconfig -a shows? > Tomorrow, if I don't hear any results from you about the dmesg output, > I'll try the kvalos firmware and your latest board-2.bin on my Arch > system on the other partition, where I haven't done any previous > troubleshooting. Maybe the clean slate will yield different results. > Can you firstly try scan on wlan0 (or wlp59s0?) is working or not before running the wifi-menu/netctl? [snap....] [ 4.437395] ath10k_pci 0000:3b:00.0: Direct firmware load for ath10k/cal-pci-0000:3b:00.0.bin failed with error -2 [ 4.437405] ath10k_pci 0000:3b:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2 [ 4.437406] ath10k_pci 0000:3b:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2 [ 4.440241] ath10k_pci 0000:3b:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 144d:412f [ 4.440243] ath10k_pci 0000:3b:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0 [ 4.440701] ath10k_pci 0000:3b:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad crc32 75dee6c5 [ 4.506267] ath10k_pci 0000:3b:00.0: board_file api 2 bmi_id N/A crc32 e35a6c0f [ 6.627412] ath10k_pci 0000:3b:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [ 6.691531] ath: EEPROM regdomain: 0x6c [ 6.691535] ath: EEPROM indicates we should expect a direct regpair map [ 6.691543] ath: Country alpha2 being used: 00 [ 6.691544] ath: Regpair used: 0x6c [ 6.700301] ath10k_pci 0000:3b:00.0 wlp59s0: renamed from wlan0
Created attachment 225291 [details] attachment-19284-0.html I ran <ifconfig -a> before <sudo wifi-menu wlp59s0> and this is the output: lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1 (Local Loopback) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlp0s20f0u3: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether 00:c0:ca:72:67:fe txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlp59s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether c8:ff:28:e4:8f:2f txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlp59s0 is the pci wifi card, and wlp0s20f0u3 is my usb wifi card. On Thu, Jul 21, 2016 at 11:43 PM, bugzilla-daemon@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=111111 > > --- Comment #14 from Ryan Hsu <ryanhsu@qca.qualcomm.com> --- > > I am not sure what is the wifi-menu/netctl that are controlling the > interface. > But i can see the driver is loaded correctly now, which was failed in > previously. > > Can you firstly try scan on wlan0 (or wlp59s0?) is working or not > before > running the wifi-menu/netctl? > > [ 4.437395] ath10k_pci 0000:3b:00.0: Direct firmware load for > ath10k/cal-pci-0000:3b:00.0.bin failed with error -2 > [ 4.437405] ath10k_pci 0000:3b:00.0: Direct firmware load for > ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2 > [ 4.437406] ath10k_pci 0000:3b:00.0: could not fetch firmware file > 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2 > [ 4.440241] ath10k_pci 0000:3b:00.0: qca6174 hw3.2 target > 0x05030000 chip_id > 0x00340aff sub 144d:412f > [ 4.440243] ath10k_pci 0000:3b:00.0: kconfig debug 0 debugfs 1 > tracing 0 dfs > 0 testmode 0 > [ 4.440701] ath10k_pci 0000:3b:00.0: firmware ver > WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features > wowlan,ignore-otp,no-4addr-pad > crc32 75dee6c5 > [ 4.506267] ath10k_pci 0000:3b:00.0: board_file api 2 bmi_id N/A > crc32 > e35a6c0f > [ 6.627412] ath10k_pci 0000:3b:00.0: htt-ver 3.26 wmi-op 4 htt-op > 3 cal otp > max-sta 32 raw 0 hwcrypto 1 > [ 6.691531] ath: EEPROM regdomain: 0x6c > [ 6.691535] ath: EEPROM indicates we should expect a direct > regpair map > [ 6.691543] ath: Country alpha2 being used: 00 > [ 6.691544] ath: Regpair used: 0x6c > [ 6.700301] ath10k_pci 0000:3b:00.0 wlp59s0: renamed from wlan0(In > reply to > linuxoso from comment #13) >> Created attachment 224881 [details] >> dmesg.dump.txt >> >> Hi, >> Thanks for your efforts. Seems to be the same. I'm attaching the >> dmesg >> output again. Also the output from my attempt to run >> wifi-menu/netctl >> is here: > > I can see the driver is loaded correctly now, which was failed in > previously. > (below logs snap) > > So I think the driver loading issue is resolved, now might be > different one... > >> sudo wifi-menu >> [sudo] password for manjaro: >> Scanning for networks... Could not read interface p2p-dev-wlp59s0 >> flags: No such device >> nl80211: Could not set interface 'p2p-dev-wlp59s0' UP >> p2p-dev-wlp59s0: Failed to initialize driver interface >> failed >> No networks found > > p2p-dev-wlp59s0 should only be created if p2p group is created, does > the > wifi-menu/netctl did that for you? have you check either > wpa_supplicant is > running or p2p group is added? what is the output of ifconfig -a > shows? > >> Tomorrow, if I don't hear any results from you about the dmesg >> output, >> I'll try the kvalos firmware and your latest board-2.bin on my Arch >> system on the other partition, where I haven't done any previous >> troubleshooting. Maybe the clean slate will yield different results. >> > > Can you firstly try scan on wlan0 (or wlp59s0?) is working or not > before > running the wifi-menu/netctl? > > [snap....] > [ 4.437395] ath10k_pci 0000:3b:00.0: Direct firmware load for > ath10k/cal-pci-0000:3b:00.0.bin failed with error -2 > [ 4.437405] ath10k_pci 0000:3b:00.0: Direct firmware load for > ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2 > [ 4.437406] ath10k_pci 0000:3b:00.0: could not fetch firmware file > 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2 > [ 4.440241] ath10k_pci 0000:3b:00.0: qca6174 hw3.2 target > 0x05030000 chip_id > 0x00340aff sub 144d:412f > [ 4.440243] ath10k_pci 0000:3b:00.0: kconfig debug 0 debugfs 1 > tracing 0 dfs > 0 testmode 0 > [ 4.440701] ath10k_pci 0000:3b:00.0: firmware ver > WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features > wowlan,ignore-otp,no-4addr-pad > crc32 75dee6c5 > [ 4.506267] ath10k_pci 0000:3b:00.0: board_file api 2 bmi_id N/A > crc32 > e35a6c0f > [ 6.627412] ath10k_pci 0000:3b:00.0: htt-ver 3.26 wmi-op 4 htt-op > 3 cal otp > max-sta 32 raw 0 hwcrypto 1 > [ 6.691531] ath: EEPROM regdomain: 0x6c > [ 6.691535] ath: EEPROM indicates we should expect a direct > regpair map > [ 6.691543] ath: Country alpha2 being used: 00 > [ 6.691544] ath: Regpair used: 0x6c > [ 6.700301] ath10k_pci 0000:3b:00.0 wlp59s0: renamed from wlan0 > > -- > You are receiving this mail because: > You are on the CC list for the bug.
as far as the missing /lib/firmware/ath10k/QCA6174/hw3.0/firmware-5.bin file goes, i usually copy or link firmware-4.bin from the same folder into firmware-5.bin. And i've just tested the last board-2.bin and it still works fine for me. just a note: i tried copying the firmware-5.bin file from the hw2.1 folder but it did not work.