From owner-freebsd-stable Sun Jan 7 15:57: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from leviathan.inethouston.com (216-118-21-146.pdq.net [216.118.21.146]) by hub.freebsd.org (Postfix) with ESMTP id 2718937B400 for ; Sun, 7 Jan 2001 15:56:49 -0800 (PST) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.com (Postfix) with ESMTP id 65BFF177E9F; Sun, 7 Jan 2001 18:01:46 -0600 (CST) Message-ID: <00c901c07906$2df88400$931576d8@inethouston.net> From: "David W. Chapman Jr." To: "Jeroen C. van Gelderen" , "David Kelly" Cc: , References: <200101072340.f07NemZ74202@grumpy.dyndns.org> Subject: Re: Intel PRO/100+ driver or hardware? Date: Sun, 7 Jan 2001 18:01:41 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've had a problem like this also with the cabling, where it worked fine with a 10mbps card but the 100mbps card would detect 100, but only really work at 10mbps(due to bad wiring/bad cabling). Are the rest of your cards that do work 10mbps? > > Anybody care to point out the obvious bits I've missed? > > I've seen "impossible" network problems like this traced to a bad > ethernet cable. One system ran fine for a year until I had to sit in > front of it for 5 mintues. Problem was its "CAT 5" cable was connected > 1:1, and not with the wires properly paired. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message