|
||||||
| Forums FAQ | Members List | Search | Today's Posts | Mark Forums Read |
| Laptop Questions about laptop hardware and laptop specific software (power management ) |
![]() |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
According to its name, "tp_smapi-kmp-pae.ymp" seems to be for the "pae" kernel, that only exists in the 32 bit distribution. You say that you are using "default", so you would not need that package.
Not sure about the "vmi" package, probably the same thing. "xen" and "trace" also refer to other kernels, but in this case they are available in 64 bit, so you probably have just installed them (you will see the option to start them in grub at boot time). |
|
||||
|
hi escaner,
so it may be that i don't need to install tp_smapi-kmp-pae.ymp & tp_smapi-kmp-vmi.ymp since i'm using 64 bit? the reason i thought they must need to be installed is because none of the tp_smapi-* files installed so far have created the smapi directory in /sys/devices/platform/ (referred to in the tp_smapi ThinkWiki) |
|
|||
|
If you download the .rpm packages, you can look at their contents with the following command:
Code:
rpm -qp package.rpm -l Code:
oscar@seafire:~> rpm -qp tp_smapi-kmp-pae-0.40_2.6.27.23_0.1-3.3.i586.rpm -l /lib/modules/2.6.27.23-0.1-pae /lib/modules/2.6.27.23-0.1-pae/updates /lib/modules/2.6.27.23-0.1-pae/updates/hdaps.ko /lib/modules/2.6.27.23-0.1-pae/updates/thinkpad_ec.ko /lib/modules/2.6.27.23-0.1-pae/updates/tp_smapi.ko oscar@seafire:~> rpm -qp tp_smapi-kmp-vmi-0.40_2.6.27.23_0.1-3.3.i586.rpm -l /lib/modules/2.6.27.23-0.1-vmi /lib/modules/2.6.27.23-0.1-vmi/updates /lib/modules/2.6.27.23-0.1-vmi/updates/hdaps.ko /lib/modules/2.6.27.23-0.1-vmi/updates/thinkpad_ec.ko /lib/modules/2.6.27.23-0.1-vmi/updates/tp_smapi.ko I think that the "/sys" filesystem is like "/proc", a virtual fs to access system data. Therefore your /sys/devices/platform/smapi should appear when the kernel loads the module. If it is correcly intalled, it will probably do it in the next boot. To load it manually, execute: "modprobe <module-name>" (without the ".ko"). There are three of them: hdaps, thinkpad_ec and tp_smapi... To see whether they have been loaded, execute: Code:
lsmod|egrep 'hdaps|thinkpad_ec|tp_smapi' Óscar |
|
||||
|
Hi Oscar,
Many thanks for your time and explanations. I didn't know there were so many different varieties of the kernel so I guess I have no doubt installed packages that were not necessary. And I didn't know about being able to display the contents of rpm files. The Wiki did mention the modprobe command but I thought something was wrong due to the missing smapi directory. Maybe it is created after the modprobe command is executed. I'll give it a go and post the results. Many thanks again, Mark |
|
||||
|
Hi again Oscar,
Everything you said was 100% spot on! Thank you. I had not noticed the Grub options for booting into the other (mistakenly installed) kernel versions because I have a multiboot system. But when I checked /boot/grub/menu.lst in OpenSuse, sure enough, the debug, xen and trace kernels were listed too. So I used Yast Software Manager to remove the unwanted tp_smapi kernel versions and then removed the unwanted kernel versions. command # lsmod|egrep 'hdaps|thinkpad_ec|tp_smapi' resulted in showing that none of the modules were loaded. command # modprobe tp_smapi resulted in error "thinkpad_ec: cannot claim io ports 0x1600-0x161f" (as detailed in the tp_smapi wiki due to T400 & T500 machines needing FORCE_IO=1). after a bit more reading of the wiki and other pages (and some lucky guesswork) I added line "options thinkpad_ec force_io=1" (without the quotes) to file modprobe.conf.local in directory /etc command # modprobe tp_smapi now resulted in no errors and command # lsmod|egrep 'hdaps|thinkpad_ec|tp_smapi' displayed the following: tp_smapi 26832 0 thinkpad_ec 7664 1 tp_smapi and sure enough ....the smapi directory appeared in sys/devices/platform so thanks to you I've managed to make substantial progress. my next step is to figure out how to have the tp_smapi loaded automatically at bootup, and then edit the start/stop battery charge %ages. Many thanks for your help. I would not have gotten this far without your help. Mark |
|
||||
|
Hi Oscar, I got it sorted
![]() to autoload the tp_smapi module on boot I changed the following line in file /etc/sysconfig from MODULES_LOADED_ON_BOOT="" to MODULES_LOADED_ON_BOOT="tp_smapi" and to set the start and stop battery charge %age thresholds to 40% and 90% respectively, i used the following commands (which are remembered after reboot): echo 40 > /sys/devices/platform/smapi/BAT0/start_charge_thresh echo 95 > /sys/devices/platform/smapi/BAT0/stop_charge_thresh I'm going to use Acronis to restore OpenSuse back to it's config before my meddling and perform a step-by-step install of tp_smapi from scratch so that i may post step-by-step instructions for other ThinkPad users. Best regards, Mark |
|
||||
|
For anyone who stumbles upon this thread, I've posted a new thread detailing a step-by-step guide on how I got tp_smapi installed on a Thinkpad W500 running openSuse 11.1.
tp_smapi on Lenovo Thinkpad T400/T500/W500 (step-by-step) - openSUSE Forums |
![]() |
| Bookmarks |
| Thread Tools | |
| Display Modes | |
|
|