From: Maxim Levitsky <maximlevitsky@gmail.com>
To: linux-wireless <linux-wireless@vger.kernel.org>
Cc: iwlwifi maling list <ipw3945-devel@lists.sourceforge.net>
Subject: IWL3945 problems in 2.6.35-rc1
Date: Tue, 01 Jun 2010 15:25:42 +0300 [thread overview]
Message-ID: <1275395142.14385.6.camel@maxim-laptop> (raw)
Hi,
in 2.6.35-rc1 the wireless became just unusable.
These are problems that I have:
1. very frequent oopses.This appears to be mention on the list already,
but patches I tried don't help.
I currently use this bandaid patch, and I still get some crashes:
diff --git a/drivers/net/wireless/iwlwifi/iwl3945-base.c b/drivers/net/wireless/iwlwifi/iwl3945-base.c
index 3e5bffb..1aef988 100644
--- a/drivers/net/wireless/iwlwifi/iwl3945-base.c
+++ b/drivers/net/wireless/iwlwifi/iwl3945-base.c
@@ -1861,6 +1861,11 @@ static int iwl3945_get_channels_for_scan(struct iwl_priv *priv,
if (!sband)
return 0;
+ if(!priv->scan_request) {
+ WARN_ON(1);
+ return 0;
+ }
+
active_dwell = iwl_get_active_dwell_time(priv, band, n_probes);
passive_dwell = iwl_get_passive_dwell_time(priv, band, vif);
2. mulicast/broadcast is broken.
this results in DHCP non working on open access point.
It seems that DHCP does work on my home wireless, but avahi-autoipd doesn't see any neighbours, and this is annoying.
It can be worked around by doing (sudo ifconfig wlan0 promisc)
Best regards,
Maxim Levitsky
next reply other threads:[~2010-06-01 12:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 12:25 Maxim Levitsky [this message]
2010-06-01 14:57 ` IWL3945 problems in 2.6.35-rc1 Maxim Levitsky
2010-06-01 15:21 ` Sedat Dilek
2010-06-01 18:12 ` Maxim Levitsky
2010-06-02 16:53 ` Maxim Levitsky
2010-06-02 18:01 ` Sedat Dilek
2010-06-01 19:03 ` Abhijeet Kolekar
2010-06-01 19:59 ` Maxim Levitsky
2010-06-02 8:35 ` Sedat Dilek
2010-06-03 6:00 ` reinette chatre
2010-06-03 9:18 ` Sedat Dilek
2010-06-03 15:55 ` reinette chatre
2010-06-18 9:28 ` Johannes Berg
2010-06-18 10:19 ` Maxim Levitsky
2010-06-18 10:30 ` Johannes Berg
2010-06-18 10:40 ` Maxim Levitsky
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=1275395142.14385.6.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;
as well as URLs for NNTP newsgroup(s).