Accton EN2212 problem

system · March 19, 2003, 11:53am

Hi
My Accton EN2212 NE2000 compatible PC Card stopped working under QNX4.
It’s working fine under 6.2.1 & Windows 98.
It seems the CIS is or got corrupted, as the -vvv option
shows a bunch of 0’s that Net.ether1000 complains about.
(Addr Prom messages, and address verification).
This used to work, I suppose something bad happened
with the Accton.

Is there a later version available?
The one I’m using are from Mar 27 '97 (29917 bytes), and another
from Jul 24 1998 (28345 bytes long).

Hugh_Brown1 · March 19, 2003, 1:09pm

Previously, acellarius@yahoo.com wrote in qdn.public.qnx4:

Hi
My Accton EN2212 NE2000 compatible PC Card stopped working under QNX4.
It’s working fine under 6.2.1 & Windows 98.
It seems the CIS is or got corrupted, as the -vvv option
shows a bunch of 0’s that Net.ether1000 complains about.
(Addr Prom messages, and address verification).
This used to work, I suppose something bad happened
with the Accton.

Is there a later version available?
The one I’m using are from Mar 27 '97 (29917 bytes), and another
from Jul 24 1998 (28345 bytes long).

The 4.25G update has a later version, but I doubt whether it will fix
your problem. Since when did the adapter stop working under QNX4? What
changed? If it works under QNX6, then I don’t think the CIS is bad.
Are you using the pccard driver under QNX4 or Pcmcia.generic?

Can you post the verbose output when you start Net.ether1000? I know this
is a pain, as you cannot re-direct the screen output, but if you have
the prtsc (usr/free) utility, you can dump the screen output ot a file.

system · March 19, 2003, 5:59pm

On Wed, 19 Mar 2003 08:09:09 -0500, Hugh Brown <hsbrown@qnx.com> wrote:

Previously, > acellarius@yahoo.com > wrote in qdn.public.qnx4:
Hi
My Accton EN2212 NE2000 compatible PC Card stopped working under QNX4.
It’s working fine under 6.2.1 & Windows 98.
It seems the CIS is or got corrupted, as the -vvv option
shows a bunch of 0’s that Net.ether1000 complains about.
(Addr Prom messages, and address verification).
This used to work, I suppose something bad happened
with the Accton.

Is there a later version available?
The one I’m using are from Mar 27 '97 (29917 bytes), and another
from Jul 24 1998 (28345 bytes long).

The 4.25G update has a later version, but I doubt whether it will fix
your problem. Since when did the adapter stop working under QNX4? What
changed? If it works under QNX6, then I don’t think the CIS is bad.
Are you using the pccard driver under QNX4 or Pcmcia.generic?

Can you post the verbose output when you start Net.ether1000? I know this
is a pain, as you cannot re-direct the screen output, but if you have
the prtsc (usr/free) utility, you can dump the screen output ot a file.

pin says port = 0x300, irq = 10, size = 32
Using Pcmcia.generic -i0 from Jan 09 2001, size 67959
Toshiba 4000 CDS is setup for PCIC compatible

Net.ether1000 -p 300 -i 10 -vvvv says:
Addr Prom 0202 000 0000
Memory verification Data : 00AA 00AB 00AC 00AD → 0002 0002 0000 0000
Trying as 16 bit card
Addr Prom 0202 000 0000
Memory verification Data : 00AA 00AB 00AC 00AD → 0002 0002 0000 0000
Memory verification failed, exiting
Net.ether1000 INITIALIZATION ERROR 10 Net.ether1000 INITIALIZATION ERROR 04

Hugh_Brown1 · March 19, 2003, 6:58pm

Some of the Toshiba’s don’t like I/O addresses in the 0x300 range.
Try modifying your /etc/config/pcmcia.cfg file to give I/O addresses in
the 0x400 range.

When did this stop working? What changed?

Previously, acellarius@yahoo.com wrote in qdn.public.qnx4:

