iwl3945 not able to associate with kernel 2.6.26 and 2.6.27

Thanks Rune,

Can you attach your dmesg output after you've booted int 2.6.27-2 instead? Thanks.

Leann,

I've attached various logs that I hope can support the debugging.

Some strange things (see nm-password.png):

1. When upgrading to intrepid, and booting into 27-2, nm-applet did not detect my network, but when I chose "connect to other wireless network" it reasks for the passphrase each tie, with a very log password prefilled in.
My wireless network is not listed in the network list, but neighbor networks are.

2. Same thing happened when booting 24-19, but after a couple of times reentering the password it logged on to the wireless network (but during the process of reentering the password it show the long prefilled password as well)
But with this kernel, my wireless network is listed in the network list (along with neighbor networks).

Attached are the result of `cat /var/log/syslog | grep -i network` using both kernels, as well as dmesg output for both, and the screenshoit of the password dialogue.

Regards,

Rune

I tested a bit further with as Wireless USB device, reported by lsusb as a "ZyDAS 802.11b/g USB2 WiFi".

With this device I can associate with my network using kernel 2.6.27-2.

Please note that nm-applet lists my network (with a bar of around 80%) under the Zydas device, but the network is not listed beneath the intel integrated chipset (network name r-stue, see attached png).

Also note that nm-applet shows no bars in the tray icon, but my wireless network connection trought the zyda device is okay, and iwconfig reports this:
wmaster0 no wireless extensions.

wlan0 IEEE 802.11abg ESSID:""
          Mode:Managed Frequency:2.447 GHz Access Point: Not-Associated
          Bit Rate:54 Mb/s Tx-Power=15 dBm
          Retry min limit:7 RTS thr:off Fragment thr=2352 B
          Power Management:off
          Link Quality=63/100 Signal level:-69 dBm Noise level=-97 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

wmaster1 no wireless extensions.

eth2 IEEE 802.11bg ESSID:"r-stue"
          Mode:Managed Frequency:2.467 GHz Access Point: 00:14:BF:E1:C8:76
          Bit Rate=54 Mb/s Tx-Power=0 dBm
          Retry min limit:7 RTS thr:off Fragment thr=2352 B
          Power Management:off
          Link Quality=100/100 Signal level:32/100
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

I have a similar problem: The WLAN (iwl3945, Intel Corporation PRO/Wireless 3945ABG) associates, then disassociates about 5 seconds later, then associates, then disassociates, and so on. Also, association takes very long (about 30 seconds).
This happens with linux-image-2.6.27-4-generic in intrepid.

Syslog:

NetworkManager: <info> (wlan0): supplicant connection state change: 0 -> 4
kernel: [ 1730.920804] wlan0: authenticate with AP xx
kernel: [ 1730.920822] wlan0: authenticated
kernel: [ 1730.920828] wlan0: associate with AP xx
kernel: [ 1730.920846] wlan0: RX ReassocResp from xx (capab=0x431 status=0 aid=1)
kernel: [ 1730.920851] wlan0: associated
NetworkManager: <info> (wlan0): supplicant connection state change: 4 -> 5
NetworkManager: <info> (wlan0): supplicant connection state change: 5 -> 0
NetworkManager: <info> (wlan0): supplicant connection state change: 0 -> 2
kernel: [ 1741.924126] wlan0: disassociating by local choice (reason=3)
NetworkManager: <info> (wlan0): supplicant connection state change: 2 -> 0
kernel: [ 1745.654378] wlan0: deauthenticated
kernel: [ 1745.654776] wlan0: authenticate with AP xx
NetworkManager: <info> (wlan0): supplicant connection state change: 0 -> 3
NetworkManager: <info> (wlan0): supplicant connection state change: 3 -> 0
kernel: [ 1745.660391] wlan0: authenticate with AP xx
kernel: [ 1745.660433] wlan0: authenticated
kernel: [ 1745.660438] wlan0: associate with AP xx
kernel: [ 1745.664160] wlan0: authenticate with AP xx
kernel: [ 1745.664183] wlan0: authenticated
kernel: [ 1745.664188] wlan0: associate with AP xx
NetworkManager: <info> (wlan0): supplicant connection state change: 0 -> 4
kernel: [ 1745.668771] wlan0: RX ReassocResp from xx (capab=0x431 status=0 aid=1)
kernel: [ 1745.668781] wlan0: associated
NetworkManager: <info> wlan0: link timed out.
NetworkManager: <info> Activation (wlan0/wireless): association took too long.

