Hi there,
got another problem...
got wireless belkin pci card, rt2500 based so got native support straight out of box with suse 10.2. had it instaled with fedora 4 and ndiswrapper and was working like a charm.
got wireless netgear dg834gt router with dhcp switched on and wpa-psk encryption.
same machine under xp works fine, my girls laptop as well, just got problems under suse...

first:
had problems with knetworkmanager - hanged at 28% of progress while connecting... kept asking me for passkey... --- found that i shouldnt use it and it helped... - for a while...

second:
wierd thing is that it doesnt connect at startup.. i have to boot into xp, "warm up" my network card and then booted into suse usualy worked, until couple of hours ago...
i've noticed that it was loosing connection after couple of minutes downloadning stuff via ktorrent and never reconect, ifdown, ifup did nothing.. had to reboot into xp and again back.

so i thought it might be sth with router and dhcp settings...
decided to turn off dhcp and set adresses over my network manualy.
and its fine now - under windows only unfortunetly .....
so again i pressume that its all fine with router ...

how shall i set it up so it would stay that way?
connect at startup and reconnect on disconnection?


thanks in advance

Do you have the same problems with wpa disabled?

I'm having some problems with my rt2500 based usb adapter also. With SUSE 10.1, I was using ndiswrapper with the windows drivers from the cd and everything worked pretty well.

With openSUSE 10.2, my D-Link adapter was recognized and configured during the installation with the open source rt2500 driver. All I had to do was set up wpa encryption with my Linksys router and choose a password and I was able to connect.

Since the install, I have experienced some erratic behavior. At boot it only connects about half the time. Usually all I have to do is click on the icon in the tool bar and enter my password and then it connects. When it doesn't connect, it acts like it's trying to connect via ethernet, even though no cable is connected.

When I'm on line, the connection sometimes will fail and when I enter my password again, the connection stalls at 28%. Previously, the only way I was able to reconnect was to reboot. But I found that if I removed the usb adapter and plugged it back in I could then enter my password and reconnect.

I have also had problems with knetworkmanager quitting for no reason. Then there's no way to reconnect because no networks are listed. I have a work around for this also. Open a terminal and become root. Use the command: rcnetwork restart

The network will restart and also restart knetworkmanager. All I have to do is select my network and enter the password. All in all, it's kind of buggy but I'm not sure if the problem is with knetworkmanager or with the rt2500 module.

HTH

i've tried to launch it with no wpa and dhcp - doesnt work... didnt try with dhcp on couse have to go now... be back later and will give it a go.

thx for replys

Hi,
got some more info that might help:

when dhcp is on ifup gives msg:

wlan0 device: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01)
wlan0 configuration: wlan-id-00:11:50:8e:a8:00
wlan0 warning: WPA configured but may be unsupported
wlan0 warning: by this device
wlan0 starting wpa_supplicant
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - Starting DHCP Client Daemon on wlan0... . . . . . no IP address yet... backgrounding.



and when its off it sais:

wlan0 device: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01)
wlan0 configuration: wlan-id-00:11:50:8e:a8:00
wlan0 warning: WPA configured but may be unsupported
wlan0 warning: by this device
wlan0 starting wpa_supplicant
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
SuSEfirewall2: batch committing...
SuSEfirewall2: Firewall rules successfully set


and when i set it manualy then in properties of network connection i can see one wierd adress - broadcasting: 192.168.0.255 - dont know what it its - but i didnt put it anywhere.

the RT2500 driver is buggy as heck in opensuse 10.2.
I have this installed on my Desktop

first go into Yast
Yast -> Network Devices -> Network Card
select traditional method

highlight the rt2500, and select EDIT
then goto advanced -> hardware Details
the name there should read rt2500pci - or something like that. Copy this name down - you need it for below.

1) edit /etc/modprobe.d/blacklist
2) in blacklist add this
# blacklist default rt2500 driver
blacklist rt2500pci
3) download the serialmonkey drivers

http://rt2x00.serialmonkey.com/wiki/...itle=Downloads
download the latest CVS tar ball

I downloaded it to my users home directory, download wherever you wish
4) un tar the file and go into
~/rt2500-cvs-2006122016/Module
as root . . .
make
make install -m
5) go back to Yast and delete the entry
6) reset up the connection (at boot, your network, your settings, etc . . ) and use "rt2500" instead of "rt2500pci", as it was origionally.
as the module to load

7) reboot to make sure it works

this worked for me, you may need just to fuss with it a bit depending on the network you are signing on to.

I had to do this with my broadcomm driver as well, I just used ndiswrapper instead of the serialmonkey drivers.

still didnt work..
got same errors as posted above..

only thing that changed is that when configured without dhcp it managed to recive couple packets (lets say 20 in 3 min, but also indicated 20 colisions) and displays speed of connection with router. <-- on default drivers it didnt recive anything.

but still wierd is adress in broadcast field - 192.168.0.255 - thats wrong i guess.
router is 192.168.0.1 so gateway is same and dns is the same... where did it came from ?

sorry, wish it did help.

The only other trick I have up my sleeve is to go back into YAST and under the advanced tab for the card is to disable IPv6.

again, that did work on this desktop with an rt2500 chipset wireless PCI, so after this little trick - I am not sure.

Just some stupid checks I cought myself doing wrong. . . best i can think of at the moment
the card is selected wireless and not ethernet?
( Suse at first sets the card as ethernet, don't ask me why . . it is stupid)
it is traditional method with ifup
you have a host name, and domain name is blank
module name is rt2500 for the serial monkey drivers
IPv6 is disabled
DHCP Host Name to Send is Auto

Also just make sure rt2500pci is blacklisted. First time I edited it for some odd reason why it did not save with kate ( I run KDE ). That caused alot of problems. So I just re did make, make install, make install -m the serial monkey drivers, and re set to load the rt2500 ( not rt2500pci) in Yast. This is the point where my wife noticed it read ethernet, and not wireless. So I deleted the card, and just re-set it up. Rebooted and all was well.

Other than that I would say search serialmonkey forums.
those drivers have been around for a long time, and there is a good community surrounding them.

Network controller: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01) <--- Mine

double checked everything again and seems like all is fine...

i've reserved first 6 ip adresess on router so i can set it up manualy (i'd prefer to have constant ip over lan). network status sais that its connected and even recives some packet from time to time but still no network access....

dont know what else to do...

i just found that i cant even find /etc/network/interfaces file anywhere... is that matter of suse it self or its just some error on my system?
same with /etc/wpa_supplicant.conf ....

also noticed:
iwconfig shows that im "connected" to some other network even tho i did set via yast to connect to my router.

help me pls

ok,
i found that is definetly problem of wpa_supplicant ... it doest seems to see my card but tries to connect with wlan1 and theres no such a device! my card is wlan0 and works perfectly without wpa enabled on ap.
how do i make wpa_supplicant use wlan0 instead??

which file should i edit, to change its config coz it seems like no matter what i set in yast it wont change wpa_supplicant settings.