...well not exactly, I have the following:
eth0-IBM 10/100 ethernet card.
eth1-Buffalo Wireless PCMCIA in PCI adapter card.

READ ON-It's not a wireless problem!!!

I currently use the Linux box to NAT nodes on the wireless network. That's all working fine but now I have been given a perfect PIII box and I want to stick XP on it and NAT through linux but NOT wirelessly. It will live beside the Linux gateway and I want to add another ethernet card to said gateway and connect to my free present that way. I just opened up the Linux box and threw in another 10/100 PCI ethernet card and botted up but nada, doesn't seem to detect it at boot. The card works on its own etc.. so any ideas how to TELL Linux it's there?
I use LILO.

Once again, thanks for any help guys.

Who made the NIC? (model/chipset) You can probabaly just look up what the module you need with google and just: modprobe <modulename> alias eth2


--tarballedtux

If you don't like dealing with modules (like myself), you can always rebuild your kernal with the new NIC drivers installed. Much more work, but less headaches.

It's a d-link NIC, think it's an Intel chipset, have to open her up again to have a look. So ya reckon that one modprobe command will bring her to life?

As for recompiling the kernel-no way, I had enough headaches doing that for wireless! I refuse to believe that installing a common thing like a NIC by any manufacturer should be in any way difficult.

I thouht kudzu or whatever it's called should pick up the new hardware at boot time?

I stopped trusting auto installers a while ago. I can trust however that they are not 100%.
Tell us what the output of this command is:

lspci -v
If that doesn't work try:
scanpci -v

--tarballedtux

Hi tarballedtux,
Output from lspci -v

00:00.0 Host bridge: Intel Corporation 430VX - 82437VX TVX [Triton VX] (rev 02)
Flags: bus master, medium devsel, latency 72

00:07.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] (rev 01)
Flags: bus master, medium devsel, latency 0

00:07.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] (prog-if 80 [Master])
Flags: bus master, medium devsel, latency 32
I/O ports at 6000 [size=16]

00:08.0 VGA compatible controller: S3 Inc. 86c325 [ViRGE] (rev 06) (prog-if 00 [VGA])
Flags: bus master, medium devsel, latency 32, IRQ 11
Memory at cc000000 (32-bit, non-prefetchable) [size=64M]
Expansion ROM at d0000000 [disabled] [size=64K]

00:0b.0 Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100] (rev 05)
Subsystem: IBM 82558B Ethernet Pro 10/100
Flags: bus master, medium devsel, latency 32, IRQ 10
Memory at ca000000 (32-bit, prefetchable) [size=4K]
I/O ports at 6020 [size=32]
Memory at d0100000 (32-bit, non-prefetchable) [size=1M]
Expansion ROM at d0200000 [disabled] [size=1M]
Capabilities: [dc] Power Management version 1

00:11.0 CardBus bridge: Ricoh Co Ltd RL5c475 (rev 80)
Subsystem: Melco Inc: Unknown device 030a
Flags: bus master, medium devsel, latency 168, IRQ 9
Memory at d0300000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=00, secondary=01, subordinate=04, sec-latency=176
Memory window 0: d0301000-d0302000 (prefetchable)
Memory window 1: 10000000-103ff000
I/O window 0: 00001000-000010ff
I/O window 1: 00001400-000014ff
16-bit legacy interface ports at 0001
==========================================================================
Output from scanpci -v

pci bus 0x0 cardnum 0x00 function 0x0000: vendor 0x8086 device 0x7030
Intel 82437VX
STATUS 0x2200 COMMAND 0x0006
CLASS 0x06 0x00 0x00 REVISION 0x02
HEADER 0x00 LATENCY 0x48

pci bus 0x0 cardnum 0x07 function 0x0000: vendor 0x8086 device 0x7000
Intel 82371 pci-isa bridge
STATUS 0x0280 COMMAND 0x000f
CLASS 0x06 0x01 0x00 REVISION 0x01
HEADER 0x80 LATENCY 0x00

pci bus 0x0 cardnum 0x07 function 0x0001: vendor 0x8086 device 0x7010
Intel 82371 bus-master IDE controller
STATUS 0x0280 COMMAND 0x0005
CLASS 0x01 0x01 0x80 REVISION 0x00
BIST 0x00 HEADER 0x00 LATENCY 0x20 CACHE 0x00
BASE4 0x00006001 addr 0x00006000 I/O
BYTE_0 0x4000e377 BYTE_1 0x00 BYTE_2 0x806c5f0 BYTE_3 0xffffffff

pci bus 0x0 cardnum 0x08 function 0x0000: vendor 0x5333 device 0x5631
S3 ViRGE
STATUS 0x0200 COMMAND 0x0007
CLASS 0x03 0x00 0x00 REVISION 0x06
BIST 0x00 HEADER 0x00 LATENCY 0x20 CACHE 0x00
BASE0 0xcc000000 addr 0xcc000000 MEM
BASEROM 0xd0000000 addr 0xd0000000 not-decode-enabled
MAX_LAT 0xff MIN_GNT 0x04 INT_PIN 0x01 INT_LINE 0x0b

pci bus 0x0 cardnum 0x0b function 0x0000: vendor 0x8086 device 0x1229
Intel 82557/8/9 10/100MBit network controller
CardVendor 0x1014 card 0x005c (IBM, Card unknown)
STATUS 0x0290 COMMAND 0x0017
CLASS 0x02 0x00 0x00 REVISION 0x05
BIST 0x00 HEADER 0x00 LATENCY 0x20 CACHE 0x00
BASE0 0xca000008 addr 0xca000000 MEM PREFETCHABLE
BASE1 0x00006021 addr 0x00006020 I/O
BASE2 0xd0100000 addr 0xd0100000 MEM
BASEROM 0xd0200000 addr 0xd0200000 not-decode-enabled
MAX_LAT 0x38 MIN_GNT 0x08 INT_PIN 0x01 INT_LINE 0x0a

pci bus 0x0 cardnum 0x11 function 0x0000: vendor 0x1180 device 0x0475
Ricoh RL5C475 PCI-CardBus bridge/PCMCIA
STATUS 0x0210 COMMAND 0x0007
CLASS 0x06 0x07 0x00 REVISION 0x80
HEADER 0x02 LATENCY 0xa8
==========================================================================

So as far as I can see it only sees the usual PCI host controllers and the graphics adapter built onto the MB and 2 of my cards, the IBM ethernet one and the PCMCIA card (the MELCO one) in the PCI adapter (that's the one with the RICOH controller). Best course of action? maybe pull all but the new card out and retry the above? My system will boot without the existing cards won't it? it will pause on 'bringing up eth0' for ages but will it eventually go through? I only have this last PCI slot available so I need to verify it's working, maybe try the IBM card on it's own in the suspect slot? If it were an IBM server running AIX I'd just boot it up and do 'lsdev -C | grep eth' and I'd know if it was there but Linux seems to hang for ages on boot when I remove the existing config.............essentially I'm asking will it boot if I leave it long enough to figure out there's no card where there once was?

Thanks again and apologies for the long post.

If the Intel card is the new one then it is being detected. You can try putting all three in the system and after its booted up, do a modprobe eepro100 alias eth2 That SHOULD bring the card into working order. Then you would just need to configure it.


--tarballedtux

Thanks for the reply,
that output listing above is with all 3 cards in (the IBM one uses the Intel chip) so it ain't bein detected, I take it that modprobe will not work above as it's not even seeing the card?