hardy alpha2 PRO/Wireless 3945ABG does not work

[lizardmenke]

hardy alpha2 live cd the intel wireless 3945abg does not work.
lshw: >clip< *-network
                description: Wireless interface
                product: PRO/Wireless 3945ABG Network Connection
                vendor: Intel Corporation
                physical id: 0
                bus info: pci@0000:06:00.0
                logical name: wmaster0
                version: 02
                serial: 00:18:de:1b:5d:22
                width: 32 bits
                clock: 33MHz
                capabilities: pm msi pciexpress bus_master cap_list logical ethernet physical wireless
                configuration: broadcast=yes driver=iwl3945 latency=0 module=iwl3945 multicast=yes wireless=IEEE 802.11g
>clip<
lsmod gave iwl3945 used by 0
sinds I had a hard time mounting an usb stick (ext3)and being able to write to it during the live session I have little documentation.

[Sarah Kowalik (hobbsee-deactivatedaccount)]

Is this working, but not showing a LED? That's what's happening with mine. I assume your linux-ubuntu-modules is installed on the live cd.

[lizardmenke (lizardmenke)]

It is not working and it is also not showing a LED, if I configure through manual configuration it keeps searchin forever. It also doesn't see any ssid.

[Václav Šmilauer (eudoxos)]

(For the LED, that is separate bug #181255)

[Carybielenberg (cary-bielenberg)]

Mine is not working either, led factor I'm not worried about but I have spent hours working on the wireless problem but to no avail! My config is Lenovo T61 Kubuntu 64bit 2.6.24-3 kernel

[lizardmenke (lizardmenke)]

Trying [Hardy Alpha-3] (Live-cd session) Iwas able to make a wireless connection and it seems to be stable. Eventhough the ssid is not listed, using the 'connect to another wireless network' function helped me establishing a WEP encrypted connection. The LED is still not showing however.

[Vlad (b100dian)]

Hello,
On Hardy Alpha 4, after boot, ipconfig shows eth0 (wired), eth1:00 and wlan0_renamed. The latter seems to have wireless capabilities but doesn't work (manually with iwconfig)
After playing around with ifconfig up/down and ip route the list changed :O to eth0, eth1 and wlan0_renamed. This time wlan0_renamed worked (the exact same iwconfig command)

I think something with udev naming scripts is wrong but I don't have the faintest idea.

[Vlad (b100dian)]

The actual steps to connect with iwconfig on Alpha4 are (to me): rmmod iwl3945 && modprobe iwl3945 && /etc/init.d/dhcdbd stop && iwconfig (your settings here) && dhclient
I am using only wep because of this

[David Nielsen (davidnielsen-deactivatedaccount)]

I can confirm, no network connection possible using the iwl3945 driver and Network Manager (0.6.5 and 0.7) connecting to my WPA2 Personal WLAN. This ia on Alpha 4 as well as Hardy upgraded to daily (7th of Feb).

[reynaldo (rverdejo)]

I'm confirming this on hardy AMD/EMT64 updated to this date.

Today I had this problem using WEP with a 802.11b router but haven't faced it
with WEP on my regular 802.11g one. NetworkManager asks for the keyring passwd
at session init and appears to associate correctly with the AP but the connection
doesn't work. I currently don't have much details but will follow up as soon as I collect
them (I have to get back to the same place tomorrow).

Briefly:

Card: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
Module: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, version: 1.2.0
kernel: 2.6.24-8-generic #1 SMP Thu Feb 14 20:13:27 UTC 2008 x86_64 GNU/Linux

This could be related; I'm seen a lot of messages like this one on syslog:

Feb 21 01:36:53 segfault-delly kernel: [ 354.019822] eth1: RX WEP frame with unknown keyidx 0 (A1=01:80:c2:00:00:00 A2=00:1a:70:58:dc:04 A3=00:1a:70:58:dc:04)

(happens even with the _working_ WEP/802.11g combo)

This sounds like related to https://bugs.launchpad.net/intellinuxwireless/+bug/190475
only that the problem here is not syslog getting filled with trash but the connection not
working at all :-).

