Eeepc 1000HE (rt2860pci) Natty wifi connection isn't staying connected

Bug #757700 reported by Xavier on 2011-04-11
36
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Linux
Fix Released
Medium
linux (Ubuntu)
Medium
Unassigned

Bug Description

Hi !

I'm using Natty Narwhal on my Eeepc 1000HE. The wifi connection works well at login, but after a while (from few seconds to hour) the connection become down. Then up, then down, then up.... Sometimes WPA code is requested.

WORKAROUND: added these line into '/etc/modprobe.d/blacklist.conf' and rebooted.
blacklist rt2800pci
blacklist rt2800lib
blacklist rt2x00usb
blacklist rt2x00pci
blacklist rt2x00lib

Please find below more information :

~$ lspci -nn | grep -i net

01:00.0 Network controller [0280]: Ralink corp. RT2860 [1814:0781]
03:00.0 Ethernet controller [0200]: Atheros Communications AR8121/AR8113/AR8114 Gigabit or Fast Ethernet [1969:1026] (rev b0)

$ lsmod

Module Size Used by
cryptd 19801 0
aes_i586 16956 1
aes_generic 38023 1 aes_i586
binfmt_misc 13213 1
parport_pc 32111 0
ppdev 12849 0
snd_hda_codec_realtek 255820 1
snd_hda_intel 24140 3
snd_hda_codec 90901 2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep 13274 1 snd_hda_codec
snd_pcm 80244 2 snd_hda_intel,snd_hda_codec
rt2860sta 494649 0
arc4 12473 2
i915 450944 2
joydev 17322 0
snd_seq_midi 13132 0
rt2800pci 18159 0
rt2800lib 43824 1 rt2800pci
snd_rawmidi 25269 1 snd_seq_midi
crc_ccitt 12595 2 rt2860sta,rt2800lib
snd_seq_midi_event 14475 1 snd_seq_midi
rt2x00pci 13986 1 rt2800pci
snd_seq 51291 2 snd_seq_midi,snd_seq_midi_event
rt2x00lib 39075 3 rt2800pci,rt2800lib,rt2x00pci
mac80211 257001 3 rt2800lib,rt2x00pci,rt2x00lib
drm_kms_helper 40745 1 i915
snd_timer 28659 2 snd_pcm,snd_seq
snd_seq_device 14110 3 snd_seq_midi,snd_rawmidi,snd_seq
drm 180037 3 i915,drm_kms_helper
uvcvideo 66851 0
cfg80211 156212 2 rt2x00lib,mac80211
psmouse 73312 0
videodev 75143 1 uvcvideo
snd 55295 15 snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
i2c_algo_bit 13184 1 i915
serio_raw 12990 0
soundcore 12600 1 snd
eeepc_laptop 19417 0
eeprom_93cx6 12653 1 rt2800pci
snd_page_alloc 14073 2 snd_hda_intel,snd_pcm
video 18951 1 i915
sparse_keymap 13666 1 eeepc_laptop
lp 13349 0
parport 36746 3 parport_pc,ppdev,lp
atl1e 32576 0

~$ iwconfig

lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11bgn ESSID:"NEUF_8E4C"
          Mode:Managed Frequency:2.462 GHz Access Point: 00:25:15:3B:8E:50
          Bit Rate=18 Mb/s Tx-Power=20 dBm
          Retry long limit:7 RTS thr:off Fragment thr:off
          Power Management:on
          Link Quality=70/70 Signal level=-40 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:5 Invalid misc:37 Missed beacon:0

~$ ifconfig

eth0 Link encap:Ethernet HWaddr 00:24:8c:88:0e:e5
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          Packets reçus:0 erreurs:0 :0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:1
          collisions:0 lg file transmission:1000
          Octets reçus:0 (0.0 B) Octets transmis:0 (0.0 B)
          Interruption:44

lo Link encap:Boucle locale
          inet adr:127.0.0.1 Masque:255.0.0.0
          adr inet6: ::1/128 Scope:Hôte
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          Packets reçus:117 erreurs:0 :0 overruns:0 frame:0
          TX packets:117 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:0
          Octets reçus:8536 (8.5 KB) Octets transmis:8536 (8.5 KB)

wlan0 Link encap:Ethernet HWaddr 00:22:43:6f:25:6b
          inet adr:192.168.1.44 Bcast:192.168.1.255 Masque:255.255.255.0
          adr inet6: fe80::222:43ff:fe6f:256b/64 Scope:Lien
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          Packets reçus:694 erreurs:0 :0 overruns:0 frame:0
          TX packets:828 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:1000
          Octets reçus:279598 (279.5 KB) Octets transmis:132177 (132.1 KB)

