public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* CPUFreq sysfs interface MIA?
@ 2003-05-06  7:29 Daniel Pittman
  2003-05-06 21:12 ` Greg KH
  0 siblings, 1 reply; 7+ messages in thread
From: Daniel Pittman @ 2003-05-06  7:29 UTC (permalink / raw)
  To: linux-kernel

Under both 2.5.68 and 2.5.69 the CPUFreq /sys interface seems to be
missing for my machine (IBM A31p), with an Intel 845 Brookdale chipset
and SpeedStep support.

It was certainly present around 2.5.67 or so, but seems to have vanished
since that point. I have not yet tracked down exactly where it went MIA.

Since I couldn't work out from either the documentation or the code if
there should be a /sys/devices/sys/cpu0/cpufreq directory when the code
is compiled in, but not active, I couldn't tell if this was failing to
find the SpeedStep support now or if it simply lost the sysfs interface.

When I compiled in the debug information to the SpeedStep driver, I only
get the following output in dmesg:

cpufreq: Intel(R) SpeedStep(TM) support $Revision: 1.70 $


The ACPI P-States driver and the P4 clock modulation driver don't work,
or cause the interface directory to show either, but I have never had
either of those two working before -- I tried them to try and eliminate
a cause.

The content of /sys/devices/sys/cpu0 is:
/sys/devices/sys/cpu0
|-- name
`-- power

0 directories, 2 files

   Daniel

-- 
That's the point of quotations you know; one can use another's words
to be insulting.
        -- Amanda Cross

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2003-05-08  1:50 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-05-06  7:29 CPUFreq sysfs interface MIA? Daniel Pittman
2003-05-06 21:12 ` Greg KH
2003-05-07  0:36   ` Daniel Pittman
2003-05-07 23:32     ` Greg KH
2003-05-08  0:23       ` Daniel Pittman
2003-05-08  0:32         ` Greg KH
2003-05-08  2:02           ` Daniel Pittman

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox