ThinkWiki - User contributions [en]

Talk:AD1981HD

2006-09-02T01:54:49Z

Deason:

== Cracking noises ==

hi, made my sound work with alsaconf, but i do have the described cracking noises.

the article reads:

''Possible cracking noises can be avoided by adding the position_fix=2 optional argument for the module.''

how can i do this? i've found the following line in my /etc/modules.conf:

''Possible cracking noises can be avoided by adding the position_fix=2 optional argument for the module.''

what do i have do add or change?

thanks for help!

== NetBSD note ==

I just wanted to mention that disabling the modem in BIOS solved a huge problem I was experiencing with the azalia sound chip in my T60p. With the modem enabled, I was only able to hear sound at less than half-volume through the headphone jack, and barely at the edge of hearing through the speakers. Disabling the modem now allows me to adjust the volume with mixerctl properly.

Talk:AD1981HD

2006-09-02T00:32:00Z

Deason: FreeBSD

Problems with ACPI suspend-to-ram

2006-08-13T02:59:32Z

Deason: /* Troubles on resume */ Adding text console garbage problem.

The following glitches may or may not occur in relation to suspending to RAM:

==Troubles on suspend==
;Permissions:If your suspend is failing, and a {{cmdroot|tail /var/log/acpid}} shows "Permission denied" errors, be sure that your new ACPI event and action scripts have the appropriate permissions.

;Broken sysfs interface:You may experience problems when using {{cmdroot|echo standby > /sys/power/state}} or {{cmdroot|echo mem > /sys/power/state}} (machine goes to sleep and wakes up immediately). This can be avoided by using {{cmdroot|echo -n 3 >/proc/acpi/sleep}} to get it to sleep. This can be also happen if hotplug daemon is still running.

;Hangs on "switching to UP code":You may be using a [[How to make use of Dynamic Frequency Scaling|frequency scaling governor]] such as "conservative" or "ondemand", which sometimes have problems with suspending. Switching to a governor such as "powersave" or "performance" before suspending may solve this problem.

;MySQL daemon running:If you're running MySQL, sleep may also not work, so stop MySQL first, then sleep. Remember to restart MySQL when you wakeup.

;LCD backlight remains on during sleep:When your system is equiped with a Radeon Mobility graphic controller your [[Problem with LCD backlight remaining on during ACPI sleep|LCD backlight may not turn off automatically]]. Use [[radeontool]] to switch off your backlight prior suspend in your sleep action script.

;High power drain during sleep:Also, you might want to take note of the [[Problem with high power drain in ACPI sleep]].

