Member
Registered: Apr 2004
Location: Belgium Antwerpen
Distribution: slackware - knoppix
Posts: 141
Rep:
|
second nic card wrong IRQ?
Hello,
I have a knoppix pc with two nic cards (only one used) which connects to a winxp gw to the internet. This works fine and now I want to use the linux box as gw but therefore I'd like to test if both nic on my linuxbox work fine. => I disconnected the ethernet cable from eth0 which has config: "iface eth0 inet dhcp" and indeed, winxp tells me: "network cable unplugged". Then I connect my cable to the eth1 nic which I also configured as "iface eth1 inet dhcp" => I do ifdown eth0 and commented out the config in the /etc/network/interfaces file. Then I do ifup eth1 but get an error msg: "Operation failed" And in winxp, the network is still marked as unplugged.
==> therefore I think there is a problem with my second nic.
when I do lspci -v, it looks ok to me:
root@Berta:/etc# lspci -v
00:00.0 Host bridge: VIA Technologies, Inc. VT82C598 [Apollo MVP3] (rev 04)
Flags: bus master, medium devsel, latency 16
Memory at e0000000 (32-bit, prefetchable) [size=64M]
Capabilities: [a0] AGP version 1.0
00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP] (prog-if 00 [Normal decode])
Flags: bus master, 66Mhz, medium devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 0000d000-0000dfff
Memory behind bridge: e4000000-e5ffffff
Prefetchable memory behind bridge: e6000000-e7ffffff
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C586/A/B PCI-to-ISA [Apollo VP] (rev 41)
Subsystem: VIA Technologies, Inc. MVP3 ISA Bridge
Flags: bus master, stepping, medium devsel, latency 0
00:07.1 IDE interface: VIA Technologies, Inc. VT82C586/B/686A/B PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
Flags: bus master, medium devsel, latency 64
I/O ports at e000 [size=16]
00:07.2 USB Controller: VIA Technologies, Inc. USB (rev 02) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
Flags: bus master, medium devsel, latency 64, IRQ 10
I/O ports at e400 [size=32]
00:07.3 Bridge: VIA Technologies, Inc. VT82C586B ACPI (rev 10)
Flags: medium devsel
00:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RT8139
Flags: bus master, medium devsel, latency 64, IRQ 11
I/O ports at e800 [size=256]
Memory at ea001000 (32-bit, non-prefetchable) [size=256]
Expansion ROM at e8000000 [disabled] [size=64K]
Capabilities: [50] Power Management version 2
00:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RT8139
Flags: bus master, medium devsel, latency 64, IRQ 12
I/O ports at ec00 [size=256]
Memory at ea000000 (32-bit, non-prefetchable) [size=256]
Expansion ROM at e9000000 [disabled] [size=64K]
01:00.0 VGA compatible controller: nVidia Corporation NV5M64 [RIVA TNT2 Model 64/Model 64 Pro] (rev 15) (prog-if 00 [VGA])
Subsystem: Creative Labs: Unknown device 103f
Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 11
Memory at e4000000 (32-bit, non-prefetchable) [size=16M]
Memory at e6000000 (32-bit, prefetchable) [size=32M]
Expansion ROM at e5000000 [disabled] [size=64K]
Capabilities: [60] Power Management version 1
Capabilities: [44] AGP version 2.0
but in dmesg, I see:
...
8139too Fast Ethernet driver 0.9.26
PCI: Assigned IRQ 11 for device 00:08.0
eth0: RealTek RTL8139 Fast Ethernet at 0xc6b96000, 00:50:bf:97:cb:fa, IRQ 11
eth0: Identified 8139 chip type 'RTL-8139C'
PCI: Found IRQ 11 for device 00:0a.0
IRQ routing conflict for 00:0a.0, have irq 12, want irq 11
eth1: RealTek RTL8139 Fast Ethernet at 0xc6b98000, 00:50:fc:a2:84:c7, IRQ 12
eth1: Identified 8139 chip type 'RTL-8139C'
...
eth0: Setting 100mbps full-duplex based on auto-negotiated partner ability 41e1.
eth0: Setting 100mbps full-duplex based on auto-negotiated partner ability 41e1.
blk: queue c0334fcc, I/O limit 4095Mb (mask 0xffffffff)
blk: queue c0334b60, I/O limit 4095Mb (mask 0xffffffff)
parport0: PC-style at 0x378 [PCSPP,TRISTATE,EPP]
lp0: using parport0 (polling).
lp0: console ready
eth0: Setting half-duplex based on auto-negotiated partner ability 0000.
eth1: Setting 100mbps full-duplex based on auto-negotiated partner ability 01e1.
eth0: Setting 100mbps full-duplex based on auto-negotiated partner ability 41e1.
eth0: Setting 100mbps full-duplex based on auto-negotiated partner ability 41e1.
Is this all normal? Especially the following worries me:
PCI: Found IRQ 11 for device 00:0a.0
IRQ routing conflict for 00:0a.0, have irq 12, want irq 11
Is this wrong and can it be fixed?
Just to complete, my ip a and ip r output:
root@Berta:/etc# ip a
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:50:bf:97:cb:fa brd ff:ff:ff:ff:ff:ff
inet 192.168.0.126/24 brd 192.168.0.255 scope global eth0
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:50:fc:a2:84:c7 brd ff:ff:ff:ff:ff:ff
root@Berta:/etc# ip r
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.126
default via 192.168.0.1 dev eth0
===All this text output is when I connect with the first (working fine) nic===
Thanks for any help.
rgds,
Lieven
|