Hi Jim, Thanks for all the good ifnormation! I will certainly try it out... A couple of clarifications though before I do so: 1. The Suse support URL talks about problems with Suse 7.0 which was broke with the tulip driver. I know 7.1 "works" because the first time a fresh Suse instal is made the Linksys driver is properly configured so I am not sure if 7.1 has a driver problem or an installation problem, Yast2 or otherwise. 2. The fixes seem to be geared for Suse 7.0 and I was wondering if they would apply to 7.1 as well. Thanks again for your input! Babu --- James Bliss wrote:

You should go to this page: http://www.scyld.com/network/tulip-devel.html or go to: ftp://ftp.suse.com/pub/people/snbarth/new-tulip.tar This is from the SuSE support database. It states that the tulip drive in 7.0 does not work. Also, the SuSE page for installing this is:

http://sdb.suse.de/en/sdb/html/ashley_linksys-tulip.html

This should work. I had the same problem when I used 7.0 (using 7.2 now) and this got it working just fine.

Good luck.

Jim

11/14/01 02:04:30 PM, babu walad wrote:

...

Folks,

A feek or so ago I posted that my modules.conf has disappeared during Yast2 installation, and this group correctly diagnosed the problem as a bug in Yast2 when one has custom partitions for Linux, as I do.

The tricky part was "downloading" the Yast2 patch when Yast2 was unable to configure your NIC card...

Well, I eventually did "download" and install the y2base RPM with no errors (at least I didn't see any output).

Problem is it does suceed in saving the modules.conf file but it FAILS to configure my NIC card. I have a Linksys NIC which used the "tulip" linux driver.

I have repeated this process half a dozen times or more. Here is what happens:

1. If I install into a defaul partitioning, everything works great. NIC and Sound are configured and saved correctly.

2. If I install into a custom partition using original or patched yast2, it fails to save the modules.conf file, which ends up as modules.conf-, but the NIC card works perfectly! Once I reboot my machine, the NIC goes to hell. Can never reconfigur it!

3. Last attempt was, install Suse 7.1 afresh without configuring NIC and Sound. Quit Yast2 and install Yast2 patch. Restart Yast2 and configure NIC. Does not work. It always says could not get DHCP IP address, card not functioning correctly. When I reboot into windows, NIC card is functional so it is not a hardware problem.

Here is my modules.conf without configuring NIC. After it is a copy of modules.conf after running patched yast2 to configure my NIC. You will notice it just adds a comment that it is configuring the network card but in fact it does nothing!!

Is there a way to manually configure the NIC? This is getting very annoying and wasteful. Help!!

Thanks for everyone's help!!

Babu

__________________________________________________ Do You Yahoo!? Find the one for you at Yahoo! Personals http://personals.yahoo.com

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com

__________________________________________________ Do You Yahoo!? Find the one for you at Yahoo! Personals http://personals.yahoo.com