-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Thinkpad edge 13 - battery threshold issue #1
Comments
Could you please test whether the limits you set (and not see) are used? I have reports that it's just the display that get's borked and the actual thresholds works okay. |
The battery was at 93% when i tested the following I set the start limit to 95: Afterwards i set the stop limit to 97 And... when it got to 97% it stopped charging as expected :) I will try again later with lower start charging limits: thanks for your help, |
Hi again, I do wonder why the reported values are different from the input... it is the same "function" no? regards, |
Well, I did not write the code, just maintaining it, so my knowledge is limited. The setting of the values you do via echo happens in The reading via cat happens in Maybe you find something in there? |
ups, wrong close |
hi, i don't know if this is a help for anyone and i'm sorry for my bad english writing skills, but i would appreciate to be able to use more features of tp_smapi. |
On Tue, Nov 29, 2011 at 12:30:33PM -0800, ajs124 wrote:
Funny, if tp-charge works, tp-smapi 0.41 should work too. Regards Bruce Schneier can read and understand Perl programs. |
"modprobe -v tp_smapi" insmod /lib/modules/3.1.3-1-ARCH/extramodules/tp_charge.ko.gz Name : tp_smapi |
I have this module loading problem too (archlinux / tp_smapi built from the git / Edge E320 Intel) |
having the same problem as described by ajs, is there any progress? |
no, none yet, sorry. |
is there a way to help? I'm like alexisrobert on archlinux too |
Hello, I am also able to load tp_charge:
But when I try to load tp_smapi (using the Ubuntu dkms version) I get: And Any ideas as to why this might happen? |
I can load tp_smapi fine on my intel Edge 13" (latest bios). Using openSUSE 12.1 with 3.3.4 kernel. On Fri, May 4, 2012 at 3:55 PM, jat255 <
|
Thanks for the reply. I tried purging the dkms module through apt-get and building from source like you suggested. The
Relevent
This is on my ThinkPad Edge E420s with Ubuntu 11.10. Any other ideas? |
Hi,
first of all let me apologize in advance if this is not the proper "channel" for a bug report/help request.
I had been reading the sourceforge page for tp_smapi but it looks "dead" in terms of development and i failed every time at installing the smapi driver. Luckily i found your project and got it installed and running now on my thinkpad edge (13", intel model) on opensuse 11.4 with the 3.0 rc1 kernel.
Loading the module goes well, as seen with dmesg:
[13534.023286] tp_smapi unloaded.
[13572.872541] tp_smapi 0.40 loading...
[13572.873353] tp_smapi successfully loaded (smapi_port=0xb2)
But trying to set the battery threshold limits is not working properly. So, what happens is that if i set the start threshold limit to 40, the stop limit gets automatically set to 39. In a similar way if i set the stop threshold to 40, the start limit will be set to 41 automatically. I can use any value and the other will always be set automatically with a +/- 1 difference - it makes no sense:
echo 40 > /sys/devices/platform/smapi/BAT0/start_charge_thresh
cat /sys/devices/platform/smapi/BAT0/*_charge_thresh
40
39
but with dmesg i see:
[13923.606105] smapi smapi: set_real_thresh: set stop to 44 for bat=0
[13923.712956] smapi smapi: set_real_thresh: set start to 39 for bat=0
likewise, if i do:
echo 40 > /sys/devices/platform/smapi/BAT0/stop_charge_thresh
cat /sys/devices/platform/smapi/BAT0/*_charge_thresh
41
40
and with dmesg i see:
[14108.540534] smapi smapi: set_real_thresh: set start to 35 for bat=0
[14108.647415] smapi smapi: set_real_thresh: set stop to 40 for bat=0
any hint as to how i can start to try and solve this?
regards,
Carlos
The text was updated successfully, but these errors were encountered: