Fedora Linux Support Community & Resources Center

Go Back   FedoraForum.org > Fedora 17/18 > Servers & Networking
FedoraForum Search

Forgot Password? Join Us!

Servers & Networking Discuss any Fedora server problems and Networking issues such as dhcp, IP numbers, wlan, modems, etc.

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 11th September 2006, 05:06 AM
Doc Walker Offline
Registered User
 
Join Date: Sep 2006
Posts: 2
Help w/error '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:

Code:
$ 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]
Code:
$ 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
  • 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:

Code:
$ sudo modprobe e1000
$ dmesg
...
Intel(R) PRO/1000 Network Driver - version 6.3.9-k4-NAPI
Copyright (c) 1999-2005 Intel Corporation.
Code:
$ 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
...
Code:
$ sudo lsmod
Module    Size  Used by
...
e1000   103853  0
...
Code:
$ sudo ifconfig eth0 10.203.0.3
SIOCSIFADDR: No such device
eth0: unknown interface: No such device
Code:
$ 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
Reply With Quote
  #2  
Old 14th September 2006, 02:56 AM
Doc Walker Offline
Registered User
 
Join Date: Sep 2006
Posts: 2
SOLVED: FC6t2 recognizes the Ethernet ports OK

PROBLEM SOLVED; this response is for the archives.

It appears that Fedora Core 6 Test 2 properly recognizes the Ethernet ports onboard the Intel S5000PAL motherboard. Thanks to the folks at FedoraUnity.org for making the FC6t2 Live-Spin DVD available so I could easily boot up a new system to test the networking facilities.

Code:
$ uname -r
2.6.17-1.2517.fc6
Code:
$ dmesg
...
Intel(R) PRO/1000 Network Driver - version 7.1.9-k4-NAPI
Copyright (c) 1999-2006 Intel Corporation.
...
e1000: 0000:05:00.0: e1000_probe: (PCI Express:2.5Gb/s:Width x4) 00:04:23:d3:05:7a
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
e1000: 0000:05:00.1: e1000_probe: (PCI Express:2.5Gb/s:Width x4) 00:04:23:d3:05:7b
e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection
e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex
e1000: eth0: e1000_watchdog: 10/100 speed: disabling TSO
Code:
$ sudo lspci -vv
...
05:00.0 Ethernet controller: Intel Corporation 631xESB/632xESB DPT LAN Controller 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: 64 bytes
        Interrupt: pin A routed to IRQ 106
        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: 00000000fee00000  Data: 406a
        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

05:00.1 Ethernet controller: Intel Corporation 631xESB/632xESB DPT LAN Controller 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: 64 bytes
        Interrupt: pin B routed to IRQ 82
        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
...
Code:
$ sudo lsmod
Module                  Size  Used by
...
e1000                 168488  0 
...
Code:
$ sudo ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:04:23:D3:05:7A  
          inet addr:10.201.0.3  Bcast:10.201.0.255  Mask:255.255.255.0
          inet6 addr: fe80::204:23ff:fed3:57a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1171 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2300 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:378576 (369.7 KiB)  TX bytes:251214 (245.3 KiB)
          Base address:0x2020 Memory:b8820000-b8840000
Reply With Quote
Reply

Tags
delaying, device, e1000, eth0, initialization, present, w or error

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
eth0 device does not seems to be present , delaying initialization neha Servers & Networking 6 10th June 2008 08:40 PM
FC6: ipw2200 device eth1 does not seem to be present, delaying initialization. Jugmun Servers & Networking 7 12th August 2007 11:42 AM
ipw3945 device eth1 does not seem to be present, delaying initialization on Fedora 7 linuxKJ Servers & Networking 6 1st August 2007 12:25 AM
ipw2100 device eth1 does not seem to be present, delaying initialization. gpiva Hardware & Laptops 7 2nd December 2006 11:39 PM


Current GMT-time: 20:07 (Wednesday, 22-05-2013)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat