[Bug 34902] Re: Ralink Wireless legacy drivers (rt2500 rt61 rt73 rt2570) USB/PCMCIA/PCI hangs PC

[marvstod]

With a Linux desktop under Feisty, rt2500.ko served and the channel
was automated ra0
Under Gutsy, rt2500pci  proved to be functional and the channel was
automated wlan0
During testing, it is a good practice to first unload all of  rt2500
rt2500pci rt61 rt73 rt2570:
$ sudo ifdown wlan0
$ sudo ifconfig wlan0 down
$ sudo modprobe -r CurrentTestDriver

Then test each one with
$ sudo modprobe TestDriver
Check auto actions with:
$ ifconfig
$ iwconfig
Even if the iwconfig default is wrong, at this point a first
functionality test can be done with:
$ iwlist wlan0 scan
You wireless router should be represented in the output.
If there are other neighboring stations with the same Address, this
can be a complication

Do
$ iwconfig --help
and
$ man iwconfig
to see how to do manually settings.
$ iwconfig
will display the default settings
You may need to do changes/choices with:
$ sudo iwconfig wlan0  essid  YourRouterESSID
$ sudo iwconfig wlan0  ap  WirelessStationAddress
Make sure the changes are set with:
$ iwconfig

$ sudo ifdown wlan0
just to clean any old stuff.
Check for compatibility of your settings with those in  /etc/network/interfaces
Then hopefully your wireless router will pickup to:
$ sudo ifup wlan0

If it fails, try the next alternate driver.

MarvS
because the default setis sometimes wrong

On 10/19/07, sefs <sefsinc at yahoo.com> wrote:
> I am wondering how one can go from a perfectly working serialmonkey set
> up in feisty to a totally broken (read hard lock) in gutsy ... what in
> the world is going on here devs.  Talk to us and give us some good news
> about this being fixed.
>
> --
> Ralink Wireless legacy drivers (rt2500 rt61 rt73 rt2570) USB/PCMCIA/PCI hangs PC
> https://bugs.launchpad.net/bugs/34902
> You received this bug notification because you are a direct subscriber
> of the bug.
>

-- 
Ralink Wireless legacy drivers (rt2500 rt61 rt73 rt2570) USB/PCMCIA/PCI hangs PC
https://bugs.launchpad.net/bugs/34902
You received this bug notification because you are a member of Kernel
Bugs, which is a direct subscriber.