That just means you have no cpu scaling support.
The majority of users have that device path, so it will work for them.
** Changed in: sysvinit (Ubuntu)
Status: New = Invalid
--
ondemand initscript refers to a non-existent entry in /sys
https://bugs.launchpad.net/bugs/348715
You
That's a bit odd - it's running a fully updated Jaunty system, on an
Intel Core 2 CPU.
On other systems, with the same CPU, I have these device paths. So is
this a kernel bug instead?
--
ondemand initscript refers to a non-existent entry in /sys
https://bugs.launchpad.net/bugs/348715
You
On Thu, 2009-03-26 at 11:27 +, RichardNeill wrote:
That's a bit odd - it's running a fully updated Jaunty system, on an
Intel Core 2 CPU.
On other systems, with the same CPU, I have these device paths. So is
this a kernel bug instead?
Unlikely - some Intel CPUs simply don't support
Thanks for your help. It's still odd - that device path exists on my
other system. Both systems have the same CPU (Q6600), though my other
system runs Mandriva 2009.0. I haven't done anything special in the
BIOS other than the defaults.
Attachment: proc/cpuinfo, lsmod, dmesg
Incidentally, none
On Thu, 2009-03-26 at 13:46 +, RichardNeill wrote:
Incidentally, none of the cpufreq* modules seem to be available on
Jaunty:
These are all built-in to the kernel.
Scott
--
Scott James Remnant
sc...@canonical.com
--
ondemand initscript refers to a non-existent entry in /sys
On Thu, 2009-03-26 at 13:46 +, RichardNeill wrote:
Thanks for your help. It's still odd - that device path exists on my
other system. Both systems have the same CPU (Q6600), though my other
system runs Mandriva 2009.0. I haven't done anything special in the
BIOS other than the defaults.
I thought that the modules might be built-in - that would explain the
lack of needing to modprobe them, and the fact that they aren't
available. But the CPU should definitely support scaling, so this seems
to be a kernel bug.
Is there anything else I can do to test?
--
ondemand initscript
