Date: Tue, 05 Dec 2000 06:58:07 -0800 From: David Greenman <dg@root.com> To: "Koster, K.J." <K.J.Koster@kpn.com> Cc: "'FreeBSD Hackers mailing list'" <freebsd-hackers@FreeBSD.ORG>, "Metz, E.T." <E.T.Metz@kpn.com> Subject: Re: yet another unsupported PHY in fxp driver Message-ID: <200012051458.GAA23226@implode.root.com> In-Reply-To: Your message of "Tue, 05 Dec 2000 15:52:20 %2B0100." <59063B5B4D98D311BC0D0001FA7E4522026D7A88@l04.research.kpn.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>Say what? I lived under the impression that MAC addresses were unique. Here >I have three cards that have identical MAC adresses. > >Finally, we finish off with: > >bpf: fxp0.0 attached >fxp1: warning: unsupported PHY, type = 0, addr = 0 >bpf: fxp1.0 attached >fxp2: warning: unsupported PHY, type = 0, addr = 0 >bpf: fxp2.0 attached >fxp3: warning: unsupported PHY, type = 0, addr = 0 >bpf: fxp3.0 attached >fxp3: link media DOWN 10Mb / half-duplex >fxp2: link media DOWN 10Mb / half-duplex >fxp0: link media DOWN 10Mb / half-duplex >fxp1: link media DOWN 10Mb / half-duplex > >The dmesg is from FreeBSD 2.2.8 (boot -v) by the way, but booting 4.1 yields >the same results. > >Now (finally) my question: how do we get this particular PHY supported? This >seems to have remained unanswered back in October. All of the above is caused by the SEEPROM not being read properly. Since it doesn't work with 4.1, this probably indicates that you're using an on-motherboard NIC (Supermicro?). I'm running out the door to the airport, however, and won't be able to get a fix to you until next week. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200012051458.GAA23226>