[martin92]

Good heavens, I hadn't thought about that!

Attached you will now find the settings displayed when I log in as root, because of some reason the language is still english in that case.
But in the meantime I got another thought coming: Could it be wrong that I unpacked the tarball with the driver in a subdirectory of /home? Where would you place it?

Best regards, Martin

[waterhead]

By driver do you mean the rt73.bin firmware file? That should make no difference, as long as you put it in the /lib/firmware folder. I still think that the dmesg command should say something about the wireless. For my Broadcom wireless I get this, concerning the firmware.

b43-phy0 debug: Loading firmware version 410.2160 (2007-05-26 15:32:10

To see the output one page at a time, use this:

dmesg | less

Use enter for next line, or page down for next page.

To see what all network cards are doing, use this command:

ifconfig

For wireless information, use this command:

iwconfig

You may want to try using the traditional ifup/ifdown method for activating the card. This is usually done in YaST, where the cards are configured. You would then use ifup to start the card, and iwconfig to send it configuration data, like this

iwconfig ra0 essid dlink

This would set the essid name of the connection. To see all of the options, use the help command:

iwconfig --help

Play around with it this way and see if you can get anything to work. After making a change, use the iwconfig command without options to see if the change took effect. You may want to stop and restart the card after any changes.

ifdown ra0
ifup ra0

[martin92]

Hello, Paul.

I didn't mean the bin file, but a tarball called
rt2x00.serialmonkey.com/rt73-cvs-daily.tar.gz
which includes a detailed readme file. As I looked it up right now, I saw that the rt73.bin file was also part of it. So that was installed anyway.
A Debian user directed me to this address, but couldn't tell me about the specialities of SuSE. He thought that all that was missing was a correct configuration.
He uses the same USB WLAN device, but with a laptop that is probably better prepared for such tasks.

In the meantime, I will try to look after dmesg and iwconfig, now that the bin file is installed.

Best regards, Martin

[waterhead]

When you compile the driver, you run the "make" command as a regular user. You then run the "make install" as root (superuser). It doesn't make any difference where the source files are .

It's not a bad idea to install the latest version of the driver. It may be just what you need.

Read through the README file that came with the latest driver. It has a lot of info on configuring the wireless. Specifically the iwpriv command

[martin92]

Hello, Paul.

I was disconnected for a while, obviously because of problem of my provider. In the meantime, I tried iwconfg and got the answer that there were no wireless device at all. As the WLAN stick was recognised during the installation (New hardware found" etc.) it seems to be a problem that occured after the first restart. Where would you place a WLAN driver? Momentarily, it's still i a subdirectory of my home folder, while the firmware has itself installed in /lib/firmware.

Best regards, Martin

[waterhead]

If you ran the "make" and "make install" commands mentioned earlier, then it should be installed.

You could try unloading and reloading the driver module (as root):

modprobe -r rt73
modprobe rt73

Post the output of this command:

lsmod

And this command:

lsusb