the iwl3945 driver will not connect to my open, 802.11 b, linksys AP

[Johne]

I have an Intel Pro Wireless 3945 chip set in my 1420 dell. After a clean install of hardy, i am unable to connect to my wireless access point. I have attached my deamon.log

[Johne (simsonloverforever)]

The ipw3945 driver works perfectly. The iwl3945 driver broke my wireless.

[Johne (simsonloverforever)]

https://bugs.launchpad.net/ubuntu/+bug/200064 might be related to this issue

[Johne (simsonloverforever)]

Network Manager doesn't work, although it scans, it does not connect to open b networks.

[Pres-Gas (presgas)]

I can confirm this and I get the same log entries. I have tried this on a Belkin b router with wep encryption and a Linksys b router configured as both open and wpa. My logs are pretty much the same, but would be happy to post them if you wish. I have them stored.

[James Westby (james-w)]

Hi,

It is not clear if this is a network manger or module
problem, so I'm starting with network manager.

It would be useful if you could test connecting
via the command line to find out.

Thanks,

James

[Michael Schultheiss (schultmc)]

I'm seeing similar log entries with my Linksys WRT54GL router with WPA. I haven't yet tried my Netgear G with WEP but I imagine it would have similar issues.

I'll try connecting via the command line to see if NetworkManager is the problem.

[Michael Schultheiss (schultmc)]

