NOT GONNA WORK Ethernet Controller?

I’ve got an embedded single-board-computer from AdLink (NP-770), with
integrated 82559 Ethernet controller. nicinfo reports the following data.
What are the implications of “NOT GONNA WORK” vs. “INTEL 8255x”? Is there a
problem with this board?

Thanks,
Marty

NOT GONNA WORK Ethernet Controller
Physical Node ID … 003064 010A26
Current Physical Node ID … 003064 010A26
Media Rate … 100.00 Mb/s half-duplex UTP
MTU … 1514
Lan … 0
I/O Port Range … 0xC000 → 0xC03F
Hardware Interrupt … 0xB
Promiscuous … Disabled
Multicast … Enabled

Total Packets Txd OK … 241420
Total Packets Txd Bad … 0
Total Packets Rxd OK … 444428
Total Rx Errors … 0

Total Bytes Txd … 62000005
Total Bytes Rxd … 106927246

Tx Collision Errors … 0
Tx Collisions Errors (aborted) … 0
Carrier Sense Lost on Tx … 0
FIFO Underruns During Tx … 4
Tx deferred … 0
Out of Window Collisions … 0
FIFO Overruns During Rx … 0
Alignment errors … 59
CRC errors … 76

“Marty Doane” <marty.doane@rapistan.com> wrote in message
news:9qhbq9$59a$1@inn.qnx.com

I’ve got an embedded single-board-computer from AdLink (NP-770), with
integrated 82559 Ethernet controller. nicinfo reports the following data.
What are the implications of “NOT GONNA WORK” vs. “INTEL 8255x”? Is there
a
problem with this board?

Thanks,
Marty

NOT GONNA WORK Ethernet Controller

LOL!

Hi Marty,

That really doesn’t appear does it?

E.


Marty Doane <marty.doane@rapistan.com> wrote:

I’ve got an embedded single-board-computer from AdLink (NP-770), with
integrated 82559 Ethernet controller. nicinfo reports the following data.
What are the implications of “NOT GONNA WORK” vs. “INTEL 8255x”? Is there a
problem with this board?

Thanks,
Marty

NOT GONNA WORK Ethernet Controller
Physical Node ID … 003064 010A26
Current Physical Node ID … 003064 010A26
Media Rate … 100.00 Mb/s half-duplex UTP
MTU … 1514
Lan … 0
I/O Port Range … 0xC000 → 0xC03F
Hardware Interrupt … 0xB
Promiscuous … Disabled
Multicast … Enabled

Total Packets Txd OK … 241420
Total Packets Txd Bad … 0
Total Packets Rxd OK … 444428
Total Rx Errors … 0

Total Bytes Txd … 62000005
Total Bytes Rxd … 106927246

Tx Collision Errors … 0
Tx Collisions Errors (aborted) … 0
Carrier Sense Lost on Tx … 0
FIFO Underruns During Tx … 4
Tx deferred … 0
Out of Window Collisions … 0
FIFO Overruns During Rx … 0
Alignment errors … 59
CRC errors … 76

Sure does. It’s a straight unedited capture of nicinfo output.

One of the reasons I posted this message is that I’m seeing inconsistent
network behavior with these cards. For example, when I ftp to another box on
the same subnet, a “put” of a 1 MB file completes in less that 1 second, but
a get of the same file takes more than 30 seconds. I haven’t ruled out a
routing problem or some other configuration issue, but this nicinfo output
sure caught my attention.

Marty

“Hardware Support Account” <hw@qnx.com> wrote in message
news:9qhmgs$mq2$1@nntp.qnx.com

Hi Marty,

That really doesn’t appear does it?

E.


Marty Doane <> marty.doane@rapistan.com> > wrote:
I’ve got an embedded single-board-computer from AdLink (NP-770), with
integrated 82559 Ethernet controller. nicinfo reports the following
data.
What are the implications of “NOT GONNA WORK” vs. “INTEL 8255x”? Is
there a
problem with this board?

Thanks,
Marty

NOT GONNA WORK Ethernet Controller
Physical Node ID … 003064 010A26
Current Physical Node ID … 003064 010A26
Media Rate … 100.00 Mb/s half-duplex UTP
MTU … 1514
Lan … 0
I/O Port Range … 0xC000 → 0xC03F
Hardware Interrupt … 0xB
Promiscuous … Disabled
Multicast … Enabled

Total Packets Txd OK … 241420
Total Packets Txd Bad … 0
Total Packets Rxd OK … 444428
Total Rx Errors … 0

Total Bytes Txd … 62000005
Total Bytes Rxd … 106927246

Tx Collision Errors … 0
Tx Collisions Errors (aborted) … 0
Carrier Sense Lost on Tx … 0
FIFO Underruns During Tx … 4
Tx deferred … 0
Out of Window Collisions … 0
FIFO Overruns During Rx … 0
Alignment errors … 59
CRC errors … 76

