Date: Wed, 7 Oct 1998 15:23:57 -0700 (PDT) From: Julian Elischer <julian@whistle.com> To: David Greenman <dg@root.com> Cc: Rich Fox <rich@f2sys.net>, freebsd-net@FreeBSD.ORG Subject: Re: Intel Pro/100B, unsupported type = 63, can't see network Message-ID: <Pine.BSF.3.95.981007151952.24389H-100000@current1.whistle.com> In-Reply-To: <199810071529.IAA13269@implode.root.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> >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 > > 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. I happen to be an expert at this particular bug... the serial eeprom has failed or is in some way not readable by the ethernet chip I have one here that did the same... I replaced the eeprom and it was fine.. We have two of these on a card we have here and before I got the eeproms programmed we could probe the card suggessfully but we'd get these symptoms (all 1 values read during the probe) julian 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?Pine.BSF.3.95.981007151952.24389H-100000>