3com 3c900 and etherexpress 16 troubles...

I have two network cards available to me and I am at a lost to explain their
behavior.

First, the old Intel Etherexpress 16. Since this is a legacy ISA card, I
have to set my bios to legacy for irq 5 to use this card in Win98 and Linux
(Mandrake 7.2). However, even with this set the card is not recognized in
QNX RTOS. I have tried slay io-net then calling it manually with
io-net -deepro ioport=0x310,irq=5 -pttcpip
but this resulted in an error in the dll: device not found.
In Linux, the Etherexpress pro driver works just fine. In Windows it calls
it Etherexpress 16 or 16 tpa. Any pointers on getting this to work in QNX
RTOS would be welcome. note: nettrap does not find this card.

Second, is a 3com 3c900 PCI. Its behavior I do not understand. With most
10-base-T cards, as soon as the system has power the connection light will
be lit. But with this card, it does not. This card works in windows (it is
PnP I am told), but the connection light does not come on until after the
Windows splash screen closes. In Linux, it appear to find and set up the
card, but the connection light did not light and it was unable to connect to
the network (local or remote). Pinging a working result resulted in an
error. In QNX RTOS, it appear to auto detect the card, so I went to network
cfg and entered my local network data under the network tab. Under the
device tab, I checked the box to activate this device, but still the
connection light on the card did not light. What is windows doing that
allows this card to “come alive” that the other two operating systems are
not doing?

I would prefer to use the 3com card, if possible, but would be willing to be
on the network with either.

Thank you for your time.

Previously, lantis wrote in qdn.public.qnxrtp.installation:

I have two network cards available to me and I am at a lost to explain their
behavior.

First, the old Intel Etherexpress 16. Since this is a legacy ISA card, I
have to set my bios to legacy for irq 5 to use this card in Win98 and Linux
(Mandrake 7.2). However, even with this set the card is not recognized in
QNX RTOS. I have tried slay io-net then calling it manually with
io-net -deepro ioport=0x310,irq=5 -pttcpip
but this resulted in an error in the dll: device not found.
In Linux, the Etherexpress pro driver works just fine. In Windows it calls
it Etherexpress 16 or 16 tpa. Any pointers on getting this to work in QNX
RTOS would be welcome. note: nettrap does not find this card.

I suspect that this is a Plug 'n Play card. You will have to run the DOS
utility against this adapter and configure it manually and turn off Plug
'n Play.

Second, is a 3com 3c900 PCI. Its behavior I do not understand. With most
10-base-T cards, as soon as the system has power the connection light will
be lit. But with this card, it does not. This card works in windows (it is
PnP I am told), but the connection light does not come on until after the
Windows splash screen closes. In Linux, it appear to find and set up the
card, but the connection light did not light and it was unable to connect to
the network (local or remote). Pinging a working result resulted in an
error. In QNX RTOS, it appear to auto detect the card, so I went to network
cfg and entered my local network data under the network tab. Under the
device tab, I checked the box to activate this device, but still the
connection light on the card did not light. What is windows doing that
allows this card to “come alive” that the other two operating systems are
not doing?

I would prefer to use the 3com card, if possible, but would be willing to be
on the network with either.

Thank you for your time.

I only have a 3C900 Combo card and it works fine with the el900 driver.
Please post the output from ‘nicinfo’ as well as ‘pci -v’.

From: “Hugh Brown” <hsbrown@qnx.com>
Subject: Re: 3com 3c900 and etherexpress 16 troubles…


Previously, lantis wrote in qdn.public.qnxrtp.installation:
I have two network cards available to me and I am at a lost to explain
their
behavior.

Second, is a 3com 3c900 PCI. Its behavior I do not understand. With
most
10-base-T cards, as soon as the system has power the connection light
will
be lit. But with this card, it does not. This card works in windows
(it is
PnP I am told), but the connection light does not come on until after
the
Windows splash screen closes. In Linux, it appear to find and set up
the
card, but the connection light did not light and it was unable to
connect to
the network (local or remote). Pinging a working result resulted in an
error. In QNX RTOS, it appear to auto detect the card, so I went to
network
cfg and entered my local network data under the network tab. Under the
device tab, I checked the box to activate this device, but still the
connection light on the card did not light. What is windows doing that
allows this card to “come alive” that the other two operating systems
are
not doing?