Same here!

But only in a certain networks!

In my work, using WPA2 is working fine, (intrepid,2.6.27-4) but in my house the problem is the same as sebastian.

Hardware and dmesg attached.

SUCCESS CONNECTION DMESG

I have the same problem in my house. I use Intrepid which I update everyday, a IPW3945 with iwl3945 driver and NetworkManager to connect to my home wifi which is protected with WPA2 personal. I can't connect and obtain a line "Link timed out" and "Association took too long" at the next line in the daemon.log.

Got very similar problem with nm but with 2.6.24-21.
It looks to me that it may be related to the signal strength and or the proximity of another AP with signal level close to the one to which i'm connected at the moment.
If I work at a couple of meter from my home AP nm seems to never lose the connection.

sudo modprobe -l iwl*
/lib/modules/2.6.24-21-generic/ubuntu/wireless/iwlwifi/mac80211/compatible/net/mac80211/iwlwifi_mac80211.ko
/lib/modules/2.6.24-21-generic/ubuntu/wireless/iwlwifi/mac80211/compatible/net/mac80211/iwlwifi_rc80211_simple.ko
/lib/modules/2.6.24-21-generic/updates/iwl3945.ko
/lib/modules/2.6.24-21-generic/updates/iwl4965.ko
/lib/modules/2.6.24-21-generic/updates/iwlcore.ko

Truxpin,

My wireless connection worked fine until I upgraded to 24-21 in hardy, and later all intrepid kernels.

Do you get similar errors in your syslog as I get ? See attached part of syslog where I attempt to associate (at a distance of 1 m from the AP).

I can successfully associate with a Zydas USB stick without problems using the same computer.

Rune

Also, using 2.6.27-7 I get a different dmesg output than XaRs and myself (using 2.6.27-2, see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264881/comments/3).

I get lots of
[12455.744842] iwl3945: No space for Tx
[12455.744846] iwl3945: Error sending REPLY_LEDS_CMD: iwl3945_enqueue_hcmd failed: -28

and as an example I don't get
phy0: Selected rate control algorithm 'iwl-3945-rs'

Rune

Rune,
the problems started after a recent upgrade, so I think it may happen to others...

See my daemon.log from this morning bootup... I filtered out the NetworkManager entries.
This is a successful connection. Also I'm now at near arm distance from my AP antenna... it stays up this way.

I'll try to collect dmesg and daemon logs of a disconnection (in my case I can connect but get a 5mins max up time - then it disconnects... a couple of clicks and it is connected again and so on).

Truxpin

Hi,

I have the same problem as Truxpin when testing from the release candidate ISO. If I try to connect with the laptop sitting very close from the AP I can not connect to a WPA2 Personal network. If I move the laptop a couple of meters way from it, it starts working flawlessly.

Interesting enough. After the first successful connection, if I move the laptop close to the AP again I can still connect without problems. I only have problems with the first connection.

Hi all,
has anybody pursued this bug further?
I still have shaky wireless connection with Network Manager is the network signal has a medium stregth (when its below 70% it disconnects happily and I have to click it back!)

Thanks, Truxpin

Hi,
I can't connect at all with Network Manager on my home wifi protected by
personal WPA2.

