Powertop is a great tool. Is does however have some disadvantages:
- ncurses GUI
- You have to run it as root
- It gives you hardcore suggestions that you have to do manually, which in turn disable bits of the desktop
- You can only run one instance of powertop at a time, else you get crazy readings
- There’s no shared library giving access to the data
- It’s not extensible, so you can’t do much with the data
Now, it turns out the actual data processing code of powertop is pretty easy, sampling /proc/interrupts and /proc/timer_stats every few seconds and throwing away interrupts that are defered and that sort of thing.
In a couple of hundred lines of C, I’ve added this support to DeviceKit-power on a new DBus interface, and added a trivial GObject helper for applications to use.
Long term I want to get this functionality in gnome-system-monitor (it’s querying a simple DBus interface), as I think this data better fits there. gnome-power-statistics is just a handy module that already depends on DeviceKit-power.
As usual, comments and suggestions welcome.
Another change coming in 2-27 – gnome-power-manager will stop listening to HAL for button events. Peter has been rocking with evdev over the last few months and now all the multimedia buttons come up through both X and HAL. g-p-m has to filter the second button, and mostly this works well. Some distros are still not configuring evdev properly, and some still inject events into HAL, or rely on HAL to scrape events from oddball kernel interfaces. The way forward is using INPUT in the kernel, and the vast majority of events are now coming through INPUT from random devices, and through X to applications.
Once upon a time there were three inhibit API’s:
Obviously, this has a few big flaws:
- An application might have to inhibit three services, using slightly different methods
- gnome-screensaver has to expose lots of low level icky stuff for g-p-m to consume
- We’ve got a screensaver doing idle detection
- We’ve got gnome-power-manager writing into gnome-screensaver GConf keys to get the timeouts correct
- It’s not possible to prevent logout or user switching
- The hand-off between the session and power manager is poorly defined, so we get stupid libnotify popups rather than nice dialogue integration.
- We don’t integrate with presence services, so we just ignore away/busy/idle status.
Basically, we need the session manager to take care of the all registrations and handle the interactions. Luckily, this is what Jon McCann has done in gnome-session.
These new interfaces are session management done right. Of course, this breaks the old world order of inhibiting gnome-power-manager and gnome-screensaver. For the 2-26 series all inhibits are proxied by g-p-m and g-s to gnome-session, so everything should pretty much just work like before. But, early in the 2-27 cycle we’re going to remove this compat code and everything will have to go through gnome-session. For most code it’ll just be a couple of lines changed and behind the scenes it’s a much simpler and more powerful design.
Like some of the other changes we are making at the moment (DeviceKit, PulseAudio, KMS) this is a new way of doing things, and things might temporarily break. They’ll be regressions, but things can be fixed quickly and most importantly, correctly. What we were using before just wasn’t good enough. With this new framework, we can do it right for GNOME 3.0.
Gaussian smoothing just isn’t working for the profile graph. Anybody got any suggestions?
Every now and then, somebody chastises me for abusing libnotify to display something to to user. I guess it’s easier to just spam a fire-and-forget notification that thinking about how to present the data properly to the user.
A classic example is the messages the PackageKit daemon passes to the client program. These messages are packets of data containing the message type and any specific details. An example of this might be a message telling you that a config file has been automatically merged, or that a non-critical error has been worked around. These also tell you when things like prelink fail, which is a pain when you’re running something like rawhide. These messages arrive as the transaction is running, and are designed to be shown to the user at the end of the transaction and not get in the way.
Now, due to some “just get it working as quickly as possible” design standards, I used libnotify to display these to the user. Bad me. My excuse is that I’ve been very busy with other stuff, and life seemed to get in the way over Christmas.
Now I guess the right way to show the user this sort of data is for an icon to appear, something like this:
When the icon is clicked, something like this would appear:
So comments and feedback appreciated. No code in git yet, until it looks nicer. Thanks.
Every time I start my laptop, I get a firmware request from the kernel for /lib/firmware/intel-ucode/06-0f-0b for a microcode update. This fails, and no package provides it, but I would like to know why the kernel is requesting this. As far as I knew, all microcode is located in microcode.dat, and pushed from userspace to kernel using microcode_ctl, rather than the kernel requesting it itself. If I can’t find any explanation, I’ll just block all microcode requests in the client to avoid PackageKit users having searches automatically done for files that aren’t going to exist.
Help appreciated. Thanks.
Has anyone got any inspired ideas how to make the text in a GtkCellRendererText selectable so the user can copy it? I’m trying to fix fd#19252 and it’s not obvious how you do this with GTK. Thanks.