From owner-freebsd-hardware Sat Jan 16 11:45:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14693 for freebsd-hardware-outgoing; Sat, 16 Jan 1999 11:45:37 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from mired.eh.local (kstreet.interlog.com [198.53.146.171]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA14680 for ; Sat, 16 Jan 1999 11:45:24 -0800 (PST) (envelope-from street@iname.com) Received: (from kws@localhost) by mired.eh.local (8.9.1/8.9.1) id OAA98912; Sat, 16 Jan 1999 14:43:36 -0500 (EST) (envelope-from kws) To: "Alex S. Burba" Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: 3com905b-TX References: <199901162024.UAA09882@ns.cormoran.ru> From: Kevin Street Date: 16 Jan 1999 14:43:35 -0500 In-Reply-To: "Alex S. Burba"'s message of "Sat, 16 Jan 1999 20:24:04 GMT" Message-ID: <87sodbc8bc.fsf@mired.eh.local> Lines: 22 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Alex S. Burba" writes: > I can not make work my 3com905b-TX in 100 mbit (full-duplex), it > works in half-duplexm only. We have a 100 mbit (full-duplex) Compex's > hub. Also, two Windows NT with 3com905B-TX are connected to this hub > and they work in full-duplex. How can I set up my FreeBSD server to > work in full-duplex?? Mine is detected in half-duplex, but I can flip it to full by putting a line like this in /etc/rc.conf.local: ifconfig_xl0="inet media 100baseTX mediaopt full-duplex" I've been assuming that the detection problem was because I just have mine on a crossover cable (no hub) which 3Com says can cause this problem. Since you see this on a hub though, perhaps there is a bug in the detection logic in the driver. In any case, you should be able to force it in the rc files or by using ifconfig yourself. -- Kevin Street street@iName.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message