[Gutsy] Intel 4965AGN wireless connection dies

Bug #149214 reported by Kyle Jones on 2007-10-05
24
Affects Status Importance Assigned to Milestone
Linux
In Progress
Unknown
linux (Ubuntu)
Undecided
Unassigned
Nominated for Gutsy by Kyle Jones
linux-source-2.6.22 (Ubuntu)
Undecided
Unassigned
Nominated for Gutsy by Kyle Jones
linux-ubuntu-modules-2.6.22 (Ubuntu)
Medium
Unassigned
Nominated for Gutsy by Kyle Jones

Bug Description

Running Gutsy, everything as up-to-date as they can be from repos. Intel 4965AGN chipset wireless card in Dell E1505 (Not ubuntu native 1505).

After install, the OS identifies the chipset fine and uses the iwlwifi and iwl4965 driver. I can connect to the AP just fine in G mode, but after a seemingly random interval, the connection dies. Gnome networking manager shows everything is still working fine and the connection is still up, but I lose complete connectivity. When I CAN connect, speeds are pretty slow downloading files, I noticed this when doing an apt-get update and upgrade. Browsing seems fine, but that isn't a good indicator of speeds. This happens on multiple access points of multiple brands.

The iwlwifi driver is out of date in the current build of Gutsy, is there any possibility of going to the latest version of 1.1.17?

Kyle Jones (mutiny32) on 2007-10-05
description: updated

This issue is evident in both 32-bit and AMD-64-bit versions of the OS, as I had originally thought it was a bug in the 64-bit version so I installed the 32-bit version with the same results.

Kyle Jones (mutiny32) wrote :

I guess this should affect linux-ubuntu-modules-2.6.22

Kyle Jones (mutiny32) wrote :
Download full text (4.3 KiB)

Kernel log wit errors in it while it is hapening. I'm seeing this as something bad:

Oct 4 11:58:49 Lappertop kernel: [ 796.356000] iwl4965: Microcode SW error detected. Restarting 0x82000000.
Oct 4 11:58:50 Lappertop kernel: [ 798.356000] wlan0: failed to restore operationalchannel after scan
Oct 4 11:58:50 Lappertop kernel: [ 798.356000] iwl4965: No space for Tx
Oct 4 11:58:50 Lappertop kernel: [ 798.356000] iwl4965: Error sending REPLY_ADD_STA: iwl_enqueue_hcmd failed: -28
Oct 4 11:58:50 Lappertop kernel: [ 798.356000] iwl4965: No space for Tx
Oct 4 11:58:50 Lappertop kernel: [ 798.356000] iwl4965: Error sending REPLY_TX_LINK_QUALITY_CMD: iwl_enqueue_hcmd failed: -28
Oct 4 11:58:50 Lappertop kernel: [ 798.356000] iwl4965: No space for Tx
Oct 4 11:58:50 Lappertop kernel: [ 798.356000] iwl4965: Error sending REPLY_TX_PWR_TABLE_CMD: iwl_enqueue_hcmd failed: -28
Oct 4 11:58:57 Lappertop kernel: [ 804.932000] iwl4965: REPLY_ADD_STA failed
Oct 4 11:59:45 Lappertop kernel: [ 852.840000] wlan0: RX deauthentication from 00:12:17:ae:73:fe (reason=7)
Oct 4 11:59:45 Lappertop kernel: [ 852.840000] wlan0: deauthenticated
Oct 4 11:59:46 Lappertop kernel: [ 853.840000] wlan0: authenticate with AP 00:12:17:ae:73:fe
Oct 4 11:59:46 Lappertop kernel: [ 853.840000] wlan0: RX authentication from 00:12:17:ae:73:fe (alg=0 transaction=2 status=0)
Oct 4 11:59:46 Lappertop kernel: [ 853.840000] wlan0: authenticated
Oct 4 11:59:46 Lappertop kernel: [ 853.840000] wlan0: associate with AP 00:12:17:ae:73:fe
Oct 4 11:59:46 Lappertop kernel: [ 853.844000] wlan0: RX ReassocResp from 00:12:17:ae:73:fe (capab=0x11 status=0 aid=2)
Oct 4 11:59:46 Lappertop kernel: [ 853.844000] wlan0: associated
Oct 4 11:59:46 Lappertop kernel: [ 853.844000] wlan0: CTS protection enabled (BSSID=00:12:17:ae:73:fe)
Oct 4 11:59:46 Lappertop kernel: [ 853.844000] iwl4965: TX Power requested while scanning!
Oct 4 11:59:46 Lappertop kernel: [ 853.844000] iwl4965: Error setting Tx power (-11).
Oct 4 11:59:46 Lappertop kernel: [ 853.844000] iwl4965: TX Power requested while scanning!
Oct 4 11:59:46 Lappertop kernel: [ 853.844000] iwl4965: Error setting Tx power (-11).
Oct 4 11:59:51 Lappertop kernel: [ 858.852000] iwl4965: Microcode SW error detected. Restarting 0x82000000.
Oct 4 11:59:53 Lappertop kernel: [ 860.852000] wlan0: failed to restore operationalchannel after scan
Oct 4 11:59:53 Lappertop kernel: [ 860.852000] iwl4965: No space for Tx
Oct 4 11:59:53 Lappertop kernel: [ 860.852000] iwl4965: Error sending REPLY_ADD_STA: iwl_enqueue_hcmd failed: -28
Oct 4 11:59:53 Lappertop kernel: [ 860.852000] iwl4965: No space for Tx
Oct 4 11:59:53 Lappertop kernel: [ 860.852000] iwl4965: Error sending REPLY_TX_LINK_QUALITY_CMD: iwl_enqueue_hcmd failed: -28
Oct 4 11:59:53 Lappertop kernel: [ 860.852000] iwl4965: No space for Tx
Oct 4 11:59:53 Lappertop kernel: [ 860.852000] iwl4965: Error sending REPLY_TX_PWR_TABLE_CMD: iwl_enqueue_hcmd failed: -28
Oct 4 11:59:59 Lappertop kernel: [ 867.444000] iwl4965: REPLY_ADD_STA failed
Oct 4 12:00:47 Lappertop kernel: [ 914.704000] wlan0: RX deauthentication from 00:12:17:ae:73:fe (reason=7)
Oct 4 12:00...

