From owner-freebsd-questions Tue Apr 7 12:49:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA25350 for freebsd-questions-outgoing; Tue, 7 Apr 1998 12:49:06 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA25323 for ; Tue, 7 Apr 1998 12:48:54 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.8) with SMTP id MAA26826; Tue, 7 Apr 1998 12:48:33 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Date: Tue, 7 Apr 1998 12:48:32 -0700 (PDT) From: Doug White Reply-To: Doug White To: Dan Williams cc: freebsd-questions@FreeBSD.ORG Subject: Re: network cards In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 6 Apr 1998, Dan Williams wrote: > I have recently put together a FreeBSD machine, and had some problems with > networking. First, I had 2.2.2 on it, and used an Infotek NE2000 > compatible network card. Everything was connected fine, and link lights > wer glowing. But the device timed out, as in ed1: kenel/device timeout. > This happened with a number of different NE2000 compatible cards. Hm, ed1. Is this a PCI card? Check that the interrupt it's getting assigned isn't being hogged by another device. > Next, I put on 2.2.5 with a 3Com 3C509. This was connected, but there was > no link light on the hub it was connected to. It also froze the machine > when running an Ifconfig on the ep0 driver. We are running 10BaseT. Bad cable? Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message