From: Maxim Levitsky <maximlevitsky@gmail.com>
To: linux-wireless <linux-wireless@vger.kernel.org>
Cc: iwlwifi maling list <ipw3945-devel@lists.sourceforge.net>
Subject: [BUG] [REGRESSION] Hardware scanning broken in latest git
Date: Tue, 24 Feb 2009 00:44:03 +0200 [thread overview]
Message-ID: <1235429043.12816.14.camel@maxim-laptop> (raw)
I have just rebuilt a kernel (same kernel, but
I needed few drivers), and using this chance pulled latest
wireless-testing.
result - wifi doesn't work unless I use disable_hw_scan - my wifi
is iwl3945.
Trying to do 'sudo iwlist scan' tells that device is busy.
it seems that at first nm connects, as it receives first scan results.
but then it can't scan again - probably something in scanning code is
broken so it never finishes a scan.
My AP is WPA-2 protected.
Also I noticed long ago that wpa_suppicant doesn't connect to the
network at first try since ts wpa handshake fail. This is probably
its bug, but just for reference - this is very annoying.
(I use latest nm and wpa_supplicant from -git - but this problem have
always existed).
And of course I noticed another very strange bug with iwlwifi.
At my university often I can't connect to the wifi - usually because of
the week signal - but at some rooms I noticed that if I somehow manage
to connect (get dhcp address that is) - connection is very fast and
stable.
In other words association usually works (forgot to say that they use
open network - duh ), then DHCP stalls - but if it succeeds and I move
to different part of the class - even where I never had any reception -
it continues to work well.
(It could be that transmission speed is lowered - but I tried to set low
speed - and never got any better results)
Thats all for bugs I have on my intel wireless - keep up the good work -
recently iwlwifi drivers improved a lot.
(even the led blinks correctly now in monitor mode)
Best regards,
Maxim Levitsky
reply other threads:[~2009-02-23 22:44 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=1235429043.12816.14.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--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