I only have a 3C900 Combo card and it works fine with the el900 driver.
Please post the output from ‘nicinfo’ as well as ‘pci -v’.

Here are the results of the output of nicinfo and then pci -v. The media
rate and LAN both being 0 strikes me as strange. Also, the PCI index is 0,
though I have no idea what they should be. Thank you for the help.

RESULT OF nicinfo:

3COM (90x) 10BASE-T/100BASE-TX Ethernet Controller
Physical Node ID … 00104B 32ECCF
Current Physical Node ID … 00104B 32ECCF
Media Rate … 0 kb/s half-duplex UTP
MTU … 1514
Lan … 0
I/O Port Range … 0xE800 → 0xE83F
Hardware Interrupt … 0xA

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

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

RESULT OF pci -v:

PCI version = 2.10

Class = Bridge (Host/PCI)
Vendor ID = 10b9h, Acer Labs Inc.
Device ID = 1541h, M1541 Aladdin V AGPset Host Bridge
PCI index = 0h
Class Codes = 060000h
Revision ID = 4h
Bus number = 0
Device number = 0
Function num = 0
Status Reg = 2410h
Command Reg = 6h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 20h
Cache Line Size= 0h
Subsystem Vendor ID = 10b9h
Subsystem ID = 1541h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = NC
Interrupt line = 0
Capabilities Pointer = b0h
Capability ID = 2h
Capabilities = 10h - 1b000203h

Class = Bridge (PCI/PCI)
Vendor ID = 10b9h, Acer Labs Inc.
Device ID = 5243h, M1541A Aladdin V PCI-to-PCI Bridge
PCI index = 0h
Class Codes = 060400h
Revision ID = 4h
Bus number = 0
Device number = 1
Function num = 0
Status Reg = 400h
Command Reg = 7h
Header type = 1h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 20h
Cache Line Size= 0h
Primary Bus Number = 0h
Secondary Bus Number = 1h
Subordinate Bus Number = 1h
Secondary Latency Timer = 20h
I/O Base = f0h
I/O Limit = 0h
Secondary Status = 2000h
Memory Base = fff0h
Memory Limit = 0h
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 = 4ns
PCI Int Pin = NC
Interrupt line = 0

Class = Serial Bus (Universal Serial Bus)
Vendor ID = 10b9h, Acer Labs Inc.
Device ID = 5237h, M5237 USB Host Controller
PCI index = 0h
Class Codes = 0c0310h
Revision ID = 3h
Bus number = 0
Device number = 2
Function num = 0
Status Reg = 290h
Command Reg = 7h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 20h
Cache Line Size= 8h un-cacheable
Mem Address = e7000000h 32bit length 4096 enabled
Max Lat = 80ns
Min Gnt = 0ns
PCI Int Pin = INT A
Interrupt line = 11
Capabilities Pointer = 60h
Capability ID = 1h
Capabilities = 2h - 0h

Class = Bridge (PCI/ISA)
Vendor ID = 10b9h, Acer Labs Inc.
Device ID = 1533h, M1533 PCI South Bridge
PCI index = 0h
Class Codes = 060100h
Revision ID = c3h
Bus number = 0
Device number = 7
Function num = 0
Status Reg = 210h
Command Reg = fh
Header type = 0h Single-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
Capabilities Pointer = f0h
Capability ID = 1h
Capabilities = 2h - 0h

