3com 3c905cx-tx-nm "unknown device"

3com 3c905cx-tx-nm "unknown device"

[Muli Ben-Yehuda]

Hello, 

I have new 3com PCI NIC, which purpots to be a "3c905cx-tx-nm". The
3c59x module (kernel 2.4.19-pre3-ac2, I'll try -pre8 in a bit) fails
to recognize the card. 

lspci -vx (with the latest pci.ids file) shows:

00:09.0 Ethernet controller: 3Com Corporation: Unknown device ffff (rev 78)
     Flags: bus master, medium devsel, latency 64, IRQ 11
     I/O ports at 6500 [size=128]
     Expansion ROM at <unassigned> [disabled] [size=128K]
     Capabilities: [dc] Power Management version 2
00: b7 10 ff ff 07 00 10 02 78 00 00 02 08 40 00 00
10: 01 65 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 ff ff ff ff
30: 00 00 00 00 dc 00 00 00 00 00 00 00 0b 01 1e 3f

Donald Becker's vortex-diag program shows:

[root@alhambra 3com]# ./vortex-diag -p 0x6500 -t 17 -ee
vortex-diag.c:v2.06 4/18/2002 Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html
Assuming a 3c905C Tornado 100baseTx adapter at 0x6500.
EEPROM format 64x16, configuration table at offset 0:
      ...

 The word-wide EEPROM checksum is 0000.
Saved EEPROM settings of a 3Com Vortex/Boomerang:
 3Com Node Address FF:FF:FF:FF:FF:FF (used as a unique ID only).
 OEM Station address ff:FF:FF:FF:FF:FF (used as the ethernet address).
  Device ID ffff,  Manufacturer ID ffff.
  Manufacture date (MM/DD/YYYY) 15/31/.
  A BIOS ROM of size 960Kx8 is expected.
 Options: force full duplex, link beat check disabled.
  Vortex format checksum is incorrect (0000 vs. ffff).
  Cyclone format checksum is incorrect (00 vs. 0xff).
  Hurricane format checksum is incorrect (00 vs. 0xff).

How can I debug this further? 
Thanks in advance!
-- 
The ill-formed Orange
Fails to satisfy the eye:       http://vipe.technion.ac.il/~mulix/
Segmentation fault.             http://syscalltrack.sf.net/

Re: 3com 3c905cx-tx-nm "unknown device"

[Andrew Morton]

Muli Ben-Yehuda wrote:
> 
> Hello,
> 
> I have new 3com PCI NIC, which purpots to be a "3c905cx-tx-nm". The
> 3c59x module (kernel 2.4.19-pre3-ac2, I'll try -pre8 in a bit) fails
> to recognize the card.

Well it would...

> lspci -vx (with the latest pci.ids file) shows:
> 
> 00:09.0 Ethernet controller: 3Com Corporation: Unknown device ffff (rev 78)
>      Flags: bus master, medium devsel, latency 64, IRQ 11
>      I/O ports at 6500 [size=128]
>      Expansion ROM at <unassigned> [disabled] [size=128K]
>      Capabilities: [dc] Power Management version 2
> 00: b7 10 ff ff 07 00 10 02 78 00 00 02 08 40 00 00
> 10: 01 65 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 20: 00 00 00 00 00 00 00 00 00 00 00 00 ff ff ff ff
> 30: 00 00 00 00 dc 00 00 00 00 00 00 00 0b 01 1e 3f

PCI IDs are 0xffff.  Normally that is supplied from the EEPROM (we think).

Try setting the NIC up with 3com's DOS-based setup program 
ftp://ftp.3com.com/pub/nic/3c90x/3c90xx2.exe and also check your
BIOS power management settings, PnP OS settings, etc.

Try to work out why the EEPROM hasn't been powered up - could be
a dead card (test it under Windows) or a BIOS thing.

-

Re: 3com 3c905cx-tx-nm "unknown device"

[Muli Ben-Yehuda]

On Sat, May 11, 2002 at 01:07:53AM -0700, Andrew Morton wrote:
> Muli Ben-Yehuda wrote:
> > lspci -vx (with the latest pci.ids file) shows:
> > 
> > 00:09.0 Ethernet controller: 3Com Corporation: Unknown device ffff (rev 78)
> >      Flags: bus master, medium devsel, latency 64, IRQ 11
> >      I/O ports at 6500 [size=128]
> >      Expansion ROM at <unassigned> [disabled] [size=128K]
> >      Capabilities: [dc] Power Management version 2
> > 00: b7 10 ff ff 07 00 10 02 78 00 00 02 08 40 00 00
> > 10: 01 65 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > 20: 00 00 00 00 00 00 00 00 00 00 00 00 ff ff ff ff
> > 30: 00 00 00 00 dc 00 00 00 00 00 00 00 0b 01 1e 3f
> 
> PCI IDs are 0xffff.  Normally that is supplied from the EEPROM (we think).
> 
> Try setting the NIC up with 3com's DOS-based setup program 
> ftp://ftp.3com.com/pub/nic/3c90x/3c90xx2.exe and also check your
> BIOS power management settings, PnP OS settings, etc.

The BIOS setting have all been tweaked to death, with no apparent
change. I tried the setup program on windows 95, and it failed to
detect the card as well. 

> Try to work out why the EEPROM hasn't been powered up - could be
> a dead card (test it under Windows) or a BIOS thing.

I'll try to test the card on a different computer running a reasonably
recent version of windows, and I'll try to get another unit of the
same card to try with linux. I'll inform the list of any conclustions.
Thanks!
-- 
The ill-formed Orange
Fails to satisfy the eye:       http://vipe.technion.ac.il/~mulix/
Segmentation fault.             http://syscalltrack.sf.net/