Comment 134 for bug 34902

My system is a AMD dual core 32 bit bridge System with PCI rt2500 hardware.
Under Feisty, the wireless was fine using the rt2500 driver
the /etc/network/interfaces stanza is:
# auto ra0
iface ra0 inet dhcp
wireless-essid MyVerizonNetRouter
wireless-key 64bit_key
wireless-ap StationAddress

After performance was reliable I enabled
auto ra0
and with bootup I am usually online

Just installed Gutsy on a spare partition.
The System auto named the wireless wlan0, so I made ra0 --> wlan0
changes to the stanza above. Upon initial bootup ifconfig had both
wlan0 and wmaster0 blocks in addition to the standard lo
I could not connect to the wireless router.

To watch kernel messages, I set:
  tail /var/log/messages &

Went through numerous trials without acquiring the wireless router,
alternately using ndiswrapper, rt2500 and rt2500pci drivers.
With each failed trial I would:
ifdown wlan0
ifconfig wlan0 down
which cleared the ifconfig blocks except lo . Unloaded
modprobe -r Driver

Then restart:
modprobe Next_Driver
because the auto setup was wrong for reasons obscure
ifdown wlan0
ifconfig wlan0 down
ifup wlan0
which usually failed to get a station offer.

With all three drivers, there was a cogent report from:
iwlist wlan0 scan
though there were following failures with:
ifup wlan0

Finally a trial worked using the rt2500pci driver,
For reasons still obscure. And there is in progress an
apt-get update

Major point, if is worth going through trial like the above several times.

MarvS

On 10/6/07, Kyle Weller <email address hidden> wrote:
> btw, I am running Gutsy Beta, Latest Updates, and I had tried to blacklist all ralink drivers as well as leaving them all allone, still not working, I get wmaster0 and wlan0 in iwconfig and my configuration is fine when using drivers from serialmonkey,
> STILL DOES NOT WORK OUT OF THE BOX
> Any fix would be greatly appreciated
>
> --
> 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.
>