ThinkWiki - User contributions [en]

Talk:Rescue and Recovery

2006-11-20T16:32:26Z

Cchiappa:

I'd like to note that my R50e shows all the signs of a Rescue and Recovery partition. I have a 4.28 GB Hidden fat32 partition labelled "IBM_SERVICE" according to QTParted. Installing LILO in the MBR also made the Predesktop Area unreachable (no response when pressing "Access IBM" during boot).
--[[User:Monobryn|Monobryn]] 17:11, 15 September 2006 (CEST)
----
Relating to the FIXME: My T42 (2373) has programs called bmgr.exe and bmgr32.exe in C:\IBMTOOLS\utils . I haven't tried them out just yet. More info when I do, and if there's anything conclusive, I'll udpate the actual page.
--[[User:Daxelrod|Daxelrod]] 23:44, 23 July 2006 (CEST)
----

"It is not known how to invoke Rescue and Recovery once GRUB has been installed in the master boot record."

See ftp://ftp.software.ibm.com/pc/pccbbs/thinkvantage_en/tvtrnr3_1027en.txt, Consideration 6:
The Master Boot Record (MBR) must be configured properly for the
Rescue and Recovery application to function properly. When possible,
the Rescue and Recovery application attempts to ensure the proper
configuration of the MBR. This can only occur if the Rescue and
Recovery application is installed after other applications that
requires the MBR.

Apparently the R and R uses some very specific stuff in the MBR. Maybe Google will help you find some further info (has someone ever looked at the R and R enabled MBR in depth?)

[[User:Pebolle|Paul Bolle]] 13:43, 9 Oct 2005 (CEST)
----

Having special data in the MBR means less room for code, which may explain why the preinstalled MBR ignores the Active bit and (as far as I can tell) always boots the first partition. The latter means GRUB can't be installed in a partition boot sector either...

--[[User:Thinker|Thinker]] 14:06, 9 Oct 2005 (CEST)
----

