From owner-freebsd-current Tue Sep 22 00:12:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA05694 for freebsd-current-outgoing; Tue, 22 Sep 1998 00:12:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA05685 for ; Tue, 22 Sep 1998 00:12:21 -0700 (PDT) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id AAA10215 for ; Tue, 22 Sep 1998 00:11:43 -0700 (PDT) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id JAA04124 for freebsd-current@freefall.cdrom.com; Tue, 22 Sep 1998 09:11:36 +0200 (MEST) (envelope-from kuku) Date: Tue, 22 Sep 1998 09:11:36 +0200 (MEST) From: Christoph Kukulies Message-Id: <199809220711.JAA04124@gilberto.physik.RWTH-Aachen.DE> To: freebsd-current@freefall.cdrom.com Subject: de driver still problematic? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After upgrading to a before yesterday -current (aout) I sadly notice that the machine's uptime only lasted a couple of hours. I will drive to the campus later and look at it would I'll bet it's the de driver still causing cumber. Maybe I change the network card (solution by avoiding) though I'd rather get this problem sorted out and would like to try test code if anyone is working at the driver presently. -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de Latest feature of Visual C++ 6.0: 'Command-line builds' - msdev crc.dsw /MAKE "WinCRC - Win32 Debug" /Rebuild /OUT wincrc.log Taken from: MSJ Oct 98, p. 19 -- :-O To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message