rt73usb fails should use open source alternative

Bug #89665 reported by peter
10
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Wishlist
Unassigned
linux-ubuntu-modules-2.6.22 (Baltix)
New
Undecided
Unassigned

Bug Description

The wireless stick dwl-g122 c1 does not work with fiesty

If you follow this wiki http://wiki.ubuntu-it.org/RalinkRT73 then the dwl-g122 H/W ver C1 F/W ver 3.00 will work using WPA on herd5

However you must not plug the stick in until you have completed the wiki instructions, if you do feisty becomes virtually unusable because the mouse pointer cannot be controlled.

When you plug the stick in it works straight away but if you then reboot feisty hangs half way through the boot progress bar. To stop this you must also blacklist rt2570. Then the wireless stick is rock solid.

Suggest you drop ralink drivers and move to serial monkey open drivers for rt73 chip.

ProblemType: Bug
Date: Sun Mar 4 14:09:06 2007
DistroRelease: Ubuntu 7.04
Uname: Linux peter-desktop 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 GNU/Linux

Revision history for this message
Cristian Aravena Romero (caravena) wrote :

Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description doesn't yet have enough information.

Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at http://wiki.ubuntu.com/DebuggingKernelProblems . Thanks in advance!

Revision history for this message
peter (peter-blackburnsonline) wrote :

I am sorry to have bothered you, if this is the sort of answer that I get to a well described problem with a working alternative, then I have no respect for this bug procedure.

From now on anything I find I shall write down for MY future reference and leave it at that.

description: updated
Revision history for this message
Chuck Short (zulcss) wrote :

Hi Peter,

The debugging information is not necessary since this is a wish list bug.

Thanks
chuck

Changed in linux-source-2.6.20:
assignee: caravena → zulcss
importance: Undecided → Wishlist
status: Needs Info → Confirmed
Revision history for this message
Nafallo Bjälevik (nafallo) wrote :

We had rt2x00 until we switched to 2.6.20 AFAIK, and it never worked from what I've heard. Atleast rt61pci didn't work here. rt2[45]00 have always been legacy from what I know. Also, ralinks drivers are GPL'd aswell. Where's the real problem with one broken driver to a little less broken driver? :-)

Revision history for this message
Kyle McMartin (kyle) wrote :

Hi Peter,

Please rest assured, the input you provided is valuable to us. If it were possible to delete comments from launchpad at the present time, I would. Unfortunately, the number of bugs we have means sometimes the community members doing bug triage post stock comments asking for more information without more than a cursory glance at the bug. If you have any further concerns or questions, feel free to bring them up to the kernel team mailing list (<email address hidden>) or directly to me (<email address hidden>.) And please, keep reporting bugs, every bit helps us produce a better distribution.

Cheers,
  Kyle (speaking on behalf of the Ubuntu Kernel Team)

Revision history for this message
Matheus Pacheco de Andrade (matheusp-andrade-deactivatedaccount) wrote :

It shouldn't be considered a wish, since it reports some piece of hardware not working properly.
I confirm that in latest kernel revision (2.6.20-14) the rt73 piece of wireless adapter only works when compiling the rt2x00 project's rt73 cvs driver.
It's funny, since in 2.6.20-13 it worked "out of the box" after the update - maybe it was using the driver I compiled for 2.6.20-12?

Revision history for this message
Robert Smart (bob-smart) wrote :

I'd like to confirm that, as shipped feisty locks up when I plug in my DWL-G122 rev C1. With the serial monkey driver installed as described at the Italian site, it works correctly, including with WPA.

Revision history for this message
Steven Wagner (stevenwagner) wrote :

I added a quick blurp here: https://help.ubuntu.com/community/WifiDocs/Driver/RalinkRT73

The driver works fine if you simply download the file and follow the readme.
Driver here: http://rt2x00.serialmonkey.com/rt73-cvs-daily.tar.gz

I expect that this will get merged into the kernel soon. Since a lot of people need this though, perhaps this could be added as a custom patch if it doesn't get merged into the linus kernel by the time gutsy roles out.

Revision history for this message
Matheus Pacheco de Andrade (matheusp-andrade-deactivatedaccount) wrote : Re: [Bug 89665] Re: rt73usb fails should use open source alternative

Remembering you that this serialmonkey driver doesnt work with
network-manager.

On 7/5/07, Steven Wagner <email address hidden> wrote:
>
> I added a quick blurp here:
> https://help.ubuntu.com/community/WifiDocs/Driver/RalinkRT73
>
> The driver works fine if you simply download the file and follow the
> readme.
> Driver here: http://rt2x00.serialmonkey.com/rt73-cvs-daily.tar.gz
>
> I expect that this will get merged into the kernel soon. Since a lot of
> people need this though, perhaps this could be added as a custom patch
> if it doesn't get merged into the linus kernel by the time gutsy roles
> out.
>
> --
> rt73usb fails should use open source alternative
> https://bugs.launchpad.net/bugs/89665
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Kyle M Weller (kylew) wrote :

the rt73 drivers do not work out of the box for gutsy beta as well, this is a serious issue that ive always had since feisty beta when I first tried out ubuntu, the serialmonkey drivers work only for WEP on the belkin usb dongle:
 Bus 004 Device 003: ID 050d:705a Belkin Components

It seems whoever wrote the driver forgot to put in the correct USB ID's here is the fixed driver
http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Flinville%2Fwireless-dev.git&a=search&h=rt2x00&st=commit&s=rt73

Revision history for this message
Id2ndR (id2ndr) wrote :

See bug #139070 too.

Changed in linux-source-2.6.20:
assignee: zulcss → ubuntu-kernel-team
Revision history for this message
Jerzy Jalocha N (jjalocha) wrote :

Will mark this as duplicate of Bug #134660, since it has higher priority. Hopefully we get this supported in Hardy!

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

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

Other bug subscribers

Remote bug watches

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