ThinkWiki - User contributions [en]

How to control fan speed

2011-10-07T15:45:56Z

TheAnarcat: add x120e

This page discusses methods for controlling the system fan.

{| width="100%" columns="2"
|style="vertical-align:top;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |

{{WARN|When designing fan-control applets, never ignore a valid thermal sensor.

Even if it seems to be stuck at a certain temperature, you must take that sensor into account. While it will probably make the fan spin faster than if the sensor was ignored, that's exactly what would happen when the fan is under EC control, and could very well be the reason for the "stuck" value in the first place.

Always play it safe. If a battery pack seems to want the fan to always run faster, the only safe thing to do is to make it run faster.}}
|}

==For Linux==

{{NOTE|Fan control operations are disabled by default for safety reasons.}}

To enable fan control, the module parameter <tt>fan_control=1</tt> must be given to thinkpad-acpi.

For example, in Ubuntu 8.04 (Hardy Heron), add the following to {{path|/etc/modprobe.d/options}}: <tt>options thinkpad_acpi fan_control=1</tt>

For Debian Squeeze (testing) create {{path|/etc/modprobe.d/thinkpad_acpi.conf}} with: <tt>options thinkpad_acpi fan_control=1</tt> and install the package <tt>thinkfan</tt>

Having done so, reboot and you can use the following commands to control fan speed:

{{cmdroot|echo level 0 > /proc/acpi/ibm/fan}} (fan off)

{{cmdroot|echo level 2 > /proc/acpi/ibm/fan}} (low speed)

{{cmdroot|echo level 4 > /proc/acpi/ibm/fan}} (medium speed)

{{cmdroot|echo level 7 > /proc/acpi/ibm/fan}} (maximum speed)

{{cmdroot|echo level auto > /proc/acpi/ibm/fan}} (automatic - default)

{{cmdroot|echo level disengaged > /proc/acpi/ibm/fan}} (disengaged)

If you receive a PERMISSION DENIED error you can use the following command syntax instead as a work-around:

<code style="white-space:nowrap;color:#495988;background-color:white;"><nowiki>#</nowiki> echo level 0 | sudo tee /proc/acpi/ibm/fan</code> (fan off)

<code style="white-space:nowrap;color:#495988;background-color:white;"><nowiki>#</nowiki> echo level 2 | sudo tee /proc/acpi/ibm/fan</code> (low speed)

<code style="white-space:nowrap;color:#495988;background-color:white;"><nowiki>#</nowiki> echo level 4 | sudo tee /proc/acpi/ibm/fan</code> (medium speed)

<code style="white-space:nowrap;color:#495988;background-color:white;"><nowiki>#</nowiki> echo level 7 | sudo tee /proc/acpi/ibm/fan</code> (maximum speed)

<code style="white-space:nowrap;color:#495988;background-color:white;"><nowiki>#</nowiki> echo level auto | sudo tee /proc/acpi/ibm/fan</code> (automatic - default)

<code style="white-space:nowrap;color:#495988;background-color:white;"><nowiki>#</nowiki> echo level disengaged | sudo tee /proc/acpi/ibm/fan</code> (disengaged)

===Automated control scripts===