I have similar issue using intrepid with last kernel 22.6.27-10-generic iwl3945
filename: /lib/modules/2.6.27-10-generic/kernel/drivers/net/wireless/iwlwifi/iwl3945.ko
license: GPL
author: Copyright(c) 2003-2008 Intel Corporation
version: 1.2.26ks
description: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux
srcversion: B8570227953474842B9209D
alias: pci:v00008086d00004227sv*sd*bc*sc*i*
alias: pci:v00008086d00004222sv*sd*bc*sc*i*
alias: pci:v00008086d00004227sv*sd00001014bc*sc*i*
alias: pci:v00008086d00004222sv*sd00001044bc*sc*i*
alias: pci:v00008086d00004222sv*sd00001034bc*sc*i*
alias: pci:v00008086d00004222sv*sd00001005bc*sc*i*
depends: mac80211,led-class,cfg80211,rfkill
vermagic: 2.6.27-10-generic SMP mod_unload modversions 586
parm: antenna:select antenna (1=Main, 2=Aux, default 0 [both]) (int)
parm: disable:manually disable the radio (default 0 [radio on]) (int)
parm: hwcrypto:using hardware crypto engine (default 0 [software])
 (int)
parm: debug:debug output mask (int)
parm: disable_hw_scan:disable hardware scanning (default 0) (int)
parm: queues_num:number of hw queues. (int)
parm: qos_enable:enable all QoS functionality (int)

But if I disable wireless at nm-applet then reload (remove | add) the module iwl3945 then enable wireless and connect to the wireless ,it works ok and no more dmesg of the iwl3945.

Reloading iwl3945 module doesn't help for me.

Geek87,

did wireless work for you using 2.6.24-19-generic (in Hardy) ?

Wireless was working fine on my computer until 2.6.24-19-generic, after this
(in both Hardy and Intrepid) it has been completely broken. It does however
work fine with an Zydas USB device.

Davidiam,

can you please check if you have the same iwl hardware as me ?

modinfo iwl3945:
filename:
/lib/modules/2.6.27-10-generic/kernel/drivers/net/wireless/iwlwifi/iwl3945.ko
license: GPL
author: Copyright(c) 2003-2008 Intel Corporation
version: 1.2.26ks
description: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver
for Linux
srcversion: B8570227953474842B9209D
alias: pci:v00008086d00004227sv*sd*bc*sc*i*
alias: pci:v00008086d00004222sv*sd*bc*sc*i*
alias: pci:v00008086d00004227sv*sd00001014bc*sc*i*
alias: pci:v00008086d00004222sv*sd00001044bc*sc*i*
alias: pci:v00008086d00004222sv*sd00001034bc*sc*i*
alias: pci:v00008086d00004222sv*sd00001005bc*sc*i*
depends: mac80211,led-class,cfg80211,rfkill
vermagic: 2.6.27-10-generic SMP mod_unload modversions 586
parm: antenna:select antenna (1=Main, 2=Aux, default 0 [both])
(int)
parm: disable:manually disable the radio (default 0 [radio on])
(int)
parm: hwcrypto:using hardware crypto engine (default 0 [software])
 (int)
parm: debug:debug output mask (int)
parm: disable_hw_scan:disable hardware scanning (default 0) (int)
parm: queues_num:number of hw queues. (int)
parm: qos_enable:enable all QoS functionality (int)

lspci -vv (extract):

03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan]
Network Connection (rev 02)
    Subsystem: Intel Corporation Device 1011
    Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx+
    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
    Latency: 0, Cache Line Size: 64 bytes
    Interrupt: pin A routed to IRQ 220
    Region 0: Memory at d2000000 (32-bit, non-prefetchable) [size=4K]
    Capabilities: [c8] Power Management version 2
        Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
PME(D0+,D1-,D2-,D3hot+,D3cold-)
        Status: D0 PME-Enable- DSel=0 DScale=0 PME-
    Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0
Enable+
        Address: 00000000fee0300c Data: 414a
    Capabilities: [e0] Express (v1) Legacy Endpoint, MSI 00
        DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1
unlimited
            ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset-
        DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
Unsupported-
            RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
            MaxPayload 128 bytes, MaxReadReq 128 bytes
        DevSta: CorrErr+ UncorrErr+ FatalErr- UnsuppReq+ AuxPwr-
