* ath10k_pci rawmode = 1 requires support from firmware @ 2020-02-21 20:26 Cale Collins 2020-03-24 12:10 ` Kalle Valo 0 siblings, 1 reply; 4+ messages in thread From: Cale Collins @ 2020-02-21 20:26 UTC (permalink / raw) To: kvalo, ath10k, kvalo Hello Kalle, When attempting to bring up my mesh0 interface, I recieve an error and in "dmesg": [ 901.629999] ath10k_pci 0001:90:00.0: must load driver with rawmode=1 to add mesh interfaces I enable this mode by changing my bootargs, appending "ath10k_core.rawmode=1". On boot "dmesg" reports: [ 12.040581] ath10k_pci 0001:90:00.0: rawmode = 1 requires support from firmware Where does this "supported" firmware come from? I'm using SparkLAN WPEQ-261ACNI(BT) 802.11ac/abgn + BT PCI Express Mini Card (Half) - Qualcomm QCA6174A-5 chipset, with a mainline 4.20.7 kernel and Ubuntu Bionic root filesystem. Thank you for looking into this, I'm glad to provide more information if needed. Best regards, Cale Collins _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: ath10k_pci rawmode = 1 requires support from firmware 2020-02-21 20:26 ath10k_pci rawmode = 1 requires support from firmware Cale Collins @ 2020-03-24 12:10 ` Kalle Valo 2020-03-24 17:39 ` Cale Collins 0 siblings, 1 reply; 4+ messages in thread From: Kalle Valo @ 2020-03-24 12:10 UTC (permalink / raw) To: Cale Collins; +Cc: ath10k Cale Collins <ccollins@gateworks.com> writes: > When attempting to bring up my mesh0 interface, I recieve an error and > in "dmesg": > > [ 901.629999] ath10k_pci 0001:90:00.0: must load driver with > rawmode=1 to add mesh interfaces > > I enable this mode by changing my bootargs, appending "ath10k_core.rawmode=1". > > On boot "dmesg" reports: > > [ 12.040581] ath10k_pci 0001:90:00.0: rawmode = 1 requires support > from firmware > > Where does this "supported" firmware come from? > > I'm using SparkLAN WPEQ-261ACNI(BT) 802.11ac/abgn + BT PCI Express > Mini Card (Half) - Qualcomm QCA6174A-5 chipset, with a mainline 4.20.7 > kernel and Ubuntu Bionic root filesystem. > > Thank you for looking into this, I'm glad to provide more information if needed. Not all firmware branches support raw mode. The firmware will have raw-mode feature bit enabled if it support raw mode, you can check it like this: $ ath10k-fwencoder --info firmware-6.bin_WLAN.RM.4.4.1.c3-00059 | grep Features Features: wowlan,ignore-otp-result,no-nwifi-decap-4addr-padding,raw-mode,mfp-support For QCA6174 with raw mode I recommend using 4.4.1.c3 branch: https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0/4.4.1.c3 -- https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: ath10k_pci rawmode = 1 requires support from firmware 2020-03-24 12:10 ` Kalle Valo @ 2020-03-24 17:39 ` Cale Collins 0 siblings, 0 replies; 4+ messages in thread From: Cale Collins @ 2020-03-24 17:39 UTC (permalink / raw) To: Kalle Valo; +Cc: ath10k Hello Kalle, Ultimately I ended up using the 5.4 kernel and firmware-6.bin_WLAN.RM.4.4.1.c3-00038. This firmware didn't work with "iw" and required custom building "wpa_supplicant" with "CONFIG_MESH=y" enabled in the .config. I apologize for leaving the thread hanging, I was vacillating if this information would be prudent or considered a regression. I'm glad to do further testing (with the latest mainline kernel) if you need. Best regards, Cale Collins _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k ^ permalink raw reply [flat|nested] 4+ messages in thread
[parent not found: <CAG2Q2vUH95JyMqOELtU4=uU3nO5jr2+806KiO+T1-tNdBZ=DYw@mail.gmail.com>]
[parent not found: <CAG2Q2vU3spU6VOdGAF5beWmgG1eaWuVm3pc+gzcnhaTUHvX+yw@mail.gmail.com>]
[parent not found: <CAMrEMU8DtaKMFqZexurzWZD8iB4YX3CmF7vq2XsaDoD=OC-eoA@mail.gmail.com>]
* Re: ath10k_pci rawmode = 1 requires support from firmware [not found] ` <CAMrEMU8DtaKMFqZexurzWZD8iB4YX3CmF7vq2XsaDoD=OC-eoA@mail.gmail.com> @ 2020-02-26 21:15 ` Cale Collins 0 siblings, 0 replies; 4+ messages in thread From: Cale Collins @ 2020-02-26 21:15 UTC (permalink / raw) To: Justin Capella, Rick Winscot, Kalle Valo; +Cc: linux-wireless, ath10k Hello Justin and Kalle, Justin thank you very much for the reply, sorry it took me so long to get back to you but I wanted to do more testing based on your recommendations before I wrote. I tried numerous versions of the firmware-6.bin file from the linux-firmware git, and the repo you linked. I have been hitting the same issue with nearly every version of firmware I try. I included the output from WLAN.RM.4.4.1-00140-QCARMSWPZ-1, but the exact same applies to WLAN.RMH.4.4.1-00042. Under normal circumstances I would try to bisect this, but I can't because I don't have a "good" (working) version of the firmware. I'm doing this on behalf of one of our clients Rick Winscot, I added him to this thread so he can offer his insight. Here's the output from my testing with WLAN.RM.4.4.1-00140-QCARMSWPZ-1: root@bionic-newport:~# ls /sys/class/net/ can0 eth0 eth1 lo root@bionic-newport:~# dmesg |grep ath10k [ 0.000000] Kernel command line: cma=64M coherent_pool=16M net.ifnames=0 ath10k_core.rawmode=1 root=/dev/mmcblk0p2 rw rootwait console=ttyAMA0,115200n8 earlycon=pl011,0x87e028000000 [ 12.356854] ath10k_pci 0001:58:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [ 12.762070] ath10k_pci 0001:58:00.0: Direct firmware load for ath10k/pre-cal-pci-0001:58:00.0.bin failed with error -2 [ 12.762132] ath10k_pci 0001:58:00.0: Direct firmware load for ath10k/cal-pci-0001:58:00.0.bin failed with error -2 [ 12.779272] ath10k_pci 0001:58:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 168c:3363 [ 12.779280] ath10k_pci 0001:58:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0 [ 12.780635] ath10k_pci 0001:58:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1 [ 12.858884] ath10k_pci 0001:58:00.0: board_file api 2 bmi_id N/A crc32 4ac0889b [ 12.858894] ath10k_pci 0001:58:00.0: rawmode = 1 requires support from firmware [ 12.866282] ath10k_pci 0001:58:00.0: fatal problem with firmware features: -22 [ 12.873670] ath10k_pci 0001:58:00.0: could not probe fw (-22) root@bionic-newport:~# ls /sys/class/net/ can0 eth0 eth1 lo wlan0 root@bionic-newport:~# dmesg |grep ath10k [ 11.981606] ath10k_pci 0001:58:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [ 12.310158] ath10k_pci 0001:58:00.0: Direct firmware load for ath10k/pre-cal-pci-0001:58:00.0.bin failed with error -2 [ 12.310206] ath10k_pci 0001:58:00.0: Direct firmware load for ath10k/cal-pci-0001:58:00.0.bin failed with error -2 [ 12.349306] ath10k_pci 0001:58:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 168c:3363 [ 12.349314] ath10k_pci 0001:58:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0 [ 12.350682] ath10k_pci 0001:58:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1 [ 12.432281] ath10k_pci 0001:58:00.0: board_file api 2 bmi_id N/A crc32 4ac0889b [ 12.978328] ath10k_pci 0001:58:00.0: Unknown eventid: 3 [ 12.994313] ath10k_pci 0001:58:00.0: Unknown eventid: 118809 [ 12.997236] ath10k_pci 0001:58:00.0: Unknown eventid: 90118 [ 12.997886] ath10k_pci 0001:58:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 root@bionic-newport:~# iw phy phy0 interface add mesh0 type mp root@bionic-newport:~# iw mesh0 info Interface mesh0 ifindex 6 wdev 0x2 addr 94:92:d2:00:04:04 type mesh point wiphy 0 txpower 0.00 dBm root@bionic-newport:~# iw dev mesh0 set freq 5745 80 5775 root@bionic-newport:~# ifconfig mesh0 192.168.1.10 SIOCSIFFLAGS: Invalid argument root@bionic-newport:~# dmesg |grep ath10k [ 11.981606] ath10k_pci 0001:58:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [ 12.310158] ath10k_pci 0001:58:00.0: Direct firmware load for ath10k/pre-cal-pci-0001:58:00.0.bin failed with error -2 [ 12.310206] ath10k_pci 0001:58:00.0: Direct firmware load for ath10k/cal-pci-0001:58:00.0.bin failed with error -2 [ 12.349306] ath10k_pci 0001:58:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 168c:3363 [ 12.349314] ath10k_pci 0001:58:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0 [ 12.350682] ath10k_pci 0001:58:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1 [ 12.432281] ath10k_pci 0001:58:00.0: board_file api 2 bmi_id N/A crc32 4ac0889b [ 12.978328] ath10k_pci 0001:58:00.0: Unknown eventid: 3 [ 12.994313] ath10k_pci 0001:58:00.0: Unknown eventid: 118809 [ 12.997236] ath10k_pci 0001:58:00.0: Unknown eventid: 90118 [ 12.997886] ath10k_pci 0001:58:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [ 256.819171] ath10k_pci 0001:58:00.0: Unknown eventid: 3 [ 256.834413] ath10k_pci 0001:58:00.0: Unknown eventid: 118809 [ 256.837352] ath10k_pci 0001:58:00.0: Unknown eventid: 90118 [ 256.884876] ath10k_pci 0001:58:00.0: must load driver with rawmode=1 to add mesh interfaces Mahalo, Cale Collins _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2020-03-24 17:39 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-02-21 20:26 ath10k_pci rawmode = 1 requires support from firmware Cale Collins
2020-03-24 12:10 ` Kalle Valo
2020-03-24 17:39 ` Cale Collins
[not found] <CAG2Q2vUH95JyMqOELtU4=uU3nO5jr2+806KiO+T1-tNdBZ=DYw@mail.gmail.com>
[not found] ` <CAG2Q2vU3spU6VOdGAF5beWmgG1eaWuVm3pc+gzcnhaTUHvX+yw@mail.gmail.com>
[not found] ` <CAMrEMU8DtaKMFqZexurzWZD8iB4YX3CmF7vq2XsaDoD=OC-eoA@mail.gmail.com>
2020-02-26 21:15 ` Cale Collins
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox