Ubuntu
linux-restricted-modules-2.6.22 package

rt2500usb module not working with asus wl-167g wifi stick

Bug #144448 reported by luca.mg on 2007-09-24

This bug report is a duplicate of: Bug #134660: Ralink rt2400 / rt2500 / rt2570 / rt61 / rt73 do not work out of the box in Gutsy/Hardy. Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	linux-restricted-modules-2.6.22 (Ubuntu)	New	Undecided	Unassigned

Bug Description

Stick details as from lsusb: Bus 005 Device 004: ID 0b05:1706 ASUSTek Computer, Inc., this thing used to work out of the box in feisty. It does not work in gutsy with kernel 2.6.22-12-generic i686 (and previous): card is detected but signal strenght stays at zero and no way it will connect to the network either with manual configuration (network-admin applet) and or NetworkManager; tested also with wicd 1.3.1 with no success. As a workaround I blacklisted rt2500usb, rt2x00usb, rt2x00lib and downloaded-compiled-loaded the cvs version of the rt2570 module from serialmonkey (the v1.1.0-b2 release would not compile), now everything works and the network applet is showing WPA-WPA2 as available (I'm using wep as this was the only choice with feisty); I also have to report that as of rt2570-cvs-2007092201 the stick works on a multiprocessor Athlon MP box too.

Thank You for Your attention

Luca M. Gazzolo

Revision history for this message

Id2ndR (id2ndr) wrote on 2007-09-28:

Hi,

According to $ modinfo rt2500usb | grep -i v0b05p1706
The module should be loaded with your device.

Is your device using rt73 with cvs version ?
What are the loaded module ($ lsmod | grep rt) with cvs version ?

Revision history for this message

luca.mg (luca-mg) wrote on 2007-09-30: Re: [Bug 144448] Re: rt2500usb module not working with asus wl-167g wifi stick

Id2ndR wrote:
> Hi,
>
> According to $ modinfo rt2500usb | grep -i v0b05p1706
> The module should be loaded with your device.
>
> Is your device using rt73 with cvs version ?
> What are the loaded module ($ lsmod | grep rt) with cvs version ?
>

I'm not at the box now, anyhow: yes the rt2500usb module is loaded,
wlan0 is there, but the thing does not work (signal strenght stays at
zero as stated) and no it's not an rt73; the cvs is the old rt2570 from
serialmonkey, several versions downloaded recently at different times.
For Your information the rt2500usb module from both fedora 7 and suse
10.3 rc1 works very well with this device (fedora works better as suse
goes off randomly). Please feel free to contact me again if You need
additional info.

Luca M. Gazzolo

Revision history for this message

Id2ndR (id2ndr) wrote on 2007-10-08:

If bug #139070 is solved by an update of the driver, this should solve your trouble too. But nobody seems to have worked on it yet. Subscribe to the other bug to see its activity.

Revision history for this message

luca.mg (luca-mg) wrote on 2007-10-09:

Download full text (6.2 KiB)

Hi there, as a new kernel is out I was coming to give You an update, and here it is; thank You for pointing me to https://bugs.launchpad.net/bugs/139070 but the stick I'm talking about is an rt25 card not an rt73 one. So, new kernel, same behaviour, here it is the details:

gabriele@chow:~$ uname -rvm
2.6.22-13-generic #1 SMP Thu Oct 4 17:18:44 GMT 2007 i686

dmesg output: what is this wmaster0 thing?
---snip---
[ 47.551086] usbcore: registered new interface driver hci_usb
[ 47.922760] ieee80211_init: failed to initialize WME (err=-17)
[ 47.935668] iwlwifi_rc80211_simple: Unknown symbol iwlwifi_ieee80211_rate_control_unregister
[ 47.935710] iwlwifi_rc80211_simple: Unknown symbol iwlwifi_sta_info_put
[ 47.935745] iwlwifi_rc80211_simple: Unknown symbol iwlwifi_sta_info_get
[ 47.935799] iwlwifi_rc80211_simple: Unknown symbol iwlwifi_ieee80211_rate_control_register
[ 47.948378] wmaster0: Selected rate control algorithm 'simple'
[ 48.002202] usbcore: registered new interface driver rt2500usb
[ 48.054484] PCI: Setting latency timer of device 0000:00:11.6 to 64
[ 48.371347] NET: Registered protocol family 10
[ 48.371464] lo: Disabled Privacy Extensions
[ 48.371539] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 48.371580] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 48.558119] ACPI: PCI interrupt for device 0000:00:11.6 disabled
[ 48.558136] VIA 82xx Modem: probe of 0000:00:11.6 failed with error -13
[ 48.558410] ACPI: PCI Interrupt 0000:00:11.5[C] -> GSI 22 (level, low) -> IRQ 19
[ 48.558553] PCI: Setting latency timer of device 0000:00:11.5 to 64
[ 48.865372] wlan0: Initial auth_alg=0
[ 48.865379] wlan0: authenticate with AP 00:14:c1:1f:1f:e0
[ 48.867136] wlan0: RX authentication from 00:14:c1:1f:1f:e0 (alg=0 transaction=2 status=0)
[ 48.867139] wlan0: authenticated
[ 48.867142] wlan0: associate with AP 00:14:c1:1f:1f:e0
[ 48.869374] wlan0: RX AssocResp from 00:14:c1:1f:1f:e0 (capab=0x411 status=0 aid=1)
[ 48.869378] wlan0: associated
[ 48.870416] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 49.071708] codec_read: codec 0 is not valid [0xfe0000]
[ 49.077951] codec_read: codec 0 is not valid [0xfe0000]
[ 49.084236] codec_read: codec 0 is not valid [0xfe0000]
[ 49.090480] codec_read: codec 0 is not valid [0xfe0000]
[ 49.433469] wlan0: duplicate address detected!
---snip---

