From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 19 21:13:37 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 70D0237B401 for ; Thu, 19 Jun 2003 21:13:37 -0700 (PDT) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 8940A43F75 for ; Thu, 19 Jun 2003 21:13:36 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 62842 invoked from network); 20 Jun 2003 04:13:35 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 20 Jun 2003 04:13:35 -0000 X-pair-Authenticated: 209.68.2.70 Date: Fri, 20 Jun 2003 01:13:30 -0500 (CDT) From: Mike Silbersack To: Daniel O'Connor In-Reply-To: <200306201252.34849.doconnor@gsoft.com.au> Message-ID: <20030620010232.T3614@odysseus.silby.com> References: <200306161909.33474.doconnor@gsoft.com.au> <200306171729.20775.doconnor@gsoft.com.au> <200306201252.34849.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org Subject: Re: vr(4) duplex problems X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jun 2003 04:13:37 -0000 On Fri, 20 Jun 2003, Daniel O'Connor wrote: > Hmm, well all I could manage was a 5 port micro switch. It is made by Alloy > but can autodetect crossover (MDX?). It works fine with the vr port doing > autodetect, so I guess it's an interaction with the older switch. > > No idea how ammenable to software fixing that would be though :( > > -- > Daniel O'Connor software and network engineer Actually, it may be possible to fix through software. The fact that your card is using "ukphy" means that we're using the generic PHY support, which may be doing something slightly wrong for whatever PHY is actually present on your NIC. If you look through the various *_phy drivers, you'll see that some have tiny little variations necessary for proper operation... However, since we've established that vr autodetects fine on some hubs, and that you can force the duplex and have it work ok, I don't think it's worth the time to track down the problem. (After all, it may not be solvable through software.) However, if you have an interest in learning about the internal workings of PHYs, I'll be glad to commit patches for you. :) Mike "Silby" Silbersack