|
|
| (3 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | {| width="100%"
| + | #REDIRECT [[How to use Ultrabay batteries]] |
| − | |style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
| |
| − | |style="vertical-align:top" |
| |
| − | ThinkPad laptops only charge/discharge one battery at a time. If you have two batteries present (a system battery and an [[UltraBay]] battery), the laptop will completely deplete the UltraBay battery before using the main battery.
| |
| − | |}
| |
| − | | |
| − | ===Battery hot-swapping===
| |
| − | Switching between the batteries is almost instant, so if you pull the UltraBay battery from the bay when it is being discharged, the system will instantly switch to the main battery. You can therefore use the UltraBay battery to hot-swap the system battery (i.e., replace it without the need to reboot, hibernate or use an external power adapter).
| |
| − | | |
| − | You should issue {{cmdroot|echo eject > /proc/acpi/ibm/bay}} before removing the battery from the bay, especially if you are replacing it with a different device (requires [[ibm-acpi]]). See [[How to hotswap UltraBay devices]].
| |
| − | | |
| − | ===Charging and discharging===
| |
| − | When charging, the system will completely charge the main battery before it starts on the UltraBay battery. However, if you change a full main battery for an empty one, the system will finish charging the ultrabay battery before charging the second main battery.
| |
| − | | |
| − | When discharging, the system will completely discharge the UltraBay battery before it discharges the main battery. This greatly reduces the lifetime of the Ultrabay battery, and also reduces its usefulness for enabling hot-swapping of the system battery. There are two ways to prevent this:
| |
| − | | |
| − | * Keep an eye on the charge in the UltraBay battery and physically remove it from the bay when it gets too low (or release the eject lever- see below).
| |
| − | * Use the [[SMAPI support for Linux#Using_the_tp_smapi_module|tp_smapi]] module to control which battery is discharged (via <tt>force_discharge</tt>) or charged (via <tt>inhibit_charge_minutes</tt> on the other battery). This only works on some ThinkPad models - see the [[tp_smapi#Model-specific_status|tp_smapi model-specific status]].
| |
| − | | |
| − | | |
| − | | |
| − | ===UltraBay eject lever===
| |
| − | It seems that you don't have to completely remove the UltraBay battery from the bay to stop using it. If you release the eject lever, but don't actually pull the battery from the bay, the battery is still visible to the system, but the BIOS reverses the order of use and will completely deplete the main battery before using the UltraBay battery. While the BIOS can switch to the UltraBay battery when the main battery runs out, it cannot switch fast enough when the main battery is pulled. Make sure you push the eject lever in before swapping the main battery or the system will loose power. Likewise, if you have the ultrabay lever pushed in: while the system can switch to the main battery when the ultrabay battery is empty, it cannot switch to the main battery fast enough if the ultrabay battery slips out of the bay without the lever being released- the system will loose power.
| |
| − | | |
| − | The order of charging is not affected by the state of the eject lever. Test machine: T23. May or may not work on other models.
| |
| − | | |
| − | ===Reading the battery status under Linux===
| |
| − | | |
| − | ====Using APM====
| |
| − | | |
| − | The second battery is correctly detected by the APM subsystem (if activated).
| |
| − | | |
| − | ====Using ACPI====
| |
| − | | |
| − | The second battery is correctly detected by the ACPI subsystem (if activated). However, the Linux ACPI subsystem only scans for batteries on boot. This means that the second battery must be present at boot time, or you will not be able to get any info for it via {{path|/proc/acpi/battery/BAT1}}.
| |
| − | | |
| − | With kernel 2.6.14.2 (possibly only with [[ibm-acpi]]) there is a sysfs file: {{path|/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/EC/BAT1/eject}}. There isn't one for BAT0, but {{cmdroot|cat /proc/acpi/battery/BAT0/*}} shows {{cmdresult|not present}} when there is no internal battery.
| |
| − | | |
| − | For BAT1 all the states go to 0, critical, etc. .
| |
| − | | |
| − | {{cmdroot|echo 1 > /sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/EC/BAT1/eject}} will remove {{path|/proc/acpi/battery/BAT1}} and turn off the UltraBay led. Interestingly the battery will still be discharging (charging not tested) until it is physically removed.
| |
| − | | |
| − | Also, if you compile the battery module of ACPI as a module, boot with the UltraBay battery present, remove the UltraBay battery (without doing the eject above), {{path|/proc/acpi/battery/BAT1}} is still there, while after {{cmdroot|rmmod battery && modprobe battery}} {{path|/proc/acpi/battery/BAT1}} is gone (BAT0 is back). Put the battery back in and {{path|/proc/acpi/battery/BAT1}} is still missing, do {{cmdroot|rmmod battery && modprobe battery}} and {{path|/proc/acpi/battery/BAT1}} is back.
| |
| − | | |
| − | If you boot without the second battery <tt>BAT1</tt> never appears in {{path|/proc}} or {{path|/sys}}.
| |
| − | | |
| − | If you eject using the sysfs file above, <tt>BAT1</tt> disappears from both {{path|/proc}} and {{path|/sys}} and never comes back.
| |
| − | | |
| − | Please note, that applications, like Gnome Power Manager (don't know about others) automatically sums both battery capacities and display the status together
| |
| − | | |
| − | ====Using <tt>tp_smapi</tt>====
| |
| − | | |
| − | Independently of APM or ACPI, the battery status is also accessible through the [[tp_smapi]] driver. The <tt>tp_smapi</tt> kernel module provides battery status (and other features) via the sysfs interface in {{path|/sys/devices/platform/smapi/BAT<nowiki>{</nowiki>0,1<nowiki>}</nowiki>}}, and includes some information not accessible through APM or ACPI (e.g., cycle count and momentary power draw). The BAT1 interface is always present, regardless of whether the battery is present, was present on boot, or was ejected using the sysfs interface above.
| |
| − | | |
| − | For a GUI interface, you can use the [[KThinkBat]] applet or [[Gkrellm-ThinkBat]] plug-in.
| |
