Asus WL-167g - WLAN discconnects after several minutes from the AP

Thank you for filing this bug. It sounds like most likely a bug in the driver, so I am reassigning to the kernel.
To clarify, you are able to connect, but get disconnected after a few minutes? Can you then reconnect? Please post your /var/log/syslog when you get disconnected.
Could you test this on Hardy? A live cd should do.

Asus WL-167g is a USB wireless adapter that uses a ralink chipset/driver.

Hi!

I send more information about this bug. I activated the wlan by hand from the knetworkmanager. The connection was estabilished, but in some second was disconnected.
Here is the var/log/syslog

Mar 23 10:24:29 emerald NetworkManager: <info> Updating allowed wireless network lists.
Mar 23 10:24:29 emerald NetworkManager: <info> SWITCH: no current connection, found better connection 'wlan0'.
Mar 23 10:24:29 emerald dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan
0.dbus.get.reason
Mar 23 10:24:29 emerald NetworkManager: <info> Will activate connection 'wlan0/Sarpeidon'.
Mar 23 10:24:29 emerald NetworkManager: <info> Device wlan0 activation scheduled...
Mar 23 10:24:29 emerald NetworkManager: <info> Activation (wlan0) started...
Mar 23 10:24:29 emerald NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Mar 23 10:24:29 emerald NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Mar 23 10:24:29 emerald NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Mar 23 10:24:29 emerald NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Mar 23 10:24:29 emerald NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Mar 23 10:24:29 emerald NetworkManager: <info> Activation (wlan0/wireless): access point 'Sarpeidon' is encrypted, but N
O valid key exists. New key needed.
Mar 23 10:24:29 emerald NetworkManager: <info> Activation (wlan0) New wireless user key requested for network 'Sarpeidon
'.
Mar 23 10:24:29 emerald NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Mar 23 10:24:29 emerald NetworkManager: <WARN> nm_dbus_get_user_key_for_network_cb(): nm_dbus_get_user_key_for_network_c
b(): dbus returned an error. (org.freedesktop.NetworkManagerInfo.GetKeyError) org.freedesktop.NetworkManagerInfo.GetKey
Error
Mar 23 10:24:29 emerald NetworkManager: <info> Activation (wlan0) failure scheduled...
Mar 23 10:24:30 emerald NetworkManager: <info> Activation (wlan0) failed for access point (Sarpeidon)
Mar 23 10:24:30 emerald NetworkManager: <info> Activation (wlan0) failed.
Mar 23 10:24:30 emerald NetworkManager: <info> Deactivating device wlan0.
Mar 23 10:24:47 emerald NetworkManager: <debug> [1206264287.872099] nm_device_802_11_wireless_get_activation_ap(): Forcin
g AP 'Sarpeidon'
Mar 23 10:24:47 emerald NetworkManager: <info> User Switch: /org/freedesktop/NetworkManager/Devices/wlan0 / Sarpeidon
Mar 23 10:24:47 emerald NetworkManager: <info> Deactivating device wlan0.
Mar 23 10:24:47 emerald dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan
0.dbus.get.reason
Mar 23 10:24:47 emerald NetworkManager: <info> Device wlan0 activation scheduled...
Mar 23 10:24:47 emerald NetworkManager: <info> Activation (wlan0) started...
Mar 23 10:24:47 emerald NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Mar 23 10:24:47 emerald NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Mar 23 10:24:47 emerald NetworkManager: <info...

Hi!

I send more detail. If I use nm-applet 0.6.5 (gnome) instead of knetworkmanager (kde), the error occurs rarer.
Now the AP was disconnected after one hours, and it was impossible to reconnect.
Here is the syslog.

Apr 3 22:34:34 emerald kernel: [ 3245.089841] phy0 -> rt73usb_rf_write: Error - PHY_CSR4 register busy. Write failed.
Apr 3 22:34:34 emerald kernel: [ 3245.095357] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x3024 with error -19.
Apr 3 22:34:34 emerald kernel: [ 3245.095373] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3024 with error -19.
Apr 3 22:34:34 emerald kernel: [ 3245.095386] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x3020 with error -19.
Apr 3 22:34:34 emerald kernel: [ 3245.095400] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3020 with error -19.
Apr 3 22:34:34 emerald kernel: [ 3245.095413] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x3040 with error -19.
Apr 3 22:34:34 emerald kernel: [ 3245.095427] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3040 with error -19.
Apr 3 22:34:34 emerald kernel: [ 3245.095440] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x3050 with error -19.
Apr 3 22:34:34 emerald kernel: [ 3245.095453] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3050 with error -19.
Apr 3 22:34:34 emerald kernel: [ 3245.095467] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x3064 with error -19.
Apr 3 22:34:34 emerald kernel: [ 3245.095480] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3064 with error -19.
Apr 3 22:34:34 emerald kernel: [ 3245.095495] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x3040 with error -19.
Apr 3 22:34:34 emerald kernel: [ 3245.095508] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3040 with error -19.
Apr 3 22:34:34 emerald kernel: [ 3245.095576] wlan0: No STA entry for own AP 00:18:f3:4d:c1:8d
Apr 3 22:34:35 emerald kernel: [ 3246.094920] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -19.
Apr 3 22:34:35 emerald kernel: [ 3246.094954] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x308c with error -19.
Apr 3 22:34:35 emerald kernel: [ 3246.094968] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -19.
Apr 3 22:34:35 emerald kernel: [ 3246.094984] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x30c4 with error -19.
Apr 3 22:34:35 emerald kernel: [ 3246.094998] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -19.
Apr 3 22:34:35 emerald kernel: [ 3246.095111] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -19.
Apr 3 22:34:35 emerald kernel: [ 3246.095224] phy0 -> rt2x00usb_v...

