From owner-freebsd-net@FreeBSD.ORG Wed May 3 03:44:02 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2017316A408 for ; Wed, 3 May 2006 03:44:02 +0000 (UTC) (envelope-from frank@exit.com) Received: from tinker.exit.com (tinker.exit.com [206.223.0.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88DDF43D48 for ; Wed, 3 May 2006 03:44:01 +0000 (GMT) (envelope-from frank@exit.com) Received: from wili.exit.com (wili.exit.com [206.223.0.194]) by tinker.exit.com (8.13.4/8.13.4) with ESMTP id k433i1Rn030128 for ; Tue, 2 May 2006 20:44:01 -0700 (PDT) (envelope-from frank@exit.com) Received: from wili.exit.com (localhost [127.0.0.1]) by wili.exit.com (8.13.4/8.13.4) with ESMTP id k433bVr0069265 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 2 May 2006 20:37:32 -0700 (PDT) (envelope-from frank@exit.com) Received: (from www@localhost) by wili.exit.com (8.13.4/8.13.4/Submit) id k433bVb3069264; Tue, 2 May 2006 20:37:31 -0700 (PDT) (envelope-from frank@exit.com) X-Authentication-Warning: wili.exit.com: www set sender to frank@exit.com using -f Received: from 206.223.0.35 (SquirrelMail authenticated user frank) by www.exit.com with HTTP; Tue, 2 May 2006 20:37:31 -0700 (PDT) Message-ID: <55164.206.223.0.35.1146627451.squirrel@www.exit.com> Date: Tue, 2 May 2006 20:37:31 -0700 (PDT) From: frank@exit.com To: freebsd-net@freebsd.org User-Agent: SquirrelMail/1.4.6 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: ClamAV 0.88/1436/Tue May 2 10:41:37 2006 on tinker.exit.com X-Virus-Status: Clean Subject: AMD 760 chipset/BCM5700 interaction. 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: Wed, 03 May 2006 03:44:02 -0000 I just replaced a flakey Intel gigabit nic with a BCM5700-based 3Com nic, thinking that would work better. Silly me. It seems there's a nasty interaction between the chipset and the nic, which 3Com solved with a driver release. From the Tyan site: # Why can't I browse Network Neighborhood with my 3Com 3C996 Gigabit Ethernet Adapter? This is a driver issue with the 3c996 Gigabit Ethernet card and the AMD chipset. 3Com has released drivers to resolve this issue. The drivers are dated 12-18-01 & can be downloaded from [...] So does anyone know the details of this interaction. Might there be a fix anywhere? Or should I just bite the bullet and get a newer Intel board? -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/