RT61 WLAN for Caros Medion Notebook with openSuse 10.3
HOW I made the RT61 WLAN Chip work on openSuse 10.3
The problem
The first impression, when installing openSuse on the new Medion notebook (mid november 2007) was: Great! Everything works just fine! But as soon as I unplugged the wired network (it is 1GBit not 100Mbit as advertised!), I realized, the WLAN is not working :-(
Firmware needed
I discovered, that the Chip used is an RT61 from RaLink and that openSuse has automatically installed the open source driver for this chip. This driver needs a firmware in /lib/firmware that I downloaded from the RaLink page. Later I discovered, that the tarballs from the open source driver project page come with firmware files, too. I did not check, if they are the same.
WLAN config not stable
After installing the firmware, I could setup the WLAN for WEP access with yast for NetworkManager as usual. Unfortunately it did not work. The card was set up, it found the access point, had the WEP key set, but could not contact the dhcp server.
After much fiddling, I discovered, that it helps, if I set the key again with iwconfig, after NetworkManager has done its setup. But this was not for long. The settings get lost quite often for no obvious reason.
Newest suse kernel and module dont help
I then did an online update and got a new kernel with a new RT61 module. Nothing changed :-(
Open source driver 2x00 does not compile
Then I tried to install the newest tarball of the 2x00 open source driver (after uninstalling the suse rt61 rpm). It did not compile, which was no big surprise, since it claims to need at least kernel 2.6.24. OpenSuse 10.3 has 2.6.22 - too bad.
Newest open source legacy rt61 driver has same symptom as suse provided driver
Next I tried the legacy RT61 open source driver tarball. Installing was a smooth ride. You need the kernel sources and kernel development packages installed (which I have always installed, anyways). Apart from that it was just the usual untar, make, sudo make install. But it was still not working. Same symptoms. I could set up the card with iwconfig, ip addr and ip route and it sometimes worked for a short period of time - so I can be sure that it is not a configuration problem.
Google did not help here
Of course, I had googled quite a lot about this until now but found only unresolved threads in the mailing list of the open source driver and some forums. So I nearly gave up and was ready to try an USB stick. At least I knew, I am not alone with this problem.
Use old RALink driver
As a last shot, I then downloaded the driver directly provided by RaLink. It has an unusual, nonstandard way of getting configured and from what I read until then, I got the impression that it is even more legacy than the legacy open source driver. So I did not try earlier. Maybe I should have: In the end it did work quite well!
I downloaded the tar, untared, did a make and got a compiler error. Fortunately it was easy enough to fix: just a text replacement for a deprecated module init function. After that, I did set it up, like described in the RaLink README, which involved copying the firmware to /etc/Wireless/... and setting all the parameters in the coniguration file there (Ssid, WEP key, ....). Konfiguration with yast was not possible, since this method is not standard at all! At last, I created the network config file in /etc/sysconfig/network (ifcfg-ra0) to tell suses startup script to get me an ip and disabled the network manager (use old style ipup instead) so it cannot interfere (precaution, since I dont know how NetworkManager works internally).
That was it!
Now the notebook can connect via WLAN - fully automatic.
Next steps
Next step will be enabling WPA and better cooperation with the wired lan. But this has quite low priority and will probably never happen...