From owner-freebsd-hardware Thu Apr 13 1:42:58 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from router.difi.de (router.difi.de [212.6.96.2]) by hub.freebsd.org (Postfix) with ESMTP id 6B3C937B67F for ; Thu, 13 Apr 2000 01:42:55 -0700 (PDT) (envelope-from uwe.laverenz@difi.de) Received: from max.difi.de (max [192.168.1.2]) by router.difi.de (8.9.3/8.9.3) with ESMTP id KAA11434 for ; Thu, 13 Apr 2000 10:42:53 +0200 (CEST) (envelope-from uwe.laverenz@difi.de) Received: from difi.de (edv1.difi.de [192.168.1.54]) by max.difi.de (8.9.3/8.9.3) with ESMTP id KAA19535 for ; Thu, 13 Apr 2000 10:42:53 +0200 (CEST) (envelope-from uwe.laverenz@difi.de) Message-ID: <38F5888D.2243A455@difi.de> Date: Thu, 13 Apr 2000 10:42:53 +0200 From: Uwe Laverenz Organization: DIFI Dierk Filmer GmbH X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: hardware@FreeBSD.ORG Subject: Re: Compaq ThunderLan (was:squid server) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Rick, > - the internal ThunderLan NIC's in mine sometimes go to sleep - not sure why > but they simply stop working once in a while. Not sure if upgrading from 3.1 > to 3.4/3.5 would resolve this but it is mainly an irritant. I think upgrading wouldn't change anything. I have a Proliant 800 with a Thunderlan NIC and the problem is just the same with FreeBSD 4.0. If I can't fix this, I'll have to put in one of my last remaining DE-500BAs from DEC... Uwe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message