From owner-freebsd-hackers Sun Dec 14 17:16:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA01131 for hackers-outgoing; Sun, 14 Dec 1997 17:16:14 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA01106 for ; Sun, 14 Dec 1997 17:16:02 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id LAA00251; Mon, 15 Dec 1997 11:40:22 +1030 (CST) Message-Id: <199712150110.LAA00251@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Karl Pielorz cc: hackers@freebsd.org Subject: Re: /kernel 'calcru' negative offset? In-reply-to: Your message of "Sun, 14 Dec 1997 23:27:16 -0000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 15 Dec 1997 11:40:21 +1030 From: Mike Smith Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I've posted this in the questions list - but not gotten any replies... I'm > running FreeBSD 2.2.5-Release on a laptop (one that sadly doesn't work > with the PAO laptop support patches / drivers etc.) Can you be more specific (not here, but on the -mobile list) about your problems? We may not be able to help, but without knowing we certainly can't. > When the system boots - the kernel thinks the CPU is only 50Mhz (instead > of 100Mhz) - It's an Intel Pentium 100. This is when running the laptop in > 'brain dead' mode, i.e. no power saving, no spinning down of the harddrive > etc. - and no APM idleing the CPU when it thinks it's not busy... What mode is the unit in? Some systems (eg. this Toshiba) save the current power mode across reboots, so if I shut it down having hotkeyed into Low, when I bring it back up, it will still be in Low. > I've fiddled around with the kernel config - in particular the > CLK_CALIBRATION type config options - all to no avail... > > Is there a way of forcing the kernel to beleive the CPU is 100Mhz? - > intead of 50Mhz? If the kernel measures the clock as being 50MHz, then either your realtime clock is broken, or the CPU *is* running at 50MHz. mike