Hi!

I upgraded my system to hardy. Here this bug doesn't come, but the connection takes very slowly. Here is my syslog.

Apr 16 18:20:42 emerald NetworkManager: <info> Updating allowed wireless network lists.
Apr 16 18:20:43 emerald NetworkManager: <info> SWITCH: no current connection, found better connection 'wlan0'.
Apr 16 18:20:43 emerald dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.reason
Apr 16 18:20:43 emerald NetworkManager: <info> Will activate connection 'wlan0/Sarpeidon'.
Apr 16 18:20:43 emerald NetworkManager: <info> Device wlan0 activation scheduled...
Apr 16 18:20:43 emerald NetworkManager: <info> Activation (wlan0) started...
Apr 16 18:20:43 emerald NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 16 18:20:43 emerald NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Apr 16 18:20:43 emerald NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Apr 16 18:20:43 emerald NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Apr 16 18:20:43 emerald NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Apr 16 18:20:43 emerald NetworkManager: <info> Activation (wlan0/wireless): access point 'Sarpeidon' is encrypted, but NO valid key exists. New key needed.
Apr 16 18:20:43 emerald NetworkManager: <info> Activation (wlan0) New wireless user key requested for network 'Sarpeidon'.
Apr 16 18:20:43 emerald NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Apr 16 18:20:44 emerald NetworkManager: <info> Activation (wlan0) New wireless user key for network 'Sarpeidon' received.
Apr 16 18:20:44 emerald NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 16 18:20:44 emerald NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Apr 16 18:20:44 emerald NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Apr 16 18:20:44 emerald NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Apr 16 18:20:44 emerald NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Apr 16 18:20:44 emerald NetworkManager: <info> Activation (wlan0/wireless): access point 'Sarpeidon' is encrypted, and a key exists. No new key needed.
Apr 16 18:20:45 emerald NetworkManager: <info> retry to connect to global supplicant socket (try=1)
Apr 16 18:20:46 emerald NetworkManager: <info> SUP: sending command 'INTERFACE_ADD wlan0^I^Iwext^I/var/run/wpa_supplicant0^I'
Apr 16 18:20:46 emerald kernel: [ 148.351643] NET: Registered protocol family 17
Apr 16 18:20:46 emerald NetworkManager: <info> SUP: response was 'OK'
Apr 16 18:20:46 emerald NetworkManager: <info> SUP: sending command 'AP_SCAN 1'
Apr 16 18:20:46 emerald NetworkManager: <info> SUP: response was 'OK'
Apr 16 18:20:46 emerald NetworkManager: <info> SUP: sending command 'ADD_NETWORK'
Apr 16 18:20:46 emerald NetworkManager: <info> SUP: response was '0'
Apr 16 18:20:46 emerald NetworkMa...

This has happened to me twice in a week now using a Belkin usb wireless stick that uses the rt73 chipset on a fresh install of Gutsy x64.

Bizarrely, a reboot has not fixed the issue - I have only got the device working again by using it in windows before booting ubuntu.

rt2x00usb_vendor_request: Error -Vendor Request 0x07 failed for offset 0x3030 with error -110

rt73usb_enable_radio: Error - Register initialization failed.

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

I have a very similar troubles on my ubuntu 8.10 beta.

Is this still an issue with the most recent 2.6.27-7.14 kernel? Please attach your dmesg output if it is. Thanks.

I've got a D-Link DWL-G122 with hardware version C1.
It has a RT2571WF chip, and so does the Asus WL-167g
Both cards uses the rt2x00 driver (rt73usb)

If i wiggle around with the USB card after it's been properly recognized, dmesg will show something like this:

rt2x00usb_vendor_request: Error - Vendor Request <hex address> failed for offset <hex address> with error -19.

This is a hardware issue. More specific: the grooves at each side inside the USB plug mismatches with the USB port, leading to a poor connection.
Try fitting the the USB network adapter in another socket, it might help.

