From: Felix <kramerfe@gmail.com>
To: ath10k@lists.infradead.org
Subject: Connection Problems with on QCA9880-BR4A
Date: Fri, 11 Nov 2016 13:07:20 +0100 [thread overview]
Message-ID: <5825B478.4020405@gmail.com> (raw)
Hello,
I am running a Debian Jessie server on the backports kernel
4.7.0-0.bpo.1-amd64. An Ubiquiti SR71 with its AR928X is working just
fine under ath9k.
The mikrotik R11e-5HacT with its QCA9880-BR4A is recognized after some
errors trying to load inexistent files with the standard firmware-5.bin
from the Jessie Backports (10.2.4.70.54):
...ath10k_pci 0000:02:00.0: firmware: failed to load
ath10k/pre-cal-pci-0000:02:00.0.bin (-2)
...ath10k_pci 0000:02:00.0: Direct firmware load for
ath10k/pre-cal-pci-0000:02:00.0.bin failed with error -2
...ath10k_pci 0000:02:00.0: firmware: failed to load
ath10k/cal-pci-0000:02:00.0.bin (-2)
...ath10k_pci 0000:02:00.0: Direct firmware load for
ath10k/cal-pci-0000:02:00.0.bin failed with error -2
...ath10k_pci 0000:02:00.0: firmware: failed to load
ath10k/QCA988X/hw2.0/board-2.bin (-2)
...ath10k_pci 0000:02:00.0: Direct firmware load for
ath10k/QCA988X/hw2.0/board-2.bin failed with error -2
There are many reports on working devices with these errors on the web
so I suppose they can be ignored.
The device seems to work (iw scan shows better results than the SR71),
but after connection to the AP via wpa_supplicant, dhclient is unable to
retrieve an IP-adress. I have tried the newer firmware (10.2.4.70.58)
and the older ones as well as those from candela without success. On
older firmwares additional errors up to firmware crash on iw set
bitrates appear.
Regards,
Felix
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next reply other threads:[~2016-11-11 12:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-11 12:07 Felix [this message]
2016-11-14 7:56 ` Connection Problems with on QCA9880-BR4A Michal Kazior
2016-11-15 12:59 ` Felix
2016-11-15 13:48 ` Michal Kazior
2016-11-15 22:42 ` Felix
2016-11-18 15:18 ` Michal Kazior
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5825B478.4020405@gmail.com \
--to=kramerfe@gmail.com \
--cc=ath10k@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.