From: Kyle McMartin <kyle@mcmartin.ca>
To: Dan Williams <dcbw@redhat.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
Kyle McMartin <kyle@mcmartin.ca>,
linux-wireless@vger.kernel.org
Subject: Re: iwl4965: slow scans
Date: Mon, 21 Apr 2008 14:49:11 -0400 [thread overview]
Message-ID: <20080421184911.GB19802@phobos.i.cabal.ca> (raw)
In-Reply-To: <1208800976.32409.0.camel@localhost.localdomain>
On Mon, Apr 21, 2008 at 02:02:56PM -0400, Dan Williams wrote:
> Yeah, could be an NM issue or a supplicant issue I guess. Or, even if
> the card _is_ returning scan results, it might not be returning results
> for your AP.
>
I'm also poking the card with iwlist with NM off, and still see huge
delays waiting for the network to show up.
> Do you have hardware or software scanning on (ie, is disable_hw_scan
> module option 1 or 0?)
>
It's pretty invariant... disable_hw_scan=1 seems to be a bit faster, but
also breaks the second suspend, unless you unload the module first.
regards, Kyle
prev parent reply other threads:[~2008-04-21 18:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 16:03 iwl4965: slow scans Kyle McMartin
2008-04-21 17:41 ` John W. Linville
2008-04-21 18:02 ` Dan Williams
2008-04-21 18:49 ` Kyle McMartin [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=20080421184911.GB19802@phobos.i.cabal.ca \
--to=kyle@mcmartin.ca \
--cc=dcbw@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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