Tulip driver

[mstich]

Hey, I just got a new nic that uses the tulip driver (Linksys). I followed the instructions in the NHF to compile the driver but much to my disappointment, there is an error. And I don't quite understand what is the matter. There is an error about "modversion.h", and it says it can not find some files. I am using the exact command that the NHF tells me to compile with.

[spacial_K]

I think I might have the same NIC. If I remember correctly, the drive that came on the disk was really old (2.0.04 old). Did you try compiling the tulip driver directly into the kernel? Once I did this it worked just fine. I suppose it's worth a shot.

Hope this helps.

[PLBlaze]

You seem to be missing your kernel source which includes modversions.h file (module version).Get latest kernel unpack it to /usr/src/linux and do make dep to set the dependencies and try building the tulip driver again.Hope this helps.

[mstich]

This is really pissing me off, no matter what I try it won't compile. I guess I'll try compiling it into the kernel.

[AntV]

I have been having the same problem but it seems to be an incompatibility with Red Hat..if you go to their site and check out the hardware compatibilties it says some things about this. There is also a link to the Linksys page and if you do a search there about linux drivers it says that there are updated tulip drivers, you can download them and supposedly compile and use these new modules. I have not yet tried it because of me linux newbieeness I do not yet know how to compile. Let me know if oyu can get this process to work.
Anthony :confused:

[sans-hubris]

The Linux kernel (I think beginning with 2.0.x) has support for this, and it's probably better than the source code you were given. I got mine working very easily by either compiling the module seperately or compiling it into the kernel, but of course you need the kernel source.

[ 03 February 2001: Message edited by: ndogg ]

[mstich]

I'm not running redhat, I'm running slackware

[sans-hubris]

I'm running Debian, what's your point?

[tnordloh]

Look at the end of your tulip.c file, it should include the line you need to use to compile it in comments.

[cool215]

I got the exacly same problem and I'm running Madrake 7.1.

I followed the instructions I got on the disk that came with the card. The drivers compiled succesfully but when I try to to
"ifup eth0" It came up that the device does not exist. But if I do "ifconfig -a" eth0 is thers.

[skweegie]

heyas mstich,

since you're using slack, i was just wondering why did you decide to compile the tulip module? if you did a default slack install, you most likely installed netmods.tgz which has most NIC modules already, in this case, the tulip driver.

1) when you ran netconfig, it didn't autoprobe the NIC as a tulip card?

2) if you didn't use netconfig to set up your network, did you try to (as root):

:# /sbin/modprobe tulip

3) lastly, if you did install the default kernel source during the slack install, you can verify that the tulip driver included with slack is current enough by doing:

:# grep "static const char version" /usr/src/linux/drivers/net/tulip.c

lemme know how it goes...

cheers

[mstich]

Originally posted by skweegie:
heyas mstich,

since you're using slack, i was just wondering why did you decide to compile the tulip module? if you did a default slack install, you most likely installed netmods.tgz which has most NIC modules already, in this case, the tulip driver.

1) when you ran netconfig, it didn't autoprobe the NIC as a tulip card?

2) if you didn't use netconfig to set up your network, did you try to (as root):

:# /sbin/modprobe tulip

3) lastly, if you did install the default kernel source during the slack install, you can verify that the tulip driver included with slack is current enough by doing:

:# grep "static const char version" /usr/src/linux/drivers/net/tulip.c

lemme know how it goes...

cheers

The stock tulip module doesn't seem to work, it says something about device being in use or something like that. While I was reading some instructions on compiling the driver, they all said that this was common and to get the newest source from the linksys website.

I'll try those other options though. Thanks.

[jbstew32]

I have Slackware with the 2.4 kernel with the Linksys NIC (tulip driver). I compiled the driver as a module when I compiled the new kernel, and all i did was insmod it and it worked. No pain or anything. It was all good and now I have DSL in Linux :)

[jbstew32]

By the way, the NHF isnt worth following if you are running Slack.....besides, the driver they give you is a POS anyway. I could never get it working. The one built into the kernel seems to be much better.

[mstich]

Woohoo! I'm finally up and running. I compiled 2.4.1 with the included tulip driver and now everything works. Thanks for everyone's input.

[jbstew32]

great news indeed.....if all else fails...upgrade your kernel (unless you have the latest) :D

[atray]

My brother and I also had this problem with Drake 7.2.
This is the link to the page whose instructions fixed the problem.

Hope this helps
http://www.scyld.com/network/tulip.html