rt73usb: an error in dmesg appears when module load but there is no error

[Id2ndR]

I've got an usb wifi dongle using rt73 chip.
During the boot (plymouth with theme text) I can see the two lines containing "Error" of the following part of my dmesg. These lines shouldn't appears because my hardware is working fine.

[ 6.126066] phy0 -> rt2500usb_init_eeprom: Error - Invalid RT chipset detected.
[ 6.126099] phy0 -> rt2x00lib_probe_dev: Error - Failed to allocate device.
[ 6.126158] usbcore: registered new interface driver rt2500usb
[ 6.427337] phy1: Selected rate control algorithm 'minstrel'
[ 6.427840] Registered led device: rt73usb-phy1::radio
[ 6.427855] Registered led device: rt73usb-phy1::assoc
[ 6.427871] Registered led device: rt73usb-phy1::quality
[ 6.428358] usbcore: registered new interface driver rt73usb

My wireless dongle is working normally since a long time but I think this is a bug in the detection of the chip that is used.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-22-generic 2.6.35-22.33
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: fabien 1659 F.... pulseaudio
CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfbff8000 irq 46'
   Mixer name : 'Realtek ALC888'
   Components : 'HDA:10ec0888,1462356a,00100001'
   Controls : 34
   Simple ctrls : 20
Card1.Amixer.info:
 Card hw:1 'NVidia'/'HDA NVidia at 0xfea7c000 irq 17'
   Mixer name : 'Nvidia ID 11'
   Components : 'HDA:10de0011,10de0101,00100100'
   Controls : 0
   Simple ctrls : 0
Card1.Amixer.values:

CheckboxSubmission: 1085bd3e1d3dc5fdefc443fc7f3687c2
CheckboxSystem: f78c696d4c0399fa91f9da1b540d7fd0
Date: Mon Sep 27 00:23:14 2010
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=e166d809-43d0-42f7-8ef0-16aaca01bd14
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7357
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=0b9cb367-7912-4673-bb3f-ccaf557fe60b ro quiet splash
ProcEnviron:
 LANG=fr_FR.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
RfKill:
 0: phy1: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
dmi.bios.date: 07/08/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.3
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: MS-7357
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.3:bd07/08/2008:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7357:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7357:rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
dmi.product.name: MS-7357
dmi.product.version: 1.0
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD

[Jeremy Foshee (jeremyfoshee)]

Hi Id2ndR,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. 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 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

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

[flash63 (elektronenblitz63)]

Hello,
two Modules are loadet, rt2500usb and rt73usb. Block rt2500usb. You need only rt73usb. Code:

echo 'blacklist rt2500usb' | sudo tee -a /etc/modprobe.d/blacklist.conf

Restart and check it out:

lsmod | egrep 'rt2|rt7'

[Id2ndR (id2ndr)]

Hi elektronenblitz63,

I confirm that blacklisting rt2500usb is a workaround for this bug.

[Francois Botha (igitur)]

I'm experiencing this problem, but I suspect I'm on the other side of the coin. Need your help to confirm it though.

$ lsusb | egrep rt -i
Bus 001 Device 002: ID 148f:2573 Ralink Technology, Corp. RT2501USB Wireless Adapter

Should I be blacklisting rt73usb or rt73usb. Either way, I tried them both and I'm unable get my wireless LAN started.

[Francois Botha (igitur)]

My question should actually read:

"Should I be blacklisting rt73usb or rt2500usb?"

[Id2ndR (id2ndr)]

In you case you need to blacklist rt2500usb.

[Francois Botha (igitur)]

*confused* If my device is identified as RT2501USB, shouldn't I be blacklisting rt73usb?

[flash63 (elektronenblitz63)]

Why confused? Your Chipset and required driver is rt73usb. Beware of the ID.
Bus 001 Device 002: ID 148f:2573 Ralink Technology

[Francois Botha (igitur)]

Ok, I was looking at the RT2501USB part and thought the rt2500usb driver is what I need. I tried blacklisting rt2500usb before and it didn't solve my issue, but I wasn't very persistent. Will try again.

[flash63 (elektronenblitz63)]

Check after reboot

lsmod | egrep 'rt2|rt7'
dmesg | egrep 'rt2500|rt73'
cat /etc/modprobe.d/blacklist.conf | grep rt2500

[Id2ndR (id2ndr)]

Sorry i would like to say to blacklist rt73 (because of the name that let me think that the chip is rt2500 in your case).

You can do more tests:
$ sudo rmmod rt2x00lib rt2x00usb rt73usb rt2500usb
$ dmesg | tail
$ sudo modprobe rt2500usb
$ dmesg | tail
$ iwconfig wlan0

$ sudo rmmod rt2x00lib rt2x00usb rt73usb rt2500usb
$ dmesg | tail
$ sudo modprobe rt73usb
$ dmesg | tail
$ iwconfig wlan0

The aim is to get more information about what happen when one module (rt73usb or rt2500usb) load and how it success or not to initialise the device.

However I think your trouble is different from mine, and maybe launchpad isn't the best place for that, especialy it your hardware hasn't been working on Linux previsouly.

[Francois Botha (igitur)]

My hardware was working 100% until recently when I upgraded the kernel. At the same time the entry in dmesg started showing, so I beilieve they are related.

I did the rmmod and modprobe steps and you were correct: rt2500usb should be blacklisted. rt73usb is the correct driver.

After blacklisting and setting up my wireless from scratch, things seems to be in order again. Thanks for you help.

[Francois Botha (igitur)]

For the record, this clarified my confusion:
"The RT2501USB is not to be confused with the RT2500USB, which is supported by different drivers."
(from http://wiki.debian.org/WiFi/rt73)

[Launchpad Janitor (janitor)]

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