Here's what I get on a freshly installed Lucid:
jul...@julien:~$ ls /etc/rc2.d/
READMES20winbind S50rsync S91apache2
S20fancontrol S25bluetooth S50saned S99acpi-support
S20kerneloops S31atieventsd S70dns-clean S99grub-common
the problem with the performance governor staying after boot occurs to
me too.
Running /etc/init.d/ondemand start manually solves the problem, but
during start, the script is somehow not started!?
--
system stays on full CPU clock
https://bugs.launchpad.net/bugs/341573
You received this bug
Why this bug was fixed so strange hard way? We always can make planet
green using /etc/sysfs.conf or something like. I have spent some time to
find init.d/ondemand that resets my governor
--
system stays on full CPU clock
https://bugs.launchpad.net/bugs/341573
You received this bug notification
Excellent! Problem solved here. Thanks.
--
system stays on full CPU clock
https://bugs.launchpad.net/bugs/341573
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
To Roger: Have you updated the initscripts package?
--
system stays on full CPU clock
https://bugs.launchpad.net/bugs/341573
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
Yes, I have. The only thing I can think of that's a little bit out of
the ordinary on this machine is that I've been experimenting with VDPAU,
so I have NVIDIA 185.13 installed. The machine is a Compaq 8710p laptop.
--
system stays on full CPU clock
https://bugs.launchpad.net/bugs/341573
You
And ls /etc/rc2.d
--
system stays on full CPU clock
https://bugs.launchpad.net/bugs/341573
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
~$ ls /etc/rc2.d
K08vmware S20winbindS89anacron
README S24halS89atd
S01policykit S25bluetooth S89cron
S10acpid S30gdmS90binfmt-support
S10sysklogdS50avahi-daemon
Hey, it must have been at least almost 25 years since I did any
programming at all, but I just had a look at the 599ondemand file. It
seems it doesn't end with exit 0 after the case-esac clause, at least
not on my computer. Could that be it? Or am I grasping at straws?
--
system stays on full
Also doesn#t work here. Manually running /etc/init.d/ondemand start
also doesn't work, but fails silently. Putting the echo-Command manually
works. I'm no bash guru, so no idea, where the problem sits.
--
system stays on full CPU clock
https://bugs.launchpad.net/bugs/341573
You received this bug
Here it is:
~$ cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_{driver,governor}
acpi-cpufreq
acpi-cpufreq
performance
performance
Come to think of it, I also have ext4 and an encrypted home directory,
though I can't how that would interfere.
Roger
--
system stays on full CPU clock
Roger, please supply the output of:
cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_{driver,governor}
--
system stays on full CPU clock
https://bugs.launchpad.net/bugs/341573
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
As I said in the duplicate bug #344875, it's the sleep 60 in
/etc/init.d/ondemand that seems to be causing the problem.
--
system stays on full CPU clock
https://bugs.launchpad.net/bugs/341573
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I suspect this is the same bug we once saw with upstart-logd (and
indeed, why we don't use it anymore), that the output terminal going
away results in the process dying
--
system stays on full CPU clock
https://bugs.launchpad.net/bugs/341573
You received this bug notification because you are a
Just done an upload that should fix it
--
system stays on full CPU clock
https://bugs.launchpad.net/bugs/341573
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
Will be fixed with an init script
** Changed in: sysvinit (Ubuntu)
Sourcepackagename: linux = sysvinit
--
system stays on full CPU clock
https://bugs.launchpad.net/bugs/341573
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This bug was fixed in the package sysvinit - 2.86.ds1-61ubuntu9
---
sysvinit (2.86.ds1-61ubuntu9) jaunty; urgency=low
* debian/initscripts/etc/init.d/ondemand: Sleep for 60 seconds, then
set CPU Frequency Scaling governor to ondemand. LP: #341573.
-- Scott James Remnant
Seems not to be working here for some reason. I've got the latest
sysvinit and kernel 2.6.28-11-generic installed now, and I still have to
swith to Ondemand manually.
--
system stays on full CPU clock
https://bugs.launchpad.net/bugs/341573
You received this bug notification because you are a
as nobody reacts, some more details: Asus M2N (intel Pentium M, 855
Chipset); no known ACPI issues since ages. Nothing (except that
nforce2-message) from cpufreq in any of the logs...
--
system stays on full CPU clock
https://bugs.launchpad.net/bugs/341573
You received this bug notification
We are missing the piece that sets the driver back to ondemand after
boot, that's in my court
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Scott James Remnant (scott)
--
system stays on full CPU clock
https://bugs.launchpad.net/bugs/341573
You received this bug notification
20 matches
Mail list logo
