[Gutsy] Ralink 802.11 bg WLAN device doesn't run (/org/freedesktop/Hal/devices/usb_device_db0_6877_noserial)

Bug #126017 reported by Carlos Menezes
4
Affects Status Importance Assigned to Milestone
hal (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

In Feisty Fawn, it used rt73usb driver, but it didn't run ..... Gusty didn't detect anything.

Revision history for this message
Carlos Menezes (cedmenezes) wrote :
Download full text (4.3 KiB)

Dear all,

I've discovered the problem is not in driver, but in NetworkManager (in Gutsy, nm-applet 0.6.5).
Look at these pages:

http://live.gnome.org/NetworkManagerHardware

Unsupported or Unknown Cards & Drivers

rt73
Status: Doesn't work with NetworkManager, but driver is good enough to get WEP/unencrypted connections "by hand"

http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Linux.Wireless.drivers.802.11ag.html

4.11 Ralink RT2500 and 2570 cards
Driver status : Beta
Driver name : rt2500.o
PCI : rt61.o
USB : rt73.o
rt2x00.o
Version : 1.1.0 (beta) and 2.0.4 (alpha)
Where : http://rt2x00.serialmonkey.com/
http://rt2400.sourceforge.net/
http://www.ralinktech.com/supp-1.htm
Maintainers : Paul Lin
Mark Wallis <markwallis at users.sourceforge.net>
Ivo van Doorn <ivd at euronet.nl>
Mailing list : http://sourceforge.net/mail/?group_id=107832
Documentation : Text files, Howtos
Configuration : Wireless Extensions and specific graphical tool
Statistics : Wireless Extensions
Modes : Managed, Ad-Hoc
Security : WEP, WPA
Scanning : Wireless Extensions
Monitor : Yes
Multi-devices : ?
Interoperability : 802.11b, 802.11g and 802.11a depending on hardware
Other features : -
Non implemented : -
Bugs : SMP problems
License : GPL
Vendor web page : http://www.ralinktech.com/
http://minitar.com/
http://rt2x00.serialmonkey.com/wiki/index.php/Hardware

4.11.1 The device
Ralink may have been late in releasing a 802.11b chipset, the RT2400 (section 3.27), however it was fairly quickly followed by the RT2500, a 802.11g chipset. The RT2500 is a evolution of the RT2400, and share many characteristics with it.

Like other 802.11g chipsets, it supports standard OFDM bitrates up to 54 Mb/s and all modern 802.11 features such as WPA and QoS (802.11e). On top of that, it support a proprietary 72 Mb/s bitrate. The RT2500 is designed for MiniPCI and CardBus interfaces, and the RT2570 is designed with a USB 2.0 interface.

As usual, this chipset is sold by a wide variety of vendors under different model names, and some of those use the same model name for different chipsets. The project pages includes a long list of cards including this chipset. A special mention to Minitar which has a dedicated Linux support forum.

The RT2500 was quickly followed by other 802.11g chipsets. The RT61 family includes the rt2561 and rt2661 PCI chipsets and adds support for turbo bit rate (100 Mb/s) and for the rt2661 only proprietary MIMO (not 802.11n compatible). The RT73 family includes the RT2573 and RT2571 USB chipsets, and is the equivalent of the RT61 (but without the MIMO chipset). Those chipset are available with two radio options, 2.4 GHz only, or 2.4 GHz plus 5 GHz, for additional 802.11a support.

Ralink has now released the RT2800 family. The main feature of those chipset is the addition of draft-802.11n MIMO support.

4.11.2 The driver
Like for the RT2400, Ralink wrote a Linux driver for the RT2500 and RT2750, but this time they decided to release it themselves as GPL. Moreover, the driver is functional, full of features and with a graphical utility, so this represent a very generous contribution to the OpenSource community. The driver supports WEP, WPA, S...

Read more...

Revision history for this message
Javier Jardón (jjardon) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.

 Please include the information requested at [WWW] https://wiki.ubuntu.com/DebuggingHardwareDetection as separate attachments.

Changed in hal:
assignee: nobody → torkiano
status: New → Incomplete
Revision history for this message
Javier Jardón (jjardon) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in hal:
status: Incomplete → Invalid
assignee: torkiano → nobody
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.