On Wednesday 24 June 2009 03:28:55 Mike Mazur wrote: > Hi, > > On Tue, Jun 23, 2009 at 04:44, Alan McKinnon<alan.mckin...@gmail.com> wrote: > > On Monday 22 June 2009 15:56:47 Mike Mazur wrote: > >> <SNIP> > >> I noticed some issues with the power management setup I had when I > >> upgraded kernels over the last few months. This past weekend I decided > >> to crack down on this to see whether they could be fixed. I visited > >> the Gentoo Power Management Guide[1] again and re-traced the setup to > >> verify my system's behavior. > > > > Dump cpufreqd. Use just the ondemand governor instead and get rid of the > > rest. > > > > <SNIP> > > > > That sounds like the conservative governor, the worst one of the lot. It > > forces the cpu to rapidly change state, and do it often. Changing C state > > is expensive, do it as seldom as you can. Just use ondemand all the time. > > You mean set the default governor to "ondemand" in the kernel and > leave it at that regardless of whether running on batter or AC power?
Yes. > >> The third issue seems to be with power management of my wireless card. > >> I have the iwl3945 wireless card. In older version of the kernel > >> (2.6.25 and before, I believe) this card was managed by a daemon in > >> userspace. After that the driver was merged into the kernel. I noticed > >> recently that the entry in /etc/conf.d/net (as per the Power > >> Management Guide) causes this error when the interface comes up: > > > > iwl3945 does not (yet) support this to the best of my knowledge. It also > > doesn't work here either. > > Alright, this makes sense I guess. > > Still one issue remains -- why are my RC states not automatically > switched between default and battery even though my acpid setup is > right and works (according to the log messages)? The simplest answer (usually the right one) is that you are probably grepping for the wrong string. These things are subject to change and there's no easy way for you to find out when it happens. -- alan dot mckinnon at gmail dot com
