On Tue, 10 May 2011, Pavel Machek wrote: > Hmm, I jave a battery pack with reasonably good cells, but firmware killed > it. IOW available for testing. That is likely a problem with the battery pack uC, we cannot override that using any know firmware path in the ThinkPad. Does the thinkpad recognizes the presence of the battery pack? If it doesn't, the pack uC is probably dead or in safe mode, and you'd need to hardware-hack it. > (And who know, perhaps recalibrate command would bring it back to life?) AFAIK, the recalibrate command really just does this: 1. sets 'force discharge' flag on EC so that it starts discharging the battery pack. Discharging stops when cell voltage drops close to the minimum safety level. 2. sets stop threshold to 0 (100%) for that battery pack. That way, the box will fully-drain the pack, and then charge it to full. At that point, the recalibration is complete (the battery pack uC will auto-calibrate itself when it notices it has hit the fully-drained and fully-charged points). You can monitor per-cell-group voltages through tp_smapi on a original IBM battery pack, that functionality should still be around on the Lenovos. Since this is not standard SBS functionality, it might not work on non-original battery packs. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ ibm-acpi-devel mailing list ibm-acpi-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
