Click to See Complete Forum and Search --> : Need help recognizing second network card
I can't get the second network card to be recognized getting errors like "eth1: unknown device" or "eth1: unknown interface". When I ifconfig the all I get is eth0 and lo, no eth1.
The first card is a Winbond Electronics Corp W89C840 and the second is Realtek RT8139. Which ever one I call "eth0", that one works but when I call one "eth1" it's not recognized. I'd appreciate any help with this... basically I don't really know what I'm doing.
Lorithar
09-10-2002, 11:42 AM
Ummm
Are you sure that you can activate both network cards?
I would suspect 1) module for the 8139 not loading .. (there are two different modules for 8139 cards, and telling the difference is up to humans, not the system) 2) plug and play os is turned on in your bios ...(You need to check this and turn it off)
What modules are loaded?
lsmod on the command line as root will return a list.
The modules that are running are:
ipv6
nfsd
rl100a
memstat
usb-uhci
serial
usbcore
I've checked the plug and play and it was already off. If you can help I'd appreciate it.
Insta_Toast
09-12-2002, 09:03 PM
Im having the same prob =(
cage47
09-13-2002, 12:35 AM
I had troubles getting 2 nics to work at the same time. I ended up having to change the ip of the second.
eth0 was 192.168.47.1
and
eth1 was 192.168.46.1
otherwise only eth0 would work. And it didn't matter which card was set as eth0. Once I did this bing bang boom, all going fine. and each machine connected to those cards could see each other too.
How do I get the "eth1" card recognized. As long as I call the card "eth0" it works. I've been able to see the network on other computers but not get on the Internet. Or I've been able to get on the Internet but see nothing on other computers.
mdwatts
09-13-2002, 03:25 PM
Have you tried to manually load the module for eth1? Any errors?
Also add
alias eth0 <module name>
alias eth1 <module name>
to /etc/modules.conf and see if that helps.
module? yeah that shows just how much I'm a newbie. some help on what that is would be appreciated as well.
michaelk
09-16-2002, 12:03 PM
A module is similar to a windows driver but can be loaded and unloaded without rebooting the computer.
To manually load the module:
insmod rtl8139
If that works then you can try mdwatts suggestion
BTW what distro are you running (did I miss reading it)?
neondog
09-17-2002, 01:52 AM
I am also having trouble with the RLT 8139c as eth1. I try to insmod the 8139too module..no luck, same with modprobe. I am beginning to suspect that it is an I/O problem and/or IRQ. Is there a way to manually assign them to the devices individually?
PnP is also diabled on the motherboard.
We're using Suse Linux 7.0. Where would I get a module for the cards?
I uname -r the machine and got 2.2.16 if that helps anyone. I'm not sure what it means.
jumpedintothefire
09-17-2002, 09:42 PM
neondog --- what is the error that is spit out???
kaut & neondog --- try: locate -u then: locate 8139
and see if it lives in you /lib/modules/ <version> /kernel/drivers/net/
There may be an option for the card in the kernel but it was not compiled as a module....
--quote---
How do I get the "eth1" card recognized. As long as I call the card "eth0" it works.
------------
So your able to ping the network as eth0??
That would sugest that It maybe compiled it into the kernel, then you need to pass that info at the boot prompt and not use conf.modules/modules.conf
see:
http://www.tldp.org/HOWTO/BootPrompt-HOWTO.html Section 11.1
http://www.ibiblio.org/mdw/HOWTO/Ethernet-HOWTO-9.html#ss9.1
neondog
09-17-2002, 10:43 PM
eth0 works fine, it is some Linksys card using the tulip module. The system doesn't detect the Realtek card (should be eth1) and 8139too module won't load. I've tried adjusting the IO address and the IRQ to no avail. I am beginning to think it just a piece of junk ( runs fine in W98) and I should get a decent NICs for this job....any suggestions?
Its an 850 Mhz P3, Intel 440BX-v2 mobo that has been pulling NAT duty for my home LAN via dial-up. Tested ADSL the other day and the connection works fine over the Lynksys card so I want to pipe the DSL into this machine for my LAN
somewhere I read there is a compatiblilty issue with this chipset (RLT 8139) and the 2.4.x kernel???
:mad:
jumpedintothefire
09-17-2002, 10:52 PM
I have 2 8139 modules... 8139.cp 8139too
try the locate.....
jumpedintothefire
09-17-2002, 11:11 PM
ftp://152.104.225.43/cn/nic/rtl8139abcd8130810xseries/linux24x-8139cp(101).zip
that's the link at realtec site id say that it uses the cp
version....
when I locate 8139 I get it in
/lib/modules/2.2.16/net/rtl8139.o
and
/usr/src/linux-2.2.16.SuSE/drivers/net/rtl8139.c
I've added alias eth1 rtl8139 to the /etc/modules.conf and both cards went out, but now we can't telnet either.
jumpedintothefire
09-18-2002, 06:43 PM
ftp://152.104.125.40/cn/nic/rtl8139abcd8130810xseries/linux22x-8139cp(100).zip
This one is for the 2.2 kernel d/l and compile it. then try to insmod it...
neondog
09-19-2002, 01:08 AM
I gave up on the Realtek NIC and got me a Linksys that works. Here is a copy of the readme for the 8139too module. Maybe it will help.
Comments for 8139too.c version 1.0.0
2001/10/31 by ShuChen Shao
1.This driver was originally based on 8139too.c version "0.9.15".
2.It has been enhanced to support RTL8139C+ PCI ethernet chips and tested in 2.4.2 kernel.
3.RTL8139C+ PCI ethernet chips is set to support C+ mode by default.
If FORCE_C_Mode below is enabled, the RTL8139C+ chip will be forced to support C mode
after reboot.
4.This program can be compiled using the attached Makefile.
And the object file named 8139too.o should be moved to the directory
/lib/modules/2.4.2-2/kernel/drivers/net/
5.It can support Auto-Negotiation ability,that is
10-half 0x01
10-full 0x02
100-half 0x04
100-full 0x08
If 10-half mode is expected, it can be achieved by the following steps:
#ifconfig eth0 down
#rmmod 8139too
#insmod 8139too media=0x01
6.If the "Install Type", selected during the Linux install procedure, is "laptop",
this driver can work normally for CardBus application without any modification.
Otherwise, reinstall Linux and select "Install Type" as "laptop".
Then this driver can also work.
################################################## ############################################
Comments for 8139too.c version 1.0.1
2001/11/21 by ShuChen Shao
1.It is able to support RTL8139C+ PCI ethernet chips in RedHat 7.2 (kernel 2.4.7).
In addition, it is backward compatiable with RedHat 7.1 (kerne 2.4.2).
Both of my cards work now, I can ping both from other machines, but I can't telnet either one, not even from the machine that they're in.
jumpedintothefire
09-19-2002, 09:11 PM
----quote------
I can ping both from other machines
----------------
What ip addresses did you set each card up with?
ie 192.168.0.101 192.168.0.102??.....
that a little tricky, there both on the same network...
try one at 192.168.0.101 and the other at 192.168.1.101, that puts them on different networks. Plug the cable into one at a time, then switch the ips around to test that they both work.....
We have the ip of the one going on the internet like 192.203.200.100 and the network one like 90.0.0.200
jumpedintothefire
09-21-2002, 06:36 PM
-----
not even from the machine that they're in.
-----
What does netstat -tna show??
the ip over the net said CLOSE_WAIT while the Lo Ip was established and then 0.0.0.0 (whatever that is) said LISTEN. The network ip didn't even show up, but when I ifconfig everything showed up.
jumpedintothefire
09-23-2002, 07:03 PM
Not too familiar with susi.... 0.0.0.0 = all interfaces
What you posted would suggest that tcpwrappers is closing the connection on you. You would need to setup the /etc/hosts.allow /etc/hosts.deny correctly for the services that you offer and allowed ips that may connect. What do you have in those files?? Start a new thread OK, this one is a little long......