2 Jan
2013
2 Jan
'13
6:13 p.m.
Hey all,
Can anyone pitch in ideas for dealing with bug 1290?
Hal is badly outdated and kpowersave is acting up, so debugging it
could be very tricky,
We also have kpowersave-nohal ready for R14...
what should we do?
Calvin
2 Jan
2 Jan
6:14 p.m.
New subject: [trinity-devel] Bug 1290 - Kpowersave 100% cpu
Hey all,
Can anyone pitch in ideas for dealing with bug 1290?
Hal is badly outdated and kpowersave is acting up, so debugging it
could be very tricky,
We also have kpowersave-nohal ready for R14...
what should we do?
Calvin
I want to switch to kpowersave-nohal for R14.0.0. The biggest problem
with doing so is that I don't know of any way to use udev to set
permissions on the various control files in the /proc filesystem; this
would be needed for a normal user to be able to control CPU frequency
scaling, display brightness, etc.
Tim
17 Jan
17 Jan
5:33 a.m.
New subject: [trinity-devel] Bug 1290 - Kpowersave 100% cpu
2013/1/3 Timothy Pearson <kb9vqf(a)pearsoncomputing.net>et>:
I want to switch to kpowersave-nohal for R14.0.0. The
biggest problem
with doing so is that I don't know of any way to use udev to set
permissions on the various control files in the /proc filesystem; this
would be needed for a normal user to be able to control CPU frequency
scaling, display brightness, etc.
Tim
For brightness control you can use X API and a standalone setuided
helper as a fall-back implementation. It's so in kde4 for now AFAIK.
I don't know what about frequency scaling... off coarse it can be
solved with a setuided handler as well but it's seems quite ugly for
me...
4138
days inactive
4152
days old
2 comments
3 participants
participants (3)
-
Calvin Morrison -
Fat-Zer -
Timothy Pearson