==Troubles on resume==
;Blank display on resume:When resuming from a suspend-to-ram the display might remain black or might only show the pre-suspend output (the system is still rebootable via {{key|ctrl}}{{key|alt}}{{key|del}}). See [[Problem with display remaining black after resume]] for solutions.
;Garbage on text consoles on resume:When resuming from suspend-to-ram the text console displays may show garbage instead of actual text. The machine is otherwise still responsive, and switching to X after resume fixes them. If all of this is true, then adding the kernel option '''acpi_sleep=s3_bios,s3_mode''' in your menu.lst or lilo.conf may stop this from happening.
;Broken hardware support after resume:
:*The '''serial port''' of the port replicator might not work after resume.
:*The '''parallel port''' might not work after resume. A possible fix is to unload and reload the parallel port drivers: {{cmdroot|rmmod lp parport_pc parport; modprobe lp}}.
:*Problems with the '''CD-RW/DVD drive''' after wake up from ram have been experienced.
:*There is a known Problem regarding '''battery info''' after suspend to RAM. A [http://www.ussg.iu.edu/hypermail/linux/kernel/0511.0/2429.html small patch] exists for kernels 2.6.14/2.6.15.
:*On {{X20}} and {{X21}} (and possibly other) models, the '''sleep LED''' is not reset properly on resume and will keep blinking. If you have the [[ibm-acpi]] kernel module loaded with the <tt>experimental=1</tt> option, you can switch it off on resume by appending the following line to your suspend script:
echo 7 off > /proc/acpi/ibm/led

;Crash on resume:
:*When using '''older ATI proprietary drivers''' a crash on resume can be solved by using [http://freshmeat.net/projects/vbetool/ vbetool]. See the example suspend script [[Problem with display remaining black after resume#Solution for ThinkPads with Intel I830 Chipset]]. This is no longer necessary with recent revisions of the ATI proprietary driver.
:*A crash could also be caused by having '''apic support''' enabled in the kernel config. Try disabling it (in the "Processor type and features" section).
:*On machines with Savage chipsets, the '''savagefb framebuffer driver''' might crash the machine on resume. Make sure it is disabled in your kernel config and use the standard vesafb driver instead.
:*Sonoma chipset based laptops ({{R52}}, {{T43}}, {{T43p}}, {{X41}}, {{X41T}}) utilize the '''SATA layer for disk access''' and SATA does not have power-management support yet. Suspend to RAM crashes these machines on resume. See the [[Problems with SATA and Linux#Hang on resume from suspend to RAM|relevant section]] on the [[Problems with SATA and Linux]] page.
:*When system resumes it hangs right after restarting tasks. This may be fixed by passing ec_intr=0 on kernel cmdline.
;Shutdown on resume:
:If your system immediately begins to shut down right after resume, make sure you don't have acpid running with the power button tied to shutdown. The system is simply sensing the power button event and shutting down. This issue has been reported as a bug against the kernel ACPI subsystem, refer to [http://bugzilla.kernel.org/show_bug.cgi?id=6612 kernel.org bugzilla bug #6612].

;Immediate suspend on resume:
:When running GNOME, sometimes gnome-power-manager will put the system back into suspend immediately after resuming. This is caused by a known bug in HAL that causes some ACPI events to be reported incorrectly after a suspend-to-ram. A simple workaround can be found [http://live.gnome.org/GnomePowerManager/Faq#head-b8b1280115b0a51c2cc27b13a57121130ebf36cb here].
:Note that suspend being triggered by unrelated ACPI events such as disconnecting the AC adapter may also be fixed by the above method.

Problems with ACPI suspend-to-ram

2006-08-13T02:51:27Z

Deason: /* Troubles on suspend */ Adding the "switching to UP code" problem for real. (I can't use cmdresult inside one of those headers?)

The following glitches may or may not occur in relation to suspending to RAM:

==Troubles on suspend==
;Permissions:If your suspend is failing, and a {{cmdroot|tail /var/log/acpid}} shows "Permission denied" errors, be sure that your new ACPI event and action scripts have the appropriate permissions.

;Broken sysfs interface:You may experience problems when using {{cmdroot|echo standby > /sys/power/state}} or {{cmdroot|echo mem > /sys/power/state}} (machine goes to sleep and wakes up immediately). This can be avoided by using {{cmdroot|echo -n 3 >/proc/acpi/sleep}} to get it to sleep. This can be also happen if hotplug daemon is still running.

;Hangs on "switching to UP code":You may be using a [[How to make use of Dynamic Frequency Scaling|frequency scaling governor]] such as "conservative" or "ondemand", which sometimes have problems with suspending. Switching to a governor such as "powersave" or "performance" before suspending may solve this problem.

;MySQL daemon running:If you're running MySQL, sleep may also not work, so stop MySQL first, then sleep. Remember to restart MySQL when you wakeup.

;LCD backlight remains on during sleep:When your system is equiped with a Radeon Mobility graphic controller your [[Problem with LCD backlight remaining on during ACPI sleep|LCD backlight may not turn off automatically]]. Use [[radeontool]] to switch off your backlight prior suspend in your sleep action script.

;High power drain during sleep:Also, you might want to take note of the [[Problem with high power drain in ACPI sleep]].

==Troubles on resume==
;Blank display on resume:When resuming from a suspend-to-ram the display might remain black or might only show the pre-suspend output (the system is still rebootable via {{key|ctrl}}{{key|alt}}{{key|del}}). See [[Problem with display remaining black after resume]] for solutions.
;Broken hardware support after resume:
:*The '''serial port''' of the port replicator might not work after resume.
:*The '''parallel port''' might not work after resume. A possible fix is to unload and reload the parallel port drivers: {{cmdroot|rmmod lp parport_pc parport; modprobe lp}}.
:*Problems with the '''CD-RW/DVD drive''' after wake up from ram have been experienced.
:*There is a known Problem regarding '''battery info''' after suspend to RAM. A [http://www.ussg.iu.edu/hypermail/linux/kernel/0511.0/2429.html small patch] exists for kernels 2.6.14/2.6.15.
:*On {{X20}} and {{X21}} (and possibly other) models, the '''sleep LED''' is not reset properly on resume and will keep blinking. If you have the [[ibm-acpi]] kernel module loaded with the <tt>experimental=1</tt> option, you can switch it off on resume by appending the following line to your suspend script:
echo 7 off > /proc/acpi/ibm/led

;Crash on resume:
:*When using '''older ATI proprietary drivers''' a crash on resume can be solved by using [http://freshmeat.net/projects/vbetool/ vbetool]. See the example suspend script [[Problem with display remaining black after resume#Solution for ThinkPads with Intel I830 Chipset]]. This is no longer necessary with recent revisions of the ATI proprietary driver.
:*A crash could also be caused by having '''apic support''' enabled in the kernel config. Try disabling it (in the "Processor type and features" section).
:*On machines with Savage chipsets, the '''savagefb framebuffer driver''' might crash the machine on resume. Make sure it is disabled in your kernel config and use the standard vesafb driver instead.
:*Sonoma chipset based laptops ({{R52}}, {{T43}}, {{T43p}}, {{X41}}, {{X41T}}) utilize the '''SATA layer for disk access''' and SATA does not have power-management support yet. Suspend to RAM crashes these machines on resume. See the [[Problems with SATA and Linux#Hang on resume from suspend to RAM|relevant section]] on the [[Problems with SATA and Linux]] page.
:*When system resumes it hangs right after restarting tasks. This may be fixed by passing ec_intr=0 on kernel cmdline.
;Shutdown on resume:
:If your system immediately begins to shut down right after resume, make sure you don't have acpid running with the power button tied to shutdown. The system is simply sensing the power button event and shutting down. This issue has been reported as a bug against the kernel ACPI subsystem, refer to [http://bugzilla.kernel.org/show_bug.cgi?id=6612 kernel.org bugzilla bug #6612].

;Immediate suspend on resume:
:When running GNOME, sometimes gnome-power-manager will put the system back into suspend immediately after resuming. This is caused by a known bug in HAL that causes some ACPI events to be reported incorrectly after a suspend-to-ram. A simple workaround can be found [http://live.gnome.org/GnomePowerManager/Faq#head-b8b1280115b0a51c2cc27b13a57121130ebf36cb here].
:Note that suspend being triggered by unrelated ACPI events such as disconnecting the AC adapter may also be fixed by the above method.

Problems with ACPI suspend-to-ram

2006-08-13T02:48:26Z

Deason: Rollback, screwed up formatting on the last one.

The following glitches may or may not occur in relation to suspending to RAM:

==Troubles on suspend==
;Permissions:If your suspend is failing, and a {{cmdroot|tail /var/log/acpid}} shows "Permission denied" errors, be sure that your new ACPI event and action scripts have the appropriate permissions.

;Broken sysfs interface:You may experience problems when using {{cmdroot|echo standby > /sys/power/state}} or {{cmdroot|echo mem > /sys/power/state}} (machine goes to sleep and wakes up immediately). This can be avoided by using {{cmdroot|echo -n 3 >/proc/acpi/sleep}} to get it to sleep. This can be also happen if hotplug daemon is still running.

;MySQL daemon running:If you're running MySQL, sleep may also not work, so stop MySQL first, then sleep. Remember to restart MySQL when you wakeup.

;LCD backlight remains on during sleep:When your system is equiped with a Radeon Mobility graphic controller your [[Problem with LCD backlight remaining on during ACPI sleep|LCD backlight may not turn off automatically]]. Use [[radeontool]] to switch off your backlight prior suspend in your sleep action script.

;High power drain during sleep:Also, you might want to take note of the [[Problem with high power drain in ACPI sleep]].

==Troubles on resume==
;Blank display on resume:When resuming from a suspend-to-ram the display might remain black or might only show the pre-suspend output (the system is still rebootable via {{key|ctrl}}{{key|alt}}{{key|del}}). See [[Problem with display remaining black after resume]] for solutions.
;Broken hardware support after resume:
:*The '''serial port''' of the port replicator might not work after resume.
:*The '''parallel port''' might not work after resume. A possible fix is to unload and reload the parallel port drivers: {{cmdroot|rmmod lp parport_pc parport; modprobe lp}}.
:*Problems with the '''CD-RW/DVD drive''' after wake up from ram have been experienced.
:*There is a known Problem regarding '''battery info''' after suspend to RAM. A [http://www.ussg.iu.edu/hypermail/linux/kernel/0511.0/2429.html small patch] exists for kernels 2.6.14/2.6.15.
:*On {{X20}} and {{X21}} (and possibly other) models, the '''sleep LED''' is not reset properly on resume and will keep blinking. If you have the [[ibm-acpi]] kernel module loaded with the <tt>experimental=1</tt> option, you can switch it off on resume by appending the following line to your suspend script:
echo 7 off > /proc/acpi/ibm/led

;Crash on resume:
:*When using '''older ATI proprietary drivers''' a crash on resume can be solved by using [http://freshmeat.net/projects/vbetool/ vbetool]. See the example suspend script [[Problem with display remaining black after resume#Solution for ThinkPads with Intel I830 Chipset]]. This is no longer necessary with recent revisions of the ATI proprietary driver.
:*A crash could also be caused by having '''apic support''' enabled in the kernel config. Try disabling it (in the "Processor type and features" section).
:*On machines with Savage chipsets, the '''savagefb framebuffer driver''' might crash the machine on resume. Make sure it is disabled in your kernel config and use the standard vesafb driver instead.
:*Sonoma chipset based laptops ({{R52}}, {{T43}}, {{T43p}}, {{X41}}, {{X41T}}) utilize the '''SATA layer for disk access''' and SATA does not have power-management support yet. Suspend to RAM crashes these machines on resume. See the [[Problems with SATA and Linux#Hang on resume from suspend to RAM|relevant section]] on the [[Problems with SATA and Linux]] page.
:*When system resumes it hangs right after restarting tasks. This may be fixed by passing ec_intr=0 on kernel cmdline.
;Shutdown on resume:
:If your system immediately begins to shut down right after resume, make sure you don't have acpid running with the power button tied to shutdown. The system is simply sensing the power button event and shutting down. This issue has been reported as a bug against the kernel ACPI subsystem, refer to [http://bugzilla.kernel.org/show_bug.cgi?id=6612 kernel.org bugzilla bug #6612].

;Immediate suspend on resume:
:When running GNOME, sometimes gnome-power-manager will put the system back into suspend immediately after resuming. This is caused by a known bug in HAL that causes some ACPI events to be reported incorrectly after a suspend-to-ram. A simple workaround can be found [http://live.gnome.org/GnomePowerManager/Faq#head-b8b1280115b0a51c2cc27b13a57121130ebf36cb here].
:Note that suspend being triggered by unrelated ACPI events such as disconnecting the AC adapter may also be fixed by the above method.

Problems with ACPI suspend-to-ram

2006-08-13T02:47:11Z

Deason: /* Troubles on suspend */ Adding 'switching to UP code' hang problem.

The following glitches may or may not occur in relation to suspending to RAM:

==Troubles on suspend==
;Permissions:If your suspend is failing, and a {{cmdroot|tail /var/log/acpid}} shows "Permission denied" errors, be sure that your new ACPI event and action scripts have the appropriate permissions.

;Broken sysfs interface:You may experience problems when using {{cmdroot|echo standby > /sys/power/state}} or {{cmdroot|echo mem > /sys/power/state}} (machine goes to sleep and wakes up immediately). This can be avoided by using {{cmdroot|echo -n 3 >/proc/acpi/sleep}} to get it to sleep. This can be also happen if hotplug daemon is still running.

;Hangs on {{cmdresult|switching to UP code}}:You may be using a [[How to make use of Dynamic Frequency Scaling|frequency scaling governor]] such as "conservative" or "ondemand", which sometimes have problems with suspending. Switching to a governor such as "powersave" or "performance" before suspending may solve this problem.

;MySQL daemon running:If you're running MySQL, sleep may also not work, so stop MySQL first, then sleep. Remember to restart MySQL when you wakeup.

;LCD backlight remains on during sleep:When your system is equiped with a Radeon Mobility graphic controller your [[Problem with LCD backlight remaining on during ACPI sleep|LCD backlight may not turn off automatically]]. Use [[radeontool]] to switch off your backlight prior suspend in your sleep action script.

;High power drain during sleep:Also, you might want to take note of the [[Problem with high power drain in ACPI sleep]].

==Troubles on resume==
;Blank display on resume:When resuming from a suspend-to-ram the display might remain black or might only show the pre-suspend output (the system is still rebootable via {{key|ctrl}}{{key|alt}}{{key|del}}). See [[Problem with display remaining black after resume]] for solutions.
;Broken hardware support after resume:
:*The '''serial port''' of the port replicator might not work after resume.
:*The '''parallel port''' might not work after resume. A possible fix is to unload and reload the parallel port drivers: {{cmdroot|rmmod lp parport_pc parport; modprobe lp}}.
:*Problems with the '''CD-RW/DVD drive''' after wake up from ram have been experienced.
:*There is a known Problem regarding '''battery info''' after suspend to RAM. A [http://www.ussg.iu.edu/hypermail/linux/kernel/0511.0/2429.html small patch] exists for kernels 2.6.14/2.6.15.
:*On {{X20}} and {{X21}} (and possibly other) models, the '''sleep LED''' is not reset properly on resume and will keep blinking. If you have the [[ibm-acpi]] kernel module loaded with the <tt>experimental=1</tt> option, you can switch it off on resume by appending the following line to your suspend script:
echo 7 off > /proc/acpi/ibm/led

;Crash on resume:
:*When using '''older ATI proprietary drivers''' a crash on resume can be solved by using [http://freshmeat.net/projects/vbetool/ vbetool]. See the example suspend script [[Problem with display remaining black after resume#Solution for ThinkPads with Intel I830 Chipset]]. This is no longer necessary with recent revisions of the ATI proprietary driver.
:*A crash could also be caused by having '''apic support''' enabled in the kernel config. Try disabling it (in the "Processor type and features" section).
:*On machines with Savage chipsets, the '''savagefb framebuffer driver''' might crash the machine on resume. Make sure it is disabled in your kernel config and use the standard vesafb driver instead.
:*Sonoma chipset based laptops ({{R52}}, {{T43}}, {{T43p}}, {{X41}}, {{X41T}}) utilize the '''SATA layer for disk access''' and SATA does not have power-management support yet. Suspend to RAM crashes these machines on resume. See the [[Problems with SATA and Linux#Hang on resume from suspend to RAM|relevant section]] on the [[Problems with SATA and Linux]] page.
:*When system resumes it hangs right after restarting tasks. This may be fixed by passing ec_intr=0 on kernel cmdline.
;Shutdown on resume:
:If your system immediately begins to shut down right after resume, make sure you don't have acpid running with the power button tied to shutdown. The system is simply sensing the power button event and shutting down. This issue has been reported as a bug against the kernel ACPI subsystem, refer to [http://bugzilla.kernel.org/show_bug.cgi?id=6612 kernel.org bugzilla bug #6612].

;Immediate suspend on resume:
:When running GNOME, sometimes gnome-power-manager will put the system back into suspend immediately after resuming. This is caused by a known bug in HAL that causes some ACPI events to be reported incorrectly after a suspend-to-ram. A simple workaround can be found [http://live.gnome.org/GnomePowerManager/Faq#head-b8b1280115b0a51c2cc27b13a57121130ebf36cb here].
:Note that suspend being triggered by unrelated ACPI events such as disconnecting the AC adapter may also be fixed by the above method.

Talk:Problems with ACPI suspend-to-ram

2006-08-13T02:40:35Z

Deason:

After a few resumes with my T43, I get "big green boxes" on my consoles tty1 and tty2.
tyy3 to tty6 stays completly black (there should be login prompt).
But X still working fine.

This is a minor issue, but anyone with the same problem and a fix/workaround?

--[[User:Defiant|Defiant]] 13:40, 02 Jun 2006 (CEST)
----
I have a similar issue on my T60. It seems like the problem is with the framebuffer; that the card is attempting to use the lowest resolution possible when I have the framebuffer set much higher, but that's just my intuition. I'm using hibernate with both <code>EnableVbetool</code> and <code>VbetoolPost</code> set to <code>yes</code>.

An interesting thing is that if I manually call hibernate from an xterm inside X, I get no negative effects. It even fixes the console "big green boxes" if I previously suspended not in X. Also, on resume I see the following messages on the xterm (all previous output is cleared):

Allocated buffer at 0x11010 (base is 0x0)
ES: 0x1101 EBX: 0x0000
Calling INT 0x15 (F000: 5E79)
EAX is 0x1005F08
Calling INT 0x15 (F000: 5E79)
EAX is 0x1005F08
Calling INT 0x15 (F000: 5E79)
EAX is 0x5F08
Calling INT 0x15 (F000: 5E79)
EAX is 0x5F08
Calling INT 0x15 (F000: 5E79)
EAX is 0x45F08
Function not supported

Any ideas?

-- [[User:Deason|Deason]] 05:39, 14 July 2006 (CEST)
----
Just to update/confirm: suspend to RAM only works if I have X running, and I switch to the console running X after resuming. Editing the ACPI sleep script to switch to vt 7 before switching back to the original console seems to work fine, though. It just means that I can't suspend to RAM if I'm not running X. (Putting a check for that in the ACPI sleep script would also be a good idea.) I've tried using <code>EnableVbetool</code>, <code>VbetoolPost</code>, <code>RestoreVCSAData</code>, and <code>RestoreVbeStateFrom</code> from hiberante, but none seem to solve this without switching to X.

-- [[User:Deason|Deason]] 21:48, 16 July 2006 (CEST)
----
Yes it's the vga framebuffer freaking out at you. Try adding '''acpi_sleep=s3_bios,s3_mode''' kernel option to /boot/grub/menu.lst

The s3_mode part fixed the green boxes for me. (debian testing, kernel 2.6.16, TP x41)

--[[User:Ladoga|Ladoga]] 06:46, 5 August 2006 (CEST)
----
Yay, that did it. Also, I'm not sure which option it is, but one of the options in hibernate (either <code>EnableVbetool</code>, <code>VbetoolPost</code>, <code>RestoreVCSAData</code>, or <code>RestoreVbeStateFrom</code>, or all of them) causes the framebuffer to freak out again. Disabling them, and enabling that s3_mode makes it all work again. (Debian Sid, 2.6.17, T60). Putting this in the article, I guess.

--[[User:Deason|Deason]]

Talk:Problems with ACPI suspend-to-ram

2006-07-16T19:48:53Z

Deason:

Talk:Problems with ACPI suspend-to-ram

2006-07-14T03:39:25Z

Deason:

Maintenance

2006-07-10T22:12:47Z

Deason: /* Cleaning the Interior */ Adding links to the T6x series instructions

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
Here you can find general hints about keeping your ThinkPad in good shape. Look at your [[:Category:Models|models category page]] for IBMs official maintenance guide for that model.
|}
==Battery treatment==
{| border=1 cellspacing=0 cellpadding=2 style="vertical-align:top;"
|+Battery life expanding guide
|- style="background:#efefef;white-space:nowrap;"
! style="background:#ffdead;" | Battery Type !! NiCd !! NiMH !! Lithium ion
|- style="vertical-align:top;"
! style="background:#ffdead;" | General
|
*always do complete discharge/charge cycles
*avoid exposing the battery (or notebook) to excessive heat
|
*always do complete discharge/charge cycles
*avoid exposing the battery (or notebook) to excessive heat
|
*never completely discharge the battery, partial dis-/recharges are better
*remove battery when on AC
*avoid exposing the battery (or notebook) to excessive heat
|- style="vertical-align:top;"
! style="background:#ffdead;" | Charging
|
*discharge before charging
|
*discharge before charging
|
*avoid charging if battery is nearly full
*keep notebook off while charging
*fully discharge battery every 30 or so charges to recalibrate fuel guage
|- style="vertical-align:top;"
! style="background:#ffdead;" | Storage
|
*almost discharged
*cool and dry
|
*almost discharged
*cool and dry
|
*never fully charged or discharged, ideally at about 40%
*cool and dry, but '''do not freeze''' them. 10-15C is recommended
|}

===Battery health===
Batteries, especially of the modern Li-Ion type, wear out quicker when they hold a large charge or are subject to higher temperatures (see above).

If you use your laptop at a desk, reduce battery wear by maintaining an appropriate charge level. When possible, remove Li-ion batteries while operating from AC as the notebook gets hot enough inside for that to damage the battery in the long run, even if charging is stopped.

On recent ThinkPads, charging thresholds can be configured in the bundled software. Under Linux, this is supported on recent models by the [[tp_smapi]] driver (and even without <tt>tp_smapi</tt>, if you have a dual-boot setup, you can set the thresholds under Windows and they will be remembered as long as you don't power off your machine with AC disconnected; suspend to RAM is OK). Have a look at [[How to use UltraBay batteries]].

If you have spare Li-ion battery packs, store them at 40% charge in a cool place (15C being a recommended temperature, do not let the batteries freeze). If storing inside a refrigerator, beware of humidity, and be careful with cold spots that can easily freeze the battery if anything goes wrong.

===The problem with 600 series batteries===
ThinkPad 600 power management causes batteries to die before they should. Read more about this on the [[Problem with ThinkPad 600 batteries|associated problem page]].

===Reviving batteries===
Some people experience sudden drops in their batteries capacity.

A way to get these batteries back to full capacity is to run the "Battery Rundown" function of IBMs "PC Doctor for DOS".
The program is downloadable from IBMs support site as three floppy disk images. For those who do not have a floppy, David Smith prepared a [http://www.mypchelp.com/~dsmith/ibmutil/ibm_t22_pcdiag.iso bootable CD image] from the T22 floppy images. For newer ThinkPads there is an official [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-56222 bootable CD image].

===External sources===
* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=ibm&lndocid=MIGR-50944 IBM Support - Extending battery life]
* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=ibm&lndocid=MIGR-51038 IBM Support - Battery troubleshooting]
* [http://www.pc.ibm.com/ww/thinkpad/batterylife/ IBM Benchmark]
* [http://batteryuniversity.com Battery University]
* [http://www.batteryuniversity.com/parttwo-34.htm BatteryUniversitys info about prolonging lithium ion batteries]
* [http://www.buchmann.ca/Chap10-page6.asp prolonging lithium ion batteries in Buchmanns Battery FAQ]

==Cleaning the Display==
If you discover markings that look like originating from the TrackPoint or keyboard, or for information on how to avoid these, look at [[Problem with key and trackpoint markings on the display|this page]].

===External Sources===
* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=ibm&lndocid=MIGR-4A2P54 IBM Support - LCD care and cleaning instructions]
* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=ibm&lndocid=MIGR-52190 IBM Support - System cleaning instructions]

==Cleaning the Interior==
{{WARN|The following instructions are not appropriate for all ThinkPad models. Please consult the hardware maintenance guide or on-line disassembly instructions for your model.}}
Most ThinkPad models (particularly the A-series and the T-series) tend to accumulate a lot of interior dust which they draw from their ventilation fan. A good dusting every few months is advised. The procedure is as follows.

===ThinkPad T4x series===
See IBM's keyboard removal [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-46515 instructions] and [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-50227 movie].

===ThinkPad T6x series===
See IBM's keyboard removal
[http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-62800 instructions] and
[http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-63912 movie].

===Other models (which?)===
#Unplug the computer.
#Remove the battery.
#Turn the ThinkPad over and find two to three screws with upraised double-arrows pointing to them.
#Unscrew these screws and set them aside.
#Press the silver area underneath where the battery used to be. The front of the keyboard will pop up.
#Turn the ThinkPad right side up and gently remove the keyboard, pulling it toward you.
#There is one connector between the ThinkPad and the keyboard. Disconnect it, and set the keyboard aside.
#If there is a small black plastic separator under the keyboard, remove it and set it aside.
#The fan should be visible in the upper left. That entire area will likely be dusty. With a can of compressed air (and ''only'' with a can of compressed air), dust that area and the surrounding area.
#Replace the small black plastic separator, then reconnect the keyboard.
#Slide the keyboard back into place, then press down on the Fn and right-arrow keys until it pops into place.
#Replace the keyboard screws and battery.

==Dealing with spilling accidents==
#Don't panic.
#Don't flip or tilt the computer to prevent the liquid from spreading all over the inside of the case.
#Shut down the OS and turn off the power:
##Unplug the computer.
##Remove the battery.
#Tilt the computer so that everything that leaked into the case can flow out the same way.
#Allow the computer to dry before switching it on again.
#For minor accidents this might already be sufficient. For major flooding you should either bring the computer to a dealer who knows how to open and clean it from inside. Or you can read the Hardware Maintenance Manual, open, clean, and dry the computer yourself.

See also [http://www.moneysense.ca/spending/technology/columnist.jsp?content=986628 Act quickly, carefully if you spill on laptops] on MoneySense.ca

==Harddisk Backup / Upgrade==
*[[How to copy a Linux installation]]
*[[Harddrive Upgrade|How to upgrade your Thinkpad hard drive]]
*[[How to copy a Windows installation]]
===External Sources===
*[http://gamma.nic.fi/~point/win2copy.htm Guide on copying Windows 2000/XP to another partition]

==Recovering BIOS passwords==
Password recovery procedure for IBM ThinkPads
using R24RF08 and IBMpass

'''1. Introduction.'''

As you probably know, IBM ThinkPad uses a small eeprom ([[AT24RF08|ATMEL 24RF08]]) to store different OEM
issues like serial number, UUID, etc. The supervisor password (SVP) is stored also into this little chip.
So, anybody should figure that he needs to read the eeprom in order to find the password string. The first problem is that 24RF08 is not an ordinary eeprom. The second is that the password is written in a special scan code.
To read properly you need a software (and an interface) specially designed for this eeprom.
This software is R24RF08 (eeprom reader) and IBMpass (password revealer) disponible at www.allservice.ro . Diagrams are included in the reader kit

'''2. Locating the eeprom. Soldering.'''

No need to unsolder the 24RF08 eeprom, just solder 3 wires to SDA, SCL and GND pins of the
eeprom. There are two eeprom layouts (see interface schematics described bellow), orresponding to 8 pin or 14 pin eeproms. Locate the eeprom first according to your model (E.g. T20-23 and T30 have the eeprom underneath TP, and can be accessed by removing the RAM modules cover, no need to dismantle the laptop.) and solder the wires using a soldering iron with a fine tip. Also, you can use 0.15 -0.20 mm enamel coated wires or similar small diameter insulated wires. These wires will be connected later to the interface.
Tip: You can use clips to connect the wires or you can solder on the PCB traces leading to the
eeprom pins. Once again, be careful and double, triple check the soldering if necessary till you are positively sure you have done the right job.

'''3. Choose and build the interface.'''

Since version 2.0, R24RF08 and W24RF08(eeprom writer) are compatible with a wide range of eeprom programmers. By default, both programs set the COM port signals to use direct logic level to access I2C bus. We provide here 2 schematics that are relevant for direct logic signals and for inverse logic signals (simple-i2cprog.pdf and driven-i2cprog.pdf). Also, depending of the interface you build, you can invert the logics for SDA-In, SDA-Out, and SCL COM port signals by some command line parameters described later in this document.
a) The file simple-i2cprog.pdf contains the schematic diagram of a simple interface (known as SIPROG)based on 2 zeners and 2 resistors. This is a classic, easy to build circuit and works with soldered or unsoldered eeproms. The purpose of the 2 zeners is to convert RS232 levels (+/- 5V) to TTL levels, needed by the eeprom. It uses direct logic signals to I2C eeprom and is powered by the COM port. However, this interface works with in-system eeproms but is dependant on COM port current and eeprom bus impedance. R24RF08 works natively with this circuit, no need to change the lines signals with command line parameters. This circuit works pretty well with almost all ThinkPads series.
b) The second interface is described in driven-i2cprog.pdf. The circuit uses MAX 232 as a RS232 to TTL driver and its main purpose is to work with soldered eeproms. The advantage of MAX232 is the TTL outputs that are more reliable and more powerful when work with soldered, in-system eeproms (dependency free from the COM port current). Due of the internal inverters of MAX232 the interface responds to an inverse signal logic level. R24RF08 needs /x, /d, /i switches to be specified in the command line.
What these switches mean:
/x - invert serial clock, also known as SCL;
/d - invert serial data output, also known as SDA-Out;
/i - invert serial data input, also known as SDA-In.
All those can be used in any combination to meet any interface specification.

'''4. How is it working:'''

Prepare your technician PC by connecting the interface to the COM1 port (donâ€™t connect the wires to eeprom yet). Turn on the ThinkPad and press F1 to enter BIOS Setup. When you are prompted for the password and thereâ€™s no other activity like HDD access or so, connect the wires (GND first!, SDA, SCL) to the corresponding wires from the interface (attached before to COM1) and execute R24RF08:

-for SI-PROG interface (as described in 3.a above):
r24rf08.exe <filename.ext>. where filename.ext is the file where eeprom content will be stored.
Example: r24rf08 mytp.bin

-for MAX232 driven I2C interface (as described in 3.b above):
r24rf08.exe <filename.ext> /x /d /i. where /x /d /i are command line parameters (switches) for this kind of interface.
Example: r24rf08 mytp2.bin /x /d /i

Use exactly the instructed switches to avoid possible damages to your eeprom data!
The file should be created in the same folder. Finally, disconnect the wires (GND last!) and turn off the ThinkPad by pressing on/off switch.

'''5. Reveal the password.'''

Now, you have the .bin file but you need to dump in scan code to retrieve the password. IBMpass 2.0 Lite is a free tool that will do the job. Just open the eeprom dump youâ€™ve created before and search for 0x330, 0x340 lines. The password is located on 0x338 (and 0x340 depending on model) in scan code. For 24C01 eeproms the password is located at 0x38, 0x40. If the password won't work for the very first time then your eeprom may use newer IBM scancodes. In this case switch to alternate scan codes to find it. For those who want quick answers the recommended version is IBMpass 1.1. Usage for IBMpass 1.1 (command line only):

ibmpass mytp.bin â€“ use â€œ/aâ€ switch to see in alternate scan code if needed:
ibmpass mytp.bin /a

For some old models like 570 or 770Z you need to execute the eeprom patcher first. This will reset the read protection on the password offset. To do that just execute patcher.exe before the reading operation, without rebooting the laptop:

-for SI-PROG:
patcher.exe , then immediately
r24rf08.exe <filename.ext>

-for Driven-I2C (Max232) you must insert the switches:
patcher.exe /x /d /i, then immediately
r24rf08.exe <filename.ext> /x /d /i

W24RF08, the writer version, has included the complete APP reset operation you donâ€™t need to use patcher.

Remember, use 3 wires from the interface and 3 wires from eeprom! Connect them after your
ThinkPad is powered and disconnect them right after you read the content, before you switch off the laptop.

===External Sources===
* [http://www.allservice.ro R24RF08 & IBMpass author's webpage.]
* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=ibm&lndocid=MIGR-59377 IBM Support - Lost or forgotten password]
* [http://www.serviceforum.lx.ro/viewforum.php?f=12 Full Service of all Thinkpad models including free password recovery]