Read more...

Kyle Jones (mutiny32) on 2007-10-06
Changed in linux-source-2.6.22:
assignee: nobody → ubuntu-kernel-network
Changed in linux-ubuntu-modules-2.6.22:
assignee: nobody → ubuntu-kernel-network
Kyle Jones (mutiny32) wrote :

Is anything else needed?

Changed in linux-source-2.6.22:
assignee: ubuntu-kernel-network → nobody
Changed in linux-ubuntu-modules-2.6.22:
assignee: ubuntu-kernel-network → nobody
Kyle Jones (mutiny32) wrote :

Linux Lappertop 2.6.22-13-generic #1 SMP Thu Oct 4 17:18:44 GMT 2007 i686 GNU/Linux

Changed in linux-source-2.6.22:
assignee: nobody → mutiny32
assignee: mutiny32 → nobody
Kyle Jones (mutiny32) wrote :
Kyle Jones (mutiny32) wrote :
Kyle Jones (mutiny32) wrote :
Kyle Jones (mutiny32) wrote :
VousDeux (launchpad-blahdot) wrote :

Greetings:

I just wanted to add my two cents worth of 'me too' to this thread with the hopes that will help escalate the issue.

I have the same wifi interface (Intel 4964AGN) and basically the same problem, but my notebook is a MicroStar MS-1719.

My problem seems to be that sometimes the wifi link will work just fine for quite a long time, but eventually it will cease to function and I cannot seem to get it working again without rebooting my computer. Other times, after a fresh boot, it will work only for a short time before ceasing to function again. Last night, for example, I rebooted about half a dozen times within just a couple of hours because the wifi kept dropping off after a very short time. I also tried adjusting the xmit power on my wireless router, but it didn't seem to make any difference, so I put it back to the setting that has worked reliably for other wireless devices in my home for the past couple of years since I installed DD-WRT on my Linksys router.