On Wed, 19 Mar 2003 08:09:09 -0500, Hugh Brown <> hsbrown@qnx.com> > wrote:
Previously, > acellarius@yahoo.com > wrote in qdn.public.qnx4:
Hi
My Accton EN2212 NE2000 compatible PC Card stopped working under QNX4.
It’s working fine under 6.2.1 & Windows 98.
It seems the CIS is or got corrupted, as the -vvv option
shows a bunch of 0’s that Net.ether1000 complains about.
(Addr Prom messages, and address verification).
This used to work, I suppose something bad happened
with the Accton.

Is there a later version available?
The one I’m using are from Mar 27 '97 (29917 bytes), and another
from Jul 24 1998 (28345 bytes long).

The 4.25G update has a later version, but I doubt whether it will fix
your problem. Since when did the adapter stop working under QNX4? What
changed? If it works under QNX6, then I don’t think the CIS is bad.
Are you using the pccard driver under QNX4 or Pcmcia.generic?

Can you post the verbose output when you start Net.ether1000? I know this
is a pain, as you cannot re-direct the screen output, but if you have
the prtsc (usr/free) utility, you can dump the screen output ot a file.

pin says port = 0x300, irq = 10, size = 32
Using Pcmcia.generic -i0 from Jan 09 2001, size 67959
Toshiba 4000 CDS is setup for PCIC compatible

Net.ether1000 -p 300 -i 10 -vvvv says:
Addr Prom 0202 000 0000
Memory verification Data : 00AA 00AB 00AC 00AD → 0002 0002 0000 0000
Trying as 16 bit card
Addr Prom 0202 000 0000
Memory verification Data : 00AA 00AB 00AC 00AD → 0002 0002 0000 0000
Memory verification failed, exiting
Net.ether1000 INITIALIZATION ERROR 10 Net.ether1000 INITIALIZATION ERROR 04
\

system · March 19, 2003, 6:59pm

On Wed, 19 Mar 2003 13:58:45 -0500, Hugh Brown <hsbrown@qnx.com> wrote:

Some of the Toshiba’s don’t like I/O addresses in the 0x300 range.
Try modifying your /etc/config/pcmcia.cfg file to give I/O addresses in
the 0x400 range.

Ok-although it used to work as it was.

When did this stop working? What changed?

No idea. The Net.ether1000 just started complaining one day.

Is there useful information I can get via QNX6 on the laptop?

system · March 19, 2003, 7:01pm

On Wed, 19 Mar 2003 13:58:45 -0500, Hugh Brown <hsbrown@qnx.com> wrote:

Some of the Toshiba’s don’t like I/O addresses in the 0x300 range.
Try modifying your /etc/config/pcmcia.cfg file to give I/O addresses in
the 0x400 range.

Tried it, and pin is now reporting 400, but running Net.ether1000
with the new address still gives the same result

Hugh_Brown1 · March 20, 2003, 1:40pm

Previously, acellarius@yahoo.com wrote in qdn.public.qnx4:

On Wed, 19 Mar 2003 13:58:45 -0500, Hugh Brown <> hsbrown@qnx.com> > wrote:
Some of the Toshiba’s don’t like I/O addresses in the 0x300 range.
Try modifying your /etc/config/pcmcia.cfg file to give I/O addresses in
the 0x400 range.

Ok-although it used to work as it was.

When did this stop working? What changed?

No idea. The Net.ether1000 just started complaining one day.

Is there useful information I can get via QNX6 on the laptop?

When you run QNX6, do you change the BIOS to CardBus/16-bit? If you can
provide the output from ‘pin’, ‘pin cis’ and ‘pci -v’ under QNX6, that
would help. This must be done with devp-pccard running and your network
card installed.

Have you tried running the new QNX4 pccard software? If you do, then you
won’t have to change the BIOS in your machine. It can stay set to
CardBus/16-bit for QNX4 and 6.

system · March 20, 2003, 3:01pm

On Thu, 20 Mar 2003 08:40:32 -0500, Hugh Brown <hsbrown@qnx.com> wrote:

