This post here

solved my problem, and unlike the original poster, I don't have any need to edit anything or run yast after each reboot.

Thanks biotek1! That solved the dns issue. Now, Mono, did you change the load order as suggested in the text below? I am having the issue where I have to go into Yast each time I restart.

------------------
Just log in as root, or open the File Manager - Super User, and browse to /etc/rc.d. Two folders will need to be addressed--"rc3.d" and "rc5.d". There you will find services starting with "k" and "s". The "k" items are for shutdown and you can ignore them. Go to the "s" items and simply assign a number to the network service that is higher than the pcmcia (and in my case I did the hotplugging also, but I'm not sure that it is necessary). What I mean to say is simply rename the network file so that the number is higher than the others. That way the netword card will be detected prior to the network and therefore be configured.
------------------

Ok guys. After re-installing the driverloader software, then implementing the two suggestions below from previous postings, everything works! And, I don't have to go into Yast after each reboot.

**************
this is a comon problem when using DHCP with SuSE 9. Verify your interface's
configuration (/etc/sysconfig/network/ifcfg-...) to make sure you have the
following parameters.

DHCLIENT_MODIFY_RESOLV_CONF='yes'
DHCLIENT_SET_DEFAULT_ROUTE='yes'
**************

------------------
Just log in as root, or open the File Manager - Super User, and browse to /etc/rc.d. Two folders will need to be addressed--"rc3.d" and "rc5.d". There you will find services starting with "k" and "s". The "k" items are for shutdown and you can ignore them. Go to the "s" items and simply assign a number to the network service that is higher than the pcmcia (and in my case I did the hotplugging also, but I'm not sure that it is necessary). What I mean to say is simply rename the network file so that the number is higher than the others. That way the netword card will be detected prior to the network and therefore be configured.
------------------

Hi guys, i changed the order in which the services loaded up , and yes I no longer need to load up YAST each time. GREAT!!!!

thanks to all for their input in solving this rather important issue.

I think SuSE really needs to look at this issue closely and do something , or at least post a bulletin in regards to a fix so that others like us can find a quicker resolution.

i for one think i will purchase this software from linuxant, who afterall have been very helpful in solving this issue. also its great to have a forum like this to share our experiences and get results !!!!!!!

thanks again.

Beware. If you start up the firewall in SuSE 9.0, the load order will be reset. You will need to re-configure using the steps below.

------------------
Just log in as root, or open the File Manager - Super User, and browse to /etc/rc.d. Two folders will need to be addressed--"rc3.d" and "rc5.d". There you will find services starting with "k" and "s". The "k" items are for shutdown and you can ignore them. Go to the "s" items and simply assign a number to the network service that is higher than the pcmcia (and in my case I did the hotplugging also, but I'm not sure that it is necessary). What I mean to say is simply rename the network file so that the number is higher than the others. That way the netword card will be detected prior to the network and therefore be configured.
------------------

Ok, I too am a SuSE 9 user and I too had wireless issues. First, I was running ver 8.2 and it didn't see the card by default, but 9.0 does. I just configured it with the drivers it provided (Linksys WPC11 v.3) and did the following and believe it or not, it works..im on it right now!!!!!!

**************
this is a comon problem when using DHCP with SuSE 9. Verify your interface's
configuration (/etc/sysconfig/network/ifcfg-...) to make sure you have the
following parameters.

DHCLIENT_MODIFY_RESOLV_CONF='yes'
DHCLIENT_SET_DEFAULT_ROUTE='yes'
**************

------------------
Just log in as root, or open the File Manager - Super User, and browse to /etc/rc.d. Two folders will need to be addressed--"rc3.d" and "rc5.d". There you will find services starting with "k" and "s". The "k" items are for shutdown and you can ignore them. Go to the "s" items and simply assign a number to the network service that is higher than the pcmcia (and in my case I did the hotplugging also, but I'm not sure that it is necessary). What I mean to say is simply rename the network file so that the number is higher than the others. That way the netword card will be detected prior to the network and therefore be configured.
------------------

Spoke too soon...drat! Still flakey...it does one service or the other...Internet or local browsing, it won't do both at the same time..... If/When I can browse my local network, no Internet and vice versa.

I believe we were all having issues with the Linksys wpc54g. You might try www.linuxant.com to see if their driverloader software works with the wpc11. My wpc54g has been quite stable using driverloader.

Ok, aint this a pip..i got the wireless card working great with the Internet, but it WILL NOT browse my LAN....WTF??? When I plug the eth0 in, all samba shares avaiable, wireless..nadda...???????? UGH! Any ideas?

Hi there

I have the same problem with a LG card texas instrument chipset. Did you fix that?