This definitely appears to be a NetworkManager problem rather than a problem with the iwl3945 driver. I installed wicd (http://wicd.sourceforge.net) and was able to connect to my WPA enabled G router without any issues.

[Pres-Gas (presgas)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'd sure like to see what you get on the wep router with
network-manager, for thoroughness. I just found out the the b router
that I have that can do wpa is borked and wicd is still not playing nice
with wep. Since this bug is associated with network-manager, let's try
that if possible.

Michael Schultheiss wrote:
> This definitely appears to be a NetworkManager problem rather than a
> problem with the iwl3945 driver. I installed wicd
> (http://wicd.sourceforge.net) and was able to connect to my WPA enabled
> G router without any issues.
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFH7rIDup357T5MfTYRApapAJ4xoqZubXvJmfkbjXWZe1m5YHLTqgCguGcp
6AeEvE8DYzkEgBQelZucqEY=
=UzFK
-----END PGP SIGNATURE-----

[Johne (simsonloverforever)]

it looks like a kernel problem to me. i only say that because if i boot up the 2.6.24-3-generic kernel, from an early alpha, wireless with network manager works perfectly with the ipw3945 driver and the iwl3945 driver. Compared with the 2.6.24-12-generic kernel. Also i have tried connecting to my AP from the cmd line with both kernels and only 2.6.24-3-generic will connect.

[syko21 (syko21)]

I have the same problem except I am nearly certain that the problem is with the iwl3945 driver since a downgrade to gutsy's ipw3945 fixes all connections issues. I can connect to my unprotected G network at home but not my unprotected B only network at school.

[syko21 (syko21)]

Forgot to write that I also attempted using wicd and the beta network-manager 0.7 to connect also with no luck. Command line also failed in connecting. I can't post any logs since I had to revert to gutsy though, I need my internet to work at school.

[Andreas Mueller (muellera)]

installing the driver from http://linuxwireless.org/en/users/Download manually fixed the problem for me

[Pres-Gas (presgas)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Just aptitude-ed the kernel update that gives me iwl3945 1.2.25. I will
test tonight.

Andreas Mueller wrote:
> installing the driver from http://linuxwireless.org/en/users/Download
> manually fixed the problem for me
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFH9Nxgup357T5MfTYRAttfAKCpcRJjh5QBrIwRmc8u5cxOJ/70mgCgidzC
3gYXtKqlA+ZTq4ukhV3Gn9g=
=qCj9
-----END PGP SIGNATURE-----

[Andreas Mueller (muellera)]

mine is 1.2.26k

[Pres-Gas (presgas)]

Kernel update 2.6.24-14-generic updated iwl and I can confirm this fixed the issue. I can now join to my wireless b router open and wep-ed.

[Johne (simsonloverforever)]

using the new 2.6.25-rc8 kernel fixes it for me, but none of the Ubuntu hardy kernels except 2.6.24-3 works for me. Since I copied the firmware from /lib/firmware/2.6.24-3-generic to /lib/firmware/2.6.25-rc8-custom/, i think that maybe it could be the firmware?

[Johne (simsonloverforever)]

The firmware is not the problem. It is the driver that is at fault. I download, and compile drivers from intelwireless.org on my 2.6.24-15 kernel, everything works. Ubuntu needs to included the updated drivers in their kernel.

[syko21 (syko21)]

I tried using the up to date compatwireless drivers and still find myself unable to connect to unencrypted B access points at my school. Although the problem is only with some of the access points. Below is an output of the relevant portion of dmesg.
[ 51.120088] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26k
[ 51.120093] iwl3945: Copyright(c) 2003-2008 Intel Corporation
[ 51.120189] ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
[ 51.120211] PCI: Setting latency timer of device 0000:02:00.0 to 64
[ 51.120233] iwl3945: Detected Intel Wireless WiFi Link 3945ABG
[ 51.162781] iwl3945: Tunable channels: 11 802.11bg, 13 802.11a channels
[ 51.164328] phy0: Selected rate control algorithm 'iwl-3945-rs'
[ 51.181679] ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
[ 51.281520] Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI
[ 51.281524] Copyright (c) 1999-2006 Intel Corporation.
[ 51.281669] PCI: Enabling device 0000:05:00.0 (0000 -> 0003)
[ 51.281676] ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 18 (level, low) -> IRQ 18
[ 51.281693] PCI: Setting latency timer of device 0000:05:00.0 to 64
[ 51.339740] e1000: 0000:05:00.0: e1000_probe: (PCI Express:2.5Gb/s:Width x1) 00:16:36:9d:e8:04
[ 51.405426] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 51.405988] e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
[ 53.880810] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 67.950659] wlan0: Initial auth_alg=0
[ 67.950663] wlan0: authenticate with AP 00:a0:f8:a3:7f:57
[ 67.953868] wlan0: RX authentication from 00:a0:f8:a3:7f:57 (alg=0 transaction=2 status=0)
[ 67.953871] wlan0: authenticated
[ 67.953873] wlan0: associate with AP 00:a0:f8:a3:7f:57
[ 68.150533] wlan0: associate with AP 00:a0:f8:a3:7f:57
[ 68.350280] wlan0: associate with AP 00:a0:f8:a3:7f:57
[ 68.549990] wlan0: association with AP 00:a0:f8:a3:7f:57 timed out
[ 71.097998] wlan0: Initial auth_alg=0
[ 71.098004] wlan0: authenticate with AP 00:a0:f8:a3:7f:57
[ 71.098796] wlan0: Initial auth_alg=0
[ 71.098799] wlan0: authenticate with AP 00:a0:f8:a3:7f:57
[ 71.098913] wlan0: RX authentication from 00:a0:f8:a3:7f:57 (alg=0 transaction=2 status=0)
[ 71.098916] wlan0: authenticated
[ 71.098918] wlan0: associate with AP 00:a0:f8:a3:7f:57
[ 71.099145] wlan0: authentication frame received from 00:a0:f8:a3:7f:57, but not in authenticate state - ignored
[ 71.128833] wlan0: associate with AP 00:a0:f8:a3:7f:57
[ 71.148531] wlan0: associate with AP 00:a0:f8:a3:7f:57
[ 71.173210] wlan0: association with AP 00:a0:f8:a3:7f:57 timed out
[ 72.571202] wlan0: Initial auth_alg=0
[ 72.571207] wlan0: authenticate with AP 00:a0:f8:a3:7f:57
[ 72.572853] wlan0: Initial auth_alg=0
[ 72.572855] wlan0: authenticate with AP 00:a0:f8:a3:80:79
[ 72.573402] wlan0: Initial auth_alg=0
[ 72.573404] wlan0: authenticate with AP 00:a0:f8:a3:80:79
[ 72.574528] wlan0: RX authentication from 00:a0:f8:a3:80:79 (alg=0 transaction=2 status=0)
[ 72.574531] wlan0: authenticated
[ 72.574534] wlan0: associate with AP 00:a0:f8:a3:80:79
[ 72.575414] wlan0: au...

[Johne (simsonloverforever)]

skyo21:

looks a lot like my log files. When did you download the source for the drivers? What ubuntu kernel were you using?

[syko21 (syko21)]

I downloaded the compat wireless of 4/7/2008 and was using ubuntu kernel 2.6.24-15. I haven't retried with 2.6.24-16 yet because it screwed around with my envy-ng video drivers and I have to fix that first. A temporary solution I used is to boot into the gutsy kernel I still had and use ipw3945. It let me work where the iwl3945 wouldn't and I hope the problem gets fixed before the release otherwise im on gutsy until intrepid comes out.

[syko21 (syko21)]

Updated the kernel and the driver. Same issue though so unless they come out with a new kernel revision in the next couple weeks I think it'll have to be the gutsy kernel running with ipw.

[Johne (simsonloverforever)]

considering that hardy is due in a couple of days we'll probably will have to wait till intrepid for a ubuntu fix.

[Johne (simsonloverforever)]

Needs fixing really soon, before hardy is released! Should be quite simple to fix.

[Steve Langasek (vorlon)]

Johne,

Have you tried installing the linux-backports-modules-2.6.24-16-generic package? This contains an updated version of the iwl3945 driver which will not be made the default for 8.04, because the version currently in linux-ubuntu-modules is the only one certified by Intel for Centrino. (In other words: the kernel module in l-b-m wouldn't be /better/, it would just give us a /different/ set of bugs).

The iwl3945 driver in l-u-m does work well for most users and the version in l-b-m seems to fix the issues for most others, so I'm marking this bug as 'declined' for hardy.

[bq (balique)]

Upgraded Kubuntu 7.10 to 8.04 RC, the wifi on FS Amilo pro v3405 (module ipw3945) stops working, the knetworkmanager does not show any network.
It is related to the kernel , the Hardy installs and uses by default kernel 2.6.24-16-generic. When I select the 2.6.22-14-generic it works fine again.

lspci with the 2.6.22-14-generic kernel :
02:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02).
If more info needed I am ready to answer on email.

[Roberto Leinardi (leinardi)]

I can confirm this issue in my Fujitsu Siemens P1620.
I also tried to connect with Wicd and with the console but without success.

More info here: http://forum.ubuntu-it.org/index.php/topic,173212.msg1187642.html#msg1187642

[jdwhitfield (jdwhitfield)]

I also have the same bug. When I upgraded my wireless would show the networks from the network manager applet drop down but it would not connect. I tried with the older kernel (2.6.22-14) and then I could connect. I think this is an issue that is fairly serious or at least the work around using 2.6.22-14 should be posted somewhere for newbies. I am using an Lenovo Thinkpad x60s with a Intel PRO/Wireless 3945ABG card.

[syko21 (syko21)]

Using ndiswrapper and the windows driver solved this for me. I know its a crude solution but it works.
instructions are below
http://ubuntuforums.org/showpost.php?p=4790682&postcount=10

note: i also get much better performance with this driver than the iwl3945

[Ben (pumrum)]

is there an automatic patch that will be released so that someone new to ubuntu can install from CD, run all updates, and the 3945 wireless will just work? Seems like this is a very popular chipset, and with Ubuntu wanting to be a mainstream OS, having to hack something together might not be well received by the masses.

[James Westby (james-w)]

On Mon, 2008-05-05 at 16:43 +0000, Ben wrote:
> is there an automatic patch that will be released so that someone new to
> ubuntu can install from CD, run all updates, and the 3945 wireless will
> just work? Seems like this is a very popular chipset, and with Ubuntu
> wanting to be a mainstream OS, having to hack something together might
> not be well received by the masses.
>

Try installing the linux-backports-modules package that is appropriate
for your architecture/kernel. It contains a different version of the
driver that will either improve things for you, or make them worse.

Thanks,

James

[Ben (pumrum)]

>Try installing the linux-backports-modules package that is appropriate
>for your architecture/kernel. It contains a different version of the
>driver that will either improve things for you, or make them worse.
>
>Thanks,
>
>James

Yes, there are plenty of ways to work 'around' the issue -- but what I'm trying to pressure here is that Ubuntu is trying to make a name for itself in the dog-eat-dog world of operating systems, and to not support a very popular wireless chipset out-of-the-box without having to do research and using intermediate level work arounds, well -- that's going to turn a lot of people off to the OS. And this release being LTS means it will be around for a very long time. This is a huge image issue, and as soon as a fix is found it needs to be included into the automatic updates so that new users don't have to do any searching on the internet or finagling with packages. I wish this could have been addressed before they pressed the CD, i see this being a problem for a long time to come now...

[syko21 (syko21)]

The linux-backports method does not work for all cases. It is an updated version of the iwl3945 driver, 1.2.26 instead of 1.2.0. This method does not work for everyone though and it did not work for me. The ndiswrapper solution was the best one I came up with so far. Perhaps when the driver has matured a little it will work as well as the ipw3945 did.

[Bráulio (brauliobo)]

same here (using archlinux and kernel 2.6.26).
really disappointed with the iwl3945 driver

[Leann Ogasawara (leannogasawara)]

Hi Everyone,

This bug was reported a while ago and hasn't had any recent activity. Is this still an issue with the most recent Intrepid Ibex 8.10 release? You should be able to test using a LiveCD. Please let us know your results. For now I'm going to retarget this bug to the actively developed linux kernel package. During the Intrepid development cycle the linux-ubuntu-modules package was merged with the linux kernel package. Thanks.

[syko21 (syko21)]

Seems to be fixed in Intrepid due to the newer iwl3945 module which I believe was the source of the problem.

[Leann Ogasawara (leannogasawara)]

Thanks marking this Fix Released then.