Date: Wed, 7 Oct 1998 10:53:17 -0400 (EDT) From: Rich Fox <rich@f2sys.net> To: freebsd-net@FreeBSD.ORG Subject: Intel Pro/100B, unsupported type = 63, can't see network Message-ID: <l03130300b240f165d635@[151.200.126.110]>
next in thread | raw e-mail | index | archive | help
Hi, 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<UP, BROADCAST, RUNNING, SIMPLEX, MULTICAST> 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 My first question is what is with the "manual" parts under media. I have seen other PRO/100B users' ifconfigs state things like "autoselect". if I try to add a "autoselect" media parameter to the ifconfig statement it gives me an error: "ifconfig: SIOCSIFMEDIA: device not configured" ifconfig man page says to check docs for the driver to determine available media types. I can not find documentation for fxp0 in the machine, the FreeBSD site, altavista, or yahoo. Second, error or not, the card *appears* to be accessing the network. That is, when I try to ping 192.168.1.3 (a mac quadra) the hub activity lights begin blink, but ultimately, ping returns "ping: sendto: host is down". When I ping the quadra off of my Starmax (192.168.1.2), I get total success. The Starmax can not ping the FreeBSD machine though. (I do not have a ping available on the quadra, so I have not tested from that machine.) Traceroute doesn't do any better in whatever circumstance. So basically, it looks to me like all of the computers are on the same network and accessing it, however FreeBSD machine, vs the rest of the computers, is on a different plane of existence. I do not have a sniffer that I can use, which is what I really want to do. There is something wrong with tcpdump on the FreeBSD 2.2.7 so that it won't run. I bought a power supply for my modest 486sx and my next move is to put it on the network and see if it can't fare any better at seeing these other machines, that is unless someone might have some insight as to what I can do to resolve the problem. Thanks, Rich. | rich fox | rich@f2sys.net | 1513 N. Rhodes St. #1 | Arlington, VA 22209 | t:703.528.9616 | f:703.329.2314 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?l03130300b240f165d635>