View Single Post
Posts: 1,463 | Thanked: 1,916 times | Joined on Feb 2008 @ Edmonton, AB
#55
Originally Posted by Mentalist Traceur View Post
The module is NEVER (by default) loaded at boottime. This just bugs me because it's been known, and gone over in the Beautify Conky thread were Creamy Goodness was a participant. Power kernel does not automatically boot with that module enabled. You can make it boot by default by echoing it to the proper file:

(as root)
echo bq27x00_battery >> /etc/modules

Make sure to use >>, not >, because > will override the rest of the stuff in there. Not good.

Creamy Goodness: I like the idea of Conky using that module by default, but then it needs to either add it to the default modules loaded at boot, or check for it when launching, and modprobe it if necessary. I would recommend the latter, because there might be other bugs that could be caused by forcing the bq27x00_battery module on people who may be running a system that doesn't have it installed already or who have it disabled for other reasons.

(Or if you really want to go through coding hell the variables that can be queried with BME can be queried that way if the bq27x00_battery module isn't loaded when conky launches - but I realize that's a pain in the ***.)
Yeah I have a bad memory, plus I probably loaded that module as soon as it was available, and totally forgot about it by now. The hal-BME stuff is read with dbus if that module isn't loaded, but the temperature really requires that kernel module loaded. I will just modprobe it I guess, I think that's relatively safe. It won't explode if it doesn't exist, or is already loaded.