Hello Daniel ! used
Daniel Hatfield schrieb:
This isn't a show stopper, but it is very frustrating.
After setting Suse 10 up on my laptop (I used to run 9.3 and yes it's a clean install), wireless configuration through Yast doesn't work. I know my settings are correct (I've rentered them several times). I know the module is correct, because all that I need to do is iwconfig and dhcpcd to get it working (I have to do it every time I boot). So, this is what happens:
If I run iwconfig after configuring yast it shows all the correct setting (essid, wep key, mode), but is says it's unassociated and that the security mode is restricted!? If i just run iwconfig with all of my settings from the CL and it connects right up. Connecting from the command line isn't the end of the world, but it is a digression.
I would soo love to get this working. Overall I love Suse 10, but if can't get this fixed I may be rolling back to 9.3.
It would be interesting to know the WLAN hardware used ...
What happens when you issue "/etc/init.d/network restart" (as user root) ?
Have you set up an additional LAN port ? If yes, did you enable "on
cable connect" for "device activation" in the section
[advanced]-[detailed settings] of the LAN port configuration ?
I had similar problems as I started with SuSE 9.3 on my notebook. Using
"on cable connect" for the LAN port helped to get the WLAN port running
more stable.
Never give up !
Best regards,
Reinhard.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]