iwl3945-module doesn't work with Intel 3945 WLAN :-( ?

by the way, i have no encryption activated, so that isn't the problem...

some debug-outputs:

ifconfig
eth0 Link encap:Ethernet Hardware Adresse 00:16:d3:9c:02:21
          UP BROADCAST MULTICAST MTU:1500 Metrik:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lo Link encap:Lokale Schleife
          inet Adresse:127.0.0.1 Maske:255.0.0.0
          inet6-Adresse: ::1/128 Gültigkeitsbereich:Maschine
          UP LOOPBACK RUNNING MTU:16436 Metrik:1
          RX packets:12512 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12512 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:0
          RX bytes:626443 (611.7 KB) TX bytes:626443 (611.7 KB)

wlan0 Link encap:Ethernet Hardware Adresse 00:19:d2:c9:f2:2e
          inet Adresse:192.168.0.109 Bcast:192.168.0.255 Maske:255.255.255.0
          inet6-Adresse: fe80::219:d2ff:fec9:f22e/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1
          RX packets:105 errors:0 dropped:0 overruns:0 frame:0
          TX packets:82 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX bytes:35480 (34.6 KB) TX bytes:10415 (10.1 KB)

wmaster0 Link encap:UNSPEC Hardware Adresse 00-19-D2-C9-F2-2E-00-00-00-00-00-00-00-00-00-00
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

iwconfig

wlan0 IEEE 802.11g ESSID:"MYNETWORK" Nickname:""
          Mode:Managed Frequency:2.427 GHz Access Point: 00:13:46:2A:33:A3
          Bit Rate=11 Mb/s Tx-Power=27 dBm
          Retry min limit:7 RTS thr:off Fragment thr=2346 B
          Power Management:off
          Link Quality=82/100 Signal level=-51 dBm Noise level=-127 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

iwlist scan

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 Scan completed :
          Cell 01 - Address: 00:13:46:2A:33:A3
                    ESSID:"MYNETWORK"
                    Mode:Master
                    Channel:4
                    Frequency:2.427 GHz (Channel 4)
                    Quality=77/100 Signal level=-57 dBm Noise level=-127 dBm
                    Encryption key:off
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
                    Extra:tsf=0000000062df5b61
route -n

Kernel-IP-Routentabelle
Ziel Router Genmask Flags Metric Ref Use Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 wlan0
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 wlan0

dhclient

There is already a pid file /var/run/dhclient.pid with pid 10384
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wmaster0/
Sending on LPF/wmaster0/
Listening on LPF/eth0/00:16:d3:9c:02:21
Sending on LPF/eth0/00:16:d3:9c:02:21
Listening on LPF/wlan0/00:19:d2:c9:f2:2e
Sending on LPF/wlan0/00:19:d2:c9:f2:2e
Sending on Socket/fallback
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPREQUEST of 192.168.0.109 on wlan0 to 255.255.255.255 port 67
DHCPACK of 192.168.0.109 from 192.168.0.1
bound to 192.168.0.109 -- renewal in 289951 seconds.

I guess i got the reason for myself: hardy includes only the iwl 3945 (open, not working) driver instead of the ipw 3945 (proprietary, but working with gutsy and previous versions) but don't know how to fix it.. Have I really to downgrade my kernel to gutsy-generic to continue using ipw 3945?? :-((

Is there any other solution to get it working with 2.24 kernel (without recompiling the whole kernel)?

Hi ,

I do had the same problem.
My wifi was working fine Ubuntu 7.10 with restricted driver. In Hardy the restricted driver for Wireless card is not listed at all.

So using Package manager install ndisgtk.

after that you will find System - Administration - Windows Wireless Driver.

Download corresponding windows driver and install using this interface.

Once you restart the system wifi will start working. this will help you to install proprietary driver.

thx for the hint. That would be with ndiswrapper i guess. (not really my wish but surely a working solution) i'll try it if my current method prooves not enought stable.

my current solution: activate backports repo, install linux-backports-modules-hardy-generic then reboot, after reboot i made sure the iwl3945 and the iwlwifi_mac??? modules loaded, made a new file /etc/modprobe.d/iwl3945 with following content:
"
alias wlan0 iwl3945
options iwl3945 disable_hw_scan=1
"

