From owner-freebsd-stable Mon Dec 20 15:23:46 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ns.itga.com.au (ns.itga.com.au [192.83.119.129]) by hub.freebsd.org (Postfix) with ESMTP id 158B315377 for ; Mon, 20 Dec 1999 15:23:34 -0800 (PST) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by ns.itga.com.au (8.9.3/8.9.3) with ESMTP id KAA22122 for ; Tue, 21 Dec 1999 10:23:28 +1100 (EST) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by lightning.itga.com.au (8.9.3/8.9.3) with ESMTP id KAA13024; Tue, 21 Dec 1999 10:23:27 +1100 (EST) Message-Id: <199912202323.KAA13024@lightning.itga.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: stable@freebsd.org Subject: xl0 won't autoneg full duplex Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 21 Dec 1999 10:23:27 +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've got a <3Com 3c905B-TX Fast Etherlink XL> plugged into a Cisco Cat5500 100Mbps switch, and I'm been running various 3.x versions from 3.0-RELEASE up to the 3.4-RC from 13/12. This card is happy to run in Full Duplex mode if I force it with ifconfig. If left to autonegotiate with the switch, the xl0 comes up 100Mbps/half-duplex, but the switch comes up full duplex. Hence I get lotsa collisions (~20%). Anything I can do to try to sort this out? This is my personal w/s so I am happy to try experimental kernels, printf debugging etc. [Yes, I know I can force it by changing ifconfig_xl0 in rc.conf...] wpaul? xl0: <3Com 3c905B-TX Fast Etherlink XL> rev 0x00 int a irq 11 on pci0.17.0 xl0: Ethernet address: 00:10:5a:a9:84:33 xl0: autoneg complete, link status good (half-duplex, 100Mbps) Greg. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message