Class = Multimedia (Audio)
Vendor ID = 1274h, Ensoniq
Device ID = 1371h, ES1371 AudioPCI
PCI index = 0h
Class Codes = 040100h
Revision ID = 2h
Bus number = 0
Device number = 8
Function num = 0
Status Reg = 410h
Command Reg = 5h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 20h
Cache Line Size= 0h
IO Address = e000h length 64 enabled
Subsystem Vendor ID = 1274h
Subsystem ID = 1371h
Max Lat = 128ns
Min Gnt = 12ns
PCI Int Pin = INT A
Interrupt line = 10
Capabilities Pointer = dch
Capability ID = 1h
Capabilities = 6c31h - 0h

Class = Display (VGA)
Vendor ID = 121ah, 3dfx Interactive Inc
Device ID = 3h, Voodoo Banshee Voodoo Banshee
PCI index = 0h
Class Codes = 030000h
Revision ID = 3h
Bus number = 0
Device number = 10
Function num = 0
Status Reg = 210h
Command Reg = 23h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h
Mem Address = e0000000h 32bit length 33554432 enabled
Mem Address = e2000000h prefetchable 32bit length 33554432 enabled
IO Address = e400h length 256 enabled
Subsystem Vendor ID = 1102h
Subsystem ID = 1017h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT A
Interrupt line = 5
Capabilities Pointer = 60h
Capability ID = 1h
Capabilities = 21h - 0h

Class = Network (Ethernet)
Vendor ID = 10b7h, 3Com Corporation
Device ID = 9000h, 3C900-TPO Fast Etherlink XL PCI 10
PCI index = 0h
Class Codes = 020000h
Revision ID = 0h
Bus number = 0
Device number = 12
Function num = 0
Status Reg = 200h
Command Reg = 7h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 20h
Cache Line Size= 0h
IO Address = e800h length 64 enabled
Expansion ROM = e6000000h length 65536 disabled
Max Lat = 8ns
Min Gnt = 3ns
PCI Int Pin = INT A
Interrupt line = 10

Class = Mass Storage (IDE)
Vendor ID = 10b9h, Acer Labs Inc.
Device ID = 5229h, M1543 Southbridge EIDE Controller
PCI index = 0h
Class Codes = 0101fah
Revision ID = c2h
Bus number = 0
Device number = 15
Function num = 0
Status Reg = 290h
Command Reg = 5h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 20h
Cache Line Size= 0h
IO Address = f000h length 16 enabled
Max Lat = 4ns
Min Gnt = 2ns
PCI Int Pin = INT A
Interrupt line = 0
Capabilities Pointer = 60h
Capability ID = 1h
Capabilities = 2h - 0h

Previously, lantis wrote in qdn.public.qnxrtp.installation:

From: “Hugh Brown” <> hsbrown@qnx.com
Subject: Re: 3com 3c900 and etherexpress 16 troubles…


Previously, lantis wrote in qdn.public.qnxrtp.installation:
I have two network cards available to me and I am at a lost to explain
their
behavior.

Second, is a 3com 3c900 PCI. Its behavior I do not understand. With
most
10-base-T cards, as soon as the system has power the connection light
will
be lit. But with this card, it does not. This card works in windows
(it is
PnP I am told), but the connection light does not come on until after
the
Windows splash screen closes. In Linux, it appear to find and set up
the
card, but the connection light did not light and it was unable to
connect to
the network (local or remote). Pinging a working result resulted in an
error. In QNX RTOS, it appear to auto detect the card, so I went to
network
cfg and entered my local network data under the network tab. Under the
device tab, I checked the box to activate this device, but still the
connection light on the card did not light. What is windows doing that
allows this card to “come alive” that the other two operating systems
are
not doing?

I only have a 3C900 Combo card and it works fine with the el900 driver.
Please post the output from ‘nicinfo’ as well as ‘pci -v’.


Here are the results of the output of nicinfo and then pci -v. The media
rate and LAN both being 0 strikes me as strange. Also, the PCI index is 0,
though I have no idea what they should be. Thank you for the help.

Can you please start the driver in verbose mode and post the output?
Do the following:

  1. slay io-net
  2. io-net -del900 verbose -pttcpip > file
  3. slay io-net
  4. post the output ‘file’

Thanks, Hugh.

[snip]