> Salutations, linux-il. 
> 
> I have a new 3com PCI NIC, which claims it is a "3c905cx", but lspci
> with the latest pci.ids file gives: 
> 
> 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
> 
> Notice the unknown device bits. Donald Becker's vortex-diag also
> spews some error about this card:
> 
> [root@alhambra 3com]# ./vortex-diag -p 0x6500 -t 17 -ee
> vortex-diag.c:v2.06 4/18/2002 Donald Becker ([EMAIL PROTECTED])
>  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).
> 
> 
> Any ideas who I should contact to pursue this further? I want to get
> this sucker to work. 
> -- 
> The ill-formed Orange
> Fails to satisfy the eye:       http://vipe.technion.ac.il/~mulix/
> Segmentation fault.             http://syscalltrack.sf.net/
> 


Looks like this card gives headaches to other people too. Searching 
Google gives http://www.tux.org/hypermail/linux-vortex/2000-Nov/0040.htm
l and the followup at 0041.html.
I didn't pursue it further.

-- 

    Shaul Karl
    email: shaulka(replace with the at - @ - character)bezeqint.net 



=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]

Reply via email to