NIC card not detected at startup

For all intents and purposes I am a Linux newbie.

I installed RedHat 9.2 about eight months ago on an ancient machine I
had lying around. A couple of months ago I acquired a slightly faster
box that had everything hardware-wise except a hard drive. So I
decided to remove the HDD from the old machine and put it in the new
one.

Background:

LINUX STUFF: RH9.2, not running X (CLI only)
NETWORKING STUFF: I use the Linux machine as a file server, web
testing server and general Linux education machine. The Linux machine
will be using DHCP, IP provided by my WinXP box (I successfully
configured this before).

OLD MACHINE
IBM Aptiva
Linksys 10/100 PCI Network Adapter (Linux driver=tulip)

NEW MACHINE
Gateway
SMC, Inc. PCI LAN card (83c170 chip, Linux driver=epic100)

I booted up the new machine and Linux brought up Kudzu. Kudzu first
asked me if I wanted to keep the configuration for the Linksys and I
said "yes," because I planned to put the Linksys card in the new
machine at a later time. What I didn't realize was that the new
machine already had the SMC card installed in it (this is called "not
doing your homework"). I learned this because Kudzu then asked me if
I wanted to keep the config for the SMC card, and I said "yes" to that
as well.

So Linux continues booting, and then I get:

....
tulip device eth0 does not seem to be present, delaying initialization
epic100 device eth1 does not seem to be present, delaying
initialization
....

I'm guessing that if I can get Linux to understand that epic100 should
be on eth0 instead of eth1, everything should work just fine. So
saying:

If I'm right, how do I tell Linux to put the SMC on eth0?
If I'm wrong, how do I get my networking working?

I know the easy way out: swap the SMC out for the Linksys, but I'd
rather do this the hard way and maybe learn something about hardware
config in Linux.

TIA,
Dave Baker

On 26 Nov 2003 20:10:50 -0800, david baker wrote:
> For all intents and purposes I am a Linux newbie.
>
> I installed RedHat 9.2 about eight months ago on an ancient machine I
> had lying around. A couple of months ago I acquired a slightly faster
> box that had everything hardware-wise except a hard drive. So I
> decided to remove the HDD from the old machine and put it in the new
> one.
>
> Background:
>
> LINUX STUFF: RH9.2, not running X (CLI only)
> NETWORKING STUFF: I use the Linux machine as a file server, web
> testing server and general Linux education machine. The Linux machine
> will be using DHCP, IP provided by my WinXP box (I successfully
> configured this before).
>
> OLD MACHINE
> IBM Aptiva
> Linksys 10/100 PCI Network Adapter (Linux driver=tulip)
>
> NEW MACHINE
> Gateway
> SMC, Inc. PCI LAN card (83c170 chip, Linux driver=epic100)
>
> I booted up the new machine and Linux brought up Kudzu. Kudzu first
> asked me if I wanted to keep the configuration for the Linksys and I
> said "yes," because I planned to put the Linksys card in the new
> machine at a later time. What I didn't realize was that the new
> machine already had the SMC card installed in it (this is called "not
> doing your homework"). I learned this because Kudzu then asked me if
> I wanted to keep the config for the SMC card, and I said "yes" to that
> as well.
>
> So Linux continues booting, and then I get:
>
> ...
> tulip device eth0 does not seem to be present, delaying initialization
> epic100 device eth1 does not seem to be present, delaying
> initialization
> ...
>
> I'm guessing that if I can get Linux to understand that epic100 should
> be on eth0 instead of eth1, everything should work just fine. So
> saying:
>
> If I'm right, how do I tell Linux to put the SMC on eth0?

Modify /etc/modules.conf