In addition to the details requested for bug submission under the Kernel Team Bug Policies, I have also attached excerpts from the syslog that have relevance to the wlan0/wifi connectivity. This logs shows where the machine was booted at 01:48 this morning and did establish a wifi connection, but shortly after began having difficulties. Toward the end, it shows where I tried to force a manual reconnect, but was unsuccessful and then rebooted again.

Thank you,

Jerry

Re Alvarez (re-alvz) wrote :

+1 here with Acer 5920...same wireless card...

the connection would work fine but eventually it will die...(it may work for days before disconnecting)...my XP box on the other hand remains connected..

i am using wireless in G mode with a minimum of 85% signal...

gnome would show me connected with 100% connection strength but i wouldnt even be able to ping my default gateway.

balmy_fool (balmy-fool) wrote :

Same here with a 4965AGN on an IBM R61. The connection seems to randomly die, and I usually can't reconnect until I remove the module and reload it.

DMESG:

[ 232.870279] iwl4965: TX Power requested while scanning!
[ 232.870286] iwl4965: Error setting Tx power (-11).
[ 232.871635] iwl4965: TX Power requested while scanning!
[ 232.871641] iwl4965: Error setting Tx power (-11).
[ 233.026727] wlan0: RX WEP frame with unknown keyidx 2 (A1=33:33:00:00:00:16 A2=00:17:9a:9a:b6:31 A3=00:0e:35:35:9a:22)
[ 233.074374] wlan0: RX WEP frame with unknown keyidx 2 (A1=33:33:ff:35:9a:22 A2=00:17:9a:9a:b6:31 A3=00:0e:35:35:9a:22)
[ 233.172414] wlan0: RX WEP frame with unknown keyidx 2 (A1=33:33:00:00:00:02 A2=00:17:9a:9a:b6:31 A3=00:0e:35:35:9a:22)
[ 233.417351] iwl4965: Microcode SW error detected. Restarting 0x82000000.
[ 236.152880] wlan0: disassociate(reason=3)
[ 237.378587] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 248.357032] ADDRCONF(NETDEV_UP): wlan0: link is not ready

VousDeux (launchpad-blahdot) wrote :

Hello again:

As a follow-up, I wanted to note that I tried the suggestion for removing the module and reloading it. Doing so does allow me to reconnect without having to reboot (thank you), but I still keep having to do it repeatedly. Sometimes it happens several times in an hour, other times it happens after several hours.

Thanks,

Jerry

I can confirm this issue.
My Hardware: Asus F3SV with Intel 4965AGN

My existing connection after the boot process dies after a short time (approx. 2-10sec)

The following excerpt from the kernel-log file:

kernel: [ 128.772000] iwl4965: Microcode SW error detected. Restarting 0x2000000.
kernel: [ 128.772000] iwl4965: Error setting new configuration (-5).

A command (sudo rmmod iwl4965 && sudo modprobe iwl4965) was only a temporary solution, the problem occurs again.

thx

elex

tuxo (beat-fasel) wrote :

This bug might be a duplicate of bug #144621 : "iwl4965 drops out from time to time (Santa Rosa)".

Kris Lowet (krislowet) wrote :

Count me in... One moment I have connection, the other time it get lost on my notebook (HP Pavilion dv9540eb).

02:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61)
06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)

Ubuntu 7.10 with kernel 2.6.22-14-generic.

Vu Ngoc San (san-vu-ngoc) wrote :

In case it may help, on my laptop dell d630 (kubuntu gutsy) with

0c:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61)

then

1. at work I have a non encrypted wifi network, which works without problem

2. there is also a encrypted network, requiring WPA enterprise/ TTLS/PAP password. Each time I try to connect, the network is detected but then the drivers fails immediately with

