From owner-freebsd-hackers Thu Oct 16 19:47:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA12528 for hackers-outgoing; Thu, 16 Oct 1997 19:47:25 -0700 (PDT) (envelope-from owner-freebsd-hackers) Received: from sparks.net (exim@gw.sparks.net [204.248.143.1]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id TAA12519 for ; Thu, 16 Oct 1997 19:47:15 -0700 (PDT) (envelope-from david@sparks.net) Received: from david by sparks.net with smtp (Exim 1.62 #5) id 0xM2RI-0001MF-00; Thu, 16 Oct 1997 22:47:00 -0400 Date: Thu, 16 Oct 1997 22:46:58 -0400 (EDT) From: To: "Jordan K. Hubbard" cc: freebsd-hackers@freebsd.org Subject: Re: 21140 version E In-Reply-To: <16821.876764087@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 13 Oct 1997, Jordan K. Hubbard wrote: > > I just got a bunch of new znyx muliport fast ethernet cards based on DEC's > > 21140A chip. I have an older rev C board which works fine. But the newer > > rev E's don't:( The Rev E boards appear fine in the boot process, but > > come up with: > > Have you tried this with 2.2-stable or 3.0-current? I believe they > should work now, but you'll need to upgrade if you're not running with > the de driver from either of those two branches. I got it working with the latest driver from Matt Thomas. In retrospect, the problem was likely not the rev E 21140. Somewhere in between the purchase of the two boards Znyx changed the phy chip, whatever that is:) The 2.2.2R driver recognized the 21140 OK, but choked on the new phy chip. Thanks for the help:) --- David ---------------------------------------------------------------------------- It's *amazing* what one can accomplish when one doesn't know what one can't do!