RT2500 installieren-Fehler

Hallo erst, mal!
Hier erst mal meine Daten:
PIII 500Mhz, Ram knappe 200Mb, Graka GeForceMx4000, Festplatte 40Gb
BS Win XP SP1 , Suse Linux 10.0, KDE 3.4.2-b, Kernel 2.6.13-15-default,
Maschine i686, WLAN-Karte  54MbCoceptronic(tuxhardware)
Jetzt das Problem:den Treiber von http://rt2x00.serialmonkey.com/ habe ich runtergeladen, entpackt und will kompilieren, wechsele in das Verzeichnis
Module und gebe "./Configure" ein alles klar soweit keine Fehlermeldung dann gebe ich "make debug"ein (vorgehensweise laut tuxbeschreibung) und da gibts Probleme weiter gehts nicht.Versuch die Fehlerausgabe noch hier reinzustellen, war aber nicht viel, glaube er sagte das da noch was fehlt aber alle Devel-Pakete und Compilerwerkzeuge sind installiert.
Über eine genaue Beschreibung des Kompiliervorgangs wäre ich wirklich dankbar!

hier noch die Meldung als ich es das erste mal mit "make debug" versucht habe:
 Linux kernel source directory [/usr/src/linux-2.6.13-15-default]: make debug

./Configure: line 89: [: make: binary operator expected
  Linux kernel source directory : make debug

sed: kann make nicht lesen: Datei oder Verzeichnis nicht gefunden
sed: kann debug/Makefile nicht lesen: Datei oder Verzeichnis nicht gefunden
sed: kann make nicht lesen: Datei oder Verzeichnis nicht gefunden
sed: kann debug/Makefile nicht lesen: Datei oder Verzeichnis nicht gefunden
sed: kann make nicht lesen: Datei oder Verzeichnis nicht gefunden
sed: kann debug/Makefile nicht lesen: Datei oder Verzeichnis nicht gefunden
expr: Syntaxfehler
./Configure: line 111: [: -lt: unary operator expected
  Module install directory : /lib/modules/2.6.13-15-default/kernel/drivers/net

Hello Rechus,

If you still have trouble??
 
Installation instructions for SuSE Linux 10.0
Ralink Rt2500 Chipset Wlan-Card

Due to popular demand (seems like more people than I though read this HOWTO) I like to give a few instruction on how to build the driver from the rt2x00 Open Source Project on a SUSE Linux System (tested with SUSE Linux 10.0).
Prerequisits

First you need to make sure you have the kernel sources and the tools you need to build the module installed. The easiest way to do so is to start YaST, launch the Install and Remove Software, use the filter Selections and install Kernel Development and Experienced User. This will give you all the packages you need to build kernel modules. Don't forget to run YaST Online Update after the installation has finished. Otherwise the installed sources may not match your running kernel.
Preparing the kernel

Before we can build the driver we need to prepare the kernel source tree. It needs to match your running kernel. To do this issue the following commands as root:


 cd /usr/src/linux
 make cloneconfig
 make prepare

Getting the latest sources for the rt2500 module

As the driver is changing quickly, it's recommended to use the latest source code from the project CVS. As regular user do this:

 cd ~
 mkdir RT2500
 cd RT2500
 cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/rt2400 login
 cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/rt2400 co source

When asked for a password, just hit Return.

Note: Please make sure the path you keep the module sources does not contain a space character. I received quite a few reports of folks who had problems when a space was in the path. Compiling and installing the module

Again as user do:

 cd ~/RT2500/source/rt2500/Module
 make debug

To install the module you need to be root again:

 make debug install
 depmod -a

That's all there is to do. The driver is ready to use now.
Configuration

The rt2500 driver names the interface ra0. Unfortunatly this prevents it to be configured with SUSE's YaST. It still works with the standard rc-scripts though. All you need to do is to manually configure the device. This can be done by creating the file /etc/sysconfig/network/ifcfg-ra0. For a mini PCI card set up using dhcp I use the following file:

 #/etc/sysconfig/network/ifcfg-ra0
 BOOTPROTO='dhcp'
 MTU=
 REMOTE_IPADDR=
 STARTMODE='auto'
 USERCONTROL='no'
 WIRELESS='yes'
 WIRELESS_MODE='managed'
 WIRELESS_KEY='your-wep-key-here'

There are many more things that can be set. Look into ifcfg.template and wireless for well commented examples of the possible settings.

To test the driver you can use (as root):

 modprobe rt2500
 ifup ra0

The interface should come up and be configured as you specified it in ifcfg-ra0. Depending on the setting of STARTMODE it will initialize itself at bootime.

If you set STARTMODE to auto and add |ra[0-9] to LINKLOCAL_INTERFACES in the file /etc/sysconfig/network/config the inteface will be set up automatically at system boot time.
Links

    * The rt2x00 Open Source Project
      http://rt2x00.serialmonkey.com/wiki/index.php/Main_Page
    * Ralink Home Page
      http://www.ralinktech.com/home.asp

         
Good Luck