From owner-freebsd-net Wed Oct 7 08:30:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11596 for freebsd-net-outgoing; Wed, 7 Oct 1998 08:30:38 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA11498 for ; Wed, 7 Oct 1998 08:30:17 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id IAA13269; Wed, 7 Oct 1998 08:29:24 -0700 (PDT) Message-Id: <199810071529.IAA13269@implode.root.com> To: Rich Fox cc: freebsd-net@FreeBSD.ORG Subject: Re: Intel Pro/100B, unsupported type = 63, can't see network In-reply-to: Your message of "Wed, 07 Oct 1998 10:53:17 EDT." From: David Greenman Reply-To: dg@root.com Date: Wed, 07 Oct 1998 08:29:24 -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I have been searching the archives for solutions to this problem, but I >haven't found any in the last 20 hours. > >I have FreeBSD 2.2.7 (which I get on subscription, I haven't received 2.2.8 >or 3.0 yet. I also do not have the capacity to upgrade this via the net.) >I have an Intel EtherExpress Pro/100B... >When I ifconfig the EtherExpress I get an unsupported PHY, type = 63 > >"portal# Oct 7 10:17:04 portal /kernel: fxp0: warning: unsupported PHY, >type = 63, addr = 255 >portal# Oct 7 10:17:04 portal /kernel: fxp0: warning: unsupported PHY, type >= 63, addr = 255" >(yes, it repeats the message twice.) > >In the list archives I saw type = 7 and type = 1. >It is understood that this card *should* work at 10mbps, the unsupported >error may only cause it to fail if I try to run it at 100Mbps. > >If I do an ifconfig -a I get: >fxp0 flags=8843 mtu 1500 > inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 > ether ff:ff:ff:ff:ff:ff > media: manual > supported media: manual Yikes. Are you sure that is a Pro/100B card? It seems to have totally failed to properly read the SRAM, including the ethernet MAC address. The card WILL NOT WORK in this case, so don't waste anymore time trying to test it. I wonder if the SRAM chip on the board might be different than the standard chip, or if perhaps the chip is actually defective? I'll need more info (like chip numbers, age of board, dmesg output, type of system this is being put into, etc.) before I can make any further guesses. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message