Bug#484467: (no subject)
On 2008. June 5. 00:56:32 you wrote:
> On Wed, 04 Jun 2008, LÉVAI Dániel wrote:
> > The problem is with cpufreqd.
> > After:
> > # update-rc.d -f cpufreqd remove
> > the system is up and runnning, but when executing:
> > # invoke-rc.d cpufreqd start
> > INIT: Switching to runlevel 0
> better use cpufrequtils
I like cpufreqd because it can run arbitrary command when rules apply,
and that command could be
"echo 5 > /sys/class/backlight/acpi_video1/brightness". Is there a way
to do this with cpufrequtils?
> > How about that :\
> > With a self-compiled 220.127.116.11, everything is fine. The freq.
> > governors are compiled in for me, in contrast with the debian
> > kernel, which has them in modules. I don't know if this is related,
> > cpufreqd suppose to load every module it needs.
> > Guess we could close this, or is this still relevant?
> hmm kernel should not reboot that easily.
> but on a quick guess aboves beast is running as root and thus..
> bug needs to be reassigned.
It reboots because there is a rule in /etc/cpufreqd.conf which halts the
system when it detects a 0-1% battery charge. cpufreqd uses the
legacy /proc way to gather battery status information, thus with the
new kernel it doesn't work, and instantly halts because it thinks that
no juice left.
PGP key ID = 0x4AC0A4B1
Key fingerprint = D037 03B9 C12D D338 4412 2D83 1373 917A 4AC0 A4B1