Previously, Marty Doane wrote in qdn.public.qnxrtp.os:

I’ve got an embedded single-board-computer from AdLink (NP-770), with
integrated 82559 Ethernet controller. nicinfo reports the following data.
What are the implications of “NOT GONNA WORK” vs. “INTEL 8255x”? Is there a
problem with this board?

Yes, the Intel spec only defines controller types 1 & 2 and yours has
a controller type of 3 in the EEPROM. We don’t know what this is,
hence the nicinfo message! I have the very latest spec. from Intel and
there is still no controller type of 3 defined in the EEPROM.
The output from ‘pci -v’ might help.

Thanks,
Marty

NOT GONNA WORK Ethernet Controller
Physical Node ID … 003064 010A26
Current Physical Node ID … 003064 010A26
Media Rate … 100.00 Mb/s half-duplex UTP
MTU … 1514
Lan … 0
I/O Port Range … 0xC000 → 0xC03F
Hardware Interrupt … 0xB
Promiscuous … Disabled
Multicast … Enabled

Total Packets Txd OK … 241420
Total Packets Txd Bad … 0
Total Packets Rxd OK … 444428
Total Rx Errors … 0

Total Bytes Txd … 62000005
Total Bytes Rxd … 106927246

Tx Collision Errors … 0
Tx Collisions Errors (aborted) … 0
Carrier Sense Lost on Tx … 0
FIFO Underruns During Tx … 4
Tx deferred … 0
Out of Window Collisions … 0
FIFO Overruns During Rx … 0
Alignment errors … 59
CRC errors … 76
\

pci -v as requested:


PCI version = 2.10

Class = Bridge (Host/PCI)
Vendor ID = 8086h, Intel Corporation
Device ID = 7120h, 82810 Host-Hub Interface Bridge / DRAM Ctrlr
PCI index = 0h
Class Codes = 060000h
Revision ID = 3h
Bus number = 0
Device number = 0
Function num = 0
Status Reg = 2080h
Command Reg = 6h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h
Subsystem Vendor ID = 8086h
Subsystem ID = 7120h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = NC
Interrupt line = 0

Class = Display (VGA)
Vendor ID = 8086h, Intel Corporation
Device ID = 7121h, 82810 Graphics Device
PCI index = 0h
Class Codes = 030000h
Revision ID = 3h
Bus number = 0
Device number = 1
Function num = 0
Status Reg = 2b0h
Command Reg = 7h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h
PCI Mem Address = d0000000h prefetchable 32bit length 67108864 enabled
PCI Mem Address = d4200000h 32bit length 524288 enabled
Subsystem Vendor ID = 8086h
Subsystem ID = 7121h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT A
Interrupt line = 10
Capabilities Pointer = dch
Capability ID = 1h
Capabilities = 21h - 0h

Class = Bridge (PCI/PCI)
Vendor ID = 8086h, Intel Corporation
Device ID = 2418h, 82801AA Hub Interface-to-PCI Bridge
PCI index = 0h
Class Codes = 060400h
Revision ID = 2h
Bus number = 0
Device number = 30
Function num = 0
Status Reg = 80h
Command Reg = 107h
Header type = 1h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h
Primary Bus Number = 0h
Secondary Bus Number = 1h
Subordinate Bus Number = 1h
Secondary Latency Timer = 20h
I/O Base = c0h
I/O Limit = c0h
Secondary Status = 2280h
Memory Base = d400h
Memory Limit = d410h
Prefetchable Memory Base = fff0h
Prefetchable Memory Limit= 0h
Prefetchable Base Upper 32 Bits = 0h
Prefetchable Limit Upper 32 Bits = 0h
I/O Base Upper 16 Bits = ffffh
I/O Limit Upper 16 Bits = ffffh
Bridge Control = 6ns
PCI Int Pin = NC
Interrupt line = 0

Class = Bridge (PCI/ISA)
Vendor ID = 8086h, Intel Corporation
Device ID = 2410h, 82801AA LPC Interface
PCI index = 0h
Class Codes = 060100h
Revision ID = 2h
Bus number = 0
Device number = 31
Function num = 0
Status Reg = 280h
Command Reg = fh
Header type = 0h Multi-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = NC
Interrupt line = 0

Class = Mass Storage (IDE)
Vendor ID = 8086h, Intel Corporation
Device ID = 2411h, 82801AA IDE Controller
PCI index = 0h
Class Codes = 010180h
Revision ID = 2h
Bus number = 0
Device number = 31
Function num = 1
Status Reg = 280h
Command Reg = 5h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h
PCI IO Address = f000h length 16 enabled
Subsystem Vendor ID = 8086h
Subsystem ID = 2411h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = NC
Interrupt line = 0

Class = Serial Bus (Universal Serial Bus)
Vendor ID = 8086h, Intel Corporation
Device ID = 2412h, 82801AA USB Controller
PCI index = 0h
Class Codes = 0c0300h
Revision ID = 2h
Bus number = 0
Device number = 31
Function num = 2
Status Reg = 280h
Command Reg = 5h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h
PCI IO Address = d000h length 32 enabled
Subsystem Vendor ID = 8086h
Subsystem ID = 2412h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT D
Interrupt line = 11