lsusb output, do not bother with the Broadcom device as it is a bluetooth dongle:
gabriele@chow:~$ lsusb
Bus 005 Device 002: ID 04b4:6560 Cypress Semiconductor Corp. CY7C65640 USB-2.0 "TetraHub"
Bus 005 Device 001: ID 0000:0000
Bus 005 Device 004: ID 0b05:1706 ASUSTek Computer, Inc.
Bus 001 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 002: ID 0a5c:2101 Broadcom Corp.
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000

according to Asus:

0B05:1706 rt25USB
0B05:1707 rt25USB
0B05:1723 rt73
0B05:1724 rt73

a couple of sifted lsusb outputs:
gabriele@chow:~$ lsmod |grep rt2
rt2500usb 22016 0
rt2x00usb 12032 1 rt2500usb
rt2x00lib 19584 2 rt2500usb,rt2x00usb
rfkill 8208 1 rt2x00lib
mac80211 ...

gabriele@chow:~$ uname -rvm
2.6.22-13-generic #1 SMP Thu Oct 4 17:18:44 GMT 2007 i686

dmesg output: what is this wmaster0 thing?
---snip---
[   47.551086] usbcore: registered new interface driver hci_usb
[   47.922760] ieee80211_init: failed to initialize WME (err=-17)
[   47.935668] iwlwifi_rc80211_simple: Unknown symbol iwlwifi_ieee80211_rate_control_unregister
[   47.935710] iwlwifi_rc80211_simple: Unknown symbol iwlwifi_sta_info_put
[   47.935745] iwlwifi_rc80211_simple: Unknown symbol iwlwifi_sta_info_get
[   47.935799] iwlwifi_rc80211_simple: Unknown symbol iwlwifi_ieee80211_rate_control_register
[   47.948378] wmaster0: Selected rate control algorithm 'simple'
[   48.002202] usbcore: registered new interface driver rt2500usb
[   48.054484] PCI: Setting latency timer of device 0000:00:11.6 to 64
[   48.371347] NET: Registered protocol family 10
[   48.371464] lo: Disabled Privacy Extensions
[   48.371539] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   48.371580] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   48.558119] ACPI: PCI interrupt for device 0000:00:11.6 disabled
[   48.558136] VIA 82xx Modem: probe of 0000:00:11.6 failed with error -13
[   48.558410] ACPI: PCI Interrupt 0000:00:11.5[C] -> GSI 22 (level, low) -> IRQ 19
[   48.558553] PCI: Setting latency timer of device 0000:00:11.5 to 64
[   48.865372] wlan0: Initial auth_alg=0
[   48.865379] wlan0: authenticate with AP 00:14:c1:1f:1f:e0
[   48.867136] wlan0: RX authentication from 00:14:c1:1f:1f:e0 (alg=0 transaction=2 status=0)
[   48.867139] wlan0: authenticated
[   48.867142] wlan0: associate with AP 00:14:c1:1f:1f:e0
[   48.869374] wlan0: RX AssocResp from 00:14:c1:1f:1f:e0 (capab=0x411 status=0 aid=1)
[   48.869378] wlan0: associated
[   48.870416] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   49.071708] codec_read: codec 0 is not valid [0xfe0000]
[   49.077951] codec_read: codec 0 is not valid [0xfe0000]
[   49.084236] codec_read: codec 0 is not valid [0xfe0000]
[   49.090480] codec_read: codec 0 is not valid [0xfe0000]
[   49.433469] wlan0: duplicate address detected!
---snip---

