Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cant get 2nd NIC up

Status
Not open for further replies.

Guest_imported

New member
Jan 1, 1970
0
I am attempting to install a second ethernet card. I run a slackware 8.0 486 with 2.2.19 kernel. I can?t compile a custom kernel with my hardware limitations so I have to stick with modules. I have tried everything I learned from the Ethernet and Multiple Ethernet how-to and from reading tons of posts. I?m embarrased to say how much time I?ve poured into this. It is sucking the fun out of Linux. Please help me detect & install both my NIC?s.

I can detect the cards individually using netconfig. The cards show:

eth0 Link encap:Ethernet HWaddr 00:00:C0:7E:4A:47
wd inet addr:10.1.1.11 Bcast:10.255.255.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:11 Base address:0x310 Memory:cc000-d0000

root@fes:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:00:C0:6C:FC:A1
sun-ultra inet addr:10.1.1.10 Bcast:10.255.255.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:5 Base address:0x310 Memory:cc000-d0000

So I added some aliases to modules.conf to pick up the card.

#modules.conf
alias eth0 wd
alias eth1 smc-ultra
...

I added a script to rc.inet1 to pick up the card on boot

#rc.inet1
# eth1
IPADDR1="10.1.1.12" # REPLACE with YOUR IP address!
NETMASK1="255.255.255.0" # REPLACE with YOUR netmask!
NETWORK1="10.1.1.0" # REPLACE with YOUR network address!
BROADCAST1="10.1.1.255" # REPLACE with YOUR broadcast address, if you
# have one. If not, leave blank and edit below.

echo "Configuring eth1 as ${IPADDR1}..."
/sbin/ifconfig eth1 ${IPADDR1} broadcast ${BROADCAST1} netmask ${NETMASK1}
/sbin/route add -net ${NETWORK1} netmask ${NETMASK1} eth1
# done eth1

But when I reboot the cards are not detected. The error on boot is

Configuring eth1 as 10.1.1.12...
SIOCSIFADDR: No such device
eth1: unknown interface: No such device
SIOCSIFBRDADDR: No such device
eth1: unknown interface: No such device
SIOCSIFNETMASK: No such device
SIOCADDRT: No such device
Configuring eth0 as 10.1.1.11...
SIOCSIFADDR: No such device
eth0: unknown interface: No such device
SIOCSIFBRDADDR: No such device
eth0: unknown interface: No such device
SIOCSIFNETMASK: No such device

I think the rc.inet1 script produced the errors because the card wasn?t loaded. I think there is a problem with my modules.conf. I?ve tried a couple of things to troubleshoot.

I added
/sbin/modprobe/wd io=0x300 irq=11
/sbin/modprobe/smc-ultra io=0x200 irq=5
to rc.network. I get the additional errors of:

/lib/modules/2.2.19/net/smc-ultra.o.gz: init_module: Device or resource busy
/lib/modules/2.2.19/net/smc-ultra.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
/lib/modules/2.2.19/net/smc-ultra.o.gz: insmod /lib/modules/2.2.19/net/smc-ultra.o.gz failed
/lib/modules/2.2.19/net/smc-ultra.o.gz: insmod smc-ultra failed
root@fes:~# modprobe wd
/lib/modules/2.2.19/net/wd.o.gz: init_module: Device or resource busy
/lib/modules/2.2.19/net/wd.o.gz: Hint: insmod errors can be caused by incorrect
module parameters, including invalid IO or IRQ parameters
/lib/modules/2.2.19/net/wd.o.gz: insmod /lib/modules/2.2.19/net/wd.o.gz failed
/lib/modules/2.2.19/net/wd.o.gz: insmod wd failed

I figure I?m loading the card twice so I take that out.

I add options lines to modules.conf to specify io and irq settings

#modules.conf
alias eth0 wd
alias eth1 smc-ultra
options eth0 -o wd io=0x300
options eth1 -o sun-ultra io=0x200

#also tried
options wd io=0x300
options sun-ultra io=0x200

I got the io numbers from slack /Documentation/networking/net-modules.txt I tried a couple of different IOs but the net-modules.txt said the IRQs would be read from EEPROM. I don?t see a problem with the IRQs as the boards had non-conflicting IRQs when they installed individually. I didn?t manually set an IRQ.

In my desperation I even tried changing lilo.conf with
append="ether=0x0240,0,eth0;ether=0x0300,0,eth1"
That didn?t work of course as this has to do with drivers built into the kernel and not modules.

If anyone could tell me what I?m doing wrong and how to get 2 nics running with kernel modules I would really appreciate it.

Cheers,

Pat
 
This may sound overly simple, but have you tried running your hardware probe tool? (e.g. kudzu under Red Hat - I'm not familiar enough with Slackware anymore to know if that exact tool is available).
 
I suppose you use two pci-nic´s?
I've never used slackware but pci-nic's should have their irq and I/O detected by linux. The changes you've made to modules.conf and lilo.conf are mainly for ISA-nic's (If I'm not misstaken).

Have you entered bios and disabled plug n play settings? That setting have given me headache before.

I see you share the I/O of 310 between the cards and I think that is where your problem is.
I had that problem a while ago and installed the NIC on a windows machine and changed I/O.
You're right that it reads the setup from the NIC's eprom.

That can cause problems when you want to change irq or I/O, since you might need a program from the manufacturer to write/change settings to the eprom. 3com, for instance, have had a special program under windows to change irq, i/o, duplex, speed. The question is, are these programs available under linux/slackware? I don't think you need a special program for your NIC's.

If no other setting works, try another NIC.

Let us/me know how it works. I do, in fact, have the EXACT problem with a machine next to me. I haven't had the time to troubleseek it just yet, but I will. /Sören
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top