From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 29 12:41:44 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE56A16A4CE for ; Mon, 29 Dec 2003 12:41:43 -0800 (PST) Received: from iscan1.intra.oki.co.jp (okigate.oki.co.jp [202.226.91.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CE7943D41 for ; Mon, 29 Dec 2003 12:41:39 -0800 (PST) (envelope-from yamamoto436@oki.com) Received: from aoi.okilab.oki.co.jp (localhost.localdomain [127.0.0.1]) by iscan1.intra.oki.co.jp (8.9.3/8.9.3) with SMTP id FAA24030 for ; Tue, 30 Dec 2003 05:41:37 +0900 Received: (qmail 4327 invoked from network); 30 Dec 2003 05:41:36 +0900 Received: from tulip.okilab.oki.co.jp (172.24.23.187) by aoi.okilab.oki.co.jp with SMTP; 30 Dec 2003 05:41:36 +0900 Received: from localhost (tulip [172.24.23.187])hBTKgO1f018567; Tue, 30 Dec 2003 05:42:24 +0900 (JST) (envelope-from yamamoto436@oki.com) Date: Tue, 30 Dec 2003 05:42:24 +0900 (JST) Message-Id: <20031230.054224.41627160.yamamoto436@oki.com> To: ohoyer@gaff.hhhr.ision.net From: Hideki Yamamoto In-Reply-To: <20031229.193152.104097268.yamamoto436@oki.com> References: <20031229.150542.41696894.yamamoto436@oki.com> <20031229100720.X65076@gaff.hhhr.ision.net> <20031229.193152.104097268.yamamoto436@oki.com> X-Mailer: Mew version 2.2 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-hardware@freebsd.org Subject: Re: Link up problem between 1000base-SX(bge) and SUN X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2003 20:41:44 -0000 Hi, I added code to recognize 3com 1000base-SX card as miibus module and compiled them, but I do not have time to test yet. I think this may solove my original problem that link of SUN SX card does not go up, though 3com card goes up well. I will start testing it from Jan.4,2004. I uploaded the fixed code on my web page, http://members.aol.com/hyama99/. I appreciate If someone gives me comments on the code before testing. Regards, Hideki Yamamoto From: Hideki Yamamoto Subject: Re: Link up problem between 1000base-SX(bge) and SUN Date: Mon, 29 Dec 2003 19:31:52 +0900 (JST) Message-ID: <20031229.193152.104097268.yamamoto436@oki.com> > > Hello again, > > Thank you for your reply. > > From: Olaf Hoyer > Message-ID: <20031229100720.X65076@gaff.hhhr.ision.net> > > > On Mon, 29 Dec 2003, Hideki Yamamoto wrote: > > > > > > > > Hello, > > > > > > I'm having a problem about link up between 1000base-SX(bge) and SUN. > > > > > > I tried yesterday's 4.9-stable on a FreeBSD box with two 3COM > > > 3C996-SXs and two onboard BMC5703 chips. Two 3COM 3C996-SX board link > > > went up, but the other side, a 1000base-SX I/F on SUN F280 did not go > > > up. When doing ping command to SUN from FreeBSD box, LED on 3C996 > > > were brinking but nothing happened to SUN board. I changed bge0 to > > > bge2, but the situation was the same. Hardware diagram is as follows. > > > bge0 can send or receive packates to the router or another PC with > > > intel SX board. > > > > > > Is this related to AUTO negotiation? > > > > Hi! > > > > Sometimes SUN cards are a bit picky. > > But, lets start gathering additional data: > > > > I assume you have a ge-card in, or which card are you using in the 280? > > The man page says that autoneg is performed, but chooses : > > Yes, I have three 'ge' cards in one F280R. > > > > > The GEM PCS is capable of performing auto-negotiation > > using the remote (or link partner) link end and receives the > > capabilities > > of the remote end. It selects the highest common demonina- > > tor mode of operation based on priorities. The ge driver > > also supports forced-mode operation under which the driver > > selects the mode of operation > > > > > > > > > > I assume that the interface is plumbed, and shows up in ifconfig as > > well, could you also post the snippet of the ifconfig entry? > > The machine is in a data center now. I cannot type ifconfig now. > > > > I cannot find any parameters about AUTO negotiation in 'bge' driver > > > source. I checked Linux 2.4.22 kernel source and have found the > > > several code about auto negotiation. I wonder if a linux box works > > > well. I do not need full support of auto negotiation, but sample code > > > that handles auto negotiation with Solaris machine. > > > > in bge(4) it is stated, that the bge's also support autoneg over a > > cross-cable-config (which this basically is). > > But: have a look at the link0 option there (can be adjusted via > > ifconfig) normally, autoneg shall do, but over a cross-cable you need to > > designate one end being master, other end being slave. > > > > My suspicion is, that autoneg procedure somewhere fails, and you should > > try to set the bge to be link master. > > > > Thank you for your advice. -----