From: textshell@neutronstar.dyndns.org
To: linux-kernel@vger.kernel.org
Cc: Henrik Persson <nix@syndicalist.net>
Subject: Re: 2.6.0-test1: CPUFreq not working, can't find sysfs interface
Date: Sun, 20 Jul 2003 23:12:46 +0200 [thread overview]
Message-ID: <20030720211246.GK2331@neutronstar.dyndns.org> (raw)
In-Reply-To: <200307201745.h6KHjcHt095999@sirius.nix.badanka.com>
[please CC your replies, because i'm not subscribed]
On Sun, Jul 20, 2003 at 07:45:37PM +0200, Henrik Persson wrote:
> On Sun, 20 Jul 2003 17:02:43 +0200
> textshell@neutronstar.dyndns.org wrote:
>
> > [please CC your replies, because i'm not subscribed]
> >
> > I'm testing 2.6.0-test1 on my HP nx9005 Laptop (using a Mobile AMD
> > Athlon XP)
> >
> > But i can't get the sysfs interface of CPUFreq part to show up. I then
> > recomplied the kernel with both old (obsolete) /proc interfaces enabled.
> > The old interfaces both show up, but seem to be not working (but the is
> > my first try to get CPUFreq working with any kernel version). I googled
> > around for hours without finding any useful information for this case.
>
> My .config attached.. Hope that will help you..
>
> With this setup I have /sys/devices/system/cpu/cpu0/cpufreq/ and it's all
> working perfectly. I am also using a Mobile AMD Athlon XP.
>
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.
next prev parent reply other threads:[~2003-07-20 20:50 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 [this message]
2003-07-22 12:08 ` Dominik Brodowski
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=20030720211246.GK2331@neutronstar.dyndns.org \
--to=textshell@neutronstar.dyndns.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nix@syndicalist.net \
/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).