*** This bug is a duplicate of bug 1885730 ***
https://bugs.launchpad.net/bugs/1885730
We are finally fixing this.
** This bug has been marked a duplicate of bug 1885730
Please switch default, hwe, oem kernel flavours governor to
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y , such that
I think this is still present in 14.04/14.10. I'm talking about the
issue with cpufreqd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/344252
Title:
CPU Frequency Scaling defaults to Performance
This bug shows up in Ubuntu 10.10 64bit too. My CPU: AMD Athlon II X2
250.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/344252
Title:
CPU Frequency Scaling defaults to Performance instead of
Solution from comment #42 works for me, even after resuming from sleep
it is respecting the ondemand setting. In summary:
edit:
/etc/rc.local
add:
cpufreq-selector -g ondemand
I have a Toshiba Tecra M10 Core2Duo 2.4GHz processor. Thanks for the
help!
--
You received this bug notification
Andy, thanks!
I'm glad to be helpful. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/344252
Title:
CPU Frequency Scaling defaults to Performance instead of OnDemand
--
ubuntu-bugs mailing list
Hi Scaine,
Please be sure to confirm this issue exists with the latest development release
of Ubuntu. ISO CD images are available from
http://cdimage.ubuntu.com/daily/current/ . If the issue remains, please run
the following command from a Terminal (Applications-Accessories-Terminal).
It
I've changed laptops since reporting this bug 18 months ago. This is no
longer the case on my Toshiba Satellite U405. I can no longer
contribute to this bug except to suggest that this bug would go away if
the app remembered what the user chose and stick to it. A common trait
on the Gnome
I can confirm the performance default governor is setted also in the
last Ubuntu 10.10 Maverick Kernel 2.6.35-23.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
CPU Frequency Scaling defaults to Performance instead of OnDemand
I also have this bug. The cpufreq govenor is always set to performance
selecting the maximum freq (1.83GHz) for my 2 cores. I have to execute
sudo cpufreq-set -g ondemand -d 100 -u 1833000 -c 0
sudo cpufreq-set -g ondemand -d 100 -u 1833000 -c 1
to get to ondemand.
Annoyingly it does
The only way around it is to create a cronjob as root and reset to
ondemand every once and awhile:
cronjob -e
add a job (every minute)
*/1 * * * * /usr/bin/cpufreq-set -g ondemand -d 100 -u 1833000 -c 0
*/1 * * * * /usr/bin/cpufreq-set -g ondemand -d 100 -u 1833000 -c 1
Ugly as hell
OK, I think I got it...well at least for you guys having speed stepped
Intel CPUs:
just edit '/etc/cpufreqd.conf' and make sure that the settings are
correct. For me the default settings were
##
# Basic states
##
# when AC use performance mode
[Rule]
name=AC Rule
ac=on#
I was having the same issue so I try this:
$ sudo start-stop-daemon --stop --name cpufreqd
$ sudo cpufreqd -D -V 7
That started the cpufreq daemon and print how the rules were evaluated.
So I find out than the problem is in the temp sensors. The sensors always shows
50ºC (122ºF) which is wrong
My laptop sometimes does not switch to ondemand as it should be. Calling
/etc/init.d/ondemand manually after logging in seems to work.
--
CPU Frequency Scaling defaults to Performance instead of OnDemand
https://bugs.launchpad.net/bugs/344252
You received this bug notification because you are a
I fixed this issue on my Lucid desktop by running
$sudo nano /etc/rc.local
and adding
cpufreq-selector -g ondemand
before exit 0 line.
--
CPU Frequency Scaling defaults to Performance instead of OnDemand
https://bugs.launchpad.net/bugs/344252
You received this bug notification because you
my athlon64 laptop stays at performance until I change it with the applet after
boot
but on my core2 duo laptop it switches to ondemand a little while after login.
Both machines run lucid with the latest updates.
--
CPU Frequency Scaling defaults to Performance instead of OnDemand
I'm not 100% positive this is the right bug to be reporting on, but I
have a situation similar to W. Kyle White (comment #31). A laptop I'm
using with a fresh install of Lucid will not allow me to select anything
other than Performance as the governor in the GNOME CPU frequency
scaling applet.
Regarding Jiri Trnka's comment #37, a closer look at the man page for
start-stop-daemon at
http://manpages.ubuntu.com/manpages/lucid/man8/start-stop-daemon.8.html
seems to show that there should be no difference in behavior whether or
not the -- portion of the command is present. It's a legal
On my Dell D830 with core duo and Lucid, the trick above (changing --
background to background) does not work
--
CPU Frequency Scaling defaults to Performance instead of OnDemand
https://bugs.launchpad.net/bugs/344252
You received this bug notification because you are a member of Ubuntu
Bugs,
I also confirm this bug in Lucid with all updates. The problem is
inside /etc/init.d/ondemand script. (Bug #576022)
At line 19:
... /etc/init.d/ondemand -- background
should be changed to
... /etc/init.d/ondemand background.
Ondemand script waits for 60s after startup and then swithes CPU
Yes confirm this in lucid too... every time I login I have to change the
cpu frequency from the applet... little annoying not sure how it didn't
make it to the paper cuts list of issues which were fixed
--
CPU Frequency Scaling defaults to Performance instead of OnDemand
Same here Lucid Final latest updates. A year old bug for this??!!
--
CPU Frequency Scaling defaults to Performance instead of OnDemand
https://bugs.launchpad.net/bugs/344252
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Same problem here. Ludic Beta 2, latest updates and kernel
--
CPU Frequency Scaling defaults to Performance instead of OnDemand
https://bugs.launchpad.net/bugs/344252
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Confirmed. Acer 5536 laptop (AMD64) running Ubuntu 10.04 beta 1 I found
the same init.d script that modifies the frequency to ondemand after
60 seconds, but apparently this does not run correctly, so it is with
apache and postgres, several times I had to start them manually. Maybe
the problem is
Just a me too. I would prefer that I be able to select the default
CPU freq mode persistently. So there are two issues here: (1) the wrong
default (should be ondemand), and (2) the mechanism for overriding the
default, already an ugly hack, (/etc/init.d/ondemand) no longer works.
Why not just
For comment #27, #28 - I have an Optiplex GX270 and a laptop which can't be set
to ondemand or conservative. It seems to be a problem with any computers I have
which use p4_clockmod - try:
$lsmod | grep p4_clockmod
The only workaround I've found is to install and start powernowd with the
Is also a problem in 10.04 alpha as of this date. It can be set to
something else with the CPU Frequency Scaling Monitor applet but it
starts the Gnome session in Performance mode and any change does not
seem to stick for a future session.
--
CPU Frequency Scaling defaults to Performance instead
More info, in 9.04 the gnome-applets package could be set with root
privileges so the CPU Frequency Scaling Monitor would be able to change
things when it was loaded, in 10.04 this is no longer possible and the
CPU Frequency Scaling Monitor requires a admin password to change the
setting.
This
Same problem here: Asus EeePC with Celeron M at 900MHz. Eight levels
available (from 112MHz to 900MHz). I can choose a fixed frequency level,
but I am unable to change the policy. I am not able to choose ondemand
(even after doing that, the system remains in performance mode)
Ubuntu 9.10, 32 bit,
Same problem here P4 1.7Ghz, DELL Optiplex GX270. Just stays in
performance no matter what I do and I've done this on dozens of
machines. Seems to be 9.10.
--
CPU Frequency Scaling defaults to Performance instead of OnDemand
https://bugs.launchpad.net/bugs/344252
You received this bug
The kernel default is performance because it is the only sensible
setting while booting; after the boot and desktop login have finished,
it's somewhat hackily set back to ondemand
--
CPU Frequency Scaling defaults to Performance instead of OnDemand
https://bugs.launchpad.net/bugs/344252
You
** Changed in: cpufreqd (Ubuntu)
Assignee: Canonical Foundations Team (canonical-foundations) =
(unassigned)
--
CPU Frequency Scaling defaults to Performance instead of OnDemand
https://bugs.launchpad.net/bugs/344252
You received this bug notification because you are a member of Ubuntu
Same problem with kernel 2.6.31-14-generic (Ubuntu 9.10). HP Pavillion
dv5-1010eu laptop.
--
CPU Frequency Scaling defaults to Performance instead of OnDemand
https://bugs.launchpad.net/bugs/344252
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Confirmed as a problem here with kernel 2.6.28-13-generic with all
updates. After starting set to 'performance.'
--
CPU Frequency Scaling defaults to Performance instead of OnDemand
https://bugs.launchpad.net/bugs/344252
You received this bug notification because you are a member of Ubuntu
I can confirm this bug too on my acer aspire 5610 laptop. After starting
it is set to performance.
Jaunty 32bit with all latest updates.
--
CPU Frequency Scaling defaults to Performance instead of OnDemand
https://bugs.launchpad.net/bugs/344252
You received this bug notification because you are
I have the same problem (Jaunty 32bit). Except that it is not always the
case : sometimes it is set on 'ondemand' after login and sometimes
'performance'. I have not found the conditions yet...
--
CPU Frequency Scaling defaults to Performance instead of OnDemand
I can confirm it using Jaunty 32, evn with latest updates, cpu defaults
to Performance.
--
CPU Frequency Scaling defaults to Performance instead of OnDemand
https://bugs.launchpad.net/bugs/344252
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Same problem here!
In fact, the lack of useful powersave settings in Ubuntu (but Linux-
based laptops/desktops in general) is annoying me even since I started
to use Linux in non-server environments regularly.
When will there be a proper setting in ubuntu (or more generic in the
designated
I can confirm. I have Jaunty 64 with latest updates running on hp
tx2110us.
--
CPU Frequency Scaling defaults to Performance instead of OnDemand
https://bugs.launchpad.net/bugs/344252
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
[quote] Strange problem here.
Often (but not always) the governor is not set to Ondemand after 60 seconds,
but remains set to Performance.
Using Jaunty with latest updates.[/quote]
I have the same problem, sometimes the governor is NOT set to ondemand
after 60 seconds.
--
CPU Frequency
Strange problem here.
Often (but not always) the governor is not set to Ondemand after 60 seconds,
but remains set to Performance.
Using Jaunty with latest updates.
--
CPU Frequency Scaling defaults to Performance instead of OnDemand
https://bugs.launchpad.net/bugs/344252
You received this bug
since this bug in its original form is fixed, should i make a new bug
report for the problem mentioned above?
--
CPU Frequency Scaling defaults to Performance instead of OnDemand
https://bugs.launchpad.net/bugs/344252
You received this bug notification because you are a member of Ubuntu
Bugs,
Steps to reproduce a situation for which this bug is still problematic:
1. add cpufreq-selector -g powersave to /etc/rc.local (instead of powersave
use your preferred governor)
2. reboot
3. watch governor be reset to ondemand about half a minute after login
4. change governor back to your
Not fixed. (for me?)
It takes half a minute after login to change from Performance to
Ondemand. That's the time i have to wait now to switch it to whatever
governor i prefer. Because if i set it to Powersave immediately after
login it gets switched back to Ondemand after that half minute.
--
Can this be selectively disabled? When my laptop is on ondemand, it
very aggressively scales the CPU down, making the system practically
unusable. I would much rather the CPU go to ondemand when using battery
and be on performance when on AC power.
--
CPU Frequency Scaling defaults to
** Changed in: cpufreqd (Ubuntu)
Status: Confirmed = Fix Released
--
CPU Frequency Scaling defaults to Performance instead of OnDemand
https://bugs.launchpad.net/bugs/344252
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Seems fixed with the latest updates (ondemand governor is selected upon
boot)
--
CPU Frequency Scaling defaults to Performance instead of OnDemand
https://bugs.launchpad.net/bugs/344252
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Fixed for me too.
--
CPU Frequency Scaling defaults to Performance instead of OnDemand
https://bugs.launchpad.net/bugs/344252
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Even though the latest kernel is still compiled with performance as default
governor it appears that once the desktop is loaded the governor is set as
ondemand. My guess is that now the governor used is saved on shutdown and
reloaded on startup.
I am not sure where this is saved and by what
There is a script called /etc/init.d/ondemand which sets it to
ondemand 60 seconds after boot. It is part of the initscripts package
and I guess the purpose of this is to speed up booting by using the
performance scheduler during boot.
--
CPU Frequency Scaling defaults to Performance instead of
Applies also to HP Pavilion DV7 1003oe series with 64bit Jaunty install
2.6.28-10-generic #33-Ubuntu SMP Mon Mar 16 23:49:27 UTC 2009 x86_64 GNU/Linux
--
CPU Frequency Scaling defaults to Performance instead of OnDemand
https://bugs.launchpad.net/bugs/344252
You received this bug notification
As multiple persons affected, changing status to confirmed.
** Changed in: cpufreqd (Ubuntu)
Status: New = Confirmed
--
CPU Frequency Scaling defaults to Performance instead of OnDemand
https://bugs.launchpad.net/bugs/344252
You received this bug notification because you are a member of
Just found this:
nanomad ~ $ grep -i default_gov /boot/config-2.6.28-10-generic
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
#
Confirmed.
--
CPU Frequency Scaling defaults to Performance instead of OnDemand
https://bugs.launchpad.net/bugs/344252
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Whenever I boot the system, the governor is set to Performance by
default, and I would have to change it back to Ondemand every time. It
gets very annoying, and I would really like a choice in choosing what
speed governor I use when I'm on AC power and on battery power.
--
CPU Frequency Scaling
Yep, confirmed here too. Even when updating
/sys/devices/cpu0/cpufreq/scaling_governer (for both my CPUs), it still
reverts back to Performance on next boot, so clearly there's a script
over-writing this. I thought there might be something in /etc/default,
but I can't see anything relevant at a
Also confirmed here. I defaults to performance on every boot.
--
CPU Frequency Scaling defaults to Performance instead of OnDemand
https://bugs.launchpad.net/bugs/344252
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Confirmed.
--
CPU Frequency Scaling defaults to Performance instead of OnDemand
https://bugs.launchpad.net/bugs/344252
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
57 matches
Mail list logo
