From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Mike Edenfield <kutulu@kutulu.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: iwl3945: disassociating from current AP on rescan with kernels > 3.0
Date: Wed, 18 Jan 2012 15:07:05 +0100 [thread overview]
Message-ID: <20120118140702.GA6628@redhat.com> (raw)
In-Reply-To: <000301ccccf7$0c9fa800$25def800$@kutulu.org>
On Fri, Jan 06, 2012 at 11:44:32PM -0500, Mike Edenfield wrote:
> > Problem looks more like software scanning issue, which we enable
> > by default on 2.6.39. Can you check if disable_hw_scan=0 module
> > parameter helps?
>
> Wow, this appears to have fixed my problem, at least so far. I'm a little
> worried because I had the module parameter set /on/ (disable_hw_scan=1) from
> way back when I first built this laptop and couldn't stay connected to our
> work LAN. I didn't realize that was on by default. I've switched it to be
> off now and hopefully it won't be a problem.
So on one AP you have to do disable_hw_scan=1 to make things work,
and on other one you have to do disable_hw_scan=0 ? Ehh bugger.
Since bugzilla.kernel.org is back again, please report these problem
there. Once you'll open the bug reports, I'll ask you for more info.
Before opening bug reports, please check if by chance problems are
not fixed in the latest kernel version i.e. 3.3-rc1
Thanks
Stanislaw
prev parent reply other threads:[~2012-01-18 14:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 22:46 iwl3945: disassociating from current AP on rescan with kernels > 3.0 Mike Edenfield
2012-01-04 16:31 ` Dan Williams
2012-01-05 11:39 ` Stanislaw Gruszka
2012-01-07 4:44 ` Mike Edenfield
2012-01-18 14:07 ` Stanislaw Gruszka [this message]
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=20120118140702.GA6628@redhat.com \
--to=sgruszka@redhat.com \
--cc=kutulu@kutulu.org \
--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).