Intel e1000 Problem

ftk · #1 12th September 2006, 06:00 PM

Heya guys+gals,
I have spent all morning trying to get the integrated dual NIC working on our new server box in FC5, Kernel 2.6.15-1.2054-FC5.

It didn't recognize the devices automatically, ended up installing the Intel e1000 driver manually from http://sourceforge.net/projects/e1000/. That all worked fine and dandy, got them listed in lspci, the module is loaded as indicated by lsmod|grep e1000 and the ports are even listed in the Network Configuration dialog in gnome.

The problem is when I try to bring the interface(s) up using either the gnome tool or ifup, I keep getting the following error:
"e1000 device eth0 does not seem to be present, delaying initialization"

I've googled and googled, but nothing is working for me. I hope some of you have a couple of ideas for me.

Thanks a lot,
Felix

David Becker · #2 12th September 2006, 06:05 PM

What does 'lspci -vv' have to say about the card ? And /etc/interrupts and /etc/devices ?

ftk · #3 12th September 2006, 07:49 PM

lspci -vv

Code:

06:00.0 Ethernet controller: Intel Corporation Enterprise Southbridge DPT LAN Copper (rev 01)
        Subsystem: Super Micro Computer Inc Unknown device 0000
        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 08
        Interrupt: pin A routed to IRQ 11
        Region 0: Memory at c8200000 (32-bit, non-prefetchable) [size=128K]
        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 512 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 a4-36-31-ff-ff-48-30-00

06:00.1 Ethernet controller: Intel Corporation Enterprise Southbridge DPT LAN Copper (rev 01)
        Subsystem: Super Micro Computer Inc Unknown device 0000
        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 08
        Interrupt: pin B routed to IRQ 10
        Region 0: Memory at c8220000 (32-bit, non-prefetchable) [size=128K]
        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 512 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 a4-36-31-ff-ff-48-30-00

There are no /etc/interrupts and /etc/devices files..

havenoclu · #4 12th September 2006, 07:52 PM

what do your ifcfg scripts look like?

Code:

/etc/sysconfig/network-scripts/ifcfg-ethx

ie: ifcfg-eth0, ifcfg-eth1, etc..

ftk · #5 12th September 2006, 07:56 PM

my ifcfg scripts...

Code:

[callminer@WOODCREST1 ~]$ cat /etc/sysconfig/network-scripts/ifcfg-eth0
# Please read /usr/share/doc/initscripts-*/sysconfig.txt
# for the documentation of these parameters.
ONBOOT=yes
USERCTL=no
IPV6INIT=no
PEERDNS=yes
TYPE=Ethernet
DEVICE=eth0
BOOTPROTO=dhcp
DHCP_HOSTNAME=WOODCREST1
[callminer@WOODCREST1 ~]$ cat /etc/sysconfig/network-scripts/ifcfg-eth1
# Please read /usr/share/doc/initscripts-*/sysconfig.txt
# for the documentation of these parameters.
ONBOOT=yes
USERCTL=no
IPV6INIT=no
PEERDNS=yes
TYPE=Ethernet
DEVICE=eth1
BOOTPROTO=dhcp
[callminer@WOODCREST1 ~]$

David Becker · #6 12th September 2006, 08:09 PM

Quote:

Originally Posted by ftk

Heya guys+gals,
I have spent all morning trying to get the integrated dual NIC working on our new server box in FC5, Kernel 2.6.15-1.2054-FC5.

What does 'dmesg' say about the driver loading?

dmesg | grep e1000

And did you disable ACPI ?

David

David Becker · #7 12th September 2006, 08:10 PM

Quote:

Originally Posted by ftk

lspci -vv

There are no /etc/interrupts and /etc/devices files..

Whoops, silly me, I mean /proc/interrupts and (you guessed it) /proc/devices.

What was I thinking ?

David

ftk · #8 12th September 2006, 08:34 PM

David,
dmesg contains no reference to e1000.

Following are /proc/interrupts and /proc/devices:

Code:

[callminer@WOODCREST1 ~]$ cat /proc/interrupts
           CPU0       CPU1       CPU2       CPU3
  0:       6278       2501       2500       2501    IO-APIC-edge  timer
  1:         11          0         28         50    IO-APIC-edge  i8042
  7:          2          0          0          0    IO-APIC-edge  parport0
  8:          0          0          0          0    IO-APIC-edge  rtc
  9:          0          0          0          0   IO-APIC-level  acpi
 12:        619          0        419          0    IO-APIC-edge  i8042
 14:       6070       1151          0          0    IO-APIC-edge  libata
 15:         39          0         89        183    IO-APIC-edge  ide1
 17:          0          0          0          0   IO-APIC-level  uhci_hcd:usb3
 18:          0          0          0          0   IO-APIC-level  uhci_hcd:usb1, ehci_hcd:usb4
 19:          0          0          0          0   IO-APIC-level  uhci_hcd:usb2
NMI:      13744      13706      13682      13657
LOC:      13722      13699      13676      13653
ERR:          3
MIS:          0
[callminer@WOODCREST1 ~]$ cat /proc/devices
Character devices:
  1 mem
  4 /dev/vc/0
  4 tty
  4 ttyS
  5 /dev/tty
  5 /dev/console
  5 /dev/ptmx
  6 lp
  7 vcs
 10 misc
 13 input
 21 sg
 29 fb
128 ptm
136 pts
180 usb
189 usb_device
202 cpu/msr
203 cpu/cpuid
216 rfcomm
254 pcmcia

Block devices:
  1 ramdisk
  1 ramdisk
  2 fd
  8 sd
  9 md
 22 ide1
 65 sd
 66 sd
 67 sd
 68 sd
 69 sd
 70 sd
 71 sd
128 sd
129 sd
130 sd
131 sd
132 sd
133 sd
134 sd
135 sd
253 device-mapper
254 mdp
[callminer@WOODCREST1 ~]$

Thank you for your time,
Felix

EDIT: ACPI is enabled.

David Becker · #9 12th September 2006, 08:43 PM

Quote:

Originally Posted by ftk

David,
dmesg contains no reference to e1000.

Apparently the driver isn't loading. You'll have to see what's failing when loading the module. Remove the module and load it again while checking logs for error messages.

David