~$ nm-tool

NetworkManager Tool

State: connected

- Device: eth0 -----------------------------------------------------------------
  Type: Wired
  Driver: ATL1E
  State: unavailable
  Default: no
  HW Address: 00:24:8C:88:0E:E5

  Capabilities:
    Carrier Detect: yes

  Wired Properties
    Carrier: off

- Device: wlan0 [Auto NEUF_8E4C] ----------------------------------------------
  Type: 802.11 WiFi
  Driver: rt2800pci
  State: connected
  Default: yes
  HW Address: 00:22:43:6F:25:6B

  Capabilities:
    Speed: 9 Mb/s

  Wireless Properties
    WEP Encryption: yes
    WPA Encryption: yes
    WPA2 Encryption: yes

  IPv4 Settings:
    Address: 192.168.1.44
    Prefix: 24 (255.255.255.0)
    Gateway: 192.168.1.1

    DNS: 192.168.1.1

Kind Regards,
Xavier.

Xavier (xavier-monset) wrote :

The problem happens even when the computer is in the same room as the router. Bitrate can vary from 1 to 54 without any apparent reason.

Xavier (xavier-monset) wrote :
Download full text (4.4 KiB)

I've found this on syslog :

Apr 11 19:35:23 petite-chose kernel: [ 611.992042] wlan0: deauthenticated from 00:25:15:3b:8e:50 (Reason: 7)
Apr 11 19:35:23 petite-chose NetworkManager[709]: <info> (wlan0): supplicant connection state: associated -> disconnected
Apr 11 19:35:23 petite-chose NetworkManager[709]: <info> (wlan0): supplicant connection state: disconnected -> scanning
Apr 11 19:35:24 petite-chose NetworkManager[709]: <info> (wlan0): supplicant connection state: scanning -> associating
Apr 11 19:35:24 petite-chose kernel: [ 613.245033] wlan0: authenticate with 00:25:15:3b:8e:50 (try 1)
Apr 11 19:35:24 petite-chose kernel: [ 613.247476] wlan0: authenticated
Apr 11 19:35:24 petite-chose kernel: [ 613.247584] wlan0: associate with 00:25:15:3b:8e:50 (try 1)
Apr 11 19:35:24 petite-chose kernel: [ 613.249931] wlan0: RX AssocResp from 00:25:15:3b:8e:50 (capab=0x411 status=0 aid=1)
Apr 11 19:35:24 petite-chose kernel: [ 613.249949] wlan0: associated
Apr 11 19:35:24 petite-chose NetworkManager[709]: <info> (wlan0): supplicant connection state: associating -> associated
Apr 11 19:35:24 petite-chose NetworkManager[709]: <info> (wlan0): supplicant connection state: associated -> 4-way handshake
Apr 11 19:35:24 petite-chose NetworkManager[709]: <info> (wlan0): supplicant connection state: 4-way handshake -> group handshake
Apr 11 19:35:24 petite-chose NetworkManager[709]: <info> (wlan0): supplicant connection state: group handshake -> completed
Apr 11 19:35:24 petite-chose NetworkManager[709]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'NEUF_8E4C'.
Apr 11 19:35:24 petite-chose NetworkManager[709]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Apr 11 19:35:24 petite-chose NetworkManager[709]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Apr 11 19:35:24 petite-chose NetworkManager[709]: <info> (wlan0): device state change: 5 -> 7 (reason 0)
Apr 11 19:35:24 petite-chose NetworkManager[709]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Apr 11 19:35:24 petite-chose NetworkManager[709]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Apr 11 19:35:24 petite-chose NetworkManager[709]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
Apr 11 19:35:24 petite-chose dhclient: Listening on LPF/wlan0/00:22:43:6f:25:6b
Apr 11 19:35:24 petite-chose dhclient: Sending on LPF/wlan0/00:22:43:6f:25:6b
Apr 11 19:35:24 petite-chose dhclient: DHCPREQUEST of 192.168.1.44 on wlan0 to 255.255.255.255 port 67
Apr 11 19:35:24 petite-chose NetworkManager[709]: <info> (wlan0): DHCPv4 state changed preinit -> reboot
Apr 11 19:35:24 petite-chose NetworkManager[709]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) scheduled...
Apr 11 19:35:24 petite-chose NetworkManager[709]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) started...
Apr 11 19:35:24 petite-chose NetworkManager[709]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Apr 11 19:35:24 petite-chose NetworkManager[709]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) complete....