Is there someone working on this? I'm of course willing to help getting this fixed.

[Kyle Martin (martikj2-deactivatedaccount)]

I get neither the led light nor a connection with any network requiring some sort of authentication, cannot get onto my WPA2 network at home or the 802.1x network at my university. I am running hardy-i386 on a dell 1420n notebook with all packages up to date as of 5:25 PM CDT, 3/6/08.

[David Nielsen (davidnielsen-deactivatedaccount)]

I did a clean install from the alternative x86_64 cd of March 5, and this is typed on the laptop, connected to my wpa2-psk network. So it's gone for me.

[lizardmenke (lizardmenke)]

[Hardy beta] Network manager is not able to make a connection. It 'sees' the SSID but somehow is not able to connect. Also there is still no led.

[Hieronymus (jslalleman)]

[hardy beta] Same here, nm does see the networks, I can chose one and it will ask for an encryption key but after that it keeps on connecting.

[Emilis Dambauskas (emilis-d)]

[hardy alpha5 with all updates] CAN connect, NO led.

I had a hard time making it work, but succeeded. I had to configure my wireless router to broadcast SSID and use WPA instead of WPA2.

If you change SSID, Network Manager is slow to recognize it and still tries previous configurations for some time. Keyring access by NetworkManager (if you don't bother to make keyring accessible to NM) might also be part of the problem.

[alphamaennchen (m-peintinger)]

I have the same problem. I cannot connect.
This happens after upgrade to hardy development branch (beta with latest upgrade 26.03.2008).
Router broadcasts SSID, encrypts with WEP.

[Emilis Dambauskas (emilis-d)]

[hardy alpha5 with all updates]

Still works for me with broadcast SSID and WPA Personal.

[DoDoENT (dodoentertainment)]

IEEE 802.1X authentication is not working. I can't connect to my university's WLAN. Network is found, but keeps connecting. I tried authentication with wpa_supplicant, but it can't attach to the driver to start the authentication process.

WLAN card: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)

Driver: iwl3945

Linux disribution: Ubuntu 8.04 hardy RC (installed as beta, but installed all updates available until April 19th (date of last test)).

[Palu (dcwolf)]

I can confirm that it doesn't work on the actual 8.04 release (not candidate, but the real thing). 3945abg tested on a Dell Inspiron 6400. I don't know where to find that other information. If someone wants to email me and tell me how, I'll include more info.

[lizardmenke (lizardmenke)]

In my case, with Hardy The official release, The computer now does connect. (wep)
So the iwl3945 driver does actually work now. (in my case)
But there is still no led.

[DoDoENT (dodoentertainment)]

In my case it works too, but only in open networks. I.e. I have no troubles
connecting to my WLAN at home, but I can't connect to my university's WLAN,
which requires 802.1X authentication. Wpa_supplicant just can't attach to
the driver. Here is the output of wpa_supplicant trying to connect to my
university's WLAN:
dodo@2nd-of-12:~$ sudo wpa_supplicant -D wext -i wlan0 -c
/home/dodo/wpa_supplicant/FERwlan.conf
Trying to associate with 00:40:96:54:28:37 (SSID='FERwlan' freq=2412 MHz)
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with 00:40:96:54:28:37 (SSID='FERwlan' freq=2412 MHz)
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with 00:40:96:54:28:37 (SSID='FERwlan' freq=2412 MHz)
Authentication with 00:00:00:00:00:00 timed out.
... and so on...

It used to work (with same config file) with ipw3945 on gutsy.

2008/4/26 lizardmenke <email address hidden>:

> In my case, with Hardy The official release, The computer now does
> connect. (wep)
> So the iwl3945 driver does actually work now. (in my case)
> But there is still no led.
>
> --
> hardy alpha2 PRO/Wireless 3945ABG does not work
> https://bugs.launchpad.net/bugs/178530
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Lian (lian.hui.lui)]

