linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@brodo.de>
To: textshell@neutronstar.dyndns.org
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 14:08:11 +0200	[thread overview]
Message-ID: <20030722120811.GD1160@brodo.de> (raw)
In-Reply-To: <20030720211246.GK2331@neutronstar.dyndns.org>

> I tried your config (with just one change, i enabled reiserfs, i use it for my
> root fs) but It's the same. /sys/devices/system/cpu/cpu0/ is just empty, no
> change.
> 
> I tried with gcc 2.95.4 (as shipped with debian testing) and gcc 3.3.1 (same)
> but neither solved to problem.
> What else could be the Problem? I assume problems loading modules or such
> userspace problems can't cause this behaviour?
> 
> Any help diagnosing the problem appricatied,
> 
> Martin H.

What's the output [if any] in "dmesg" starting with either "cpufreq" or
"powernow"?

I guess it's yet another BIOS problem... [as seen quite often wrt AMD
PowerNow, unfortunately]

	Dominik

  reply	other threads:[~2003-07-22 12:08 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 [this message]
2003-07-22 14:18       ` textshell
2003-07-22 14:23         ` Dominik Brodowski
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=20030722120811.GD1160@brodo.de \
    --to=linux@brodo.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).