[ 564.416000] wlan0: authenticated
[ 564.416000] wlan0: associate with AP ***hiden**
[ 564.416000] wlan0: RX ReassocResp from ***hidden** (capab=0x431 status=0 aid=239)
[ 564.416000] wlan0: associated
[ 564.424000] iwl4965: TX Power requested while scanning!
[ 564.424000] iwl4965: Error setting Tx power (-11).
[ 564.424000] iwl4965: TX Power requested while scanning!
[ 564.424000] iwl4965: Error setting Tx power (-11).
[ 569.428000] iwl4965: Microcode SW error detected. Restarting 0x82000000.
[ 571.428000] wlan0: failed to restore operationalchannel after scan
[ 571.428000] iwl4965: No space for Tx
[ 571.428000] iwl4965: Error sending REPLY_ADD_STA: iwl_enqueue_hcmd failed: -28
[ 571.428000] iwl4965: No space for Tx
[ 571.428000] iwl4965: Error sending REPLY_TX_LINK_QUALITY_CMD: iwl_enqueue_hcmd failed: -28
[ 571.428000] iwl4965: No space for Tx
[ 571.428000] iwl4965: Error sending REPLY_TX_PWR_TABLE_CMD: iwl_enqueue_hcmd failed: -28
[ 578.660000] iwl4965: REPLY_ADD_STA failed
[ 594.340000] wlan0: disassociate(reason=3)

Günter Haus (mcframe) wrote :
Download full text (23.5 KiB)

Same here with a Intel 4965AGN within a HP2710p notebook on gutsy version 2.6.22-14-generic. No chance to bring it to work with WPA encryption.

