[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

e1000 device eth0 does not seem to be present, delaying initialization



I'm in the process of setting up a new server and have been unable to
get the NICs working properly. Specifically, I'm requesting help with
the following error while trying to bring up the network interface via:

$ sudo service network restart

Shutting down loopback interface:  [  OK  ]
Bringing up loopback interface:    [  OK  ]
Bringing up interface eth0:  e1000 device eth0 does not seem to be
present, delaying intitialization.
                                   [FAILED]
Bringing up interface eth1:  e1000 device eth1 does not seem to be
present, delaying intitialization.
                                   [FAILED]

$ uname -r
2.6.15-1.2054_FC5smp

Hardware:
- (2) Intel 5110 Xeon Dual-Core processors
- (1) Intel S5000PAL server board w/(2) on-board NICs

Software:
- Updated server board BIOS via included Intel S5000PAL Server
Deployment Toolkit 2.0 CD (this is an ISOLINUX CD with Intel's
deployment software which connected to intel.com via the on-board
NIC--proving the network hardware works)
- Installed Intel's Linux* Base Driver for the IntelĀ® PRO/1000 Family of
Adapters <http://downloadmirror.intel.com/df-support/11518/ENG/e1000.htm>
- Fedora Core 5 x86_64 DVD (tried this first, fresh install)
- Fedora Core 5 i386 DVD (tried this second, another fresh install)

I've googled for the error message and followed the advice on various
forums for detecting whether the NIC is visible to the OS:

$ sudo modprobe e1000
$ dmesg
...
Intel(R) PRO/1000 Network Driver - version 6.3.9-k4-NAPI
Copyright (c) 1999-2005 Intel Corporation.

$ sudo lspci -vv
...
05:00.0 Ethernet controller: Intel Corporation Enterprise Southbridge
DPT LAN Copper (rev 01)
        Subsystem: Intel Corporation Unknown device 346c
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr+ Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 0, Cache Line Size 10
        Interrupt: pin A routed to IRQ 5
        Region 0: Memory at b8820000 (32-bit, non-prefetchable) [size=128K]
        Region 1: Memory at b8400000 (32-bit, non-prefetchable) [size=4M]
        Region 2: I/O ports at 2020 [size=32]
        Capabilities: [c8] Power Management version 2
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=1 PME-
        Capabilities: [d0] Message Signalled Interrupts: 64bit+
Queue=0/0 Enable-
                Address: 0000000000000000  Data: 0000
        Capabilities: [e0] Express Endpoint IRQ 0
                Device: Supported: MaxPayload 256 bytes, PhantFunc 0,
ExtTag-
                Device: Latency L0s <512ns, L1 <64us
                Device: AtnBtn- AtnInd- PwrInd-
                Device: Errors: Correctable+ Non-Fatal+ Fatal+ Unsupported-
                Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
                Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
                Link: Supported Speed 2.5Gb/s, Width x4, ASPM unknown,
Port 0
                Link: Latency L0s <128ns, L1 <64us
                Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch-
                Link: Speed 2.5Gb/s, Width x4
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Device Serial Number 7a-05-d3-ff-ff-23-04-00

05:00.1 Ethernet controller: Intel Corporation Enterprise Southbridge
DPT LAN Copper (rev 01)
        Subsystem: Intel Corporation Unknown device 346c
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr+ Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 0, Cache Line Size 10
        Interrupt: pin B routed to IRQ 11
        Region 0: Memory at b8800000 (32-bit, non-prefetchable) [size=128K]
        Region 1: Memory at b8000000 (32-bit, non-prefetchable) [size=4M]
        Region 2: I/O ports at 2000 [size=32]
        Capabilities: [c8] Power Management version 2
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=1 PME-
        Capabilities: [d0] Message Signalled Interrupts: 64bit+
Queue=0/0 Enable-
                Address: 0000000000000000  Data: 0000
        Capabilities: [e0] Express Endpoint IRQ 0
                Device: Supported: MaxPayload 256 bytes, PhantFunc 0,
ExtTag-
                Device: Latency L0s <512ns, L1 <64us
                Device: AtnBtn- AtnInd- PwrInd-
                Device: Errors: Correctable+ Non-Fatal+ Fatal+ Unsupported-
                Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
                Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
                Link: Supported Speed 2.5Gb/s, Width x4, ASPM unknown,
Port 0
                Link: Latency L0s <128ns, L1 <64us
                Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch-
                Link: Speed 2.5Gb/s, Width x4
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Device Serial Number 7a-05-d3-ff-ff-23-04-00
...

$ sudo lsmod
Module    Size  Used by
...
e1000   103853  0
...

$ sudo ifconfig eth0 10.203.0.3
SIOCSIFADDR: No such device
eth0: unknown interface: No such device

$ sudo ifup eth0
e1000 device eth0 does not seem to be present, delaying initialization.

I'm confident that the NIC works properly since I was able to download
the BIOS update from intel.com via the Intel Server Deployment CD. Both
port status LEDs are green, indicating a live connection at 100 MB/sec.
My router is set to assign IP addresses via DHCP and each MAC address
shows up in the router's Attached Devices list.

What am I missing here?

Rx


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]