TransPend-
        LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0
<128ns, L1 <64us
            ClockPM+ Suprise- LLActRep- BwNot-
        LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- Retrain-
Co...

I have the problem since Hardy. It's normal before that the driver
wasn't iwl3945 but ipw3945.

Le samedi 06 décembre 2008 à 19:12 +0000, Rune Evjen a écrit :
> Reloading iwl3945 module doesn't help for me.
>
> Geek87,
>
> did wireless work for you using 2.6.24-19-generic (in Hardy) ?
>
> Wireless was working fine on my computer until 2.6.24-19-generic, after this
> (in both Hardy and Intrepid) it has been completely broken. It does however
> work fine with an Zydas USB device.
>
> Davidiam,
>
> can you please check if you have the same iwl hardware as me ?
>
> modinfo iwl3945:
> filename:
> /lib/modules/2.6.27-10-generic/kernel/drivers/net/wireless/iwlwifi/iwl3945.ko
> license: GPL
> author: Copyright(c) 2003-2008 Intel Corporation
> version: 1.2.26ks
> description: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver
> for Linux
> srcversion: B8570227953474842B9209D
> alias: pci:v00008086d00004227sv*sd*bc*sc*i*
> alias: pci:v00008086d00004222sv*sd*bc*sc*i*
> alias: pci:v00008086d00004227sv*sd00001014bc*sc*i*
> alias: pci:v00008086d00004222sv*sd00001044bc*sc*i*
> alias: pci:v00008086d00004222sv*sd00001034bc*sc*i*
> alias: pci:v00008086d00004222sv*sd00001005bc*sc*i*
> depends: mac80211,led-class,cfg80211,rfkill
> vermagic: 2.6.27-10-generic SMP mod_unload modversions 586
> parm: antenna:select antenna (1=Main, 2=Aux, default 0 [both])
> (int)
> parm: disable:manually disable the radio (default 0 [radio on])
> (int)
> parm: hwcrypto:using hardware crypto engine (default 0 [software])
> (int)
> parm: debug:debug output mask (int)
> parm: disable_hw_scan:disable hardware scanning (default 0) (int)
> parm: queues_num:number of hw queues. (int)
> parm: qos_enable:enable all QoS functionality (int)
>
>
> lspci -vv (extract):
>
> 03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan]
> Network Connection (rev 02)
> Subsystem: Intel Corporation Device 1011
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR+ FastB2B- DisINTx+
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
> <MAbort- >SERR- <PERR- INTx-
> Latency: 0, Cache Line Size: 64 bytes
> Interrupt: pin A routed to IRQ 220
> Region 0: Memory at d2000000 (32-bit, non-prefetchable) [size=4K]
> Capabilities: [c8] Power Management version 2
> Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
> PME(D0+,D1-,D2-,D3hot+,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0
> Enable+
> Address: 00000000fee0300c Data: 414a
> Capabilities: [e0] Express (v1) Legacy Endpoint, MSI 00
> DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1
> unlimited
> ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset-
> DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
> Unsupported-
> RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
> MaxPayload 128 bytes, MaxReadReq 128...

Same as yours!

0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG
[Golan] Network Connection (rev 02)
 Subsystem: Intel Corporation Device 1020
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 64 bytes
 Interrupt: pin A routed to IRQ 217
 Region 0: Memory at fe8ff000 (32-bit, non-prefetchable) [size=4K]
 Capabilities: <access denied>
 Kernel driver in use: iwl3945
 Kernel modules: iwl3945

 modinfo iwl3945
filename: /lib/modules/2.6.27-10-generic/kernel/drivers/net/wireless/iwlwifi/iwl3945.ko
license: GPL
author: Copyright(c) 2003-2008 Intel Corporation
version: 1.2.26ks
description: Intel(R) PRO/Wireless 3945ABG/BG Network Connection
driver for Linux
srcversion: B8570227953474842B9209D
alias: pci:v00008086d00004227sv*sd*bc*sc*i*
alias: pci:v00008086d00004222sv*sd*bc*sc*i*
alias: pci:v00008086d00004227sv*sd00001014bc*sc*i*
alias: pci:v00008086d00004222sv*sd00001044bc*sc*i*
alias: pci:v00008086d00004222sv*sd00001034bc*sc*i*
alias: pci:v00008086d00004222sv*sd00001005bc*sc*i*
depends: mac80211,led-class,cfg80211,rfkill
vermagic: 2.6.27-10-generic SMP mod_unload modversions 586
parm: antenna:select antenna (1=Main, 2=Aux, default 0 [both])
(int)
parm: disable:manually disable the radio (default 0 [radio
on]) (int)
parm: hwcrypto:using hardware crypto engine (default 0
[software])
 (int)
parm: debug:debug output mask (int)
parm: disable_hw_scan:disable hardware scanning (default 0)
(int)
parm: queues_num:number of hw queues. (int)
parm: qos_enable:enable all QoS functionality (int)

El sáb, 06-12-2008 a las 19:12 +0000, Rune Evjen escribió:

> Reloading iwl3945 module doesn't help for me.
>
> Geek87,
>
> did wireless work for you using 2.6.24-19-generic (in Hardy) ?
>
> Wireless was working fine on my computer until 2.6.24-19-generic, after this
> (in both Hardy and Intrepid) it has been completely broken. It does however
> work fine with an Zydas USB device.
>
> Davidiam,
>
> can you please check if you have the same iwl hardware as me ?
>
> modinfo iwl3945:
> filename:
> /lib/modules/2.6.27-10-generic/kernel/drivers/net/wireless/iwlwifi/iwl3945.ko
> license: GPL
> author: Copyright(c) 2003-2008 Intel Corporation
> version: 1.2.26ks
> description: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver
> for Linux
> srcversion: B8570227953474842B9209D
> alias: pci:v00008086d00004227sv*sd*bc*sc*i*
> alias: pci:v00008086d00004222sv*sd*bc*sc*i*
> alias: pci:v00008086d00004227sv*sd00001014bc*sc*i*
> alias: pci:v00008086d00004222sv*sd00001044bc*sc*i*
> alias: pci:v00008086d00004222sv*sd00001034bc*sc*i*
> alias: pci:v00008086d00004222sv*sd00001005bc*sc*i*
> depends: mac80211,led-class,cfg80211,rfkill
> vermagic: 2.6.27-10-generic SMP mod_unload modversions 586
> parm: an...

Hi all,

I run Intrepid with 2.6.27-9-generic kernel-image and have also trouble with iwl3945.
I do not use network-manager so I try to connect to my home-wlan by wpa_supplicant and /etc/network/interfaces fileconfigs.
But I think that makes nothing, because even when loading iwl3945 i see "wlan0: link is not ready" in /var/log/messages...

------ snip -------
konlux@amilo:~$ sudo modprobe -v -i iwl3945
insmod /lib/modules/2.6.27-9-generic/kernel/net/wireless/cfg80211.ko
insmod /lib/modules/2.6.27-9-generic/kernel/drivers/leds/led-class.ko
insmod /lib/modules/2.6.27-9-generic/kernel/net/mac80211/mac80211.ko
insmod /lib/modules/2.6.27-9-generic/kernel/net/rfkill/rfkill.ko
insmod /lib/modules/2.6.27-9-generic/kernel/drivers/net/wireless/iwlwifi/iwl3945.ko
------ snip ------
(same time on a other shell...)
------ snip ------
konlux@amilo:~$ tail -f /var/log/messages
Dec 13 15:34:16 amilo kernel: [ 9601.364608] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network
Connection driver for Linux, 1.2.26ks
Dec 13 15:34:16 amilo kernel: [ 9601.364619] iwl3945: Copyright(c) 2003-2008 Intel Corporation
Dec 13 15:34:16 amilo kernel: [ 9601.364696] iwl3945 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Dec 13 15:34:16 amilo kernel: [ 9601.364740] iwl3945: Detected Intel Wireless WiFi Link 3945ABG
Dec 13 15:34:16 amilo kernel: [ 9601.406447] iwl3945: Tunable channels: 13 802.11bg, 23 802.11a channels
Dec 13 15:34:16 amilo kernel: [ 9601.408436] iwl3945 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Dec 13 15:34:16 amilo kernel: [ 9601.409892] firmware: requesting iwlwifi-3945-1.ucode
Dec 13 15:34:16 amilo kernel: [ 9601.462597] Registered led device: iwl-phy0:radio
Dec 13 15:34:16 amilo kernel: [ 9601.462683] Registered led device: iwl-phy0:assoc
Dec 13 15:34:16 amilo kernel: [ 9601.462721] Registered led device: iwl-phy0:RX
Dec 13 15:34:16 amilo kernel: [ 9601.462757] Registered led device: iwl-phy0:TX
Dec 13 15:34:16 amilo kernel: [ 9601.470626] ADDRCONF(NETDEV_UP): wlan0: link is not ready
------ snip -------

So I suspect that I have no chance of getting a functioning wlan connection while the "wlan0: link is not ready" error occurs ;-)

