Date: Tue, 3 Dec 2002 09:00:26 -0500 (EST) From: Andrew Gallatin <gallatin@cs.duke.edu> To: Brad Knowles <brad.knowles@skynet.be> Cc: cbiffle@safety.net, "Craig Reyenga" <creyenga@connectmail.carleton.ca>, <freebsd-current@FreeBSD.ORG> Subject: Re: Any ideas at all about network problem? Message-ID: <15852.47354.584019.485101@grasshopper.cs.duke.edu> In-Reply-To: <a05200f01ba119f5e79ff@[10.0.1.2]> References: <2668299.1038795112570.JavaMail.creyenga@connectmail.carleton.ca> <001001c299c7$766a6120$0200000a@sewer.org> <a05200f26ba10df70dc1d@[146.106.12.76]> <200212021532.03071.cbiffle@safety.net> <a05200f01ba119f5e79ff@[10.0.1.2]>
next in thread | previous in thread | raw e-mail | index | archive | help
Brad Knowles writes: > At 3:32 PM -0700 2002/12/02, Cliff L. Biffle wrote: > > > One thing I've used in the past that improves Realtek throughput is forcing > > the media type and duplex setting on both ends of the connection. Autodetect > > in the 8139s seems to be unreliable at times. > > This is true for most 10/100 Base-T implementations I've seen. > None of them have been able to reliably auto-detect. Any time I hear > someone complain of network throughput problems, this is one of the > first things I have them check. However, this would not seem to be > the case in this instance, unless 4.7 and 5.x are not handling > auto-detect in the same way. Phk made some large (and somewhat controversial, at the time) changes to the mii support code in -current about 7 months ago. Before blaming the mii code, I'd feel better if we knew a hardcoded connection worked better. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15852.47354.584019.485101>