From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 16 18:08:33 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 6C27337B401 for ; Mon, 16 Jun 2003 18:08:33 -0700 (PDT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2B6543FBD for ; Mon, 16 Jun 2003 18:08:30 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from localhost (localhost [127.0.0.1]) by cain.gsoft.com.au (8.12.9/8.12.8) with ESMTP id h5H18ODo060578; Tue, 17 Jun 2003 10:38:25 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Mike Silbersack Date: Tue, 17 Jun 2003 10:38:23 +0930 User-Agent: KMail/1.5 References: <200306161909.33474.doconnor@gsoft.com.au> <20030616100658.X906@odysseus.silby.com> In-Reply-To: <20030616100658.X906@odysseus.silby.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200306171038.23826.doconnor@gsoft.com.au> X-Spam-Score: -1.5 () CARRIAGE_RETURNS,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) 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: Tue, 17 Jun 2003 01:08:33 -0000 On Tuesday 17 June 2003 00:40, Mike Silbersack wrote: > Well, there have been a few reports of similar problems. However, back > when those reports came in, there were a bunch of other problems with our > if_vr driver, so everyone gave up and switched network cards before we > could get to the duplex autoneg problem. :) Hehe :) > If possible, I'd like you to try some other brands of 100/FDX hubs and see > if autonegotiation works properly; this would help tell us if the problem > is general, or specific to that card. I don't have any other brands of 100/FDX switches :( I will try and dig one up, but I think the best I can do is a different generation switch from the same manufacturer. > Also, can you post the dmesg output relating to your card? I'm curious > which PHY device you have. Duh, knew I forgot something.. vr0: port 0xe800-0xe8ff mem 0xdd006000-0xdd0060ff irq 11 at device 18.0 on pci0 vr0: Ethernet address: 00:04:61:49:23:7c miibus1: on vr0 ukphy0: on miibus1 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vr0: flags=8843 mtu 1500 inet 203.31.81.48 netmask 0xffffffc0 broadcast 203.31.81.63 ether 00:04:61:49:23:7c media: Ethernet 100baseTX status: active -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5