Is there a fix or maybe a workaround for this severe problem???

thanks in advance

For those still having issues, care to try installing the linux-backports-modules-intrepid package to see if it helps. It contains and updated compat-wireless stack. Please let us know your results. Thanks.

https://bugs.launchpad.net/ubuntu/+source/linux-backports-modules-2.6.27/+bug/294667/

That might be not that easy...

Anyway, I tried 2.6.28-3 from jaunty -which I think still has an old version of wireless-compat, as I only get mac80211 loaded and not those lbm modules I saw in backports-, and although it associates very quick, I get 20 / 30% package loss to my router when connected to my home wifi via WPA / TKIP (as in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/271463 or http://intellinuxwireless.org/bugzilla/show_bug.cgi?id=1495 ).

Tired of not being able to work with my laptop I just switched to Fedora 10, whose 2.6.27 kernels from koji.fedoraproject.org work perfectly (at least the wifi, I'm getting some problems as in https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/67126 ) . Right now I'm on the latest 2.6.27.9-157.fc10.x86_64. I tried installing kernel sources from their RPM, but it wasn't trivial (as in alien kernel-source*.rpm) and I just stopped trying. Just for the record.

I have installed linux-backports-modules-intrepid on my (pretty base install) of Kubuntu intrepid which has resolved the issue of connecting to WPA secured wireless networks with network manager and kernel 2.6.27-9-generic.

Thanks Leann!

Leann,

Using kernel 2.6.27-7-generic I am affected by https://bugs.launchpad.net/bugs/294667 when installing the backport modules, so I am unable with this kernel and backport module version.

Using kernel 2.6.27-9-generic the backport modules loads fine, but I cannot associate with my AP as described in comment 1 and onwards of this bug report (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264881/comments/1).

I have done some more testing on my laptop, and made the following observations:
- I am unable to associate with my AP using the Intrepid Live CD
- iwlist wlan0 scanning never lists my AP (but does list others, using both WEP and WPA encryprtion as well as no encrpytion)
- A manual setup using wpasupplicant and /etc/network interfaces for key setup is not successfull
- Using my AP, I am also not able to associate using no encryption.

With my USB Zydas device my computer connects fine using all 2.6.26 and .27 kernels, but I did notice that after installing linux-backport-modules on 2.6.27-9 I was not able connect with the Zydas device. After removing backport-modules and rebooting I could connect with the Zydas device but not the integrated iwl3945 chipset.

Rune

When testing with the Jantu 2.6.28 kernel, I am not able to connect to my AP with my iwl3945 device as well as the Zydas USB device. I tested with kernel https://edge.launchpad.net/ubuntu/jaunty/i386/linux-image-2.6.28-3-generic/2.6.28-3.4

My wireless network is not listed in n-m under any of the adapters. After choosing create new wireless network, I am not able to associate using both wireless adapters. Attached is excerpts for both network cards.

When testing with another unencrypted AP, I can associate using the Zydas device but not the iwl3945.

Hi,

I installed linux-backports-modules-intrepid but same behavior: wlan0 do not bekomes ready.

---- snip ----
konlux@amilo:~$ sudo dpkg-query -l linux-backports-modules-intrepid
Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten
| Status=Nicht/Installiert/Config/U=Entpackt/Fehlgeschl. Konfiguration/
         Halb installiert/Trigger erWartet/Trigger anhängig
|/ Fehler?=(kein)/Halten/R=Neuinst notw/X=beide (Status, Fehler: GROSS=schlecht)
||/ Name Version Beschreibung
+++-================================================-================================================-================================================================================================================
ii linux-backports-modules-intrepid 2.6.27.9.13 Generic Linux backported drivers.
konlux@amilo:~$ sudo rmmod iwl3945
konlux@amilo:~$ lsmod | grep iwl
konlux@amilo:~$ sudo modprobe -v -i iwl3945
insmod /lib/modules/2.6.27-9-generic/updates/iwl3945.ko
konlux@amilo:~$ lsmod |grep iwl3945
iwl3945 95480 0
rfkill 17176 2 iwl3945
lbm_cw_mac80211 210728 1 iwl3945
led_class 12164 1 iwl3945
lbm_cw_cfg80211 39696 2 iwl3945,lbm_cw_mac80211
---- snip ----

tail in /var/log/messages

---- snip ---
Dec 18 15:07:58 amilo kernel: [ 1645.214358] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks
Dec 18 15:07:58 amilo kernel: [ 1645.214367] iwl3945: Copyright(c) 2003-2008 Intel Corporation
Dec 18 15:07:58 amilo kernel: [ 1645.216878] iwl3945 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Dec 18 15:07:58 amilo kernel: [ 1645.216922] iwl3945: Detected Intel Wireless WiFi Link 3945ABG
Dec 18 15:07:58 amilo kernel: [ 1645.262347] iwl3945: Tunable channels: 13 802.11bg, 23 802.11a channels
Dec 18 15:07:58 amilo kernel: [ 1645.282008] iwl3945 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Dec 18 15:07:58 amilo kernel: [ 1645.283528] firmware: requesting iwlwifi-3945-1-lbm.ucode
Dec 18 15:07:58 amilo kernel: [ 1645.338607] Registered led device: iwl-phy3:radio
Dec 18 15:07:58 amilo kernel: [ 1645.338693] Registered led device: iwl-phy3:assoc
Dec 18 15:07:58 amilo kernel: [ 1645.338726] Registered led device: iwl-phy3:RX
Dec 18 15:07:58 amilo kernel: [ 1645.338759] Registered led device: iwl-phy3:TX
Dec 18 15:07:58 amilo kernel: [ 1645.349547] ADDRCONF(NETDEV_UP): wlan0: link is not read
---- snip ----

Leann,

Installing kernel 2.6.27-11-generic and linux-backport-modules for -11 from proposed does not solve my association problem.

Regards

Rune

@Rune

It worked for me with -9-generic, but when I updated to -11 it broke again.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

@Alan

For me it has not worked since 2.6.24-19-generic, including 2.6.27-9, with and without backport-modules, so I suspect that I am experiencing a different bug than you.

Rune

This bug is now solved for me !

I am using a Linksys WRT54Gv4 with DD-WRT v23 SP2 firmware, and have been experiencing problems with assoicating with this AP as described in the first comment in this bug report.

But after resetting the NVRAM of my router, I am able to associate with my AP. This has been tested with no encryption as well as WPA2.

So, for me resetting the NVRAM of the AP made it possible to associate with kernels >2.6.24.19.

Rune

Thanks for the update Rune. Since you are the original bug reporter, I'm going to go ahead and close this report. For anyone else still experiencing issues, please open a new bug report - https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks.