Good question.

No, one is the linksys and the other is an el cheapo $10 special which uses
the ne2k-pci module. So I don't know if 2 linksys cards at once will have
problems or not.

I found a tulip driver list at http://www.scyld.com/mailman/listinfo/tulip.
you could check the archive.

Gavin

on 9/3/00 7:33 PM, Sridhar G  wrote:

> Gavin,
> 
> BTW, are both the cards linksys cards. I am planning to install another
> linksys card.
> 
> Cheers
> Sridhar
> 
> ----- Original Message -----
> From: "Gavin Clark" <[EMAIL PROTECTED]>
> 
>> I did manage to get it working. Here's the story:
>> 
>> The linksys etherfast 10/100 has multiple models, each with a different
> chip
>> set. I have version 4 which is not supported in the current release of the
>> tulip driver. if yours works out of the box it's probably version 2.
>> 
>> the solution:
>> 
>> Get the new tulip.c source file (and some other files which you need to
> get
>> it to compile).
>> 
>> DO NOT follow the instructions for compiling the tulip module, they don't
>> work. It tells you to just compile the tulip.c file with a gcc command but
>> you need some headers that are not there resulting in compile errors out
> the
>> wazzu.
>> 
>> What you need is the latest source RPM for the PCI card modules:
>> 
>> ftp://ftp.scyld.com/pub/network/netdriver-2.0-3.src.rpm
>> 
>> Install the RPM and  #cd /usr/src/linux/drivers/net/
>> 
>> run #make
>> 
>> this will recompile the new modules. move the new tulip.o and pci-scan.o
>> into /lib/modules/2.2.xxxx/net/ and run #depmod
>> 
>> Now it ought to load just fine: #modprobe -a tulip
>> If not, get the newest test tulip.c file from
>> ftp://ftp.scyld.com/pub/network/test/
>> 
>> put it in /usr/src/linux/drivers/net/ and run #make again
>> 
>> 
>> taste it,
>> Gavin
>> 
>> P.S.
>> I like to answer my own problems as too many times I search the archives
> and
>> find questions but no answers.
>> 
>> on 9/1/00 7:40 PM, Gavin Clark  wrote:
>> 
>>> Hi,
>>> just got a linksys etherfast 10/100 to be my second ethernet card
>>> 
>>> it says to use the tulip.o module to drive it but it doesn't work. the
>>> module won't load.  I get 'device or resource busy':
>>> 
>>> # modprobe -a tulip
>>> /lib/modules/2.2.15-4mdk/net/tulip.o: init_module: Device or resource
> busy
>>> /lib/modules/2.2.15-4mdk/net/tulip.o: insmod
>>> /lib/modules/2.2.15-4mdk/net/tulip.o failed
>>> /lib/modules/2.2.15-4mdk/net/tulip.o: insmod tulip failed
>>> 
>>> anyone using this card and what did you do to get it running?
>>> 
>>> thanks,
>>> Gavin


Reply via email to