by harina » Mon, 19 Feb 2001 09:45:02
I'm working on setting up my first linux box. It has two network cards. eth0
is a 3com card, and is working fine. eth1 is a linksys pci card EtherFast.
When I try ne2000pci or tulip driver (that comes with RH7), it gives me an
error on bootup that the card is busy.
What can I do? Can it possibly be that the driver for eth1 is trying to
access the card of eth0?
Thanks a lot.
HariNam
by Silviu Minu » Mon, 19 Feb 2001 13:22:01
In /etc/modules.conf put
alias eth0 3c905 # or whatever driver you're using for the 3com card
alias eth1 tulip # the driver for the linksys card
> I'm working on setting up my first linux box. It has two network cards. eth0
> is a 3com card, and is working fine. eth1 is a linksys pci card EtherFast.
> When I try ne2000pci or tulip driver (that comes with RH7), it gives me an
> error on bootup that the card is busy.
> What can I do? Can it possibly be that the driver for eth1 is trying to
> access the card of eth0?
> Thanks a lot.
> HariNam
by harina » Mon, 19 Feb 2001 17:09:41
I tried compiling the driver. And, exactly as you mentioned, there are
issues with RH7.0. The first one, was to use kgcc instead of gcc. I did
that. The second problem is that rh has the wrong header files of linux
kernel. I have no clue, how to work around that. The instructions just say
that's the issue.
You seem to be more familiar with this driver and rh7.0. Please, help.
> In /etc/modules.conf put
> alias eth0 3c905 # or whatever driver you're using for the 3com
card
> alias eth1 tulip # the driver for the linksys card
> > Hi,
> > I'm working on setting up my first linux box. It has two network cards.
eth0
> > is a 3com card, and is working fine. eth1 is a linksys pci card
EtherFast.
> > When I try ne2000pci or tulip driver (that comes with RH7), it gives me
an
> > error on bootup that the card is busy.
> > What can I do? Can it possibly be that the driver for eth1 is trying to
> > access the card of eth0?
> > Thanks a lot.
> > HariNam
by Silviu Minu » Tue, 20 Feb 2001 04:07:48
rpm -Uvh netdriver-2.1.src.rpm
This will create two files: netdrivers.tgz and netdrivers.spec. The first one
goes in /usr/src/redhat/SOURCES and the second goes in /usr/src/redhat/SPECS.
If you try to make the rpm from sources with the command they specify on the
scyld.com page, the compiler will be gcc, which in your case is the wrong
version. So what you need to do is unpack the netdrivers.tgz file in
/usr/src/redhat/BUILD, and either do
make CC=kgcc
or change the CC=gcc to CC=kgcc in the Makefile and then do a usual
make
This should compile the drivers. You do not need to worry about the include
path, it is correct in the Makefile. Then simply copy the tulip.o driver into
/lib/modules/2.2.16-22/net. You may want to back-up the old tulip.o module,
which you can later delete if the new one works (as it should).
> I tried compiling the driver. And, exactly as you mentioned, there are
> issues with RH7.0. The first one, was to use kgcc instead of gcc. I did
> that. The second problem is that rh has the wrong header files of linux
> kernel. I have no clue, how to work around that. The instructions just say
> that's the issue.
> You seem to be more familiar with this driver and rh7.0. Please, help.
> > For the linksys card use the tulip driver from http://www.scyld.com (just
> > follow the obvious links). It's tricky to compile the standalone driver on
> a
> > RH7.0 because of the gcc-2.96 compiler. Read the instructions carefully
> to get
> > an idea about what's going on. Download the whole netdriver.src
> > (ftp://ftp.scyld.com/pub/network/netdriver-2.1.src.rpm) and build it as an
> rpm.
> > Then install the rpm.
> > In /etc/modules.conf put
> > alias eth0 3c905 # or whatever driver you're using for the 3com
> card
> > alias eth1 tulip # the driver for the linksys card
> > > Hi,
> > > I'm working on setting up my first linux box. It has two network cards.
> eth0
> > > is a 3com card, and is working fine. eth1 is a linksys pci card
> EtherFast.
> > > When I try ne2000pci or tulip driver (that comes with RH7), it gives me
> an
> > > error on bootup that the card is busy.
> > > What can I do? Can it possibly be that the driver for eth1 is trying to
> > > access the card of eth0?
> > > Thanks a lot.
> > > HariNam
by harina » Thu, 22 Feb 2001 12:25:32
I found a binary version. The binary version installed with almost no
problems. I ran into some other things. But, now my whole network and
masquerading just work fine. What an adventure into Linux!
/usr/src/redhat/SPECS.Quote:> Download the source rpm netdriver-2.1.src.rpm from the location I
mentioned in
> the previous post and put it /usr/src/redhat/SRPMS.
> rpm -Uvh netdriver-2.1.src.rpm
> This will create two files: netdrivers.tgz and netdrivers.spec. The first
one
> goes in /usr/src/redhat/SOURCES and the second goes in
> make CC=kgcc
> or change the CC=gcc to CC=kgcc in the Makefile and then do a usual
> make
> This should compile the drivers. You do not need to worry about the
include
> path, it is correct in the Makefile. Then simply copy the tulip.o driver
into
> /lib/modules/2.2.16-22/net. You may want to back-up the old tulip.o
module,
> which you can later delete if the new one works (as it should).
> > Thanks. I think that's what I need.
> > I tried compiling the driver. And, exactly as you mentioned, there are
> > issues with RH7.0. The first one, was to use kgcc instead of gcc. I did
> > that. The second problem is that rh has the wrong header files of linux
> > kernel. I have no clue, how to work around that. The instructions just
say
> > that's the issue.
> > You seem to be more familiar with this driver and rh7.0. Please, help.
> > > For the linksys card use the tulip driver from http://www.scyld.com
(just
> > > follow the obvious links). It's tricky to compile the standalone
driver on
> > a
> > > RH7.0 because of the gcc-2.96 compiler. Read the instructions
carefully
> > to get
> > > an idea about what's going on. Download the whole netdriver.src
> > > (ftp://ftp.scyld.com/pub/network/netdriver-2.1.src.rpm) and build it
as an
> > rpm.
> > > Then install the rpm.
> > > In /etc/modules.conf put
> > > alias eth0 3c905 # or whatever driver you're using for the
3com
> > card
> > > alias eth1 tulip # the driver for the linksys card
> > > > Hi,
> > > > I'm working on setting up my first linux box. It has two network
cards.
> > eth0
> > > > is a 3com card, and is working fine. eth1 is a linksys pci card
> > EtherFast.
> > > > When I try ne2000pci or tulip driver (that comes with RH7), it gives
me
> > an
> > > > error on bootup that the card is busy.
> > > > What can I do? Can it possibly be that the driver for eth1 is trying
to
> > > > access the card of eth0?
> > > > Thanks a lot.
> > > > HariNam
by Fred Marsic » Sat, 24 Feb 2001 02:09:16
> I'm working on setting up my first linux box. It has two network cards. eth0
> is a 3com card, and is working fine. eth1 is a linksys pci card EtherFast.
> When I try ne2000pci or tulip driver (that comes with RH7), it gives me an
> error on bootup that the card is busy.
> What can I do? Can it possibly be that the driver for eth1 is trying to
> access the card of eth0?
> Thanks a lot.
> HariNam
1. Getting a Linksys PCI ethernet card to work
I have just purchased and installed a Linksys 10/100 Ethernet PCI card, but I
can't get it to work under RedHat 5.2. I run netcfg and it cannot identify the
card.
Here's my configuration details:
RedHat Linux 5.2
Kernel 2.2.1, compiled with all PCI ethernet cards as modules
Here's what the command lspci returns for the network card:
00:0c.0 Ethernet controller: Lite-On Communications Inc LNE100TX (rev 20)
What do I need to do to get my card working?
Thanks.
3. Problem getting my second ethernet card working...
5. Getting two PCI ethernet cards working on the same machine.
6. Removing runtime link path in binary
7. Need help getting Linksys Wireless Ethernet to work with RedHat 7.1
8. SCSI hassel: can't fdisk HP 1GB disk (no disk geometery)
9. getting Ethernet to work (Linksys)
10. Getting RedHat9 to work with Linksys WPC54G (802.11g PCMCIA card)
11. getting a linksys ether fast card to work in red hat 6.1
12. Problems getting Linksys wireless card w/PCI adapter to work
13. Has anyone gotten a new Linksys 100 base T card to work properly?