kernel: [ 295.428000] wlan0: Initial auth_alg=0
kernel: [ 295.428000] wlan0: authenticate with AP 00:1c:4a:d2:11:39
kernel: [ 295.428000] wlan0: RX authentication from 00:1c:4a:d2:11:39 (alg=0 transaction=2 status=0)
kernel: [ 295.428000] wlan0: authenticated
kernel: [ 295.428000] wlan0: associate with AP 00:1c:4a:d2:11:39
kernel: [ 295.432000] wlan0: RX AssocResp from 00:1c:4a:d2:11:39 (capab=0x411 status=0 aid=1)
kernel: [ 295.432000] wlan0: associated
kernel: [ 295.432000] wlan0: WMM queue=2 aci=0 acm=0 aifs=3 cWmin=15 cWmax=1023 burst=0
kernel: [ 295.440000] wlan0: WMM queue=3 aci=1 acm=0 aifs=7 cWmin=15 cWmax=1023 burst=0
kernel: [ 295.440000] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
kernel: [ 295.440000] wlan0: WMM queue=1 aci=2 acm=0 aifs=2 cWmin=7 cWmax=15 burst=30
kernel: [ 295.440000] wlan0: WMM queue=0 aci=3 acm=0 aifs=2 cWmin=3 cWmax=7 burst=15
kernel: [ 299.436000] wlan0: RX deauthentication from 00:1c:4a:d2:11:39 (reason=1)
kernel: [ 299.436000] wlan0: deauthenticated
kernel: [ 300.436000] wlan0: authenticate with AP 00:1c:4a:d2:11:39
kernel: [ 300.436000] wlan0: RX authentication from 00:1c:4a:d2:11:39 (alg=0 transaction=2 status=0)
kernel: [ 300.436000] wlan0: authenticated
kernel: [ 300.436000] wlan0: associate with AP 00:1c:4a:d2:11:39
kernel: [ 300.440000] wlan0: RX ReassocResp from 00:1c:4a:d2:11:39 (capab=0x411 status=0 aid=1)
kernel: [ 300.440000] wlan0: associated
kernel: [ 300.440000] iwl4965: TX Power requested while scanning!
kernel: [ 300.440000] iwl4965: Error setting Tx power (-11).
kernel: [ 300.444000] iwl4965: TX Power requested while scanning!
kernel: [ 300.444000] iwl4965: Error setting Tx power (-11).
kernel: [ 304.436000] wlan0: RX deauthentication from 00:1c:4a:d2:11:39 (reason=1)
kernel: [ 304.436000] wlan0: deauthenticated
kernel: [ 305.436000] wlan0: authenticate with AP 00:1c:4a:d2:11:39
kernel: [ 305.636000] wlan0: authenticate with AP 00:1c:4a:d2:11:39
kernel: [ 305.668000] wlan0: no IPv6 routers present
kernel: [ 305.836000] wlan0: authenticate with AP 00:1c:4a:d2:11:39
kernel: [ 306.036000] wlan0: authentication with AP 00:1c:4a:d2:11:39 timed out
kernel: [ 306.092000] iwl4965: Microcode SW error detected. Restarting 0x82000000.
kernel: [ 306.092000] wlan0: failed to restore operationalchannel after scan
kernel: [ 306.092000] iwl4965: TX Power requested while scanning!
kernel: [ 379.120000] ADDRCONF(NETDEV_UP): eth0: link is not ready
kernel: [ 380.744000] e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
kernel: [ 380.744000] e1000: eth0: e1000_watchdog: 10/100 speed: disabling TSO
kernel: [ 380.748000] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
kernel: [ 383.772000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
kernel: [ 385.952000] wlan0: Initial auth_alg=0
kernel: [ 385.952000] wlan0: authenticate with AP 00:1c:4a:d2:11:39
kernel: [ 385.956000] wlan0: RX authentication from 00:1c:4a:d2:11:39 (alg=0 transaction=2 status=0)
kernel: [ 385.956000] wlan0: authe...

Changed in linux-source-2.6.22:
status: New → Confirmed
Changed in linux-ubuntu-modules-2.6.22:
status: New → Confirmed
camellight (ceminino) wrote :

same problem here on a MSI PR200, disconnects several times per hour, I'm using a wired connection right now :(

At the beginning all was good, then after some times, these blocks started and now the card isn't usable AT ALL!!!
I mean, the wireless interface doesn't associate!

This is my dmesg output:
[ 24.744000] iwl4965: Intel(R) Wireless WiFi Link 4965AGN driver for Linux, 1.1.0
[ 24.744000] iwl4965: Copyright(c) 2003-2007 Intel Corporation
[ 24.744000] iwl4965: Detected Intel Wireless WiFi Link 4965AGN
[ 25.372000] iwl4965: Tunable channels: 13 802.11bg, 19 802.11a channels
[ 25.372000] wmaster0: Selected rate control algorithm 'iwl-4965-rs'
[ 46.320000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 118.156000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 140.904000] ADDRCONF(NETDEV_UP): wlan0: link is not ready

And this is iwconfig:
wlan0 IEEE 802.11g ESSID:"Access Point"
          Mode:Managed Frequency:2.437 GHz Access Point: Not-Associated
          Retry min limit:7 RTS thr:off Fragment thr=2346 B
          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

I only can use a wired connection... I use wicd to control the interface, but I think this shouldn't matter, since using command line doesn't solve!

Henrik Nilsen Omma (henrik) wrote :

This will be retargeted towards the Hardy kernel once it is released. I've tagged this as "hardy-kernel-candidate" so that we make sure to retarget this report once the new release is out. However against the linux-source-2.6.22 package this is being marked as "Won't Fix" as it does not meet the criteria for a stable release update. To learn more about the stable release update process please refer to https://wiki.ubuntu.com/StableReleaseUpdates . Thanks!

Changed in linux-source-2.6.22:
status: Confirmed → Won't Fix
Changed in linux-ubuntu-modules-2.6.22:
importance: Undecided → Medium
status: Confirmed → Won't Fix
Anton Khokhlov (orvind) wrote :

HP 8510p notebook. Same issue. After several hours of working the wireless module dies. Gnome network manager shows the network is still available, but "enter the passphrase" dialog appears. After entering passphrase the connection process hangs.
"iwlist scan" says "resource temporary unavailable"
The problem solves (for the next several hours) if I say
rmmod iwl4965
rmmod iwlwifi_mac80211
rmmod cfg80211
modprobe iwl4965

But it's too annoying to repeat the commands every two hours. And you can't use any program that demands long time internet connection.

Can confirm this, i have the same laptop (hp 8510p) and the same problem, why doesn't the Ubuntu kernel team update the driver? (or at least provide instructions how to do it)

Anton Khokhlov (orvind) wrote :

Yesterday I had found the solution. Ubuntu seems to use old Intel firmware and the issue will be resolved if you perform the following steps:
- Download the last firmware archive from http://www.intellinuxwireless.org/?p=iwlwifi&n=Downloads . The file's name is iwlwifi-4965-ucode-version number.tgz
- Unpack the archive tar xvf iwlwifi-4965-ucode-what version you got.tgz
- Copy iwlwifi-4965.ucode from the unpacked folder into /lib/firmware/your kernel version/iwlwifi-4965.ucode and /lib/firmware/your kernel version/iwlwifi-4965-1.ucode (you should overwrite two files with the same data)

After that you need to reboot or just to say
rmmod iwl4965
modprobe iwl4965
Now on my computer it have been working for the 24 hours continuously without any disconnect. But I can not guarantee it works everywhere.

Anton Khokhlov (orvind) wrote :

Forgot to say sorry for my English.

Damiano Venturin (damko) wrote :

it works for me now. I'm working on a Thinkpad T61.

Thanks Anton!

Dam

not for me,

10:47:00 asus kernel: [ 710.480000] iwl4965: Intel(R) Wireless WiFi Link 4965AGN driver for Linux, 1.1.0
10:47:00 asus kernel: [ 710.480000] iwl4965: Copyright(c) 2003-2007 Intel Corporation
10:47:00 asus kernel: [ 710.480000] ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 17
10:47:00 asus kernel: [ 710.480000] PCI: Setting latency timer of device 0000:03:00.0 to 64
10:47:00 asus kernel: [ 710.480000] iwl4965: Detected Intel Wireless WiFi Link 4965AGN
10:47:00 asus kernel: [ 710.716000] iwl4965: Tunable channels: 13 802.11bg, 19 802.11a channels
10:47:00 asus kernel: [ 710.716000] wmaster0: Selected rate control algorithm 'iwl-4965-rs'
10:47:00 asus kernel: [ 710.760000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
10:47:31 asus kernel: [ 740.804000] iwl4965: Microcode SW error detected. Restarting 0x2000000.

alex@asus:~$ sudo rmmod iwl4965
alex@asus:~$ sudo modprobe iwl4965
alex@asus:~$ modinfo iwl4965
filename: /lib/modules/2.6.22-14-generic/ubuntu/wireless/iwlwifi/iwlwifi/origin/iwl4965.ko
license: GPL
author: Copyright(c) 2003-2007 Intel Corporation
version: 1.1.0
description: Intel(R) Wireless WiFi Link 4965AGN driver for Linux
srcversion: B07647EE168D101F8179F5B
alias: pci:v00008086d00004230sv*sd*bc*sc*i*
alias: pci:v00008086d00004229sv*sd*bc*sc*i*
depends: iwlwifi_mac80211
vermagic: 2.6.22-14-generic SMP mod_unload 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)

Hardy Heron Alpha2 was recently released. It contains an updated version of the kernel. You can download and try the new Hardy Heron Alpha2 release from http://cdimage.ubuntu.com/releases/hardy/alpha-2/ . You should be able to then test the new kernel via the LiveCD. If you can, please verify if this bug still exists or not and report back your results. General information regarding the release can also be found here: http://www.ubuntu.com/testing/hardy/alpha2 . Thanks!

Changed in linux:
status: New → Incomplete
reynaldo (rverdejo) wrote :

revision 62 (from their subversion repo) of the driver works on gutsy using instructions
from rtl-wifi's wiki (http://rtl-wifi.sourceforge.net/wiki/Installing). I Tested this against
2.6.22-14-generic. only some minor tweaking is needed to aid automatic loading of the
otherwise unloaded ieee80211_crypt_[wep|pkip|ccmp]-rtl. I'm unsure whether I will have this
laptop around for trying out hardy's alpha2 but figured out the info deserved a comment.

reynaldo (rverdejo) wrote :

Sorry, Wrong window :/ last comment belongs to #104132, not here. Isn't
there a way to get rid of the comment? (New to launchpad)

agenthex (hexsmith) wrote :

Same problem for me. This is far better since someone pointed out the "sudo rmmod iwl4965 && sudo modprobe iwl4965" fix. I've since made a shell script to make this easier to manage, but it's pretty aggravating to have my connection drop out.

My dmesg:

[ 198.492970] wlan0: associated
[ 198.492977] wlan0: CTS protection enabled (BSSID=00:1b:2b:6a:a4:11)
[ 198.498844] iwl4965: TX Power requested while scanning!
[ 198.498851] iwl4965: Error setting Tx power (-11).
[ 198.500188] iwl4965: TX Power requested while scanning!
[ 198.500194] iwl4965: Error setting Tx power (-11).
[ 200.840893] iwl4965: Microcode SW error detected. Restarting 0x2000000.
[ 208.977140] wlan0: deauthenticate(reason=3)
[ 209.590098] ADDRCONF(NETDEV_UP): wlan0: link is not ready

Per Heldal (heldal) wrote :

Don't expect this to be fixed in Gutsy as components of a release rarely (if at all) are upgraded within a release-cycle. Are any bugs being addressed at all if they're not security-related? That seems to be a problem with Ubuntu. The best fix for wireless problems in 7.10 seems to be to reinstall 7.04 if your hardware works there. There's not much new in 7.10 apart from eye-candy.

Per Heldal <email address hidden> writes:

> Don't expect this to be fixed in Gutsy as components of a release rarely
> (if at all) are upgraded within a release-cycle. Are any bugs being
> addressed at all if they're not security-related? That seems to be a
> problem with Ubuntu. The best fix for wireless problems in 7.10 seems to
> be to reinstall 7.04 if your hardware works there. There's not much new
> in 7.10 apart from eye-candy.

Ahem. I seem to have missed some key information in my report.

This is tagged Gutsy, but the problem was in the *Hardy* kernel; it
seems to have more or less stabilized recently, though, despite no
listed changes to the wireless driver.

        Daniel
--
Daniel Pittman <email address hidden> Phone: 03 9428 6922
1/130-132 Stawell St, Richmond Web: http://www.cyber.com.au
Cybersource: Australia's Leading Linux and Open Source Solutions Company

Hi Daniel,

Just wanted to let you know that the linux-ubuntu-modules package in Hardy updated to iwlwifi version 1.2.0 which might have helped. Thanks!

Denis Walrave (deniswalrave) wrote :

Hi all,

I tried a later version included in kernel 2.6.24-rc8. Behaviour is better but the connection still fails on heavy loads (Like using backuppc on wifi). The connection drops after a while and reloading the module is the only option (rmmod iwl4965; modprobe iwl4965).

When it happens, I have got in dmesg:
[54526.621912] iwl4965: Microcode SW error detected. Restarting 0x2000000.
[54530.136399] iwl4965: Can't stop Rx DMA.

Denis

Changed in linux:
status: Unknown → In Progress

I can confirm Denis Walrave's experience: the same issue happens with the Hardy kernel as the Gutsy kernel.

The only common issues I have noted are:
1. Heavy network load.
2. Occasionally the first failure is accompanied by a note that the EC did not return a write confirmation.

The second message is related to the embedded controller in the Thinkpad T61p I use, but has occurred coincidentally enough times that I suspect there may be some race issue, triggered only under load, that the EC access or an SMI trap causes to run and make a timing constraint (or another bug) in the wireless firmware show up.

muriel (muriel-bowie) wrote :

Same issue here, doesn't seem to be solved in Hardy yet.

Hi All,

It seems this may be a duplicate report of bug 200509 (or vice versa). Care to confirm?

Leann Ogasawara <email address hidden> writes:

> It seems this may be a duplicate report of bug 200509 (or vice versa).
> Care to confirm?

I see the same symptoms as reported in bug 200509; this seems to be a
duplicate to me.

Regards,
        Daniel

Thanks. I'm going to go ahead and mark this as a duplicate of bug 200509. As noted in the last few comments of that report, an updated version of the iwlwifi drivers (version 1.2.25) was recently added to the linux-backports-modules-2.6.24 package. It would be good if those of you here could retest once lbm with the update is published and available: https://edge.launchpad.net/ubuntu/+source/linux-backports-modules-2.6.24 . Thanks.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.