I have the same(?) problem. No LED and cannot detect the networks (Hardy fully updated, same result on Live CD). There is nothing under Wireless Networks in the network manager in the notification area.

I noticed that there is nothing in Restricted Drivers (now renamed to Hardware Drivers in Hardy Heron), while in Gutsy there used to be a proprietary driver for Intel Pro/Wireless.. something.

Running "lspci | grep Wireless" returns:
03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)

[Maxim Veksler (maxim-veksler)]

Not working for me.

I'm updated to the latest debs as of 29.04.2008.

This forum post might be related, http://ubuntuforums.org/showthread.php?t=691955

[WKen Couser (ken-couser-deactivatedaccount)]

Helllo,
Here is my issue. My wireless was working fine under Gutsy Gibson and i upgraded to Hardy Heron. I was getting error messages about 'network.... ' during the upgrade. Now my wireless does not work. No 'restricted drivers' and it is called 'wmaster0' rather than 'wlan0'.
Thank you for your assistance

[lizardmenke (lizardmenke)]

 Allthough PRO/Wireless 3945ABG does connect (manual connection). The last few days (after updates?) it keeps losing connection every 10 minutes or so (very annoying ). -> sudo /etc/init.d/networking restart gets the connection back up again but only to be lost in the next so many minutes again.
Also there is stil no led but I don't know if the one has to do with the other

[khelll (khellls)]

I'm using ubuntu 8.04 on my laptop Compaq nc6400
using lspci i get: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
using ifconfig wlan0 i get :
wlan0 Link encap:Ethernet HWaddr 00:18:de:60:95:11
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

using iwconfig wlan0 i get:
wlan0 IEEE 802.11g ESSID:"" Nickname:""
          Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
          Tx-Power=27 dBm
          Retry min limit:7 RTS thr:off Fragment thr=2346 B
          Power Management:off
          Link Quality:0 Signal level:0 Noise level:0
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

doing iwlist wlan0 scanning i get :

wlan0 Failed to read scan data : Resource temporarily unavailable

[khelll (khellls)]

finally it worked

check Rammy Eid's solution on this link

https://bugs.launchpad.net/ubuntu/+source/linux-backports-modules-2.6.24/+bug/185470/comments/65

[Charlie Daly (cdaly)]

Rammy's solution doesn't work for me.

My hardy installation uses the iwl3945 driver and can connect to an unsecured AP but cannot connect to my WEP AP with a hex key. It tries and then asks me to enter the key again.

If I boot into gutsy using the ipw3945 driver, it connects quickly and without any problems.

[Charlie Daly (cdaly)]

By the way, I don't know if it makes any difference, but I installed Hardy from the alternate CD.

[Wladston Viana (wladston)]

confirming this on an acer aspire, using intel 3945ABG.

