From owner-freebsd-hackers Mon Aug 11 18:50:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA15808 for hackers-outgoing; Mon, 11 Aug 1997 18:50:02 -0700 (PDT) Received: from cypher.net (black@zen.pratt.edu [205.232.115.155]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA15779 for ; Mon, 11 Aug 1997 18:49:58 -0700 (PDT) Received: (from black@localhost) by cypher.net (8.8.5/8.7.1) id VAA21887; Mon, 11 Aug 1997 21:54:31 -0400 Date: Mon, 11 Aug 1997 21:54:31 -0400 (EDT) From: Ben Black To: Tom Samplonius cc: David Greenman , hackers@FreeBSD.ORG Subject: Re: fxp driver full duplex packet loss problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk assuming the 1900 has the same software config commands as the 5500 then you should just be able to say: set port duplex full and it will automatically switch right then. On Mon, 11 Aug 1997, Tom Samplonius wrote: > > On Mon, 11 Aug 1997, Tom Samplonius wrote: > > > > > On Mon, 11 Aug 1997, Ben Black wrote: > > > > > a good indication of this duplex mismatch is a sudden appearance of FCS > > > errors and Runts on the cisco interface. > > > > When I switch full duplex on the FreeBSD server, the switch starts > > recording late collision errors on that port (a 10BT port on a Cat 1900). > > I'm not sure what this means. > > > > Tom > > Actually I do know (now) what that means. The switch (which is supposed > to auto-negotiate and has no manual setting) is set to half, and card is > set to full. > > I'm guessing the switch doesn't understand devices switching from half > to full on the fly, and only detects this on intial connect. I will try > turning full duplex on, and them plug it into a different port. > > Tom >