|
|
| (12 intermediate revisions by 7 users not shown) |
| Line 3: |
Line 3: |
| | |style="vertical-align:top" | | | |style="vertical-align:top" | |
| | <div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"> | | <div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"> |
| − | === UltraBay 2000 Battery === | + | === Ultrabay 2000 Battery === |
| − | This is a battery that slides into a supported UltraBay 2000. | + | This is a battery pack that slides into an Ultrabay 2000. Please note that not all Ultrabay 2000 or Plus bays are capable of using this battery pack, as some do not have the required power interfacing pins to use this. |
| | | | |
| | === Features === | | === Features === |
| − | * 10.8V Lithium-Ion | + | * 3.2Ah or 3.6Ah, 10.8V |
| − | * 9 cells | + | * 9 lithium-ion cells |
| | * Up to 3 hours of battery life | | * Up to 3 hours of battery life |
| − | * Weight: 268g (0.59 lbs) | + | * Charge time: 2 hours |
| − | * Charge time: 2.0 h
| + | * Weight: 268 grams or 0.59 pounds |
| | </div> | | </div> |
| | |style="vertical-align:top" | | | |style="vertical-align:top" | |
| − | [[image:ultrabay2000battery.gif|UltraBay 2000 Battery]] | + | [[image:ultrabay2000battery.gif|Ultrabay 2000 battery]] |
| | |} | | |} |
| | | | |
| − | === IBM Partnumbers === | + | === Part numbers === |
| | + | |
| | + | ==== 3.2Ah, 10.8V, Sanyo ==== |
| | + | |
| | *Marketing PN: 02K6646 | | *Marketing PN: 02K6646 |
| | *FRU PN: 02K6645 | | *FRU PN: 02K6645 |
| | | | |
| − | === Linux Support === | + | ==== 3.6Ah, 10.8V, Sanyo ==== |
| − | The second battery is correctly detected by either the APM or ACPI subsystem. 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.
| + | *Marketing PN: 02K6819 |
| | + | *FRU PN: 02K6817, 02K6818 |
| | | | |
| − | Fortunately, the battery status is accessible independently of the ACPI system. The [[SMAPI support for Linux|tp_smapi]] module gives battery status (and other features) via the sysfs interface in {{path|/sys/devices/platform/smapi/BAT{0,1}}}. 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.
| + | === Usage and Linux support === |
| − | | + | See [[How to use UltraBay batteries]]. |
| − | Unfortunately, all battery monitor scripts/applets currently use the ACPI interface to get battery status information.
| |
| − | | |
| − | Test machine: T23.
| |
| − | | |
| − | === Battery Control === | |
| − | | |
| − | The system only charges/discharges one battery at a time.
| |
| − | If you have both batteries present, the system will completely deplete the UltraBay battery before using the main battery.
| |
| − | When charging, the system will completely charge the main battery before it starts on the UltraBay battery.
| |
| − | | |
| − | {{WARN|You need to keep an eye on the charge in the UltraBay battery and physically remove it from the bay when it gets too low. Failure to do so will result in the system completely discharging the UltraBay battery. This will significantly reduce the lifetime of your battery. }}
| |
| − | | |
| − | Switching between the batteries is 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 main battery (i.e., replace it without the need to reboot, hibernate or use an external power adapter).
| |
| − | | |
| − | Someone suggested that the [[SMAPI support for Linux|tp_smapi]] module could be used to control which battery gets used first. As of tp_smapi-0.13, the only way this could be possible is using <tt>force_discharge</tt>. But none of the functions to manipulate the battery are implemented on the T23 (may work on T30 though).
| |
| | | | |
| | === Supported with === | | === Supported with === |
| − | *ThinkPad {{A20m}}, {{A20p}}, {{A21e}}, {{A21m}}, {{A21p}}, {{A22e}}, {{A22m}}, {{A22p}}, {{A30}}, {{A30p}}, {{A31}}, {{A31p}} | + | * {{A Series}} |
| − | *ThinkPad {{R30}}, {{R31}}, {{R32}}, {{R40}} | + | * {{T20}}, {{T21}}, {{T22}}, {{T23}}, {{T30}} |
| − | *ThinkPad {{T20}}, {{T21}}, {{T22}}, {{T23}}, {{T30}}
| + | * [[UltraBase X3]] with the {{X30}}, {{X31}}, {{X32}} docked |
| − | | + | * {{R32}}, {{R40}} |
| | | | |
| | [[Category:Components]] | | [[Category:Components]] |
