Missconfiguration of ethernet interfaces on reboot

Hello everybody,

recently I have the same error in two different machines running
RedHat Linux 9 (kernel 2.4.20-8).

Each machine has 3 NICs: 2 of them come included in motherboard (one
network card with 2 NICs: one Intel e100 and one intel e1000) and the
other is an Intel e1000 Fiber Network Card attached in a PCI-Express
slot.

The interfaces' alias are assigned like this (looking at /etc/
modules.conf):
eth0: e100 NIC in motherboard
eth1: e1000 NIC in mother board
eth2: e1000 NIC in PCI slot

All the system was working properly untill the other day the machine
made a reboot (due to the softdog) and the interfaces' configuration
became wrong: the system couldn't find the eth2 interface and also it
tried to asign eth0 a e1000 module, but it couldn't, so it didn't
result in a good rising of the interface and failed to be up.
Indeed, the e100 module was not loaded (consulting via lsmod)

When I tried to re-configure the interfaces trough the redhat-config-
networg assistant, then appeared a message box telling me that I was
wrongly trying to asign a e100 module to eth0 while it needed a e1000
module (it's false).

It seems like someone is saying that interface eth0 needs a e1000
module, but neither the /etc/module.conf file, nor the /etc/sysconfig/
network-scripts/ifcfg-ethX files had changed.

I looked at the /etc/sysconfig/hwconf file and it was the same like
few weeks ago. No changes. But I realized that on the interface name
especification, the COMPLETE interface name was not correct.
I mean, it was written just eth, without 0, 1 or 2, insteed of
eth0,eth1,eth2.

The file hwconf network part is like this:

class: NETWORK
bus: PCI
detached: 0
device: eth
driver: e100
desc: "Intel Corp.|82801BD PRO/100 VE (LOM) Ethernet Controller"
vendorId: 8086
deviceId: 1039
subVendorId: 8086
subDeviceId: 103a
pciType: 1
-
class: NETWORK
bus: PCI
detached: 0
device: eth
driver: e1000
desc: "Unknown vendor|Generic e1000 device"
vendorId: 8086
deviceId: 1076
subVendorId: 8086
subDeviceId: 1076
pciType: 1
-
class: NETWORK
bus: PCI
detached: 0
device: eth
driver: e1000
desc: "Unknown vendor|Generic e1000 device"
vendorId: 8086
deviceId: 1027
subVendorId: 8086
subDeviceId: 1027
pciType: 1


In other (newer) RedHat systems (kernel 2.6.9-55), interface name in
that file is complete (eth0, eth1, eth2).


The /etc/modules.conf file is like this:
alias eth0 e100
alias eth1 e1000
alias eth2 e1000


Does anybody knows if there's a bug in hwconf file or something
related with those files? I was several days looking for a clue about
that, but I haven't find anything.


Thanks for any advice,
Fionn
.

Relevant Pages

  • Re: FreeBSD 8.0 retires into itself
    ... |> One physical interface is in trunk mode to configure these two ... |> interrupts eat about only 6-7% of CPU time ... |You need to check your network setups: ... With multiple NICs if ...
    (freebsd-questions)
  • Re: [SOLVED!!] Re: can i completely delete and recreate my network interfaces?
    ... man ifrename ... 08:07.0 Network controller: Broadcom Corporation BCM4318 [AirForce One ... recipe to restore my eth0 interface? ...
    (Fedora)
  • Re: FreeBSD 8.0 retires into itself
    ... |> One physical interface is in trunk mode to configure these two ... |> interrupts eat about only 6-7% of CPU time ... |You need to check your network setups: ... With multiple NICs if ...
    (freebsd-questions)
  • Re: Internet interface problem
    ... The selection of the eth0 interface, into which the DSL cable coming ... KNetworkConf ... UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 ...
    (Debian-User)
  • Re: Setting up dhcp-server on my desktop machine SOLVED
    ... Your server is configured to use dhcp to acquire a network address? ... For your own sanity you probably want to add 'auto eth0' in addition ... But in error you have set a second gateway on your secondary interface ...
    (Debian-User)