lsusb output, do not bother with the Broadcom device as it is a bluetooth dongle:
gabriele@chow:~$ lsusb
Bus 005 Device 002: ID 04b4:6560 Cypress Semiconductor Corp. CY7C65640 USB-2.0 "TetraHub"
Bus 005 Device 001: ID 0000:0000  
Bus 005 Device 004: ID 0b05:1706 ASUSTek Computer, Inc. 
Bus 001 Device 001: ID 0000:0000  
Bus 004 Device 001: ID 0000:0000  
Bus 003 Device 002: ID 0a5c:2101 Broadcom Corp. 
Bus 003 Device 001: ID 0000:0000  
Bus 002 Device 001: ID 0000:0000

according to Asus:

0B05:1706	rt25USB
0B05:1707	rt25USB
0B05:1723	rt73
0B05:1724	rt73

a couple of sifted lsusb outputs:
gabriele@chow:~$ lsmod |grep rt2
rt2500usb              22016  0 
rt2x00usb              12032  1 rt2500usb
rt2x00lib                19584  2 rt2500usb,rt2x00usb
rfkill                        8208  1 rt2x00lib
mac80211             171016  3 rc80211_simple,rt2x00usb,rt2x00lib
input_polldev         5896  1 rt2x00lib
crc_itu_t                3072  1 rt2x00lib
usbcore                 138248  6 rt2500usb,rt2x00usb,hci_usb,ehci_hcd,uhci_hcd

gabriele@chow:~$ lsmod |grep 80211
rc80211_simple          6912  1 
mac80211              171016  3 rc80211_simple,rt2x00usb,rt2x00lib
cfg80211                7304  1 mac80211

iwconfig output:
gabriele@chow:~$ iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

wmaster0  no wireless extensions.

wlan0     IEEE 802.11g  ESSID:"c4s4"  
          Mode:Managed  Frequency:2.437 GHz  Access Point: 00:14:C1:1F:1F:E0   
          Retry min limit:7   RTS thr:off   Fragment thr=2346 B   
          Link Signal level=-59 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

ifconfig output:
gabriele@chow:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:0C:6E:9C:B7:91  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:16

eth0:avah Link encap:Ethernet  HWaddr 00:0C:6E:9C:B7:91  
          inet addr:169.254.8.110  Bcast:169.254.255.255  Mask:255.255.0.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          Interrupt:16

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:219 errors:0 dropped:0 overruns:0 frame:0
          TX packets:219 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:19073 (18.6 KB)  TX bytes:19073 (18.6 KB)

wlan0     Link encap:Ethernet  HWaddr 00:11:D8:DF:79:13  
          inet addr:192.168.1.13  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::211:d8ff:fedf:7913/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:23 errors:0 dropped:0 overruns:0 frame:0
          TX packets:301 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:3903 (3.8 KB)  TX bytes:25409 (24.8 KB)

wmaster0  Link encap:UNSPEC  HWaddr 00-11-D8-DF-79-13-00-00-00-00-00-00-00-00-00-00  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

and still the stick does not work; this is it! Hope the info is of some use. Next I'm going to do some tests compiling modules downloaded from the internet and I'll let You know what the outcome is. FYI the fedora kernel driving this card beautifully is release 2.6.22.9-91.fc7, also the 2.6.23 kernel from the fedora development version works well with this card. As for the serialmonkey rt2570 cvs the last I've tried was rt2570-cvs-2007092413.

