I recently found a Linksys WUSB11 USB Wireless network card and decided that I wanted it to work with a linux box I had sitting around. After not too much trouble, Yast informed me that I needed the atmel-firmware drivers... got them no problem. But I am still having some problems. I have been able to get the card "half-working" I guess you could say.

I configured the card through Yast and set up my ESSID and all my network settings. When I exit Yast it does save it to a configuration file in /etc/sysconfig/network with all of the correct data but it does not set the correct ESSID to the card. I have to manually run iwconfig wlan0 essid MyAP and then ifdown wlan0 | ifup wlan0 to get the card working correctly.

Has anyone else had any experiences like this?
Is there anyway that I can get the card to correctly set itself up on boot?

Thanks,
-paco

Try this: http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/

It may help

Yes, I have a WUSB11 v2.6 and have had the same exact problem. I would have to manually restart it too.

Thanks for the reply. After reading through some of the Atmel stuff that was included in your link I found that when I edit my /etc/sysconfig/network/wireless to include WIRELESS_ESSID="MyAP" then it will correctly configure the access point when I boot the machine. However it still tells me that "wlan0 Interface could not be set up" during the boot process but by the time I log in it connects to the access point and is assigned an IP address and works fine.

So I guess that the bottom line is that configuring the ifcfg-wlan-wlan0 file (either manually or through Yast) does not work and you must manually configure your wireless file instead. During boot the initialization of wlan0 will fail, but it will be assigned an IP address and work correctly in the end.

Thanks for the help,
-paco

After believing that the change to my wireless file fixed the issue... it doesn't work at boot any longer. I'm not exactly sure what happened. I am rereading the stuff that cucolin linked and I think I will probably just end up writing a boot script that runs iwconfig with the correct essid.

-paco