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.

Thanks,
Daniel

The way you set it up for 10.0 should be basically the same as you did for 9.3. You might just need to tell your card to come up on boot. See here http://www.angelfire.com/linux/hardw...ttodonext.html and skip to number 4. See if that helps.

Agentvenom,

Thanks, but that is how I set it up. If fact, I reset it up many times. I'm entering all the same information into Yast that I enter usign iwconfig, but the results are what I mentioned above.

Thanks for trying to help.

Daniel

Hi I used to have the same problems with all my PC's which I installed Suse 10 on, but then I tried to make a new install with ACPI disabled, and now it seams to work on all computers all wireless network cards are up at boot. If you are using a 64bit computer then it will not work with ACPI disabled.

hmm... I would rather keep using iwconfig to bring them vs. disabling ACPI on my laptop.

Thanks for the advice though.

Daniel

My Compaq M2000 works 100% perfect with ACPI enabled on the build in wireless.

zenix,
I had a similar problem. Use KWiFiManager, select 'settings' then select 'configuration editor' and put your card settings in there. ie Network Name, Operation Mode, Encryption etc.

Make sure you select the check box 'Execute script on connect' and enter 'dhcpcd wlan0' -or- 'dhcpcd your_device'.

Using this method, each time you re-boot your machine, you will have to start KWiFiManager, select 'settings' 'configuration editor' select your configuration i.e. configuration 1 and hit the 'activate' button.

It is cruder than just having the WiFi load on boot, but it works. What does not work on my system yet is selecting the box 'Load preset configuration on startup'. There must be a permission problem.

I had a similar problem with my laptop and was going nutz... long story short, I started Gnome (I'm a KDE/XFCE user) and started to fool around with some of the network/wifi widgets there, and low and behold, next time I rebooted and went into KDE my wifi was working properly.

Go figure.... oh, and sorry, don't remember the exact Gnome 'widget' ....