From owner-freebsd-hackers Fri Feb 14 10:43:43 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA23114 for hackers-outgoing; Fri, 14 Feb 1997 10:43:43 -0800 (PST) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA23106 for ; Fri, 14 Feb 1997 10:43:33 -0800 (PST) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.6.12) with SMTP id KAA01518; Fri, 14 Feb 1997 10:42:31 -0800 (PST) Date: Fri, 14 Feb 1997 10:42:31 -0800 (PST) From: Doug White X-Sender: dwhite@localhost Reply-To: Doug White To: Luigi Rizzo cc: Tim Tsai , hackers@freebsd.org Subject: Re: Status of 21140AC driver ? In-Reply-To: <199702141137.MAA25239@labinfo.iet.unipi.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This info was forwarded on to me, and since I have this info, I'll pass it on. I don't have the card anymore, though, so I can't test it. On Fri, 14 Feb 1997, Luigi Rizzo wrote: > To add a few datapoint to the 21140/21140A/21140-AC status: (the > names are repeated so that the search engines will match someone > of them!) > > More news tonight. In the meantime, can people with problems tell me > the Rev. and pass. number of their boards (printed by the kernel > diagnostics) This is what my Kingston EtherRx 10/100 card spit out: Feb 11 22:31:19 gdi /kernel: de0 rev 32 int a irq 10 on pci0:17 Feb 11 22:31:19 gdi /kernel: de0: 21140A [10-100Mb/s] pass 2.0 Feb 11 22:31:19 gdi /kernel: de0: address 00:c0:f0:16:3f:1d Feb 11 22:31:19 gdi /kernel: de0: enabling 100baseTX port The chip is labelled 21140-AC. I swapped this card with a Dayna that wasn't going anywhere in a Mac Performa 6360. To say the least, both parties are very happy to have functional PCI Ethernet cards. > I'd really like to try and have this fixed, so your cooperation is very > much appreciated. As a datapoint, the 21041-AA chip in the Dayna E/PCI-M works fine with the 21041 driver, with some i/o errors; I'm still trying to find where these are coming from. It's a .03% error rate so I'm not worried :) Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major