Class = Network (Ethernet)
Vendor ID = 8086h, Intel Corporation
Device ID = 1229h, 82557/8/9 Fast Ethernet LAN Controller
PCI index = 0h
Class Codes = 020000h
Revision ID = 8h
Bus number = 1
Device number = 7
Function num = 0
Status Reg = 290h
Command Reg = 7h
Header type = 0h Multi-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 20h
Cache Line Size= 8h un-cacheable
PCI Mem Address = d4100000h 32bit length 4096 enabled
PCI IO Address = c000h length 64 enabled
PCI Mem Address = d4000000h 32bit length 1048576 enabled
Subsystem Vendor ID = 8086h
Subsystem ID = 1h
Max Lat = 56ns
Min Gnt = 8ns
PCI Int Pin = INT A
Interrupt line = 11
Capabilities Pointer = dch
Capability ID = 1h
Capabilities = fe22h - 3a004000h






“Hugh Brown” <hsbrown@qnx.com> wrote in message
news:Voyager.011016140758.14109X@node90.ott.qnx.com

Previously, Marty Doane wrote in qdn.public.qnxrtp.os:
I’ve got an embedded single-board-computer from AdLink (NP-770), with
integrated 82559 Ethernet controller. nicinfo reports the following
data.
What are the implications of “NOT GONNA WORK” vs. “INTEL 8255x”? Is
there a
problem with this board?


Yes, the Intel spec only defines controller types 1 & 2 and yours has
a controller type of 3 in the EEPROM. We don’t know what this is,
hence the nicinfo message! I have the very latest spec. from Intel and
there is still no controller type of 3 defined in the EEPROM.
The output from ‘pci -v’ might help.

Thanks,
Marty

NOT GONNA WORK Ethernet Controller
Physical Node ID … 003064 010A26
Current Physical Node ID … 003064 010A26
Media Rate … 100.00 Mb/s half-duplex UTP
MTU … 1514
Lan … 0
I/O Port Range … 0xC000 → 0xC03F
Hardware Interrupt … 0xB
Promiscuous … Disabled
Multicast … Enabled

Total Packets Txd OK … 241420
Total Packets Txd Bad … 0
Total Packets Rxd OK … 444428
Total Rx Errors … 0

Total Bytes Txd … 62000005
Total Bytes Rxd … 106927246

Tx Collision Errors … 0
Tx Collisions Errors (aborted) … 0
Carrier Sense Lost on Tx … 0
FIFO Underruns During Tx … 4
Tx deferred … 0
Out of Window Collisions … 0
FIFO Overruns During Rx … 0
Alignment errors … 59
CRC errors … 76

\

My $0.02… This is a good thing to do. I bet Marty has wasted a lot
less time, due to the straightforward message; however, one step better,
don’t even mount the driver (without a special option) if it isn’t going
to work.

-----Original Message-----
From: Hugh Brown [mailto:hsbrown@qnx.com]
Posted At: Tuesday, October 16, 2001 11:08 AM
Posted To: os
Conversation: NOT GONNA WORK Ethernet Controller?
Subject: Re: NOT GONNA WORK Ethernet Controller?


Previously, Marty Doane wrote in qdn.public.qnxrtp.os:

I’ve got an embedded single-board-computer from AdLink (NP-770), with
integrated 82559 Ethernet controller. nicinfo reports the following
data.
What are the implications of “NOT GONNA WORK” vs. “INTEL 8255x”? Is
there a
problem with this board?

Yes, the Intel spec only defines controller types 1 & 2 and yours has
a controller type of 3 in the EEPROM. We don’t know what this is,
hence the nicinfo message! I have the very latest spec. from Intel and
there is still no controller type of 3 defined in the EEPROM.
The output from ‘pci -v’ might help.

Thanks,
Marty

NOT GONNA WORK Ethernet Controller
Physical Node ID … 003064 010A26
Current Physical Node ID … 003064 010A26
Media Rate … 100.00 Mb/s half-duplex UTP
MTU … 1514
Lan … 0
I/O Port Range … 0xC000 → 0xC03F
Hardware Interrupt … 0xB
Promiscuous … Disabled
Multicast … Enabled

Total Packets Txd OK … 241420
Total Packets Txd Bad … 0
Total Packets Rxd OK … 444428
Total Rx Errors … 0

Total Bytes Txd … 62000005
Total Bytes Rxd … 106927246

Tx Collision Errors … 0
Tx Collisions Errors (aborted) … 0
Carrier Sense Lost on Tx … 0
FIFO Underruns During Tx … 4
Tx deferred … 0
Out of Window Collisions … 0
FIFO Overruns During Rx … 0
Alignment errors … 59
CRC errors … 76
\