linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Thomas Bächler" <thomas@archlinux.org>
To: linux-wireless@vger.kernel.org
Cc: ipw3945-devel@lists.sourceforge.net
Subject: iwl3945 driver is still unusable!
Date: Sun, 13 Jan 2008 10:33:58 +0100	[thread overview]
Message-ID: <fmclu6$dvl$1@ger.gmane.org> (raw)

Some history of this problem can be found here:
http://bughost.org/bugzilla/show_bug.cgi?id=1468

I want to describe my problem here again to get some more people to pay
attention, as Intel doesn't seem to be able to reproduce this problem,
although it is quite easy and I am not the only one who experiences it.

I will start with my setup: I own a Lenovo 3000 N100, which includes a
Core 2 Duo CPU and an Intel 3945ABG Wireless LAN chip. I am working with
Archlinux x86_64 and use wpa_supplicant 0.5.9 (0.5.8 and 0.5.7 in the
past) combined with autowifi, a small tool that starts dhclient
automatically once a wireless connection has been established by
wpa_supplicant.

I am roaming with my Laptop a lot, so I have to switch between networks
often. After I had some problems with the driver over half a year ago, I
 figured out this test case:

- Connect to my own WPA network.
- Tell wpa_supplicant to switch to an open network.
- Switch to another open network or (if none available) back to my WPA
network.

The first network I use after loading the driver always works fine.
After some switching networks (always the second or at most third
network I try to connect to), I don't get DHCP anymore. Sometimes I
still get a DHCPNAK, but after that, there is no response to my
DHCPDISCOVER messages. When apppropriate, I assign a static IP and still
cannot transmit any traffic. However, I can always reconnect to the last
working network (so long-term, the driver works with exactly one network).

One of the debug outputs I generated for the bug report (see above)
suggests that only the first package is transmitted over the link, after
that no data is transmitted at all!

This problem persists even if I
- restart wpa_supplicant
- unload the driver and the mac80211 stack completely and reload them
- do both of the above and then suspend to RAM, then resume later and
try again

This issue is not limited to switching between encrypted and unencrypted
networks. I am pretty sure that if I connect to my WPA network here at
home, go to the university and connect to their WPA network, the issue
persists (however, this is not a practical test case, as there is a 30
minute walk in between).

These are the test cases I did today (I could get similar results with
older kernel versions and drivers):

Linux 2.6.23.13, iwlwifi 1.2.23 from Intel's website:
- Connect to WPA network succeeds
- Connect to an open network succeeds
- Going back to the WPA network: Associates fine, but no DHCP, with
static IP no traffic can be transmitted

Linux 2.6.24-rc7-gd0c4c9d4 (latest git as of today), included iwl3945
version:
- Connect to WPA network succeeds
- Connect to an open network: Associates fine, no DHCP (same network
that I could connect to in the last test).

Linux 2.6.24-rc7-gd0c4c9d4 (latest git as of today), iwlwifi 1.2.23:
- Does not compile!

All these test cases _always_ worked perfectly with the old ipw3945
driver. Unloading the iwl driver and loading the ipw driver always makes
my connection work again. BUT, the ipw3945 driver has been discontinued
and does not compile anymore with 2.6.24 (as iwl3945 is considered a
replacement, which it is obviously not).
All this means, if I update to 2.6.24 (which I want to, due to several
improvements), I have no usable driver for my wireless anymore.

What I need is a solution, meaning either a working iwl3945 version or a
patch to ipw3945 to compile with 2.6.24.

Thanks in advance for any help or comments.


             reply	other threads:[~2008-01-13  9:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-13  9:33 Thomas Bächler [this message]
2008-01-13 10:17 ` [ipw3945-devel] iwl3945 driver is still unusable! Jerone Young
2008-01-18  6:55 ` Thomas Bächler
2008-01-18 16:09   ` Chatre, Reinette
2008-01-18 20:42     ` Thomas Bächler
2008-01-18 21:09       ` Chatre, Reinette
2008-01-19  2:04         ` [ipw3945-devel] " Jerone Young
2008-01-19  8:53           ` drago01
2008-01-20 10:43         ` Thomas Bächler

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='fmclu6$dvl$1@ger.gmane.org' \
    --to=thomas@archlinux.org \
    --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).