Doki (lkishalmi) solution works great for me. I`m impressed that i had
to correct it on ubuntu 10.10 maybe on next release it comes fixed. I
had to install cpufrequtils for the cpufreq indicator to work. Is not
very fast but for an old celeron M notebook working as a router ondemand
governator
FactTech, I don't think there will be any SRU updates for karmic. I
tried with the lucid kernel and FWIW, the change from the command line
works fine even though it takes quite a while to do so.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I see this issue is marked as fix released and nominated for karmic, but
what happens next? Will this be corrected in Lucid?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/432706
Title:
cannot
throwing my two cents in; i agree 100% with #23 (dan k.) -- the CPU
frequency scaling control capability and applet is one of my favorite
things about linux and the ubuntu/GNOME desktop environment, and i
attempt to enable it on every single machine i put ubuntu onto. i have
personally witnessed
ps. powernowd gives me back the behaviour i was looking for from the
'ondemand' setting, for anyone who wants to try that, last machine i
used this fix on was a toshiba C650D laptop with ubuntu 10.04.
--
cannot change governor from command line
https://bugs.launchpad.net/bugs/432706
You received
A binary hack is a silly way to have to fix something that should not
have been broken.
If ondemand is too slow - make the default performance so the user can
choose, rather than making ondemand work exactly the same way as
performance. Honestly, what is the point of having two policies that do
Ok, I finally tried out Doki's idea and it worked fine! :)
--
cannot change governor from command line
https://bugs.launchpad.net/bugs/432706
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Changing to ondemand doesn't work for me, too. I'm using lucid with a
P4 celeron 1,46GHz.
--
cannot change governor from command line
https://bugs.launchpad.net/bugs/432706
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Well you don't really need to recompile the module a simple binary hack
could solve the problem. The basic idea is that 1001 is 00989681 in
hex and stored in p4-clockmod.ko as 81969800 a simple search for it
and replace it with 80969800. So I did the following hack (far from
being optimal):
I'm seeing the same issue with the same apparent cause as Anno Loki
explains in comment #9. Like her, I disagree with this change; I'm
running Lucid on a Sony Vaio PCG-GRZ610 which is a tremendous power hog
when the ondemand setting is not available. I had it running for years
using ondemand under
I believe I am also experiencing the same bug.
I started trying to get CPU scaling enabled on my HP DL380 G3 (2x Xeon 2.4Ghz
HT) a couple of days back and wasn't having much luck using powernowd or the
command line to manually set governer.
I ended up using cpufreqd as this at least seemed to
I just upgraded to lucid and this is still a problem for me. I'm not
sure if there is any change I have to make but it doesn't seem to work
out of the box for me on lucid...
--
cannot change governor from command line
https://bugs.launchpad.net/bugs/432706
You received this bug notification
Rolf, is Anno's guidance enough to backport? This has been bugging me
for a while
--
cannot change governor from command line
https://bugs.launchpad.net/bugs/432706
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
crackbaby, I don't know. But I think I did try once something along
those lines and it did not fix the issue for me. Your best bet
currently is to run the lucid kernel.
--
cannot change governor from command line
https://bugs.launchpad.net/bugs/432706
You received this bug notification because
FYI (I'm not sure how relevant this still is) but 4294967295 is as
recognisable a number as 1001 is: it's -1 on a 32bit processor, or
0x.
The 1001 number in the kernel mod I use is assigned by
policy-cpuinfo.transition_latency = 1001;
A grep for other modules setting this:
This does indeed work in the Lucid kernel which as I was told runs
straight in karmic without recompilation. Setting to fix released. If
somebody figures out what it was exactly that fixed this and provides a
minimal patch I guess that could be backported to the 2.6.31 kernel for
inclusion in
Anno, great find. Thanks for sharing. But, my situation does not fit
your description.
$ cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_transition_latency
4294967295
Did this change recently or is this something changed in Ubuntu?
--
cannot change governor from command line
today's mainline kernel does not have this problem anymore. It's fixed
upstream.
next steps:
1) bisect to the upstream kernel that broke as well as the one that fixed this
2) recompile Lucid kernel to see if it's fixed there
** Tags added: regression-release
** Changed in: linux (Ubuntu)
I'm glad to finally figure out why ondemand doesn't work.
That said, I'm disappointed to hear the outcome.
I, for one, hope the Ubuntu community decides to reverse this kernel
decision
--
cannot change governor from command line
https://bugs.launchpad.net/bugs/432706
You received this bug
This has been deliverately broken in recent kernel as it's been deemed
too slow for us to carry on using. If like me you disagree, you can
reverse the change quite easily if you're building your own
kernel/modules, I'll try and post these details to where I can find
people who've hit the same
Count me in, same here, cannot change CPU frequency on a 2.0 GHz P4.
I can switch manually to powersave, all other governors show the too long
transition latency... mentioned above and fallback to performance.
--
cannot change governor from command line
https://bugs.launchpad.net/bugs/432706
I have a similar problem. I can't set the ondemand governer either
through the command line or GUI since upgrading to Karmic. Here is the
output of the above request from a boot to the previous kernel (it all
works here):
ti...@seq:~$ uname -a
Linux seq 2.6.28-15-generic #52-Ubuntu SMP Wed Sep 9
One additional note: I can manually (with the GUI app) set my clock
frequency to any of the supported frequencies (.25GHz -2GHz in .25GHz
steps), I just can't set the ondemand governer to make it autoscale.
--
cannot change governor from command line
https://bugs.launchpad.net/bugs/432706
You
Thank you for your bug report. That looks more like a kernel issue
rather than an applet one though
** Package changed: gnome-applets (Ubuntu) = linux (Ubuntu)
--
cannot change governor from command line
https://bugs.launchpad.net/bugs/432706
You received this bug notification because you are a
If it's a kernel bug, then it's not Ubuntu-specific. The mainline
kernel is no different.
--
cannot change governor from command line
https://bugs.launchpad.net/bugs/432706
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Please run:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo conservative | sudo tee
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo ondemand | sudo tee /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
cat
As I mentioned in our private chat, I have serious doubts this is a
kernel bug. I can switch governors with the applet, but using the CLI
fails.
$ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
performance
$ echo conservative | sudo tee
turns out, this is indeed a kernel bug after all. At least mainline
kernel 2.6.28-02062810-generic works fine. So, it's a fairly recent
regression. I'll disect in the next few days to find the latest working
kernel.
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Changed
28 matches
Mail list logo
