[burnit]

Hello to all!

I have added a NIC to my PC. This is the current PCI configuration:

02:04.0 Ethernet controller: D-Link System Inc RTL8139 Ethernet (rev 10)
02:09.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13)

All these NICs are working well, but I cannot use them at the same time: only the first card (following module loading) is working. The other cannot be configured for the use. Modules used are sk98lin and 8139too.

At boot it prints:

8139too Fast Ethernet driver 0.9.27
ACPI: PCI Interrupt 0000:02:04.0[A] -> GSI 18 (level, low) -> IRQ 16
eth0: RealTek RTL8139 at 0xf881e000, 00:0d:88:1a:88:51, IRQ 16
eth0: Identified 8139 chip type 'RTL-8100B/8139D'

...

ACPI: PCI Interrupt 0000:02:09.0[A] -> GSI 20 (level, low) -> IRQ 17
eth1: Yukon Gigabit Ethernet 10/100/1000Base-T Adapter
PrefPort:A RlmtMode:Check Link State

ifconfig eth0 192.168.0.1
ifconfig eth1 198.168.1.1
SIOCSIFADDR: No such device
eth1: ERROR while getting interface flags: No such device

Any suggestion?

[gruven]

Give us a printout of "ifconfig" after boot with both modules loaded.

Also, try this:

rmmod sk98lin
modprobe sk98lin
-or-
rmmod sk98lin
modprobe skge

I am not sure if the skge module will work for your card, but it does work for some Marvell/Yukon cards.

I have had to reload the module for a marvell card before, so the first command may work just fine.

[burnit]

As I said, the card associated with the first loaded module is configured correctly (and can be configured correctly), while the second card associated with the second module can't be configured. ALWAYS.

Unloading all modules, and loading modules, make eth0 always working (because eth0 is the interface claimed by the first module), and make eth1 not working (becuase eth1 is the interface claimed by the second module).

Just because someone asked, here is the output when all modules are loaded:

eth0 Link encap:Ethernet HWaddr 00:0F:EA:48:75:C0
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:462967 errors:0 dropped:0 overruns:0 frame:0
TX packets:522133 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:251046254 (239.4 MiB) TX bytes:275298506 (262.5 MiB)
Interrupt:17 Memory:fb000000-0

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1718 errors:0 dropped:0 overruns:0 frame:0
TX packets:1718 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:104620 (102.1 KiB) TX bytes:104620 (102.1 KiB)

Don't think I'm a noob, please. I know what I'm doing.

Here is a snippet of a bash session, to explain what happens:

rmmod sk98lin
rmmod 8139too
modprobe sk98lin
modprobe 8139too
# Now eth0 is related to sk98lin, and eth1 is related to 8139too
ifconfig eth0 192.168.0.1
ifconfig eth1 198.168.1.1
SIOCSIFADDR: No such device
eth1: ERROR while getting interface flags: No such device

rmmod sk98lin
rmmod 8139too
modprobe 8139too
modprobe sk98lin
# Now eth0 is related to 8139too, and eth1 is related to sk98lin
ifconfig eth0 192.168.0.1
ifconfig eth1 198.168.1.1
SIOCSIFADDR: No such device
eth1: ERROR while getting interface flags: No such device

Any suggestion?

[gruven]

I didn't assume you were a noob, I was just asking for the ifconfig.

Have you tried

ifconfig eth1 up

to see if you can get the device to be recognized?

It may not work, but I have actually had to do that before to get eth1 to show up.

All of the rest of my suggestions you have probably already tried since you know what you are doing, so I don't know. I hope you get this sorted out.

[burnit]

ifconfig eth1 up
eth1: ERROR while getting interface flags: No such device

It seems the module is not loaded... but it is!
Maybe it could be a IRQ related problem? I've tried to move the second NIC in another PCI slot (often this trick work in these situations), but without luck.

The problem is that my kernel don't printout any error message!

[cyberinstru]

Hey, while inserting the module sk98lin, could you check for any debug messages in 'dmesg'?

I think you wud have verified it... but can u post that here if you could get any??