From owner-freebsd-questions Wed Jun 28 16:25: 4 2000 Delivered-To: freebsd-questions@freebsd.org Received: from nisser.com (c1870039.telekabel.chello.nl [212.187.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 9020F37C233 for ; Wed, 28 Jun 2000 16:24:51 -0700 (PDT) (envelope-from roelof@nisser.com) Received: from nisser.com (roelof [10.0.0.2]) by nisser.com (8.9.3/8.9.2) with ESMTP id BAA71225 for ; Thu, 29 Jun 2000 01:24:47 +0200 (CEST) (envelope-from roelof@nisser.com) Message-ID: <395A89B1.204E32D6@nisser.com> Date: Thu, 29 Jun 2000 01:26:41 +0200 From: Roelof Osinga Organization: eboa - engineering buro Office Automation X-Mailer: Mozilla 4.72 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD Questions Subject: Re: NE2000 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FENIX wrote: > > I have this old NE2000 adapter working good with my 4.0-Release, i use the > adapter for mij lan, but as soon as the lan computer is off i get kernel > message device ed0 timeout. I know that it can be normal for some NIC's, but > does anyone knows how to fix this so i wont be getting messages every few > minutes ? Maybe it's time to retire those NE2K's? They're bound to be over a decade old by now. I know for a fact some of mine got retired just in the nick of time :) Anyway, maybe it's a just complaint. Then again, maybe it's just the age of the NIC showing. There's no way to be sure. Not by the way the 'recent' NE2K NIC clone's have deviated from The Path. You're better off buying a couple of El Cheapo PCI NICs. Iff your system supports PCI, of course Roelof PS your > lacks a MX record. -- ----------------------------------------------------------------------- Eboa (ingenieursburo Office Automation) web. http://eboa.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message