As I recall, Chris Foote wrote:
> These symptoms sound like they're caused by duplex mismatch problems.
>
> Try forcing half or full-duplex options and test again - i.e. use
> media and mediaopt flags in your /etc/rc.conf. Available values for
> these are in `man fxp`.
If you've selected "autoselect" for the media, is there then a way
to determine what was negotiated? That is:
+---------------
| chad> grep fxp /var/run/dmesg.boot
| fxp0 <Intel EtherExpress Pro 10/100B Ethernet> rev 2 int a irq 10 on pci0:10:0
| fxp0: Ethernet address 00:a0:c9:49:ec:ca
|
| chad> ifconfig fxp0
| fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
| inet 192.168.1.129 netmask 0xffffff00 broadcast 192.168.1.255
| ether 00:a0:c9:49:ec:ca
| media: autoselect
| supported media: autoselect 100baseTX <full-duplex> 100baseTX 10baseT/UTP
|<full-duplex> 10baseT/UTP
+---------------
How can I tell if this interface is running 100/full or 10/half?
-crl
--
Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm?
[EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