Previously, > acellarius@yahoo.com > wrote in qdn.public.qnx4:
On Wed, 19 Mar 2003 13:58:45 -0500, Hugh Brown <> hsbrown@qnx.com> > wrote:
Some of the Toshiba’s don’t like I/O addresses in the 0x300 range.
Try modifying your /etc/config/pcmcia.cfg file to give I/O addresses in
the 0x400 range.

Ok-although it used to work as it was.

When did this stop working? What changed?

No idea. The Net.ether1000 just started complaining one day.

Is there useful information I can get via QNX6 on the laptop?

When you run QNX6, do you change the BIOS to CardBus/16-bit? If you can
provide the output from ‘pin’, ‘pin cis’ and ‘pci -v’ under QNX6, that
would help. This must be done with devp-pccard running and your network
card installed.

I used to have to, but I see you have weaved a little magic, so it
works both ways in QNX6. I’ve left it on PCIC for now.

Have you tried running the new QNX4 pccard software? If you do, then you
won’t have to change the BIOS in your machine. It can stay set to
CardBus/16-bit for QNX4 and 6.

Not yet. When did that become part of QNX4? I think I have up to 425E here.
(up to where the new installer phinstall wasn’t necessary).

PCI version = 2.10

Class = Bridge (Host/PCI)
Vendor ID = 8086h, Intel Corporation
Device ID = 7192h, 82443BX/ZX 440BX/ZX chipset Host-to-PCI Bridge
PCI index = 0h
Class Codes = 060000h
Revision ID = 2h
Bus number = 0
Device number = 0
Function num = 0
Status Reg = 2200h
Command Reg = 6h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 0h
Subsystem Vendor ID = 1179h
Subsystem ID = 1h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = NC
Interrupt line = 0

Class = Display (VGA)
Vendor ID = 102ch, Chips And Technologies
Device ID = e5h, 65555 VGA GUI Accelerator
PCI index = 0h
Class Codes = 030000h
Revision ID = c6h
Bus number = 0
Device number = 4
Function num = 0
Status Reg = 280h
Command Reg = 82h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h
PCI Mem Address = fe000000h 32bit length 16777216 enabled
Subsystem Vendor ID = 1179h
Subsystem ID = 1h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = NC
Interrupt line = 0

Class = Bridge (Unknown)
Vendor ID = 8086h, Intel Corporation
Device ID = 7110h, 82371AB/EB PIIX4 ISA Bridge
PCI index = 0h
Class Codes = 068000h
Revision ID = 2h
Bus number = 0
Device number = 7
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 = 7111h, 82371AB/EB PIIX4 IDE Controller
PCI index = 0h
Class Codes = 010180h
Revision ID = 1h
Bus number = 0
Device number = 7
Function num = 1
Status Reg = 280h
Command Reg = 5h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 0h
PCI IO Address = fe60h length 16 enabled
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 = 7112h, 82371AB/EB PIIX4 USB Interface
PCI index = 0h
Class Codes = 0c0300h
Revision ID = 1h
Bus number = 0
Device number = 7
Function num = 2
Status Reg = 280h
Command Reg = 4h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 0h
PCI IO Address = 0h length 32 disabled
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT D
Interrupt line = 11

Class = Bridge (Unknown)
Vendor ID = 8086h, Intel Corporation
Device ID = 7113h, 82371AB/EB PIIX4 Power Management Controller
PCI index = 0h
Class Codes = 068000h
Revision ID = 2h
Bus number = 0
Device number = 7
Function num = 3
Status Reg = 280h
Command Reg = 3h
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

Class = Communication (Unknown)
Vendor ID = 1179h, Toshiba America Info Systems
Device ID = 701h, PCI Communication Device
PCI index = 0h
Class Codes = 078000h
Revision ID = 23h
Bus number = 0
Device number = 10
Function num = 0
Status Reg = 400h
Command Reg = 4h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 0h
PCI IO Address = 0h length 32 disabled
Subsystem Vendor ID = 1179h
Subsystem ID = 1h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT A
Interrupt line = 11

