From owner-freebsd-current Fri Aug 21 16:57:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16480 for freebsd-current-outgoing; Fri, 21 Aug 1998 16:57:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-d3.dialup.hilink.com.au [203.2.144.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16474 for ; Fri, 21 Aug 1998 16:57:44 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA10776; Fri, 21 Aug 1998 16:55:20 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808211655.QAA10776@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith cc: freebsd-current@FreeBSD.ORG Subject: Re: 13 months of user time? In-reply-to: Your message of "Fri, 21 Aug 1998 04:53:10 GMT." <199808210453.EAA07850@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Aug 1998 16:55:18 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >Then in my case anyway, it's not a problem of disabling APM or not: > > >unless I'm severely mistaken about my motherboard (Asus T2P4) and > > >its BIOS settings, it's NOT an APM system. > > > > I think it has APM, check the BIOS setting... > > Only with recent BIOS upgrades. It doesn't support clock idling either. Actually, I should correct myself there; *if* I recall the part number correctly, that's a 430FX-based board, and I don't believe that said chipset supports clock idling of any sort. The clock may still "jump" forwards courtesy of SMI activity, etc. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message