linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@brodo.de>
To: textshell@neutronstar.dyndns.org, davej@suse.de
Cc: linux-kernel@vger.kernel.org, Henrik Persson <nix@syndicalist.net>
Subject: Re: 2.6.0-test1: CPUFreq not working, can't find sysfs interface
Date: Tue, 22 Jul 2003 16:23:53 +0200	[thread overview]
Message-ID: <20030722142353.GA1301@brodo.de> (raw)
In-Reply-To: <20030722141839.GD7517@neutronstar.dyndns.org>

On Tue, Jul 22, 2003 at 04:18:39PM +0200, textshell@neutronstar.dyndns.org wrote:
> So it seems to me that the BIOS doesn't have the tables for my Athlon
> model/stepping. I tried to get a new bios from hp, but it didn't change anything
> relevant (they changed something in the PSTs but did not add a new one for my
> processor)

Indeed, that's the BUG().

> > I guess it's yet another BIOS problem... [as seen quite often wrt AMD
> > PowerNow, unfortunately]
> 
> I think it would be a good thing to display a Message explaining why powernow
> isn't working to the user in the case that no relevant PST is found.

Patch appended at the end.

> Can you suggest any workaround for this problem, or is my only option to
> complain to HP do supply an updated BIOS. 

Well, you could try using the PST which mostly matches your system except
the CPUID [PST #12, see below] -- if the values used are similar to the ones
Windows XP uses. But this might be risky!!!

> I very much would like to have a way to override (or add to) the bios provided
> values.

AFAIK, Dave Jones will add support to override the BIOS-provided tables.

>  --DEBUG: 7a0 ?= 781 && 21 ?= 21, 11 ?= 11
>  PST:12 (@0x4017d8dc)
>   cpuid: 0x781	  fsb: 133	  maxFID: 0x15	  startvid: 0xb
>   num of p states in this table: 6
>     FID: 0x12 (4.0x [532MHz])	VID: 0x13 (1.200V)
>     FID: 0x4 (5.0x [665MHz])	VID: 0x13 (1.200V)
>     FID: 0x6 (6.0x [798MHz])	VID: 0x13 (1.200V)
>     FID: 0x8 (7.0x [931MHz])	VID: 0x13 (1.200V)
>     FID: 0xe (10.0x [1330MHz])	VID: 0xe (1.300V)
>     FID: 0x15 (13.5x [1796MHz])	VID: 0xb (1.450V)

	Dominik

diff -ruN linux-original/arch/i386/kernel/cpu/cpufreq/powernow-k7.c linux/arch/i386/kernel/cpu/cpufreq/powernow-k7.c
--- linux-original/arch/i386/kernel/cpu/cpufreq/powernow-k7.c	2003-07-11 14:12:35.000000000 +0200
+++ linux/arch/i386/kernel/cpu/cpufreq/powernow-k7.c	2003-07-22 16:16:00.000000000 +0200
@@ -345,6 +345,7 @@
 						p+=2;
 				}
 			}
+			dprintk (KERN_INFO PFX "Did not find any PST table for this CPU -- exiting\n");
 			return -EINVAL;
 		}
 		p++;

  reply	other threads:[~2003-07-22 14:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-20 15:02 2.6.0-test1: CPUFreq not working, can't find sysfs interface textshell
2003-07-20 17:45 ` Henrik Persson
2003-07-20 21:12   ` textshell
2003-07-22 12:08     ` Dominik Brodowski
2003-07-22 14:18       ` textshell
2003-07-22 14:23         ` Dominik Brodowski [this message]
2003-07-22 14:42           ` Dave Jones
2003-07-22 14:53           ` textshell
2003-07-23 11:13             ` Pavel Machek
2003-07-23 11:28               ` Richard B. Johnson
2003-07-23 12:30                 ` Pavel Machek
2003-07-23 16:36             ` Dominik Brodowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030722142353.GA1301@brodo.de \
    --to=linux@brodo.de \
    --cc=davej@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nix@syndicalist.net \
    --cc=textshell@neutronstar.dyndns.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).