From: Francesco Saverio Schiavarelli <fschiava@libero.it>
To: linux-wireless@vger.kernel.org
Subject: brcm80211: brcmsmac not working on channel 13
Date: Tue, 06 Mar 2012 19:56:25 +0100 [thread overview]
Message-ID: <jj5mkp$he9$1@dough.gmane.org> (raw)
Hi,
using my MacMini 4,1 integrated wireless adapter on kernel 3.2 and
brcmsmac I cannot connect to AP on channel 13, other 2.4 GHz channels
work fine.
When booting MacOsX with the same AP on channel 13 it works.
My distro is Debian and I tried to set country code via:
- iw reg set
- crda
- setting the AP to broadcast country code
but made no difference.
The very same issue with detailed symptoms is described here:
http://133nux.blogspot.com/2011/12/missing-channel-13-this-time-broadcom.html
I tried the fix proposed in the above page, basically in
brcmsmac/channel.c struct locale_info change from
LOCALE_RESTRICTED_SET_2G_SHORT to LOCALE_RESTRICTED_NONE.
To me this seems like a hack, but works. Can you please comment?
Is this a bug or the code was intented that way?
if the latter how am I supposed to use channel 13?
uname and lspci output follows:
> frankio@debmini:~$ uname -a
> Linux debmini 3.2.0-1-686-pae #1 SMP Fri Feb 17 06:27:21 UTC 2012 i686 GNU/Linux
> frankio@debmini:~$ lspci -v -d 14e4:4353
> 03:00.0 Network controller: Broadcom Corporation BCM43224 802.11a/b/g/n (rev 01)
> Subsystem: Apple Computer Inc. Device 0093
> Flags: bus master, fast devsel, latency 0, IRQ 21
> Memory at d3300000 (64-bit, non-prefetchable) [size=16K]
> Capabilities: <access denied>
> Kernel driver in use: brcmsmac
thank you
Francesco
reply other threads:[~2012-03-06 19:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='jj5mkp$he9$1@dough.gmane.org' \
--to=fschiava@libero.it \
--cc=linux-wireless@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).