From owner-freebsd-hackers Thu Apr 5 8:16:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 4A4F537B422 for ; Thu, 5 Apr 2001 08:16:07 -0700 (PDT) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f35FALO30437; Thu, 5 Apr 2001 10:10:21 -0500 (CDT) (envelope-from jlemon) Date: Thu, 5 Apr 2001 10:10:21 -0500 (CDT) From: Jonathan Lemon Message-Id: <200104051510.f35FALO30437@prism.flugsvamp.com> To: istore-techs@CS.Berkeley.EDU, hackers@freebsd.org Subject: Re: unsupport fxp PHY's revisited X-Newsgroups: local.mail.freebsd-hackers In-Reply-To: Organization: Cc: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >When booting FreeBSD 4.x on a system board with onboard fxp ethernet we >developed for a research project here, we observe the same behaviour as >described in the Dec 2000 -hackers thread "RE: yet another unsupported >PHY in fxp driver" You might want to try the updated fxp driver, which is available at http://www.flugsvamp.com/~jlemon/fbsd/drivers/Intel_EtherExpress/ This uses a different method for detecting the PHYs. >From a verbose boot of a generic kernel: > >Onboard fxp0 (the wacky one) >found-> vendor=0x8086, dev=0x1229, revid=0x09 This looks like an Intel Pro/100S Management Adapter. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message