Thinkpads Forum

Has somebody successfully installed tp_smapi on an opensuse system ? I absolutely don't know how to do it ! It doesnt' work at all...

Thank you very much...

I have installed it from source. The first time I installed it worked, after subsequent reboots, I cannot get it to work.

I don't know how suse does it, but Mandriva provides a DKMS ready tp-smapi module and a DKMS binary kernel module for the tp-smapi driver for each possible kernel of a distribution. These are installed using urpmi or Software Installer. Very easy to do this way. Perhaps Opensuse offers something similar?

in debian i just install the precompiled kernel module through synaptic and then i'm ready to rock-n-roll. the module in the repo is rebuilt for each kernel update, so when you update kernels, it automatically downloads the matched precompiled module to go with it.

remember that if you build from source, you'll have to rebuild and depmod after updating kernels. if it doesn't auto load on subsequent boots, first make sure that you're not getting errors in dmesg when you insert with modprobe, then add it and its dependencies to the modules list so that modprobe will load it next time.

I have this working now. I clean installed the tp_smapi from source again.

I have to do a modprobe -a tp_smapi everytime i reboot, then if i set the value for top charge threshold , it stops at the values. Is there a way to make to load automatically and remember the values.

I am doing this on open suse 11.0,

Linux 2.6.25.11-0.1-default #1 SMP 2008-07-13 20:48:28 +0200 i686 i686 i386 GNU/Linux

Thank you.

i have my values set in rc.local that way it's set on every boot before gdm starts up. just make sure you chmod +x rc.local (it's not by default) so that it executes as it's called via a script that checks first if it's executable.

In Mandriva there is a file /etc/modprobe.preload where you can enter the base name of the module you are using modprobe to install. This will cause the module to be loaded at each boot. Putting in rc.local works as well, but it is a little more work. Not sure how the -a switch figures into all this.

i should have been more clear. i'm using rc.local only to set the charging thresholds, not to load the module. i suppose that this could be done with a script executed on gdm login, but i feel it should be a system-wide thing, not per-user, so i load it in rc.local before anyone logs in.

for modprobe, i have the hdaps and thinkpad_ec modules explicitly listed along with tp_smapi to make sure that the dependencies are loaded.

In suse there is no rc.local , there is a boot.local and boot.modules not sure how to use these. Any help is appreciated.