Why not? If the RnR-MBR always boots the first partition, just go back to the classical recommended partition layout (from the times that LILO didn't support LBA) and create a tiny first partition (that you can i.e. use as /boot partition, which has certain advantages). Install grub into that partition.

[[User:Wyrfel|Wyrfel]] 14:44, 9 Oct 2005 (CEST)
----

I saw posts about the R&R software (or at least some versions thereof) assuming that the Windows partition is the first one.

--[[User:Thinker|Thinker]] 14:52, 9 Oct 2005 (CEST)
----

Another hack you might try is to "rebrand" your first partition to some Windows type (I guess you should choose NTFS) without any other change to the fs! (So in reality it's still an ext3 fs or whatever.) If R and R is _non_ destructive (I wouldn't know!) it would be interesting to see how deeply it really checks the first partition. (It shouldn't check too deeply, as it should be able to "rescue" a messed up Windows partition, shouldn't it?)

But chances are this is a pointless hack ...

[[User:Pebolle|Paul Bolle]] 15:16, 9 Oct 2005 (CEST)
----
Is that true? That would mean you'd have to keep the Windows installation for the R&R system to work. In that case the only way to go would be installing grub4dos on that windows installation.

[[User:Wyrfel|Wyrfel]] 14:56, 9 Oct 2005 (CEST)
----
Another idea/question. Shouldn't it be possible to copy an NT boot sector to a file via dd and chainload that file from GRUB? This way grub could go to the boot sector of the first partition and boot the NT boot sector that may then sit on a Linux filesystem, which in turn would boot the first partition.

[[User:Wyrfel|Wyrfel]] 14:59, 9 Oct 2005 (CEST)
----
Could you please elaborate, Wyrfel? You lost me here ...

[[User:Pebolle|Paul Bolle]] 15:18, 9 Oct 2005 (CEST)
----

I think chaining GRUB from Windows will work (I don't know about grub4dos, but there's the trick of copying over the GRUB boot sector into a file and telling NTDETECT to load that.)

The trick with putting GRUB into the Windows boot sector and chaning into a copy of the original also sounds like it might work.

Alas, I can test neither, since I eliminated RNR from my disk after it stopped working even with the original MBR restored. No idea why. IBM sure didn't work very hard to make RNR 3.0 compatible with the standard partitioning and boot conventions...

--[[User:Thinker|Thinker]] 16:12, 9 Oct 2005 (CEST)

For my R50e the claim, that the active bit is ignored is not true. If I remove the active bit or put it to my Linux partitition I get something like missing operation system
--[[User:Samba|Samba]

----

----
I mean the reverse approach of [[How_to_setup_boot_loaders#Using_the_NT_Boot_Loader_to_boot_Linux|this]].

Copy the NT boot sector into a file, place that file on a linux partition, boot into the file via grub. I don't know if this could at all work. First, grub might not be able to chainload a file, though i believe it is, second, the NT boot sector may not like to be a file. AFAIK, the NT boot sector knows the partition it is suppossed to find NTLDR on. So it wouldn't depend on being the first sector of the same partition.

[[User:Wyrfel|Wyrfel]] 01:27, 10 Oct 2005 (CEST)
----

== Success booting R&R from GRUB ==

The method mentioned on the article (changing the partition type to 0x0b) worked for me on my T42.

You can do that with GRUB:

parttype (hd0,1) 0x0b

You can add that to a GRUB menu entry that boots the recovery partition, which otherwise looks like this:

title IBM Rescue and Recovery
root (hd0,1)
chainloader +1

(Note that the Access IBM does not work during boot any more -- you have to explicitly choose the R&R partition from the GRUB menu. Good enough for me.)

I think that the recovery partition type is set to 0x12 to hide it from your Windows installation. The preinstalled MBR probably changes the partition type when you press Access IBM, and changes it back on next boot.

Grub for dos is the best solution: http://freshmeat.net/projects/grub4dos/

----

More advice (which didn't work for me without the partition type fix):

* IBM Support: [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-46088
Accessing the Recovery Partition if Linux has been installed and the F11 button no longer works]

* [http://sharadware.com/2005/07/11/suse-linux-winxp-access-ibm-on-the-thinkpad-t43/ how to keep the AccessIBM functionality]: 
''Set the IBM Predesktop Area (in the BIOS) to â€œSecureâ€. Boot using the SUSE DVD. Shrink the Windows partition as required. Follow the instructions and go through the regular installation process. Create a primary partition for /boot (the other stuff can go into the extended partitions) and when the time comes to install GRUB (you do prefer GRUB to LILO, donâ€™t you?), make sure you install it into the boot sector of the boot partition. Set this partition as active. Leave the MBR alone.''

The issue and solutions need to be summarized and added to the main article.

--[[User:Thinker|Thinker]] 19:26, 9 Dec 2005 (CET)
----
Tried to do just that. Please correct hings if i got something wrong. [[User:Wyrfel|Wyrfel]] 14:46, 31 January 2006 (CET)
----

== R52 MBR for those who want to dissect it. ==

Hi there, I had the issue regarding the blue screen while trying to boot the IBM R&R partition, but the type-changing trick worked. I made a complete factory restore, and I was happy to discover that it fixed the MBR in such a way that the R&R PreDesktop area now works at all times. I've now made a backup of this MBR in case something ever happens (like accidentally putting a better boot loader in it ;-)). It looks quite different compared to a classic Windows XP made MBR, so it might be worth to take a look.

Anyway, for those interested, [http://student.ulb.ac.be/~mlindstr/ibm-r52.mbr the R52 MBR can be downloaded here].

[[User:81.240.31.97|81.240.31.97]] 10:21, 28 Oct 2005 (CEST)

----

Thanks for the information. Question: "works at all times" here means:

a) when pressing the Access IBM / ThinkVantage / Whatever button

b) when booted by GRUB (chainloaded by NTLDR?)

c) ?

[[User:Pebolle|Paul Bolle]] 20:52, 28 Oct 2005 (CEST)

----

Yeah sorry, I could have been more verbose on that part. Actually, what I meant was that pressing the "Access IBM" button launches the R&R area successfully, regardless of the partition being of type 0x12 or 0xb. I'm fairly sure that if anything is changed in the MBR, R&R will be broken once more. I guess some very specific stuff is initialized within the master boot code. I can't risk experimenting with it for now, as the laptop in question isn't mine to begin with.

Also, note that pressing the button doesn't give any other options, apparently. It just immediately boots the R&R partition. When the MBR was tampered with, pressing the button would give a boot menu, where one could choose to enter the BIOS menu, or boot another device. The only way to boot into R&R was to use a separate bootloader (in my case, a GRUB boot CD).

[[User:81.240.31.97|81.240.31.97]] 23:19, 28 Oct 2005 (CEST)

----

It would be rather nice to dissect and discus that MBR. But I'm not sure whether we should encourage to do that on ThinkWiki. Any opinions (other than mere slogans such as: "We should have freedom to tinker!") on this subject would be greatly appreciated. Admins?

[[User:Pebolle|Paul Bolle]] 01:03, 30 Oct 2005 (CEST)

----
Concerning the encouragement, it should in any case be clearly mentioned that tinkering can cause (serious) damage. For as far as legal issues go, R&R is a trademark, but APS is as well. Reverse engineering is a legal issue in some countries, but not in all. People who dig into this should be aware of their legal situation. That said, i think it's an interesting issue that might shed light into the MBR in general. If the final result gets provided here as a way of how to build a compatible GRUB MBR or something the like, i see no issues with the publication. I think, however, that discussing the fiddling (reverse engineering - if so) process here is not without concerns, because afaik this has legal issues in some countries.

[[User:Wyrfel|Wyrfel]] 02:03, 30 Oct 2005 (CET)

----

I accidently killed my bootsector when I installed Linux, so this image comes in verry handy to restore the "Access IBM" button function. How can I write this image back onto my disk?

--[[User:84.63.23.253|84.63.23.253]] 22:58, 5 Dec 2005 (CET)

----
Hello,
dealing with a new T43p (installing Ubuntu 5.10) and struggling with the AccessIBM "thing". 
There seems to be a way to backup the "special" IBM MBR, and that would give a lot
of peace of mind because one could restore that instead of reinstalling everything from the CDs.
How can that be done?
Just a plain dd on /dev/sda?

I have checked the [http://sharadware.com/2005/07/11/suse-linux-winxp-access-ibm-on-the-thinkpad-t43/ SUSE Linux, WinXP & Access IBM on the ThinkPad T43 thread on SharadWare],
whose bottom line seems to be: '''don't touch the MBR, put grub in a linux partition and make that the bootable partition'''.

However, if I do that it does not start with grub.
I have posted a longish note there [http://sharadware.com/2005/07/11/suse-linux-winxp-access-ibm-on-the-thinkpad-t43/#comment-210 my post].

One of the main outstanding questions to me is: ''does AccessIBM boot alright if/when called from GRUB if this latter is installed in the MBR?'' 
If so, then I will be happy to go with a normal grub-in-MBR.

Does anybody know the answer? 
Thanks

--[[User:Fossatig|GF]] 00:08, 19 Dec 2005 (CET)

----

FYI I have just come across this page on the IBM site: 
[http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-54483 Recovery repair diskette], it seems to
make it possible to restore the MBR to the factory installed status, namely it states "''This package can also be used to reenable the F11 function as long as the service partition has not been removed from your hard drive.''" 

It could be the lifesaver for heavy-testing moments, because based on my readings more or less
the solution seemed to be to reinstall everything.

I have not tried this yet, and I hope I will not need to, but since the system (t43) is
new I could invest some time in this... I will keep you posted.

Only '''question'''... the instructions are for creating a floppy, but there is not floppy driver
in the T43. Will it be ok to create the floppy on any other windows box?

[[User:Fossatig|GF [t41, t43p]]] 01:04, 19 Dec 2005 (CET)

----

I have tested the Recovery repair diskette on my T43, which was not booting the Rescue and Recovery partition anymore. I have successfully created and used the disk with an USB floppy drive. Everything works now again the same way it used to when the laptop was shipped.
The tool on that floppy will offer two different major options:

"1. Repair the current master boot record" and 
"2. Replace the current master boot record.".

The first option did not fix the problem with the Rescue and Recovery partition on my system. When selecting the second choice, there were three new "sub-options":

"A: Supports the newer IBM Rescue & Recovery ...", 
"B: Supports previous versions ..." and 
"C: Supports only the main operating system environment.".

For my system the choice A was successfull.

--[[User:217.146.157.238|217.146.157.238]] 10:30, 12 Jan 2006 (CET)

----

Hmm... I just tested this on my T43. The starting point was that I hosed the original MBR by installing grub onto it. "repair the current master boot record" did repair the MBR, but the IBM rescue & recovery was still unaccessible from BIOS ({{ibmkey|Access IBM|#495988}}). However, replacing the MBR did the trick, so I can boot from grub into linux, winXP and IBM rescue and recovery. The {{ibmkey|Access IBM|#495988}} key works from BIOS.

== Diagnostic tools only ==

Anybody know how to run the hardware diagnostic tools only from the R&R backup CD's? I can boot off the R&R diagnostic CD, but in order to run diagnostic hardware tests, the cd asks to reboot the system, which will then repeat the process. I do not have the R&R partition on my hdd (backed up before putting Linux on the hdd.)
--[[User:gsmenden|gsmenden]] 10:50, 30 Jan 2006 (EST)

== Problems with Windows Partition ==
I have successfully managed to install Kanotix and keeping the "ACCESS IBM"-Key working at the beginning by following the instructions in the way that I installed GRUB in the LINUX-Partition, not in the MBR. However, I can not boot the Windows XP-Partition which I have downsized with Qt-Parted. When I start it I get a GRUB-Error 25, before Installing Linux I got something "invalid ...". From Linux the Partition is fully accessible, so I have 3 theories what is the problem:
- I have stopped the Thinkpad-System-Installation just at the point where it was going to convert the file system into NTFS (did not let it reboot at this point), so the problem may have something to do, that the convert utility tampered the file-system
- The partition shrinking did not work correctly, at least for Windows standards.
- Something wrong with my Grub-configuration, this is less likely since it also did not work, when Linux was not installed.
Another problem: After using Diagnostics, the setting of the active partition is changed in the partition table. So the next booting does not work, I have to manually reset it.
Any hints? Samba

BTW: Rescue and Recovery is also used with Thinkpad R50e

A recommendation: If you want to keep your Windows Partition and resize it, I can recommend [http://gparted.sourceforge.net/livecd.php|Gparted-Live CD]. The actual version even resizes, when the partition is fragmented. That is important because the defragmenter within Windows does not defragment correctly.

== Moving the R&R Partition ==
I just got a new hard drive and, since my recovery CDs had gone bad, I wasn't able to just do a reinstallation with the new hard drive (IBM/Microsoft only let you make one copy of the recovery CDs off the hard drive). So, I decided to preserve my current installation by dd'ing the old 40GB hard drive to the new 120GB one. Unfortunately, this led to a fragmented situation since, while I can move my Linux partitions no problem and ntfsresize can grow the NT partition, the rescue partition is smack in the middle of the drive at the 35GB mark. It wasn't enough to make a new recovery partition at the end and dd the current one over because the format of the DOS boot sector depends on the size of the partition and the geometry of the disk. I discovered however, that I could use GNU parted to cp the old R&R partition to the new one and GRUB could then boot it just fine, even though the partition number had changed from 2 to 4. I suspect that using parted's move command would work as well and probably work with the original MBR as well since that would preserve the partition number.
[[User:Cchiappa|Cchiappa]] 17:32, 20 November 2006 (CET)

How to get special keys to work

2005-04-04T02:12:59Z

Cchiappa: Add description of using Forward and Backwards keys for fvwm

===Overview===
{| border="1" cellspacing="0" cellpadding="2"
! key !! standard function !! tool !! configurability !! remarks
|-
| Fn || - || xmodmap, [[tpb]] || full || on release without completed key combination
|-
| Fn-F3 || blank screen || [[ibm-acpi]], [[thinkpad-acpi]] || full ||
|-
| Fn-F4 || suspend to ram || [[ibm-acpi]], [[thinkpad-acpi]] || full ||
|-
| Fn-F5 || switch bluetooth || [[thinkpad-acpi]] || ??? || in models starting from 2002
|-
| Fn-F7 || switch display || [[thinkpad-acpi]], [[tpb]] || additional actions ||
|-
| Fn-F8 || toggle display expansion || [[thinkpad-acpi]], [[tpb]] || additional actions ||
|-
| Fn-F9 || eject from dock || [[thinkpad-acpi]] || full ||
|-
| Fn-F12 || hibernate || [[ibm-acpi]], [[thinkpad-acpi]] || full ||
|-
| Fn-Pos1 || brightness up || [[tpb]] || additional actions ||
|-
| Fn-End || brightness down || [[tpb]] || additional actions ||
|-
| Fn-PageUp || toggle thinklight || [[ibm-acpi]], [[tpb]] || additional actions ||
|-
| Fn-Space || toggle zoom || [[tpb]] || full ||
|-
| Access IBM || help application || [[tpb]] || full ||
|-
| Home || open web browser || xmodmap, [[tpb]] || full || only iSeries and ext. keyboards
|-
| Search || open search application || xmodmap, [[tpb]] || full || only iSeries and ext. keyboards
|-
| Mail || open mail application || xmodmap, [[tpb]] || full || only iSeries and ext. keyboards
|-
| Favorites || open favorites || xmodmap, [[tpb]] || full || only iSeries and ext. keyboards
|-
| Reload || reload web page || xmodmap, [[tpb]] || full || only iSeries and ext. keyboards
|-
| Abort || abort loading page || xmodmap, [[tpb]] || full || only iSeries and ext. keyboards
|-
| Backward || previous page || xmodmap, [[tpb]] || full || iSeries, ext. keyboards, Thinkpads starting from 2002
|-
| Forward || next page || xmodmap, [[tpb]] || full || iSeries, ext. keyboards, Thinkpads starting from 2002
|-
| Volume up || volume up || [[tpb]] || additional actions ||
|-
| Volume down || volume down || [[tpb]] || additional actions ||
|-
| Volume mute || mute volume || [[tpb]] || additional actions ||
|-
| Power || shutdown || [[ibm-acpi]] || full || triggered on pressing 3secs, but notebook goes off on 5sec press
|-
| Display lid || blank screen || [[ibm-acpi]] || full ||
|-
| Ultrabay lid || announce ultrabay change || [[ibm-acpi]] || full ||
|-
| Dock eject || eject from dock || [[ibm-acpi]] || full ||
|}

===ibm-acpi events===
{| border="1" cellspacing="0" cellpadding="2"
|+ events triggered by ibm-acpi for /etc/acpi/events files
! key !! event
|-
| Fn-F3 || ibm/hotkey HKEY 00000080 00001003
|-
| Fn-F4 || ibm/hotkey HKEY 00000080 00001004
|-
| Fn-F12 || ibm/hotkey HKEY 00000080 0000100c
|-
| Power || button/power PWRF 00000080 xxxxxxxx
|-
| Display lid || button/lid LID 00000080 xxxxxxxx
|-
| Ultrabay eject || ibm/bay MSTR 00000003 00000000
|-
| Ultrabay inserted || ibm/bay MSTR 00000001 00000000
|}

===tpb configuration===
{| border="1" cellspacing="0" cellpadding="2"
|+ configuration keywords for tpbrc
! key !! config keyword
|-
| Access IBM || THINKPAD
|-
| Home || HOME
|-
| Search || SEARCH
|-
| Mail || MAIL
|-
| Favorites || FAVORITES
|-
| Reload || RELOAD
|-
| Abort || ABORT
|-
| Backward || BACKWARD
|-
| Forward || FORWARD
|-
| Fn || FN
|-
| Fn-Space || CALLBACK (zoom on/off)
|-
| Fn-PageUp || CALLBACK (thinklight on/off)
|-
| Fn-F7 || CALLBACK (display lcd/crt/both)
|-
| Fn-F8 || CALLBACK (expand on/off)
|-
| Fn-PageUp || CALLBACK (brightness <percent>)
|-
| Fn-PageDown || CALLBACK (brightness <percent>)
|-
| Volume up || CALLBACK (volume <percent>)
|-
| Volume down || CALLBACK (volume <percent>)
|-
| Volume mute || CALLBACK (mute on/off)
|}

To all parameter keywords should be assigned the full path to the executables supposed to be started on key press.
The exectable provided for the CALLBACK keyword should take the parameters given in parentheses and act according to them.
If you want to use xmodmap for the HOME, SEARCH, MAIL, FAVORITES, RELOAD, ABORT, BACKWARD, FORWARD and FN keys you should
provide a XEVENTS=off in your tpbrc.

===xmodmap configuration===
xmodmap enables you to edit the modifier map and keymap tables that are used to translate keycodes into keysyms.
Understood? Well, basically it allows you to give the X server a dictionary for the translation of keycodes like "97" into more human readable synonyms like "Home". This way xmodmap allows you to make the special keys of your keyboard known to X applications.

Usually you should write your keycode-keysym associations into the file ~/.Xmodmap. This file is usually read by the X session startup scripts of your system, so that the mappings automatically get included everytime you run the X server.

The ~/.Xmodmap lines for our purpose are in the form of
keycode <keycode> = <keysym>

The following table shows the keycodes generated by the Thinkpad special keys and sensible keysyms to assign them to.
{| border="1" cellspacing="0" cellpadding="2"
|+ keycodes and recommended keysyms
! key !! keycode !! keysym
|-
| Backward || 234 || XF86Back or F21
|-
| Forward || 233 || XF86Forward or F22
|-
| Home || 178 || XF86HomePage
|-
| Search || 229 || XF86Search
|-
| Mail || 236 || XF86Mail
|-
| Favorites || 230 || XF86AddFavorite or XF86Favorites
|-
| Reload || 231 || XF86Reload
|-
| Abort || 232 || XF86Stop
|-
| Fn || 227 || F35
|}

(In case you want to use the browser keys in Firefox, you will have to assign the F21 and F22 or similar keysyms to them.)

Note: if you are running tpb you might need to add the line XEVENTS=off into your tpbrc to stop it from grabbing the key events and allow them to get through to X instead.

===firefox configuration===
(First of all thanks go to Ryan Barrett for writing the little howto on his blog.) 
To have firefox make use of the browser keys you need to modify one of its files.
To do this you will first need to extract it from the browser.jar archive. Do...
$ cd <firefox-directory>/chrome
$ unzip browser.jar
The file of interest is content/browser/browser.xul. Edit it...
$ vi content/browser/browser.xul
Look for the '''<keyset id="mainKeyset">''' section and add the following lines within...
<key id="goBackTP" keycode="VK_F21" command="Browser:Back" />
<key id="goForwardTP" keycode="VK_F22" command="Browser:Forward" />
No save the file and repackage the browser.jar archive...
$ zip -rD0 browser.jar content/browser/
That's it.

===pekwm configuration===
This is just a small example of what else you can do with your extra keys. 
I configured the two browser keys of my T41p to switch workspaces in pekwm, by adding the following two lines to the .pekwm/keys file:
KeyPress = "Mod1 XF86Back" { Actions = "GoToWorkspace prev" }
KeyPress = "Mod1 XF86Forward" { Actions = "GoToWorkspace next" }

===pwm configuration===
Another example how to use these two keys to switch between pwm tabs. These two lines should be added to $HOME/.pwm/keys-default.conf or /etc/pwm/keys-default.conf:
kbind "Back", "switch_rot", -1
kbind "Forward", "switch_rot", 1

===opera configuration===
However this isn't simple configration file, you can set your browser manualy. 
Go to Tool > Settings > Mouse and keyboard > Keyboard settings > Edit > Browser Window. There add F21 - Back and F22 - Forward. Now you can surf using your TP keys ;-)

===fvwm configuration===
To get the Backwards and Forwards keys to cycle through pages in the virtual desktop, add this to your .fvwmrc:
Key XF86Back A A Scroll -100000 0
Key XF86Forward A A Scroll +100000 0
If you use multiple virtual desktops, you could instead use the keys to flip between them by using GotoDesk.

Problem with high power drain in ACPI sleep

2005-03-12T23:09:30Z

Cchiappa: Note 2378-FVU unaffected

Information about the problem of too high power drain in ACPI sleep mode.

==Problem description==
Several people realised that their ThinkPads eat up too much power while suspended to ram via ACPI. Compared to APM suspend to ram the power drain is experienced to be about 10 times as high, 2-5 Watts. This empties the battery within one or two days.

==Affected Models==
*Different symptoms have been reported for different models. In some models the origin of the power drain is obvious ([[Problem with LCD backlight remaining on during ACPI sleep|backlight on during suspend]]), in other models there is no obvious reason.
*On some models/configurations the higher power drain couldn't even be realized or was at least significantly lower.
*The T4x thinkpad series (T40, T40p, T41, T41p, T42, T42p) suspends to ram just fine, and there are no components that are obviously left powered up. The ultrabay and network light is on, but that is the same under windows (but under APM sleep to RAM those lights are OFF).
The following table gives an overview of the models suffering from the mysterious power drain. To find out about your model, you may use the following [[ACPI sleep power drain test script | script]]. It creates a file <tt>/var/log/battery.log</tt> which will tell you if you are affected or not.

One thing to keep in mind, though, is that some models only suffer this problem with certain software. For example, my T40 (2374-94U) has the high power drain issue with the stock Fedora Core 3. If I use one of the more recent kernels from [http://www.sas.upenn.edu/~vbraun/computing/T41/kernel.html Volker Braun's T-41 site], everything (suspend-to-RAM, suspend-to-disk) works just fine and my battery life seems much better than APM. In other words, just because you see this problem with your ThinkPad with your current software does not mean that your ThinkPad will doomed to always be affected. There are similar solutions for Debian-based systems too.

{| border="1" cellspacing="0" cellpadding="2"
|-
! style="vertical-align:top;background-color:#ffcfbc;" | affected models
! style="vertical-align:top;background-color:#cfefcf;" | unaffected models
|-
| style="vertical-align:top;background-color:#fff0e0;" |
*[[:Category:T40 | T40]]
**2373-MU3
**2373-82U
**2373-92U
**2373-22G
*[[:Category:T40p | T40p]]
**2373-G1U
**2373-G3U
**2373-G3G
**2373-G1G
* [[:Category:T41 | T41]]
**2379-DJU
**2373-9HU
**2373-4FG
**2373-2FG
**2373-6U4
**2373-7JU
* [[:Category:T41p | T41p]]
**2373-9FU
* [[:Category:T42 | T42]]
**2378-DUU
**2373-FWG
* [[:Category:R40 | R40]]
** 2722-5MG
** 2722-B3G
** 2897-GWU
* [[:Category:X21 | X21]]
* [[:Category:T30 | T30]]
** 2366-81A
** 2366-97U
* [[:Category:R51 | R51]]
** 1829-EHG
** 1836-Q6U
| style="vertical-align:top;background-color:#e9f9e9;" |
*[[:Category:T41p | T41p]]
**2373-GKG
**2373-GGG
**[[2373-GHG]]
*[[:Category:T42p | T42p]]
**[[2373-HTG]]
**[[2373-W6M]]
**[[2373-GTG]]
**[[2373-GXG]]
**2373-KXM
*[[:Category:T42 | T42]]
**[[2378-FVU]]
*[[:Category:R50p | R50p]]
|}

==Affected Operating Systems==

*Linux, all flavours.
*Windows, for some models as well (only when using non-IBM drivers).

==Status==
The cause of the problem is not really clear, yet.

A faulty DSDT might be responsible for the phenomenon. The thinkpad T4x DSDT has a few small bugs, none of which should cause the extra power drain. (Interesting to note: The DSDT from BIOS 3.13 (Nov 04) for the T42p compiles without bugs.)

There is a interesting discussion taking place in the [http://bugme.osdl.org/show_bug.cgi?id=3022 OSDL Bugzilla].

Update: it seems that the most significant difference can be made by properly turning off the video chip.

==Solutions==
===For Thinkpads with Radeon graphic driver===
A proposed solution is to remove the CONFIG_PPC_PMAC condition for enabling D2 sleep in drivers/video/aty/radeon_pm.c as discussed in [http://bugme.osdl.org/show_bug.cgi?id=3022 kernel bug 3022]. There you can also find patches doing this. The patches devide in unconditional ones like [http://carrot.hep.upenn.edu/~vbraun/kernel-T4x/test/patch-2.6.11-rc2-radeonfb-D2.patch.bz2 this one for 2.6.11-rc2] and conditional ones. The conditional ones only do D2 on models where it has been reported to work, the unconditional ones force D2 sleep on every model and you might experience hangs on resume with those.

For [[:Category:Fedora Core | Fedora Core]] there's are precompiled patched kernels (2.6.11-rc2 based) available:
*[http://carrot.hep.upenn.edu/~vbraun/kernel-T4x/test/kernel-DANGEROUS-T4x-2.6.11-8.i386.rpm kernel with unconditional patch applied]
*[http://carrot.hep.upenn.edu/~vbraun/kernel-T4x/test/kernel-T4x-2.6.11-8.i386.rpm kernel with conditional patch applied].

If you try, please send the result (hang yes/no, battery drain yes/no) with the precise model number (for example, I have a IBM thinkpad T41 2379-DJU) to <tt>vbraun at physics dot upenn dot edu</tt>, it would be nice if your subject line would include "RADEONFB:" to make sure that I do not miss any emails.

'''ATTENTION!''' 
This solution enables doing suspend-to-D2 on non-PPC-machines, which is not tested at all and supposed to be the wrong thing to do!
Be careful and have a look at [http://bugme.osdl.org/show_bug.cgi?id=3022 the bugs discussion] before applying the patch.

===Other models===
Nothing yet.

[[Category:R40]] [[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R51p]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:X30]] [[Category:X31]] [[Category:X40]]