Hi folks,

I've added a second Ethernet card to my Mandrake box (which has been working with a single card for a couple of years on different versions of Mandrake). When I go to command centre it can only see the original card. I expected to find some graphical tool for adding the new card (either manually or by scanning) but there doesn't seem to be anything.

Do I need to run something from the command line? If so, could anyone point me in the right direction please?

Many thanks,

Rob

Well I didn't find anything. I will let you know if I do..Sorry!

Is Kudzu exist for this distro ??

it's a hardware detection softeware provided with red hat..

You need to add the driver for the 2nd card to /etc/modules.conf. You will find an alias for your existing eth0 in there, you need to add one for eth1.

If you have no idea which driver to pick, post the output of lspci and your current /etc/modules.conf and we'll be able to help you.

Hope is helps,
mlp

You have to insert the driver in your /etc/modules.conf file. After a reboot, the card should be detected.

Cheers bagira

Thanks for all the seggestions. :-)

The plot thickens. When lspci (neat command that!) didn't list the second Ethernet card, I rebooted to see what the BIOS was detecting. Sure enough, only one network card. So, I opened up the computer and the card itself wasn't quite pushed far enough into the PCI slot.

Now I can see both cards and the second one is loaded (automatically) into modules.conf. Great.

Weird things is I can *only* get on the LAN with eth1 now! eth0 refuses to let me do as much as ping! I assume I should be able to use both to access the LAN...

It would appear that Linux has no problem with autodetecting networks cards anyway!

No, that's not correct. From your statement that you didn't have to do anything to the modules.conf file I take it that the 2nd card has the same driver as your original one. Unless you take special action, the naming (which one is eth0 and which is eth1) is determined by the position of the card on the bus. Now only one card can be the one that talks to your LAN; that seems to be eth1. You would want to have two cards in order to route the internet trafic to your private LAN (say, eth0 connects to your cable/DSL modem and the other card serves your home-internal network). You cannot simply connect both cards to the same network, if that's what you have done.

Please post the output of your ifconfig command and tell us which IP you pinged successfully.

mlp

Ah, having run ifconfig, I only get eth0 - and also on bootup, it only brings up eth0 as it lists everything that's being loaded/brought up. Certainly both cards have Realtek RTL8139 devices on them, I'm guessing the driver *should* be the same. It's certainly what modules.conf indicates.

I can ping 192.168.0.x - where x is is any valid address on my LAN.

I can also ping the likes of bbc.co.uk

Here are my listings.

Many thanks,

Rob.

First off, ifconfig:

eth0 Link encap:Ethernet HWaddr 00:50:FC:31:2F:64
inet addr:192.168.0.81 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::250:fcff:fe31:2f64/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:539 errors:0 dropped:0 overruns:0 frame:0
TX packets:371 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:530989 (518.5 Kb) TX bytes:39044 (38.1 Kb)
Interrupt:5 Base address:0x9000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:70 errors:0 dropped:0 overruns:0 frame:0
TX packets:70 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4594 (4.4 Kb) TX bytes:4594 (4.4 Kb)

then /etc/modules.conf:

probeall scsi_hostadapter aic7xxx
probeall usb-interface usb-uhci
above snd-via82xx snd-pcm-oss
alias eth0 8139too
alias sound-slot-0 snd-via82xx
alias eth1 8139too

Ok. I'm still at a loss what you want to use the eth1 for. The eth0 is brought up because (I guess) there's a configuration file for it. It would be in /etc/sysconfig/network-scripts/ifcfg-eth0. Unless there's also a ifcfg-eth1 with the specific settings, eth1 will be left alone. You can either use your favorite editor to write such a file, or use one of the configuration tools to do it.

By default, ifconfig shows only interfaces which are up, so you would need to do ifconfig eth1 to see it (and find it down). Again, eth0 presumably got configured at the time you installed the OS.

Now you can go and run yet another LAN off eth1...

Hope it helps,
mlp