Here is the read me file >> http://linux.ucla.edu/pipermail/linu...ne/005441.html

----------

I have ran thru all of this and seemed like I did everything right, but I am still not able to get it working. When running /etc/rc.d/rc.modules I get the following errors.

pci-scan.o Command not found
tulip.o Command not found

Do i need to put like /sbin/modprobe before the pci-scan.o and the tulip.o ??

Also at bootup i get a depmod error. Anyone have any ideas?

TIA!!

PS: I just tried it again the "insmod tulip.o" and I get the following errors.

tulip.o: unresolved symbol _global_cli
tulip.o: unresolved symbol _global_save_flags
tulip.o: unresolved symbol _global_restore_flags

gotta download the hermes.config and put into ur pcmcia directory. Do a search on linksys and u should find the answer that u need.

This is a PCI network card, not pcmcia. Does this still apply?

Sorry...I was thinkin' laptop, I think this might be ur problem I did a search and found this...this is quoted from one of finegans post helping another linux user with his linksys pci

Try: modprobe tulip.o
If that errors out, you're going to need to get fresher source and compile a new module.

To get it to compile, download all 4 of the files from the Scyld site that ssu4716 pinted out: pci-scan.c, pci-scan.h, kern_compat.h and tulip.c To find out what line to type to compile them, try :
tail pci-scan.c

after you type in the compile command, you should have a module called pci-scan.o. repeat this for tulip.c in order to get tulip.o. Then:

modprobe /directory_that_you_are_in/pci-scan.o
modprobe /directory_that_you_are_in/tulip.o

Then try ifconfig eth0 up to see if the card works. Honestly, if you can't get the module to just pop right in, it might not be worth fiddling with.

Ohhh...I forgot the Scyld site he is talkin bout is here:
www.scyld.com/network/tulip.html

Awesome thanks. Let me go through all that and I'll let you know what happens!

Thanks again!

I dont see the new tulip.c file on that site to update.

Am I missing it somewhere.

I believe if u download the rpm source it would be in that source package.

Anyway I also searched alittle harder than before and also found this very helpful link...linksys.com has a linux support website.


http://www.linksys.com/support/support.asp?spid=26

Geez, I have tried everything lol. And i still get those errors on the tulip.o file.

Any other suggestions?

The problem of rc.modules modprobe not finding the tulip.o module on boot comes from the fact that from the 2.2.x kernel series (when that how to was written, to the 2.4.x series (I guess you are running 2.4.5, check it with uname -r), the kernel modules were moved around the /lib/modules tree. Offhand, you probably didn't need to compile your own tulip source as it came with 2.4.5, and its probably a lot newer than what Becker still has up there over at Scyld.

Old (according to the how-to)

/lib/modules/2.2.19/net/tulip.o.gz

New (where modprobe is looking now)

/lib/modules/2.4.5/kernel/drivers/net/tulip/tulip.o.gz

If you compiled the tulip code on your own... you've probably replaced the modules that came with Slackware 8.0 with Ollllllllld source for the 2.2.x kernel series. I've got 7 of these cards and they're all running, and I've only had to compile them for Slack 7.1, which is as nearly old as the Mandy 7.2 which that how-to was written for. If you are still running the base kernel that came with Slackware 8.0 I can email you the right kernel modules as attachments. First off though, whch kernel 2.4.5 or 2.2.19?

Cheers,

Finegan

Thanks for helpin out fin....you just saved me from doin a whole lot of homework to figure out his problem

I am running the 2.2.19 kernel. But by the time you posted this, I threw in a D-Link card and got it to work in like 10 seconds. I had such a hard time with this Linksys card I wanted to try another. I really appreciate you guys helping me with this. Could the card have been bad? Maybe that's why it was so hard for me to get it going? Since I did all the instruction correctly and also read alot more posts/articles about my problem. Anyways, thanx again for the awesome support

I have one of these and it works fine in my PIII system but not at all in my old Pentium 166 system.

Ya, this system is a 300 AMD K6 ...

The Linksys cards, or more to the point, the DEC tulip chipset they run off of is one of the most cloned and open chipsets on the planet. It also works rather well, is cheap, and reliable, so that's why so many companies produce cards using it. With this comes the fact that they put in minor revisions, which have caused the tulip source code to balloon to 4 times the size of most network drivers just to take into account the idiosyncracies of 100 flavors of tulip. Linksys makes some rev every time they re-batch their ne100s, so you can pick up 3 on the same shelf at CompUSA, take them home, put them all in the same machine and 1 won't work. The card is fine, its just a little tiny bit different than the two next to it.

This is annoying, which is why I like to pick up $5 used 3Coms from a bin at my local used kit store, but when its empty I just buy an el cheapo linksys card.

Cheers,

Finegan