This bug made my girlfriend HAVE to stop using Ubuntu, because there is no internet on it :(

Proposed workaround didn't work. Running ubuntu 8.04 with all the backports updates.

[Maxim Veksler (maxim-veksler)]

@Wladston Viana: What are you talking about, this bug forced ME into start using Vista! [because that's the only OS my girlfriend has on her laptop, with mine being offloaded because of the WiFi].

;)

[startling (mark-starling)]

I'm still running Feisty because it's the only Ubuntu version that will connect to wireless networks - and even then it's not working as well as it should; when I try to log onto some networks it won't connect and I have to boot into Vista (always an embarrassment for an Ubuntu advocate like me). Annoyingly, Vista's wireless connection also seems to be quicker.

I tried 7.10 but no luck, and 8.04 also doesn't work. It's a shame because I'd really like to upgrade.

My laptop is a Toshiba A100 with 3945ABG wireless.

[JimBurton (jim-sdf-eu)]

I have the same sort of problem with this driver on a Samsung q45 laptop running hardy official release. I removed encryption from my network but still can't connect.

None of the solutions discussed here worked for me.

[JimBurton (jim-sdf-eu)]

Switching kernels from 2.6.24-19 to 2.6.22-15 fixed it for me.

[sanijabo (sanijabo)]

it is unfortunate that i tried several options from the forum but i still cannot connect to my wlan, ubuntu 8.04 is running on my acer aspire, though i connect via lan and updated regularly but there is no detection of my wlan. help out pls with any further solution.

[Dimitrios Symeonidis (azimout)]

can the subscribers please confirm that this is still an issue for you?

also, be informed that the closed-source ipw3945 driver (which some of you used until gutsy) was replaced in newer linux kernels by the open-source iwl3945 driver, and ipw3945 was deprecated.

what is also strange is that i also have the 3945 chipset, and i've never had a problem, under gutsy, hardy or intrepid...

[startling (mark-starling)]

At last, Intrepid seems to work! I have tried Gusty and Hardy and neither worked. I ran the live CD of Intrepid as a test and it worked.

[Hieronymus (jslalleman)]

The problem still exists within Ubuntu 8.04.1, but the workaround using ndiswrapper works fine. In Ubuntu 8.10 the problem is gone. So, for me it isn't an issue anymore.

Jeroen

[lizardmenke (lizardmenke)]

In 8.04.1 it works fine, only the led doesn't work but that's a minor thing.
In intrepid everything works, also the led.

[Charlie Daly (cdaly)]

Same as Hieronymus.

[DoDoENT (dodoentertainment)]

It works for me in intrepid, but it still has low scan sensitivity - much lower that ipw3945 had.

[Dimitrios Symeonidis (azimout)]

assigning to the linux source package

[Christian Johansson (christian.johansson)]

I'm having this problem too and I have the same network card. I just upgraded from 7.10 to 8.04 and now Network-Manager won't connect to my wireless router (with WPA2 encryption) anymore. It just tries forever. However, the network is shown to exist in Network-Manager.

If I issue the "sudo iwlist scan" command to scan for my network, it also acts strangely. The scan stops for a long while at eth1 (my wireless interface) and then most of the time it says "No scan results". Only at rare occasions, it shows my network although the router is very close to the computer and I know the signal strength is good.

What a pity this is. Wireless networking has worked fine for me in 6.10, 7.04 and 7.10 and now when I update to 8.04 LTS that I had intended to stay with for a few years, it doesn't work anymore.

[DoDoENT (dodoentertainment)]

This is fixed in intrepid ibex. You should upgrade to version 8.10.

[Christian Johansson (christian.johansson)]

No, I don't want to upgrade to 8.10. I get so stressed by upgrading once every half year and the errors it often introduces to upgrade so I have been longing for the day when I have upgraded to an LTS version. Therefore, now when I finally have got to an LTS version, I plan to stick with it for a couple of years. I expect that errors that exist in 8.04 should be fixed.

[Dimitrios Symeonidis (azimout)]

dodonet, christian is right, 8.04 is supported until April 2011!
Christian, could you please try with an Intrepid livecd (or liveusb) and tell us if the issue is actually fixed for you in 8.10? The fix would in this case have to be backported to 8.04...
If not, you're having a different issue

[Christian Johansson (christian.johansson)]

Some more detailed information:

I have tested twice to disconnect the Ethernet cable after the computer has been started and both times the connection to the wireless router by Network Manager has worked although it has taken a long time (over 1 minute).

I have also tested twice to start up the computer without an Ethernet cable inserted and both times Network Manager has failed to connect to the wireless router (has given up after 2 minutes). I have tried a few more times to let Network Manager connect but that has also failed.

I attach a log from the case of starting the computer with no Ethernet cable inserted (an excerpt from /var/log/syslog/).

I will also attach a log for the case when the Ethernet cable is unplugged.

My router is set to use WPA2 with AES encryption and I had no problem to connect to it under Ubuntu 7.10.

 I'm using Ubuntu 8.04.1, Kernel version 2.6.24-22.

[Christian Johansson (christian.johansson)]

Attached is the relevant excerpt from /var/log/syslog for the unplugging Ethernet cable case that I mentioned as well.