From: "Valo, Kalle" <kvalo@qca.qualcomm.com>
To: Tom Marble <tmarble@info9.net>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: Cannot initialize Compex WLE600VX for 802.11ac?
Date: Wed, 22 Jun 2016 06:47:12 +0000 [thread overview]
Message-ID: <87y45xiuts.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <57dtwgmmwmr.fsf@cerise.info9.net> (Tom Marble's message of "Tue, 21 Jun 2016 09:42:20 -0500")
Tom Marble <tmarble@info9.net> writes:
> Setting channel=0 to enable scanning results in finding channel 52
> as the ideal channel, but then (full log in [7])...
> # hostapd -dd /etc/hostapd/wlan0.conf | tee /tmp/wlan0.log
> ...
> Mode: IEEE 802.11a Channel: 52 Frequency: 5260 MHz
> DFS 0 channels required radar detection
> Could not set channel for kernel driver
> Interface initialization failed
>
> Setting channel=52 and trying again fails with... (full log in [8]).
> # hostapd -dd /etc/hostapd/wlan0.conf | tee /tmp/wlan0-52.log
> ...
> nl80211: Failed to start radar detection: -16 (Device or resource busy)
>
>
> What suggestions do you have to help me identify the cause of
> this problem (and hopefully resolve it!)?
Do you have CONFIG_ATH10K_DFS_CERTIFIED enabled? Also check that that
regulatory is correct with 'iw reg get' and 'iw phy0 info', especially
that 80 MHz channels are supported.
Also I would try first without DFS on channel 36 just to make it easier
to pinpoint the problem.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2016-06-22 6:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 14:42 Cannot initialize Compex WLE600VX for 802.11ac? Tom Marble
2016-06-22 6:47 ` Valo, Kalle [this message]
2016-06-22 13:10 ` Tom Marble
2016-06-22 14:08 ` Valo, Kalle
2016-06-23 13:00 ` Tom Marble
2016-06-23 13:27 ` Tomasz Skapski
2016-06-24 3:27 ` Tom Marble
2016-06-27 11:52 ` Michal Kazior
2016-06-27 12:42 ` Tom Marble
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=87y45xiuts.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=tmarble@info9.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox