From: Michael Buesch <mb@bu3sch.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Priit Laes <plaes@plaes.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [REGRESSION] Trouble seeing some wireless networks in latest git
Date: Sun, 27 Apr 2008 17:48:49 +0200 [thread overview]
Message-ID: <200804271748.49377.mb@bu3sch.de> (raw)
In-Reply-To: <48149F2B.4000503@lwfinger.net>
On Sunday 27 April 2008 17:43:39 Larry Finger wrote:
> Priit Laes wrote:
> > Hey,
> >
> > There seems to be some kind of regression in wireless drivers that makes
> > it not possible to see some wireless networks.
> >
> > This can be seen with both b43 and iwl3945 drivers.
> >
> > Using Kismet wireless scanner these networks were visible under latest
> > git.
> > All the networks rendered invisible seem to be from channels: 1 (one
> > network visible), 3, 8, 12 and 13. Visible networks are in channels 1,
> > 4, 6, 9 and 11.
> >
> > Any hints how to debug this further?
>
> This regression sounds like a perfect place to use git bisection. As it affects
> b43 and iwl3945, I would suspect some change in mac80211.
Nah, it's a regulatory setting issue.
The default regdomain is US, which only allows chans 1-11.
There's some module parameter to switch the regdomain.
This is not a regression, but a feature.
--
Greetings Michael.
next prev parent reply other threads:[~2008-04-27 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 9:24 [REGRESSION] Trouble seeing some wireless networks in latest git Priit Laes
2008-04-27 15:43 ` Larry Finger
2008-04-27 15:48 ` Michael Buesch [this message]
2008-04-27 17:00 ` Priit Laes
2008-04-27 17:04 ` Brian Morrison
2008-04-28 17:38 ` Johannes Berg
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=200804271748.49377.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=plaes@plaes.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).