Rafael Tapia(deleted)
|
interface not coming up when using e1000 driver on i82580
|
Rafael Tapia(deleted)
01/30/2015 6:56 PM
post113166
|
interface not coming up when using e1000 driver on i82580
This is our setup:
CPU:X86 Release:6.5.0 FreeMem:1681Mb/2047Mb BootTime:Jan 30 21:13:52 UTC 2015
Processes: 23, Threads: 82
Processor1: 66222 Intel 686 F6M12S2 1331MHz FPU
Processor2: 66222 Intel 686 F6M12S2 1330MHz FPU
QNX Version:
QNX NGDAQ 6.5.0 2010/07/09-14:43:36EDT x86pc x86
Network driver version:
NAME=devnp-e1000.so
DESCRIPTION=Driver for Intel 82544 Gigabit Ethernet controllers
DATE=2013/04/12-08:13:50-EDT
STATE=Experimental
HOST=node321
USER=hsbrown
pci network related info:
Class = Network (Ethernet)
Vendor ID = 8086h, Intel Corporation
Device ID = 10d3h, 82574L Gigabit Network Connection
PCI index = 0h
BAR - 0 [Mem] = ff000000h enabled
BAR - 2 [I/O] = e000h enabled
BAR - 3 [Mem] = ff020000h enabled
PCI Int Pin = INT A
Interrupt line = 0
CPU Interrupt = 100h
Class = Network (Ethernet)
Vendor ID = 8086h, Intel Corporation
Device ID = 150eh, 82580 Gigabit Network Connection
PCI index = 0h
BAR - 0 [Mem] = ff100000h enabled
BAR - 3 [Mem] = ff180000h enabled
PCI Expansion ROM = 0h disabled
PCI Int Pin = INT A
Interrupt line = 6
CPU Interrupt = 106h
Class = Network (Ethernet)
Vendor ID = 8086h, Intel Corporation
Device ID = 150eh, 82580 Gigabit Network Connection
PCI index = 1h
BAR - 0 [Mem] = ff200000h enabled
BAR - 3 [Mem] = ff280000h enabled
PCI Int Pin = INT B
Interrupt line = 16
CPU Interrupt = 110h
Class = Network (Ethernet)
Vendor ID = 8086h, Intel Corporation
Device ID = 150eh, 82580 Gigabit Network Connection
PCI index = 2h
BAR - 0 [Mem] = ff300000h enabled
BAR - 3 [Mem] = ff380000h enabled
PCI Int Pin = INT C
Interrupt line = 26
CPU Interrupt = 11ah
Class = Network (Ethernet)
Vendor ID = 8086h, Intel Corporation
Device ID = 150eh, 82580 Gigabit Network Connection
PCI index = 3h
BAR - 0 [Mem] = ff400000h enabled
BAR - 3 [Mem] = ff480000h enabled
PCI Int Pin = INT D
Interrupt line = 36
CPU Interrupt = 124h
Our start up scripts load the e100driver as such: io-pkt-v4 -v -de1000
and we then we use ifconfig to set the ip information:
ifconfig wm0 10.10.0.190 netmask 255.255.255.128
ifconfig wm1 10.1.0.191 netmask 255.255.255.0
ifconfig wm2 192.168.1.192 netmask 255.255.255.0
ifconfig wm3 10.3.0.193 netmask 255.255.255.0
The problem is that once we come up wm3 is still down:
wm3:
INTEL PRO/1000 Gigabit (Copper) Ethernet Controller
Link is DOWN
Physical Node ID ........................... C4C19F 000059
Current Physical Node ID ................... C4C19F 000059
Current Operation Rate ..................... 0 kb/s half-duplex
Active Interface Type ...................... MII
Active PHY address ....................... 1
Maximum Transmittable data Unit ............ 1500
Maximum Receivable data Unit ............... 1500
Hardware Interrupt ......................... 0x11a
Hardware Interrupt ......................... 0x11b
Hardware Interrupt ......................... 0x11c
Memory Aperture ............................ 0xff300000 - 0xff37ffff
Promiscuous Mode ........................... Off
Multicast Support .......................... Enabled
Packets Transmitted OK ..................... 0
Bytes Transmitted OK ....................... 0
Broadcast Packets Transmitted OK ........... 0
Multicast Packets Transmitted OK ........... 0
Memory Allocation Failures on Transmit ..... 0
Packets Received OK ........................ 0
Bytes Received OK .......................... 0
Broadcast Packets Received OK .............. 0
Multicast Packets Received OK .............. 0
Memory Allocation Failures on Receive ...... 0
Single Collisions on Transmit .............. 0
Multiple Collisions on Transmit ............ 0
Deferred Transmits ......................... 0
Late Collision on Transmit errors .......... 0
...
View Full Message
|
|
|