Read more...

Xavier (xavier-monset) wrote :

and then :

grep 'wpa' syslog

Apr 11 19:35:23 petite-chose wpa_supplicant[867]: CTRL-EVENT-DISCONNECTED bssid=00:25:15:3b:8e:50 reason=0
Apr 11 19:35:24 petite-chose wpa_supplicant[867]: Trying to associate with 00:25:15:3b:8e:50 (SSID='NEUF_8E4C' freq=2462 MHz)
Apr 11 19:35:24 petite-chose wpa_supplicant[867]: Associated with 00:25:15:3b:8e:50
Apr 11 19:35:24 petite-chose wpa_supplicant[867]: WPA: Key negotiation completed with 00:25:15:3b:8e:50 [PTK=CCMP GTK=TKIP]
Apr 11 19:35:24 petite-chose wpa_supplicant[867]: CTRL-EVENT-CONNECTED - Connection to 00:25:15:3b:8e:50 completed (reauth) [id=0 id_str=]
Apr 11 19:36:16 petite-chose wpa_supplicant[867]: CTRL-EVENT-DISCONNECTED bssid=00:25:15:3b:8e:50 reason=0
Apr 11 19:36:17 petite-chose wpa_supplicant[867]: Trying to associate with 00:25:15:3b:8e:50 (SSID='NEUF_8E4C' freq=2462 MHz)
Apr 11 19:36:17 petite-chose wpa_supplicant[867]: Associated with 00:25:15:3b:8e:50

Ricardo Salveti (rsalveti) wrote :

Can you try disabling powersaving?
$ sudo iwconfig wlan0 power off

At least for me it's a lot more stable after disabling it.

Changed in linux (Ubuntu):
status: New → Confirmed
summary: - Eeepc 1000HE Natty wifi connection isn't staying connected
+ Eeepc 1000HE (rt2860pci) Natty wifi connection isn't staying connected
Changed in linux:
importance: Unknown → Medium
status: Unknown → Confirmed

@Xavier:

Your wireless is not working due to a conflict between 2 different wireless drivers that are being loaded at the same time (rt2860sta and rt2800pci)

To solve the issue, please follow the suggestion here:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/673440/comments/8

which is part of the following bugreport:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/673440

Hope it helps....

Xavier (xavier-monset) wrote :

@Mark Thanks a lot ! That's solve my problem.

Many thanks.

John Costella (jpcostella) wrote :

I have this bug and this workaround DID NOT fix it for me.

Machine works AOK booting into Windows, connects straight away and never drops the connection.

Under 10.04 and 10.10, the connection would be dropped occasionally (maybe after a few hours of inactivity) and annoyingly pop up the password dialog asking for confirmation (rather than just auto-connecting -- there doesn't seem to be an option for that).

Under 11.04, the machine is UNUSABLE. When in the SAME ROOM as the router, it connects straight away and works forever. (Like now.) When moved just 15 feet away, it drops the connection within seconds. Moving it back to the same room as the router reconnects it. Moving it 15 feet and it loses it within 5-15 seconds again.

I'm gobsmacked that Ubuntu has screwed up such an elementary driver.

Please tell me what dumps you would like me to provide.

Xvani (fredrile+launchpad) wrote :

@John Costella

Try disabling wireless power saving. More info:

http://ubuntuforums.org/showthread.php?t=1757558

Should this be separated into two bugs?

Seth Forshee (sforshee) wrote :

@John: If the workaround does not work for you then you must have a different problem. Please open a new bug report by running 'ubuntu-bug linux' from a terminal.

@Mark, @Xavier: Regarding the workaround linked to in comment #5, the rt2860sta driver is deprecated and in fact has already been removed from newer upstream kernel versions. If anything this driver should be blacklisted and the other drivers should not.

Changed in linux:
status: Confirmed → Fix Released

Xavier, thank you for reporting this and helping make Ubuntu better. Natty reached EOL on October 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the tag:
needs-upstream-testing

This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the text:
needs-upstream-testing

If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

Please let us know your results. Thank you for your understanding.

Helpful Bug Reporting Tips:
https://help.ubuntu.com/community/ReportingBugs

tags: added: natty needs-kernel-logs needs-upstream-testing
description: updated
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

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