[Bug 638791] [NEW] old and faulty rt2870sta

Launchpad Bug Tracker 638791 at bugs.launchpad.net
Sun Sep 19 21:15:10 UTC 2010


You have been subscribed to a public bug:

This report concerns the Gigabyte AirCruiser N300 GN-WB31N-RH,  with a
Ralink RT2870 chip set. The problem seems to concern several other
devices with this chipset as well, considering all the different guides
I've come across while trying to make it work. There is several reports
concerning this chip set here on launchpad, but it's still an issue, an
issue that should be an easy fix for maverick.

I'm running lucid (kernel 2.6.32-24 generic).

First of all the current driver in the kernel is old. The latest driver
(v2.4.0.1) can be downloaded here:
http://www.ralinktech.com/support.php?s=2

Second, the driver is not set up to allow WPA encryption by default.
This can be easily fixed by editing the two lines concerning this in the
file /os/linux/config.mk (in the downloaded driver folder) before
running make/make install. WPA is very common and should be activated by
default.

Third. My device is apparently recognized as another chip set, and
ubuntu loads the rt2800usb driver instead of the correct rt2870sta. I've
had to blacklist rt2800usb to make it load the right driver.

Fourth. My device is not included in the device list
(/common/rtusb_dev_id.c) for the new driver. The lsusb command gives
this information on my Gigabyte device: ID 1044:800c Chu Yuen Enterprise
Co., Ltd

Bug report #632187 concerns the same Gigabyte usb device on the same
kernel, but does not mention the blacklisting rt2800 issue. In my
experience the problem can not be solved without blacklisting the rt2800
driver.

A quick search here at launchpad indicates that there is other devices
missing in the device list as well.

In short by, blacklsiting the rt2800 driver, editing the device list and
activating WPA, i got it to work.

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

-- 
old and faulty rt2870sta
https://bugs.launchpad.net/bugs/638791
You received this bug notification because you are a member of Kernel Bugs, which is subscribed to linux in ubuntu.




More information about the kernel-bugs mailing list