Revision history for this message

Id2ndR (id-2ndr) wrote on 2007-10-09:

> thank You for pointing me to
> https://bugs.launchpad.net/bugs/139070 but the stick I'm talking about
> is an rt25 card not an rt73 one. So, new kernel, same behaviour, here it
> is the details:
>

Yes. But rt2x00 is a driver for several chips. So if rt2x00 is update,
it may help you too.

> dmesg output: what is this wmaster0 thing?
>
Interface for master mode (access point).

According to your ifconfig and iwconfig output, your wireless interface
got an ip (192.168.1.13), and is connected to an AccessPoint. So what
about the dhcp server ? Can you ping your router (may be 192.168.1.1) ?
> and still the stick does not work; this is it! Hope the info is of some
> use. Next I'm going to do some tests compiling modules downloaded from
> the internet and I'll let You know what the outcome is. FYI the fedora
> kernel driving this card beautifully is release 2.6.22.9-91.fc7, also
> the 2.6.23 kernel from the fedora development version works well with
> this card. As for the serialmonkey rt2570 cvs the last I've tried was
> rt2570-cvs-2007092413.

Driver include in Ubuntu isn't rt2570 one, it's the new rt2x00 that will
be release with future kernel.

You can use rt2570 but it doesn't work with networkManager.

Revision history for this message

luca.mg (luca-mg) wrote on 2007-10-11:

Thank You for taking the time to deal with this.

>Yes. But rt2x00 is a driver for several chips. So if rt2x00 is update,
>it may help you too.

I'm sorry it does not help; I also took a test with the latest 2.6.22-14 kernel
with no success, the only thing I spotted is from dmesg:

gabriele@ciao:~$ dmesg |grep ieee802
[ 43.096306] ieee80211_init: failed to initialize WME (err=-17)
[ 43.112825] iwlwifi_rc80211_simple: Unknown symbol iwlwifi_ieee80211_rate_control_unregister
[ 43.112962] iwlwifi_rc80211_simple: Unknown symbol iwlwifi_ieee80211_rate_control_register

>According to your ifconfig and iwconfig output, your wireless interface
>got an ip (192.168.1.13), and is connected to an AccessPoint. So what
>about the dhcp server ? Can you ping your router (may be 192.168.1.1) ?

the card has an ip because it is configured for static ip, it can only ping itself

>Driver include in Ubuntu isn't rt2570 one, it's the new rt2x00 that will
>be release with future kernel.

yes indeed but downloading-compiling-loading the rt2570 module
(blacklisting the rt2x00) gives me a working network.

Thank You for Your attention

Revision history for this message

Daniel Comşa (daniel-comsa) wrote on 2007-10-13:

This looks similar with bug #147811. I have the same problem. I have posted my log files on the other bug report.

Br,
Daniel.

Revision history for this message

luca.mg (luca-mg) wrote on 2007-10-14:

Daniel

>This looks similar with bug #147811. I have the same problem.

I do agree with ^that^, this is the same that's happening to me

>I have posted my log files on the other bug report.

regarding Your dmesg:

[ 218.108000] ieee80211_init: failed to initialize WME (err=-17)
[ 218.120000] iwlwifi_rc80211_simple: Unknown symbol iwlwifi_ieee80211_rate_control_unregister
[ 218.120000] iwlwifi_rc80211_simple: Unknown symbol iwlwifi_sta_info_put
[ 218.120000] iwlwifi_rc80211_simple: Unknown symbol iwlwifi_sta_info_get
[ 218.120000] iwlwifi_rc80211_simple: Unknown symbol iwlwifi_ieee80211_rate_control_register

You get the error 17 too

>Also, here is lsusb and lspci. The Asus adapter si the one on usb (Bus 004 Device 002: ID 174f:a311)

this is a device id that I do not know of, perhaps a very recent stick? Anyhow all those different
flavours of Asus sticks seem to share the same code, and hidden somewhere there must a typo!

Revision history for this message

Javier Jardón (jjardon) wrote on 2008-02-07:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 134660, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.