run "depmod -ae" and restart again, then it should be working.. (I'm not really sure what was the command which really solved it but that are all methods I read about to fix "any" problem with iwl3945, and one of them, or the combination worked for me)

I've got the same problem on a Toshiba Tecra A6 laptop, with the Intel 3945ABG wireless interface.

Trying ndiswrapper didn't work, as the network I'm trying to connect to is WPA Enterprise and dmesg shows that this was not supported by ndiswrapper with Intel's driver.

dei, please could you provide more details on how you got this to work? I don't have internet access on the laptop, so I can't use the package managers provided.

Sadly the connection wasn't really stable and it didn't connect after some reboots. So I decided to install the windows-driver with ndiswrapper. No problems installing it, but as soon as I wanted to connect to a WPA-Network, NetworkManager --no-daemon spit out a whole bunch of errors and doesn't seem to get the network's shared-key:

NetworkManager: <debug> [1210141271.731083] nm_device_802_11_wireless_get_activation_ap(): Forcing AP 'MARS'
NetworkManager: <info> User Switch: /org/freedesktop/NetworkManager/Devices/wlan0 / MARS
NetworkManager: <info> Deactivating device wlan0.
CTRL-EVENT-TERMINATING - signal 15 received
sendmsg(CTRL_IFACE monitor): No such file or directory
NetworkManager: <WARN> nm_device_802_11_wireless_set_essid(): error setting ESSID to '' for device wlan0: Invalid argument
NetworkManager: <info> Device wlan0 activation scheduled...
NetworkManager: <info> Activation (wlan0) started...
NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
NetworkManager: <info> Activation (wlan0/wireless): access point 'MARS' is encrypted, but NO valid key exists. New key needed.
NetworkManager: <info> Activation (wlan0) New wireless user key requested for network 'MARS'.
NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.

but no pwd-request pops up (nm-applet is showing "Waiting for network secret...")

second start:
NetworkManager: <info> starting...
NetworkManager: <info> New VPN service 'vpnc' (org.freedesktop.NetworkManager.vpnc).
NetworkManager: <info> eth0: Device is fully-supported using driver 'e100'.
NetworkManager: <info> nm_device_init(): waiting for device's worker thread to start
NetworkManager: <info> nm_device_init(): device's worker thread started, continuing.
NetworkManager: <info> Now managing wired Ethernet (802.3) device 'eth0'.
NetworkManager: <info> Deactivating device eth0.
NetworkManager: <info> wlan0: Device is fully-supported using driver 'ndiswrapper'.
NetworkManager: <info> wlan0: driver does not support SSID scans (scan_capa 0x00).
NetworkManager: <info> nm_device_init(): waiting for device's worker thread to start
NetworkManager: <info> nm_device_init(): device's worker thread started, continuing.
NetworkManager: <info> Now managing wireless (802.11) device 'wlan0'.
NetworkManager: <info> Deactivating device wlan0.
NetworkManager: <WARN> nm_device_802_11_wireless_set_essid(): error setting ESSID to '' for device wlan0: Invalid argument
NetworkManager: <info> Updating allowed wireless network lists.
NetworkManager: <info> Updating VPN Connections...
NetworkManager: <WARN> nm_dbus_get_network_data_cb(): message arguments were invalid (could not deserialize wireless network security information.
NetworkManager: <info> User request to disable wireless.
NetworkManager: <info> Deactivating device wlan0.
NetworkManager: <WARN> nm_device_802_11_wireless_set_essid(): error setting ESSID to '' for device wlan0: Invalid argument
NetworkManager: <info> User request to enable wireless.

And nothing more happens (and I can't see my Networks any more)

I tried to connect to another wlan in my reach (unsecured), it connects but is really unstable and NetworkManager spits out the following errors ever-repeating:
ioctl[SIOCGIWSCAN]: Resource temporarily unavailable
ioctl[SIOCGIWSCAN]: Resource temporarily unavailable
ioctl[SIOCGIWSCAN]: Resource temporarily unavailable
ioctl[SIOCGIWSCAN]: Resource temporarily unavailable
ioctl[SIOCGIWSCAN]: Resource temporarily unavailable
ioctl[SIOCGIWSCAN]: Resource temporarily unavailable
ioctl[SIOCGIWSCAN]: Resource temporarily unavailable
ioctl[SIOCGIWSCAN]: Resource temporarily unavailable
ioctl[SIOCGIWSCAN]: Resource temporarily unavailable
NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one.
ioctl[SIOCGIWSCAN]: Resource temporarily unavailable

(the same thing I already had with iwl3945 driver, and couldn't fix it some times)

any idea what could it be? Regarding the many new bugs connected with iwl and the new NetworkManager and my different error-messages I think I'm having more than one bug involved.

deactivating the wpa-encryption helped, but now my network is only limited to some mac-addresses (not really secure). I'm stil working with ndiswrapper.
Would be cool if someone could give me a tip how I can reinstall the ipw3945 module on the 24 kernel and the good old feisty-version networkmanager.

I gave up with ndiswrapper as it wouldn't work with my University's WPA Enterprise enterprise network, but after returning to the original driver and messing around I finally got it to work! It's been working consistently for a week now.

Unfortunately, it's difficult to work out exactly how I fixed it! However, if you want any details about how my system is configured I can provide them.

Cheers

Dave

Hello, I had / have similar problems. I tried wicd and NetworkManager. But in both cases the key point was if I had PERFECT wifi signal during connection initialization. If I took my laptop < 5 meters from the router, connection has been successful and I could leave this area and still worked perfectly. Currently I have NetworkManager + linux-backports-modules-2.6.24-16-generic

jlechner@NTB2007:~$ lsmod | grep iw
iwl3945 93940 0
iwlwifi_mac80211 219108 1 iwl3945
cfg80211 15112 1 iwlwifi_mac80211
led_class 6020 1 iwl3945

jlechner@NTB2007:~$ lspci | grep 3945
10:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)

ifconfig, iwconfig same as described above

So currently, if I lost connection, I go near to the router, restart connection and next I go back ;-)

It seems http://linuxexpert.wordpress.com/2008/04/28/fix-intel-wireless-driver-on-hardy solved problem for me...

I added this file as part of my fix, but it didn't seem to work straight away. After messing with loading the modules it eventually did work.

The problems vanished for me somewhere between hardy and jaunty, so for me its solved.