I don't know about the other issues though.

Correction: The error code varies as well.
I've seen: error -19, error -62, and error -71. And that's just this session.
The error code seems to depend on what instructions are attempted at the moment. (doh)

Still reproducing on ubuntu 8.10 with kernel 2.6.27-11-generic.

Is there any solution to this problem?!

The problem has somehow dissipated.

What I have done is:

sudo modprobe rt73usb #(wrong driver according to http://wiki.debian.org/WiFi/rt73#procedure)
sudo ifconfig wlan0 up

Also try different usb ports. It could also help.

After that I made several reboots. And everything was working even without above mentioned commands.
But it is to early to close the incident. My ifconfig shows erroneous record:

wmaster0-00 . My dongle has incorrectly long MAC addrres in the format XX-XX-XX-XX-XX-XX-XX-XX-00-00-00-00-00-00-00-00
Hope that this bug will soon be exterminated :)

With Jaunty on my laptop Samsung R610 my WLAN worked flawless for months already. Up to now, for the event is similar to reported in this bug. In Windows it works OK, in Ubuntu I see all sorts of AP's. Mine works with another laptop (Acer T800/Sweex PCcard WLAN and Jaunty too) settings are exactly the same. The wired connection is OK (I use it now) but wireless will not work anymore.

This is what tghe syslog says:
Oct 1 21:31:41 pje-laptop NetworkManager: <info> Marking connection 'Auto PJE_NET' invalid.
Oct 1 21:31:41 pje-laptop NetworkManager: <info> Activation (wlan0) failed.
Oct 1 21:31:41 pje-laptop NetworkManager: <info> (wlan0): device state change: 9 -> 3
Oct 1 21:31:41 pje-laptop NetworkManager: <info> (wlan0): deactivating device (reason: 0).
Oct 1 21:31:41 pje-laptop kernel: [ 837.744054] iwlagn: index 0 not used in uCode key table.

What more can I do to get it working again? What more should I post from logs?
Thanks
Peter

I am having a similar (the same?) problem with Ubuntu 9.10 and Asus WL-167G. The device works out-of-the-box, I am able to connect to my WPA2 encrypted network. The connection is fine for a few minutes, then problems appear. I am not really being disconnected, but larger packets (e.g. 1000 bytes) are not going thru, or maybe every 20th packet goes thru - I am testing this with ping -s ..., I am pinging my DSL modem. There is nothing interesting in the syslog.
Restarting network-manager solves the problem, but it reappears after a few minutes.

My problem is resolved when I set the power management to off via "iwconfig wlan0 power off".

Thanks a lot!

iwconfig wlan0 power off

this solves the problem.

My Asus WL-167G just stopped connecting to my WPA2 enabled network.. does anybody else experience this? I don't know if this happened after some recent upgrade or not.

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

Dear support team,

I want to confirm that the bug still exist in ubuntu 10.10, but as mentioned above, command "iwconfig wlan0 power off" fix the issue.
Maybe it is a good idea to turn off this fag by default

Many thanks,
Georgi

i can confirm that this problem persists in ubuntu 11.04. the solution of using "iwconfig wlan0 power off" is also still valid. i wish somebody would fix this problem which has been around for three years and six ubuntu versions.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 201306

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: miso 311 F.... pulseaudio
 /dev/snd/pcmC1D0c: miso 311 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'NVidia'/'HDA NVidia at 0xfce78000 irq 20'
   Mixer name : 'Nvidia MCP77/78 HDMI'
   Components : 'HDA:1106e721,10438345,00100100 HDA:10de0002,10de0101,00100000'
   Controls : 39
   Simple ctrls : 20
Card1.Amixer.info:
 Card hw:1 'SAA7134'/'saa7133[0] at 0xfcfff800 irq 17'
   Mixer name : 'SAA7134 Mixer'
   Components : ''
   Controls : 6
   Simple ctrls : 3
DistroRelease: Ubuntu 11.04
HibernationDevice: RESUME=UUID=3685f391-7aa8-49a2-b454-fb9f495ee8c0
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic root=UUID=f6a0ff1f-b640-4c28-880e-a0525968bd64 ro quiet splash acpi_enforce_resources=lax vt.handoff=7
ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
RelatedPackageVersions:
 linux-restricted-modules-2.6.38-11-generic N/A
 linux-backports-modules-2.6.38-11-generic N/A
 linux-firmware 1.52.1
RfKill:
 13: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: natty
Uname: Linux 2.6.38-11-generic i686
UpgradeStatus: Upgraded to natty on 2011-05-05 (108 days ago)
UserGroups: adm admin audio cdrom dialout lpadmin mythtv netdev plugdev pulse-access sambashare users
dmi.bios.date: 07/28/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1307
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M3N78-VM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1307:bd07/28/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78-VM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]