Re: QCA6174 hw2.1 Firmware crash when connecting to a 5GHz network

2015-11-19 Thread Bartosz Markowski 
On 18 November 2015 at 16:28, Roman Bange  wrote:
> Hey,
>
> im getting a firmware crash when i try to connect to a 5GHz network.
> I tested the older firmware WLAN.RM.1.1-00141, which is now provided in 
> linux-firmware, and SW_RM.1.1.1-00157-QCARMSWPZ-1, which is provided by you 
> in ath10k-firmware.
>
> SW_RM.1.1.1-00157-QCARMSWPZ-1 didn't crash but i wasn't able to connect 
> either.
>
> In addition i tested a solution that worked for me with the 4.1 Kernel where 
> i extracted the firmware out of the windows driver (and can be found here 
> (https://github.com/sumdog/ath10k-firmware). This solution didn't worked for 
> me too.
>
> I tested the firmware with 4.2.0-16 under Ubuntu, but experienced the same 
> problem with the stable releases 4.2.6 and 4.3 too. I have not tested the 
> 4.4-rc1 Kernel yet because its not compilable with the Ubuntu packages.

The firmware crash you experience with "older" firmwares got fixed in
the 000157.
It's most likely related with wrong txbf capability advertisement,
which your card (and firmware for it) does not support.

May I ask what AP you test with?

> I attached the related dmesg logs to this mail.

When you use the 000157 firmware you can see there's a successful
auth/assoc seq. but later on for some reason there's a local deauth
triggered.

[   58.966382] wlp3s0: authenticate with f0:7f:06:2a:44:2d
[   59.008957] wlp3s0: send auth to f0:7f:06:2a:44:2d (try 1/3)
[   59.009546] wlp3s0: authenticated
[   59.014268] wlp3s0: associate with f0:7f:06:2a:44:2d (try 1/3)
[   59.019139] wlp3s0: RX AssocResp from f0:7f:06:2a:44:2d (capab=0x11
status=0 aid=6)
[   59.022291] wlp3s0: associated
[   59.022324] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
...
[   62.130412] wlp3s0: deauthenticating from f0:7f:06:2a:44:2d by
local choice (Reason: 3=DEAUTH_LEAVING)

And these steps repeat in your log.

Could you try to connect with the AP w/o the network manager (using
wpa_supplicant / wpa_cli directly)?

> Best regards,
> Roman
> ___
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
>

-- 
Bartosz

___
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: QCA998X not working at all

2015-11-19 Thread Sebastian Gottschall 

simple solution.

as for ath9k. otp must be ignored for various chipsets, since they wont 
return valid results


--- core.c (Revision 2702)
+++ core.c (Arbeitskopie)
@@ -1735,9 +1735,8 @@

  ret = ath10k_core_get_board_id_from_otp(ar);
  if (ret && ret != -EOPNOTSUPP) {
-  ath10k_err(ar, "failed to get board id from otp for qca99x0: %d\n",
+  ath10k_err(ar, "failed to get board id from otp for qca99x0: %d, 
ignore\n",

 ret);
-  return ret;
  }

  ret = ath10k_core_fetch_board_file(ar);



Am 19.11.2015 um 18:12 schrieb Sebastian Gottschall:

Am 19.11.2015 um 17:13 schrieb Ben Greear:


git clone git://dmz2.candelatech.com/linux.ath

same effect with yours

6.201141] ath10k_pci :01:00.0: enabling device (0140 -> 0142)
[6.201593] ath10k_pci :01:00.0: pci irq legacy interrupts 0 
irq_mode 0 reset_mode 0

[8.578573] ath10k_pci :01:00.0: unable to read from the device
[8.578605] ath10k_pci :01:00.0: could not execute otp for 
board id check: -110
[8.583648] ath10k_pci :01:00.0: failed to get board id from 
otp for qca99x0: -110

[8.591338] ath10k_pci :01:00.0: could not probe fw (-110)
[8.600062] ath10k_pci 0001:01:00.0: enabling device (0140 -> 0142)
[8.605600] ath10k_pci 0001:01:00.0: pci irq legacy interrupts 0 
irq_mode 0 reset_mode 0

[   10.798574] ath10k_pci 0001:01:00.0: unable to read from the device
[   10.798598] ath10k_pci 0001:01:00.0: could not execute otp for 
board id check: -110
[   10.803644] ath10k_pci 0001:01:00.0: failed to get board id from 
otp for qca99x0: -110

[   10.811346] ath10k_pci 0001:01:00.0: could not probe fw (-110)


___
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k




___
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: QCA998X not working at all

2015-11-19 Thread Sebastian Gottschall 

Am 19.11.2015 um 17:13 schrieb Ben Greear:


git clone git://dmz2.candelatech.com/linux.ath

same effect with yours

6.201141] ath10k_pci :01:00.0: enabling device (0140 -> 0142)
[6.201593] ath10k_pci :01:00.0: pci irq legacy interrupts 0 
irq_mode 0 reset_mode 0

[8.578573] ath10k_pci :01:00.0: unable to read from the device
[8.578605] ath10k_pci :01:00.0: could not execute otp for board 
id check: -110
[8.583648] ath10k_pci :01:00.0: failed to get board id from otp 
for qca99x0: -110

[8.591338] ath10k_pci :01:00.0: could not probe fw (-110)
[8.600062] ath10k_pci 0001:01:00.0: enabling device (0140 -> 0142)
[8.605600] ath10k_pci 0001:01:00.0: pci irq legacy interrupts 0 
irq_mode 0 reset_mode 0

[   10.798574] ath10k_pci 0001:01:00.0: unable to read from the device
[   10.798598] ath10k_pci 0001:01:00.0: could not execute otp for board 
id check: -110
[   10.803644] ath10k_pci 0001:01:00.0: failed to get board id from otp 
for qca99x0: -110

[   10.811346] ath10k_pci 0001:01:00.0: could not probe fw (-110)


___
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k