From owner-freebsd-net@FreeBSD.ORG Thu Oct 25 13:31:04 2007 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3318A16A419 for ; Thu, 25 Oct 2007 13:31:04 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from s200aog14.obsmtp.com (s200aog14.obsmtp.com [207.126.144.128]) by mx1.freebsd.org (Postfix) with SMTP id 8EC4A13C4B0 for ; Thu, 25 Oct 2007 13:31:02 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from source ([217.206.187.80]) by eu1sys200aob014.postini.com ([207.126.147.11]) with SMTP; Thu, 25 Oct 2007 13:31:01 UTC Received: from [10.0.0.89] (bill.mintel.co.uk [10.0.0.89]) by rodney.mintel.co.uk (Postfix) with ESMTP id 50E3B18141F; Thu, 25 Oct 2007 14:09:05 +0100 (BST) Message-ID: <47209570.20609@tomjudge.com> Date: Thu, 25 Oct 2007 14:09:04 +0100 From: Tom Judge User-Agent: Thunderbird 1.5.0.13 (X11/20070824) MIME-Version: 1.0 To: Garrett Cooper References: <20071019182349.J97691@odysseus.silby.com> <47194EA1.8000402@u.washington.edu> <20071019212012.C97691@odysseus.silby.com> <47202922.3070700@u.washington.edu> In-Reply-To: <47202922.3070700@u.washington.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: net@freebsd.org Subject: Re: Marvell chipsets on 8-CURRENT and XP x64 won't talk with one another X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Oct 2007 13:31:04 -0000 Garrett Cooper wrote: > Mike Silbersack wrote: >> >> On Fri, 19 Oct 2007, Garrett Cooper wrote: >> >>>> Just to clarify, how are the two hooked together? Is it over >>>> gigabit switch, a 10mbps hub, or directly cabled together? >>>> >>>> -Mike >>> >>> Sure. They're both connected over a gigabit switch, but the Windows >>> driver's kind of sketchy because it keeps on switching between >>> 100MBit and 1GBit. I haven't really paid that much attention to what >>> speed the FreeBSD msk driver is registering at. >>> -Garrett >> >> Ah ha! >> >> I had the flopping between 100mbps and 1gbps problem with some Intel >> cards once - some of the machines in the lab were fine, others kept >> switching back and forth. We eventually narrowed it down to the >> cables we had hand-made; some of them just weren't up to snuff, and >> the NIC apparently decided that it had to go back down to 100. >> >> I think you should switch your gigabit switch out for a 100mbps switch >> and see if the network becomes more reliable. >> >> -Mike > > I think I've discovered what the issue is. I believe the problem lies > in the fact that the FreeBSD Marvell chipset driver (msk) isn't up to > speed with the Gigabit transferring on my particular chipset(s). That's > why transfers were most likely working with my laptop (Apple with > 100MBit Broadcom) vs my desktop (Asus MB with another Marvell chipset > driver) and another laptop (Dell laptop with Broadcom Gigabit). > How do I tell ifconfig via rc.conf to downgrade the max speed to > 100MBit duplex? > Thanks, > -Garrett You would need to hard code the interface configuration on the switch and box. This is only possible if you have a managed switch and the methods on the switch are manufacturer and model dependent. On FreeBSD however it is trivial for example "ifconfig em0 media 100baseTX mediaopt full-duplex". This will disable speed negotiation and therefore must be configured at both ends of the link. Tom