Socket : 2 - Function : 0
Device : Function Specific 32k
Attribute Device : Flash 2k
PC Card function : Network LAN Adapter
POST : 0x3
Card tuple version : 4.01
Manufacturer : ACCTON
Name of Product : EN2212
Add’nl info (lot #) : PCMCIA-ETHERNET
Add’nl info (programming): R06
Configuration base/st : 0x100 0-subtuples
Configuration Index : 0x20 Default
Interface : MWait Req’d, I/O
Feature : 0x1d
Timing Info : Wait
IO Space : Bus16 Bus8 0x0-0x1F(5 lines)
IRQ Description : Level 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Configuration Index : 0x2
Feature : 0x8
IO Space : Bus16 0x300-0x31F
Configuration Index : 0x3
Feature : 0x8
IO Space : Bus16 0x320-0x33F
Configuration Index : 0x4
Feature : 0x8
IO Space : Bus16 0x340-0x35F
Configuration Index : 0x5
Feature : 0x8
IO Space : Bus16 0x360-0x37F

Sock Func Type Flags PID Base Size IRQ
1 Empty ----MF---------- None
1 Empty ----MF---------- None
2 0 Network C—I-±-------- None 0x300 32 3
2 Empty ----MF---------- None

Hugh_Brown1 · March 20, 2003, 5:08pm

Previously, acellarius@yahoo.com wrote in qdn.public.qnx4:

On Thu, 20 Mar 2003 08:40:32 -0500, Hugh Brown <> hsbrown@qnx.com> > wrote:
Previously, > acellarius@yahoo.com > wrote in qdn.public.qnx4:
On Wed, 19 Mar 2003 13:58:45 -0500, Hugh Brown <> hsbrown@qnx.com> > wrote:
Some of the Toshiba’s don’t like I/O addresses in the 0x300 range.
Try modifying your /etc/config/pcmcia.cfg file to give I/O addresses in
the 0x400 range.

Ok-although it used to work as it was.

When did this stop working? What changed?

No idea. The Net.ether1000 just started complaining one day.

Is there useful information I can get via QNX6 on the laptop?

When you run QNX6, do you change the BIOS to CardBus/16-bit? If you can
provide the output from ‘pin’, ‘pin cis’ and ‘pci -v’ under QNX6, that
would help. This must be done with devp-pccard running and your network
card installed.

I used to have to, but I see you have weaved a little magic, so it
works both ways in QNX6. I’ve left it on PCIC for now.

Have you tried running the new QNX4 pccard software? If you do, then you
won’t have to change the BIOS in your machine. It can stay set to
CardBus/16-bit for QNX4 and 6.

Not yet. When did that become part of QNX4? I think I have up to 425E here.
(up to where the new installer phinstall wasn’t necessary).

The pccard driver was released with the latest 4.25G patch. There is also
an archive at developers.qnx.com, but this is a bit older. I’m sure that
you will have to change the bios to run this new driver.

As a matter of interest, does the card work if you put it in the other
socket? I have had experiences where a card works in one socket and not
in another! Don’t ask me why?

PCI version = 2.10

Class = Bridge (Host/PCI)
Vendor ID = 8086h, Intel Corporation
Device ID = 7192h, 82443BX/ZX 440BX/ZX chipset Host-to-PCI Bridge
PCI index = 0h
Class Codes = 060000h
Revision ID = 2h
Bus number = 0
Device number = 0
Function num = 0
Status Reg = 2200h
Command Reg = 6h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 0h
Subsystem Vendor ID = 1179h
Subsystem ID = 1h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = NC
Interrupt line = 0

Class = Display (VGA)
Vendor ID = 102ch, Chips And Technologies
Device ID = e5h, 65555 VGA GUI Accelerator
PCI index = 0h
Class Codes = 030000h
Revision ID = c6h
Bus number = 0
Device number = 4
Function num = 0
Status Reg = 280h
Command Reg = 82h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h
PCI Mem Address = fe000000h 32bit length 16777216 enabled
Subsystem Vendor ID = 1179h
Subsystem ID = 1h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = NC
Interrupt line = 0

Class = Bridge (Unknown)
Vendor ID = 8086h, Intel Corporation
Device ID = 7110h, 82371AB/EB PIIX4 ISA Bridge
PCI index = 0h
Class Codes = 068000h
Revision ID = 2h
Bus number = 0
Device number = 7
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 = 7111h, 82371AB/EB PIIX4 IDE Controller
PCI index = 0h
Class Codes = 010180h
Revision ID = 1h
Bus number = 0
Device number = 7
Function num = 1
Status Reg = 280h
Command Reg = 5h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 0h
PCI IO Address = fe60h length 16 enabled
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 = 7112h, 82371AB/EB PIIX4 USB Interface
PCI index = 0h
Class Codes = 0c0300h
Revision ID = 1h
Bus number = 0
Device number = 7
Function num = 2
Status Reg = 280h
Command Reg = 4h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 0h
PCI IO Address = 0h length 32 disabled
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT D
Interrupt line = 11

Class = Bridge (Unknown)
Vendor ID = 8086h, Intel Corporation
Device ID = 7113h, 82371AB/EB PIIX4 Power Management Controller
PCI index = 0h
Class Codes = 068000h
Revision ID = 2h
Bus number = 0
Device number = 7
Function num = 3
Status Reg = 280h
Command Reg = 3h
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

Class = Communication (Unknown)
Vendor ID = 1179h, Toshiba America Info Systems
Device ID = 701h, PCI Communication Device
PCI index = 0h
Class Codes = 078000h
Revision ID = 23h
Bus number = 0
Device number = 10
Function num = 0
Status Reg = 400h
Command Reg = 4h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 0h
PCI IO Address = 0h length 32 disabled
Subsystem Vendor ID = 1179h
Subsystem ID = 1h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT A
Interrupt line = 11

Socket : 2 - Function : 0
Device : Function Specific 32k
Attribute Device : Flash 2k
PC Card function : Network LAN Adapter
POST : 0x3
Card tuple version : 4.01
Manufacturer : ACCTON
Name of Product : EN2212
Add’nl info (lot #) : PCMCIA-ETHERNET
Add’nl info (programming): R06
Configuration base/st : 0x100 0-subtuples
Configuration Index : 0x20 Default
Interface : MWait Req’d, I/O
Feature : 0x1d
Timing Info : Wait
IO Space : Bus16 Bus8 0x0-0x1F(5 lines)
IRQ Description : Level 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Configuration Index : 0x2
Feature : 0x8
IO Space : Bus16 0x300-0x31F
Configuration Index : 0x3
Feature : 0x8
IO Space : Bus16 0x320-0x33F
Configuration Index : 0x4
Feature : 0x8
IO Space : Bus16 0x340-0x35F
Configuration Index : 0x5
Feature : 0x8
IO Space : Bus16 0x360-0x37F

Sock Func Type Flags PID Base Size IRQ
1 Empty ----MF---------- None
1 Empty ----MF---------- None
2 0 Network C—I-±-------- None 0x300 32 3
2 Empty ----MF---------- None

\

system · March 20, 2003, 6:29pm

On Thu, 20 Mar 2003 12:08:24 -0500, Hugh Brown <hsbrown@qnx.com> wrote:

The pccard driver was released with the latest 4.25G patch. There is also
an archive at developers.qnx.com, but this is a bit older. I’m sure that
you will have to change the bios to run this new driver.

As a matter of interest, does the card work if you put it in the other
socket? I have had experiences where a card works in one socket and not
in another! Don’t ask me why? >

Changing socket had no effect

Tried the archive version you mentioned.
Wouldn’t work at all in Cardbus/16 bit setting.
Had to pick PCIC.

The new Net.ether1000 still fails.
Complains about _CA_PCI_Find_Device failed
Also insists on scanning address up to 400 even if -p 400 is supplied.
(After saying “ROM not detected”)

show_pci, pin and pic cis below:

PCI version = 2.10

Vendor ID = 8086h, INTEL CORPORATION
Device ID = 7192h,
PCI index = 0h
Class Code = 060000h Bridge (Host/PCI) ProgIF=0
Revision ID = 2h
Bus number = 0
Device number = 0
Function num = 0
Status Reg = 2200h
Command Reg = 6h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 0h
Base Address = MEM@e0000000h,Prefetchable,32bit length 268435456
Subsystem Vendor ID = 1179h
Subsystem ID = 1h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = 0, NC
Interrupt line = 0

Vendor ID = 102ch, Chips & Technologies
Device ID = e5h,
PCI index = 0h
Class Code = 030000h Display (VGA) ProgIF=0
Revision ID = c6h
Bus number = 0
Device number = 4
Function num = 0
Status Reg = 280h
Command Reg = 83h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h
Base Address = MEM@fe000000h,32bit length 16777216
Subsystem Vendor ID = 1179h
Subsystem ID = 1h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = 0, NC
Interrupt line = 0

Vendor ID = 8086h, INTEL CORPORATION
Device ID = 7110h,
PCI index = 0h
Class Code = 068000h Bridge (Other 128) ProgIF=0
Revision ID = 2h
Bus number = 0
Device number = 7
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 = 0, NC
Interrupt line = 0

Vendor ID = 8086h, INTEL CORPORATION
Device ID = 7111h,
PCI index = 0h
Class Code = 010180h Mass Storage (IDE) ProgIF=128
Revision ID = 1h
Bus number = 0
Device number = 7
Function num = 1
Status Reg = 280h
Command Reg = 5h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 0h
IO@fe60h length 16 bytes
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = 0, NC
Interrupt line = 0

Vendor ID = 8086h, INTEL CORPORATION
Device ID = 7112h,
PCI index = 0h
Class Code = 0c0300h Serial Bus (Universal Serial Bus) ProgIF=0
Revision ID = 1h
Bus number = 0
Device number = 7
Function num = 2
Status Reg = 280h
Command Reg = 5h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 0h
IO@ffe0h length 32 bytes
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = 4, INT D
Interrupt line = 11

Vendor ID = 8086h, INTEL CORPORATION
Device ID = 7113h,
PCI index = 0h
Class Code = 068000h Bridge (Other 128) ProgIF=0
Revision ID = 2h
Bus number = 0
Device number = 7
Function num = 3
Status Reg = 280h
Command Reg = 3h
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 = 0, NC
Interrupt line = 0

Vendor ID = 1179h,
Device ID = 701h,
PCI index = 0h
Class Code = 078000h Communication (Other 128) ProgIF=0
Revision ID = 23h
Bus number = 0
Device number = 10
Function num = 0
Status Reg = 400h
Command Reg = 5h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 0h
Base Address = IO@ff80h length 32 bytes
Subsystem Vendor ID = 1179h
Subsystem ID = 1h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = 1, INT A
Interrupt line = 11

IRQ Routing = bus=0 motherboard device=2
No card configured in slot
INTA=11
INTB=11

IRQ Routing = bus=0 motherboard device=10
Vendor ID = 1179h,
Device ID = 701h,
INTA=11

IRQ Routing = bus=0 motherboard device=4
Vendor ID = 102ch, Chips & Technologies
Device ID = e5h,

IRQ Routing = bus=0 motherboard device=7
Vendor ID = 8086h, INTEL CORPORATION
Device ID = 7110h,
Vendor ID = 8086h, INTEL CORPORATION
Device ID = 7111h,
Vendor ID = 8086h, INTEL CORPORATION
Device ID = 7112h,
Vendor ID = 8086h, INTEL CORPORATION
Device ID = 7113h,
INTD=11

Sock Func Type Flags PID Base Size IRQ
1 0 Network C—I-±-------- None 0x400 32 10
1 Empty ----MF---------- None
2 Empty ----MF---------- None
2 Empty ----MF---------- None

Socket : 1 - Function : 0
Device : Function Specific 32k
Attribute Device : Flash 2k
PC Card function : Network LAN Adapter
POST : 0x3
Card tuple version : 4.01
Manufacturer : ACCTON
Name of Product : EN2212
Add’nl info (lot #) : PCMCIA-ETHERNET
Add’nl info (programming): R06
Configuration base/st : 0x100 0-subtuples
Configuration Index : 0x20 Default
Interface : MWait Req’d, I/O
Feature : 0x1d
Timing Info : Wait
IO Space : Bus16 Bus8 0x0-0x1F(5 lines)
IRQ Description : Level 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Configuration Index : 0x2
Feature : 0x8
IO Space : Bus16 0x300-0x31F
Configuration Index : 0x3
Feature : 0x8
IO Space : Bus16 0x320-0x33F
Configuration Index : 0x4
Feature : 0x8
IO Space : Bus16 0x340-0x35F
Configuration Index : 0x5
Feature : 0x8
IO Space : Bus16 0x360-0x37F

Hugh_Brown1 · March 21, 2003, 3:31pm

Previously, acellarius@yahoo.com wrote in qdn.public.qnx4:

On Thu, 20 Mar 2003 12:08:24 -0500, Hugh Brown <> hsbrown@qnx.com> > wrote:
The pccard driver was released with the latest 4.25G patch. There is also
an archive at developers.qnx.com, but this is a bit older. I’m sure that
you will have to change the bios to run this new driver.

As a matter of interest, does the card work if you put it in the other
socket? I have had experiences where a card works in one socket and not
in another! Don’t ask me why? >

Changing socket had no effect

Tried the archive version you mentioned.
Wouldn’t work at all in Cardbus/16 bit setting.
Had to pick PCIC.

The new Net.ether1000 still fails.
Complains about _CA_PCI_Find_Device failed
Also insists on scanning address up to 400 even if -p 400 is supplied.
(After saying “ROM not detected”)

Well I’m at a loss! Something must have changed for it to stop working.
Have you tried the ‘-a’ command line option to Net.ether1000 to force
8-bit mode, or the ‘-6’ option to force 16-bit mode?

show_pci, pin and pic cis below:

PCI version = 2.10

Vendor ID = 8086h, INTEL CORPORATION
Device ID = 7192h,
PCI index = 0h
Class Code = 060000h Bridge (Host/PCI) ProgIF=0
Revision ID = 2h
Bus number = 0
Device number = 0
Function num = 0
Status Reg = 2200h
Command Reg = 6h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 0h
Base Address = MEM@e0000000h,Prefetchable,32bit length 268435456
Subsystem Vendor ID = 1179h
Subsystem ID = 1h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = 0, NC
Interrupt line = 0

Vendor ID = 102ch, Chips & Technologies
Device ID = e5h,
PCI index = 0h
Class Code = 030000h Display (VGA) ProgIF=0
Revision ID = c6h
Bus number = 0
Device number = 4
Function num = 0
Status Reg = 280h
Command Reg = 83h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h
Base Address = MEM@fe000000h,32bit length 16777216
Subsystem Vendor ID = 1179h
Subsystem ID = 1h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = 0, NC
Interrupt line = 0

Vendor ID = 8086h, INTEL CORPORATION
Device ID = 7110h,
PCI index = 0h
Class Code = 068000h Bridge (Other 128) ProgIF=0
Revision ID = 2h
Bus number = 0
Device number = 7
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 = 0, NC
Interrupt line = 0

Vendor ID = 8086h, INTEL CORPORATION
Device ID = 7111h,
PCI index = 0h
Class Code = 010180h Mass Storage (IDE) ProgIF=128
Revision ID = 1h
Bus number = 0
Device number = 7
Function num = 1
Status Reg = 280h
Command Reg = 5h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 0h
IO@fe60h length 16 bytes
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = 0, NC
Interrupt line = 0

Vendor ID = 8086h, INTEL CORPORATION
Device ID = 7112h,
PCI index = 0h
Class Code = 0c0300h Serial Bus (Universal Serial Bus) ProgIF=0
Revision ID = 1h
Bus number = 0
Device number = 7
Function num = 2
Status Reg = 280h
Command Reg = 5h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 0h
IO@ffe0h length 32 bytes
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = 4, INT D
Interrupt line = 11

Vendor ID = 8086h, INTEL CORPORATION
Device ID = 7113h,
PCI index = 0h
Class Code = 068000h Bridge (Other 128) ProgIF=0
Revision ID = 2h
Bus number = 0
Device number = 7
Function num = 3
Status Reg = 280h
Command Reg = 3h
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 = 0, NC
Interrupt line = 0

Vendor ID = 1179h,
Device ID = 701h,
PCI index = 0h
Class Code = 078000h Communication (Other 128) ProgIF=0
Revision ID = 23h
Bus number = 0
Device number = 10
Function num = 0
Status Reg = 400h
Command Reg = 5h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 0h
Base Address = IO@ff80h length 32 bytes
Subsystem Vendor ID = 1179h
Subsystem ID = 1h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = 1, INT A
Interrupt line = 11

IRQ Routing = bus=0 motherboard device=2
No card configured in slot
INTA=11
INTB=11

IRQ Routing = bus=0 motherboard device=10
Vendor ID = 1179h,
Device ID = 701h,
INTA=11

IRQ Routing = bus=0 motherboard device=4
Vendor ID = 102ch, Chips & Technologies
Device ID = e5h,

IRQ Routing = bus=0 motherboard device=7
Vendor ID = 8086h, INTEL CORPORATION
Device ID = 7110h,
Vendor ID = 8086h, INTEL CORPORATION
Device ID = 7111h,
Vendor ID = 8086h, INTEL CORPORATION
Device ID = 7112h,
Vendor ID = 8086h, INTEL CORPORATION
Device ID = 7113h,
INTD=11

Sock Func Type Flags PID Base Size IRQ
1 0 Network C—I-±-------- None 0x400 32 10
1 Empty ----MF---------- None
2 Empty ----MF---------- None
2 Empty ----MF---------- None

Socket : 1 - Function : 0
Device : Function Specific 32k
Attribute Device : Flash 2k
PC Card function : Network LAN Adapter
POST : 0x3
Card tuple version : 4.01
Manufacturer : ACCTON
Name of Product : EN2212
Add’nl info (lot #) : PCMCIA-ETHERNET
Add’nl info (programming): R06
Configuration base/st : 0x100 0-subtuples
Configuration Index : 0x20 Default
Interface : MWait Req’d, I/O
Feature : 0x1d
Timing Info : Wait
IO Space : Bus16 Bus8 0x0-0x1F(5 lines)
IRQ Description : Level 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Configuration Index : 0x2
Feature : 0x8
IO Space : Bus16 0x300-0x31F
Configuration Index : 0x3
Feature : 0x8
IO Space : Bus16 0x320-0x33F
Configuration Index : 0x4
Feature : 0x8
IO Space : Bus16 0x340-0x35F
Configuration Index : 0x5
Feature : 0x8
IO Space : Bus16 0x360-0x37F
\

system · March 21, 2003, 7:33pm

On Fri, 21 Mar 2003 10:31:21 -0500, Hugh Brown <hsbrown@qnx.com> wrote:

Previously, > acellarius@yahoo.com > wrote in qdn.public.qnx4:
On Thu, 20 Mar 2003 12:08:24 -0500, Hugh Brown <> hsbrown@qnx.com> > wrote:
The pccard driver was released with the latest 4.25G patch. There is also
an archive at developers.qnx.com, but this is a bit older. I’m sure that
you will have to change the bios to run this new driver.

As a matter of interest, does the card work if you put it in the other
socket? I have had experiences where a card works in one socket and not
in another! Don’t ask me why? >

Changing socket had no effect

Tried the archive version you mentioned.
Wouldn’t work at all in Cardbus/16 bit setting.
Had to pick PCIC.

The new Net.ether1000 still fails.
Complains about _CA_PCI_Find_Device failed
Also insists on scanning address up to 400 even if -p 400 is supplied.
(After saying “ROM not detected”)

Well I’m at a loss! Something must have changed for it to stop working.
Have you tried the ‘-a’ command line option to Net.ether1000 to force
8-bit mode, or the ‘-6’ option to force 16-bit mode?

Well blow me over but it started working now.
Must start from the warm boot state it seems.
If you start with the old stuff, slay it all and try
the newer version without a reboot, it doesn’t work.

Thanks for the help!