First I would like to thanks the following person for their reply:
John Losey <JOHLOS_at_HBSI.COM>
Hoai Tran <hoai_at_abc.net.au>
They both mentioned dia and uerf. With which you can identify
the CHIP Version of your DE500 card.
Its also possible to go to /var/adm/syslog.dated/current
and have a look kern.log in which this information is also
present.
My Problem was not solved whith this information so I had to open
the boxes and this are messages which appear for the different
cards.
1) DE500-AA
I have an old Version of the DE500-AA (DEC21140-AA) but I never installed
it. (I had no time)
2) DE500-AA (new Version with DEC21140-AC, PCI 2.1 compliant)
Mar 19 19:08:01 apex vmunix: tu0: DECchip 21140: Revision: 2.0
Mar 19 19:08:01 apex vmunix: tu0: auto negotiation capable device
Mar 19 19:08:01 apex vmunix: tu0 at pci0 slot 5
Mar 19 19:08:01 apex vmunix: tu0: DEC TULIP (10/100) Ethernet Interface,
hardware address: 00-00-F8-02-20-E0
3) DE500-BA( PCI2.1compliant)
Mar 24 18:11:18 apex vmunix: tu0: DECchip 21143: Revision: 3.0
Mar 24 18:11:18 apex vmunix: tu0: auto negotiation capable device
Mar 24 18:11:18 apex vmunix: tu0 at pci0 slot 5
Mar 24 18:11:18 apex vmunix: tu0: DEC TULIP (10/100) Ethernet Interface,
hardware address: 00-00-F8-07-E9-47
Thanks
Wieland
---
*Wieland Stübinger Tel.:Office 49-89-722-36108 *
*82031 Grünwald e-mail: stuebi_at_stuebi.de *
*Germany nic-hdl: WS6-RIPE *
* Real programmers don`t comment. *
* Something hard to write should be hard to read. *
Received on Fri Mar 24 2000 - 17:41:57 NZST