From owner-freebsd-stable Sun Jan 7 15:42:10 2001 Delivered-To: freebsd-stable@freebsd.org Received: from grumpy.dyndns.org (user-24-214-56-41.knology.net [24.214.56.41]) by hub.freebsd.org (Postfix) with ESMTP id DEFD537B698 for ; Sun, 7 Jan 2001 15:40:56 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by grumpy.dyndns.org (8.11.1/8.11.1) with ESMTP id f07NemZ74202; Sun, 7 Jan 2001 17:40:48 -0600 (CST) (envelope-from dkelly@grumpy.dyndns.org) Message-Id: <200101072340.f07NemZ74202@grumpy.dyndns.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Jeroen C. van Gelderen" Cc: freebsd-stable@FreeBSD.ORG, dkelly@grumpy.dyndns.org Subject: Re: Intel PRO/100+ driver or hardware? In-Reply-To: Message from "Jeroen C. van Gelderen" of "Sun, 07 Jan 2001 15:21:02 -0400." <128310000.978895262@grolsch.ai> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 07 Jan 2001 17:40:48 -0600 From: David Kelly Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jeroen C. van Gelderen" writes: > My tentative conclusion is that the Intel NICs don't work with my hub, even > though they should. As my hub seems to work with other cards, I'm > suspecting an Intel PRO/100+ specific problem. I can't determine whether it > is a hardware or a software problem though :-( > > 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. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message