https://bugzilla.novell.com/show_bug.cgi?id=235251#c11 --- Comment #11 from Dieter Jurzitza <dieter.jurzitza@t-online.de> 2007-07-25 08:01:42 MST --- Dear Michal, 1.) sorry for the German, just didn't think about it. 2.) please find the file "hwconfig-netcard" attached. Howerver, there are two different issues we are looking at. The rt61pci / rt2500pci drivers that come with the wlan-kmp-default rpm exhibit stability issues and they do not provide WPA PSK. Therefore I switched to the legacy rt61 / rt2500 drivers, but the drivers as such are _not_ what I am discussing in this bug report (only for clarification) a.) the card 19: PCI 0b.0: 0200 Ethernet controller is a WLAN card and should be detected as such. "Features" says "WLAN" so I do not understand why it is said to be an Ethernet card - but maybe you have more insight into this. This may be a hwinfo issue. b.) as I readily said, original SUSE does not support WPA-PSK for these cards because SUSE only supports cards that can be handled by wpa-supplicant. This is acceptable as the new rt2x - releases to come will provide the appropriate interface. But this is not the point. When configuring traditional with yast2 as depicted in the jpegs it is not sure whether or not you can access the WPA-PSK dialogue for the cards. Usually you cannot access it for the first time, so you choose "Common Key" (WEP) as the first step. Then you save configuration, restart yast2 a second time. If you configure the card again, voila, you can choose WPA settings. The reason behind my points here is that it does not take more than a 10 liner patch to ifup-wireless to allow the configuration of WPA-PSK to both rt61.ko and rt2500.ko from within yast2 - if only yast2 would open the corresponding setting options. This is what I have been referring to in my initial Bug - hope I could clarify now. Thank you for taking care! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.