An [[ACPI fan control script#Variable speed control scripts|ACPI fan control script]] can be used to override the firmware's fan algorithm with gentler, quieter version. It monitors the laptop's [[thermal sensors]] and sets the fan speed accordingly, according to customizable thresholds. For the default behavior, simply save {{CodeRef|tp-fancontrol}} as {{path|tp-fancontrol}}, make sure you've loaded [[thinkpad-acpi]] with the "fan_control=1" parameter, and run:<br />
{{cmdroot|./tp-fancontrol}}

There is an distro independent daemon (http://launchpad.net/tp-fan/tpfand/0.94/+download/tpfand-0.94.tar.gz), written in python. Packages are available for debian based linux systems.

[http://www.gambitchess.org/moin.py/ThinkPad_Fan_Control A GTK GUI program (packaged for Ubuntu 7.10 and 8.04)] may also help.

===Automated program - Simple ThinkPad Fan Control===
Written by Stanko, stanko [at] mfhinc [dot] net

This is program for controlling fans speed on IBM/Lenovo ThinkPads. It is written
for Linux only. This program is written in C, using GTK GUI.

You are required to have the Linux kernel with 'thinkpad-acpi' patch.
You must also enable manual control for your fans. For Linux 2.6.22 and above,
you must add 'fan_control=1' as a module parameter to 'thinkpad-acpi'.
For example, in Debian Lenny (and Ubuntu 8.04), you must add the following
to "/etc/modprobe.d/options":
options thinkpad_acpi fan_control=1

Having done so, reboot. Now you'll be able to use this program easily.

Here is screenshot:
[[Image:Tpfc.png|none]]

and direct download (src + i386 32bit binary). Please read README.txt file
included in package.

'''Download links'''

[[http://www.box.net/shared/phz3foll8oe0501k8s1j tpfc0.5.tar.gz]]

[[http://stanko.mfhinc.net/projects/tpfc/tpfc0.5.tar.gz mirror 1]]

[[http://sale.mfhinc.net/wp-content/uploads/2010/04/tpfc0.5.tar.gz mirror 2]]

----

I wrote this for my own personal use, and thought that it would be a good idea
to release it to the world, and hope that it will be useful to someone!
Feel free to send comments, bug reports or a thanks to the e-mail above. Although I don't use ThinkPad anymore (so I can't test the program), I still try to respond to all emails I get.

==For Windows==

Shimodax's ThinkPad fan control tool offers similar functionality (see [http://forum.thinkpads.com/viewtopic.php?t=17715 forum discussion] at thinkpads.com). Source and binaries are available through the [http://sourceforge.net/projects/tp4xfancontrol "Tp4xFanControl"] project on SourceForge.

==Hardware specs==

The following hardware behavior was discovered experimentally by [[User:Thinker|Thinker]] and neither provided by nor confirmed by IBM/Lenovo. The following description may be inaccurate and may vary by model (see list of models above). The terminology probably does not match the one used by IBM/Lenovo engineers.

{{NOTE|Information on other models is included in the [[thinkpad-acpi]] [[Git]] version.}}
{{NOTE|1=The ThinkPad {{X61s}} and {{X61}} with WWAN have a [http://forum.notebookreview.com/showthread.php?t=141931 second system fan]. It shares the same control register as the main fan (cannot be controlled separately), and exposes a second tachometer.}}

ACPI DSDT register HFSP (8 bits, offset 0x2F in the <tt>EmbeddedController</tt> address space, accessed through the standard EC interface at IO ports 0x62 and 0x66) is read/writable and has the following meaning:

Bits 7 6 5 4 3 2 1 0
---------------
Value 1 0 * * * * * * - automatic
* 1 * * * * * * - disengaged
0 0 N N N N N N - manual (0..63; 0=disable fan, 1=min, ..., 7=max)

Changing modes may not be immediate on all ThinkPads. Later ThinkPad models seem to take at least 5s to start responding to a fan mode change, for example.

After boot, the HFSP register may not reflect the true state of the EC (on some models it reads 0x07 even though the EC is actually in automatic mode).

The HFSP register controls both fans at the same time in the X61/X61s.

=== Fan Tachometer ===

The embedded controller registers 0x84 (LSB), 0x85 (MSB) are the main fan tachometer, and report fan speed in RPM in everything since the {{A31}} and maybe a little earlier. Not much is know about the tachometer in earlier models, or even whether they had one or not.

On the X61/X61s, one must select through EC register 0x31 bit 0 which fan the tachometer registers will expose (Firmware 7M). Beware: this is the same register used for brightness control in other models.

=== Automatic mode ===
In ''automatic'' mode, the embedded controller sets the fan speed automatically according to system temperatures and some unknown algorithm.

Note that the ACPI DSDT may supplement this in some models. The {{X40}}, for example, changes the profile of speeds the automatic mode should use depending on battery status.

=== Manual mode ===

In ''manual'' mode, the fan level is forced to the given value and the EC will auto-regulate the fan to maintain at a (roughly) constant RPM, which is model-dependent. Manual speed levels 8-63 yield the same behavior as level 7, and the the ACPI DSDT uses level 7 for the emergency mode it enters upon critical CPU/GPU temperature, so apparently 7 is the real maximum level.

=== Disengaged (full-speed) mode ===

In ''disengaged'' mode, the embedded controller does not monitor the fan speed. It "disengages" the closed-loop control function that keeps track of fan speed, and uses an open-loop control function that ramps up the fan to its maximum speed (100% duty-cycle). The end speed is not stable, but it is often much faster than the maximum speed manual and automatic modes would set the fan to.

Most newer ThinkPads take quite a while (in excess of one minute) to fully enter disengaged mode. Exiting it is much faster. The {{A31}} acts differently, and switches to disengaged mode as fast as it switches to other modes.

For some reason, the embedded controller may stop updating the tachometer registers while entering or exiting disengaged mode in some ThinkPad firmware versions (hence the EC tachometer registers will not be updated on these models while entering/exiting disengaged mode). Once it arrives at maximum speed, or once it gets back at closed-loop cruise speed, the embedded controller starts updating the tachometer registers again. Later T models such as the {{T43}} have this problem, while the {{A31}} does not.

{{HINT|Apparently the [[Problem with fan noise|pulsing fan noise]] experienced by some users can be cured by repeatedly running 2-4 seconds of manual control followed by 0.5-1 seconds of disengaged mode. The pulse occurs when the the embedded controller computes the fan speed and adjusts the fan voltage adaptively every few seconds (~4.8sec for the ThinkPad T43); the aforementioned mode switching doesn't give it a chance to do so. One of the [[ACPI fan control script#Variable speed control scripts|ACPI fan control scripts]] implements this solution.}}

==Supported models==

The above was successfully tested on the following models:

* ThinkPad {{A31}}, {{A31p}} (fan levels RPM: 0 = off, 1-2 = ~3280-3380 (!), 3-5 = ~3200, 6-7 = ~3380, "disengaged" = ~4000 (see NOTE above))
* ThinkPad {{R50}} (highest manual level is 3; disengage mode works and reaches much higher RPM)
* ThinkPad {{R50p}} (fan levels RPM: 0 = off, 1-2 = ~3200, 3-5 = ~3500-3600, 6-7 = ~3700-3800, disengaged = ~5300)
* ThinkPad {{R51}} (fan levels RPM: 0 = off, 1-2 = ~3150, 3-5 = ~3350, 6 = ~3750, disengaged = ~5100)
* ThinkPad {{R51e}} (fan levels RPM: 0 = off, 1-2 = ~3300, 3-5 = ~3800, 6 = ~4150, disengaged = ~5100)
* ThinkPad {{R52}} (fan levels RPM: 0 = off, 1-2 = ~3350, 3-5 = ~3650, 6 = ~4250, disengaged = ~5245)
* ThinkPad {{R60}} (fan levels RPM: 0 = off, 1-1 = ~2650, 3-5 = ~3300, 6-7 = ~3950, disengaged = ~4800)
* ThinkPad {{R60e}}
* ThinkPad {{R61i}} (fan levels RPM: 0 = off, 1 = 2689, 2 = 2729, 3 = 3059, 4 = 3047, 5 = 3051, 6 = 3515, 7 = 3468, full-speed/disengaged = 4119~4200)mod.#7650-D7G@+/-2yr.used
* ThinkPad {{T22}}
* ThinkPad {{T23}}
** (low speed = '''~2200''', medium and maximum speed = '''~4800'''; disengaged mode works at '''~5800''')
** (fan levels = ~RPM: 0 = '''0'''; 1,2 = '''~2200'''; 3,4,5,6,7 = '''~4900'''; disengaged,full-speed = '''~6331''')
* ThinkPad {{T30}}
* ThinkPad {{T40}} (fan levels RPM: 1-2 = ~2950, 3-5 = ~3600, 6-7 = ~4050; disengaged = ~5400)
* ThinkPad {{T41}}, {{T41p}} (fan levels RPM: 1-2 = ~2980, 3-5 = ~3500, 6-7 = ~4050; disengaged mode works at ~5100)
* ThinkPad {{T410i}} (fan levels RPM: 0 = off, 1 = ~1950, 2 = ~3575, 3-4 = ~3700, 5-6 = ~3825, 7 = ~4525; full-speed/disengaged = ~5450; only Linux-tested with tpfc0.5)
* ThinkPad {{T42}}, {{T42p}} (fan levels RPM: 1-2 = ~2900, 3-5 = ~3700, 6-7 = ~4700; disengaged mode works at ~5200)
* ThinkPad {{T43}}, {{T43p}} (fan levels RPM: 1-2 = ~3300, 3-5 = ~4100, 6-7 = ~4700; disengaged mode works at ~6450)
* ThinkPad {{T60}} (fan levels RPM: 1-2 = 3000-3100, 3-5 = ~3600, 6-7 = ~4500; disengaged mode works at ~5500)
* ThinkPad {{T61}} (fan levels RPM: 0 = off, 1-2 = ~2980, 3-5 = ~3330, 6-7 = ~3760; disengaged mode works at ~4500)
* ThinkPad {{W500}} (fan levels RPM: 0=off, 1-2 = 1900, 3-5 = ~3000, 6-7 = ~3500; disengaged mode works at ~5100)
* ThinkPad {{W510}} (fan levels RPM: 0=off, 1 = ~2750, 2 = ~3100, 3-5 = ~3500, 6-7 = ~4000; disengaged mode works at ~4585)
* ThinkPad {{X30}} (level 0 = off, low = ~3900, medium = ~4200, maximum = ~4650, disengaged = ~5900)
* ThinkPad {{X31}} (fan levels RPM: 0 = off, 1-2 = ~2850, 3-5 = ~3450, 6 = ~4050, 7 = ~4150; disengaged mode works at ~4975)
* ThinkPad {{X40}}
* ThinkPad {{X41}}
* ThinkPad {{X41T}}
* ThinkPad {{X60}} (fan levels RPM: 7 = ~3700, disengaged ~4700)
* ThinkPad {{X61}} (fan levels RPM: 1-2 = ~3400, 3-5 = ~3800, 6-7 = ~4500, disengaged = ~6700)
* ThinkPad {{X61s}} (fan levels RPM: 0 = off, 1-2 = ~3800, 3-5 = ~4500, 6-7 = ~4800, disengaged = ~4800) (though fancontrol can keep it at 2500rpm...)
* ThinkPad {{X120e}}
* ThinkPad {{Z60t}}, {{Z60m}} (fan levels RPM: 1-2 = ~1700, 3-5 = ~2800, 6-7 = ~3500)
* ThinkPad {{Z61m}}
* Thinkpad {{Z61p}} (fan levels 0-7, auto, disengaged; enable, disable; watchdog (untested))
* Thinkpad {{Edge11}} (fan levels: 0 = off, 1, 2, 3, 7 = full; RPM shown value is around 492 - 503, but should be 1000 - 3000)
Probably other models are supported too (please update this page if you confirm this; maintain some ordering too).

==Models using a different interface==

The following models also work, use a different access method which supported (only) via the {{path|/proc/acpi/ibm/fan}} of [[thinkpad-acpi]]. No need for patching.

* ThinkPad {{600E}}, {{600X}}, {{770E}}, {{770X}} (these use a different fan control interface)

==Unsupported models==

* ThinkPad {{560}} (these models don't have a fan)

Category:X120e

2011-09-30T01:03:05Z

TheAnarcat: link to the debian install instructions

__NOTOC__
{| width="100%"
|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;">
=== ThinkPad X120e ===
This page gives an overview of all ThinkPad X120e related topics.

'''NOTE:''' The [http://shop.lenovo.com/us/products/new-products?ipromoID=sociallogo1001&#x120e X120e] was [http://news.lenovo.com/article_display.cfm?article_id=1398 announced] on January 3, 2011 at CES 2011, with availability beginning in February, 2011.

==== Machine Type ====
* 0596
* 0611
* 0613
* 0622
* 0627

==== Details ====
* CPU
** AMD Fusion E-240 (1.5Ghz, 512KB L2, 1.0GHz FSB) 2.3GT/s single-core Accelerated Processing Unit (APU)
** AMD Fusion E-350 (1.6Ghz, 1MB L2, 1.0GHz FSB) 2.0GT/s dual-core Accelerated Processing Unit (APU)
* Graphics
** AMD Radeon HD 6310
** 11.6" TFT anti-glare display with 1366×768 (HD) resolution with LED backlight
** VGA and HDMI port(s)
* Memory
** two DDR3 SO-DIMM slots (1333MHz modules will run at 1066MHz, according to Data Sheet)
** 2 GB PC3-10600 DDR3 SDRAM 1333MHz SODIMM Memory (1 DIMM) at 1066MHz
** 3 GB PC3-10600 DDR3 SDRAM 1333MHz SODIMM Memory (2 DIMM) at 1066MHz
** 4 GB PC3-10600 DDR3 SDRAM 1333MHz SODIMM Memory (2 DIMM) at 1066MHz (official limit is 4GB; service manual indicates 4GB DIMMs are supported for total of 8GB)
* Storage
** 250GB/320GB Hard Disk Drive (5400RPM)
** 160GB/320GB Hard Disk Drive (7200RPM)
** 128GB Solid State Drive (SSD)
* Networking
** Realtek RTL8111DL GbE PCIe
* Bluetooth on select models
** Bluetooth daughter card (BDC-2.1)
* Wireless
** [[MiniPCI Express slot]] 1 with one of the following:
*** Broadcom Mini PCIe 802.11 a/b/g/n WLAN adapter (FRU 60Y3251)
*** ThinkPad 1x1 b/g/n Wireless LAN Mini-PCI Express Adapter II (FRU 60Y3247 or 60Y3249)
** [[MiniPCI Express slot]] 2 with one of the following:
*** Integrated Mobile Broadband (Gobi 2000 3G with GPS)
*** Integrated China Telecom Mobile Broadband (Huawei EM660)
* three USB ports (one powered)
* 4-in-1 multicard reader
* [[UltraNav]] (TrackPoint / Touchpad combo)
* Audio
** HD audio codec (Conexant CX20582)
** two 1-Watt stereo speakers
** combo headphone/mic jack
* low-light webcam (0.3MP, FPS unknown)
* 3-cell or 6-cell battery
</div>
|style="vertical-align:top" |
[[Image:ThinkPadX100e.jpg|thumb|ThinkPad X100e]]
|}
* [http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles_pdf/63y0640_02.pdf Hardware Maintenance Manual Thinkpad X100e/X120e] (9,436,398 bytes)

==== Reviews ====
* [http://www.engadget.com/2011/01/03/lenovo-thinkpad-x120e-snatches-up-amds-zacate-aims-to-right-al Lenovo ThinkPad X120e snatches up AMD's Zacate, aims to right all of the X100e's wrongs] Engadget.com, 2011-01-03
* [http://www.pcworld.com/article/221084/lenovo_thinkpad_x120e_a_superfast_business_netbook.html Lenovo Thinkpad x120e: A Super-fast Business Netbook] PCWorld.com 2011-1-03
* [http://www.crn.com/news/client-devices/228901645/lenovo-showcases-thinkpad-x120e-notebook-with-amd-fusion-chips.htm;jsessionid=bcyvlMqXRbFPgBuS1bVPIA**.ecappj01 Lenovo Showcases ThinkPad x120e Notebook With AMD Fusion Chips] CRN 2011-01-03
* [http://blog.laptopmag.com/lenovo-unveils-thinkpad-x120e-11-inch-notebook-with-amd-fusion Lenovo Unveils ThinkPad X120e, 11-inch Notebook With AMD Fusion] LAPTOP Magazine Blog 2011-01-03
* [http://nexus404.com/Blog/2011/01/03/ces-2011-lenovo-thinkpad-x120e-ultraportable-notebook-announced-lenovo-thinkpad-x120e-notebook-to-feature-amd-fusion-11-6-display-sub-400-price-point/ CES 2011: Lenovo ThinkPad X120e Ultraportable Notebook Announced [Lenovo ThinkPad X120e Notebook To Feature AMD Fusion, 11.6" Display & Sub $400 Price Point] TFTS 2011-01-03
* [http://www.thinkpadtoday.com/thinkpad-x120-review-superb-lenovo-gets-it-right-on-target-2.htm ThinkPad X120 Review, Superb! – Lenovo gets it right on target] ThinkPadToday 2011-01-03

==== Other resources ====

* [https://www.dei.unipd.it/~pettarin/debian-wheezy-x120e.html Installing Debian Wheezy on Lenovo ThinkPad X120e]

[[Category:X Series]]

Problems with ACPI suspend-to-ram

2008-10-20T00:07:25Z

TheAnarcat:

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.

;Write error:If {{cmdroot|echo mem > /sys/power/state}} shows "write error: Operation not permitted", verify that CONFIG_HOTPLUG_CPU option is enabled in the kernel. [[Software_Suspend_2|Suspend2]] automatically selects this option.

;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 or if the usb hcd modules are still loaded.

;Immediate Resume after Suspend:If a resume starts a few seconds after suspend a reason might be the USB modules. Unload the modules uhci_hcd and ehci_hcd before you suspend. Users of hibernate-scripts add "UnloadModules uhci_hcd ehci_hcd" to {{path|/etc/hibernate/common.conf}}.

;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]].

;Built-in MMC reader:If you have an MMC reader, and the computer hangs when attempting suspend then remove sdhci, mmc_block, and mmc_core modules before suspending.

;Could not power down device <NULL>: error -22:If you have the acpi_cpufreq kernel module loaded, this prevents suspension.

;Immediate Resume, but Suspend "moon" light continues to flash:???

;Hard system lock up:If you are using savagefb, make sure to [[Problem_with_unusable_console|disable the "Console Acceleration" option]] (CONFIG_FB_SAVAGE_ACCEL) in the kernel config. Otherwise, susped-to-RAM may lock up your system such that you must remove the AC adapter and battery to get it to boot again.

;Hard system lock up 2: If you are using a Thinkpad G40 and Ubuntu (this problem experienced on 8.04), you may experience problems with ACPI when opening your laptop lid that freezes the system. You can disable ACPI in your kernel parameters, or modify {{path|/etc/acpi/lid.sh}} to switch to a plain text console on close and back to Gnome/KDE on open (use {{path|/usr/bin/chvt 1}} and {{path|/usr/bin/chvt 7}}, respectively)

;Solid 'moon' but fans still spinning: On a T61p with an nvidia quadro 570M, you might experience a near-complete suspend, with the backlight turned off, unresponsive usb, and a solid 'moon' lit, however system fans are still going. The proprietary nvidia module is to blame. On gentoo, appending "NVreg_Mobile=3" to the 'option' line in /etc/modules.d/nvidia fixed the issue for me. On other distros, look in your module autoloading conf file

==Troubles on resume==
;Blank display on resume:
:When resuming from a suspend-to-ram the display might remain black (on {{X60}}) 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. See also '''System hang on resume''' on this page - which may be potentially mismatched with this one.

;No mouse cursor on resume:
:When resuming from a suspend-to-ram your X cursor might be invisible(on {{X40}}) when using {{path|/sys/power/state}} directly to suspend, they way to fix this is to rerun the post bios code after returning for suspending.
:{{cmdroot|FGCONSOLE<nowiki>=</nowiki>`fgconsole\`}}
:{{cmdroot|chvt 1 && echo -n mem >/sys/power/state}}
:{{cmdroot|vbetool post && chvt 7 && chvt $FGCONSOLE}}

;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 X displays fine. If all of this is true, then adding the kernel option {{bootparm|acpi_sleep|s3_bios,s3_mode}} in your menu.lst or lilo.conf may solve the problem.

;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 {{bootparm|ibm-acpi.experimental|1}} option, you can switch it off on resume by appending the following line to your suspend script: {{cmdroot|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.
:*SATA-based laptops utilize the '''libata layer for disk access''' which does not have fully-working power-management support before Linux kernel 2.6.16 (ata_piix) and 2.6.19 (ahci). 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.
:*Using [[HDAPS]] as a module causes a crash on resume with the Linux kernel 2.6.19 (possibly even earlier versions). This was observed on a {{X41}}. Try unloading the module before suspending.
:*Gnome-power-manager might be using the wrong backend. If you are able to suspend from the commandline with a certain method, make sure the others are not available so that g-p-m doesn't choose the wrong one. For example, if you suspend with {{cmdroot|echo mem > /sys/power/state}}, make sure '''uswsusp''' and '''hibernate''' are uninstalled.

;System hang on resume:
:System hangs immediately upon attempted resume if suspended with USB devices attached to dock. Try using the laptop's own USB ports instead. That fixed the problem for me. Details: https://bugs.launchpad.net/ubuntu/+bug/218760 --[[User:Dave abrahams|Dave abrahams]] 17:45, 28 April 2008 (CEST)
:When system resumes it hangs right after restarting tasks. Strange thing is, that you may be even able to restart your ThinkPad using {{key|ctrl}}{{key|alt}}{{key|del}}, but if you try to blindly exec a command, it will not work, (eg. touch FILE) so it's not only the problem of videocard. This may be fixed by passing {{bootparm|ec_intr|0}} on kernel cmdline. Affected models: {{T20}}, {{T21}} (at least [[2648-46U]] (T20),[[2647-8AG]] (T21)).
:'''Note:''' ''this is resolved in kernel 2.6.20, there is no need to pass the {{bootparm|ec_intr|0}} bootparam anymore (moreover, you are discouraged to use it) See [http://bugzilla.kernel.org/show_bug.cgi?id=6749 revelant kernel bug report]''
:See also [https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/73546 this bug report], I can confirm some strange problems on resume with Bluetooth enabled - my T61 may freeze in a couple of minutes after resuming. This problem is gone as soon as I disable Bluetooth (stop all bluetooth related services and `echo "disable" > /proc/acpi/ibm/bluetooth`).

;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?action=recall&rev=28#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.

;Power Off when suspended laptop is docked
:When T60p is suspended, docking laptop into Advanced Dock immediately turns off laptop and crescent moon sleep indicator LED. Pressing power button initiates cold boot. Also reported by multiple people on thinkpads.com.

;SectorIdNotFound disk errors when laptop is resumed
:The errors look like this:
Oct 14 17:35:02 cacharro kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Oct 14 17:35:02 cacharro kernel: hda: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=115896900, sector=115896900
Oct 14 17:35:02 cacharro kernel: ide: failed opcode was: unknown

:This happens when you have [[Hidden Protected Area]] (HPA) enabled on the hard drive. There is a [http://bugzilla.kernel.org/show_bug.cgi?id=6840 kernel bug report with an unfinished patch] to fix this. This is not fixed as of kernel 2.16.18. Adding {{bootparm|libata.ignore_hpa|1}} to the kernel command line might help.

:Update: This is still occuring here on 2.6.26-1-686 on Debian, even though the bug has been marked as fixed in 2.6.22. I will try disabling the HPA to see if the problem is related... [[User:TheAnarcat|TheAnarcat]] 01:51, 20 October 2008 (CEST)

Problems with ACPI suspend-to-ram

2008-10-19T23:51:27Z

TheAnarcat: /* Troubles on resume */

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.

;Write error:If {{cmdroot|echo mem > /sys/power/state}} shows "write error: Operation not permitted", verify that CONFIG_HOTPLUG_CPU option is enabled in the kernel. [[Software_Suspend_2|Suspend2]] automatically selects this option.

;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 or if the usb hcd modules are still loaded.

;Immediate Resume after Suspend:If a resume starts a few seconds after suspend a reason might be the USB modules. Unload the modules uhci_hcd and ehci_hcd before you suspend. Users of hibernate-scripts add "UnloadModules uhci_hcd ehci_hcd" to {{path|/etc/hibernate/common.conf}}.

;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]].

;Built-in MMC reader:If you have an MMC reader, and the computer hangs when attempting suspend then remove sdhci, mmc_block, and mmc_core modules before suspending.

;Could not power down device <NULL>: error -22:If you have the acpi_cpufreq kernel module loaded, this prevents suspension.

;Immediate Resume, but Suspend "moon" light continues to flash:???

;Hard system lock up:If you are using savagefb, make sure to [[Problem_with_unusable_console|disable the "Console Acceleration" option]] (CONFIG_FB_SAVAGE_ACCEL) in the kernel config. Otherwise, susped-to-RAM may lock up your system such that you must remove the AC adapter and battery to get it to boot again.

;Hard system lock up 2: If you are using a Thinkpad G40 and Ubuntu (this problem experienced on 8.04), you may experience problems with ACPI when opening your laptop lid that freezes the system. You can disable ACPI in your kernel parameters, or modify {{path|/etc/acpi/lid.sh}} to switch to a plain text console on close and back to Gnome/KDE on open (use {{path|/usr/bin/chvt 1}} and {{path|/usr/bin/chvt 7}}, respectively)

;Solid 'moon' but fans still spinning: On a T61p with an nvidia quadro 570M, you might experience a near-complete suspend, with the backlight turned off, unresponsive usb, and a solid 'moon' lit, however system fans are still going. The proprietary nvidia module is to blame. On gentoo, appending "NVreg_Mobile=3" to the 'option' line in /etc/modules.d/nvidia fixed the issue for me. On other distros, look in your module autoloading conf file

==Troubles on resume==
;Blank display on resume:
:When resuming from a suspend-to-ram the display might remain black (on {{X60}}) 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. See also '''System hang on resume''' on this page - which may be potentially mismatched with this one.

;No mouse cursor on resume:
:When resuming from a suspend-to-ram your X cursor might be invisible(on {{X40}}) when using {{path|/sys/power/state}} directly to suspend, they way to fix this is to rerun the post bios code after returning for suspending.
:{{cmdroot|FGCONSOLE<nowiki>=</nowiki>`fgconsole\`}}
:{{cmdroot|chvt 1 && echo -n mem >/sys/power/state}}
:{{cmdroot|vbetool post && chvt 7 && chvt $FGCONSOLE}}

;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 X displays fine. If all of this is true, then adding the kernel option {{bootparm|acpi_sleep|s3_bios,s3_mode}} in your menu.lst or lilo.conf may solve the problem.

;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 {{bootparm|ibm-acpi.experimental|1}} option, you can switch it off on resume by appending the following line to your suspend script: {{cmdroot|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.
:*SATA-based laptops utilize the '''libata layer for disk access''' which does not have fully-working power-management support before Linux kernel 2.6.16 (ata_piix) and 2.6.19 (ahci). 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.
:*Using [[HDAPS]] as a module causes a crash on resume with the Linux kernel 2.6.19 (possibly even earlier versions). This was observed on a {{X41}}. Try unloading the module before suspending.
:*Gnome-power-manager might be using the wrong backend. If you are able to suspend from the commandline with a certain method, make sure the others are not available so that g-p-m doesn't choose the wrong one. For example, if you suspend with {{cmdroot|echo mem > /sys/power/state}}, make sure '''uswsusp''' and '''hibernate''' are uninstalled.

;System hang on resume:
:System hangs immediately upon attempted resume if suspended with USB devices attached to dock. Try using the laptop's own USB ports instead. That fixed the problem for me. Details: https://bugs.launchpad.net/ubuntu/+bug/218760 --[[User:Dave abrahams|Dave abrahams]] 17:45, 28 April 2008 (CEST)
:When system resumes it hangs right after restarting tasks. Strange thing is, that you may be even able to restart your ThinkPad using {{key|ctrl}}{{key|alt}}{{key|del}}, but if you try to blindly exec a command, it will not work, (eg. touch FILE) so it's not only the problem of videocard. This may be fixed by passing {{bootparm|ec_intr|0}} on kernel cmdline. Affected models: {{T20}}, {{T21}} (at least [[2648-46U]] (T20),[[2647-8AG]] (T21)).
:'''Note:''' ''this is resolved in kernel 2.6.20, there is no need to pass the {{bootparm|ec_intr|0}} bootparam anymore (moreover, you are discouraged to use it) See [http://bugzilla.kernel.org/show_bug.cgi?id=6749 revelant kernel bug report]''
:See also [https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/73546 this bug report], I can confirm some strange problems on resume with Bluetooth enabled - my T61 may freeze in a couple of minutes after resuming. This problem is gone as soon as I disable Bluetooth (stop all bluetooth related services and `echo "disable" > /proc/acpi/ibm/bluetooth`).

;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?action=recall&rev=28#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.

;Power Off when suspended laptop is docked
:When T60p is suspended, docking laptop into Advanced Dock immediately turns off laptop and crescent moon sleep indicator LED. Pressing power button initiates cold boot. Also reported by multiple people on thinkpads.com.

;SectorIdNotFound disk errors when laptop is resumed
:The errors look like this:
Oct 14 17:35:02 cacharro kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Oct 14 17:35:02 cacharro kernel: hda: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=115896900, sector=115896900
Oct 14 17:35:02 cacharro kernel: ide: failed opcode was: unknown

:This happens when you have [[Hidden Protected Area]] (HPA) enabled on the hard drive. There is a [http://bugzilla.kernel.org/show_bug.cgi?id=6840 kernel bug report with an unfinished patch] to fix this. This is not fixed as of kernel 2.16.18. Adding {{bootparm|libata.ignore_hpa|1}} to the kernel command line might help.

:Update: This is still occuring here on 2.6.26-1-686 on Debian, even though the bug has been marked as fixed in 2.6.22. I will try using the libata.ignore_hpa trick. [[User:TheAnarcat|TheAnarcat]] 01:51, 20 October 2008 (CEST)

How to get special keys to work

2007-07-16T16:08:21Z

TheAnarcat: /* Window Managers */

==Overview==
The following table gives an overview over the special keys found on ThinkPads and what is needed to make them work.
{| {{prettytable}}
! key !! standard function{{footnote|1}} !! tools supporting key{{footnote|2}} !! configurability{{footnote|3}} !! remarks
|-
| {{key|Fn}} || - || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || on release without completed key combination
|-
| {{key|Fn}}{{key|F1}} || - || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| {{key|Fn}}{{key|F2}} || lock screen || [[#ibm-acpi events|ibm-acpi]] || full || in models from T/X/Z 60 onwards
|-
| {{key|Fn}}{{key|F3}} || blank screen || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full ||
|-
| {{key|Fn}}{{key|F4}} || suspend to ram || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full || may generate ACPI event when not enabled in the ibm-acpi hotkey mask
|-
| {{key|Fn}}{{key|F5}} || switch bluetooth || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full || in models starting from 2002
|-
| {{key|Fn}}{{key|F6}} || - || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| {{key|Fn}}{{key|F7}} || switch display || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]], [[#tpb configuration|tpb]] || additional actions ||
|-
| {{key|Fn}}{{key|F8}} || toggle display expansion || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]], [[#tpb configuration|tpb]] || additional actions ||
|-
| {{key|Fn}}{{key|F9}} || eject from dock || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full ||
|-
| {{key|Fn}}{{key|F10}} || - || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| {{key|Fn}}{{key|F11}} || - || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| {{key|Fn}}{{key|F12}} || hibernate || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full || may generate ACPI event when not enabled in the ibm-acpi hotkey mask
|-
| {{key|Fn}}{{key|Home}} / {{key|Fn}}{{key|Pos1}} || brightness up || [[#ibm-acpi events|ibm-acpi]], [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{key|Fn}}{{key|End}} || brightness down || [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{key|Fn}}{{key|PageUp}} || toggle thinklight || [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{key|Fn}}{{key|Space}} || toggle zoom || [[#tpb configuration|tpb]], [[KMilo]] || full ||
|-
| {{key|Fn}}{{key|Ins}} || - || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| {{key|Fn}}{{key|Del}} || - || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| {{key|Fn}}{{key|Backspace}} || - || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| {{key|NumLock}} || - || [[#xmodmap configuration|xmodmap]] || make working ||
|-
| {{key|Windows}} || - || [[#xmodmap configuration|xmodmap]] || remapping ||
|-
| {{ibmkey|Access IBM|#495988}} or {{ibmkey|ThinkPad|#494949}} || help application || [[#tpb configuration|tpb]], [[KMilo]] || full ||
|-
| {{ibmkey|Home|#494949}} || open web browser || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]], [[KMilo]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Search|#494949}} || open search application || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]], [[KMilo]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Mail|#494949}} || open mail application || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]], [[KMilo]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Favorites|#494949}} || open favorites || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Reload|#494949}} || reload web page || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Abort|#494949}} || abort loading page || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Backward|#494949}} || previous page || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || ext. keyboards and ThinkPads starting from 2002
|-
| {{ibmkey|Forward|#494949}} || next page || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || ext. keyboards and ThinkPads starting from 2002
|-
| {{ibmkey|Volume up|#494949}} || volume up || [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{ibmkey|Volume down|#494949}} || volume down || [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{ibmkey|Volume mute|#494949}} || mute volume || [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{ibmkey|Play/Pause|#494949}} || start/pause playback || [[#xmodmap configuration|xmodmap]] || full || {{X60s}} (Fn+Arrow Down)
|-
| {{ibmkey|Stop|#494949}} || stop playback || [[#xmodmap configuration|xmodmap]] || full || {{X60s}} (Fn+Arrow Up)
|-
| {{ibmkey|Next|#494949}} || play next || [[#xmodmap configuration|xmodmap]] || full || {{X60s}} (Fn+Arrow Right)
|-
| {{ibmkey|Previous|#494949}} || play previous || [[#xmodmap configuration|xmodmap]] || full || {{X60s}} (Fn+Arrow Left)
|-
| {{ibmkey|Power|#494949}} || shutdown || [[#ibm-acpi events|ibm-acpi]] || full || triggered on pressing 3secs, but notebook goes off on 5sec press
|-
| Display lid || blank screen || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| Ultrabay lid || announce ultrabay change || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| Dock eject || eject from dock || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| {{ibmkey|Tablet power|#494949}} || shutdown || [[#ibm-acpi events|ibm-acpi]] || full || triggered on pressing 3secs, but notebook goes off on 5sec press
|-
| {{ibmkey|Tablet orientation|#494949}} || rotates screen || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet shortcut|#494949}} || shortcut menu || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet Esc|#494949}} || esc key || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet Enter|#494949}} || enter key || [[#mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet Up|#494949}} || up key || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet Down|#494949}} || down key || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet (unlabeled)|#494949}} || down key || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|}

==Triggering key events==
===ibm-acpi events===
Some of the following events require a {{cmdroot|echo enable,0xffff >/proc/acpi/ibm/hotkey}} in order to make acpi able to get information on them. These events can be used to [[How to configure acpid|configure acpid]].

{| {{prettytable}}
|+ events triggered by [[ibm-acpi]] for {{path|/etc/acpi/events}} files.
! key !! event
|-
| {{key|Fn}}{{key|F1}} || ibm/hotkey HKEY 00000080 00001001
|-
| {{key|Fn}}{{key|F2}} || ibm/hotkey HKEY 00000080 00001002
|-
| {{key|Fn}}{{key|F3}} || ibm/hotkey HKEY 00000080 00001003
|-
| {{key|Fn}}{{key|F4}} || ibm/hotkey HKEY 00000080 00001004
|-
| {{key|Fn}}{{key|F5}} || ibm/hotkey HKEY 00000080 00001005
|-
| {{key|Fn}}{{key|F6}} || ibm/hotkey HKEY 00000080 00001006
|-
| {{key|Fn}}{{key|F7}} || ibm/hotkey HKEY 00000080 00001007
|-
| {{key|Fn}}{{key|F8}} || ibm/hotkey HKEY 00000080 00001008
|-
| {{key|Fn}}{{key|F9}} || ibm/hotkey HKEY 00000080 00001009
|-
| {{key|Fn}}{{key|F10}} || ibm/hotkey HKEY 00000080 0000100a
|-
| {{key|Fn}}{{key|F11}} || ibm/hotkey HKEY 00000080 0000100b
|-
| {{key|Fn}}{{key|F12}} || ibm/hotkey HKEY 00000080 0000100c
|-
| {{key|Fn}}{{key|Backspace}} || ibm/hotkey HKEY 00000080 0000100d
|-
| {{key|Fn}}{{key|Ins}} || ibm/hotkey HKEY 00000080 0000100e
|-
| {{key|Fn}}{{key|Del}} || ibm/hotkey HKEY 00000080 0000100f
|-
| {{key|Fn}}{{key|Home}}/{{key|Fn}}{{key|Pos1}} || ibm/hotkey HKEY 00000080 00001010
|-
| {{ibmkey|Power|#494949}} || 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
|-
| Dock eject || ibm/dock GDCK 00000003 00000001
|-
| Wireless switch || ibm/hotkey HKEY 00000080 00007000
|}

By disassembling and editing the DSDT, more events can be added. HKEY events are triggered by calls to the MKHQ function, e.g. <tt>\_SB.PCI0.LPC.EC.HKEY.MHKQ(0Ã—1007)</tt> will trigger "ibm/hotkey HKEY 00000080 00001007". Most of these can be found in <tt>_Qxx</tt> methods within the DSDT, which are executed on embedded controller events, e.g. _Q10 is triggered by pressing Fn-F7. You can add a call to MKHQ into an existing <tt>_Qxx</tt> method to get it recognized by ibm-acpi as well as creating new <tt>_Qxx</tt> methods, which if you're lucky will correspond to an EC event that IBM never used (e.g. A 770 will send Fn-Home/End/PgUp/PgDn to ibm-acpi if hacked in this fashion). For example, [http://www.wormnet.eu/ibm-g40/morebuttons.dsl this is a modified block of DSDT for a G40].

=== Pure ACPI events ===

A few keys can generate ACPI events of their own on certain ThinkPads, as long as they are masked off in the ibm-acpi hotkey's mask (or the hotkey feature is disabled in ibm-acpi).

If you want the ThinkPad's BIOS and ACPI methods to know about these keys being pressed, you probably want to leave them masked out from ibm-acpi, and use their non-HKEY events listed below, instead.

{| {{prettytable}}
|+ events triggered by ACPI when hotkey is masked out or disabled.
! key !! event
|-
| {{key|Fn}}{{key|F4}} || button/sleep SLPB 00000080 00000001
|-
| {{key|Fn}}{{key|F12}} || ibm/hotkey HKEY 00000080 0000100c
|}

===tpb configuration===
{| {{prettytable}}
|+ configuration keywords for [[tpb]] (to put in {{path|/etc/tpbrc}})
! key !! config keyword
|-
| {{ibmkey|Access IBM|#495988}} or {{ibmkey|ThinkPad|#494949}} || THINKPAD
|-
| {{ibmkey|Home|#494949}} || HOME
|-
| {{ibmkey|Search|#494949}} || SEARCH
|-
| {{ibmkey|Mail|#494949}} || MAIL
|-
| {{ibmkey|Favorites|#494949}} || FAVORITES
|-
| {{ibmkey|Reload|#494949}} || RELOAD
|-
| {{ibmkey|Abort|#494949}} || ABORT
|-
| {{ibmkey|Backward|#494949}} || BACKWARD
|-
| {{ibmkey|Forward|#494949}} || FORWARD
|-
| {{key|Fn}} || FN
|-
| {{key|Fn}}{{key|Space}} || CALLBACK (zoom on/off)
|-
| {{key|Fn}}{{key|PageUp}} || CALLBACK (thinklight on/off)
|-
| {{key|Fn}}{{key|F7}} || CALLBACK (display lcd/crt/both)
|-
| {{key|Fn}}{{key|F8}} || CALLBACK (expand on/off)
|-
| {{key|Fn}}{{key|Home}} / {{key|Fn}}{{key|Pos1}} || CALLBACK (brightness <percent>)
|-
| {{key|Fn}}{{key|End}} || CALLBACK (brightness <percent>)
|-
| {{ibmkey|Volume up|#494949}} || CALLBACK (volume <percent>)
|-
| {{ibmkey|Volume down|#494949}} || CALLBACK (volume <percent>)
|-
| {{ibmkey|Volume mute|#494949}} || 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 <tt>XEVENTS OFF</tt> in your {{path|/etc/tpbrc}}.
You can use an appropriate executable to [[How to inject fake keystrokes|inject fake keystrokes]].

For Debian users, tpb is started from {{path|/etc/X11/Xsession.d/90tpb}}.

'''Sound Button configuration'''

''Note: Tested on T60p with Ubuntu 6.06 LTS''

Most Thinkpads have a hardware sound mixer, thus the volumes buttons should work without configuration. However, this change is not reflected in the software mixer. tpb has a switch to enable software mixer support via OSS. The manual recommends this only for devices without a hardware mixer, but it also works for other hadware mixer enabled devices, even with the ALSA system. Just put MIXER ON in your {{path|/etc/tpbrc}} file and you can see the effect immediately in any ALSA mixer (e.g. kmix). For this to work you need write permissions to {{path|/dev/nvram}}.

''Note: Tested on X21 with Ubuntu 6.06 LTS''

On the ThinkPad X21 (and maybe some other older models) ACPI causes problems with tpb. On an X21 using acpi the volume buttons would work occasionally, and the OSD for tpb functions would rarely work. If a volume buttons was pressed too often, sometimes the computer would enter a low power (unplugged state) and would require a reboot. The solution is to use APM instead of ACPI. Instructions can be found in [[How_to_make_APM_work]].

===KMilo configuration===
The programs to be executed by [[KMilo]] are configured via the KDE Control Center (<tt>kcontrol</tt>), under <tt>System Administration --> IBM Thinkpad Laptop</tt>. Note that you can use appropriate commands to [[How to inject fake keystrokes|inject fake keystrokes]].

===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.

To discover the keycode that a certain keypress produces, use the tool {{cmduser|xev}}

Usually you should write your keycode-keysym associations into the file {{path|~/.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 {{path|~/.Xmodmap}} lines for our purpose are in the form of
keycode <keycode> = <keysym>

Load the assocation using the command

{{cmduser|xmodmap ~/.Xmodmap}}

(some configurations do this automatically upon X startup).

The following table shows the keycodes generated by the ThinkPad special keys and sensible keysyms to assign them to.
{| {{prettytable}}
|+ keycodes and recommended keysyms
! key !! keycode !! keysym
|-
| {{ibmkey|Access IBM|#495988}} or {{ibmkey|ThinkPad|#494949}} || 159 || XF86LaunchA
|-
| {{ibmkey|Backward|#494949}} || 234 || XF86Back or F19
|-
| {{ibmkey|Forward|#494949}} || 233 || XF86Forward or F20
|-
| {{ibmkey|Play/Pause|#494949}} || 162 || XF86AudioPlay
|-
| {{ibmkey|Stop|#494949}} || 164 || XF86AudioStop
|-
| {{ibmkey|Next|#494949}} || 153 || XF86AudioNext
|-
| {{ibmkey|Previous|#494949}} || 144 || XF86AudioPrev
|-

| {{ibmkey|Home|#494949}} || 178 || XF86HomePage
|-
| {{ibmkey|Search|#494949}} || 229 || XF86Search
|-
| {{ibmkey|Mail|#494949}} || 236 || XF86Mail
|-
| {{ibmkey|Favorites|#494949}} || 230 || XF86AddFavorite or XF86Favorites
|-
| {{ibmkey|Reload|#494949}} || 231 || XF86Reload
|-
| {{ibmkey|Abort|#494949}} || 232 || XF86Stop
|-
| {{key|Fn}} || 227 || F35
|}

Note: You can also using xkeycaps(a tool graphically display and edit the X keyboard mapping) to generate proper .Xmodmap.

Note: if you are running [[tpb]] you might need to add the line <tt>XEVENTS=off</tt> into your tpbrc to stop it from grabbing the key events and allow them to get through to X instead. See [[http://www.thinkwiki.org/wiki/Tpb]] for more detailed instruction on how to use tpb and xmodmap.

Note: XF86Forward and XF86Back do not work correctly in Firefox. You may want to map them to F19 and F20 instead if you use Firefox.

=====Enabling the Windows and Menu Keys=====
On some systems the Windows and Menu keys may not be recognized. You can enable then by
making the following changes:

keycode 115 = F13
keycode 227 = F35

F13 and F35 are used for the Windows and and Menu keys respectively. Labelling keycpode 227 as "Menu" may conflict with the right-mouse-click event.

=====Using Caps Lock as Super L (Windows key)=====
You can easily use Caps Lock as Win key by adding the following in your ~/.Xmodmap:
! No Caps Lock
clear lock
! Caps Lock as Win key
add mod4 = Caps_Lock
=====NumLock=====
On the ThinkPad {{600}}, {{T20}}, {{T21}}, {{T22}}, {{T30}}, {{X20}}, {{X21}}, {{X31}}, {{T43}}, {{R51}}, {{R52}} and possibly other models, X does not recognize the keycode for {{key|NumLk}} = {{key|Shift}}+{{key|ScrLk}}. To fix this, add the following to {{path|~/.Xmodmap}} in your home directory or {{path|/etc/X11/Xmodmap}} and run <tt>xmodmap</tt>, ex: <tt>xmodmap ~/.Xmodmap</tt>:
keycode 77 = Num_Lock

===Mapping keys with setkeycodes===
You can use the setkeycodes command to remap certain keys. I.e. you can use {{cmdroot|setkeycodes 6e 109 6d 104 69 28 6b 1}} to map the Tablets Up and Down keys to the standard PageUp and PageDown keys and Tablet Escape and Enter to their respective keys.

The following table shows the keycodes generated by the ThinkPad keys.
{| {{prettytable}}
|+ keycodes
! key !! keycode
|-
| {{ibmkey|Tablet orientation|#494949}} || 0x6d
|-
| {{ibmkey|Tablet Shortcut|#494949}} || 0x6e
|-
| {{ibmkey|Tablet Esc|#494949}} || 0x6b
|-
| {{ibmkey|Tablet Enter|#494949}} || 0x69
|-
| {{ibmkey|Tablet Up|#494949}} || 0x68
|-
| {{ibmkey|Tablet Down|#494949}} || 0x6c
|-
| {{ibmkey|Tablet (unlabeled)|#494949}} || 0x67
|}

==Example Applications==
===Web Browsers===
====Firefox====

There are various ways to assign actions to the browser keys. The easiest way is to install [http://mozilla.dorando.at/keyconfig.xpi keyconfig.xpi] from http://mozilla.dorando.at, which adds a menu entry Tools->Keyconfig. Then you can assign any action you want to the F19/F20 keys (you still need to create {{path|~/.Xmodmap}} as explained above).

The remaining discussion gives you various more complicated ways to achieve the same thing.
To have firefox make use of the browser keys you need to modify one of its files{{footnote|4}}.
To do this you will first need to extract it from the {{path|browser.jar}} archive. Do...

:{{cmdroot|cd <firefox-directory>/chrome}}<br />
:{{cmdroot|unzip browser.jar}}

The file of interest is {{path|content/browser/browser.xul}}. Edit it {and don't forget to make a backup copy first}...
:{{cmdroot|vi content/browser/browser.xul}}

Look for the '''<keyset id="mainKeyset">''' section and add the following lines within...
<key id="goBackKb" keycode="VK_F19" command="Browser:Back" />
<key id="goForwardKb" keycode="VK_F20" command="Browser:Forward" />

The Command you need for Next Tab
<key id="goBackTabKb" keycode="VK_F19" oncommand="gBrowser.mTabContainer.advanceSelectedTab(-1)" />
For the Previous Tab
<key id="goForwardTabKb" keycode="VK_F20" oncommand="gBrowser.mTabContainer.advanceSelectedTab(1)" />

Now save the file and repackage the {{path|browser.jar}} archive...
:{{cmdroot|zip -rD0 browser.jar content/browser/}}

That's it.

{{HINT|For Firefox 2.0, just edit <firefox-directory>/chrome/browser/content/browser/browser.xul}}

{{HINT|Outdated: Another interesting Page on Firefox is http://dqd.com/~mayoff/notes/thinkpad/dqdnavkeys/ It uses different key mappings (F19 resp. F20) but a ready [http://dqd.com/~mayoff/notes/thinkpad/dqdnavkeys/dqdnavkeys-1.2.xpi .xpi] is provided which is pretty comfortable. However, this xpi file does not install on Firefox 1.5. or later.}}

{{HINT|Outdated: You can also use the [http://extensionroom.mozdev.org/more-info/keyconfig keyconfig] extension to configure custom keys. This extension works with Firefox 1.5 but not with Firefox 2.0. The Command you need for Next Tab is gBrowser.mTabContainer.advanceSelectedTab(1,true); For Previous Tab its gBrowser.mTabContainer.advanceSelectedTab(-1,true); }}.

====Konqueror====
KDE allows you set key mappings for KDE applications (Go to KMenu > System > Control Center > Regional & Accessibility > Keyboard Shortcuts). By default (at least in KDE 3.5), XF86Back and XF86Forward are set as alternatives to Alt-Left and Alt-Right, and are mapped to KDE Back and Forward navigation actions.

If you use Konqueror as your only browser, you only need to set up {{path|~/.Xmodmap}} as described [[#xmodmap configuration|above]] to assign ThinkPad back/forward keys to the symbols XF86Back/XF86Forward. This also make these keys work for other KDE applications such as Quanta Plus, KPackage and so on (not all KDE applications honor this setting, e.g. KDE help system doesn't).

If you want to use Firefox, however, the above settings do not work. You will have to map ThinkPad back/forward keys to F19/F20 as described [[#Firefox|above]], and change KDE navigation key settings to use F19/F20 instead of the default.

====Opera====
However this isn't a simple configration file, you can set your browser manually.<br />
Go to <i>Tool > Settings > Mouse and keyboard > Keyboard settings > Edit > Browser Window</i>. There add F19 - Back and F20 - Forward. Now you can surf using your TP keys ;-)

===Window Managers===
====fvwm====
To get the {{ibmkey|Forward|#494949}} and {{ibmkey|Backward|#494949}} keys to cycle through pages in the virtual desktop, add this to your {{path|~/.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.

====fluxbox====
To get the keys to cycle through pages in the virtual desktop, add this to your {{path|~/.fluxbox/keys}}:
None F19 :PrevWorkspace
None F20 :NextWorkspace

====pekwm configuration====
You can make the two browser keys switch workspaces in pekwm, by adding the following two lines to the {{path|~/.pekwm/keys}} file:
KeyPress = "Mod1 XF86Back" { Actions = "GoToWorkspace prev" }
KeyPress = "Mod1 XF86Forward" { Actions = "GoToWorkspace next" }

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

====IceWM====
To make IceWM cycle workspaces using the {{ibmkey|Forward|#494949}} and {{ibmkey|Backward|#494949}} keys, change these two options in {{path|~/.icewm/preferences}} (Provided you assigned keysyms F19 and F20 with xmodmap):
# "Previous workspace" shortcut
KeySysWorkspacePrev="F19"
# "Next workspace" shortcut
KeySysWorkspaceNext="F20"

==== Gnome/metacity ====

Follow the [https://wiki.ubuntu.com/Keybindings Ubuntu guide].

===Other Uses===
====Console tools configuraton====
To make the {{ibmkey|Forward|#494949}} and {{ibmkey|Backward|#494949}} keys useful in console, add this to your keymap ({{path|/etc/console/boottime.kmap.gz}} in {{Debian}}):
keycode 158 = Decr_Console
keycode 159 = Incr_Console

Alternatively you can load this script (perhaps on system startup) to enable Backward/Forward button console (VT) switch:

#!/bin/sh
echo keycode 158 = Decr_Console | loadkeys
echo keycode 159 = Incr_Console | loadkeys

It should work with any distro.

==External Sources==
*[http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-51537 IBMs page on configuring the ThinkPad buttons (ThinkPad, Access IBM, Mail, Search, and Home buttons) under Linux]
*[http://dqd.com/~mayoff/notes/thinkpad/dqdnavkeys/ Rob Mayoffs page on using IBM Keyboard Navigation Keys in Linux Mozilla and Firefox]
*[http://snarfed.org/space/thinkpad+keys+in+firefox Ryan Barretts blog article about using the browser keys in Firefox]
*[http://chaotika.org/~bluesceada/?page=soft&sub=thinkpad#acpibutn DennisG's help to get the ibm-acpi buttons do useful things] on a {{Z61e}} and possibly {{Z61m}}, {{Z61t}} and {{Z61p}}

{{footnotes|
#Note that the associated functionality for Fn-F* key combinations is not consistent amongst all ThinkPads. We are maintaining [[Default meanings of special keys|a table of associated meanings]].
#if there are more than one tool listed, one is sufficient
#'full' means you can completely reassign any action to be triggered by the key, 'additional actions' means you can trigger actions in addition to the standard function of the key, which can not be changed.
#Thanks go to Ryan Barrett for writing the [http://snarfed.org/space/thinkpad+keys+in+firefox little howto] on [http://snarfed.org/space/start his blog].
}}

ThinkPad X3 UltraBase

2007-07-16T15:38:20Z

TheAnarcat:

{| cellspacing="0" cellpadding="2" border="0"
| style="vertical-align:top;" | __TOC__
[[image:UltraBaseX3.gif|UltraBase X3]]
| 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;">
== IBM UltraBase X3 ==
The IBM UltraBase X3 is a portable dock for the X30, X31 and X32 ThinkPads providing extra ports as well as a bay for an optical drive and a set of stereo speakers. Containing a full featured [[UltraBay|UltraBay Plus]] slot, it provides flexibility in drive choice as well as the option of a secondary battery for extended working time on the road. The Ultrabase X3 also features a battery slot on the underside that accepts the same battery as your X30 Series ThinkPad. The UltraBase X3 doesn't provide a second docking port as the original [[UltraBase]] did, hence you can't dock the UltraBase to any of the other docking solutions.

=== Features ===
* Passthrough ports:
** Ethernet (RJ45)
** Modem (RJ11)
** USB
** [[VGA Port|VGA]]
** [[Serial Port|Serial (DB9-M)]]
** [[Parallel Port|Parallel (DB25-F)]]
** [[PS/2 Port|Combined PS/2 Mouse + Keyboard]]
* [[UltraBay|Ultrabay Plus]]
* Stereo speakers
* Kensington security hole
* Battery Slot (For Second X30 Series Battery)

===Pros & Cons===
* Positives: Expansion capability, portable
* Negatives: makes the ThinkPad quite thick, no extra docking port
* Compatibility: {{X30}}, {{X31}}, {{X32}}
* Warranty: Three Years
</div>
|}

==UltraBay Plus==
The [[UltraBay|UltraBay Plus]] slot in this dock is a full featured one and supports hot swapping with all UltraBay Plus and UltraBay 2000 drives. You can also feed it with the UltraBay Plus battery pack to extend the overall battery life time.

== Kernel support ==

In general, see [[How_to_hotswap_the_UltraBase]] and [[How_to_hotswap_UltraBay_devices]].

This can be problematic under Debian, as the default kernel (2.6.18) do not support the IBM docks by default, as the IBM_DOCK and DOCK methods are not compatible. This is not a problem with 2.6.22 for some reason. Under 2.6.18, you need to recompile the Linux kernel with CONFIG_ACPI_IBM_DOCK enabled, and CONFIG_ACPI_DOCK disabled. You also need to hook a few scripts into the acpi events system.

ibm-dock.sh:
#!/bin/sh

# acknowledge docking with the dockstation
echo dock > /proc/acpi/ibm/dock

ibm-undock.sh:
#!/bin/sh

# prepare the laptop for undocking with the dockstation

echo undock > /proc/acpi/ibm/dock

events/ibm-dock:

event=ibm/dock GDCK 00000000 00000003
action=/etc/acpi/ibm-dock.sh

events/ibm-undock:

event=ibm/dock GDCK 00000003 00000001
action=/etc/acpi/ibm-undock.sh

2.6.22-rc2 actually works without a flaw, without the above modifications, provided that the "bay" and "dock" modules are loaded at boot time.

Talk:Problem with display remaining black after resume

2007-07-16T03:22:07Z

TheAnarcat: /* X31 */

== T43 with Intel Graphics Media Accelerator ==

It seems there are several possible solutions for this issue:

I tried 'Option "VBERestore" "yes"' as hinted in X41 section below, and this worked for me on my T43/915GM.

My T43 (1871-FYG) with Intel 915GM is also affected by the problem and the 'ATI' sollution with
acpi_sleep=s3_bios works. Please consider updating the page (I don't dare to do it myself).

== From my experience, this does not work with TP R50e. ==

If you want to be able to resume, you need :
* To start from a VT
* No option acpi_sleep
* to save the PCI state like:
cat /proc/bus/pci/00/02.0 > /var/cache/video.config
* Once you get back, restore it:
cat /var/cache/video.config > /proc/bus/pci/00/02.0

However, the X screen is not clean after the restore, so this is not very useable...

== The comment on R50e ==

There is a comment at the end of the page on R50e, saying that you should switch to console first, and look at a page to learn how to do this.

However. it seems to me that the given script already does it. Should the comment be removed?
----
The scripts are different. However, if you can approve that the solution provided on this page resolves the problem, please remove the footnote.

[[User:Wyrfel|Wyrfel]] 14:46, 17 Oct 2005 (CEST)
----
On my R50e, the script on this page works fine, while the one linked in the footnote quickly wakes up from sleep.

[[User:Thisnukes4u|Thisnukes4u]] 19:39, 1 Jan 2006 (CET)

== Problems with R51 and Intel Graphics ==

The problems described on the page occur intermittently
with an Intel Graphics card on an R51. Here is what happens:

1. One some occassions everything seems to work fine.

2. On other occassions the screen looks OK but the some plane seems to have vanished. New text on the screen overwrites instead of replaces prior text. The "standard" pattern disappears from the X background.

3. On yet other occassions the X server dies and comes out "blank" in the mode (2) above.

4. The above problems appear only with the "i810" driver. The "vesa" driver works fine. Moreover, if the machine is "suspend-to-disk"ed then the problem disappears on resumption once the X server is killed and re-started.

But for 1 and 4 above I would have given up and either avoided suspend to ram altogether or used vesa mode---as it stands the problem is tantalising.

Kapil kapil at imsc dot res dot in

== X30 ==

The {{bootparm|acpi_sleep|s3_bios}} boot parameter did the trick, no additional scripts required (Ubuntu feisty).

== X31 ==

In addition to the s3_bios trick, i needed to uninstall the uswsusp and hibernate packages. I've put all the details in the [[Category_talk:X31|X31 talk page]]. [[User:TheAnarcat|TheAnarcat]] 18:50, 14 July 2007 (UTC)

== X40 with an Intel 855GM Integrated Graphics Device ==

I used the {{bootparm|acpi_sleep|s3_bios}} boot parameter and the following ACPI script:

#!/bin/sh
set -e

vt=`fgconsole`
chvt 12
echo mem >/sys/power/state
vbetool post
chvt $vt

The {{bootparm|acpi_sleep|s3_bios}} boot parameter alone did not fix things, and neither did saving and restoring the information from {{path|/proc/bus/pci/00/02.0}}.

== X41 with an Intel 915GM Integrated Graphics Device ==

It works with the {{bootparm|acpi_sleep|s3_bios,s3_mode}} boot parameter. Resume works great, both on the VESA console and in X.

:Interesting--that didn't work for me. I needed to do several things to get it to work. First, I used s3_bios, but not s3_mode. Secondly, I had to edit resume_video() in /etc/pm/functions-intel to comment out the VBE post and restore. Those two changes made it functional, but the improper lid state in the HAL daemon caused it to go back to sleep just as soon as it resumed upon the lid opening, so I added a HAL restart to the front end of /etc/acpi/actions/sleep.sh. This means that I have to restart gnome-power-manager, too. I haven't yet figured out a way to do that in sleep.sh; currently I do it manually. I'll post this to the main page soon, unless I hear comments to the contrary. [[User:BrianTung|BrianTung]] 19:52, 30 April 2006 (CEST) (fixed a little)

:(gsaito): I used the {{bootparm|acpi_sleep|s3_bios,s3_mode}} boot parameter and it worked perfectly, entering Suspend to RAM and resuming perfectly. No more blank screens after resuming. No need for any other change as described above, at least in my case. I also have an X41 with Intel 915GM graphics adapter. I use OpenSUSE v.10.0.

I read the edit by Uberpenguin and tried the stated fix. No go: The next time I pulled out the adapter after a resume--boom, the machine goes straight back to sleep again. Evidently, the suggested workaround does not work on all machines. [[User:BrianTung|BrianTung]] 19:54, 22 June 2006 (CEST)

Yesterday I tried adding 'Option "VBERestore" "yes"' to the Driver section in xorg.conf on my X41 and it works great. I used no boot-params or anything else. The distribution is OpenSuSE 10.1. If anyone can acknowledge to my experience, I'd like to add this solution to the articles in this wiki. [[User:Sirmoloch|Sirmoloch]] 11:49, 4 July 2006 (CEST)

== Z60t with an Intel 915GM Integrated Graphics Device (PCI Express) ==

It works with the {{bootparm|acpi_sleep|s3_bios}} boot parameter. Here is the script I use (gentoo). Note: stopping and starting WiFi is not necessary to resume, but it is dead on resume until restarted and the module is reloaded. This is on a 2.6.15.4 kernel with framebuffer console support. The blinking led thing is a nice touch I got from the hibernate-scripts package - it blinks the sleep led (moon icon) until the sleep or resume cycle is finished.

The 'vbetool vbemode get/set' commands are for saving and restoring the console text mode - otherwise the screen becomes garbled.

#!/bin/bash

# blink sleep led (if ibm_acpi is installed)
echo 7 blink > /proc/acpi/ibm/led

# change to console 10 (unused?)
FGCONSOLE=`fgconsole`
chvt 10

# save video state
VBEMODE=`vbetool vbemode get`
cat /proc/bus/pci/00/02.0 > /tmp/video_state

# sync filesystem
sync

# sync hardware clock with system time
hwclock --systohc

# stop networking (atheros chipset)
/etc/init.d/net.ath0 stop
rmmod ath_pci

# go to sleep
sleep 2 ; echo -n 3 > /proc/acpi/sleep

# blink sleep led
echo 7 blink > /proc/acpi/ibm/led

# restore system clock
hwclock --hctosys

# restore video state
vbetool vbemode set $VBEMODE
cat /tmp/video_state > /proc/bus/pci/00/02.0

# change back to X
chvt $FGCONSOLE

# restart networking
modprobe ath_pci
/etc/init.d/net.ath0 start

# clean up behind us
rm /tmp/video_state
echo 7 off > /proc/acpi/ibm/led

== Fedora Core 5 ==

The vbetool on the article page worked great for me, but NetworkManager would not bring the wireless interface back up. I had to add "ath_pci" to the SUSPEND_MODULES variable in /etc/sysconfig/pm.

== R50e 1834-S3G in Debian Etch ==

I found it necessary to add a {{cmdroot|clear}} to the script before {{cmdroot|chvt}} 'ing back to VT7 after wakeup. If I didn't, I would end up with a 99% black corrupted screen in X.
[[User:Ris|Ris]] 18:38, 30 October 2006 (CET)

== Work-arounds for X60s / Intel 950 ==

The page identifies X60s's as having problems with blank display on resume (and I can confirm), but doesn't suggest a work-around. (Nor are there any obvious fixes for this boxes Intel 950 graphics card.) Has anyone gotten it working? [[User:Johnh|Johnh]] 06:47, 16 November 2006 (CET)

My error, the chip is really an Intel 945, and the suggested work-around of acpi_sleep=s3_bios works great! [[User:Johnh|Johnh]] 05:42, 17 November 2006 (CET)

== T60 with intel video card 945 ==

Linux: Gentoo, kernel 2.6.17
I have problem with black display after resume with active framebuffer (vesa or vesa-tng).
I have a lot of garbage after resume with active fb and acpi_sleep=s3_bios,s3_mode parameter.
And I have normal screen without fb and with acpi_sleep=s3_bios,s3_mode, but I cant operate with console.

Any ideas?

Category talk:X31

2007-07-16T03:20:47Z

TheAnarcat: /* sleeping the airo card */

=Bluetooth Antenna?=

Any idea how the Bluetooth BMDC antenna looks like, how large it is, or if it is posible to install it into an X31 without Bluetooth card or Logo on the panel? [[User:Epic|Epic]]

= ACPI and CF Cards =

If you have a CF Card (mounted or unmounted) in the CF slot, it might happen, that ACPI Suspend/Hibernate modes don't work. This happened to me with an old 4 MB CF-Card, I'll try with something more recent sometime. Couldn't find anything useful about that in syslog.

= Installation Report =
Today, I installed a GNU/Linux Debian system on my X31 - without any external USB devices. This is what I did instead:

* Boot up my regular PC with Knoppix 3.8 (including Knoppix Terminal Server)
* Start terminal server. In settings, uncheck "security" to enable root access on clients!
* Link X31 to PC's network interface (either directly using a crossed cable or with normal patch cables using a switch).
* Boot up X31 (the odd boot device name stands for ethernet).
* Start knx2hd (Knoppix Menu) and install to your liking.

Note: With qtparted you even can shrink existing NTFS partitions if you dare (no guarantees), be aware that this may take some 20 minutes.

All hardware was correctly detected (sound, cisco wlan, energy savings), just hibernation lacks the suspend2 patch in kernel. Suspend to RAM works, however.

----
Hei,

great, thanks for the info. It would be nice if you could turn this into an Installation page with the title "Installing Knoppix on a ThinkPad X31". [[User:Wyrfel|Wyrfel]] 20:34, 28 May 2005 (CEST)
----

=Sound problems=

I am unable to get sound to work on my X31.. The modules are loaded, alsamixer is set max and i unmuted all channels (tried with both headphones on and off). Any help would be greatly appreciated.. -- [[User:RichiH|RichiH]] 01:57, 8 October 2006 (CEST)

= make all sleep modes work =

I was able to have all sleep modes (hibernate and sleep) work properly on my X31 by doing the following:

* acpi_sleep=s3_bios,s3_mode passed to the kernel
* no uswsusp or hibernate package installed
* the following in /etc/default/acpi-support:

anarcat@mumia:~$ grep '^\w' /etc/default/acpi-support
ACPI_SLEEP=true
ACPI_HIBERNATE=true
ACPI_SLEEP_MODE=mem
MODULES="snd_intel8x0 snd_intel8x0m snd_ac97_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd snd_page_alloc"
MODULES_WHITELIST=""
SAVE_VBE_STATE=true
VBESTATE=/var/lib/acpi-support/vbestate
POST_VIDEO=true
USE_DPMS=true
RADEON_LIGHT=true
HIBERNATE_MODE=platform
LOCK_SCREEN=true
STOP_SERVICES="mysql "
RESTART_IRDA=false
ENABLE_LAPTOP_MODE=false

I also hacked around the scripts in /etc/acpi, although I think it is not really necessary... The only files I modified are:

anarcat@mumia:/etc/acpi$ hg status
M events/ibm-hibernatebtn
M events/ibm-sleepbtn
M events/sleepbtn

and those are not called by the gnome or default ACPI scripts.

[[User:TheAnarcat|TheAnarcat]] 18:49, 14 July 2007 (UTC)

= sleeping the airo card =

This is what I use to power off my airo card, as the default debian scripts do not work since there's no proper hooks in the driver (i think) to power it off. Sorry for the quick brain dump...

First you need to change the action that gets called when the wifi button is hit:

--- a/events/ibm-wireless Wed Jul 04 15:27:47 2007 -0400
+++ b/events/ibm-wireless Wed May 23 02:46:02 2007 -0400
@@ -3,5 +3,5 @@
# /etc/acpi/wireless.sh for further processing.

event=ibm/hotkey HKEY 00000080 00001005
-action=/etc/acpi/ibm-wireless.sh
+action=/etc/acpi/airo-wireless.sh

The airo-wireless.sh script reads like this:

#!/bin/bash
# Find and enable/disable wireless devices

cd /sys/class/net/
for DEVICE in *; do
if [ -d $DEVICE/wireless ]; then
# $DEVICE is a wireless device. Check if it's powered on:
if ifconfig -s | grep -q $DEVICE; then
# It's powered on. Switch it off.
ifconfig $DEVICE down
echo 0
else
# It's powered off. Switch it on.
ifconfig $DEVICE up
echo 1
fi
fi
done

[[User:TheAnarcat|TheAnarcat]] 18:49, 14 July 2007 (UTC)

Category talk:X31

2007-07-16T03:18:17Z

TheAnarcat: /* make all sleep modes work */

=Bluetooth Antenna?=

Any idea how the Bluetooth BMDC antenna looks like, how large it is, or if it is posible to install it into an X31 without Bluetooth card or Logo on the panel? [[User:Epic|Epic]]

= ACPI and CF Cards =

If you have a CF Card (mounted or unmounted) in the CF slot, it might happen, that ACPI Suspend/Hibernate modes don't work. This happened to me with an old 4 MB CF-Card, I'll try with something more recent sometime. Couldn't find anything useful about that in syslog.

= Installation Report =
Today, I installed a GNU/Linux Debian system on my X31 - without any external USB devices. This is what I did instead:

* Boot up my regular PC with Knoppix 3.8 (including Knoppix Terminal Server)
* Start terminal server. In settings, uncheck "security" to enable root access on clients!
* Link X31 to PC's network interface (either directly using a crossed cable or with normal patch cables using a switch).
* Boot up X31 (the odd boot device name stands for ethernet).
* Start knx2hd (Knoppix Menu) and install to your liking.

Note: With qtparted you even can shrink existing NTFS partitions if you dare (no guarantees), be aware that this may take some 20 minutes.

All hardware was correctly detected (sound, cisco wlan, energy savings), just hibernation lacks the suspend2 patch in kernel. Suspend to RAM works, however.

----
Hei,

great, thanks for the info. It would be nice if you could turn this into an Installation page with the title "Installing Knoppix on a ThinkPad X31". [[User:Wyrfel|Wyrfel]] 20:34, 28 May 2005 (CEST)
----

=Sound problems=

I am unable to get sound to work on my X31.. The modules are loaded, alsamixer is set max and i unmuted all channels (tried with both headphones on and off). Any help would be greatly appreciated.. -- [[User:RichiH|RichiH]] 01:57, 8 October 2006 (CEST)

= make all sleep modes work =

I was able to have all sleep modes (hibernate and sleep) work properly on my X31 by doing the following:

* acpi_sleep=s3_bios,s3_mode passed to the kernel
* no uswsusp or hibernate package installed
* the following in /etc/default/acpi-support:

anarcat@mumia:~$ grep '^\w' /etc/default/acpi-support
ACPI_SLEEP=true
ACPI_HIBERNATE=true
ACPI_SLEEP_MODE=mem
MODULES="snd_intel8x0 snd_intel8x0m snd_ac97_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd snd_page_alloc"
MODULES_WHITELIST=""
SAVE_VBE_STATE=true
VBESTATE=/var/lib/acpi-support/vbestate
POST_VIDEO=true
USE_DPMS=true
RADEON_LIGHT=true
HIBERNATE_MODE=platform
LOCK_SCREEN=true
STOP_SERVICES="mysql "
RESTART_IRDA=false
ENABLE_LAPTOP_MODE=false

I also hacked around the scripts in /etc/acpi, although I think it is not really necessary... The only files I modified are:

anarcat@mumia:/etc/acpi$ hg status
M events/ibm-hibernatebtn
M events/ibm-sleepbtn
M events/sleepbtn

and those are not called by the gnome or default ACPI scripts.

[[User:TheAnarcat|TheAnarcat]] 18:49, 14 July 2007 (UTC)

= sleeping the airo card =

Sorry for the quick brain dump...

--- a/events/ibm-wireless Wed Jul 04 15:27:47 2007 -0400
+++ b/events/ibm-wireless Wed May 23 02:46:02 2007 -0400
@@ -3,5 +3,5 @@
# /etc/acpi/wireless.sh for further processing.

event=ibm/hotkey HKEY 00000080 00001005
-action=/etc/acpi/ibm-wireless.sh
+action=/etc/acpi/airo-wireless.sh

#!/bin/bash
# Find and enable/disable wireless devices

cd /sys/class/net/
for DEVICE in *; do
if [ -d $DEVICE/wireless ]; then
# $DEVICE is a wireless device. Check if it's powered on:
if ifconfig -s | grep -q $DEVICE; then
# It's powered on. Switch it off.
ifconfig $DEVICE down
echo 0
else
# It's powered off. Switch it on.
ifconfig $DEVICE up
echo 1
fi
fi
done

[[User:TheAnarcat|TheAnarcat]] 18:49, 14 July 2007 (UTC)

Problems with ACPI suspend-to-ram

2007-07-14T18:54:20Z

TheAnarcat: /* Troubles on resume */

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.

;Write error:If {{cmdroot|echo mem > /sys/power/state}} shows "write error: Operation not permitted", verify that CONFIG_HOTPLUG_CPU option is enabled in the kernel. [[Software_Suspend_2|Suspend2]] automatically selects this option.

;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]].

;Built-in MMC reader:If you have an MMC reader, and the computer hangs when attempting suspend then remove sdhci, mmc_block, and mmc_core modules before suspending.

;Could not power down device <NULL>: error -22:If you have the acpi_cpufreq kernel module loaded, this prevents suspension.

==Troubles on resume==
;Blank display on resume:
:When resuming from a suspend-to-ram the display might remain black (on {{X60}}) 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. See also '''System hang on resume''' on this page - which may be potentially mismatched with this one.

;No mouse cursor on resume:
:When resuming from a suspend-to-ram your X cursor might be invisible(on {{X40}}) when using {{path|/sys/power/state}} directly to suspend, they way to fix this is to rerun the post bios code after returning for suspending.
:{{cmdroot|FGCONSOLE<nowiki>=</nowiki>`fgconsole\`}}
:{{cmdroot|chvt 1 && echo -n mem >/sys/power/state}}
:{{cmdroot|vbetool post && chvt 7 && chvt $FGCONSOLE}}

;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 X displays fine. If all of this is true, then adding the kernel option {{bootparm|acpi_sleep|s3_bios,s3_mode}} in your menu.lst or lilo.conf may solve the problem.

;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 {{bootparm|ibm-acpi.experimental|1}} option, you can switch it off on resume by appending the following line to your suspend script: {{cmdroot|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.
:*SATA-based laptops utilize the '''libata layer for disk access''' which does not have fully-working power-management support before Linux kernel 2.6.16 (ata_piix) and 2.6.19 (ahci). 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.
:*Using [[HDAPS]] as a module causes a crash on resume with the Linux kernel 2.6.19 (possibly even earlier versions). This was observed on a {{X41}}. Try unloading the module before suspending.
:*Gnome-power-manager might be using the wrong backend. If you are able to suspend from the commandline with a certain method, make sure the others are not available so that g-p-m doesn't choose the wrong one. For example, if you suspend with {{cmdroot|echo mem > /sys/power/state}}, make sur '''uswsusp''' and '''hibernate''' are uninstalled.

;System hang on resume:
:When system resumes it hangs right after restarting tasks. Strange thing is, that you may be even able to restart your ThinkPad using {{key|ctrl}}{{key|alt}}{{key|del}}, but if you try to blindly exec a command, it will not work, (eg. touch FILE) so it's not only the problem of videocard. This may be fixed by passing {{bootparm|ec_intr|0}} on kernel cmdline. Affected models: {{T20,T21}} (at least [[2648-46U]] (T20),[[2647-8AG]] (T21)).
:'''Note:''' ''this is resolved in kernel 2.6.20, there is no need to pass the {{bootparm|ec_intr|0}} bootparam anymore (moreover, you are discouraged to use it) See [http://bugzilla.kernel.org/show_bug.cgi?id=6749 revelant kernel bug report]''

;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?action=recall&rev=28#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.

;Power Off when suspended laptop is docked
:When T60p is suspended, docking laptop into Advanced Dock immediately turns off laptop and crescent moon sleep indicator LED. Pressing power button initiates cold boot. Also reported by multiple people on thinkpads.com.

;SectorIdNotFound disk errors when laptop is resumed
:The errors look like this:
: Oct 14 17:35:02 cacharro kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
: Oct 14 17:35:02 cacharro kernel: hda: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=115896900, sector=115896900
: Oct 14 17:35:02 cacharro kernel: ide: failed opcode was: unknown

:This happens when you have [[Hidden Protected Area]] (HPA) enabled on the hard drive. There is a [http://bugzilla.kernel.org/show_bug.cgi?id=6840 kernel bug report with an unfinished patch] to fix this. This is not fixed as of kernel 2.16.18.

Problems with ACPI suspend-to-ram

2007-07-14T18:52:48Z

TheAnarcat: add trick about installing just what's needed

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.

;Write error:If {{cmdroot|echo mem > /sys/power/state}} shows "write error: Operation not permitted", verify that CONFIG_HOTPLUG_CPU option is enabled in the kernel. [[Software_Suspend_2|Suspend2]] automatically selects this option.

;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]].

;Built-in MMC reader:If you have an MMC reader, and the computer hangs when attempting suspend then remove sdhci, mmc_block, and mmc_core modules before suspending.

;Could not power down device <NULL>: error -22:If you have the acpi_cpufreq kernel module loaded, this prevents suspension.

==Troubles on resume==
;Blank display on resume:
:When resuming from a suspend-to-ram the display might remain black (on {{X60}}) 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. See also '''System hang on resume''' on this page - which may be potentially mismatched with this one.

;No mouse cursor on resume:
:When resuming from a suspend-to-ram your X cursor might be invisible(on {{X40}}) when using {{path|/sys/power/state}} directly to suspend, they way to fix this is to rerun the post bios code after returning for suspending.
:{{cmdroot|FGCONSOLE<nowiki>=</nowiki>`fgconsole\`}}
:{{cmdroot|chvt 1 && echo -n mem >/sys/power/state}}
:{{cmdroot|vbetool post && chvt 7 && chvt $FGCONSOLE}}

;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 X displays fine. If all of this is true, then adding the kernel option {{bootparm|acpi_sleep|s3_bios,s3_mode}} in your menu.lst or lilo.conf may solve the problem.

;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 {{bootparm|ibm-acpi.experimental|1}} option, you can switch it off on resume by appending the following line to your suspend script: {{cmdroot|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.
:*SATA-based laptops utilize the '''libata layer for disk access''' which does not have fully-working power-management support before Linux kernel 2.6.16 (ata_piix) and 2.6.19 (ahci). 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.
:*Using [[HDAPS]] as a module causes a crash on resume with the Linux kernel 2.6.19 (possibly even earlier versions). This was observed on a {{X41}}. Try unloading the module before suspending.
:*Gnome-power-manager might be using the wrong backend. If you are able to suspend from the commandline with a certain method, make sure the others are not available so that g-p-m doesn't choose the wrong one. For example, if you suspend with echo mem > /sys/power/state, make sur uswsusp and hibernate or uninstalled.

;System hang on resume:
:When system resumes it hangs right after restarting tasks. Strange thing is, that you may be even able to restart your ThinkPad using {{key|ctrl}}{{key|alt}}{{key|del}}, but if you try to blindly exec a command, it will not work, (eg. touch FILE) so it's not only the problem of videocard. This may be fixed by passing {{bootparm|ec_intr|0}} on kernel cmdline. Affected models: {{T20,T21}} (at least [[2648-46U]] (T20),[[2647-8AG]] (T21)).
:'''Note:''' ''this is resolved in kernel 2.6.20, there is no need to pass the {{bootparm|ec_intr|0}} bootparam anymore (moreover, you are discouraged to use it) See [http://bugzilla.kernel.org/show_bug.cgi?id=6749 revelant kernel bug report]''

;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?action=recall&rev=28#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.

;Power Off when suspended laptop is docked
:When T60p is suspended, docking laptop into Advanced Dock immediately turns off laptop and crescent moon sleep indicator LED. Pressing power button initiates cold boot. Also reported by multiple people on thinkpads.com.

;SectorIdNotFound disk errors when laptop is resumed
:The errors look like this:
: Oct 14 17:35:02 cacharro kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
: Oct 14 17:35:02 cacharro kernel: hda: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=115896900, sector=115896900
: Oct 14 17:35:02 cacharro kernel: ide: failed opcode was: unknown

:This happens when you have [[Hidden Protected Area]] (HPA) enabled on the hard drive. There is a [http://bugzilla.kernel.org/show_bug.cgi?id=6840 kernel bug report with an unfinished patch] to fix this. This is not fixed as of kernel 2.16.18.

Talk:Problem with display remaining black after resume

2007-07-14T18:50:46Z

TheAnarcat: point to the X31 talk page

== T43 with Intel Graphics Media Accelerator ==

It seems there are several possible solutions for this issue:

I tried 'Option "VBERestore" "yes"' as hinted in X41 section below, and this worked for me on my T43/915GM.

My T43 (1871-FYG) with Intel 915GM is also affected by the problem and the 'ATI' sollution with
acpi_sleep=s3_bios works. Please consider updating the page (I don't dare to do it myself).

== From my experience, this does not work with TP R50e. ==

If you want to be able to resume, you need :
* To start from a VT
* No option acpi_sleep
* to save the PCI state like:
cat /proc/bus/pci/00/02.0 > /var/cache/video.config
* Once you get back, restore it:
cat /var/cache/video.config > /proc/bus/pci/00/02.0

However, the X screen is not clean after the restore, so this is not very useable...

== The comment on R50e ==

There is a comment at the end of the page on R50e, saying that you should switch to console first, and look at a page to learn how to do this.

However. it seems to me that the given script already does it. Should the comment be removed?
----
The scripts are different. However, if you can approve that the solution provided on this page resolves the problem, please remove the footnote.

[[User:Wyrfel|Wyrfel]] 14:46, 17 Oct 2005 (CEST)
----
On my R50e, the script on this page works fine, while the one linked in the footnote quickly wakes up from sleep.

[[User:Thisnukes4u|Thisnukes4u]] 19:39, 1 Jan 2006 (CET)

== Problems with R51 and Intel Graphics ==

The problems described on the page occur intermittently
with an Intel Graphics card on an R51. Here is what happens:

1. One some occassions everything seems to work fine.

2. On other occassions the screen looks OK but the some plane seems to have vanished. New text on the screen overwrites instead of replaces prior text. The "standard" pattern disappears from the X background.

3. On yet other occassions the X server dies and comes out "blank" in the mode (2) above.

4. The above problems appear only with the "i810" driver. The "vesa" driver works fine. Moreover, if the machine is "suspend-to-disk"ed then the problem disappears on resumption once the X server is killed and re-started.

But for 1 and 4 above I would have given up and either avoided suspend to ram altogether or used vesa mode---as it stands the problem is tantalising.

Kapil kapil at imsc dot res dot in

== X30 ==

The {{bootparm|acpi_sleep|s3_bios}} boot parameter did the trick, no additional scripts required (Ubuntu feisty).

== X31 ==

In addition to the s3_bios trick, i needed to uninstall the uswsusp and hibernate packages. I've put all the details in the X31 talk page. [[User:TheAnarcat|TheAnarcat]] 18:50, 14 July 2007 (UTC)

== X40 with an Intel 855GM Integrated Graphics Device ==

I used the {{bootparm|acpi_sleep|s3_bios}} boot parameter and the following ACPI script:

#!/bin/sh
set -e

vt=`fgconsole`
chvt 12
echo mem >/sys/power/state
vbetool post
chvt $vt

The {{bootparm|acpi_sleep|s3_bios}} boot parameter alone did not fix things, and neither did saving and restoring the information from {{path|/proc/bus/pci/00/02.0}}.

== X41 with an Intel 915GM Integrated Graphics Device ==

It works with the {{bootparm|acpi_sleep|s3_bios,s3_mode}} boot parameter. Resume works great, both on the VESA console and in X.

:Interesting--that didn't work for me. I needed to do several things to get it to work. First, I used s3_bios, but not s3_mode. Secondly, I had to edit resume_video() in /etc/pm/functions-intel to comment out the VBE post and restore. Those two changes made it functional, but the improper lid state in the HAL daemon caused it to go back to sleep just as soon as it resumed upon the lid opening, so I added a HAL restart to the front end of /etc/acpi/actions/sleep.sh. This means that I have to restart gnome-power-manager, too. I haven't yet figured out a way to do that in sleep.sh; currently I do it manually. I'll post this to the main page soon, unless I hear comments to the contrary. [[User:BrianTung|BrianTung]] 19:52, 30 April 2006 (CEST) (fixed a little)

:(gsaito): I used the {{bootparm|acpi_sleep|s3_bios,s3_mode}} boot parameter and it worked perfectly, entering Suspend to RAM and resuming perfectly. No more blank screens after resuming. No need for any other change as described above, at least in my case. I also have an X41 with Intel 915GM graphics adapter. I use OpenSUSE v.10.0.

I read the edit by Uberpenguin and tried the stated fix. No go: The next time I pulled out the adapter after a resume--boom, the machine goes straight back to sleep again. Evidently, the suggested workaround does not work on all machines. [[User:BrianTung|BrianTung]] 19:54, 22 June 2006 (CEST)

Yesterday I tried adding 'Option "VBERestore" "yes"' to the Driver section in xorg.conf on my X41 and it works great. I used no boot-params or anything else. The distribution is OpenSuSE 10.1. If anyone can acknowledge to my experience, I'd like to add this solution to the articles in this wiki. [[User:Sirmoloch|Sirmoloch]] 11:49, 4 July 2006 (CEST)

== Z60t with an Intel 915GM Integrated Graphics Device (PCI Express) ==

It works with the {{bootparm|acpi_sleep|s3_bios}} boot parameter. Here is the script I use (gentoo). Note: stopping and starting WiFi is not necessary to resume, but it is dead on resume until restarted and the module is reloaded. This is on a 2.6.15.4 kernel with framebuffer console support. The blinking led thing is a nice touch I got from the hibernate-scripts package - it blinks the sleep led (moon icon) until the sleep or resume cycle is finished.

The 'vbetool vbemode get/set' commands are for saving and restoring the console text mode - otherwise the screen becomes garbled.

#!/bin/bash

# blink sleep led (if ibm_acpi is installed)
echo 7 blink > /proc/acpi/ibm/led

# change to console 10 (unused?)
FGCONSOLE=`fgconsole`
chvt 10

# save video state
VBEMODE=`vbetool vbemode get`
cat /proc/bus/pci/00/02.0 > /tmp/video_state

# sync filesystem
sync

# sync hardware clock with system time
hwclock --systohc

# stop networking (atheros chipset)
/etc/init.d/net.ath0 stop
rmmod ath_pci

# go to sleep
sleep 2 ; echo -n 3 > /proc/acpi/sleep

# blink sleep led
echo 7 blink > /proc/acpi/ibm/led

# restore system clock
hwclock --hctosys

# restore video state
vbetool vbemode set $VBEMODE
cat /tmp/video_state > /proc/bus/pci/00/02.0

# change back to X
chvt $FGCONSOLE

# restart networking
modprobe ath_pci
/etc/init.d/net.ath0 start

# clean up behind us
rm /tmp/video_state
echo 7 off > /proc/acpi/ibm/led

== Fedora Core 5 ==

The vbetool on the article page worked great for me, but NetworkManager would not bring the wireless interface back up. I had to add "ath_pci" to the SUSPEND_MODULES variable in /etc/sysconfig/pm.

== R50e 1834-S3G in Debian Etch ==

I found it necessary to add a {{cmdroot|clear}} to the script before {{cmdroot|chvt}} 'ing back to VT7 after wakeup. If I didn't, I would end up with a 99% black corrupted screen in X.
[[User:Ris|Ris]] 18:38, 30 October 2006 (CET)

== Work-arounds for X60s / Intel 950 ==

The page identifies X60s's as having problems with blank display on resume (and I can confirm), but doesn't suggest a work-around. (Nor are there any obvious fixes for this boxes Intel 950 graphics card.) Has anyone gotten it working? [[User:Johnh|Johnh]] 06:47, 16 November 2006 (CET)

My error, the chip is really an Intel 945, and the suggested work-around of acpi_sleep=s3_bios works great! [[User:Johnh|Johnh]] 05:42, 17 November 2006 (CET)

== T60 with intel video card 945 ==

Linux: Gentoo, kernel 2.6.17
I have problem with black display after resume with active framebuffer (vesa or vesa-tng).
I have a lot of garbage after resume with active fb and acpi_sleep=s3_bios,s3_mode parameter.
And I have normal screen without fb and with acpi_sleep=s3_bios,s3_mode, but I cant operate with console.

Any ideas?

Category talk:X31

2007-07-14T18:49:15Z

TheAnarcat: add my sigs, fix headings

=Bluetooth Antenna?=

Any idea how the Bluetooth BMDC antenna looks like, how large it is, or if it is posible to install it into an X31 without Bluetooth card or Logo on the panel? [[User:Epic|Epic]]

= ACPI and CF Cards =

If you have a CF Card (mounted or unmounted) in the CF slot, it might happen, that ACPI Suspend/Hibernate modes don't work. This happened to me with an old 4 MB CF-Card, I'll try with something more recent sometime. Couldn't find anything useful about that in syslog.

= Installation Report =
Today, I installed a GNU/Linux Debian system on my X31 - without any external USB devices. This is what I did instead:

* Boot up my regular PC with Knoppix 3.8 (including Knoppix Terminal Server)
* Start terminal server. In settings, uncheck "security" to enable root access on clients!
* Link X31 to PC's network interface (either directly using a crossed cable or with normal patch cables using a switch).
* Boot up X31 (the odd boot device name stands for ethernet).
* Start knx2hd (Knoppix Menu) and install to your liking.

Note: With qtparted you even can shrink existing NTFS partitions if you dare (no guarantees), be aware that this may take some 20 minutes.

All hardware was correctly detected (sound, cisco wlan, energy savings), just hibernation lacks the suspend2 patch in kernel. Suspend to RAM works, however.

----
Hei,

great, thanks for the info. It would be nice if you could turn this into an Installation page with the title "Installing Knoppix on a ThinkPad X31". [[User:Wyrfel|Wyrfel]] 20:34, 28 May 2005 (CEST)
----

=Sound problems=

I am unable to get sound to work on my X31.. The modules are loaded, alsamixer is set max and i unmuted all channels (tried with both headphones on and off). Any help would be greatly appreciated.. -- [[User:RichiH|RichiH]] 01:57, 8 October 2006 (CEST)

= make all sleep modes work =

I was able to have all sleep modes (hibernate and sleep) work properly on my X31 by doing the following:

* acpi_sleep=s3_bios,s3_mode passed to the kernel
* no uswsusp or hibernate package installed
* the following in /etc/default/acpi-support:

anarcat@mumia:~$ grep '^\w' /etc/default/acpi-support
ACPI_SLEEP=true
ACPI_HIBERNATE=true
ACPI_SLEEP_MODE=mem
MODULES="snd_intel8x0 snd_intel8x0m snd_ac97_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd snd_page_alloc"
MODULES_WHITELIST=""
SAVE_VBE_STATE=true
VBESTATE=/var/lib/acpi-support/vbestate
POST_VIDEO=true
USE_DPMS=true
RADEON_LIGHT=true
HIBERNATE_MODE=platform
LOCK_SCREEN=true
STOP_SERVICES="mysql "
RESTART_IRDA=false
ENABLE_LAPTOP_MODE=false

I also hacked around the scripts in /etc/acpi, although I think it is not really necessary... The only files I modified are:

anarcat@mumia:/etc/acpi$ hg status
M events/ibm-hibernatebtn
M events/ibm-sleepbtn
M events/sleepbtn

and those are not called by the gnome or default ACPI scripts.

[[User:TheAnarcat|TheAnarcat]] 18:49, 14 July 2007 (UTC)

= sleeping the airo card =

Sorry for the quick brain dump...

--- a/events/ibm-wireless Wed Jul 04 15:27:47 2007 -0400
+++ b/events/ibm-wireless Wed May 23 02:46:02 2007 -0400
@@ -3,5 +3,5 @@
# /etc/acpi/wireless.sh for further processing.

event=ibm/hotkey HKEY 00000080 00001005
-action=/etc/acpi/ibm-wireless.sh
+action=/etc/acpi/airo-wireless.sh

#!/bin/bash
# Find and enable/disable wireless devices

cd /sys/class/net/
for DEVICE in *; do
if [ -d $DEVICE/wireless ]; then
# $DEVICE is a wireless device. Check if it's powered on:
if ifconfig -s | grep -q $DEVICE; then
# It's powered on. Switch it off.
ifconfig $DEVICE down
echo 0
else
# It's powered off. Switch it on.
ifconfig $DEVICE up
echo 1
fi
fi
done

[[User:TheAnarcat|TheAnarcat]] 18:49, 14 July 2007 (UTC)

Category talk:X31

2007-07-14T18:48:38Z

TheAnarcat: sleeping the airo card

=Bluetooth Antenna?=

Any idea how the Bluetooth BMDC antenna looks like, how large it is, or if it is posible to install it into an X31 without Bluetooth card or Logo on the panel? [[User:Epic|Epic]]

= ACPI and CF Cards =

If you have a CF Card (mounted or unmounted) in the CF slot, it might happen, that ACPI Suspend/Hibernate modes don't work. This happened to me with an old 4 MB CF-Card, I'll try with something more recent sometime. Couldn't find anything useful about that in syslog.

= Installation Report =
Today, I installed a GNU/Linux Debian system on my X31 - without any external USB devices. This is what I did instead:

* Boot up my regular PC with Knoppix 3.8 (including Knoppix Terminal Server)
* Start terminal server. In settings, uncheck "security" to enable root access on clients!
* Link X31 to PC's network interface (either directly using a crossed cable or with normal patch cables using a switch).
* Boot up X31 (the odd boot device name stands for ethernet).
* Start knx2hd (Knoppix Menu) and install to your liking.

Note: With qtparted you even can shrink existing NTFS partitions if you dare (no guarantees), be aware that this may take some 20 minutes.

All hardware was correctly detected (sound, cisco wlan, energy savings), just hibernation lacks the suspend2 patch in kernel. Suspend to RAM works, however.

----
Hei,

great, thanks for the info. It would be nice if you could turn this into an Installation page with the title "Installing Knoppix on a ThinkPad X31". [[User:Wyrfel|Wyrfel]] 20:34, 28 May 2005 (CEST)
----

=Sound problems=

I am unable to get sound to work on my X31.. The modules are loaded, alsamixer is set max and i unmuted all channels (tried with both headphones on and off). Any help would be greatly appreciated.. -- [[User:RichiH|RichiH]] 01:57, 8 October 2006 (CEST)

== make all sleep modes work ==

I was able to have all sleep modes (hibernate and sleep) work properly on my X31 by doing the following:

* acpi_sleep=s3_bios,s3_mode passed to the kernel
* no uswsusp or hibernate package installed
* the following in /etc/default/acpi-support:

anarcat@mumia:~$ grep '^\w' /etc/default/acpi-support
ACPI_SLEEP=true
ACPI_HIBERNATE=true
ACPI_SLEEP_MODE=mem
MODULES="snd_intel8x0 snd_intel8x0m snd_ac97_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd snd_page_alloc"
MODULES_WHITELIST=""
SAVE_VBE_STATE=true
VBESTATE=/var/lib/acpi-support/vbestate
POST_VIDEO=true
USE_DPMS=true
RADEON_LIGHT=true
HIBERNATE_MODE=platform
LOCK_SCREEN=true
STOP_SERVICES="mysql "
RESTART_IRDA=false
ENABLE_LAPTOP_MODE=false

I also hacked around the scripts in /etc/acpi, although I think it is not really necessary... The only files I modified are:

anarcat@mumia:/etc/acpi$ hg status
M events/ibm-hibernatebtn
M events/ibm-sleepbtn
M events/sleepbtn

and those are not called by the gnome or default ACPI scripts.

== sleeping the airo card ==

Sorry for the quick brain dump...

--- a/events/ibm-wireless Wed Jul 04 15:27:47 2007 -0400
+++ b/events/ibm-wireless Wed May 23 02:46:02 2007 -0400
@@ -3,5 +3,5 @@
# /etc/acpi/wireless.sh for further processing.

event=ibm/hotkey HKEY 00000080 00001005
-action=/etc/acpi/ibm-wireless.sh
+action=/etc/acpi/airo-wireless.sh

#!/bin/bash
# Find and enable/disable wireless devices

cd /sys/class/net/
for DEVICE in *; do
if [ -d $DEVICE/wireless ]; then
# $DEVICE is a wireless device. Check if it's powered on:
if ifconfig -s | grep -q $DEVICE; then
# It's powered on. Switch it off.
ifconfig $DEVICE down
echo 0
else
# It's powered off. Switch it on.
ifconfig $DEVICE up
echo 1
fi
fi
done

Category talk:X31

2007-07-14T18:48:03Z

TheAnarcat: make all sleep modes work

=Bluetooth Antenna?=

Any idea how the Bluetooth BMDC antenna looks like, how large it is, or if it is posible to install it into an X31 without Bluetooth card or Logo on the panel? [[User:Epic|Epic]]

= ACPI and CF Cards =

If you have a CF Card (mounted or unmounted) in the CF slot, it might happen, that ACPI Suspend/Hibernate modes don't work. This happened to me with an old 4 MB CF-Card, I'll try with something more recent sometime. Couldn't find anything useful about that in syslog.

= Installation Report =
Today, I installed a GNU/Linux Debian system on my X31 - without any external USB devices. This is what I did instead:

* Boot up my regular PC with Knoppix 3.8 (including Knoppix Terminal Server)
* Start terminal server. In settings, uncheck "security" to enable root access on clients!
* Link X31 to PC's network interface (either directly using a crossed cable or with normal patch cables using a switch).
* Boot up X31 (the odd boot device name stands for ethernet).
* Start knx2hd (Knoppix Menu) and install to your liking.

Note: With qtparted you even can shrink existing NTFS partitions if you dare (no guarantees), be aware that this may take some 20 minutes.

All hardware was correctly detected (sound, cisco wlan, energy savings), just hibernation lacks the suspend2 patch in kernel. Suspend to RAM works, however.

----
Hei,

great, thanks for the info. It would be nice if you could turn this into an Installation page with the title "Installing Knoppix on a ThinkPad X31". [[User:Wyrfel|Wyrfel]] 20:34, 28 May 2005 (CEST)
----

=Sound problems=

I am unable to get sound to work on my X31.. The modules are loaded, alsamixer is set max and i unmuted all channels (tried with both headphones on and off). Any help would be greatly appreciated.. -- [[User:RichiH|RichiH]] 01:57, 8 October 2006 (CEST)

== make all sleep modes work ==

I was able to have all sleep modes (hibernate and sleep) work properly on my X31 by doing the following:

* acpi_sleep=s3_bios,s3_mode passed to the kernel
* no uswsusp or hibernate package installed
* the following in /etc/default/acpi-support:

anarcat@mumia:~$ grep '^\w' /etc/default/acpi-support
ACPI_SLEEP=true
ACPI_HIBERNATE=true
ACPI_SLEEP_MODE=mem
MODULES="snd_intel8x0 snd_intel8x0m snd_ac97_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd snd_page_alloc"
MODULES_WHITELIST=""
SAVE_VBE_STATE=true
VBESTATE=/var/lib/acpi-support/vbestate
POST_VIDEO=true
USE_DPMS=true
RADEON_LIGHT=true
HIBERNATE_MODE=platform
LOCK_SCREEN=true
STOP_SERVICES="mysql "
RESTART_IRDA=false
ENABLE_LAPTOP_MODE=false

I also hacked around the scripts in /etc/acpi, although I think it is not really necessary... The only files I modified are:

anarcat@mumia:/etc/acpi$ hg status
M events/ibm-hibernatebtn
M events/ibm-sleepbtn
M events/sleepbtn

and those are not called by the gnome or default ACPI scripts.

User:TheAnarcat

2007-05-23T06:32:56Z

TheAnarcat: simple homepage

Free software enthousiast, see http://wiki.koumbit.net/TheAnarcat for my WikiHome.

ThinkPad X3 UltraBase

2007-05-23T06:14:32Z

TheAnarcat: 2.6.22-rc2 better supported

{| cellspacing="0" cellpadding="2" border="0"
| style="vertical-align:top;" | __TOC__
[[image:UltraBaseX3.gif|UltraBase X3]]
| 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;">
== IBM UltraBase X3 ==
The IBM UltraBase X3 is a portable dock for the X30, X31 and X32 ThinkPads providing extra ports as well as a bay for an optical drive and a set of stereo speakers. Containing a full featured [[UltraBay|UltraBay Plus]] slot, it provides flexibility in drive choice as well as the option of a secondary battery for extended working time on the road. The Ultrabase X3 also features a battery slot on the underside that accepts the same battery as your X30 Series ThinkPad. The UltraBase X3 doesn't provide a second docking port as the original [[UltraBase]] did, hence you can't dock the UltraBase to any of the other docking solutions.

=== Features ===
* Passthrough ports:
** Ethernet (RJ45)
** Modem (RJ11)
** USB
** [[VGA Port|VGA]]
** [[Serial Port|Serial (DB9-M)]]
** [[Parallel Port|Parallel (DB25-F)]]
** [[PS/2 Port|Combined PS/2 Mouse + Keyboard]]
* [[UltraBay|Ultrabay Plus]]
* Stereo speakers
* Kensington security hole
* Battery Slot (For Second X30 Series Battery)

===Pros & Cons===
* Positives: Expansion capability, portable
* Negatives: makes the ThinkPad quite thick, no extra docking port
* Compatibility: {{X30}}, {{X31}}, {{X32}}
* Warranty: Three Years
</div>
|}

==UltraBay Plus==
The [[UltraBay|UltraBay Plus]] slot in this dock is a full featured one and supports hot swapping with all UltraBay Plus and UltraBay 2000 drives. You can also feed it with the UltraBay Plus battery pack to extend the overall battery life time.

== Linux support ==

This can be problematic under Debian, as the default kernel (2.6.18) do not support the IBM docks. I had to recompile it to enable CONFIG_ACPI_IBM_DOCK, and disable CONFIG_ACPI_DOCK. I also needed to hook a few scripts into the acpi events system.

ibm-dock.sh:
#!/bin/sh

# acknowledge docking with the dockstation
echo dock > /proc/acpi/ibm/dock

ibm-undock.sh:
#!/bin/sh

# prepare the laptop for undocking with the dockstation

echo undock > /proc/acpi/ibm/dock

events/ibm-dock:

event=ibm/dock GDCK 00000000 00000003
action=/etc/acpi/ibm-dock.sh

events/ibm-undock:

event=ibm/dock GDCK 00000003 00000001
action=/etc/acpi/ibm-undock.sh

''Update'': 2.6.22-rc2 actually works without a flaw, without the above modifications, provided that the "bay" and "dock" modules are loaded at boot time.

ThinkPad X3 UltraBase

2007-05-22T20:08:25Z

TheAnarcat: document how to dock/undock properly under debian

{| cellspacing="0" cellpadding="2" border="0"
| style="vertical-align:top;" | __TOC__
[[image:UltraBaseX3.gif|UltraBase X3]]
| 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;">
== IBM UltraBase X3 ==
The IBM UltraBase X3 is a portable dock for the X30, X31 and X32 ThinkPads providing extra ports as well as a bay for an optical drive and a set of stereo speakers. Containing a full featured [[UltraBay|UltraBay Plus]] slot, it provides flexibility in drive choice as well as the option of a secondary battery for extended working time on the road. The Ultrabase X3 also features a battery slot on the underside that accepts the same battery as your X30 Series ThinkPad. The UltraBase X3 doesn't provide a second docking port as the original [[UltraBase]] did, hence you can't dock the UltraBase to any of the other docking solutions.

=== Features ===
* Passthrough ports:
** Ethernet (RJ45)
** Modem (RJ11)
** USB
** [[VGA Port|VGA]]
** [[Serial Port|Serial (DB9-M)]]
** [[Parallel Port|Parallel (DB25-F)]]
** [[PS/2 Port|Combined PS/2 Mouse + Keyboard]]
* [[UltraBay|Ultrabay Plus]]
* Stereo speakers
* Kensington security hole
* Battery Slot (For Second X30 Series Battery)

===Pros & Cons===
* Positives: Expansion capability, portable
* Negatives: makes the ThinkPad quite thick, no extra docking port
* Compatibility: {{X30}}, {{X31}}, {{X32}}
* Warranty: Three Years
</div>
|}

==UltraBay Plus==
The [[UltraBay|UltraBay Plus]] slot in this dock is a full featured one and supports hot swapping with all UltraBay Plus and UltraBay 2000 drives. You can also feed it with the UltraBay Plus battery pack to extend the overall battery life time.

== Linux support ==

This can be problematic under Debian, as the default kernels do not support the IBM docks. I had to recompile it to enable CONFIG_ACPI_IBM_DOCK, and disable CONFIG_ACPI_DOCK. I also needed to hook a few scripts into the acpi events system.

ibm-dock.sh:
#!/bin/sh

# acknowledge docking with the dockstation
echo dock > /proc/acpi/ibm/dock

ibm-undock.sh:
#!/bin/sh

# prepare the laptop for undocking with the dockstation

echo undock > /proc/acpi/ibm/dock

events/ibm-dock:

event=ibm/dock GDCK 00000000 00000003
action=/etc/acpi/ibm-dock.sh

events/ibm-undock:

event=ibm/dock GDCK 00000003 00000001
action=/etc/acpi/ibm-undock.sh

BIOS Upgrade

2007-03-07T15:21:00Z

TheAnarcat: -- me too

__TOC__

This page is meant to describe ways to update the BIOS on a ThinkPad that only runs Linux for users that don't have ready access to Windows. If you have Windows on your ThinkPad you can just boot into it and follow instructions on the IBM website.

{{NOTE| In one case ([[APM setup on a type 2379 ThinkPad T40]]) it was not possible to upgrade the BIOS from Windows XP; a downgrade to Windows 98 was required to successfully run the BIOS upgrade app. The symptoms in this case were that, once the files had been extracted to the hard disk, and the machine was to reboot into the upgrade app, it would beep and hang just before reboot, requiring a power cycle. Once the power was cycled, it would simply reboot back into XP without performing any BIOS upgrade actions. So even if you have Windows, you may still need to use the info on this page.}}

----
==Before You Begin==
Updating the BIOS in Linux (with few exceptions) '''is not officially supported''' by IBM. However there are work arounds.

{{WARN|By following any of the instructions here you are accepting the '''very real risk''' of turning your thinkpad into a big expensive paper weight, as a firmware update gone wrong can create unfixable problems.

'''Proceed at your own risk!'''

It is also '''important''' to understand that all newer thinkpads have 2 seperate firmwares, the BIOS and the Control Program. A specific version of the Control Program will only work with specific versions of the BIOS. The IBM documentation is sometimes confusing about the order of update. Updating the Control Program first, then the BIOS seems to be the correct order. Make sure to do the updates immediately following each other, otherwise you risk turning your thinkpad into a very nice paper weight.}}

==BIOS Upgrade Paths==

For every firmware (either BIOS or Control Program) update on the IBM site there are two different firmware update programs provided. A list of links to firmware downloads can be found at [[BIOS Upgrade Downloads]] for nearly all Thinkpad Models.

===The Diskette Updater===

This installer appears to be a 16bit dos program which asks you to accept a license agreement. It will run in Windows, DOS, OS/2, or [http://dosemu.sf.net Dosemu] perfectly, but requires a real floppy disk attached via a real floppy control. The USB Floppy Drive to the new Thinkpads doesn't count.

===The Non Diskette Updater===
{{WARN|Though this process was successfully tested on one version of .exe files found on IBMs website this doesn't mean it will work for all of them. Use at your own risk.}}

This installer appears to be a 32bit windows exe which is designed for updating the BIOS directly from a running Windows OS. It turns out that the .exe is really a wrapper license program arround windows .cab files (this information is in [[How_to_change_the_BIOS_bootsplash_screen|BIOS-Bootsplash]]). If you install the Linux program [http://freshmeat.net/projects/cabextract/ '''cabextract'''] you can expand these files directly. Run the following:

:{{cmduser|cabextract FILENAME.exe}}

You will get 8 files in the current directory. One of them will be FILENAME.img. You can test that this is really a floppy image by running:

:{{cmdroot|mkdir mntfloppy}}
:{{cmdroot|mount -o loop FILENAME.img mntfloppy}}
:{{cmdroot|ls -la mntfloppy}}

If the results of {{cmdroot|ls -la mntfloppy}} look like a dos floppy, and no read errors were displayed, you have a pretty good chance that the floppy image is usable.

If you were able to create the boot floppy per the Diskette update method, and you have a Floppy with your Thinkpad, the update should be simple.

==Updating an X60==
If there is no floppy, and no windows, but an external USB CD, then there is hope.

===Build a bootable CD with USB support===
Get the ISO Image style BIOS upgrade, and the freedos floppy (http://www.ankreuzen.de/freedos/files/fd9sr1/fdos1440.zip)

:{{cmdroot|su # get root}}
:{{cmdroot|mkdir /tmp/iso}}
:{{cmdroot|mkdir /tmp/cdimage}}
:{{cmdroot|mount -o loop <iso-bios-file> /tmp/iso}}
:{{cmdroot|cp /tmp/iso/* /tmp/cdimage}}
:{{cmdroot|cp <freedos-disk-image> /tmp/cdimage/floppy.img}}
:{{cmdroot|mkisofs -b floppy.img -o bootcd.iso /tmp/cdimage}}

finished.. now boot from cd and flash.

==Updating via CD/DVD Drive==

The whole thing gets more complicated if you neither have Windows nor a floppy drive installed. This is what this page is intended to describe.

Another possibility which works even without a CD-drive or network is to boot the disk image via the grub initrd mechanism.

Be aware that IBM officially does '''not''' support this! The official statement to my support request was:

<blockquote style="background: white; border: 1px solid black; padding: 1em;">
<pre><nowiki>
I'm afraid we only support the options listed on our web page and no you
can't burn a CD/DVD, however you can try to use an external USB FDD
(floppy) drive. The experts recommend a IBM USB FDD, however they have also
tested it with a Sony USB FDD drive.

In order to make sure the drive is recognised you can boot up the FDD with
a bootable dos diskette for w98
</nowiki></pre>
</blockquote>

But it seems to be possible as Mathias Dalheimer describes this [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/1998-January/009743.html here].

Another indication that it should work is that IBM uses PHLASH16.EXE (at least on T4x/p systems) to flash the BIOS into the chip. The same tool is used by [http://www.samsungpc.com/gb/support/p35/bios/bios-instructions.html other vendors] to flash the BIOS from bootable CD-ROMs.
{{WARN|Do '''not''' use the [http://syslinux.zytor.com/ SYSLINUX] image-loader [http://syslinux.zytor.com/memdisk.php MEMDISK] to boot the images! Some flash tools crash in that situation!}}

Some interesting but very technical information about the used flash tool can be found [http://www.paul.sladen.org/thinkpad-r31/wifi-card-pci-ids.html here].

===Creating a Floppy Image===
If you have created a boot floppy on another machine, you need to create an image file of that floppy. This can be easily done in linux by running a command line:

:{{cmdroot|1=dd bs=2x80x18b if=/dev/fd0 of=/tmp/floppy.img}}

You can also create a floppy image by using Ken Kato's [http://chitchat.at.infoseek.co.jp/vmware/vfd.html VMware's back]. It is a free Windoze tool that creates a virtual floppy drive and allows you to produce an image file ready to be ISO'ed. Note: you might have to 'manually' (through application's interface) assign the virtual drive a volume letter in order to be seen by IBM's application (as, by default, it seems not to do it).

You should verify this {{path|floppy.img}} as explained above.

===Creating a Bootable CD from a Floppy Image===
Once you have your floppy image, either from imaging a real floppy, or from extracting them via the cabextract method above, you need to make a boot CD out of it.

The eltorito bootable CD standard is a wonderful thing. What this means is that a bootable CD can be made with a bootable floppy in such as way that the CD believes that it is a 2.88 MB floppy drive. This allows you to replace a boot floppy by a boot CD in nearly all situations.

It is very easy to create such a bootable CD ISO image in Linux using the mkisofs tool. To do this run a command as follows:

:{{cmdroot|mkisofs -b bootfloppy.img -o bootcd.iso bootfloppy.img}}

Note: You don't strictly need the last {{path|bootfloppy.img}}, however some versions of mkisofs get confused about why you would want to create an iso with no contents, and thus won't let you. You don't actually care about the contents of the CD, you only care that the <tt>-b <boot image></tt> is applied to the CD. For more info on this read {{cmduser|man mkisofs}}.

You can now burn the {{path|bootcd.iso}} in your favorite CD burning program.

To get an overview which models have been tested with this version, here is a list:

===Does work:===
{| border="1" cellspacing="0" cellpadding="2"
| '''Model''' || '''Tested by'''
|-
| style="vertical-align:top;" | {{600X}} (2645) ||
*Jonathan Byrne <jonathan@RemoveThisToMailMe.yamame.org>. BIOS 1.11 from spsuit55.exe worked perfectly using cabextract/CD method.
|-
| style="vertical-align:top;" | {{A20p}} (2629-6VU) ||
*Chris Pickett http://www.sable.mcgill.ca/~cpicke/. BIOS 1.11 flashed fine with cabextract/CD method.
|-
| style="vertical-align:top;" | {{A21e}} (2628-JXU) ||
*Amit Gurdasani <gurdasani at yahoo dot com>. BIOS 1.13 flashed fine with cabextract/CD method. Alarmingly, after the BIOS update, the laptop beeped but did not shut down as was indicated onscreen -- that was frozen on the "do not shut down the laptop" screen. On power down and up again, the BIOS setup showed the newer BIOS image running, and Linux booted up fine. Linux ACPI didn't complain about the BIOS being too old either.
|-
| style="vertical-align:top;" | {{A31p}} (2653) ||
*Matthias Meinke largeeddy@gmx.at, BIOS 1.09 1NET15WW flashed fine with cabextract/CD method.
|-
| style="vertical-align:top;" | {{A31}} (2652) ||
*[[User:Wnoise|Aaron Denney]], BIOS 1.13 flashed fine with cabextract/CD method.
|-
| style="vertical-align:top;" | {{R31}} ||
*[http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/1998-January/009743.html Mathias Dalheimer]
*Sebastian Sauer (with cabextract/CD method)
|-
| style="vertical-align:top;" | {{R40}} ||
*Matthew Lambie, http://lambie.org
|-
| style="vertical-align:top;" | {{R50}} (1836-3SU) ||
*jlbartos <jlbartos at hotmail dot com>
|-
| style="vertical-align:top;" | {{R51}} (1829) ||
*Robert Uhl <rob dot uhl at gmx dot de>, Jellby <jellby at yahoo dot com>
|-
| style="vertical-align:top;" | {{R51}} (1830-RM7) ||
*Will Parker <stardotstar at sourcepoint dot com dot au> successfully flashed 3.20 using existing 3.04 ECP and retained custom boot splash.
|-
| style="vertical-align:top;" | {{R51}} (2887) ||
*Ingo van Lil <inguin at gmx dot de>
|-
| style="vertical-align:top;" | {{R52}} (1858) ||
*Stuart McCord <stuart dot mccord at gmail dot com> flashed both BIOS and ECP using cabextract, BIOS flashed first as on IBM website
|-
| style="vertical-align:top;" | {{T20}} ||
*Franz Hassels <fhassel at suse dot com>
|-
| style="vertical-align:top;" | {{T22}} ||
*Daniel Maier <nusse teamidiot de>
*Mathias Behrle (with cabextract/CD method, Version 1.07 => 1.12) --[[User:Mathiasb|Mathiasb]] 11:58, 14 December 2006 (CET)
*Bob Skaroff (cabextract/CD), 1.06 => 1.12
|-
| style="vertical-align:top;" | {{T23}} ||
*Bart Snapp <snapp at uiuc dot edu> Note: I followed IBM's instructions to flash the BIOS *first* and the Embedded Controller *second*.
*Moy Easwaran: BIOS 1.18 / EC 1.06a via cabextract and CD-boot. The BIOS-update exe generated errors in Windows 2000.
*Joe Renes: BIOS 1.18 / EC 1.06a on 2006-03-20 via cabextract and CD-boot. Piece of cake.
*Raphael Errani: BIOS 1.20 / EC 1.06a on 2006-11-06 via cabextract and CD-boot (using mkisofs). Worked without errors. 1st Bios, 2nd EC
|-
| style="vertical-align:top;" | {{T30}} ||
*Martin GÃ¼hring <guehring at gmail.com> BIOS 2.10 via cabextract the Non-Diskette BIOS -> mkisofs '''in the directory the exe was extracted''' to generate the iso -> burn the iso -> boot the CD
|-
| style="vertical-align:top;" | {{T40}} ||
*Sean Dague, http://dague.net
*Justin Mason, http://jmason.org
*Ivanhoe (Bios 3.19)
|-
| style="vertical-align:top;" | {{T40p}} ||
*Lukas KrÃ¤henbÃ¼hl, ismo at pop dot agri dot ch
*Thomas Achtemichuk, tom at tomchuk dot com. BIOS 3.15 flashed fine with cabextract/CD method
|-
| style="vertical-align:top;" | {{T41}} ||
*Lev Givon (Bios 3.15 / EC 3.04) <lev at columbia dot edu>
*Ernesto HernÃ¡ndez-Novich (Bios 3.19 / CP 3.04) < emhn at usb dot ve >
|-
| style="vertical-align:top;" | {{T41p}} ||
*Nils Newman, work great. (Version: Bios 3.14 / Embedded Controller 3.04)
|-
| style="vertical-align:top;" | {{T42}} ||
*Dan (BIOS 3.20 / EC 3.04, cabextract/CD method) <tronic171 at evilphb.org>
|-
| style="vertical-align:top;" | {{T42p}} ||
*Robert Schiele <rschiele@uni-mannheim.de>, Joern Heissler <joern@heissler.de>
|-
| style="vertical-align:top;" | {{T43}} ||
*Conrad Rentsch <Conrad dot Rentsch at t-online dot de> (Version: Bios 1.29 / Embedded Controller 1.06)
*Tom Heady <tom-thinkwiki.org@punch.net>
*Florian Boucault <florian at boucault dot ath dot cx> (Model : 1871-W34 & Version: Bios 1.23 / Embedded Controller 1.03)
|-
| style="vertical-align:top;" | {{X20}} ||
*Neil Caunt <retardis at gmail dot com>
|-
| style="vertical-align:top;" | {{X21}} ||
*Patrick Leickner <ranma at web dot de>, (BIOS 2.21->2.25 / EC 1.31->1.36) via non-disk/cabextract/mkisofs/cdrecord
|-
| style="vertical-align:top;" | {{X22}} ||
*David Emery <dave at skiddlydee dot com>, (EC 1.30, BIOS 1.32 using non-disk/cabextract/CD method)
|-
| style="vertical-align:top;" | {{X23}} ||
*Nils Faerber <nils dot faerber at kernelconcepts dot de> (Embedded Controller 1.30, BIOS 1.32 with cabextract/CD method)
|-
| style="vertical-align:top;" | {{X30}} ||
*Hella Breitkopf, [http://www.unixwitch.de/ www] (Embedded Controller 1.04, BIOS 1.07 with cabextract/CD method)
|-
| style="vertical-align:top;" | {{X31}} ||
*Grzegorz KuÅ›nierz <koniu at sheket dot org> (Embedded Controller 1.08, BIOS 3.01 with cabextract/CD method)
|-
| style="vertical-align:top;" | {{X40}} ||
*Robbie Stone <robbie@serendipity.cx>
|-
| style="vertical-align:top;" | {{Z60m}} ||
*[[User:Morle|Morle]] 13:09, 20 May 2006 (CEST), (Embedded Controller 1.14 with cabextract/CD method)
|}

===Does not work:===
{|
| '''Model''' || '''Tested by'''
|}

Please note that testing this is '''at your own risk'''!!!

==Updating via Grub and a Floppy Image==

{{WARN|Many have warned '''not''' to use the [http://syslinux.zytor.com/ SYSLINUX] image-loader [http://syslinux.zytor.com/memdisk.php MEMDISK] to boot the images! Some flash tools may crash in that situation! Proceed at your own risk!}}

Floppy images may be booted from Grub via a utility called [http://syslinux.zytor.com/memdisk.php MEMDISK], which may be compiled from the [http://www.kernel.org/pub/linux/utils/boot/syslinux/ '''SYSLINUX source''']. Copy the compiled memdisk image and the floppy image to your boot directory and configure grub as follows:

<blockquote style="background: white; border: 1px solid black; padding: 1em;">
<pre><nowiki>
title Bios Flash
kernel /boot/memdisk
initrd /boot/FILENAME.img
</nowiki></pre></blockquote>

Again, proceed at your own risk. This was tested on an R51 type 2888.

This also worked for me on a T41p type 2373. -- [[User:MrStaticVoid|James Lee]] 20:55, 8 May 2006 (CEST)

And it worked for me on a X31 type 2673-CBU. -- [[User:JanTopinski|Jan Topinski]], 18 September 2006

And it worked for me too on a X31 type 2672-CXU, very useful. -- [[User:TheAnarcat|TheAnarcat]] 16:21, 7 March 2007 (CET)

And it worked for me on two X40 type 2371 -- [[User:Antialize|Jakob Truelsen]], 19 Jan 2007 -- BIOS: 2.07 1uuj21us.exe -- ECP: 1.62 1uhj10us.exe

Not working for me on T43 type 2668-F7G -- [[User:Maus3273|Maus3273]] 20:48, 30 January 2007 (CET) -- BIOS: 1.29 1YUJ18US.IMG -- I got into the bios program, but the machine never restarts after initiating the upgrade.

==Updating with Network Boot Image==

BIOS, Embedded Controller (EC), CD/DVD and Harddisk firmware disks can be booted
over the network with [http://syslinux.zytor.com/pxe.php PXELINUX] as part of the [http://syslinux.zytor.com/ SYSLINUX] package.

This requires that you have a DHCP and tftp server configured and setup properly on
your network, and is probably not for the faint of heart.

Make sure the firmware bootdisk is in linux 'dd' format, as the self-extracting .exe disks
from the IBM website cannot be booted directly as such.

This worked on the {{R31}}, {{X22}}, {{T21}}, {{T30}} and {{T41p}} with various firmware updates.

==Updating via "IBM Predesktop area", suitable for model X (not have CDROM and floppy)==
It's so difficult to update BIOS and ECP without cdrom, floppy disk.
Don't know the reason why I couldn't update BIOS and ECP(1QHJ08US and 1QUJ19US) for my IBM Thinkpad X31.Hmm, may be cause of the dividing partition on my hard disk, that is:
<blockquote style="background: white; border: 1px solid black; padding: 1em;">
<pre><nowiki>
Primary: ext3, ext3, ntfs
Extended: Ntsf, fat32
Bootloader: GRUB
</nowiki></pre></blockquote>

No problem, you can use this way to do it:
* First, config in BIOS
In Security part:
# Remove all password of Subpervisor and Power on password
# Set Access IBM Predesktop Area to Normal
# Choose Enable "Flash BIOS updating by End User" in BIOS update Option.

In Config part:
# Choose Enable for Network flash over Lan

* Second, download the newest version of BIOS update and ECP update
Running: The program extract all files to the folder. There is a .img file (1QUJ19US.IMG, 1QUJ08US.IMG) in each folder.
Copy the imformation content in that img file and paste it to one FAT partition(using winimage or TotalCmd to extract)

as seen All files in 1QUJ19US.IMG is extracted to D:\BIOS
<blockquote style="background: white; border: 1px solid black; padding: 1em;">
<pre><nowiki>
695,764 $018E000.FL1
163 0691.HSH
2,049 0691.PAT
163 0694.HSH
2,049 0694.PAT
163 0695.HSH
2,049 0695.PAT
2,049 06D0.PAT
163 06D1.HSH
2,049 06D1.PAT
163 06D2.HSH
2,049 06D2.PAT
163 06D6.HSH
2,049 06D6.PAT
2,049 06D8.PAT
697 CHKBMP.EXE
8,128 COMMAND.COM
26 CONFIG.SYS
24,860 FLASH2.EXE
26 LCREFLSH.BAT
170 LOGO.BAT
330 LOGO.SCR
111,925 PHLASH16.EXE
91,648 PREPARE.EXE
45 PROD.DAT
22,252 QKFLASH.EXE
9,923 README.TXT
4,260 TPCHKS.EXE
39,666 UPDTFLSH.EXE
6,958 UPDTMN.EXE
12,501 USERINT.EXE
15,254 UTILINFO.EXE
</nowiki></pre></blockquote>

And all files in 1QUJ08US.IMG are: D:\ECP
<blockquote style="background: white; border: 1px solid black; padding: 1em;">
<pre><nowiki>
315,404 $018E000.FL2
8,000 COMMAND.COM
36 CONFIG.SYS
16,910 ECFLASH2.EXE
45 PROD.DAT
17,812 QKFLASH.EXE
990 README.TXT
4,260 TPCHKS.EXE
89,738 UPDTEC.EXE
31,134 UPDTFLSH.EXE
12,501 USERINT.EXE
15,226 UTILINFO.EXE
</nowiki></pre></blockquote>

* Okie, now plug AC Adapter, charge full battery to your laptop and continue third step:

** '''Flash BIOS first,'''
1. Power On, press blue button on keyboard: '''Access IBM'''

2. On "Utilities", double click " Diagnostic disk"

3. Your laptop will start PC-DOS, wait when this message appear:
<blockquote style="background: white; border: 1px solid black; padding: 1em;">
<pre><nowiki>
Please insert the first floppy diskette and
Press any key to continue
</nowiki></pre></blockquote>

4. Press Ctrl + Break, you will see :
<blockquote style="background: white; border: 1px solid black; padding: 1em;"><pre><nowiki>Terminate batch job (Y/N) ?</nowiki></pre></blockquote>

5. Okie, press Y, you will get DOS prompt like D:\
{{NOTE|D:\ is my RAMDISK, C:\ is my disk format as FAT.!}}

6. Enter to c:\BIOS
<blockquote style="background: white; border: 1px solid black; padding: 1em;">
<pre><nowiki>
c:
cd c:\BIOS
</nowiki></pre></blockquote>

7. Run FLASH2.EXE /u $018E000.FL1

8. Wait flash progress compelete and reboot.
** '''Flash ECP'''
Follow above instruction from step 1 to 5

6. Enter to c:\ECP
<blockquote style="background: white; border: 1px solid black; padding: 1em;">
<pre><nowiki>
c:
cd c:\ECP
</nowiki></pre></blockquote>

7. run UPDTFLSH.EXE $018E000.FL2

8. Follow UPDTFLSH's instructions

9. Wait flash complete and auto turn off computer.

I done it on my IBM Thinkpad X31.

Enjoy,

Tested by nm.

==Check List==

The following is important to remember:
# You must update '''both''' the Control Program and the BIOS at the same time if your current Control Program is not compatible with the new BIOS (see below)
# You must find versions of the Control Program and BIOS that are compatible. Not all of them are, so follow the readmes on the IBM website carefully to determine which are.
# You must update the Control Program '''before''' you update the BIOS

When the Control Program '''and''' the BIOS need updating, have both update disks or CDs ready. Update the Control Program first and the system should switch itself off when finished. Insert the BIOS update disk and proceed to update the BIOS. When it's all finished, enter setup, reset the settings to their defaults and reboot. Enter setup again and tweak the settings as necessary.

How to configure acpid

2007-02-04T17:00:51Z

TheAnarcat: tell people the script might already be enabled

__TOC__
==Introduction==
Basically, [[acpid]] just executes scripts residing in {{path|/etc/acpi/actions}}. Which script to launch at which event is configured in several files in {{path|/etc/acpi/events}}. All actions are documented in {{path|/var/log/acpid}}.

==Sources of Information==
*{{cmduser|man acpid}} holds detailed information on how to configure acpid.
*The [[ibm-acpi]] package includes example scripts in the {{path|config}} folder inside the tarball. They are a good starting point to adjust them to your needs.
*You also might want to have a look at the [[Configs#ACPI | ACPI section of the Configs page]] or the [[:Category:Scripts|Scripts]] repository.
*And you can find information about the event strings [[ibm-acpi]] generates for certain keys at the [[How to get special keys to work#ibm-acpi_events | Special Keys HOWTO]].

==Example: go to sleep on lid close==
To make the ThinkPad go to sleep when you close the lid, you need to add
an event handler for the lid event and an action script that takes care
of going to sleep and resuming.

===Event Script===
The event script needs to be created within {{path|/etc/acpi/events}} and can have any name you like.
In this case we call it lid because it will trigger the lid event. Do {{cmdroot|vi /etc/acpi/events/lid}} and make it look like this:
event=button/lid
action=/etc/acpi/actions/sleep.sh %e

The "event" line is a regular expression specifying the events we're
interested in. You can determine what the event strings are from looking at
{{path|/var/log/acpid}} after trying to suspend, close the lid, etc. .
You can find information about the event strings [[ibm-acpi]] generates for certain keys at the [[How to get special keys to work#ibm-acpi_events | Special Keys HOWTO]].

The "action" line is the command to be executed when these events are
dispatched. In this example we call the {{path|sleep.sh}} script residing in {{path|/etc/acpi/actions}} and pass the event description text using the %e placeholder.

For the script you can use the <tt>hibernate</tt> script of [http://www.suspend2.net/ Software Suspend 2] (it is independent of the [[Software Suspend 2|suspend-to-disk]] functionality), or any of many examples available on the web, such as the one below.

{{NOTE|To make your changes take effect after adding or modifying the events files you must do a <tt>kill -SIGHUP `pidof acpid`</tt>}}

===Action Script===
Our example {{path|/etc/acpi/actions/sleep.sh}} script looks as follows:

#!/bin/sh

# if launched through a lid event and lid is open, do nothing
echo "$1" | grep "button/lid" && grep -q open /proc/acpi/button/lid/LID/state && exit 0

# remove USB 1.1 driver
rmmod uhci_hcd

# sync filesystem and clock
sync
/sbin/hwclock --systohc

# switch to console
FGCONSOLE=`fgconsole`
chvt 6
/usr/sbin/radeontool light off

# go to sleep
sleep 5 && echo -n "mem" > /sys/power/state

# readjust the clock (it might be off a bit after suspend)
/sbin/hwclock --adjust
/sbin/hwclock --hctosys

# reload USB 1.1 driver
modprobe uhci_hcd

# turn on the backlight and switch back to X
radeontool light on
chvt $FGCONSOLE

{{NOTE|This parts of this script are now part of some distributions, like Debian Etch and you probably don't need to add this script. Look into /etc/acpi/lid.sh, for example.}}

====Explanations====
*The lid generates an event for both opening and closing thus requiring that we check its state and only act if it's closed.
*There have been problems encountered with the USB devices not working properly after a resume from suspend. To circumvent those we remove the USB driver prior to suspend and reload it afterwards.
*Note that the {{cmdroot|echo -n "mem" > /sys/power/state}} line does not return until we are revived. So there is only one event generated and there is no need to check the state of anything.
*The console switching code in this script is a special solution for [[Problem with LCD backlight remaining on during ACPI sleep|a problem where the backlight doesn't switch off]] on the {{T30}} and some other models. Before going to sleep, these models switch to console mode which causes the backlight to come back on. So we preemptively switch to console mode and turn off the backlight using [[radeontool]] before going to sleep.

==Troubleshooting==
*If something doesn't work, your first action should be a {{cmdroot|tail /var/log/acpid}}. It will tell you a lot about what is going on. If it has "Permission denied" errors, check the permissions of your {{path|/etc/acpi/actions}} scripts (especially make sure that the executable bit is set). Also check the permissions for other involved files like i.e. device nodes.
*For further problems look at the [[Problems with ACPI suspend-to-ram|Problems with ACPI suspend-to-ram page]].

[[Category:770X]] [[Category:770Z]] [[Category:A20m]] [[Category:A20p]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T20]] [[Category:T21]] [[Category:T22]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]] [[Category:Z60t]] [[Category:Z60m]] [[Category:TransNote]]

Table of thinkpad-acpi LEDs

2007-02-04T16:53:12Z

TheAnarcat: confirm a few leds

This table contains informations about which LED number is used for which LED in the [[ibm-acpi]] driver.

To test please do the following and add the blinking LED to the table. The moon symbol is the standby led.

<pre>
echo "0 blink" > /proc/acpi/ibm/led
echo "1 blink" > /proc/acpi/ibm/led
echo "2 blink" > /proc/acpi/ibm/led
echo "3 blink" > /proc/acpi/ibm/led
echo "4 blink" > /proc/acpi/ibm/led
echo "5 blink" > /proc/acpi/ibm/led
echo "6 blink" > /proc/acpi/ibm/led
echo "7 blink" > /proc/acpi/ibm/led
echo "on" > /proc/acpi/ibm/light
</pre>

<div style="font-size: 92%">
{| {{prettytable}}
|-
! [[:Category:A Series|A Series]]
! LED #0
! LED #1
! LED #2
! LED #3
! LED #4
! LED #5
! LED #6
! LED #7
! ThinkLight
! Notes
|-
! colspan=11 style="text-align:center;background:#efefef;" |
|-
! {{A22p}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{A30}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{A31}}
| {{PowerLED}} || {{Battery(amber)}} || {{Battery(green)}} || Ultrabay left || Ultrabay right || not found || Standby || {{Cunk}} || {{Cunk}} ||
|-
! colspan=11 style="text-align:center;background:#efefef;" |
|-
! [[:Category:G Series|G Series]]
! LED #0
! LED #1
! LED #2
! LED #3
! LED #4
! LED #5
! LED #6
! LED #7
! ThinkLight
! Notes
|-
! colspan=11 style="text-align:center;background:#efefef;" |
|-
! {{G41}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! colspan=11 style="text-align:center;background:#efefef;" |
|-
! [[:Category:R Series|R Series]]
! LED #0
! LED #1
! LED #2
! LED #3
! LED #4
! LED #5
! LED #6
! LED #7
! ThinkLight
! Notes
|-
! colspan=11 style="text-align:center;background:#efefef;" |
|-
! [[:Category:R31|R31]]
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{R40}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || {{Cunk}} ||
|-
! {{R50}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{R50p}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{R50e}}
| {{PowerLED}} || {{Battery(amber)}} || {{Battery(green)}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || Standby || {{ThinkLight(amber)}} ||
|-
! {{R51}}
| {{PowerLED}} || {{Battery(amber)}} || {{Battery(green)}} || {{Cunk}} || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || {{ThinkLight(amber)}} || 2883-ELU
|-
! {{R52}}
| {{PowerLED}} || {{Battery(amber)}} || {{Battery(green)}} || {{Cunk}} || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || {{ThinkLight(amber)}} ||
|-
! {{R60}}
| {{PowerLED}} || {{Battery(amber)}} || {{Battery(green)}} || {{Cunk}} || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || {{ThinkLight(amber)}} ||
|-
! {{R60e}}
| {{PowerLED}} || {{Battery(amber)}} || {{Battery(green)}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || Standby || {{ThinkLight(amber)}} ||
|-
! colspan=11 style="text-align:center;background:#efefef;" |
|-
! [[:Category:T Series|T Series]]
! LED #0
! LED #1
! LED #2
! LED #3
! LED #4
! LED #5
! LED #6
! LED #7
! ThinkLight
! Notes
|-
! colspan=11 style="text-align:center;background:#efefef;" |
|-
! {{T20}}
| {{PowerLED}} || {{Battery(amber)}} || {{Battery(green)}} || {{Cunk}} || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || {{ThinkLight(white)}} ||
|-
! {{T22}}
| {{PowerLED}} || {{Battery(amber)}} || {{Battery(green)}} || nothing || Ultrabay || nothing || nothing || Standby || {{ThinkLight(white)}} ||
|-
! {{T23}}
| {{PowerLED}} || {{Battery(amber)}} || {{Battery(green)}} || {{Cunk}} || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || {{ThinkLight(white)}} || 2647-4MG
|-
! {{T30}}
| {{PowerLED}} || {{Battery(amber)}} || {{Battery(green)}} || {{Cunk}} || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || {{ThinkLight(white)}} ||
|-
! {{T40}}
| {{PowerLED}} || {{Battery(amber)}} || {{Battery(green)}} || {{Cunk}} || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || {{ThinkLight(white)}} ||
|-
! {{T40p}}
| {{PowerLED}} || {{Battery(amber)}} || {{Battery(green)}} || {{Cunk}} || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || {{ThinkLight(white)}} ||
|-
! {{T41}}
| {{PowerLED}} || {{Battery(amber)}} || {{Battery(green)}} || {{Cunk}} || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || {{ThinkLight(white)}} || 2373-2gg
|-
! {{T41p}}
| {{PowerLED}} || {{Battery(amber)}} || {{Battery(green)}} || {{Cunk}} || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || {{ThinkLight(white)}} || 2373-GHG
|-
! {{T42}}
| {{PowerLED}} || {{Battery(amber)}} || {{Battery(green)}} || {{Cunk}} || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || {{ThinkLight(white)}} ||
|-
! {{T42p}}
| {{PowerLED}} || {{Battery(amber)}} || {{Battery(green)}} || {{Cunk}} || Ultrabay || {{Cunk}} || {{Cunk}} || Stanby || {{ThinkLight(white)}} || 2373-C96
|-
! {{T43}}, {{T43p}}
| {{PowerLED}} || {{Battery(amber)}} || {{Battery(green)}} || {{Cunk}} || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || {{ThinkLight(white)}} ||
|-
! {{T60}}
| {{PowerLED}} || {{Battery(amber)}} || {{Battery(green)}} || {{Cunk}} || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || {{ThinkLight(white)}} || 2007-49G
|-
! colspan=11 style="text-align:center;background:#efefef;" |
|-
! [[:Category:X Series|X Series]]
! LED #0
! LED #1
! LED #2
! LED #3
! LED #4
! LED #5
! LED #6
! LED #7
! ThinkLight
! Notes
|-
! colspan=11 style="text-align:center;background:#efefef;" |
|-
! {{X20}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{X21}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || Standby || {{ThinkLight(white)}} ||
|-
! {{X24}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{X30}}
| {{PowerLED}} || {{Battery(amber)}} || {{Battery(green)}} || Ultrabase || Ultrabay || Ultrabase Battery || {{Cunk}} || Standby || {{ThinkLight(white)}} ||
|-
! {{X31}}
| {{PowerLED}} || {{Battery(amber)}} || {{Battery(green)}} || Ultrabase || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || {{ThinkLight(white)}} ||
|-
! {{X32}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{X40}}
| {{PowerLED}} || {{Battery(amber)}} || {{Battery(green)}} || Ultrabase || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || {{Cunk}} ||
|-
! {{X41}}
| {{PowerLED}} || {{Battery(amber)}} || {{Battery(green)}} || Ultrabase || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || {{Cunk}} ||
|-
! {{X60}}
| {{PowerLED}} || {{Battery(amber)}} || {{Battery(green)}} || Ultrabase || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || {{Cunk}} ||
|-
! colspan=11 style="text-align:center;background:#efefef;" |
|-
! [[:Category:Z Series|Z Series]]
! LED #0
! LED #1
! LED #2
! LED #3
! LED #4
! LED #5
! LED #6
! LED #7
! ThinkLight
! Notes
|-
! colspan=11 style="text-align:center;background:#efefef;" |
|-
! {{Z60t}}
| {{PowerLED}} || {{Battery(amber)}} || {{Battery(green)}} || {{Cunk}} || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || {{ThinkLight(amber)}} ||
|-
! {{Z61m}}
| {{PowerLED}} || {{Battery(amber)}} || {{Battery(green)}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || Standby || {{ThinkLight(amber)}} ||
|-
! {{Z61p}}
| {{PowerLED}} || {{Battery(amber)}} || {{Battery(green)}} || {{Cunk}} || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || {{ThinkLight(amber)}} ||
|}
</div>

Mini-PCI Modem card

2006-04-19T17:46:37Z

TheAnarcat:

__NOTOC__
{| width="100%"
|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;">
=== Mini-PCI Modem card ===
This is a [[MiniPCI slot|Mini-PCI]] [[Modem Devices|Modem Adapter]] that is installed in a Mini-PCI slot.

=== Features ===
* Chipset: Ambit (formerly Lucent Microelectronics) [[Wikipedia:Softmodem|Softmodem]]
* PCI ID: 11c1:0449
</div>
|style="vertical-align:top" |
|}

=== IBM Partnumbers ===
IBM FRU PN: 08K3251, 08K3252, 08K3338, 08K3383, 08K3429, 08K4852, 08K4853, 08K4855, 91P7659<br>
IBM FRU PN (390X): 10L1296<br>
IBM FRU PN (570/E): 08K3412

=== Also known (in IBM literature) as.... ===
* Mini PCI modem card (Ambit)
* Mini PCI modem card (IBM CR)
* Mini PCI modem card (M2) (IBM)
* modem card Ambit
* Mini PCI modem

=== Linux driver ===
The Linux driver from [http://www.smlink.com/ SmartLink] may work.<br>
Latest version of this driver is 2.9.10 and supports both the 2.4 and 2.6 kernels.

Otherwise try using the slightly dated [http://www.heby.de/ltmodem/ ltmodem driver for Linux].<br>
The latest version of this driver is 8.31a and supports the 2.4 kernels.
alk@tut.by has prepared a version of the driver for 2.6 kernels.

Lastly, IBM supplies an outdated version (5.95) of the ltmodem driver, with only kernel 2.2 support [http://www-3.ibm.com/pc/support/site.wss/MIGR-4VFTT3.html here].

The Fax is supported by hylafax only, as mgetty-fax requires a class 2 modem, which this one isn't.

=== ThinkPads this card may be found in ===
* {{390E}}, {{390X}}, {{570}}, {{570E}}, {{600X}}
* {{A20m}}, {{A20p}}, {{A21e}}, {{A21m}}, {{A21p}}, {{A22e}}, {{A22m}}, {{A22p}}
* {{T20}}, {{T21}}, {{T22}}, {{T23}}
* {{X20}}, {{X21}}, {{X22}}, {{X23}}, {{X24}}
* {{TransNote}}

[[Category:Components]]