ThinkWiki - User contributions [en]

ThinkWiki talk:General disclaimer

2026-01-21T03:48:21Z

ThinkGNU: Added note, removed spam.

Anything forgotten?
Please tell us!

--[[User:Akw|akw]] 13:01, 27 Sep 2004 (CEST)

`"ThinkWiki" and the ThinkWiki logo are private property of Arno Willig` - what on earth does this mean? Is "ThinkWiki" trademarked? As for the logo, it includes the Linux penguin, which different drawings have been released under difference licenses, for example the GPLv2-or-later - regardless neither trademarks nor copyrights are property laws. I also see "the original authors of these ThinkWiki articles under the GFDL licensing scheme" - wouldn't that mean that the articles would really need to be released under a GFDL«version»-compatible license? [[User:ThinkGNU|ThinkGNU]] ([[User talk:ThinkGNU|talk]]) 04:48, 21 January 2026 (CET)

Category:500

2026-01-21T03:36:41Z

ThinkGNU: Seems × got corrupted into Ã—?

Category:R400

2025-10-27T04:29:01Z

ThinkGNU: I ran into a R400 with switchable Radeon graphics - the 2787-22M - so those do exist. I can't find any evidence that models with nvidia graphics existed.

{| 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 R400 ===
This page gives an overview of the ThinkPad R400.

=== Machine Type ===
{{NOTE|Switchable Graphics models are extremely rare but do exist.}}
* 2782, 2783, 2784, 2786, 2787, 2788, 2789 AMD Mobility Radeon HD3470
* 7438, 7439, 7440, 7443, 7445, 7446, 7447 Intel Graphics GMA 4500MHD

It appears that some models (such as 2784-R1U) were possibly shipped with nVidia Ge Force 9300M graphics

==== Standard Features ====
* One of the following processors:
** [[Intel Core 2 Duo (Merom)]] T5870 and 5670
** [[Intel Core 2 Duo (Penryn)]] P8400, P8600, T9400 and T9600
** [[Intel Celeron M| Intel Celeron M (Merom L)]] 575 and 585
* Chipset
** Mobile Intel® GM45 Express CS/ICH 9M-E
** Mobile Intel® GMA X4500 HD
** Mobile Intel® GL667 MHz (Celeron®)
* One of the following graphics adapters:
** [[Intel Graphics Media Accelerator 4500MHD]]
** [[Switchable Graphics]] with [[Intel Graphics Media_Accelerator 4500MHD|Intel GMA 4500MHD]] and [[ATI Mobility Radeon HD 3470]]
** [[nVidia GeForce 9300M]] (unconfirmed)
* One of the following displays:
** 14.1" wide: WXGA (1280 x 800, 107DPI, 185+ nit)
** 14.1" wide: WXGA+ (1440 x 900, 120DPI, 200+ nit)
*System Memory
** Up to 8GB of [[PC3-8500]] 1066MHz DDR3
*Harddrive
** 80, 160, 250 or 320GB 5400RPM SATA HDD
** 160, 200GB (FDE) 7200 RPM SATA HDD
* [[Intel Gigabit Ethernet (10/100/1000) PCI-Express]]
* Intel HD Audio with a [[CX20561]] codec
* [[ThinkPad Modem (MDC-3.0, 56kbps HDA)]]
* [[MiniPCI Express slot]] 1 with one of the following:
** [[Intel Wifi Link 5100 (AGN)]] (1x2AGN)
** [[Intel Wifi Link 5300 (AGN)]] (3x3 AGN)
** [[ThinkPad 11b/g/n Wireless LAN Mini-PCI Express Adapter II]]
* [[MiniPCI Express slot]] 2 with one of the following:
** None (not upgradable)
** [[Intel® Turbo Memory hard drive cache]] up to 2GB
** [[Wireless USB (UWB)]]
* 1 [[CardBus slot]] (Type 2)
* under which there one of:
** [[ExpressCard slot|ExpressCard/54 slot]]
** SmartCard reader
** [[Ricoh_R5C843|4-in-1 Memory reader]]
* [[Embedded Security Subsystem|Trusted Computing Group TPM 1.2]]
* [[Active Protection System]]
* [[Integrated Fingerprint Reader]] on select models
* [[ThinkPad_Bluetooth_with_Enhanced_Data_Rate_(BDC-2.1)|Bluetooth]] on select models
* [[UltraNav]] (TrackPoint / Touchpad combo)
* 1.3MP [[Integrated camera]] on select models
* [[Firewire Port|Firewire 400]] (IEEE1394a) on selected models
</div>
|style="vertical-align:top" |
[[image:ThinkPadR400.jpg|ThinkPad R400|300px]]
|}

[[Category:R Series]]

ATI Mobility Radeon HD 3470

2025-10-27T04:09:46Z

ThinkGNU: The driver has only some source code available - part of the driver is proprietary software that runs on the card. The driver has improved.

__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;">

This is a ATI video adapter
== Features ==
* Chipset: ATI RV620
* PCI ID: 1002:95c4
* PCI-E
* 128 or 256MB video memory
</div>
|style="vertical-align:top" |
|}

== Linux driver - Partially Source Available ==
The partially source-available "radeon" driver works quite well for 2D. It gets a bit hotter than fglrx. 3D support was previously limited as per the [https://web.archive.org/web/20121101090730if_/http://www.x.org/wiki/RadeonProgram old radeon game database], but it is now reported to [https://www.x.org/wiki/RadeonFeature/ work fine].

The patched version of radeon in GNU Linux-libre works fine with llvmpipe - 3D is just slow and suspend cannot work.

== Linux driver - Proprietary ==
Please look at the [[fglrx]] page for details

== ThinkPads this chip may be found in ==
* {{R400}}, {{R500}}
* {{T400}}

[[Category:Video Controllers]]

CompactFlash boot drive

2025-10-27T03:45:09Z

ThinkGNU: Grammar. It is incorrect that a single business came up with SSD write reduction. Linux is only a kernel. Occasionally de-fragmenting a large SSD improves performance as metadata frag. reduces it.

__NOTOC__
[[image:Addonics.JPG|thumb|Addonics Dual CF-IDE HDD Adapter with 8GB SanDisk Extreme IV CompactFlash]]
Changing your HDD for a CF boot drive (CompactFlash card on CF-PATA/SATA adapter) is an alternative to using SSD to boost the performance.

This is primarily done by ThinkPad {{X40}}, {{X41}} and {{X41 Tablet}} series owners due to the extremely slow speed of the 1.8" HDD.

Previously, using CompactFlash cards meant giving up on storage capacity. Nowadays the biggest available CF sizes are up to 100 GB so you even gain more storage space compared to a classic 1.8" HDD.

ThinkPads utilizing a PATA controller for the HDD slot can recognize both CF cards installed on a dual adapter. While newer ThinkPads, such as X41, which utilize a SATA controller, can only recognize the single card installed in the primary slot.

===Advantages of CF boot drive===
* Much faster access time (<1ms for CF, >20ms for 4200RPM HDD and >15ms for 5400RPM HDD)
* Higher read throughput for >8KB blocks (may differ depending on brand, model, partition type and cluster size)
* Higher write throughput for >64KB blocks (may differ depending on brand, model, partition type and cluster size)
* Minimal risk of mechanical damage due to shock and vibration. The [[Active Protection System]] is therefore unnecessary
* Does not generate any noise or vibrations
* (Possibly) a slight increase in battery life
* (Possibly) less heat being generated

===Disadvantages of CF boot drive===
* Lower read throughput for <8KB blocks (may differ depending on brand, model, partition type and cluster size)
* Lower write throughput for <64KB blocks (may differ depending on brand, model, partition type and cluster size)
* Lower capacity
* Higher price per GB
* Not officially supported
* Invoke boot error 2010 on certain ThinkPads, including the X41 series

{{NOTE|A often mentioned disadvantage of flash-based storage is the limited number of write cycles (typically 100,000 for the current generation Single-Level Cell (SLC) NAND, the type typically used in the faster CF cards). This should not however be as much of an issue because...<br>
* The 100,000 write cycles applies to each address block separately in the card, not to the card as a whole<br>
* The flash controller automatically distributes write operations evenly (wear leveling), so that the number of writes to each address block is kept low<br>
Therefore, it should take years of typical real world usage to render a flash memory card based on SLC NAND unusable<br>

However, manufacturers beginning in 2008 started using Multi-Level Cell (MLC) NAND to make SSDs. MLC NAND typically has only around 10,000 write cycles per block. But there are techniques that flash controllers can use to reduce write amplification and therefore extend SSD lifespan - for example a company called EasyCo claims Managed Flash Technology (MFT) "increases the write-life of Flash Disks more than 50-fold".<br>

If in doubt, check with the manufacturer directly for details.

See [http://www.storagesearch.com/ssdmyths-endurance.html] and [http://www.storagesearch.com/ssd-slc-mlc-notes.html] for more information.}}

==What you need==
* A passive CF to PATA/SATA adapter
** Sadly, the X30's native CF slot does not appear to be bootable, so you're stuck using an adapter in the PATA drive sled like everyone else.
* One or more CompactFlash cards with the following parameters:
** (For Windows) Identify itself as a fixed disk instead of removable media
** (Preferably) UDMA support
** (Preferably) 266X speed or better

==CF to PATA adapter==
===CF to PATA (IDE)===
These adapters will work with both ThinkPads with 1.8" and 2.5" HDD slot with PATA interface
* Addonics AD44MIDECF (single slot) [http://www.addonics.com/products/flash_memory_reader/ad44midecf.asp]
* Addonics AD44MIDE2CF (dual slot) [http://www.addonics.com/products/flash_memory_reader/ad44midecf.asp]

{{WARN|Many of the adapters sold in eBay may not be usable for x40 as their #1 pin is on the left side (looking from the top, usually marked by a white diagonal line). The #1 pin should be on the right side as the Addonics series. Flipping the insertion of popular "V B1" adapter works but there is no guarantee of performance and space may not permit. On the other hand PA-CF18H adapter has been reported to work fine and may be a good alternative for Addonics converters. Please read page 15 of the forum discussion link below this page.}}

{{WARN|The second (slave) slots on dual slot adapters, or a single slot configured as slave (Device 1), do not work on newer ThinkPads, including the {{X41}}, {{X41T}}, {{T43}}, {{T43p}} and {{R52}}. Because their ATA interface is actually connected to the SATA controller via a PATA-SATA bridge.
The second slot works fine on the others, like the X40, which use a native PATA controller, and 2 separated drives will be recognized.}}

{{WARN|On the {{X41}}, {{X41T}}, {{T43}}, {{T43p}} and {{R52}}, the [[Problem with non-ThinkPad hard disks|system will complain that an unsupported disk is installed (Error 2010)]], but will continue to boot after 5-10 seconds or after pressing enter (assuming you have a recent BIOS installed). The beeps can be muted by using the hardware mute button before the last shutdown/reboot}}

==CompactFlash cards==

===Speed===
While many CF cards claim to have high throughput, it's not necessarily a good indicator. As the claimed throughput is usually only attainable in specific situations (usually sequential and large block operations). But in typical usage as a boot drive, it usually involves lots of random and small block operations.

Therefore, the actual performance figures can only be found out via real world benchmarks.

Below is a list of some of the cards reported to be working, it's by no mean authoritative and final.

{{WARN|
Most CompactFlash cards by default identify themselves as '''removable media''' instead of '''fixed disk'''. Which is fine for GNU/Linux, but not for Windows.

If you have to use a CF card that has the type bits set to Removable and want to install Windows XP you can work around it as follows;
* Use fdisk & mkfs.fat or (g)parted in GNU/Linux to partition the drive with a FAT32 partition (you can boot from one of the LiveCD/LiveUSB distributions for this), making sure to set the partition as bootable.
* Start the install of Windows, during install you will be given the opportunity to migrate to NTFS
* After the install is finished you will need to install the Hitachi microdrive disk drivers (google for XPfildrvr1224.zip), which will mask the removable bits and should allow suspend and other operations that fail on a removable drive to work.}}

===Transcend 133X/266X/300X===
These cards are known to identify themselves as fixed disk via CF-IDE adapters without any manual intervention, and is of good value, and speed (for 266X/300X).

===SanDisk Extreme===
SanDisk used to provide a utility (when asked) under NDA to change the type bit to Fixed disk. It now refuses to provide it. This utility (ATCFWCHG.COM) however can be found for download at various places (try a search engine).

You will need to boot DOS and run it with the CF configured as either the master on the primary IDE interface or the master on the secondary interface. It will not work if the drive is attached as a slave or to any other interfaces.

To set a SanDisk Extreme adapter attached to the primary IDE interface to Fixed disk
ATCFWCHG.COM /P /F
To set a SanDisk Extreme adapter attached to the secondary IDE interface (Ultrabay) to Fixed disk
ATCFWCHG.COM /S /F

{{NOTE|It seems that the ATCFWCHG.EXE utility is incompatible with SATA to IDE bridges, such as found in the X41. In those cases you will have to connect the CF card to another computer or ThinkPad with a regular IDE (PATA) interface to change the flag, after which you can put it into the ThinkPad X41.}}

===SanDisk Ultra II 4 GB===
This card doesn't work with the Debian stable 2.6.26 kernel in a X41 tablet with SATA controller, it seems to be to slow.

===Kingston Ultimate===
The Kingston Ultimate CF card ships as CF-Removable, and although Kingston admits it is possible to change the type to Fixed disk, it was not willing when asked to provide a tool/application for this purpose.

But supposedly the Kingston card automatically changes ID based on the adapter used, so it will ID as fixed disk when used with an IDE-CF or SATA-CF adapter, but will ID as CF-Removable when used with a PCMCIA adapter.

===Silicon Power 300X===
to be updated

===Photofast 533X===
Works fine, read performance up to 43mbit/s acording to hdparm

==Storage capacity issues==
Due to the limited capacity for high speed CF cards, the space may not be enough for some users. As a typical OS may already consume 3-4GB already. Here are some suggestions on how to work around it. Each of the below suggestion has its pros and cons, and should be selected on a case-to-case basis.
* Put only the OS and frequently accessed files on the main CF card
* (If dual-CF is possible) Add a second CF card, which will show up as an additional drive. Moreover since the speed needs not be as fast as the main CF card, a slower card with larger capacity could be desirable.
* On certain ThinkPads, there is an internal card reader (e.g. CF on X20/X30, and SD/SDHC on X40/X41/X60/X61) which can house another flash card. However, the speed is certainly to be worse than connecting to the PATA/SATA interface.
* Use a PC Card/ExpressCard SSD drive. However, the price of SSD is likely to be more expensive than flash cards.
* Use a PC Card/ExpressCard flash reader to house another flash card.
* Use a USB drive. Take mind that the drive will stick out, which is less desirable as a permanent solution (appearance/damage/speed especially if USB 2.0 is not supported)
* (If network access is readily available) Store the files on a network drive (e.g. server disk/NAS)

==GNU/Linux issues==
With the Addonics adapters listed above (and possibly with other ones as well), the kernel's libata driver might warn about a 40-wire cable and default to UDMA/33 operation:

<pre>
[ 27.831146] ata1.00: limited to UDMA/33 due to 40-wire cable
[ 27.846808] ata1.00: configured for UDMA/33
</pre>

This has been observed with version 2.6.24 of the kernel, and it may affect older ones, too. A patch is available from [http://permalink.gmane.org/gmane.linux.ide/26879] that adds a <tt>force_cbl</tt> kernel parameter. After applying the patch and recompiling the kernel, you can then set <tt>force_cbl=80</tt>:

<pre>
[ 7.140864] ata1: forcing 80c
[ 7.140886] ata1.00: CFA: LEXAR ATA FLASH CARD, 20071016, max UDMA/100
[ 7.140890] ata1.00: 7831152 sectors, multi 0: LBA
[ 7.140908] ata1.00: forcing 80c
[ 7.141625] ata1.00: configured for UDMA/100
</pre>

With the patch enabled, the above system achieves 42MB/sec read performance according to <tt>hdparm</tt>. Without it, performance suffers: 23MB/sec.

==GNU/Linux tuning==
* edit /etc/fstab and add the option noatime to disable writing of last access timestamps on each file or directory access for each ext3 filesystem
LABEL=/ / ext3 defaults,noatime 1 1
* disable swap (remove swap volume from /etc/fstab), just make sure you have enough memory installed (as old memory is now cheap, should be easy to just max out the machine!)
* increase writeback time (add the following line to /etc/rc.local)
echo 1500 > /proc/sys/vm/dirty_writeback_centisecs
* remove beagle (if installed) from your system, it indexes the filesystem, but causes disk activity and keeps your cpu busy
rpm -e beagle beagle-gnome beagle-evolution

== Windows tuning==
{{NOTE|Instead of throwing together all kind of tweaks here, it's probably better to keep the tweaks be CF boot-specific... And link to another page showing the more generic tweaks...}}
Due to the space constraints of CF, you will want to do some tuning of Windows. In addition there are some tunes that help performance, and can even help in the case where your not changing your HDD to CF.
* Do a minimal Windows XP install (not a recovery) with nLite, this allows you to remove components of Windows before they even get to the HDD, such as Movie Maker, Windows Messenger and Outlook Express that you might not need, while at the same time slipstreaming the latest ServicePack (SP3 for XP). Alternatively if you cannot reinstall, you can try the public domain xplite program, but for it to be useful you need to pay, and it does not work with SP3.
* Disable NTFS from updating the last access of a file or directory on each access. This causes NTFS to do a write for each file read operation and writes are always slower, and with flash storage might not be a good idea, for this you need to set NtfsDisableLastAccessUpdate in your registry.
* Disable Indexing of the drive (drive properties)
* Compress the drive (NTFS only), this saves space and might in some cases even be faster as it will require less disk access (drive properties)
* Disable swap (system properties), just make sure you have enough memory (just max out the machine, RAM is cheap these days)
* Disable windows system restore (system properties), if you feel you can live without it. It reserves a defined amount of space for this purpose
* Do not enable Hibernation, it requires a huge hibernation file and suspend should be good enough.
* Disable programs from starting on boot that you do not need (do you really need Java, Adobe, Apple iTunes, etc from starting on boot each time?) with a program such as MSCONFIG (->Start ->Run -> msconfig)
* Disable Windows services that you do not need from starting on boot
* Only install the IBM/Lenovo applications you truly know you will need (in my case, only the Hotkey utility and the Wireless drivers package to be able to disable wireless with Fn-F5)
* Never do a full install of an application, do a custom install and prune the options to remove all the stuff you will never use
* Disable HW devices in device manager that you do not need (in my case, the Modem and Infrared)
* Only install drivers you actually need (video, ethernet, wireless and sound in my case), and remove the C:\DRIVERS directory after your done.
* Do not run defrag, it is pointless on CF type media and just causes unnecessary writes!
With this I was able to Install Windows XP (SP3) with Office 2003 (SP2), IE7, WMP 11, Symantec Client Security, Adobe acrobat reader, Firefox, Thunderbird, Pidgin and Palm Desktop in addition to the necessary drivers in under 4GB of an 8GB CF card on a ThinkPad X40.

==useful links==
* [http://forum.thinkpads.com/viewtopic.php?t=41568 ThinkPads Forum discussion on the subject]
* [http://www.hjreggel.net/cardspeed/index.html Flash memory speed - check out the UDMA CF link]
* [http://www.nliteos.com/ nLite - Utility to create a minimal Windows install CD with fixes and drivers]
* [http://www.daniel-boehmer.de/thinkpad-cf using Compact Flash cards as SSD alternative]

Problems with SATA and Linux

2025-10-27T03:06:02Z

ThinkGNU: You're installing more than just Linux. Linux is only a kernel and therefore it is repetitive to write kernel and the point is in fact the version of Linux. Can't work out the template problem.

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
Some ThinkPad models use an [[Intel ICH6-M]] SATA/PATA controller for the system hard disk. This causes several complications for GNU/Linux installation. The following lists these problems and known workarounds. Note that the details are often version- and distribution-specific.
{{HINT|The information on this page is outdated. As long as you have a fairly recent distribution with kernel 2.6.19 or newer, none of the issues described here apply}}
===Models using a SATA disk interface===
Models using a SATA controller and a SATA system disk:
*ThinkPad {{R60}}, {{R60e}}, {{R61}}
*ThinkPad {{T60}}, {{T60p}}, {{T61}}
*ThinkPad {{X60}}, {{X60s}}, {{X60_Tablet}}, {{X61}}, {{X61s}}, {{X61_Tablet}}
*ThinkPad {{Z60t}}, {{Z60m}}
*ThinkPad {{Z61e}}, {{Z61t}}, {{Z61m}}, {{Z61p}}
Models using a SATA controller and a PATA (IDE) system disk with a SATA-to-PATA bridge:
*ThinkPad {{T43}}, {{T43p}}
*ThinkPad {{R52}}
*ThinkPad {{X41}}, {{X41T}}

{{NOTE|Some of these problems (namely SMART support, power management and disk information) are solved in Linux 2.6.15 with the inclusion of libata pass-through. See the SATA driver [http://linux-ata.org/features.html features], [http://linux-ata.org/software-status.html software status] and [http://linux-ata.org/driver-status.html hardware status].}}
|}

==Hang on resume from suspend to RAM==

Linux versions prior to 2.6.16 (ata_piix) and 2.6.19 (ahci) do not support suspend and resume for SATA devices. As a result, the machine hangs upon the first disk access after resume. A kernel patch ([http://lkml.org/lkml/2005/5/2/46 LKML posting]) fixes this by adding SATA power management support.

Kernel 2.6.16 and later fixes this problem for most systems. The Thinkpad T60 and X60s still need some patches to get resume working using 2.6.16, see [[Talk:Problems with SATA and Linux#Patch against SATA-resume problem with T60|here]]. The T60p resumes properly with 2.6.17-rc6, the T60 and X60 should also. You need to enable ata_piix and disable AHCI in the bios. The latest fedora (FC5) 2.6.17 kernel seems to have fixed the resume problem on the T60p, still need to disable AHCI though. Applying [http://cvs.fedora.redhat.com/viewcvs/rpms/kernel/FC-5/linux-2.6-console-suspend.patch this FC5 patch] makes suspend-to-ram work with AHCI enabled.

===Patches===
* [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.12.diff Patch for kernel 2.6.12]
* [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.13-rc5.diff Patch for kernel 2.6.13-rc5]
* [http://lkml.org/lkml/2005/9/23/97 Patch for kernel 2.6.14]
* [http://www.xenotime.net/linux/SATA/2.6.15-rc/libata_suspend.patch Patch for kernel 2.6.15-rc4]
* [http://tpctl.sourceforge.net/tmp/sata_pm.2.6.15-rc6.patch Patch for kernels 2.6.15-rc6 through 2.6.15]

Some distributions already include this patch (e.g., {{Ubuntu}} Breezy, {{Gentoo}}'s gentoo-sources 2.6.15-r1), but some don't (e.g., {{Fedora}} 4). If your distribution doesn't include the patch, you will need to compile your own kernel with this patch included.

===Links===
* RedHat Bugzilla [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169201 bug 169201: "SATA drives fail on laptop suspend"]
* [http://lkml.org/lkml/2005/11/15/385 Fix to libata.h recommended on LKML] in case you get "ata: abnormal state 0x80 on port 0x1F7"
* RedHat Bugzilla [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=183138 bug 183138": "SATA failure after pm-suspend/resume ata1: handling error/timeout"]

==Failed resume from suspend to disk==

Suspend to disk (using [[swsusp]] or [[Software Suspend 2]]) needs to load the memory image from the SATA disk. For this to work, you either need an initrd with all the necessary SATA modules, or the SATA drivers compiled into the kernel.

==No DMA on DVD drive==

Using the IDE driver, DMA support cannot be enabled on an Ultrabay optical drive:

# hdparm -d1 /dev/hdc

/dev/hdc:
setting using_dma to 1 (on)
HDIO_SET_DMA failed: Operation not permitted
using_dma = 0 (off)

As a result, the optical drive is slow, and in particular, too slow to play video DVDs.

One workaround is to use the <tt>ata_piix</tt> driver (instead of the IDE driver) for the optical drive. This requires enabling the ATAPI support of the <tt>ata_piix</tt> driver (which as of 2.6.2x kernels, is working fine but wasn't stable in kernels before 2.6.18). You must also make sure that the IDE driver (<tt>ide-generic</tt>) does not grab the devices before <tt>ata_piix</tt>.

* Grab a recent kernel (must be 2.6.18 or newer)
* Do one of the following:
** Enable the <tt>ata_piix</tt> and <tt>libata</tt> drivers as built-in,
** Enable <tt>ata_piix</tt> and <tt>libata</tt> as modules (this is often the default) and add "<tt>options libata atapi_enabled=1</tt>" to your {{path|/etc/modprobe.conf}} (or the equivalent in your distribution).
* Do one of the following:
** Disable the IDE system.
** Build the IDE driver as built-in (this is often the default) and add the {{bootparm|hdc|noprobe}} kernel argument (e.g., in in {{path|/boot/grub/menu.lst}} or {{path|/etc/lilo.conf}}. Don't forget to run lilo after changes).
** Build the IDE driver as module and add "<tt>options ide hdc=noprobe</tt>" to your {{path|/etc/modprobe.conf}} (or the equivalent in your distribution).
* If you chose to use modules above, regenerate your <tt>initrd</tt> file.

Note : If you are using a ''Debian Sid'' system, and want to use Debian precompiled kernels, then type the following command in a ''root'' shell (This creates a new <tt>initrd</tt> with enabled ATAPI support of <tt>ata_piix</tt> and loads <tt>ata_piix</tt> before the IDE driver):
'''# echo options libata atapi_enabled=1>/etc/modprobe.d/atapienable && update-initramfs -u'''
(this is apparently not necessary with newer kernels)

<b>The following is likely obsolete with recent kernels</b>
Note : If your work was successful, your CD-ROM drive will no longer be accessible through /dev/hdc, but /dev/scd0 or /dev/sr0.

If this all doesn't work, use {{cmd|lspci -vn|}} to check whether one of the following chipsets is used in the Thinkpad:
{| border="1" cellspacing="0" cellpadding="2"
|-
!PCI ID
!Name
|-
|8086:7111
|Intel 82371AB/EB/MB PIIX4 IDE
|-
|8086:24db
|Intel 82801EB/ER (ICH5/ICH5R) IDE Controller
|-
|8086:25a2
|Intel 6300ESB PATA Storage Controller
|}
If yes, enable support for these chipsets has to be enabled by setting
#define ATA_ENABLE_PATA
in {{path|include/linux/libata.h}} (and report your ThinkPad model in the discussion page).

There have been reports that DVD burning doesn't work under this configuration, but it seems to work with kernel 2.6.14 and later (tested on a ThinkPad {{T43}} and {{T43p}} with a [[UltraBay Slim DVD Multi-Burner Plus]]).

===Problem with kernel 2.6.16 kernel and suspend2 2.2.1===
DVD access fails with kernel 2.6.16.* and [[Software Suspend 2|suspend2]] 2.2.1. Thia is fixed by later versions of suspend2, or by deleting the 4000-libata-rollup-2616-rc3.patch (see
[http://lists.suspend2.net/lurker/message/20060322.082452.873dc526.en.html this post notice] by Alexander E. Patrakov).

===Links===
* RedHat Bugzilla [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=163418 bug 163418: "can't enable DMA on DVD drive"]
* Enabling DMA on a SATA DVD drive, kernel 2.6.18 [http://thomer.com/howtos/dma_on_sata_dvd.html]

==No DMA on system hard disk==

In recent Linux versions, there are two modules capable of handling the ICH6 disk controller:
* <tt>ata_piix</tt>: the disk shows as {{path|/dev/sda}} and DMA is enabled.
* Generic IDE driver (<tt>ide-disk</tt>): the disk shows as {{path|/dev/hda}} and DMA is disabled.

The simplest way to enable DMA is to force the IDE driver to ignore the system hard disk by passing the {{bootparm|hda|noprobe}} and {{bootparm|hda|none}} kernel argument. The driver will then be handled by the <tt>ata_piix</tt> driver. Note that this will change its device name to {{path|/dev/sda}} (which may require changes in {{path|/etc/fstab}} and the boot loader) and may cause other problems as listed above.

(Observed on a ThinkPad T43 with Fedora Core kernel 2.6.13-1.1526_FC4.)
(Observed on a ThinkPad X40 with Debian kernel 2.6.18-4-686.) [[User:Hendry|Hendry]] 20:05, 11 June 2007 (UTC)

It may be necessary to set CONFIG_IDE to n and not pass the parameters mentioned above.

(Observed on a ThinkPad T60 with gentoo kernel 2.6.26)

==No SMART support==

Prior to kernel 2.6.15, the Linux SATA system did not support SMART commands (e.g., via smartctl).

The necessary capability is "libata pass-through", which was incorporated into Linux 2.6.15-rc1 and later. A patch is available for older kernels:
* Kernel 2.6.12: http://rtr.ca/dell_i9300/kernel/kernel-2.6.12/03_libata_passthru.patch
* Kernel 2.6.13: http://rtr.ca/dell_i9300/kernel/kernel-2.6.13/02_libata_passthru.patch
* Kernel 2.6.14: http://www.foo.fh-furtwangen.de/~koenigr/02_libata_passthru.fixed.again.patch
* Kernel 2.6.14 with the above suspend-to-RAM patch: http://linux.spiney.org/system/files?file=02_libata_passthru.fixed.patch

After applying the patch, run smartctl with the "-d ata" parameter:
:{{cmdroot|smartctl -d ata -a /dev/sda}}

From smartmontools version 5.37 "-d sat" is preferred to "-d ata". The smartctl command will auto-detect SATA disks so:
:{{cmdroot|smartctl -a /dev/sda}}
should just work. The smartd daemon still requires "-d sat" in /etc/smartd.conf .

==No disk power management==

Prior to kernel 2.6.15, the Linux SATA system did not support power management commands on these models.

The above patches for SMART support resolves this, and in particular enables the following commands:
* {{cmdroot|hdparm -y}} (spin down)
* {{cmdroot|hdparm -S num}} (automatic spin down timeout)
* {{cmdroot|hdparm -B num}} (advanced power management level)
Note that this command is still rejected:
* {{cmdroot|hdparm -M num}} (acoustic management)
(Tested with patched kernels 2.6.13.1 and 2.6.12-4 and a 60GB 7200RPM disk model HTS726060M9AT00.)

Refer to [[How to make use of Harddisk Power Management features]] for details about using
HD power management. Refer to [[Laptop-mode]] if you are interested into spinning down your HD.

==No disk information==

Prior to kernel 2.6.15, on these models the disk information could not be read by the standard commands such as:
*{{cmdroot|hdparm -i /dev/sda}}
*{{cmdroot|hdparm -I /dev/sda}}
The latter is fixed by the above patch for SMART support.

==No swapping of UltraBay device==

The <tt>ata_piix</tt> driver in mainline Linux supports hot-swapping and warm-swapping of PATA and SATA devices. This requires kernel 2.6.18 or newer (with older kernels, you must power off the laptop before swapping such devices). See [[How to hotswap Ultrabay devices#When_using_the_ata_piix_driver|How to hotswap Ultrabay devices]] for further information.

Swapping of the [[Ultrabay Slim Battery]] works out-of-the box.

==BIOS error 2010 on user-installed hard disk==

There is an issue with installing alternative PATA (IDE) hard disks as the system drive (this has nothing to do with Linux). Unless the disk is one of the few approved disks listed inside the BIOS, you will get an BIOS error 2010 during system boot, and the disk may operate unreliably. See [[Problem with non-ThinkPad hard disks]].

==CompactFlash module doesn't work==

Normally, PATA disks can be replaced with a solid-state [[CompactFlash]] module using a cheap PATA-to-CompactFlash adapter. However, there is a [http://thread.gmane.org/gmane.linux.ide/22400 report] that replacing the system disk with CompactFlash fails on a ThinkPad {{X41}}, possibly due to the SATA-to-PATA bridge. If so, the problem would probably occur also on the {{X41T}}, {{T43}}, {{T43p}} and {{R52}}.
I (KotCzarny) can confirm that {{X41T}} has this issue. READ is OK, but every attempt to do a WRITE results in timeouts as listed in gmane report. A quick and dirty workaround is to use generic ide driver (not sata one) to disable DMA. You won't get high speeds but at least it will work.

'''Update''' please check [[Compact Flash boot drive]] for more current information on using Compact Flash to boot

==RHEL3.0 Update 7 on T60p==

RHEL3.0 Update 7 will install on a {{T60p}}, but you need to make an adjustment. Both uni-processor and SMP kernels get installed, with the SMP kerrnel the default. However, the SMP kernel can't seem to find the disk drive. You can work around this by use "e" at the GRUB kernel prompt, then on the "kernel" line appending " noapic". After the system boots, you'll want to edit /boot/grub/grub.conf to add the " noapic" option to the kernel line as well.

==Mandriva 2006 on T60==

Mandriva 2006.0 has a problem with SATA on a {{T60}}, to fix this you need to make an adjustment. The install procedure can't seem to find the SATA disk drive, you can work around this by adding the "noapic" kernel option during CD/DVD boot. You *might* need to add this to lilo or GRUB for normal operations, after install completes. The problem with not using apic during normal operations is that you might have problems with power management, please see article on [[Software Suspend 2]]

==Problem burning CD/DVD==

To a CD/DVD problem, try to burn a CD/DVD as "root"-user on command-line with the option "-dummy" and "-v" enabled, do not use K3B or similar. Doing so you will get more informations and waste less CD/DVD's.

Experiment with the parameters "burnfree" and "dev". With cdrecord on debian etch, burnfree seems not work, disable it. With wodim on debian etch: try parameter "dev=/dev/scd0", the default "dev=1,0,0" seems not to work.

==Spurious NCQ completions==

It was initially thought the HDD controller software support for NCQ was buggy ([http://lkml.org/lkml/2007/6/6/15 LKML posting] and [http://lkml.org/lkml/2007/6/6/195 LKML posting]).
It was later found that it was a driver misinterpretation and there is no hardware problem ([http://article.gmane.org/gmane.linux.ide/26012 newsgroup posting]).

If you have an old kernel and get some warnings about spurious NCQ completions, you can safely ignore them. You are advised, anyway, to upgrade to a recent kernel.

How to hotswap Ultrabay devices

2025-10-27T02:53:54Z

ThinkGNU: R400 etc is not the latest generation anymore. The userland software is not merely tools. Spelling and grammar. Hdparm sets the password, not Linux.

The following discusses hotswap (AKA "hotplug") of devices in the [[Ultrabay]].

This page has a lot of old information. Some cleanup might be useful.

==Which driver?==
This may be confusing, so first a quick history lesson.

Older ThinkPads (up to the R51, T42p and X40) were fully IDE (PATA) for both the internal HDD and Ultrabay. For these there are two drivers, the modern libata based {{path|ata_piix}} and the old legacy {{path|piix}}/{{path|ide-disk}} combo. Most modern distributions will default to the {{path|ata_piix}} driver, which is really what you want anyway.

ThinkPads like the R52, T43, T43p, X41 and X41 Tablet are strange hybrids. They have a Serial-ATA (SATA) chipset for the internal disk controller, but the actual disk is still legacy IDE, using a separate SATA-PATA bridge chip. The Ultrabay, though, is still connected to the legacy IDE host controller. This results in a setup where the internal disk is handled by a SATA driver and the Ultrabay is handled by either {{path|ata_piix}} or {{path|piix}}/{{path|ide-disk}}.

ThinkPads like the R60, T60 and Z60 series are also hybrids, but they use a native SATA HDD internal. Ultrabay still uses legacy IDE (PATA) though. So just like with the previous models you end up with two separate drivers for the internal HDD and the Ultrabay.

Newer generation ThinkPads like the R400, R500, T400, T500, W500, W700, X200, and X301 are all fully SATA for both the internal HDD and the Ultrabay device, so both are handled by the same SATA driver.
{{Todo|Figure out in which category the X60 series ThinkPads truly belong. Some of these machines might have been shipped with a 1.8" HDD which is likely to be PATA, in fact the HMM even states so. But tabook and ltwbook only lists SATA models, so the 1.8" model might never have shipped. But even if it did there will be a SATA-PATA bridge chip, so from the OS it will look like SATA.}}

{| border="1" cellspacing="0" cellpadding="2"
|+Overview of disk interface types
! Thinkpad !! internal HDD !! Ultrabay !! Modern Driver !! Old Driver
|-
| {{A20m}}, {{A20p}}, {{A21e}}, {{A21m}}, {{A21p}}, {{A22e}}, {{A22m}}, {{A22p}}, {{A30}}, {{A30p}}, {{A31}}, {{A31p}} || Legacy 2.5" IDE (PATA) || Legacy IDE (PATA) || ata_piix || piix + ide-disk
|-
| {{R30}}, {{R31}}, {{R32}}, {{R40}}, {{R50}}, {{R50e}}, {{R50p}}, {{R51}} || Legacy 2.5" IDE (PATA) || Legacy IDE (PATA) || ata_piix || piix + ide-disk
|-
| {{R52}} || Legacy 2.5" PATA HDD with conversion to SATA || Legacy IDE (PATA) || ahci + ata_piix || -
|-
| {{R60}}, {{R61}} || 2.5" SATA || Legacy IDE (PATA) || ahci + ata_piix || -
|-
| {{R400}}, {{R500}} ||2.5" SATA || SATA || ahci || -
|-
| {{T20}}, {{T21}}, {{T22}}, {{T23}}, {{T30}}, {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}} || Legacy 2.5" IDE (PATA) || Legacy IDE (PATA) || ata_piix || piix + ide-disk
|-
| {{T43}}, {{T43p}} || Legacy 2.5" PATA HDD with conversion to SATA || Legacy IDE (PATA) || ahci + ata_piix || -
|-
| {{T60}}, {{T60p}}, {{T61}}, {{T61p}} || 2.5" SATA || Legacy IDE (PATA) || ahci + ata_piix || -
|-
| {{T400}}, {{T500}} ||2.5" SATA || SATA || ahci || -
|-
| {{X20}}, {{X21}}, {{X22}}, {{X23}}, {{X24}}, {{X30}}, {{X31}}, {{X32}} || Legacy 2.5" IDE (PATA) || Legacy IDE (PATA) || ata_piix || piix + ide-disk
|-
| {{X40}} || Legacy 1.8" IDE (PATA) || Legacy IDE (PATA) || ata_piix || piix + ide-disk
|-
| {{X41}}, {{X41t}} || Legacy 1.8" PATA HDD with conversion to SATA || Legacy IDE (PATA) || ahci + ata_piix || -
|-
| {{X60}}, {{X60s}}, {{x60t}}, {{x61}}, {{x61s}}, {{x61t}} || 2.5" HDD is SATA, 1.8" HDD is PATA with SATA conversion || Legacy IDE (PATA) || ahci + ata_piix || -
|-
| {{X300}} ||2.5" SATA || Legacy IDE (PATA) || ahci + ata_piix || -
|-
| {{X200}}, {{X200 Tablet}}, {{X301}} ||2.5" SATA || SATA || ahci || -
|-
| {{W500}}, {{W700}} ||2.5" SATA || SATA || ahci || -
|-
| {{Z60m}}, {{Z60t}}, {{Z61e}}, {{Z61m}}, {{Z61p}}, {{Z61t}} || 2.5" SATA || Legacy IDE (PATA) || ahci + ata_piix || -
|-
|}

{{NOTE|Debian users: at least up the the kernel released with Lenny, Debian applies a patch in the Debian kernel sources which prevents the use of <tt>ata_piix</tt> with PATA devices (like the IDE bus for the Ultrabay). You will have to either use an upstream kernel or (re)patch the Debian kernel sources.
You may want to have a look at the following Debian bug reports as well: [http://bugs.debian.org/444182 #444182], [http://bugs.debian.org/463833 #463833].}}

==Modern systems (using the <tt>ahci</tt> or <tt>ata_piix</tt> drivers)==
The following applies when using the <tt>ahci</tt> or <tt>ata_piix</tt> driver (which supercedes the old <tt>ide_disk</tt> driver).

You should at least be using a distribution with kernel 2.6.23. If you have a distribution with an older kernel, please update your distribution, as in addition to a newer kernel, you will need some of the newer userland software.

===Using libata-acpi and udev===

Starting from kernel 2.6.26-rc5, it's possible to use <tt>libata-acpi</tt> in combination with udev to hotswap. Please check if CONFIG_ATA_ACPI is enabled in your kernel configuration.

For 2.6.25, you need two patches which can be easily backported ([http://article.gmane.org/gmane.linux.acpi.devel/31159],[http://article.gmane.org/gmane.linux.acpi.devel/31369]).

Create a file {{path|/etc/udev/rules.d/50-thinkpad-ultrabay.rules}} with the following contents:
<pre>
ENV{BAY_EVENT}=="3", ACTION=="change", SUBSYSTEM=="scsi", RUN+="/usr/local/sbin/ultrabay_eject"
</pre>
Then ensure it has the right permissions
chown root:root /etc/udev/rules.d/50-thinkpad-ultrabay.rules
chmod 644 /etc/udev/rules.d/50-thinkpad-ultrabay.rules
For Red Hat/Fedora and other systems with selinux, you also need to set the security context:
chcon system_u:object_r:etc_runtime_t:s0 /etc/udev/rules.d/50-thinkpad-ultrabay.rules

Now create the below ultrabay-eject script

===Script for Ultrabay eject===

The following script does the following:
* Automatically unmounts the relevant filesystems and power off the Ultrabay when the Ultrabay eject lever is released. Screams if some filesystem can't be unmounted.

Create a executable file {{path|/usr/local/sbin/ultrabay_eject}} with the following content. Note if you want to be able to run it directly (not by the UDEV eject script), then you need to manually edit the DEVPATH variable near the top of the script.
<pre>
#!/bin/bash

# Change the following DEVPATH= to match your system, if you want to run this directly instead of having it called by the udev eject script
# To find the right value, insert the UltraBay optical drive and run:
# udevadm info --query=path --name=/dev/sr0 | perl -pe 's!/block/...$!!'

# Try to guess DEVPATH. It works with optical drive or Hard disk (or SSD)
if [ "$DEVPATH" = "" ]; then
# try to guess for CD
DEVPATH=$(udevadm info --query=path --name=/dev/sr0 | perl -pe 's!/block/...$!!')
if [ "$DEVPATH" = "" ]; then
echo "No optical device attached?"
echo "Try for harddisk"
# try to guess for sdb
DEVPATH=$(udevadm info --query=path --name=/dev/sdb | perl -pe 's!/block/...$!!')
fi
fi

shopt -s nullglob
export DISPLAY=:0.0 # required for notify-send
ULTRABAY_SYSDIR=/sys$DEVPATH

# Find generic dock interface for UltraBay
dock=$( /bin/grep -l ata_bay /sys/devices/platform/dock.?/type )
dock=${dock%%/type}
if [ -n "$dock" -a -d "$dock" ]; then
logger ultrabay_eject starting eject of $dock
else
logger ultrabay_eject cannot locate bay dock device
notify-send -u critical -t 100000 "ThinkPad Ultrabay eject failed" "Cannot locate bay dock device"
fi

# Umount the filesystem(s) backed by the given major:minor device(s)
unmount_rdev() { perl - "$@" <<'EOPERL' # let's do it in Perl
for $major_minor (@ARGV) {
$major_minor =~ m/^(\d+):(\d+)$/ or die;
push(@tgt_rdevs, ($1<<8)|$2);
}
# Sort by reverse length of mount point, to unmount sub-directories first
open MOUNTS,"</proc/mounts" or die "$!";
@mounts=sort { length($b->[1]) <=> length($a->[1]) } map { [ split ] } <MOUNTS>;
close MOUNTS;
foreach $m (@mounts) {
($dev,$dir)=@$m;
next unless -b $dev; $rdev=(stat($dev))[6];
next unless grep($_==$rdev, @tgt_rdevs);
system("umount","-v","$dir")==0 or $bad=1;
if ($bad == 1) {
system("logger","ultrabay_eject","ERROR unmounting",$dev,$dir);
system("notify-send -u critical -t 100000 \"Error unmounting $dir\" \"Unmounting of $dir on $dev failed!\"");
} else {
system("logger","ultrabay_eject","unmounted",$dev,$dir);
system("notify-send -u normal -t 5000 \"Unmounted $dir\"");
};
}
exit 1 if $bad;
EOPERL
}

if [ -d $ULTRABAY_SYSDIR ]; then
logger ultrabay_eject dock occupied, shutting down storage device $DEVPATH
sync
# Unmount filesystems backed by this device
## This seems to be very inelegant and prone to failure
unmount_rdev `cat $ULTRABAY_SYSDIR/block/*/dev \
$ULTRABAY_SYSDIR/block/*/*/dev` \
|| {
logger ultrabay_eject umounting failed
echo 2 > /proc/acpi/ibm/beep # triple error tone
notify-send -u critical -t 100000 "ThinkPad Ultrabay eject failed" "Please do not pull the device, doing so could cause file corruption and possibly hang the system. Unmounting of the filesystem on the ThinkPad Ultrabay device failed. Please put the eject leaver back in place, and try to unmount the filesystem manually. If this succeeds you can try the eject again"
exit 1;
}
sync
# Let HAL+KDE notice the unmount
sleep 0.5
# Unregister this SCSI device:
sync
echo 1 > $ULTRABAY_SYSDIR/delete
elif [ $( cat $dock/docked ) == 0 ]; then
logger ultrabay_eject dock reports empty
else
logger ultrabay_eject bay occupied but incorrect device path $DEVPATH
notify-send -u critical -t 100000 "ThinkPad Ultrabay eject failed" "Bay occupied but incorrect device path"
echo 2 > /proc/acpi/ibm/beep # triple error tone
exit 1
fi

# We need sleep here so someone can disconnect the bay and the drive
sleep 1

# Turn off power to the UltraBay
logger ultrabay_eject undocking $dock
echo 1 > $dock/undock

# Tell the user we're OK
logger ultrabay_eject done
echo 12 > /proc/acpi/ibm/beep
notify-send -u normal -t 10000 "Safe to remove device" "The ThinkPad Ultrabay device can now safely be removed"
</pre>
a possible fix for the notify not working thing is here [[Talk:How_to_hotswap_Ultrabay_devices#get_notify-send_working]]

Then make sure ownership and permissions are set correct
chown root:root /usr/local/sbin/ultrabay_eject
chmod 555 /usr/local/sbin/ultrabay_eject

If the <tt>ata_piix</tt> driver is built in the kernel, it will catch bay events and you will see the
following message in your system log:
<pre>
thinkpad_acpi: another device driver is already handling bay events
thinkpad_acpi: disabling subdriver bay
</pre>
You should load <tt>thinkpad_acpi</tt> before <tt>ata_piix</tt> if you want it to handle bay events.

===Script for Ultrabay insert===
{{WARN|Only needed for kernels prior to 2.6.26}}
Create {{path|/usr/local/sbin/ultrabay_insert}} with the following content:
#!/bin/bash
echo 12 > /proc/acpi/ibm/beep
sync
echo 0 0 0 > /sys/class/scsi_host/host1/scan

and set the right permissions
chown root:root /usr/local/sbin/ultrabay_insert
chmod 555 /usr/local/sbin/ultrabay_insert

===Using the generic bay driver and udev===
{{WARN|If you have kernel 2.6.26 or newer, please use the above [[#Using libata-acpi and udev]] method instead}}
Starting from kernel 2.6.23-rc3, it's possible to use the generic <tt>bay</tt> driver in combination with udev to hotswap. Please check if CONFIG_ACPI_BAY is enabled (module or built-in) in your kernel configuration.

Create {{path|/etc/udev/rules.d/ibm-ultrabay.rules}}:
ENV{BAY_EVENT}=="3", KERNEL=="bay.0", ACTION=="change", SUBSYSTEM=="platform", RUN+="/usr/local/sbin/ultrabay_eject"
ENV{BAY_EVENT}=="1", KERNEL=="bay.0", ACTION=="change", SUBSYSTEM=="platform", RUN+="/usr/local/sbin/ultrabay_insert"

Starting with kernel 2.6.28, the <tt>bay</tt> driver was removed from the mainline kernel. The <tt>dock</tt> driver replaced it completely. Make sure CONFIG_ACPI_DOCK is enabled in the kernel, and use the following udev rules:

ENV{EVENT}=="undock", KERNEL=="dock.2", ACTION=="change", SUBSYSTEM=="platform", RUN+="/usr/local/sbin/ultrabay_eject"
ENV{EVENT}=="dock", KERNEL=="dock.2", ACTION=="change", SUBSYSTEM=="platform", RUN+="/usr/local/sbin/ultrabay_insert"

However, the ultra_eject script needs to be changed, otherwise udev goes into an infinite event loop. It will send undock events every few seconds forever. That means as soon as the ultrabay is plugged in again, it will be immediately ejected. For kernels 2.6.28 and higher, the bay cannot be powered off using this method, so change the end of the script to read:
# Turn off power to the UltraBay:
if [ -d /sys/devices/platform/bay.0 ]; then
echo 1 > /sys/devices/platform/bay.0/eject
elif [ -e /proc/acpi/ibm/bay ]; then
echo eject > /proc/acpi/ibm/bay
fi
# Tell the user we're OK
echo 12 > /proc/acpi/ibm/beep

Alternatively, instead of modifying the script, use the libata-acpi method below.
This was tested on a T61p running Gentoo with tuxonice 2.6.28-r8 without any issues.

===udisks support===
Just like the HAL support mentioned below this is only about marking the device as hotpluggable.

Recently distributions do not use HAL anymore. On these systems Gnome, KDE, etc. use udisks instead to discover installed disks. So today most people will have to tell udisks that the ultrabay device is a removeable device. The HAL configuration described below does not work anymore.

Udisks reads device properties from udev. In order to force a device to be considered "removeable" we have to set the udev property "UDISKS_SYSTEM_INTERNAL" to "0". (man 7 udisks)
In order for this to work you need at least version 1.0.3 of udisks.

Here is an example of a udev rule that adds the property. You can add it to the file that contains the other utrabay rules (i.e. {{path|/etc/udev/rules.d/50-thinkpad-ultrabay.rules}}). You may have to adjust the DEVPATH.
<pre>
SUBSYSTEMS=="block", DEVPATH=="/devices/pci0000:00/0000:00:1f.1/host4/*", ENV{UDISKS_SYSTEM_INTERNAL}="0"
</pre>

Now tell udev to reread the rules:
<pre>
udevadm control --reload-rules
</pre>

Now your window manager should give you a notification when you plug in a disk into the ultrabay.

===HAL support===
{{HELP| If the script below does not work, please provide your lshal output on the [[Talk:How_to_hotswap_Ultrabay_devices]] page}}
{{NOTE| If your HAL version is older then 0.5.11, you need to replace "info.parent" with "storage.physical_device".}}

HAL support is only needed for proper notification to your desktop applications, such as Gnome and KDE. You will still require the udev script to handle the proper removal.

To tell HAL that devices connected to the UltraBay port are hotpluggable, you need to create a file {{path|/etc/hal/fdi/information/10-thinkpad-ultrabay.fdi}} with the following content:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 



<deviceinfo version="0.2">
<device>
<match key="/org/freedesktop/Hal/devices/computer:system.hardware.version" prefix="ThinkPad">
<match key="/org/freedesktop/Hal/devices/computer:system.hardware.vendor" string="IBM">


<match key="/org/freedesktop/Hal/devices/computer:system.hardware.version" contains_outof="A20;A21;A22;T20;T21;T22;X20;X21">
<match key="storage.bus" string_outof="pci;scsi">
<match key="info.parent" string="/org/freedesktop/Hal/devices/pci_8086_7111_scsi_host_0_scsi_device_lun0">
<merge key="storage.hotpluggable" type="bool">true</merge>
</match>
</match>
</match>


<match key="/org/freedesktop/Hal/devices/computer:system.hardware.version" contains_outof="T23;T30;X22;X23;X24;X30">
<match key="storage.bus" string_outof="pci;scsi">
<match key="info.parent" string="/org/freedesktop/Hal/devices/pci_8086_248a_scsi_host_0_scsi_device_lun0">
<merge key="storage.hotpluggable" type="bool">true</merge>
</match>
</match>
</match>


<match key="/org/freedesktop/Hal/devices/computer:system.hardware.version" contains_outof="A30;A31">
<match key="storage.bus" string_outof="pci;scsi">
<match key="info.parent" string="/org/freedesktop/Hal/devices/pci_8086_248a_scsi_host_scsi_device_lun0_0">
<merge key="storage.hotpluggable" type="bool">true</merge>
</match>
<match key="info.parent" string="/org/freedesktop/Hal/devices/pci_8086_248a_scsi_host_0_scsi_device_lun0">
<merge key="storage.hotpluggable" type="bool">true</merge>
</match>
</match>
</match>


<match key="/org/freedesktop/Hal/devices/computer:system.hardware.version" contains_outof="R50;R51;T40;T41;T42;X31;X32;X40">
<match key="storage.bus" string_outof="pci;scsi">
<match key="info.parent" string="/org/freedesktop/Hal/devices/pci_8086_24ca_scsi_host_0_scsi_device_lun0">
<merge key="storage.hotpluggable" type="bool">true</merge>
</match>
</match>
</match>


<match key="/org/freedesktop/Hal/devices/computer:system.hardware.version" contains_outof="R52;T43;X41;Z60">
<match key="storage.bus" string_outof="pci;scsi">
<match key="info.parent" string="/org/freedesktop/Hal/devices/pci_8086_2653_scsi_host_scsi_device_lun0">
<merge key="storage.hotpluggable" type="bool">true</merge>
</match>
</match>
</match>

</match>
<match key="/org/freedesktop/Hal/devices/computer:system.hardware.vendor" string="LENOVO">


<match key="/org/freedesktop/Hal/devices/computer:system.hardware.version" contains_outof="T60;Z61">
<match key="storage.bus" string_outof="pci;scsi">
<match key="info.parent" string="/org/freedesktop/Hal/devices/pci_8086_27df_scsi_host_scsi_device_lun0">
<merge key="storage.hotpluggable" type="bool">true</merge>
</match>
</match>
</match>


<match key="/org/freedesktop/Hal/devices/computer:system.hardware.version" contains_outof="R60;X60">
<match key="storage.bus" string_outof="pci;scsi">
<match key="info.parent" string="/org/freedesktop/Hal/devices/pci_8086_27c4_scsi_host_scsi_device_lun0">
<merge key="storage.hotpluggable" type="bool">true</merge>
</match>
</match>
</match>


<match key="/org/freedesktop/Hal/devices/computer:system.hardware.version" contains_outof="R61;T61;X300">
<match key="storage.bus" string_outof="pci;scsi">
<match key="info.parent" string="/org/freedesktop/Hal/devices/pci_8086_2850_scsi_host_scsi_device_lun0">
<merge key="storage.hotpluggable" type="bool">true</merge>
</match>
</match>
</match>


<match key="/org/freedesktop/Hal/devices/computer:system.hardware.version" contains_outof="R400;R500;T400;T500;W500;W700;X200;X301">
<match key="storage.bus" string_outof="pci;scsi">
<match key="info.parent" string="/org/freedesktop/Hal/devices/pci_8086_2929_scsi_host_0_scsi_device_lun0">
<merge key="storage.hotpluggable" type="bool">true</merge>
</match>
</match>
</match>


<match key="/org/freedesktop/Hal/devices/computer:system.hardware.version" contains_outof="T410;T510">
<match key="storage.bus" string_outof="pci;scsi">
<match key="info.parent" string="/org/freedesktop/Hal/devices/pci_8086_3b2f_scsi_host_0_scsi_device_lun0">
<merge key="storage.hotpluggable" type="bool">true</merge>
</match>
</match>
</match>

</match>
</match>
</device>
</deviceinfo>
</pre>

Then ensure it has the right permissions

chown root:root /etc/hal/fdi/information/10-thinkpad-ultrabay.fdi
chmod 644 /etc/hal/fdi/information/10-thinkpad-ultrabay.fdi

To check the effect, look at your lshal output, the section for your optical disk (/dev/sr0 typically) or your 2nd hdd (/dev/sdb typically) should have storage.hotpluggable = true after restarting your hal deamon or rebooting.

===Disable ultrabay at boot time===
To save some energy you can create an init.d start script to automatically "eject" the ultrabay at boot time<br />
vim /etc/init.d/stop-ultrabay

#! /bin/sh
### BEGIN INIT INFO
# Provides: stop-ultrabay
# Required-Start: $remote_fs $syslog
# Required-Stop: $remote_fs $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: stops the ultrabay
### END INIT INFO

# Script to shutdown ultrabay at boot time. To reenable, simply push the ultrabay eject lever
# and put it in again.
# By Frank Doelitzscher, 2010-08-04
#

# This things will always run
/usr/local/sbin/ultrabay_eject

# Carry out specific functions when asked to by the system
case "$1" in
*)
echo "This script runs automatically at boot time."
echo "It does not need any switches like start|stop"
exit 1
;;
esac
exit 0
Then ensure it has the right permissions<br />
chmod 755 /etc/init.d/stop-ultrabay

And make it known to the init subsystem<br />
update-rc.d -f stop-ultrabay start 90 2 3 4 5 .

It just gets a start script since it does not make sense to execute it at a shutdown or restart.<br />

This was tested on a T60 running Debian Squeeze with standard 2.6.32-5-686 #1 SMP without any issues.

==When using the <tt>ide-disk</tt> driver==
The following applies if you use the <tt>ide-disk</tt> driver for the UltraBay device.<BR>
<b>Note that essentially, you shouldn't be using this driver, and use ata_piix instead unless you're running an older kernel where ata_piix won't work for you</b>

Hotswapping is supposed to be supported as well, using either hdparm/[http://packages.debian.org/unstable/admin/hotswap Debian hotswap] or [[lt_hotswap]] to (un)register IDE devices. The latter is the recommended method with kernels from 2.6, since it will leave DMA working. However, for recent models (R52, T43, X41, Z60 and later) no method is known to work while maintaining DMA support; see [[Problems with SATA and Linux]].

Only IDE devices (HDD's, optical drives, zip drives) require special treatment - batteries, floppies and other devices can just be pulled from the bay, provided they are not mounted or in use at the time. However, you should still power them down first using the [[thinkpad-acpi]] eject function.

The [[thinkpad-acpi]] kernel module has an eject function ({{cmdroot|echo eject > /proc/acpi/ibm/bay}}). This only manages the ACPI calls to power down the device and the bay. It does not actually unregister the device from the IDE driver. {{cmdroot|cat /proc/acpi/ibm/bay}} shows "unoccupied" unless an IDE device is present, but the eject function still works and should still be used.

To unregister the device, you can either use the [http://packages.debian.org/unstable/admin/hotswap Debian hotswap] package, or [[lt_hotswap]]. Note that lt_hotswap doesn't seem to even build on recent (at 2.6.22 or newer, although it probably broke before 2.6.22) and on newer kernels, you should not build/load the old IDE PIIX (CONFIG_BLK_DEV_PIIX) and use the natively hotswapping ata_piix (CONFIG_ATA_PIIX) as explained on the top of this page.

[http://packages.debian.org/unstable/admin/hotswap Debian hotswap] also allows the drive to be swapped as a normal user by default, which is useful. You should use <tt>hotswap</tt> to unregister the device and then {{cmdroot|echo eject > /proc/acpi/ibm/bay}}. However, if you use this method on a 2.6 kernel, you will lose DMA support for the reinserted drive. This is due to kernel issues. This method was reported to work on a ThinkPad {{T23}} (kernels 2.6.8.1, 2.6.14.2 and 2.6.15-arch) and {{T42}} (kernel 2.6.13), but fails on a ThinkPad {{T43}} (kernel 2.6.14.3).

[[lt_hotswap]] is now the recommended method to un- and reregister the IDE device. It installs as a kernel module and has support for automatically unregistering (if loaded with the auto_eject=1 option) the device when the eject event is generated by [[thinkpad-acpi]]. It will leave DMA support intact. It has supported to work on a ThinkPad {{T22}} and {{T40}} and should work with many other models (but not recent models which require the <tt>ata_piix</tt> driver for disk DMA support). With the [[lt_hotswap]] kernel module loaded, run: {{cmdroot|modprobe -r ide_cd && modprobe -r cdrom && echo "MSTR eject" > /proc/acpi/lths}}

===HAL support===

HAL support also can also be configured To do so, create the file {{path|/etc/hal/fdi/information/10-ultrabay.fdi}} as follows:
<pre>
<?xml version="1.0" encoding="UTF-8"?> 

<deviceinfo version="0.2">
<device>


<match key="storage.bus" string="ide">
<match key="storage.physical_device" string="/org/freedesktop/Hal/devices/pci_8086_24ca_ide_1_0">
<merge key="storage.hotpluggable" type="bool">true</merge>
</match>
</match>

</device>
</deviceinfo>
</pre>
For more details see HAL section for ata driver.

==Password protected HDD==
{{WARN|Do not attempt to set a new HDD password with hdparm - if you succeed, it is likely that the drive will not unlock and it will not be possible to remove the password either.}}
There are multiple issues with hotplugging a password protected HDD. In short, it does not work from within the operating system. You will need to reboot, or use the suspend/wakeup procedure below, and let the BIOS do the unlock.
===hdparm===
While in theory you should be a able to use hdparm to unlock a drive, or set or remove a password. In practice none of it works the way it should.

First of all, by default the BIOS during POST will freeze the security settings of any drives that are present, preventing you from making changes until the drive is power cycled. You can see this by running the following command
# hdparm -I /dev/sdb|grep frozen
not frozen
If the above command simply returns 'frozen' any hdparm security commands will fail with an IO error. If this is an Ultrabay HDD you can simply remove the drive and hotplug it again to reset the drive.

If your drive has a PW set by the BIOS, any attempt to unlock it will result in an IO error.

But a fatal flaw is to use hdparm to actually set a password, if you do you will find the following issues
* setting a Master password will appear to succeed, but in fact does nothing
* setting a User password does succeed, but you will no longer be able to unlock or remove the password using either hdparm or the BIOS. hdparm will just give IO errors, and the BIOS will report the password being wrong. It is speculated that the BIOS applies some kind of hashing to the password, which is why setting the PW from the BIOS and setting the PW with hdparm is incompatible.

# hdparm --verbose --user-master u --security-disable test /dev/sdb
security_password="test"

/dev/sdb:
Issuing SECURITY_DISABLE command, password="test", user=user
oflags.lob_all=0x82, flags={ feat command }
oflags.hob_all=0x82, flags={ feat }
using LBA48 taskfile
outgoing cdb: 85 0b 26 00 00 00 00 00 00 00 00 00 00 40 f2 00
data: 00 00 74 65 73 74 00 00 00 00 00 00 00 00 00 00
SG_IO: ATA_16 status=0x2, host_status=0x0, driver_status=0x8
SG_IO: sb[]: 72 0b 00 00 00 00 00 0e 09 0c 01 04 00 00 00 00 00 00 00 00 e0 51 00 00 00 00 00 00 00 00 00 00
SG_IO: desc[]: 09 0c 01 04 00 00 00 00 00 00 00 00
ATA_16 stat=51 err=04 nsect=00 lbal=00 lbam=00 lbah=00 dev=e0
I/O error, ata_op=0xf2 ata_status=0x51 ata_error=0x04
SECURITY_UNLOCK: Input/output error

*[https://bugzilla.redhat.com/show_bug.cgi?id=603018 bug report against hdparm]

===Letting the BIOS unlock the disk by suspending the computer===

A password protected disk can be unlocked by ensuring the laptop has been suspended '''before''' inserting the disk into the Ultrabay. The device being removed should still be ejected before suspending the laptop.

Upon waking up (resuming) the computer the BIOS should prompt for the password, and provided you enter it correctly, will unlock the disk. Once Linux regains control it may be necessary to re-scan the SCSI bus to find the disk and make it available, using the command "sudo rescan-scsi-bus.sh".

This is confirmed to work on a T61 running Ubuntu 8.04, (kernel 2.6.24) with the scsitools package installed.

===libata EH going crazy===
hotplugging a password protected HDD causes the libata error handler to go crazy

ACPI: \_SB_.PCI0.IDE0.SCND.MSTR - docking
ata2: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0xe frozen
ata2: ACPI event
ata2: soft resetting link
ata2.00: ATA-6: HTS726060M9AT00, MH4OA6DA, max UDMA/100
ata2.00: 117210240 sectors, multi 0: LBA
ata2.00: limited to UDMA/33 due to 40-wire cable
ata2.00: configured for UDMA/33
ata2: EH complete
scsi 1:0:0:0: Direct-Access ATA HTS726060M9AT00 MH4O PQ: 0 ANSI: 5
sd 1:0:0:0: Attached scsi generic sg1 type 0
sd 1:0:0:0: [sdb] 117210240 512-byte logical blocks: (60.0 GB/55.8 GiB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdb:

After which there are hundreds of errors such as these...
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: BMDMA stat 0x5
ata2.00: failed command: READ DMA
ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in
res 51/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)
ata2.00: status: { DRDY ERR }
ata2.00: error: { ABRT }
ata2.00: configured for UDMA/33
ata2: EH complete

Basically what is happening is that libata is ignoring the ATA IDENTIFY data, that reports that the drive is locked, and just tries to scan for every partition type possible.
*[https://bugzilla.kernel.org/show_bug.cgi?id=16181 Bug report against libata]

===udisks===
lastly, there should be some userland support to detect the password protected HDD and prompt you for a password or retrieve the password from gnome-keyring. But that will require hdparm to be able to unlock the HDD first, and to figure out if the BIOS is doing some kind of hashing and how.

*[https://bugs.freedesktop.org/show_bug.cgi?id=23110 bug report against udisks]

[[Category:Scripts]]
[[Category:HOWTOs]]

How to reduce power consumption

2025-10-27T02:37:23Z

ThinkGNU: If there's a single Wi-Fi card, it's generally wlan0, not eth1. Grammar. 1000BASE-T require auto-negotiation and most networks are 1000BASE-T now - with the exception of now rare 100BASE-TX networks.

Reducing system power consumption will extend battery life, reduce system
temperature and (on some models) reduce system fan noise.
Power consumption can be greatly improved from a stock distribution configuration
to a fine tuned system. The general rules are :
* Unload drivers for unused devices (ie. USB 1.1, Yenta/PCMCIA, Wireless, IRDA, Bluetooth, ...)
* Reduce polling on devices (drives, USB subsystem, nvram, use SATA AN, ...)
* Reduce hard drive activity
* Reduce LCD brightness to the minimum you can stand
* Reduce CPU wakeups, so it can stay longer in deep power saving c-states
* Make use of every hardware devices availables power saving features (AHCI ALPM, USB autosuspend, Alsa and Wireless powersaving modes, HPET timers, ...)

==Tools==
Arjan van de Ven's [[PowerTOP]] utility
is a gold mine to improve energy efficiency, but is almost only CPU-oriented. This tool helps to easily detect
the top power offenders, both userland and kernel modules, which prevent the use of CPU power saving mechanisms and sometime suggest
fixes accordingly.
PowerTOP users collected some [http://www.lesswatts.org/projects/powertop/known.php tips & tricks]
and an informative [http://www.lesswatts.org/projects/powertop/faq.php faq].

Alternatively (or complementary) to PowerTOP, running <code>strace -p $(pidof yourapp)</code>
for all your favorite or background running applications while they are expected to be
idle, will show the misbehaviors.

Beside CPU wakeups, disks spins are also power hungry. To detect what make your disk spinning,

sysctl vm.block_dump=1

will list all applications causing disks wakeups on the kernel's dmesg.
Other useful tools for this purpose are blktrace, iostat and lm-profiler
(from laptop-mode-tools suite).

See also [[#Misbehaving Userland]].

==BIOS settings==
===Enabling Power Management===
Some Thinkpad BIOS (like 2.08 BIOS on {{X40}}) offer two very lame options,
with a very misleading online help (saying "Usually not needed"). That's

CPU power management: (default disabled)
PCI bus power management: (default disabled)

You should indeed ''enable'' them, else the deepest C3 and C4 ACPI C-states
are disabled.

===Disabling I/O Ports===
The BIOS (at least version 3.11 on {{X200}}) can also be used to disable I/O ports, like PCMCIA/CardBus. Although this requires a reboot to change settings, using the BIOS rather than a configuration file will survive distribution changes and may make it easier to remember how to re-enable a port. Disabling these devices can reduce power consumption by several watts.

==CPU==
Look at:
* [[How to make use of Dynamic Frequency Scaling]]
* [[Pentium M undervolting and underclocking]]

A good thing to keep in mind is that every CPU wakeup, even if it's for
a trivial light job, reduce the time the CPU stays on a deep power
saving C-state (like C3 or C4). Therefore you should ensure your applications
stay really idle when they meant to be idle (track shorts select timeouts
in loop, etc. with [[PowerTOP]]).

Also note that manually locking the CPU in the lowest P-state (frequency)
available is '''not''' an efficient way to improve battery lifetime. This will
cause the CPU to stay longer in C0 (power hungry C-state) doing hard work when
there is something to do, while it could have done this work faster by augmenting
the CPU freq, and returned back faster to a deeper, economic, C-state and to a
lower frequency (P-state).
The best is to let the kernel select the appropriates CPU frequencies by itself
with the help of in kernel CPU governors.
Have a look at [http://www.bughost.org/pipermail/power/2007-May/000166.html this explanation]
from Intel's kernel developer Arjan van de Ven.

==Kernel settings and patches==

===General settings===
The 2.6.21 kernel brought some very effective changes (like [[dynticks]]).
Later, 2.6.24-rc2 brought a lot of other power efficiency improvements.
If it's not already on your distribution and you value power efficiency,
you may think about compiling a recent kernel yourself.

Here are a few options (beside the ACPI and APM related one) that matter to
reduce power consumption or to help diagnosing consumers:

# From PowerTOP's FAQ:
CONFIG_NO_HZ
CONFIG_HIGH_RES_TIMERS
CONFIG_HPET
CONFIG_HPET_TIMER
CONFIG_CPU_FREQ_GOV_ONDEMAND
CONFIG_USB_SUSPEND
CONFIG_SND_AC97_POWER_SAVE
CONFIG_SND_HDA_POWER_SAVE
CONFIG_SND_HDA_POWER_SAVE_DEFAULT=3
CONFIG_TIMER_STATS
CONFIG_ACPI_BATTERY
CONFIG_CPU_FREQ_STAT
CONFIG_INOTIFY

# Not from the PowerTOP FAQ:
CONFIG_BLK_DEV_IO_TRACE
CONFIG_X86_ACPI_CPUFREQ
CONFIG_X86_SPEEDSTEP_CENTRINO depreciated as of kernel 2.6.24, use CONFIG_X86_ACPI_CPUFREQ
CONFIG_X86_SPEEDSTEP_ICH
CONFIG_X86_SPEEDSTEP_SMI
CONFIG_CPU_IDLE
CONFIG_CPU_IDLE_GOV_LADDER
CONFIG_CPU_IDLE_GOV_MENU

Those options are already in Fedora Core 7 and Ubuntu Gutsy (not Feisty) default i686 kernels.
PowerTOP FAQ also suggest to '''disable'''
CONFIG_IRQBALANCE and CONFIG_ACPI_DEBUG.

Also, you need to properly set APM and ACPI. Look at:
* [[Power Management]]
* [[How to make use of Power Management features]]

=== Kernel boot and module loading options ===
If you have an Intel chipset ICH5 or later (cf. lspci output), as in most modern Thinkpads, you should
be using the integrated HPET timer (saves about 30 CPU wake ups per second). To see if
hpet is enabled on your laptop:

grep hpet /proc/timer_list

If this does not display "Clock Event Device: hpet", then add

hpet=force

{{WARN|The ICH4 does have an HPET, but it is disabled for a good reason: Intel didn't test/validade it! Use of the ICH4 HPET is '''not''' recommended}}

to your kernel boot options (usualy in /boot/grub/menu.lst or lilo.conf).
Note that "hpet=force" is only available by default in 2.6.24-rc2 and above
(or as a separated patch for 2.6.22 and 2.6.23, see below).

On modern ThinkPads the HPET timer is automatically detected and enabled. On certain older machines hpet=force is required such as on the following machines:
* {{T30}}, {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}
* {{X22}}, {{X23}}, {{X24}}, {{X30}}, {{X31}}, {{X40}}
* {{A31}}
* {{SL500}}

{{HELP|please add your ThinkPad to the above list, if <nowiki>hpet=force</nowiki> was required}}

===Useful Patches===

Thomas Gleixner High Resolution Timers (hrt) patchset brings many improvements,
like the cpuidle work and Udo A. Steinberg and Venki Pallipadi "force
enable HPET" patches (non HPET timers causes about 20-40 CPU wakeups/second, but
HPET is often hidden by the BIOS due to Windows XP deficiencies). Those are
fully merged in 2.6.24-rc1 vanilla kernel.
See http://www.tglx.de/projects/hrtimers/

Kristen Carlson Accardi from Intel has a patchset to turn on "Aggressive
Link Power Management" (ALPM) for the AHCI driver (for SATA bus). Also from
Accardi, SATA Asynchronous Notification (SATA AN), alows SATA link to notify
media insertions (thus avoid hal polling the cdrom). Those patches were merged
in 2.6.24-rc2 kernel (AN needs also support in hal to be used).
See: http://www.kernel.org/pub/linux/kernel/people/kristen/patches/SATA/alpm/

As of now (2.6.24-rc8), the linux kernel doesn't support PCI Express power
management (aka PCIe ASPM, aka PCIe LPM). Shaohua Li from Intel submited a
patch on LKML (http://lkml.org/lkml/2008/1/17/544 ) though, and reported it
to reduce power consumption by 1.3 watts for a system with three PCIe links.

The [[HDAPS]] disk protection systems can reduce battery life.
Matthew Garrett provides [http://www.linuxpowertop.org/patches/hdaps.patch a patch]
that prevents hdaps kernel module to generate interrupts when
this feature isn't used.

===Useful sysctls===
The meaning of those settings is explained case by case on the relevant
sections of this document. But for convenience sake, we group them here too.

Note that the "ondemand" scaling governor is recommended by Intel developers
for energy efficiency: it's expected to be more efficient than the "powersave"
governor, or than userspace daemons (like cpufreq-utils, cpufreqd, powernowd...).
Look [http://www.bughost.org/pipermail/power/2007-May/000071.html here],
[http://www.bughost.org/pipermail/power/2007-May/000073.html here], or
[http://www.bughost.org/pipermail/power/2007-May/000166.html here] for a
kernel developer explanation about "ondemand" being better on modern Intel CPUs.

The "link_power_management_policy" tunable won't be available unless you
run a 2.6.24-rc2 or more kernel, or applied Kirsten patchset, have an Intel
AHCI compatible chipset, and use SATA drives.

echo 5 > /proc/sys/vm/laptop_mode
echo 0 > /proc/sys/kernel/nmi_watchdog
echo Y > /sys/module/snd_ac97_codec/parameters/power_save
echo 1 > /sys/devices/system/cpu/sched_mc_power_savings
echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 1500 > /proc/sys/vm/dirty_writeback_centisecs
for i in /sys/bus/usb/devices/*/power/autosuspend; do echo 1 > $i; done
# those sysctl's are only available if you have an AHCI compatible SATA
# controler and use kernel > 2.6.24-rc2 (or use Kristen ALPM patchset) :
echo min_power > /sys/class/scsi_host/host0/link_power_management_policy
echo min_power > /sys/class/scsi_host/host1/link_power_management_policy
echo min_power > /sys/class/scsi_host/host2/link_power_management_policy

If you're running a kernel older than 2.6.22 do this. Not needed for kernels 2.6.22 onward:

cd /sys/devices/system/cpu/cpu0/cpufreq
cat ondemand/sampling_rate_max > ondemand/sampling_rate

==ATA drives==
Hard drives and CDRom drives spinning is very costly. To improve battery
lifetime, you should reduce disks access (or devices polling) the more you
can.

===Hard Drives===

The files access time update, while mandated by POSIX, is causing lots of
disk write access; even accessing files on disk cache may wake the ATA or USB
bus. If you don't use this feature, disable it by adding the <tt>relatime</tt>
option to all relevant lines in the /etc/fstab, for example:
/dev/sda1 / ext3 relatime,errors=remount-ro 0 1

(On older kernels you may need to use <tt>noatime</tt> instead of <tt>relatime</tt>.)

Also consider merely using a larger value for the <tt>commit</tt> option. This defines how often changed data is written to the disk (it is cached until then). The default value is 5 seconds.

See man mount(8) for details on how the <tt>rel/noatime</tt> and <tt>commit</tt> options work.

Use laptop_mode to reduce disk usage by delaying and grouping writes. You should enable
it, at least while on battery. See [[Laptop-mode]] for more details:

echo 5 > /proc/sys/vm/laptop_mode

The default kernel dirty page writeback frequency is very conservative. On
a laptop running on battery, one might find more appropriate to reduce it:

echo 1500 > /proc/sys/vm/dirty_writeback_centisecs

Some power saving hard drives features can be activated with hdparm (beware
that "-B 1" may reduce your drive lifetime, if you have lot of intermittent
disk activity causing lots of heads load/unloads: so reduce I/O activity first,
as explained above, in order to get longer disks idling periods).
For more details look at [[How to make use of Power Management features]] :

hdparm -B 1 -S 12 /dev/sda # and/or any other disk device

====SATA Link Power Management====
On kernels 2.6.24 and new this enables SATA Link Power Management:
echo min_power > /sys/class/scsi_host/host0/link_power_management_policy
echo min_power > /sys/class/scsi_host/host1/link_power_management_policy
echo min_power > /sys/class/scsi_host/host2/link_power_management_policy

Disable it by replacing <code>min_power</code> with <code>max_performance</code>.

Which host-number to use depends on your laptop. It is typically 0 for the main drive, but for example on the T61 the 0 and 1 are for the pata interface used for the optical drive, and the main hard-disk is on host2.

On Ubuntu Hardy Heron with a 2.6.24-16 kernel, a suspend/resume cycle is much quicker if you disable SATA Link Power Management before initiating the suspend. As of Intrepid Ibex and kernel 2.6.27, this should be fixed. ([https://bugs.launchpad.net/linux/+bug/234047 Launchpad bug 234047], [http://bugzilla.kernel.org/show_bug.cgi?id=10817 Kernel bug 10817])

====Laptop Mode Tools====

The [http://samwel.tk/laptop_mode/ Laptop Mode Tools] utility implements many of the above power-saving measures from disks, and some others.

===Optical drive===
The optical drive is reported to consume power even when not accessed. See

* [[How to hotswap UltraBay devices|Eject the UltraBay optical drive]], or just turn off its power supply (i.e., run the appropriate eject script but leave the drive inserted).
* [[How to set optical drive speed|Reduce the spinning speed of the optical drive]].

The hald daemon polling tends to maintain the ATA buses out of power saving
modes, and to wakeup CDROM drive (except if you have a kernel >= 2.6.24, hal >= 0.5.10,
and SATA AN compatible devices). If you have a recent hald version, you
can stop this polling when on battery:

hal-disable-polling --device /dev/scd0 # or whatever your CD drive is

start polling again when on ac:

hal-disable-polling --enable-polling --device /dev/scd0 # or whatever your CD drive is

If your hald is not recent enough, consider suspending it when running on battery. Some moderns SATA buses and drivers supports a notification mechanism (SATA AN - Asynchronous Events Notifications) that obsolete the need for polling on modern hardware; support for this feature had been merged in Linux 2.6.24-rc1 and HAL 0.5.10.

==LCD Backlight/Brightness==
The LCD backlight is one of the very major power drain.
Reducing brightness to the lowest readable
level will save a lot of battery lifetime. Also, don't forget to configure
your screen saver to shutdown the screen backlight (rather than displaying some
eye candy), when no activity for a few minutes.

You can also let the system [[automatically reduce brightness]] after a
period of inactivity.

If you're choosing your Thinkpad laptop model, keep in mind that the screen
size affect the battery time greatly: more power needed for larger screens.

The very recent, but xorg standard way to control backlight from CLI is
using xbacklight. ie. to set backlight at half the brightness:

xbacklight -set 50

You should configure the DPMS to shutdown the screen when idle (rather than
displaying a fancy but power consuming screensaver). ie. to turn off the
display after 5 minutes of idling:

xset +dpms
xset dpms 0 0 300

===Screensaver method===
Alternatively, you can add a screensaver that does nothing but blank the screen and turn off the display. In this example, I'm using Linux Mint MATE 17.2, please adjust the keywords below accordingly. Also, you will need to enable DPMS as above, or as in [[How to make ACPI work#Screen blanking (Standby)]].

We need to create 2 files, the first one is <code>/usr/share/applications/screensavers/screenoff.desktop</code>:

[Desktop Entry]
Name=Screen off
Comment=Turns the screen off
Exec=/usr/lib/mate-screensaver/screenoff
TryExec=/bin/true
StartupNotify=false
Terminal=false
Type=Application
Categories=Screensaver;
Keywords=MATE;screensaver;dpms;
OnlyShowIn=MATE;

The second one is <code>/usr/lib/mate-screensaver/screenoff</code>, which needs to be executable:

#!/bin/sh
pidof mate-screensaver-preferences | grep -w $PPID && exit 0
xset q | grep -q "Monitor is On" && xset dpms force off

The <code>Keywords</code> section and the <code>mate-screensaver-preferences</code> should be customized according to your desktop (like Cinnamon, or GNOME, etc).

After creating those files, open the Screensaver preferences dialog and choose the screensaver with the name "Screen off". Now, when the screensaver is activated, the screen will fade to black and backlight will be turned off by DPMS.

==Graphic controllers==
All xorg Thinkpad graphics chipsets drivers (ati, radeon, fglrx, i810) have
the same bug causing very frequent CPU wakeups when DRI is activated, even
when you don't use any 3D application.
This problem is partly fixed on xorg git tree but not released as of xorg
7.2. If you value more battery than 3D, you should disable DRI: put this on
the /etc/X11/xorg.conf "Device" of you graphic controller:

Option "NoDRI"

Also be sure that DPMS is working: <code>grep DPMS /var/log/Xorg.0.log</code>
should output "DPMS enabled". If not, put <code>Option "DPMS"</code> in your config.
See the section above about how to enable dpms driven display power saving.

On recent xrandr/xorg versions, you can disable the TV output (or any other detected
as connected but not used outputs) when you're not using it: it's known to consume power.

xrandr # see all displays listed here, but that you don't actually use and disable them.
xrandr --output TV --off # for instance (if "xrandr" above listed a connected output named "TV" that you don't use)

When you don't have an external monitor plugged, disable CRT and DVI output
(for some, this can make a difference in power usage) :

echo crt_disable > /proc/acpi/ibm/video
echo dvi_disable > /proc/acpi/ibm/video

Some drivers have specials power saving mode, and/or allows underclocking the GPU. See also:
* [[How to make use of Graphics Chips Power Management features]], or with [[Rovclock]] on ATI.
* [[Problem with high power drain in ACPI sleep]]

==USB Subsystem==
The kernel support an efficient USB 2.0 power saving feature if you enabled
CONFIG_USB_SUSPEND. This may not trigger in when you have an USB device
plugged (and beside, USB devices tends to suck power on their own), so avoid
using such devices when on battery. To enable it by default, you must add the line

options usbcore autosuspend=1

to your <tt>/etc/modprobe.conf</tt> or add it to (and create if necessary) the file <tt>/etc/modprobe.d/usbcore</tt> depending on how your distribution organises modprobe configuration.

If on the other hand, you have <tt>usbcore</tt> built into your kernel, you can add this in the kernel boot options (ie. in grub's menu.lst):

usbcore.autosuspend=1

or at runtime, per device, with:

for i in /sys/bus/usb/devices/*/power/autosuspend; do echo 1 > $i; done
for i in /sys/bus/usb/devices/*/power/level; do echo auto > $i; done

USB 1.1 is worst. It needs polling the bus frequently, hence can't really go
in a low power mode when you enabled it, even if you don't have any device
plugged. You'd better remove it when you don't use a 1.1 device:

rmmod uhci_hcd

If you don't intend to use any device needing USB 1.1 (unfortunately, the built-in bluetooth and fingerprint-reader are USB 1.1 devices), the USB 1.1 support can also be totally avoided. On Debian and derivatives, just do:

echo "blacklist uhci_hcd" >> /etc/modprobe.d/blacklist

==PCMCIA/CardBus==
Same for PCMCIA/CardBus. Some users experiences interrupts clouds (sometime up to
several thousands interrupts/second) causing CPU wakeups, thus totally preventing
the CPU to reach lower C-states.
If you don't use PCMCIA, you may disable it the same way (unloading seems insufficient
to restore the system properly, you have to boot without it):

echo "blacklist pcmcia" >> /etc/modprobe.d/blacklist
echo "blacklist yenta_socket" >> /etc/modprobe.d/blacklist

==Sound==

ALSA has a power saving feature that should be enabled on your kernel
(CONFIG_SND_AC97_POWER_SAVE). Note that this low power mode won't trigger in
unless you muted all sound inputs (micro, line in etc.). This feature has
to be activated with:

amixer set Line mute nocap
amixer set Mic mute nocap
echo Y > /sys/module/snd_ac97_codec/parameters/power_save

===Intel HD Audio===

If you have Intel HD audio as your onboard sound controller, substitute the following for the last line in the above sequence:

echo Y > /sys/module/snd_hda_intel/parameters/power_save_controller

You also may wish to decrease the sound poweroff timeout to something shorter, like 1 second after last playback:

echo 1 > /sys/module/snd_hda_intel/parameters/power_save

===Additional Tweaks===

You can unload all sound related modules when you are on
battery, or mute the sound system (echo mute > /proc/acpi/ibm/volume).

See also [[How to enable audio codec power saving]].

==Wireless Interface==
===intel wireless===
Wireless network consume a lot of power.
To save power, you can kill the Wi-Fi radio when it's not in use:

echo 1 > /sys/bus/pci/devices/*/rf_kill

If you need Wi-Fi, you can also reduce power consumption (at the price of
performances) by activating the power saving modes:

iwpriv wlan0 set_power 5

For drivers using the new Wi-Fi kernel framework (mac80211/cfg80211),
the canonical way to do this is now:

for i in /sys/bus/pci/devices/*/power_level ; do echo 5 > $i ; done

Most drivers, like ipw2200, that don't use the new mac80211 framework place the
interfaces in aggressive scanning mode when they are not associated with any
Access Point, even when the interface is down (more info about this on Intel's
[http://www.lesswatts.org/tips/wireless.php LessWatts] website).
This behavior consumes a lot of power, even more than when the interface
is plain active and in use. But this can disabled at module's load time :

rmmod ipw2200
modprobe ipw2200 associate=0

You can fix this setting by placing the following in /etc/modprobe.d/options
(Debian/Ubuntu) or in /etc/modprobe.conf (Red Hat/Fedora):

options ipw2200 associate=0

Reducing beacon intervals on your Access Point to 1 per second will also
reduce network card interrupts, therefore power savings. This shouldn't have
negatives side effects.

In recent kernels, the powersaving on the intel ipw3945 has been disabled, as
for some it is unstable. For others it worked just fine.

See [http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.33.y.git;a=blobdiff;f=drivers/net/wireless/iwlwifi/iwl-3945.c;h=e413bd35bc411a1113177f1576538eb0ac26f00c;hp=4609323d8436dc9e22c74be2f1f3cf5e97785cb2;hb=bc45a67079c916a9bd0a95b0b879cc0f259bac6e;hpb=b7bb1756cb6a610cdbac8cfdad9e79bb5670b63b this patch]. You may wish to try changing '.broken_powersave=true' to false, in /usr/src/linux/drivers/net/wireless/iwlwifi/iwl-3945.c if you wish to enable powersave.

See also, to activate power saving on the wireless network card:
* For [[Intel PRO/Wireless 2200BG Mini-PCI Adapter]] and [[Intel PRO/Wireless 2915ABG Mini-PCI Adapter]], see instructions for the [[ipw2200]] driver.
* For [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter]], see the [http://ipw3945.sourceforge.net/README.ipw3945 ipw3945 driver README]

==Ethernet Controler==
If you don't use Wake-on-LAN, you should disable it for your network card,
because it sucks a lot of power:

ethtool -s eth0 wol d

If you can, try to reduce useless network activity on your ethernet
segment, coming to your NIC (ie. uneeded broadcasts), those cause
interrupts and CPU wakeups.

Forcing 100Mbps full-duplex speed on a gigabit ethernet NIC can also save a lot of power (~1W) on most network workloads. This also reduces component temperatures (e.g., [[Thermal Sensors|thermal sensor]] 0xC0 on the {{T43}} cools down by 5 degrees between 1000Mbps and 100Mbps, and another 1 degree for 10Mbps).

ethtool -s eth0 autoneg off speed 100

Note, however, that if the network device on the other side has auto-negotiation enabled (which is almost guaranteed) and you turn auto-negotiation off, the other side will assume half-duplex mode and you will experience a significant loss of performance.

==Bluetooth==
When you don't need bluetooth, disable it. Because of its radio,
bluetooth is not power friendly.

hciconfig hci0 down ; rmmod hci_usb
echo disable > /proc/acpi/ibm/bluetooth

==Modem==
When was the last time you used your analog modem? If you can't remember, you probably just don't need it. If it is on a separate module in your laptop, simply remove it. Store it in a ESD safe place (like the bag in which your last addon card or hard drive was packed), in case you should need it again. This won't save you a lot of power and weight, but why carry something around you never use.

==System Fans==
Fans consumes power when running, so you may look at the [[ACPI fan control script]].

==Misbehaving Userland==
You should avoid using Beagle, Compiz, Beryl, XMMS, gnome-power-manager
and Evolution while on battery.
Look at the PowerTOP's [http://www.linuxpowertop.org/known.php known problems]
list.

Deactivate desktop animations (blinking cursor on the terms, animated wallpapers, ...): they cause regular X (therefore kernel and CPU) wakeups.

In short, while on battery, you should stop all applications that don't really stay idle when you're not using them. This means applications that:
* Wakes up the CPU too often (by polling something, because of too short select() timeouts, ...)
* Access the disks at regular intervals
* Access an hardware bus (USB, ATA, ...) at regular intervals
To find those offenders run:
* <code>strace -p $(pidof yourapp)</code> # for all your running applications
* <code>powertop</code>
* <code>dstat -t -c --power --top-cpu --top-io --top-bio --top-latency --top-cputime</code>
* <code>sysctl vm.block_dump=1</code> # and look at dmesg
* <code>ps aux | awk '{print$10,$11}' | sort -n</code> # will list all running softs sorted by used cpu time
Please consider filling a bug if you identify such misbehaving software.
{{NOTE|Not all software is evil, buggy or badly written. Some produce regular activity as it is required to provide the intended functionality. Think twice before filling bugs about this.}}

==See Also==
* [[How to measure power consumption]]
* [[Script for monitoring power consumption]]
* Battery [[maintenance]]

==External resources==
* [http://www.free-it.de/archiv/talks_2005/paper-11017/paper-11017.html ''Current trends in Linux Kernel Power Management''], Dominik Brodowski, 2005
* [http://www.linuxpowertop.org PowerTOP] website
* [http://www.gentoo.org/doc/en/power-management-guide.xml Power Management Guide] from the Gentoo Linux documentation
* [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-November/030478.html When/where/what for low power consumption?] (thread on Linux-Thinkpad)
* Intel's [http://www.lesswatts.org/ LessWatts] "''Saving power on Linux''" website
* ''8 hours of battery life on your lap(top)'' ([http://atrey.karlin.mff.cuni.cz/~pavel/swsusp/8hours.odp ODP]/[http://atrey.karlin.mff.cuni.cz/~pavel/swsusp/8hours.pdf PDF]), a presentation by Pavel Machek

[[Category:600X]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:A30]] [[Category:A30p]] [[Category:A31]] [[Category:A31p]] [[Category:i1200]] [[Category:i1300]] [[Category:i1620]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50e]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:R60]] [[Category:R60e]] [[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:T60]] [[Category:T60p]] [[Category:T61]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]] [[Category:X60]] [[Category:X60s]] [[Category:X61]] [[Category:X61s]] [[Category:Z60m]] [[Category:Z60t]] [[Category:Z61t]] [[Category:Z61e]] [[Category:TransNote]]

Maintenance

2025-10-09T02:44:23Z

ThinkGNU: Added hinge lubrication instructions.

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
Here you can find general hints about keeping your ThinkPad in good shape. Look at your [[:Category:Models|models category page]] for IBMs official maintenance guide for that model.
|}
==Assembly/Disassembly instructions==
Lenovo has a website dedicated to servicing ThinkPads, but it only covers the more recent models. For older models check the HMM (Hardware Maintenance Manual) for your ThinkPad.
* http://www.lenovoservicetraining.com/

==Battery treatment==
{| border=1 cellspacing=0 cellpadding=2 style="vertical-align:top;"
|+Battery life expanding guide
|- style="background:#efefef;white-space:nowrap;"
! style="background:#ffdead;" | Battery Type !! NiCd !! NiMH !! Lithium ion
|- style="vertical-align:top;"
! style="background:#ffdead;" | General
|
*always do complete discharge/charge cycles
*avoid exposing the battery (or notebook) to excessive heat
|
*always do complete discharge/charge cycles
*avoid exposing the battery (or notebook) to excessive heat
|
*avoid deep discharges except when resetting fuel gauge or reconditioning a battery; partial dis-/recharges are better for the battery lifetime (note: fuel gauge will slowly get inaccurate over time)
*remove battery when on AC (due to heat)
*avoid exposing the battery (or notebook) to excessive heat
|- style="vertical-align:top;"
! style="background:#ffdead;" | Charging
|
*discharge before charging
|
*discharge before charging
|
*avoid charging if battery is nearly full, unless you will need its full capacity soon; keep it on the 30%-85% charged range
*keep notebook off while charging due to heat
*fully discharge, then fully charge battery when needed to recalibrate fuel gauge; newer battery pack models require this less often, old ones might need it as often as every 30 cycles
|- style="vertical-align:top;"
! style="background:#ffdead;" | Storage
|
*almost discharged
*cool and dry
|
*almost discharged
*cool and dry
|
*never fully charged or discharged, ideally at about 40%
*cool and dry, but '''do not freeze''' them: 10-15C is recommended
|}

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

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

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

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

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

===Reviving batteries===
Some people experience sudden drops in their batteries capacity. A way to get these batteries back to full capacity is to run the "Battery Rundown" function of IBMs "PC Doctor for DOS". The program is downloadable from IBMs support site as three floppy disk images. Make sure you get the specific version of program made for your ThinkPad model. For those who do not have a floppy, David Smith prepared a [http://www.mypchelp.com/~dsmith/ibmutil/ibm_t22_pcdiag.iso bootable CD image] (dead link, a copy is also available [http://server6.org/~marker/software/ibm_t22_pcdiag.iso here]) from the T22 floppy images. For newer ThinkPads there is an official [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-56222 bootable CD image]. (Although the instructions on this page (as of May 2008) include details for Linux and refer to a CD image, it is actually provided as a Windows executable. On Linux systems, [http://winehq.org Wine] can execute this file and extract the CD image.) Once extracted, you must mount the iso as a loop device (as root) like so:

:{{cmdroot|mount -o loop 1ety48ww.iso /mnt/floppy}}

Then copy the .IMA file out of that mounted iso:

:{{cmdroot|cd /mnt/floppy}}
:{{cmdroot|cp 1ETY48WW.IMA /boot}}

(Or to some other suitable directory.) After this, you can follow the same directions that apply for [[BIOS Upgrade|BIOS upgrade]]s.

{{NOTE|This will do nothing to improve the performance of a dying battery. It serves only to recalibrate the battery charge controller. The "Battery Rundown" function of IBMs "PC Doctor for DOS" has no intelligence. It merely runs a series of dumb operations to consume battery power, and it cannot detect whether a battery is present or not. If you leave the mains connected while running "Battery Rundown", it will have no effect, as the battery will simply keep charging. The [[tp_smapi]] module, if installed, will report the number of charge cycles the battery has had since it was manufactured. If that number is high, the battery's poor performance is almost certainly due to its age.}}

I have recently made an interesting discovery, I have an R40 with two main batteries, both of them have aproximately about under 200 cycles and are nowadays 4 years old, projected capacity for R40/R32 main battery is 57Wh, and both my batteries were about 30Wh, then I left my notebook with one of them about a day in a standby mode, as long as it powered off itself because of low battery power, when I turned it on I saw the battery capacity at about 42Wh, then, I did this too for the second battery and I got even about 46Wh, I think I could go even higher with letting the battery discharge completely from 100% in standby, I think this has something to do with low power consumption in standby mode, it may work for you too.

===See also===
* [[Battery safety]]

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

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

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

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

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

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

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

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

See also [http://www.moneysense.ca/spending/technology/columnist.jsp?content=986628 Act quickly, carefully if you spill on laptops] on MoneySense.ca (link broken as of 2006-09-18, the article is still available via [http://web.archive.org/web/20050221034011/http://www.moneysense.ca/spending/technology/columnist.jsp?content=986628 web.archive.org]).

==Fan Lubrication==
Older ThinkPads, like the Core/Core 2 Duo line can have issues with the bearing lubrication drying out, resulting in the fan rattling without spinning and only spinning slowly at 100% fanspeed. Even if the fan is working fine at the moment, the lubrication may fail in a few years, thus it is recommended that fan lubrication is done as well if you ever deassemble such ThinkPads for repasting or GNUbooting;
* Unscrew heatsink+fan housing and carefully deassemble, removing screws and tape and moving wiring as needed - avoid bending the housing, otherwise the fan will rattle until it is bent back.
* Pull out the magnet-retained fan blades and clean the dust from the blades and housing (it's easiest to wash the blades in water - but complete drying with paper towel etc will be required afterwards).
* Put a drop of 3-in-1 or sewing machine oil into the motor bearing and re-insert the fan - it should spin freely if manually spun a bit (if gunk near or in the bearing, oil, use paper towel to remove it, then re-oil).
* Reinstall housing - old tape can be replaced with any moderately heat-resistant tape, like rubber electrical tape (the temperature shouldn't ever exceed 60°C, but to avoid melted or burning plastic, tape with heat resistance of at least 105°C should be used).

==Hinge Lubrication==
Older ThinkPads, like the Core/Core 2 Duo line can develop very stiff hinges as the lubrication dries out, requiring excessive force to move the screen, which can lead to the screen mount breaking off. Lubricating the hinges fixes the problem;
* Deassemble the ThinkPad, removing/unplugging the keyboard, top cover, LCD connector, Wi-Fi antenna and screen screws so you can remove the screen assembly (moving the screen to the 90° position, so the hinges are 180° on removal is recommended).
* Take off the black screen screw covers with your fingernails or a plastic tool and unscrew the screen cover screws and gently unclip the screen cover all around until it comes off (very difficult to do without cosmetic damage).
* Unscrew the hinges and take them out (the antennas may need to be unscrewed and the screen may need to be partially pulled out before the hinges can be unscrewed and removed - if there is a webcam, unplug it, or be extremely gentle when manipulating the screen, otherwise the ribbon cable will tear).
* Place the bottom end of the hinge into a vice with the insertion side of the hinge joint facing up (the other end usually has a tiny circlip on it).
* Place 3-in-1 or sewing machine oil onto the joint and move the hinge back and forth with pliers to work oil into the joint - add more oil and work it into the joint until the hinge is no longer excessively stiff (the hinges need to be quite stiff, otherwise the screen will flop around).
* Clean off excess oil external to the joint and oil the other hinge - both hinges should have similar stiffness to avoid uneven forces.
* Reassemble the screen assembly - a glue stick of paper glue is good for re-attaching the screen screw covers, while also ensuring those can be easily removed later.
* On re-insertation into the base, the screen should move with a reasonable amount of force.

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

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

(Note: An updated tutorial can always be found [http://www.allservice.ro/forum/viewtopic.php?t=47&start=0 HERE])

'''1. Introduction.'''

The IBM ThinkPad uses a small eeprom ([[AT24RF08|ATMEL 24RF08]]) to store different OEM
issues like serial number, UUID, etc. The supervisor password (SVP) is also stored in this eeprom.
The 24RF08 is not an ordinary eeprom: it features read protection, which the BIOS uses to lock down
access to the eeprom contents. Also, the password is written in a special scan code, which needs to
be translated to ASCII to be of any use.

To recover the password, one can use two different programs: R24RF08 (eeprom reader) and IBMpass
(password revealer) available at [http://www.allservice.ro/store/utils http://www.allservice.ro/store/utils]. Diagrams are included in the reader kit.

Models for which R24RF08 and IBMpass are enough to recover the password: 240, 240X, 390E, 390X, 570, 570E,
600e, 600X, 770Z, A20m, A21e, A21m, a22m, A30, A30p, A31, A31p, G40, G41, R30, R31, R32, R40, R50, R51,
Transnote, T20, T21, T22, T23, T30, T40, T40p, T41, T41p, T42, T42p, X20, X21, X22, X23, X24, X30, X31, X40, X41, X61.

ThinkPads featuring TPCA technology (i.e. a [[Tpm|TPM trusted platform module chip]]), especially T4x, X3x, X4x, X61 and X61T need the W24RF08 eeprom writer program to complete the password recovery procedure, if the passphrase function is enabled in BIOS setup.

Other models such as the 380XD or 600 use 24C01 or 93C46 eeproms, which can be read without special tools.
The method is the same like for the models based on 24RF08, only the software to dump the eeprom is different.

Newer T43/T43p, R52, R60, T60/p, X60 and Z60 ThinkPads can be unlocked using PC8394 programming tools that consist in RPC8394 and WPC8394 (reader and writer for TPM chips).
The software is available as well at [http://www.allservice.ro/forum/viewtopic.php?p=1061#1061 www.allservice.ro]. IBMpass 2.0 works for any TP model without exceptions.

'''2. Locating the ATMEL 24RF08 eeprom. Soldering.'''

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

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

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

What these switches mean:
/x - invert serial clock, also known as SCL;
/d - invert serial data output, also known as SDA-Out;
/i - invert serial data input, also known as SDA-In.
All those can be used in any combination to meet any interface specification.

Note that the "standard" serial port programmer probably won't work with a USB-Serial adapter, but requires the full nominal voltage of a hardware serial port. [Example: the A22p's serial port works fine here.]

'''4. Dump the EEPROM:'''

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

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

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

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

Dump the EEPROM data at least twice, and do a bytewise compare with `cmp`. Both files should be identical, and 1024 bytes long. Otherwise, you probably have a serial port problem.

Note: the r24rf08.exe program automatically sets the serial port parameters. It also works fine with Wine under Linux - provided that a symlink (com1) exists in the .wine/dos_devices directory, and points to the /dev/ttySX for the actual serial port.

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

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

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

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

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

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

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

Moreover, there are a new encrypting algos used with some new security chips (AT97SC3201, AT97SC3203) that are very secured. The password is not in scancode and in some cases not even in the eeprom. To unlock the machine, the dump should suffer some changes and the eeprom must be reprogrammed using W24RF08. This operation works for all IBM TCG/TCPA secured laptops w/o exceptions.

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

'''6. Password format'''

The thinkpad power-on/supervisor passwords are a maximum of 7 characters, and are NOT case-sensitive. The allowed characters are restricted to A-Z, 0-9, semicolon, _, - (and perhaps a few others).
If PassPhrase is enabled then the password can be longer than 7 characters.
Models like T43/R52/T60/R60/T60/X60/Z60/Z61 need the TPM chip dumped with [http://www.allservice.ro/forum/viewtopic.php?p=1061#1061 PC8394 programming tools] in order to find password/reset the TCPA lock.

===External Sources===
* [http://www.allservice.ro/forum R24RF08/W24RF08, PC8394 programming tools & IBMpass author's forums]
* {{IBMDOCURL|MIGR-59377|IBM/Lenovo Support - Lost or forgotten password}}
* [http://www.allservice.ro/forum/viewforum.php?f=12 Full Service of all ThinkPad models including free password recovery]
* [http://sodoityourself.com/hacking-ibm-thinkpad-bios-password/ A tutorial on how to do this]

[[Category:HOWTOs]]

Maintenance

2025-10-09T01:59:37Z

ThinkGNU: Added fan lube instructions.

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
Here you can find general hints about keeping your ThinkPad in good shape. Look at your [[:Category:Models|models category page]] for IBMs official maintenance guide for that model.
|}
==Assembly/Disassembly instructions==
Lenovo has a website dedicated to servicing ThinkPads, but it only covers the more recent models. For older models check the HMM (Hardware Maintenance Manual) for your ThinkPad.
* http://www.lenovoservicetraining.com/

==Battery treatment==
{| border=1 cellspacing=0 cellpadding=2 style="vertical-align:top;"
|+Battery life expanding guide
|- style="background:#efefef;white-space:nowrap;"
! style="background:#ffdead;" | Battery Type !! NiCd !! NiMH !! Lithium ion
|- style="vertical-align:top;"
! style="background:#ffdead;" | General
|
*always do complete discharge/charge cycles
*avoid exposing the battery (or notebook) to excessive heat
|
*always do complete discharge/charge cycles
*avoid exposing the battery (or notebook) to excessive heat
|
*avoid deep discharges except when resetting fuel gauge or reconditioning a battery; partial dis-/recharges are better for the battery lifetime (note: fuel gauge will slowly get inaccurate over time)
*remove battery when on AC (due to heat)
*avoid exposing the battery (or notebook) to excessive heat
|- style="vertical-align:top;"
! style="background:#ffdead;" | Charging
|
*discharge before charging
|
*discharge before charging
|
*avoid charging if battery is nearly full, unless you will need its full capacity soon; keep it on the 30%-85% charged range
*keep notebook off while charging due to heat
*fully discharge, then fully charge battery when needed to recalibrate fuel gauge; newer battery pack models require this less often, old ones might need it as often as every 30 cycles
|- style="vertical-align:top;"
! style="background:#ffdead;" | Storage
|
*almost discharged
*cool and dry
|
*almost discharged
*cool and dry
|
*never fully charged or discharged, ideally at about 40%
*cool and dry, but '''do not freeze''' them: 10-15C is recommended
|}

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

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

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

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

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

===Reviving batteries===
Some people experience sudden drops in their batteries capacity. A way to get these batteries back to full capacity is to run the "Battery Rundown" function of IBMs "PC Doctor for DOS". The program is downloadable from IBMs support site as three floppy disk images. Make sure you get the specific version of program made for your ThinkPad model. For those who do not have a floppy, David Smith prepared a [http://www.mypchelp.com/~dsmith/ibmutil/ibm_t22_pcdiag.iso bootable CD image] (dead link, a copy is also available [http://server6.org/~marker/software/ibm_t22_pcdiag.iso here]) from the T22 floppy images. For newer ThinkPads there is an official [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-56222 bootable CD image]. (Although the instructions on this page (as of May 2008) include details for Linux and refer to a CD image, it is actually provided as a Windows executable. On Linux systems, [http://winehq.org Wine] can execute this file and extract the CD image.) Once extracted, you must mount the iso as a loop device (as root) like so:

:{{cmdroot|mount -o loop 1ety48ww.iso /mnt/floppy}}

Then copy the .IMA file out of that mounted iso:

:{{cmdroot|cd /mnt/floppy}}
:{{cmdroot|cp 1ETY48WW.IMA /boot}}

(Or to some other suitable directory.) After this, you can follow the same directions that apply for [[BIOS Upgrade|BIOS upgrade]]s.

{{NOTE|This will do nothing to improve the performance of a dying battery. It serves only to recalibrate the battery charge controller. The "Battery Rundown" function of IBMs "PC Doctor for DOS" has no intelligence. It merely runs a series of dumb operations to consume battery power, and it cannot detect whether a battery is present or not. If you leave the mains connected while running "Battery Rundown", it will have no effect, as the battery will simply keep charging. The [[tp_smapi]] module, if installed, will report the number of charge cycles the battery has had since it was manufactured. If that number is high, the battery's poor performance is almost certainly due to its age.}}

I have recently made an interesting discovery, I have an R40 with two main batteries, both of them have aproximately about under 200 cycles and are nowadays 4 years old, projected capacity for R40/R32 main battery is 57Wh, and both my batteries were about 30Wh, then I left my notebook with one of them about a day in a standby mode, as long as it powered off itself because of low battery power, when I turned it on I saw the battery capacity at about 42Wh, then, I did this too for the second battery and I got even about 46Wh, I think I could go even higher with letting the battery discharge completely from 100% in standby, I think this has something to do with low power consumption in standby mode, it may work for you too.

===See also===
* [[Battery safety]]

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

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

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

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

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

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

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

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

See also [http://www.moneysense.ca/spending/technology/columnist.jsp?content=986628 Act quickly, carefully if you spill on laptops] on MoneySense.ca (link broken as of 2006-09-18, the article is still available via [http://web.archive.org/web/20050221034011/http://www.moneysense.ca/spending/technology/columnist.jsp?content=986628 web.archive.org]).

==Fan Lubrication==
Older ThinkPads, like the Core/Core 2 Duo line can have issues with the bearing lubrication drying out, resulting in the fan rattling without spinning and only spinning slowly at 100% fanspeed. Even if the fan is working fine at the moment, the lubrication may fail in a few years, thus it is recommended that fan lubrication is done as well if you ever deassemble such ThinkPads for repasting or GNUbooting;
* Unscrew heatsink+fan housing and carefully deassemble, removing screws and tape and moving wiring as needed - avoid bending the housing, otherwise the fan will rattle until it is bent back.
* Pull out the magnet-retained fan blades and clean the dust from the blades and housing (it's easiest to wash the blades in water - but complete drying with paper towel etc will be required afterwards).
* Put a drop of 3-in-1 or sewing machine oil into the motor bearing and re-insert the fan - it should spin freely if manually spun a bit (if gunk near or in the bearing, oil, use paper towel to remove it, then re-oil).
* Reinstall housing - old tape can be replaced with any moderately heat-resistant tape, like rubber electrical tape (the temperature shouldn't ever exceed 60°C, but to avoid melted or burning plastic, tape with heat resistance of at least 105°C should be used).

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

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

(Note: An updated tutorial can always be found [http://www.allservice.ro/forum/viewtopic.php?t=47&start=0 HERE])

'''1. Introduction.'''

The IBM ThinkPad uses a small eeprom ([[AT24RF08|ATMEL 24RF08]]) to store different OEM
issues like serial number, UUID, etc. The supervisor password (SVP) is also stored in this eeprom.
The 24RF08 is not an ordinary eeprom: it features read protection, which the BIOS uses to lock down
access to the eeprom contents. Also, the password is written in a special scan code, which needs to
be translated to ASCII to be of any use.

To recover the password, one can use two different programs: R24RF08 (eeprom reader) and IBMpass
(password revealer) available at [http://www.allservice.ro/store/utils http://www.allservice.ro/store/utils]. Diagrams are included in the reader kit.

Models for which R24RF08 and IBMpass are enough to recover the password: 240, 240X, 390E, 390X, 570, 570E,
600e, 600X, 770Z, A20m, A21e, A21m, a22m, A30, A30p, A31, A31p, G40, G41, R30, R31, R32, R40, R50, R51,
Transnote, T20, T21, T22, T23, T30, T40, T40p, T41, T41p, T42, T42p, X20, X21, X22, X23, X24, X30, X31, X40, X41, X61.

ThinkPads featuring TPCA technology (i.e. a [[Tpm|TPM trusted platform module chip]]), especially T4x, X3x, X4x, X61 and X61T need the W24RF08 eeprom writer program to complete the password recovery procedure, if the passphrase function is enabled in BIOS setup.

Other models such as the 380XD or 600 use 24C01 or 93C46 eeproms, which can be read without special tools.
The method is the same like for the models based on 24RF08, only the software to dump the eeprom is different.

Newer T43/T43p, R52, R60, T60/p, X60 and Z60 ThinkPads can be unlocked using PC8394 programming tools that consist in RPC8394 and WPC8394 (reader and writer for TPM chips).
The software is available as well at [http://www.allservice.ro/forum/viewtopic.php?p=1061#1061 www.allservice.ro]. IBMpass 2.0 works for any TP model without exceptions.

'''2. Locating the ATMEL 24RF08 eeprom. Soldering.'''

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

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

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

What these switches mean:
/x - invert serial clock, also known as SCL;
/d - invert serial data output, also known as SDA-Out;
/i - invert serial data input, also known as SDA-In.
All those can be used in any combination to meet any interface specification.

Note that the "standard" serial port programmer probably won't work with a USB-Serial adapter, but requires the full nominal voltage of a hardware serial port. [Example: the A22p's serial port works fine here.]

'''4. Dump the EEPROM:'''

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

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

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

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

Dump the EEPROM data at least twice, and do a bytewise compare with `cmp`. Both files should be identical, and 1024 bytes long. Otherwise, you probably have a serial port problem.

Note: the r24rf08.exe program automatically sets the serial port parameters. It also works fine with Wine under Linux - provided that a symlink (com1) exists in the .wine/dos_devices directory, and points to the /dev/ttySX for the actual serial port.

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

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

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

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

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

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

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

Moreover, there are a new encrypting algos used with some new security chips (AT97SC3201, AT97SC3203) that are very secured. The password is not in scancode and in some cases not even in the eeprom. To unlock the machine, the dump should suffer some changes and the eeprom must be reprogrammed using W24RF08. This operation works for all IBM TCG/TCPA secured laptops w/o exceptions.

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

'''6. Password format'''

The thinkpad power-on/supervisor passwords are a maximum of 7 characters, and are NOT case-sensitive. The allowed characters are restricted to A-Z, 0-9, semicolon, _, - (and perhaps a few others).
If PassPhrase is enabled then the password can be longer than 7 characters.
Models like T43/R52/T60/R60/T60/X60/Z60/Z61 need the TPM chip dumped with [http://www.allservice.ro/forum/viewtopic.php?p=1061#1061 PC8394 programming tools] in order to find password/reset the TCPA lock.

===External Sources===
* [http://www.allservice.ro/forum R24RF08/W24RF08, PC8394 programming tools & IBMpass author's forums]
* {{IBMDOCURL|MIGR-59377|IBM/Lenovo Support - Lost or forgotten password}}
* [http://www.allservice.ro/forum/viewforum.php?f=12 Full Service of all ThinkPad models including free password recovery]
* [http://sodoityourself.com/hacking-ibm-thinkpad-bios-password/ A tutorial on how to do this]

[[Category:HOWTOs]]

Fan error

2025-10-09T01:31:44Z

ThinkGNU: Added fan lube instructions

=="fan error" occurs, as reported, after an excessive use of the fan.==
You can skip this by pressing the ESC key. Or you can try to solve this problem by cleaning the fan.

===Known affected models:===
T series:
* [[:Category:T23|T23]]
* [[:Category:T40|T40]]
* [[:Category:T41|T41]]
* [[:Category:T42|T42]]
* [[:Category:T43|T43]]

=="Fan error" also occurs on bootup if the fan fails to spin up at boot.==
It can be skipped with the ESC key. On the Core/Core 2 Duo line of ThinkPads, the problem is usually a lubrication failure, which can be solved by oiling the fan;
* Unscrew heatsink+fan housing and carefully deassemble, removing screws and tape as needed - avoid bending the housing, otherwise the fan will rattle until you bend it back.
* Pull out the magnet-retained fan blades and clean the dust from the blades and housing (it's easiest to wash the blades in water - but you'll need to completely dry it with paper towel etc afterwards).
* Put a drop of 3-in-one or sewing machine oil into the motor bearing and re-insert the fan - it should spin freely if you spin it a bit (if there's gunk near/in the bearing, oil, then use paper towel to remove it, then re-oil).
* Reinstall housing - old tape can be replaced with any moderately heat-resistant tape, like rubber electrical tape (the temperature shouldn't ever exceed 60°C, but you want heat resistance of at least 105°C, so you don't end up with melted or burning plastic).
* Repasting the CPU while you're at it is recommended.

Wireless USB (UWB)

2025-10-09T00:41:17Z

ThinkGNU: According to https://www.phoronix.com/news/Linux-5.7-Dropping-UWB-WUSB support was removed in Linux 5.7.

__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;">
=== Wireless USB (UWB) ===
Select ThinkPads have the option for a Mini PCIe Wireless USB (WUSB) adapter

=== Features ===
* PCI ID: 8086:??
</div>
|style="vertical-align:top" |
|}
=== Lenovo Partnumbers ===
* FRU PN: 42T0885 (US for T61p)
* FRU PN: 42T0887 (Japan for T61p)
* FRU PN: 43Y6501 (US)
* FRU PN: 43Y6503 (Japan)

=== Linux support ===
Support for this technology was merged in the 2.6.28 kernel and removed in kernel 5.7

{{HELP|How to actually make use of it?}}
=== Links ===
* [http://www.linuxuwb.org/ Linux UWB and Wireless USB]
* [http://en.wikipedia.org/wiki/Wireless_USB WikipediA article on Wireless USB]

=== ThinkPads which may have this feature ===
* {{R400}}
* {{T61p}}, {{T400}}, {{T500}}
* {{X300}}, {{X301}}

Category:X200

2025-10-09T00:35:47Z

ThinkGNU: 8GB works fine in my X200. From experience, everything but Kingston sticks work with GM45.

__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 X200 ===
This page gives an overview of the ThinkPad X200.

==== Standard Features ====
* One of the following [[Intel Core 2 Duo (Penryn)]] processors:
** Intel Core 2 Duo P8400, 2.26GHz, 3MB L2, 1066MHz FSB
** Intel Core 2 Duo P8600, 2.40GHz, 3MB L2, 1066MHz FSB
** Intel Core 2 Duo P8700, 2.53GHz, 3MB L2, 1066MHz FSB
** Intel Core 2 Duo P8800, 2.66GHz, 3MB L2, 1066MHz FSB
* [[Intel Graphics Media Accelerator 4500MHD]] graphics
* One of the following [[TFT display|TFT displays]]:
** 12" TFT display with 1280x800 (WXGA) resolution
** 12" TFT display with 1280x800 (WXGA) resolution with LED backlight
* 1, 2, 3 or 4GB [[PC3-8500]] memory standard, upgradable to 4GB, 8GB is not officially supported but generally works
* One of the following hard drives:
** 80GB SSD 1.8" SATA
** 128GB SSD 1.8" SATA
** 160GB 5400RPM 2.5" SATA
** 160GB 7200RPM 2.5" SATA
** 250GB 5400RPM 2.5" SATA
* 5-1 (MMC/SD/SDHC and MS/MS Pro) Media card Reader
* [[Intel Gigabit Ethernet (10/100/1000) PCI-Express]]
* Intel HD Audio with a [[CX20561]] codec
* [[ThinkPad Modem (MDC-3.0, 56kbps HDA)]]
* [[MiniPCI Express slot]] 1 with one of the following:
** [[Intel Wifi Link 5100 (AGN)]]
** [[Intel Wifi Link 5300 (AGN)]]
** [[Intel WiMAX/WiFi Link 5150]]
** [[Intel WiMAX/WiFi Link 5350]]
* [[MiniPCI Express slot]] 2 with one of the following:
** none (empty)
** none (WWAN upgradable)
** [[Sierra Wireless MC5725|Verizon Mobile Broadband with GPS]]
** [[Ericsson F3507g Mobile Broadband Module|AT&T Mobile Broadband with GPS]]
* [[MiniPCI Express slot]] 3 with one of the following:
** none (empty)
** [[Intel® Turbo Memory hard drive cache]] 2GB
* 1.3MP [[Integrated camera]] on select models
* [[Integrated Fingerprint Reader]] on select models
* [[ThinkPad_Bluetooth_with_Enhanced_Data_Rate_(BDC-2.1)|Bluetooth]] on select models
* [[Embedded Security Subsystem|Trusted Computing Group TPM 1.2]]
* [[Active Protection System]]
* One [[ExpressCard_slot|ExpressCard/54 Slot]]
* One of the following batteries
** 4-cell battery, 29 Wh (14.4 V, 2.0 Ah). up to 3.3 hr, 1.34kg
** 4-cell *tablet, 29 Wh (14.4 V, 2.0 Ah).
** 6-cell battery, 56 Wh (10.8 V, 5.2 Ah). up to 6.5 hr, 1.47kg (slightly elevates the back)
** 8-cell *tablet, 66 Wh (14.4 V, 4.6 Ah)
** 9-cell battery, 85 Wh (10.8 V, 7.8 Ah). up to 9.8 hr, 1.63kg (protrudes out back 22.8mm/.9in)
</div>
|style="vertical-align:top" |
[[Image:ThinkPadX200.jpg|ThinkPad X200|300px]]
|}

==== Resources ====
* [http://shop.lenovo.com/ISS_Static/merchandising/US/PDFs/x200_datasheet.pdf X200 Technical Specifications (x200_datasheet.pdf 1138738 octet)]
*{{IBMDOCURL|MIGR-70149|Hardware Maintenance Manual (HMM) - ThinkPad X200, Twelfth Edition (November 2014) (x200_x200s_x200si_x201_x201i_x201s_hmm_en_43y6632_11.pdf 16338562 octet)}}

==== Reviews ====
* [http://www.notebookreview.com/default.asp?newsID=4497 Notebookreview.com] 2008-07-15
* [http://www.laptopmag.com/review/laptops/lenovo-thinkpad-x200.aspx Laptopmag.com] 2007-07-14
* [http://reviews.cnet.com/laptops/lenovo-thinkpad-x200/4505-3121_7-33184078.html Cnet.com] 2008-08-14

==== Notes ====
Sometimes even basic information is hard to find. Here's a place for it.

* [[GPS]] - If you have an optional WWAN card (AT&T or Verizon), you have GPS. ''unconfirmed''
* The 5300 normally has 3 x 3 antennas. Adding the webcam reduces this to 2 x 2. ''unconfirmed''
*: Any other conflicts? Bluetooth, etc?
* X200 configured with SSD include the [[Active Protection System]] accelerometer (at least 7454-CTO models shipped in Q4 2008). [[User:Vminko|Vminko]] 02:41, 30 December 2008 (CET)
* The X200 does not have a touchpad. For folks who really want one, a somewhat messy possibility ''might'' be [http://www.ergonomictouchpad.com/ergonomic_touchpad.php www.ergonomictouchpad.com] (never used - no endorsement) which looks vaguely like a [http://www.cirque.com/cpages/?page=17 Cirque TSM9925 Touchpad] with velcro and wire added.
* There can be a ''big'' cost difference between preconfigured units from VARs, and custom configured units from shop.lenovo.com, as of 2008-10-31 ([http://alltp.blogspot.com/2008/10/heckuva-deal-on-lenovo-x200-tablet-pc.html examples]).

[[Category:X Series]]

Fix for suspend problems on T410s with touchscreen

2025-05-03T02:11:07Z

ThinkGNU: Linux is only a kernel. The script will work on any distro that has hid_ntrig as a module. Cleaned up.

In {{Ubuntu}} (and a lot of other GNU/Linux distrubutions) the Lenovo {{T410s}} with a [[MultiTouch|touchscreen]] has (had?) the issue that it cannot go into suspend.

It is the kernel module hid_ntrig that seems to be causing the problem. Thus a work around this is to turn off the kernel module hid_ntrig by running the following command:
modprobe -r hid_ntrig

This will disable the touch screen, but now suspend works.

If you want to have both your touch screen and suspend, go to the folder: /etc/pm/sleep.d/. You should create a script file in this folder which will then be called when your laptops goes into and awakens from suspend. The script should contain the following and remember to make the file executable (<code>chmod +x disable-enable-hid-ntrig.sh</code>):
#!/bin/sh

# Disable ntrig on suspend and enable it when awakening from suspend.
# Goal: Make both suspend and touchscreen work on Lenovo ThinkPad T410s.

# pm-action(8) - <action> <suspend method>

case "${1}" in
suspend|hibernate)
modprobe -r hid_ntrig
;;
resume|thaw)
modprobe hid_ntrig &
;;
esac

When your laptop goes into suspend, the touch screen module will be disabled; <code>modprobe -r hid_ntrig</code> and on awakening the module is enabled; <code>modprobe hid_ntrig &</code>

Ampersand (&) was added when enabling hid_ntrig, because this command is rather slow. By doing so the command in run in the background, and thus it will not make your computer stall on awakening, but it might take 10 seconds before you can use your touch screen.

This has been implemented in Mint 10 but I guess it will also work in a normal {{Ubuntu}} 10.10 installation.

MultiTouch

2025-05-03T02:01:19Z

ThinkGNU: Capitalization, spelling and grammar. It probably has been fixed now, but leave the details in place in case anyone still has problems.

__NOTOC__
{| width="100%"
|style="vertical-align:top" |[[Image:Logo_wacom.gif|Wacom Logo]]
|style="vertical-align:top" |
<div style="margin:0px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== MultiTouch ===
Some models come with touchscreen abilities, known as MultiTouch.
</div>
|}

MultiTouch is an optional feature on the X60/X61/X200/X201/etc Tablet. It allows you to use any device that can create pressure (such as your finger) instead of the tablet pen. This feature is currently ''experimentally'' supported with linuxwacom. However, the tablet pen will still work on such systems.

With the wacom drivers, it will only support as a single-touch interface and not as real multitouch.

If your tablet pen does not work, try building the linuxwacom modules from source. You can find everything you need [http://linuxwacom.sourceforge.net on their website.]

On the X201 Tablet, it was reported that 2 fingers work on the display without pressure and the pen is working normal (with pressure).

A multitouch screen is an optional upgrade for the (non-tablet) {{T410s}}. As of January 2011, this is not recommended. Although it has some support as an input device, it seems to cause significant stability problems. On Ubuntu it prevents suspend from working; on both Debian and Ubuntu it seems to cause instability in X; and on Debian, while suspend works, wakeup from suspend seems quite unreliable.

If you run into such issues (i.e. you are using Mint 10), you can fix this by disabling the kernel module during suspend. See [[Fix_for_suspend_problems_on_T410s_with_touchscreen|Fix for suspend problems on T410s with touchscreen]].

Category:X200 Tablet

2025-05-03T01:48:23Z

ThinkGNU: "in linux" is not correct. It's not hypothetical, it's merely a technical and interest matter. grammar. Bluetooth uses an internal antenna, thus that won't be a conflict.

{| 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 X200 Tablet ===
This page gives an overview of the ThinkPad X200 Tablet.

==== Standard Features ====
*One of the following [[Intel Core 2 Duo (Penryn)]] processors:
** Intel® Core™ 2 Duo processor SU9300 (1.2GHz, 800MHz FSB, 3MB L2 cache)
** Intel® Core™ 2 Duo processor SL9300 (1.6Ghz, 1066Mhz FSB, 6MB L2 cache)
** Intel® Core™ 2 Duo processor SL9400 (1.86Ghz, 1066Mhz FSB, 6MB L2 cache)
** Intel® Core™ 2 Duo processor SL9600 (2.13Ghz, 1066Mhz FSB, 6MB L2 cache)
* [[Intel Graphics Media Accelerator 4500MHD]] graphics
* One of the following [[TFT display|TFT displays]]:
** 12.1" 1280x800 (CCFL backlight) 190 nit, FFS
** 12.1" 1280x800 (LED backlight) 285 nit, IPS
** 12.1" 1280x800 (LED backlight) 200 nit, IPS
** 12.1" 1280x800 (LED backlight) 230 nit, IPS, MultiView, [[MultiTouch]]
** 12.1" 1280x800 (LED backlight) 270 nit, IPS, MultiView, [[MultiTouch]]
** 12.1" 1280x800 (LED backlight) 400 nit, IPS, Outdoor
* 2 or 4GB [[PC3-8500]] memory standard, upgradable to 8GB
* One of the following hard drives:
** 80GB SSD 1.8" SATA
** 128GB SSD 1.8" SATA
** 160GB 5400RPM 2.5" SATA
** 160GB 7200RPM 2.5" SATA
** 250GB 5400RPM 2.5" SATA
* 5-in-1 (MMC/SD/SDHC and MS/MS Pro) Media card Reader
* [[Intel Gigabit Ethernet (10/100/1000) PCI-Express]]
* [[ThinkPad Modem (MDC-3.0, 56kbps HDA)]]
* [[MiniPCI Express slot]] 1 with one of the following:
** [[Intel Wifi Link 5100 (AGN)]]
** [[Intel Wifi Link 5300 (AGN)]]
** [[Intel WiMAX/WiFi Link 5350]]
** [[ThinkPad 11b/g/n Wireless LAN Mini-PCI Express Adapter II]]
* [[MiniPCI Express slot]] 2 with one of the following:
** none (empty, not upgradable)
** none (WWAN upgradable)
** [[Sierra Wireless MC5725|Verizon Mobile Broadband with GPS]]
** [[Ericsson F3507g Mobile Broadband Module|AT&T Mobile Broadband with GPS]]
* [[MiniPCI Express slot]] 3 with one of the following:
** none (empty)
** [[Intel® Turbo Memory hard drive cache]] 2GB
** Lenovo Wireless USB Module
* [[ExpressCard slot|ExpressCard/54 slot]]
* [[ThinkPad_Bluetooth_with_Enhanced_Data_Rate_(BDC-2.1)|Bluetooth]] on select models
* [[TrackPoint]]
* Fingerprint reader (Authentec 2810) on select models
* Intel HD Audio with a [[CX20561]] codec
* 1.3MP [[Integrated camera]] on select models
* [[Embedded Security Subsystem|Trusted Computing Group TPM 1.2]]
* [[Active Protection System]]
* Battery Sizes - 4 cell, 8 cell (sticks out the back)
</div>
|style="vertical-align:top" |
[[Image:ThinkPadX200_Tablet.jpg|ThinkPad X200 Tablet|300px]]
|}

==== Resources ====
*{{IBMDOCURL|MIGR-70830|Hardware Maintenance Manual - ThinkPad X200/X201 Tablet (45n3683_04.pdf 15774415 octet)}}

==== Notes ====
Sometimes even basic information is hard to find. Here's a place for it.

* The standard '''X200T does ''not'' support [http://en.wikipedia.org/wiki/Multi-touch Multi-touch]!'''. Only the "Enhanced MultiTouch" supports true MultiTouch. The standard X200T uses Wacom's no-longer-cutting-edge non-multitouch screen. Only one contact point is available in hardware.
** Although, you probably could get two points from a MultiTouch screen, one from finger contact, and one from a stylus hovering over but not touching the screen (available from Linux as separate devices under /sys/class/input), nobody has tried so far and there's a chance the hardware could lock or clear the "hover" position during a touch.
* [[GPS]] - If you have an optional WWAN card (AT&T or Verizon), you have GPS. ''unconfirmed''
* The 5300 normally has 3 x 3 antennas. Adding the webcam reduces this to 2 x 2. ''unconfirmed''
* X200T configured with SSD do '''not''' include the [[Active Protection System]] accelerometer, despite alternate uses (theft deterrence). Confirmed by Lenovo US sales phone, 2008-10. [[User:Mitchell|Mitchell]] 21:54, 28 October 2008 (CET)
** My x200t that shipped with an SSD (Feb 2009) *does* include the accelerometer. I suspect that the same accelerometer is the one used to automatically change the screen orientation, so it doesn't make sense that any of the tablets wouldn't include it. There's also only a single part number for the motherboard in the Hardware Maintenance Manual: if there was a revision used for units shipped with SSDs it would likely be listed separately.
* The [http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=AN&subtype=CA&htmlfid=897/ENUS108-588&appname=lenovous&language=en X200 Tablet Sleeve] supports 4 and 8 cell batteries, but not 9 cell. ''from announcement''

[[Category:X Series]]

Category:R400

2025-05-01T12:24:01Z

ThinkGNU: Those spaces shouldn't be there.

{| 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 R400 ===
This page gives an overview of the ThinkPad R400.

=== Machine Type ===
{{HELP|Did switchable Graphics models exist? I cannot find any such hybrid model Machine Types, even though there was talk of it in the press and some Lenovo datasheets seem to suggest they did exist}}
* 2782, 2783, 2784, 2786, 2787, 2788, 2789 AMD Mobility Radeon HD3470
* 7438, 7439, 7440, 7443, 7445, 7446, 7447 Intel Graphics GMA 4500MHD

It appears that some models (such as 2784-R1U) were also shipped with nVidia Ge Force 9300M graphics

==== Standard Features ====
* One of the following processors:
** [[Intel Core 2 Duo (Merom)]] T5870 and 5670
** [[Intel Core 2 Duo (Penryn)]] P8400, P8600, T9400 and T9600
** [[Intel Celeron M| Intel Celeron M (Merom L)]] 575 and 585
* Chipset
** Mobile Intel® GM45 Express CS/ICH 9M-E
** Mobile Intel® GMA X4500 HD
** Mobile Intel® GL667 MHz (Celeron®)
* One of the following graphics adapters:
* [[nVidia GeForce 9300M]]
** [[Intel Graphics Media Accelerator 4500MHD]]
** [[Switchable Graphics]] with [[Intel Graphics Media_Accelerator 4500MHD|Intel GMA 4500MHD]] and [[ATI Mobility Radeon HD 3470]]
* One of the following displays:
** 14.1" wide: WXGA (1280 x 800, 107DPI, 185+ nit)
** 14.1" wide: WXGA+ (1440 x 900, 120DPI, 200+ nit)
*System Memory
** Up to 8GB of [[PC3-8500]] 1066MHz DDR3
*Harddrive
** 80, 160, 250 or 320GB 5400RPM SATA HDD
** 160, 200GB (FDE) 7200 RPM SATA HDD
* [[Intel Gigabit Ethernet (10/100/1000) PCI-Express]]
* Intel HD Audio with a [[CX20561]] codec
* [[ThinkPad Modem (MDC-3.0, 56kbps HDA)]]
* [[MiniPCI Express slot]] 1 with one of the following:
** [[Intel Wifi Link 5100 (AGN)]] (1x2AGN)
** [[Intel Wifi Link 5300 (AGN)]] (3x3 AGN)
** [[ThinkPad 11b/g/n Wireless LAN Mini-PCI Express Adapter II]]
* [[MiniPCI Express slot]] 2 with one of the following:
** None (not upgradable)
** [[Intel® Turbo Memory hard drive cache]] up to 2GB
** [[Wireless USB (UWB)]]
* 1 [[CardBus slot]] (Type 2)
* under which there one of:
** [[ExpressCard slot|ExpressCard/54 slot]]
** SmartCard reader
** [[Ricoh_R5C843|4-in-1 Memory reader]]
* [[Embedded Security Subsystem|Trusted Computing Group TPM 1.2]]
* [[Active Protection System]]
* [[Integrated Fingerprint Reader]] on select models
* [[ThinkPad_Bluetooth_with_Enhanced_Data_Rate_(BDC-2.1)|Bluetooth]] on select models
* [[UltraNav]] (TrackPoint / Touchpad combo)
* 1.3MP [[Integrated camera]] on select models
* [[Firewire Port|Firewire 400]] (IEEE1394a) on selected models
</div>
|style="vertical-align:top" |
[[image:ThinkPadR400.jpg|ThinkPad R400|300px]]
|}

[[Category:R Series]]

Code/thinkpad-smapi.sh

2025-04-13T09:31:59Z

ThinkGNU: William confirmed via email that; "As for your request, sure, I will license it to you under GPLv3 or later."

<pre>
#!/bin/bash
# Copyright (C) 2007 William Poetra Yoga Hadisoeseno <williampoetra@gmail.com>
# This file is licensed under the GPL version 3, or (at your option) any later version.
# E-mail me if you have any ideas of other licenses to use (BSD, Public Domain, etc.), I'm open :)

# IDEAS
# - make an ncurses interface, and also maybe gtk+ and qt
# - add option to enable modifying the charge control variables

TP_SMAPI_BASE=/sys/devices/platform/smapi

# function to simplify reading from files
# syntax: read_file <variable> <filename> <check_return_value 0/1> <translate 0/1> [[value] [translation_string]]
read_file()
{
local VARIABLE
local FILENAME
local CHECK_RETURN
local TRANSLATE
local VAL
local RET

VARIABLE="$1"; shift
FILENAME="$1"; shift
CHECK_RETURN="$1"; shift
TRANSLATE="$1"; shift

VAL=`cat "$FILENAME" 2> /dev/null`
RET=$?

if [[ "$CHECK_RETURN" == "1" ]] && [[ $RET -gt 0 ]]
then
RESULT="[unavailable]"
elif [ "$TRANSLATE" == "1" ]
then
RESULT="unknown ($RET)"
while [ -n "$1" ]
do
if [ "$VAL" == "$1" ]
then
RESULT="$2"
break
fi
shift 2
done
else
RESULT="$VAL"
fi

eval "$VARIABLE="'"'"$RESULT"'"'
# eval "$VARIABLE=$RESULT"
}

give_units()
{
local VARIABLE
local UNIT
local VALUE
local RESULT

VARIABLE="$1"
UNIT="$2"
eval "VALUE=\$$VARIABLE"

if (echo "$VALUE" | grep -qs "^-\?[0-9]")
then
RESULT="$VALUE $UNIT"
else
RESULT="$VALUE"
fi

eval "$VARIABLE="'"'"$RESULT"'"'
}

replace_val()
{
local VARIABLE
local OLD_VALUE
local NEW_VALUE
local VALUE
local RESULT

VARIABLE="$1"
OLD_VALUE="$2"
NEW_VALUE="$3"

eval "VALUE=\$$VARIABLE"

if [ "$VALUE" == "$OLD_VALUE" ]
then
RESULT="$NEW_VALUE"
else
RESULT="$VALUE"
fi

eval "$VARIABLE="'"'"$RESULT"'"'
}

show_help()
{
cat << EOF

thinkpad-smapi.sh - Show SMAPI information on ThinkPad laptops, through
the exported SMAPI information by the tp_smapi module.

-a Show all available information
-b [n] Show all available information for battery [n]
-h Show this help text
-m Show miscellaneous information

EOF
}

show_misc()
{
cd $TP_SMAPI_BASE

read_file PCI_POWER_SAVINGS "enable_pci_power_saving_on_boot" 1 1 1 "enabled" 0 "disabled"
read_file AC_ADAPTER "ac_connected" 1 1 1 "connected" 0 "disconnected"

cat << EOF
MISCELLANEOUS INFORMATION
=========================

PCI power savings on boot: $PCI_POWER_SAVINGS
AC adapter status: $AC_ADAPTER

EOF
}

show_batt()
{
SLOT=$1
cd $TP_SMAPI_BASE/BAT$SLOT

TMP=`cat installed`
if [ $TMP -eq 1 ]
then
BATT_INSTALLED="yes"
else
BATT_INSTALLED="no"
fi

BATT_STATE=`cat state`

if [ $BATT_INSTALLED == "yes" ]
then

read_file BARCODING "barcoding" 1 0
read_file BATT_CHEMISTRY "chemistry" 1 0
read_file DESIGN_CAPACITY "design_capacity" 1 0
read_file DESIGN_VOLTAGE "design_voltage" 1 0
read_file MANUFACTURE_DATE "manufacture_date" 1 0
read_file BATT_FRU "model" 1 0
read_file MANUFACTURER "manufacturer" 1 0
read_file BATT_SERIAL "serial" 1 0

read_file FIRST_USE_DATE "first_use_date" 1 0
read_file CYCLE_COUNT "cycle_count" 1 0
read_file LAST_FULL_CAPACITY "last_full_capacity" 1 0
read_file CURRENT_1MIN "current_avg" 1 0
read_file POWER_1MIN "power_avg" 1 0

read_file CAPACITY_MWH "remaining_capacity" 1 0
read_file CAPACITY_PERCENT "remaining_percent" 1 0
read_file REMAINING_RUNNING_TIME "remaining_running_time" 1 0
read_file CURRENT_NOW "current_now" 1 0
read_file POWER_NOW "power_now" 1 0
read_file BATT_TEMPERATURE "temperature" 1 0
read_file BATT_VOLTAGE "voltage" 1 0
read_file REMAINING_CHARGING_TIME "remaining_charging_time" 1 0

# fixups
give_units DESIGN_CAPACITY "mWh"
give_units DESIGN_VOLTAGE "mV"
give_units CURRENT_NOW "mA"
give_units POWER_NOW "mW"
give_units CURRENT_1MIN "mA"
give_units POWER_1MIN "mW"
give_units LAST_FULL_CAPACITY "mWh"
give_units REMAINING_RUNNING_TIME "min"
give_units REMAINING_CHARGING_TIME "min"
give_units CAPACITY_PERCENT "%"
give_units BATT_TEMPERATURE "mC"
give_units BATT_VOLTAGE "mV"

# some more
replace_val REMAINING_RUNNING_TIME "not_discharging" "[not discharging]"
replace_val REMAINING_CHARGING_TIME "not_charging" "[not charging]"

else

BATT_FRU=
MANUFACTURER=
BATT_SERIAL=
BARCODING=
BATT_CHEMISTRY=
DESIGN_CAPACITY=
DESIGN_VOLTAGE=
MANUFACTURE_DATE=

FIRST_USE_DATE=
CYCLE_COUNT=
LAST_FULL_CAPACITY=
CURRENT_1MIN=
POWER_1MIN=

CAPACITY_MWH=
CAPACITY_PERCENT=
REMAINING_RUNNING_TIME=
CURRENT_NOW=
POWER_NOW=
BATT_TEMPERATURE=
BATT_VOLTAGE=
REMAINING_CHARGING_TIME=

fi

read_file START_CHARGE_THRESH "start_charge_thresh" 1 0
read_file STOP_CHARGE_THRESH "stop_charge_thresh" 1 0
read_file INHIBIT_CHARGE_MIN "inhibit_charge_minutes" 1 0
read_file BATT_FORCE_DISCHARGE "force_discharge" 1 1 1 "yes" 0 "no"

# installed*, state*, dump
# barcoding, chemistry, design_capacity, design_voltage, manufacture_date, model, manufacturer, serial
# first_use_date, cycle_count, last_full_capacity, current_avg, power_avg
# remaining_capacity, remaining_percent, remaining_running_time, current_now, power_now, temperature, voltage, remaining_charging_time
# start_charge_thresh*, stop_charge_thresh*, inhibit_charge_minutes*, force_discharge*

cat << EOF
BATTERY $SLOT INFORMATION
=====================

Battery slot:
Battery present: $BATT_INSTALLED
Battery state: $BATT_STATE

EOF

if [ "$BATT_INSTALLED" == "yes" ]
then
cat << EOF
Embedded info:
FRU P/N: $BATT_FRU
Barcoding: $BARCODING
Serial number: $BATT_SERIAL
OEM Manufacturer: $MANUFACTURER
Chemistry: $BATT_CHEMISTRY
Manufacture date: $MANUFACTURE_DATE
Design capacity & voltage: $DESIGN_CAPACITY, $DESIGN_VOLTAGE

Battery health:
First use date: $FIRST_USE_DATE
Cycle count: $CYCLE_COUNT
Last full capacity: $LAST_FULL_CAPACITY
Average current / power (past 1 minute): $CURRENT_1MIN, $POWER_1MIN

Battery status:
Remaining capacity: $CAPACITY_MWH mWh ($CAPACITY_PERCENT)
Remaining running time: $REMAINING_RUNNING_TIME
Running current & power: $CURRENT_NOW, $POWER_NOW
Temperature: $BATT_TEMPERATURE
Voltage: $BATT_VOLTAGE
Remaining charging time: $REMAINING_CHARGING_TIME

EOF
fi

cat << EOF
Battery charging control:
Start charging at: $START_CHARGE_THRESH %
Stop charging at: $STOP_CHARGE_THRESH %
Prevent charging for: $INHIBIT_CHARGE_MIN min
Force battery discharge: $BATT_FORCE_DISCHARGE

EOF
}

SHOW_ALL=
SHOW_BATT=
SHOW_MISC=
GOT_OPTS=

while getopts ab:hm OPT
do
GOT_OPTS=y
case ${OPT} in
a) SHOW_ALL=y;;
b) if [ ${OPTARG} -eq 0 -o ${OPTARG} -eq 1 ]
then
SHOW_BATT=${OPTARG}
else
SHOW_BATT=y
fi
;;
h) show_help
exit 0
;;
m) SHOW_MISC=y;;
\?) show_help
exit 1
;;
esac
done

if [ "$GOT_OPTS" != y ]
then
show_help
exit 1
fi

if [ "$SHOW_ALL" == y ]
then
show_misc
show_batt 0
show_batt 1
else
if [ -n "$SHOW_MISC" ]
then
show_misc
fi
if [ -n "$SHOW_BATT" ]
then
show_batt $SHOW_BATT
fi
fi
</pre>

Switchable Graphics

2025-04-12T02:04:27Z

ThinkGNU: Fixed broken link.

Select ThinkPads feature switchable graphics, where a low power consumption integrated GPU and high performance dedicated GPU is combined and you have the ability to switch between them, sacrificing either performance or battery life.

In Windows XP this switching requires a logout/login, while in Vista and Windows 7 there is support for runtime switching.

Under GNU/Linux, switching can be configured by entering BIOS setup and choosing between the "Internal" (low power, integrated), "External" (high performance, discrete) or "Switchable" (OS selectable) options.

Depending on which GNU/Linux version you use, you could have the following effects
* On Ubuntu 8.10 (Intrepid) BIOS setting has to be either on Internal or External, not Switchable.
* On Ubuntu 9.10 (Karmic) the Integrated Intel card works with both Integrated or Switchable set
* On Ubuntu 13.10 and above, see [http://www.junauza.com/2014/03/how-to-get-nvidia-optimus-working-on-ubuntu-linux.html How to Get NVIDIA Optimus Working on Ubuntu]

== Switchable Graphics and Docks ==

ThinkPads with switchable graphics can only drive DVI or DisplayPort outputs on Docks by using the high-performance discrete graphics card, the integrated GPU is just not attached to the DVI or DisplayPort outputs (though VGA output through the dock is possible).

== Improving Battery-life with Optimus ==
ThinkPads with NVidia Optimus graphics, have been well known to have significantly better battery-life in Windows than in GNU/Linux, even when GNU/Linux only uses the internal graphics. The reason is that the NVidia GPU is not automatically powered off when it is not used. So to get optimal battery-life in GNU/Linux on ThinkPad with Optimus, you need to switch it off manually (or by a script).

First you need to enable access to vga-switcheroo settings, for that you need to mount the debugfs. You can do that by adding the following line to {{path|/etc/fstab}}:
none /sys/kernel/debug debugfs defaults 0 0

After mounting that you can now access {{path|/usr/kernel/debug/vgaswitcheroo/switch}}.

See which GPU is currently active (look for '+'), and which ones are powered (look for 'pwr'):
{{cmdroot|cat /sys/kernel/debug/vgaswitcheroo/switch}}

To force it to use the internal graphics write:
{{cmdroot|echo 'IGD' > /sys/kernel/debug/vgaswitcheroo/switch}}

To force it to use the discrete GPU:
{{cmdroot|echo 'DES' > /sys/kernel/debug/vgaswitcheroo/switch}}

Most importantly, to poweroff the currently unused GPU, run:
{{cmdroot|echo 'OFF' > /sys/kernel/debug/vgaswitcheroo/switch}}

Your average battery-life will greatly improved on the ThinkPad T420 if you only use intel integrated.

== Development status ==
David Arlie worked on switching between GPUs without having to reboot or change BIOS settings. An initial version of a new driver (vga_switcheroo) was merged in the 2.6.34 kernel. This driver allowed switching between graphics cards, but required restarting the X server.

http://www.phoronix.com/scan.php?page=news_item&px=ODAyMg

Seamless runtime switching support required significant X server work, which was later completed. If free software graphics drivers are used, integrated or discrete graphics can now be selected via configuration of the DRI_PRIME environmental value globally, or per application.

Generally, integrated is renderer 0 and discrete is renderer 1 as below (although it is possible for the order to be reversed);
<pre>
DRI_PRIME=0 glxinfo | grep "OpenGL renderer"
OpenGL renderer string: <renderer>
DRI_PRIME=1 glxinfo | grep "OpenGL renderer"
OpenGL renderer string: <renderer>
</pre>

To default to integrated for all graphical programs, add to .bash_profile;
<pre>
#default to integrated
export DRI_PRIME=0
#default to discrete
#export DRI_PRIME=1
</pre>
You would comment the integrated export and uncomment the discrete export to default to discrete.

Even with a default selection, you can still select which GPU to use at runtime by setting the DRI_PRIME variable (see the glxinfo example).

A script to switch between ATI discrete graphics with the fglrx driver and Intel integrated graphics with xorg driver through rebooting and selection in the bios is posted here. The user must reboot, but no further configuration is needed as the script detects the card used and copies the correct libraries and configuration file.

http://www.thinkwiki.org/wiki/Auto_detect_drivers_for_switchable_graphics

It has been discovered that on a W500 running Windows 7 64-bit that the switch can be invoked using one of the two following commands (depending on which chipset is currently in use)

{{cmd|C:\PROGRA~2\ThinkPad\UTILIT~1\PWMUIAux.exe /HighPerformanceGpu |}}

{{cmd|C:\PROGRA~2\ThinkPad\UTILIT~1\PWMUIAux.exe /EnergySavingGpu |}}

A small utility has been developed to switch between the chipsets with the ThinkVantage button, using Windows SetupAPI to detect the current chipset. More information and download of source and binary available here: http://entropicassembly.com/thinkpadgraphics/

== ThinkPad models which may have this feature ==
* {{R400}}
* {{T400}}, {{T500}}, {{T510i}}, {{T420}}, {{T420s}}, {{T520}}, {{T430s}}
* {{W500}}, {{W520}}, {{W530}}

Switchable Graphics

2025-04-12T02:02:05Z

ThinkGNU: Linux is only a kernel. Updated information and added DRI_PRIME graphics switching information.

Select ThinkPads feature switchable graphics, where a low power consumption integrated GPU and high performance dedicated GPU is combined and you have the ability to switch between them, sacrificing either performance or battery life.

In Windows XP this switching requires a logout/login, while in Vista and Windows 7 there is support for runtime switching.

Under GNU/Linux, switching can be configured by entering BIOS setup and choosing between the "Internal" (low power, integrated), "External" (high performance, discrete) or "Switchable" (OS selectable) options.

Depending on which GNU/Linux version you use, you could have the following effects
* On Ubuntu 8.10 (Intrepid) BIOS setting has to be either on Internal or External, not Switchable.
* On Ubuntu 9.10 (Karmic) the Integrated Intel card works with both Integrated or Switchable set
* On Ubuntu 13.10 and above, see [http://www.junauza.com/2014/03/how-to-get-nvidia-optimus-working-on-ubuntu-linux.html | How to Get NVIDIA Optimus Working on Ubuntu Linux]

== Switchable Graphics and Docks ==

ThinkPads with switchable graphics can only drive DVI or DisplayPort outputs on Docks by using the high-performance discrete graphics card, the integrated GPU is just not attached to the DVI or DisplayPort outputs (though VGA output through the dock is possible).

== Improving Battery-life with Optimus ==
ThinkPads with NVidia Optimus graphics, have been well known to have significantly better battery-life in Windows than in GNU/Linux, even when GNU/Linux only uses the internal graphics. The reason is that the NVidia GPU is not automatically powered off when it is not used. So to get optimal battery-life in GNU/Linux on ThinkPad with Optimus, you need to switch it off manually (or by a script).

First you need to enable access to vga-switcheroo settings, for that you need to mount the debugfs. You can do that by adding the following line to {{path|/etc/fstab}}:
none /sys/kernel/debug debugfs defaults 0 0

After mounting that you can now access {{path|/usr/kernel/debug/vgaswitcheroo/switch}}.

See which GPU is currently active (look for '+'), and which ones are powered (look for 'pwr'):
{{cmdroot|cat /sys/kernel/debug/vgaswitcheroo/switch}}

To force it to use the internal graphics write:
{{cmdroot|echo 'IGD' > /sys/kernel/debug/vgaswitcheroo/switch}}

To force it to use the discrete GPU:
{{cmdroot|echo 'DES' > /sys/kernel/debug/vgaswitcheroo/switch}}

Most importantly, to poweroff the currently unused GPU, run:
{{cmdroot|echo 'OFF' > /sys/kernel/debug/vgaswitcheroo/switch}}

Your average battery-life will greatly improved on the ThinkPad T420 if you only use intel integrated.

== Development status ==
David Arlie worked on switching between GPUs without having to reboot or change BIOS settings. An initial version of a new driver (vga_switcheroo) was merged in the 2.6.34 kernel. This driver allowed switching between graphics cards, but required restarting the X server.

http://www.phoronix.com/scan.php?page=news_item&px=ODAyMg

Seamless runtime switching support required significant X server work, which was later completed. If free software graphics drivers are used, integrated or discrete graphics can now be selected via configuration of the DRI_PRIME environmental value globally, or per application.

Generally, integrated is renderer 0 and discrete is renderer 1 as below (although it is possible for the order to be reversed);
<pre>
DRI_PRIME=0 glxinfo | grep "OpenGL renderer"
OpenGL renderer string: <renderer>
DRI_PRIME=1 glxinfo | grep "OpenGL renderer"
OpenGL renderer string: <renderer>
</pre>

To default to integrated for all graphical programs, add to .bash_profile;
<pre>
#default to integrated
export DRI_PRIME=0
#default to discrete
#export DRI_PRIME=1
</pre>
You would comment the integrated export and uncomment the discrete export to default to discrete.

Even with a default selection, you can still select which GPU to use at runtime by setting the DRI_PRIME variable (see the glxinfo example).

A script to switch between ATI discrete graphics with the fglrx driver and Intel integrated graphics with xorg driver through rebooting and selection in the bios is posted here. The user must reboot, but no further configuration is needed as the script detects the card used and copies the correct libraries and configuration file.

http://www.thinkwiki.org/wiki/Auto_detect_drivers_for_switchable_graphics

It has been discovered that on a W500 running Windows 7 64-bit that the switch can be invoked using one of the two following commands (depending on which chipset is currently in use)

{{cmd|C:\PROGRA~2\ThinkPad\UTILIT~1\PWMUIAux.exe /HighPerformanceGpu |}}

{{cmd|C:\PROGRA~2\ThinkPad\UTILIT~1\PWMUIAux.exe /EnergySavingGpu |}}

A small utility has been developed to switch between the chipsets with the ThinkVantage button, using Windows SetupAPI to detect the current chipset. More information and download of source and binary available here: http://entropicassembly.com/thinkpadgraphics/

== ThinkPad models which may have this feature ==
* {{R400}}
* {{T400}}, {{T500}}, {{T510i}}, {{T420}}, {{T420s}}, {{T520}}, {{T430s}}
* {{W500}}, {{W520}}, {{W530}}

Install Mandriva 2009.0 on a ThinkPad W500

2025-04-12T01:36:33Z

ThinkGNU: Linux is only a kernel. Spelling. Added correction about EC mute.

[[:Category:W500|W500]] {{NOTE|The below issues have been fixed in later GNU/Linux versions, but they have been left in case someone decides to try installing Mandriva 2009.0 for some reason.}}

==BIOS Issues==

* [[Switchable Graphics]]
GNU/Linux with X.Org previously lacked the support for on-the-fly switching of GPUs. It not only did not support switching, you also had to explicitly turn off switching in BIOS. Go to Config->Display->Graphics Device and '''DISABLE''' OS detection of switchable graphics.

If you don't disable OS detection, Linux will enumerate two graphic adapters (see `lspci` output) and X.Org will be confused as to which one to use, leading to random weird side effects such as hangs and worse.

* AHCI
I also had to turn off AHCI in Config->SATA and used '''Compatibility Mode''' instead, otherwise the kernel would not boot occasionally.

* Intel Virtualization
The T9400 and up CPUs also support advanced Intel Virtualization technologies. Just don't turn on '''VT-d''' (disk I/O virtualization) in BIOS, otherwise WLAN any a couple of other things will not work and even freeze your system, see [https://qa.mandriva.com/show_bug.cgi?id=44711 https://qa.mandriva.com/show_bug.cgi?id=44711]

==Things not working/issues==

As I've found most of the components are just working out of the box, I will only list the issues I have found so far:

* booting with "vga=788" not working
** the Mandriva installer added the "vga=788" parameter to my Linux boot line. That prevented the laptop from booting quite frequently, not always though. Still to be investigated, but removing "vga=788" from the kernel boot line solved the issue for now.
* [[Active Protection System]]
** HD-APS is not working for me, probably due to a BIOS bug, see [http://bugzilla.kernel.org/show_bug.cgi?id=12221 http://bugzilla.kernel.org/show_bug.cgi?id=12221]
*** some kind of workaround is to add pnpacpi=off to the kernel boot line, but that turns off ACPI, which is no real option
* Suspend/Resume
** while suspending works fine, resuming always ended with a blank screen, workaround below
* muted audio not shown in alsamixer
** when you use the built in "mute audio" button on the ThinkPad keyboard, the EC does a hardware mute without sending a XF86AudioMute event, so the mute state will not show in any audio mixer. So if you don't hear a sound, press the "mute audio" or "volume up" button to unmute :-)
* 3D and radeonhd
** the radeonhd driver did not support 3D acceleration
* 2D and fglrx
** see below

== Suspend/Resume problem ==

If resuming just leaves you with a blank black display, try the following:

echo "ADD_PARAMETERS='--quirk-vbe-post'" > /etc/pm/config.d/w500_vbe_post

== Display / Xorg ==

The laptop comes with [[Switchable Graphics]], so you can choose on your own which GPU to use:

* intel
** consumes the least energy
** DVI connector on the [[ThinkPad Advanced Mini Dock]] ist not recognoized
** a static dual head configuration gives weird background garbage when one of the statically configured monitors is not connected, see [http://bugs.freedesktop.org/show_bug.cgi?id=19412 http://bugs.freedesktop.org/show_bug.cgi?id=19412]

* radeonhd
** consumes the most energy
** lack of 3D support

* fglrx
** changing runlevel to 3 (init 3) leaves you with X eating 100% CPU
** huge performance issues when switching between virtual desktops, switching can take a couple of seconds with 100% CPU again

So if battery life and 3D are important for you, you should probably use the intel driver, but I am fine with the radeonhd driver for now. And fglrx is nothing but proprietary nonsense, IMHO ... for a '''commercial''' driver this is ridiculous.

[[Category:W500]][[Category:Mandriva]]

Category:W500

2025-04-12T01:12:07Z

ThinkGNU: Those are GNU/Linux distro's, so you are installing GNU/Linux and not just Linux.

Intel GMA 4500MHD

2025-04-12T01:10:31Z

ThinkGNU: X.org is not Linux. Linux is only a kernel. intel-gfx is for Xorg, although it's xf86-video-intel now (I can't tell if anyone bothered to implement video acceleration for the 4500MHD).

__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;">
=== Intel Graphics Media Accelerator 4500MHD ===
This is an Intel video adapter

=== Features ===
* Integrated into the following chipsets:
** [[Intel GM45]]
* PCI ID: 8086:2a42
* Uses part of main memory for video usage
</div>
|style="vertical-align:top" |
|}

== Linux KMS ==
KMS (Kernel Mode Setting) is a recent development, and requires that you have at least kernel 2.6.31 and Intel Xorg driver version 2.8. But newer is better. With the 2.6.32 kernel and Intel Xorg driver 2.9 you can expect full functionality including external displays and 3D acceleration. However, Linux >=3.19 should be used because it includes a fix for a [https://bbs.archlinux.org/viewtopic.php?id=190528 Graphics Corruption Bug].

== X.Org driver User Mode Setting ==
{{NOTE|UMS where the mode setting is done by the Xorg driver in user-land is deprecated and newer versions of the Intel Xorg driver (v2.10+) no longer support it. Instead you will have to use KMS (Kernel Mode Setting)}}

Make sure you're using Intel Xorg driver, version 2.8 or 2.9.

== HD video acceleration ==
The hardware does support acceleration of video decoding, but it's not yet supported by X.Org's intel-gfx. Support '''was''' supposed to arrive in [http://lists.freedesktop.org/archives/intel-gfx/2010-March/006404.html Q3 2010] via libva. There is already MPEG2 acceleration for this chip though.

== ThinkPad models with this component==
* {{Edge 13"}} (Intel)
* {{R400}}, {{R500}}
* {{SL300}}, {{SL400}}, {{SL400c}}, {{SL410}}, {{SL500}}, {{SL500c}}, {{SL510}}
* {{T400}}, {{T400s}}, {{T500}}
* {{W500}}
* {{X200}}, {{X200s}}, {{X200 Tablet}}, {{X301}}

== Resources ==
* [https://web.archive.org/web/20100811005120/http://www.intel.com/design/chipsets/embedded/GM45/index.htm http://www.intel.com/design/chipsets/embedded/GM45/index.htm (archived from the original)]
* http://www.notebookcheck.net/Intel-Graphics-Media-Accelerator-4500MHD-GMA-X4500MHD.9883.0.html
* https://01.org/linuxgraphics

ATI Mobility Radeon X1300

2025-04-12T00:57:23Z

ThinkGNU: Linux is not X.Org. Linux's terminal emulator is called fbcon.

== Features ==
* Chipset: ATI M52
* PCI ID: 1002:7149
* PCI Express x16
* 64MB GDDR1 video memory

== X.Org driver ==
Supported by either recent versions of the [[radeon]] driver or the [[radeonhd]] driver (availible in debian stable).
3D is even working with latest versions of mesa (7.1rc3) and xorg from debian experimental (as of July 20, 2008).

== ThinkPad LCD ==
Display on the internal LCD works as long as you set the monitor settings correct.

== External VGA port ==
Using the radeon driver, VGA port is enabled or disabled by using "xrandr --auto" if something is plugged in or unplugged.

== SVideo port ==
??

== DVI port ==
DVI port is enabled in T60.

Using the proprietary driver the Dell 2405FPW works at 1920x1200 pixels via Advanced Mini Dock.

== Proprietary ATI driver ==
[[Fglrx]] supports this card since release 8.24.8.

driver by ATI

https://support.ati.com/ics/support/KBAnswer.asp?questionID=18875

== Linux fbcon Framebuffer driver ==
* OS: RHEL4-U3
* Kernel: 2.6.9-34
* X Version: 6.8.2-1
* Result: ''Failure''
** Driver can't find a compatible card

== ThinkPads this chip may be found in ==
* {{T60}}

[[Category:Video Controllers]]

Problem with high pitch noises

2025-04-12T00:56:11Z

ThinkGNU: Linux is not an OS. Typo.

Information on strange high pitch, low volume noises emitted by ThinkPads.

==Problem description==
Even though ThinkPads are known as very silent notebooks, they tend to emit different, mostly high pitch noises in certain circumstances. The noises are of low volume and hence not realized by everyone or at least tolerated by most people. However, there are those with "bat like ears" that hear them and might be annoyed by that.

==Affected Models==
Noises have been experienced in the following situations:
{| border="1" cellspacing="0" cellpadding="2"
|-
! style="vertical-align:top;background-color:#DDDDDD;" | situation
! style="vertical-align:top;background-color:#DDDDDD;" | noise description
! style="vertical-align:top;background-color:#DDDDDD;" | affected models
|-
| style="vertical-align:top;" |
Plugged into AC / running at high CPU frequency
| style="vertical-align:top;" |
soft crackling, buzzing noise
| style="vertical-align:top;" |
*{{T41}}
**2379-DJU
|-
| style="vertical-align:top;" |
ThinkPad suspended to RAM
| style="vertical-align:top;" |
constant high pitch noise
| style="vertical-align:top;" |
*{{T42p}}
|-
| style="vertical-align:top;" |
ThinkPad connected to power and switched off, with battery fully charged
| style="vertical-align:top;" |
constant high pitch noise
| style="vertical-align:top;" |
*{{T41p}}
**2373-GHG
|-
| style="vertical-align:top;" |
moving windows or just the mouse in xorg
| style="vertical-align:top;" |
strange noise like a rapid series of very short high pitch noises adding to a constant kind of whistling (only as long as the movement goes)
| style="vertical-align:top;" |
*{{A21m}}
**2628
*{{T41p}}
**2373-GHG
*{{T60}}
|-
| style="vertical-align:top;" |
Thinkpad connected to power or working on battery, also when suspended to RAM
| style="vertical-align:top;" |
High pitch noise also when HD is powered down.
| style="vertical-align:top;" |
*{{T23}}
**2647-DG4
*{{X24}}
**2662-MWG
|-
| style="vertical-align:top;" |
Thinkpad connected to power battery charged less than 60%
| style="vertical-align:top;" |
High pitch noise till battery is charged more than 60%.
| style="vertical-align:top;" |
*{{T41p}}
**2373-GEG
|-
| style="vertical-align:top;" |
Constantly, if AC connected
| style="vertical-align:top;" |
High pitched, low volume constant noise.
| style="vertical-align:top;" |
*{{T40}}
**2373-88U
|-
| style="vertical-align:top;" |
When the CPU freq jumps up to 1Ghz or above, or when the laptop is in suspend mode
| style="vertical-align:top;" |
Constant high pitched
| style="vertical-align:top;" |
*{{R50}}
**1829-6DM
|-
| style="vertical-align:top;" |
(May come from harddisk.)
| style="vertical-align:top;" |
continuous, intermittent, low volume, high pitched
| style="vertical-align:top;" |
*{{600X}}
|-
| style="vertical-align:top;" |
ACPI puts the processor into the C3 or C4 power saving states (i.e., the system is idle).
| style="vertical-align:top;" |
High-pitched crackling noise.
| style="vertical-align:top;" |
*{{X61}}
**7673-B56
*{{X41}}
*{{T43}}
**2686-DGU
*{{T43p}}
*{{T60}}
**2007-72U
*{{T21}}
*{{T20}}
**2648-46U
|-
| style="vertical-align:top;" |
Cpufreqd (or powernowd etc.) slows down the processor, for exemple at the end of an heavy task.
| style="vertical-align:top;" |
High-pitched crackling noise.
| style="vertical-align:top;" |
*{{T42}}
|-
| style="vertical-align:top;" |
When on battery
| style="vertical-align:top;" |
Noise level varies from inaudible to clearly audible, screeching sound, or sometimes beeping (when wifi is on).
| style="vertical-align:top;" |
*{{A21m}}
**2628
*{{R51}}
**EHG-1829
*{{R52}}
**1858-A11
**1846-B5G
*{{R60}}
**9461-DXG
**9462-77G
**9456-HTG
**9461-DXG
*{{R60e}}
**0657-A9G
**0657-3LG
*{{T43}}
**2686-DGU
**1871-4AG
*{{T60}}
**2007-72U
**1951-24G
**1951-24G
**2007-49G
**2007-FUG
*{{T60p}}
**2007-FBG
*{{T61}}
**7659-12G
**8898-5FG
**6463-9WG
*{{x60}}
*{{x31}}
**2673-CBU
*{{Z61m}}
**9450-3HG
**9452-128
**9452-W5Q
*{{Z61t}}
**9440-2QU

|-
| CPU is used much AND laptop is on AC power AND the TFT panel is enabled.
| Screetching high pitch noise, like a million crickets
|
* {{X41}}

|-
| Network is pluged in and networkload is ~100%.
| low volume highfreq. pitch noise from left speaker or cpu.
|
*{{Z60m}}, {{Z60t}}
*{{T40}}
*{{T43}}
**2687-DDU

|-
| Constant, but is louder when Tablet Pen is near screen, on battery power
| high pitch noise, screeching sounds *solved by "Media player paused" (see below) and also by BIOS versions 1.05 and later.
|
*{{X60_Tablet}}
**6366-4DU

|-
| When fan is running on some speeds. Turning off fan stops pitch noise instandly.
| High pitch noise ("CPU whining").
|
*{{T60p}}
**2007-83G
|}

==Affected Operating Systems==
All, though GNU/Linux appears especially susceptible.

==Possible sources==

* '''CPU activity:''' On some models the noise is triggered by certain CPU power states or activity patterns (as proven [http://www.wisdom.weizmann.ac.il/~tromer/acoustic here]).
* '''Graphics processor:''' In some models from the T2x era, e.g. the {{T23}}, the problem was related to the graphics circuitry and occured especially or only while making use of DirectDraw functions. IBM was able to fix it through a BIOS upgrade.
* '''Hard disk:''' On some ThinkPads the processor and hard disk are adjacent and produce similar noise. For example, in the {{X41}} the sound generated by the hard disk is likely to be loudest at the vent.
* '''Gigabit Ethernet processor:''' In some models (e.g., {{T43}}) high ethernet activity causes a high pitch noise.
* '''Screen brightness:''' on an {{X31}}, a hissing sound is started whenever screen brightness is not full.
* '''Power supply:''' a T61p is known to have the sound if a 90W power supply revision 01 is used. An alternative power supply of an other manufacturer did not make the laptop noisy.

==Status==

The problem is highly specific to operating system, model and even individual machines. There is no universal solution, but on most machines one of the following will reduce or eliminate the noise (possibly at some cost in power consumption).

==Solutions for CPU-triggered noise==

===Limit ACPI CPU power states===

By default, the kernel supports up to eight ACPI CPU power saving states (C-states), called C1 through C8 (but the ThinkPad BIOS and hardware often offers (or remaps them to) only C1 to C4). Often only the extreme power saving modes C4 or C3 produce the noise, so the noise can be stopped by instructing the Linux ACPI code to use only lower modes. This has a cost, though: disabling C3 and C4 will make the CPU consume more power and reduce battery life.

To forbid the ACPI driver from using C4 (this fixed the problem with on some ThinkPad {{T43}}, {{T43p}} and {{T41}}):
* If the ACPI processor component is compiled as built-in (<tt>CONFIG_ACPI_PROCESSOR=y</tt>):
**Pass the {{bootparm|processor.max_cstate|3}} kernel argument.
* If the ACPI processor component is loaded as a module (<tt>CONFIG_ACPI_PROCESSOR=m</tt> and <tt>processor</tt> shows in the output of {{cmdroot|lsmod}}), do either of:
** Pass the {{bootparm|processor.max_cstate|3}} kernel argument (this does not work in Ubuntu 5.10 with default kernel).
** Add <code>options processor max_cstate=3</code> to {{path|/etc/modprobe.conf}} (or {{path|/etc/modprobe.conf.local}}, or {{path|/etc/modprobe.d/...}}, depending on your system) (this does not work in Ubuntu 5.10 with default kernel).
** {{cmdroot|echo 3 > /sys/module/processor/parameters/max_cstate}} (this can be changed in runtime for experimentation). (If may need to be set again upon resume from suspend, e.g., in the wakeup script.)
** (On Ubuntu 5.10, the default kernel uses <code>processor</code> as a module. Unfortunately, the script loading it, {{path|/etc/init.d/acpid}}, ignores the <code>options processor max_cstate=3</code> setting in {{path|/etc/modprobe.d/<my file>}}. As a solution for this specific problem, add the line <code>echo 2 > /sys/module/processor/parameters/max_cstate</code> directly to {{path|/etc/init.d/acpid}}, at the end of the function <code>load_modules()</code>, immediately after the line <code>echo "$PRINTK" > /proc/sys/kernel/printk</code>.)
** On Gentoo: Configure your Thinkpad as described in the [http://www.gentoo.org/doc/en/power-management-guide.xml Power Management Guide]. Then as root create the files {{path|/etc/init.d/limit-sleep-states}} and {{path|/etc/conf.d/limit-sleep-states}} as below. After that just issue the command {{cmdroot|rc-update add limit-sleep-states default}} to limit the sleep states only when running on AC power, or {{cmdroot|rc-update add limit-sleep-states default battery}} to always limit the sleep states.
cat <<EOF > /etc/init.d/limit-sleep-states
#!/sbin/runscript

depend() {
need acpid
}

start() {
ebegin "Limiting CPU sleep state to C${LIMIT_CSTATE}"
echo $LIMIT_CSTATE > /sys/module/processor/parameters/max_cstate
eend $?
}

stop() {
ebegin "Removing CPU sleep state limit"
echo $REMOVE_CSTATE > /sys/module/processor/parameters/max_cstate
eend $?
}
EOF

cat <<EOF > /etc/conf.d/limit-sleep-states
# limit CPU sleep state to the following value (adjust accordingly)
LIMIT_CSTATE=3
# some value which is higher than all available sleep states
REMOVE_CSTATE=8
EOF

To also forbid the C3 state, replace "<tt>3</tt>" with "<tt>2</tt>" above (this fixed the problem on some ThinkPad {{X40}}, {{X41}}, {{X60}}, {{T60}}, {{T61}}, {{Z61t}} and {{R52}}, as well as on {{T20}} where C4 is not supported at all).

Note that these options affect power consumption when the CPU is idle. For example, here is the [[How to measure power consumption|measured power consumption]] on a ThinkPad {{T43}}:
* {{bootparm|processor.max_cstate|4}}: 15160mW (default, noisy)
* {{bootparm|processor.max_cstate|3}}: 15770mW (660mW higher, silent)
* {{bootparm|processor.max_cstate|2}}: 16100mW (2940mW higher, silent)

One can control how often Linux tries to enter the C3 state by using the {{bootparm|processor.bm_history|<bitmask>}} parameter on kernels with a scheduler frequency below 800Hz (and if you have noise problems, you really should not be running the kernel at 1000Hz...). Setting {{bootparm|processor.bm_history|0xFFFFFFFF}} will cause C3 to be entered less often. This will waste more power as the CPU won't do C3 or C4 as often, but at least it doesn't forbid C3 and C4 permanently, unlike {{bootparm|max_cstate|2}}.

See the [http://thinkwiki.org/wiki?title=Talk:Problem_with_high_pitch_noises discussion page] for further information and success reports.

*Jakob Schou Pedersen: Editing the file {{path|/etc/init.d/acpid}} as described above (the last solution) worked on my T43 :-)

===MS Windows: Disable CPU popup mode ===

This is a generic solution for Core 2 Duo platforms --- using the RMClock utility you can disable C4 to C1/C2/C3 transition and force the CPU to go straight to C0. To do this, in RMClock settings go to: "Enable Advanced CPU settings > Chipset" and disable at least "Enable Popup Mode". Related discussion can be found here: [[http://forum.thinkpads.com/viewtopic.php?f=30&t=75283]].

===Turn off CPU power saving in the BIOS===

Go into the BIOS and turn off the power saving processor feature that puts it into idle mode. This should be somewhere under Config/Power - look for "CPU Power Management", the default being automatic. Set "CPU Power Management" to "Disabled" (This worked on a ThinkPad {{T21}}, {{T43}}, {{T60}}, {{X60s}}, {{X200s}} and {{Z61m}}). However, this also affects power consumption when the CPU is idle, it's similar to disabling the C4/C3 ACPI CPU power state. For example, on a Z61m 9450-3HG, a full charged battery with power management enabled in the BIOS provides the notebook with power for about 3.5h, if disabled, the battery-lifetime is only about 2h.

===Disable ACPI CPU power states===

Completely disable CPU ACPI power states. Discussion:

*From Martin Steigerwald: I made the observation that I get at least less high pitch noises on my {{T23}} when I do not use the two ACPI modules "processor" and "thermal" (depends on the first one). I have no clue, why. Anyone with similar experiences?
:Omar Yasin: I've got a {{R52}} and when I load the same ACPIO modules the high pitch noises are not as loud but I can still hear them.
*Kaspar Schleiser: On my {{T23}} the noise is less loud when setting max_cstate to 2, but to completely silence it, I have to set it to "1". Is that the same as removing the "processor"-module? "cat /proc/acpi/battery/BAT0/state" does not show increased power drain.
*Niko Ehrenfeuchter: I'm experiencing the same here on my {{X24}}. Removing the "processor" module also stops the pitch noise, which does ONLY occur when setting the CPU to maximum speed (using cpufreq). On low speed it's completely silent, even having loaded the processor module.

*Rolf Adelsberger: I can confirm this: the high pitch noise is only remarkable (at least with my ears ;-) ) if the processor speed is set to maximum frequency.

*Stefan Baums: My {{X41}} produced a high-pitched crackle from the processor vent on the left. Changing HZ did nothing, and the 'processor' module could not easily be removed from the system (Ubuntu 5.04). What solved the problem for me was adding {{bootparm|idle|halt}} to the boot command line. Unfortunately, this solution only lasts until the first hibernation or suspend - when the computer ({{X41}}) resumes, the high-pitched crackle is back.

* The {{bootparm|idle|halt}} solution combined with setting <code>#define HZ 100</code> in the kernel fixes the problem on a {{T43}}.

* jhatch: {{bootparm|idle|halt}} plus <code>#define HZ 100</code> also worked on my {{T43}}. It still reverts back to noisy after a suspend/resume though. This needs to be fixed...

===Use both C-States (sleep modes) and P-States (frequency scaling)===
*Max Gaukler: I had the problem with a "beeping" noise of my {{R60}} on battery. When using powertop I recognised that it went into C3 (deep sleep mode), but it was always running at the highest possible frequency. I followed the instructions in [[How_to_make_use_of_Dynamic_Frequency_Scaling|How to make use of Dynamic Frequency Scaling]] and the noise disappeared except for a short time during boot until frequency scaling has been loaded.

===Change the timer interrupt frequency===

Change the "HZ" kernel constants to alter the frequency of timer interrupts. Discussion:

{{NOTE|The timer interrupt frequency (HZ) in current kernels is directly tied to Linux's task scheduler. Lower frequencies provide larger time-slices and thus also higher latencies (which may kill latency-sensitive applications like audio processing). 100Hz ended up as the recommended "server" setting (because it increases disk/CPU throughput in a latency-insensitive environment). Higher frequencies are better for latency-sensitive applications, and improve desktop responsivity at the cost of less processor throughput. 1000Hz ended up as the recommended "desktop" setting.}}

*Andreas Karnahl: i've read in several forums it has something to do with the "idle"-state (or "C3") of the processor. There is a frequency called "timer interrupt" (or something like that). Since kernel 2.6x it is set to 1000 Hz by default (compared to 100 Hz in Kernel 2.4x). The exact reason i don't know, but it is safe to change this frequency to 100 Hz in kernel 2.6x (by the way, windows up to XP uses 100 Hz by default).<br />Just do the following:<br />
: In {{path|[path to kernel-sources]/include/asm-i386/param.h}} find the line
:: <code>#define HZ 1000</code>
: and change the value of HZ to 100:
:: <code>#define HZ 100</code>
:Then recompile the kernel.<br />After i changed it on my ThinkPad {{A30}} (under SuSE 9.2 and 9.3) and recompiling the kernel the high pitch noise is gone away.

* Omar Yasin: Worked on my {{R52}}, thanks.

* [[User:Thinker|Thinker]]: In modern kernels this constant is in the kernel configuration {{kernelconf|CONFIG_HZ|Processor type and features||Timer Frequency|||||}}.

* [[User:sklnd|sklnd]]: As of 2.6.21, enabling a tickless kernel (CONFIG_NO_HZ) seems to fix the sound issue on the X60. This also has the added benefit of causing the kernel to wake up less, which will improve battery life.

===Prevent idling===

Indirectly avoid power saving states by making sure the CPU is rarely idle:

* Paul RIVIER: Here is a really simple workaround. C3 / C4 states are mainly called when the cpu freq is higher than required, for example if your cpufreqd is lazy to slow down the frequency but quick to raise it. That is why I use powernowd with the builtin "passive" mode, which is lazy for raising frequency, but quick to go back to the lowest. Now I don't hear them as often as before, as I avoid C3/C4 states at high frequency.

* The problem also occurs on my {{X41}} with 2.6.11. Setting up [[How to make use of Dynamic Frequency Scaling|frequency scaling]] with the <code>ondemand</code> governor makes things a lot better, as the processor does not stay with the maximum frequency when in idle mode. It can be still heard sometimes, though.

* On a {{T43}} the noise was gone after dropping cpufreqd and switching to the ondemand governor - maybe because of the high sampling rate? (used the default: 10ms)

===Change the processor voltage===

Reducing the processor voltage (when possible) may decrease or eliminate the noise. On one ThinkPad {{T43}}, [[Pentium M undervolting and underclocking|undervolting the Pentium M processor]] eliminated the high-pitched noise. Compared to the other solutions this has the benefit of lower power consumption, both due to the undervolting itself and because there is no need to forbid high APCI CPU power saving modes.

===Kernel BIOS options===

Adding acpi_sleep=s3_bios and pci=bios as boot parameters significantly reduced the pitch noise on a T61. Seems to be the best solution so far, without losing battery capacity. If ondemand governor is enabled as well, the noise is almost gone.--[[User:Mozz|Mozz]] 13:14, 18 January 2008 (CET)

===Kernel Update===

The recent kernel update in Ubuntu 8.04 from 2.6.24-19 to 2.6.24-21 made the noise disappear on my T61. With the old kernel the sound was very audible when running on battery power, although setting the kernel BIOS options as specified in the paragraph above made it somewhat bearable. Now I can barely hear anything with the default startup options, even with my ear close to the laptop.

==Solutions for screen brightness related sounds==

===Disable BIOS brightness control===

The sound starts when on batteries as the BIOS automatically reduces screen brightness. To disable this, simply switch Config>Display>Brightness from
Normal to High. See also [[User:Piccobello/Hissing sound on battery|here]].

==Other solutions==

===Disable UltraBay===
*Naheed Vora: My {{T41}} (2373-268) started to give high pitch noise ocassionally, when I upgraded to 2.6.11 kernel. I tried to unload lot of modules but finally figured out that disabling bay stops the noise. If you have [[ibm-acpi]], do (need a cleaner solution): {{cmduser|echo eject >/proc/acpi/ibm/bay}} .

===Disable IrDA===
*Mike Perry: I was able to cure an intermittent high-pitched whine on both my {{X24}} and {{X40}} by disabling the Infrared port.

===Disable the Linuxant Modem Driver===
*Joern Heissler: I made another experience. I played around with linuxant conexant [[Modem Devices|modem]] drivers. After loading them I got some noise on my {{T42p}}.

===Media Player paused===
*Eilif Muller: On my {{R52}} the high-pitched noises go away if I load XMMS, play something then pause it.
*Jacob: On my {{T43}} DGU it goes away if I open mplayerc.exe and press play then pause it. This is the high-pitched noise that only shows up when I'm on battery.
*butcom: On my {{X60 Tablet}}, this tip works in Windows as well with Media Player Classic or Windows Media Player. Just open either program, start playing any music file and pause it and the screeching noise stops.

''I'd guess that the above tip works as when xmms or similar is running, it is uncompressing compressed audio/video, which is a processor intensive action. Keeping this paused means that the app won't 'let go' of the processor, forcing it to stay up and running, which stops it entering the higher powersave modes.''

===nice yes===

Run the command:
{{cmduser|nice yes > /dev/null}}.

This is a good way to test whether the processor is causing the interference, since it forces the CPU to stay at full power. Of course, this will make your system get warm, and probably turn on the fan, as well as eating power.

===Upgrade BIOS===
On a ThinkPad {{X60s}}, [[BIOS_Upgrade|upgrading the BIOS]] to version 1.06 eliminated the high pitch noise when running on battery.

On a ThinkPad {{X61}}, [[BIOS_Upgrade|upgrading the BIOS]] to version 2.21 reduces the noise. It's not completely eliminated though.

On a ThinkPad {{R60}}, [[BIOS_Upgrade|upgrading the BIOS]] to version 2.19 eliminated the voice also.

===Disable USB===
Disabling USB (partially) using {{cmdroot|rmmod uhci_hcd}} significantly reduced the noise in some cases.
Reported on {{T43}}, {{T61}}, {{X60}}, {{X200s}}
On a {{T60}} this trick worked well and doing ''rmmod/modprobe'' twice wiped the noise permanently.

This is likely a CPU-induced noise case, as disabling USB UHCI will reduce a lot the amount of busmaster activity while the computer is idle, and thus has a direct effect on the need for ACPI C-state transitions from C3/C4 to C2 or lower states.

*syscrash: Plugging in my USB mouse has completely solved the problem for me.
*lorien: Plugging USB mouse helped me too {{T61}}
*telofy: Disabling USB "solved" the problem; so does disabling the CPU idle setting in the BIOS on my X200s.

===Suspend USB===
*Stefan Ott: On my X41, the noise seems to have stopped since I enabled "USB selective suspend/resume and wakeup" (CONFIG_USB_SUSPEND).
*babrodtk: This approach worked with an R60 as well.

===Turn off fan===
On a ThinkPad {{T60p}}, changing the fan speed or turning off the fan using TP Fan Control eliminated the high pitch noise.

Code/thinkpad-smapi.sh

2025-04-11T07:53:44Z

ThinkGNU: Put script in pre block.

<pre>
#!/bin/bash
# Copyright (C) 2007 William Poetra Yoga Hadisoeseno <williampoetra@gmail.com>
# This file is licensed under the GPL v2. E-mail me if you have any ideas of
# other licenses to use (BSD, GPL v3, Public Domain, etc.), I'm open :)

# IDEAS
# - make an ncurses interface, and also maybe gtk+ and qt
# - add option to enable modifying the charge control variables

TP_SMAPI_BASE=/sys/devices/platform/smapi

# function to simplify reading from files
# syntax: read_file <variable> <filename> <check_return_value 0/1> <translate 0/1> [[value] [translation_string]]
read_file()
{
local VARIABLE
local FILENAME
local CHECK_RETURN
local TRANSLATE
local VAL
local RET

VARIABLE="$1"; shift
FILENAME="$1"; shift
CHECK_RETURN="$1"; shift
TRANSLATE="$1"; shift

VAL=`cat "$FILENAME" 2> /dev/null`
RET=$?

if [[ "$CHECK_RETURN" == "1" ]] && [[ $RET -gt 0 ]]
then
RESULT="[unavailable]"
elif [ "$TRANSLATE" == "1" ]
then
RESULT="unknown ($RET)"
while [ -n "$1" ]
do
if [ "$VAL" == "$1" ]
then
RESULT="$2"
break
fi
shift 2
done
else
RESULT="$VAL"
fi

eval "$VARIABLE="'"'"$RESULT"'"'
# eval "$VARIABLE=$RESULT"
}

give_units()
{
local VARIABLE
local UNIT
local VALUE
local RESULT

VARIABLE="$1"
UNIT="$2"
eval "VALUE=\$$VARIABLE"

if (echo "$VALUE" | grep -qs "^-\?[0-9]")
then
RESULT="$VALUE $UNIT"
else
RESULT="$VALUE"
fi

eval "$VARIABLE="'"'"$RESULT"'"'
}

replace_val()
{
local VARIABLE
local OLD_VALUE
local NEW_VALUE
local VALUE
local RESULT

VARIABLE="$1"
OLD_VALUE="$2"
NEW_VALUE="$3"

eval "VALUE=\$$VARIABLE"

if [ "$VALUE" == "$OLD_VALUE" ]
then
RESULT="$NEW_VALUE"
else
RESULT="$VALUE"
fi

eval "$VARIABLE="'"'"$RESULT"'"'
}

show_help()
{
cat << EOF

thinkpad-smapi.sh - Show SMAPI information on ThinkPad laptops, through
the exported SMAPI information by the tp_smapi module.

-a Show all available information
-b [n] Show all available information for battery [n]
-h Show this help text
-m Show miscellaneous information

EOF
}

show_misc()
{
cd $TP_SMAPI_BASE

read_file PCI_POWER_SAVINGS "enable_pci_power_saving_on_boot" 1 1 1 "enabled" 0 "disabled"
read_file AC_ADAPTER "ac_connected" 1 1 1 "connected" 0 "disconnected"

cat << EOF
MISCELLANEOUS INFORMATION
=========================

PCI power savings on boot: $PCI_POWER_SAVINGS
AC adapter status: $AC_ADAPTER

EOF
}

show_batt()
{
SLOT=$1
cd $TP_SMAPI_BASE/BAT$SLOT

TMP=`cat installed`
if [ $TMP -eq 1 ]
then
BATT_INSTALLED="yes"
else
BATT_INSTALLED="no"
fi

BATT_STATE=`cat state`

if [ $BATT_INSTALLED == "yes" ]
then

read_file BARCODING "barcoding" 1 0
read_file BATT_CHEMISTRY "chemistry" 1 0
read_file DESIGN_CAPACITY "design_capacity" 1 0
read_file DESIGN_VOLTAGE "design_voltage" 1 0
read_file MANUFACTURE_DATE "manufacture_date" 1 0
read_file BATT_FRU "model" 1 0
read_file MANUFACTURER "manufacturer" 1 0
read_file BATT_SERIAL "serial" 1 0

read_file FIRST_USE_DATE "first_use_date" 1 0
read_file CYCLE_COUNT "cycle_count" 1 0
read_file LAST_FULL_CAPACITY "last_full_capacity" 1 0
read_file CURRENT_1MIN "current_avg" 1 0
read_file POWER_1MIN "power_avg" 1 0

read_file CAPACITY_MWH "remaining_capacity" 1 0
read_file CAPACITY_PERCENT "remaining_percent" 1 0
read_file REMAINING_RUNNING_TIME "remaining_running_time" 1 0
read_file CURRENT_NOW "current_now" 1 0
read_file POWER_NOW "power_now" 1 0
read_file BATT_TEMPERATURE "temperature" 1 0
read_file BATT_VOLTAGE "voltage" 1 0
read_file REMAINING_CHARGING_TIME "remaining_charging_time" 1 0

# fixups
give_units DESIGN_CAPACITY "mWh"
give_units DESIGN_VOLTAGE "mV"
give_units CURRENT_NOW "mA"
give_units POWER_NOW "mW"
give_units CURRENT_1MIN "mA"
give_units POWER_1MIN "mW"
give_units LAST_FULL_CAPACITY "mWh"
give_units REMAINING_RUNNING_TIME "min"
give_units REMAINING_CHARGING_TIME "min"
give_units CAPACITY_PERCENT "%"
give_units BATT_TEMPERATURE "mC"
give_units BATT_VOLTAGE "mV"

# some more
replace_val REMAINING_RUNNING_TIME "not_discharging" "[not discharging]"
replace_val REMAINING_CHARGING_TIME "not_charging" "[not charging]"

else

BATT_FRU=
MANUFACTURER=
BATT_SERIAL=
BARCODING=
BATT_CHEMISTRY=
DESIGN_CAPACITY=
DESIGN_VOLTAGE=
MANUFACTURE_DATE=

FIRST_USE_DATE=
CYCLE_COUNT=
LAST_FULL_CAPACITY=
CURRENT_1MIN=
POWER_1MIN=

CAPACITY_MWH=
CAPACITY_PERCENT=
REMAINING_RUNNING_TIME=
CURRENT_NOW=
POWER_NOW=
BATT_TEMPERATURE=
BATT_VOLTAGE=
REMAINING_CHARGING_TIME=

fi

read_file START_CHARGE_THRESH "start_charge_thresh" 1 0
read_file STOP_CHARGE_THRESH "stop_charge_thresh" 1 0
read_file INHIBIT_CHARGE_MIN "inhibit_charge_minutes" 1 0
read_file BATT_FORCE_DISCHARGE "force_discharge" 1 1 1 "yes" 0 "no"

# installed*, state*, dump
# barcoding, chemistry, design_capacity, design_voltage, manufacture_date, model, manufacturer, serial
# first_use_date, cycle_count, last_full_capacity, current_avg, power_avg
# remaining_capacity, remaining_percent, remaining_running_time, current_now, power_now, temperature, voltage, remaining_charging_time
# start_charge_thresh*, stop_charge_thresh*, inhibit_charge_minutes*, force_discharge*

cat << EOF
BATTERY $SLOT INFORMATION
=====================

Battery slot:
Battery present: $BATT_INSTALLED
Battery state: $BATT_STATE

EOF

if [ "$BATT_INSTALLED" == "yes" ]
then
cat << EOF
Embedded info:
FRU P/N: $BATT_FRU
Barcoding: $BARCODING
Serial number: $BATT_SERIAL
OEM Manufacturer: $MANUFACTURER
Chemistry: $BATT_CHEMISTRY
Manufacture date: $MANUFACTURE_DATE
Design capacity & voltage: $DESIGN_CAPACITY, $DESIGN_VOLTAGE

Battery health:
First use date: $FIRST_USE_DATE
Cycle count: $CYCLE_COUNT
Last full capacity: $LAST_FULL_CAPACITY
Average current / power (past 1 minute): $CURRENT_1MIN, $POWER_1MIN

Battery status:
Remaining capacity: $CAPACITY_MWH mWh ($CAPACITY_PERCENT)
Remaining running time: $REMAINING_RUNNING_TIME
Running current & power: $CURRENT_NOW, $POWER_NOW
Temperature: $BATT_TEMPERATURE
Voltage: $BATT_VOLTAGE
Remaining charging time: $REMAINING_CHARGING_TIME

EOF
fi

cat << EOF
Battery charging control:
Start charging at: $START_CHARGE_THRESH %
Stop charging at: $STOP_CHARGE_THRESH %
Prevent charging for: $INHIBIT_CHARGE_MIN min
Force battery discharge: $BATT_FORCE_DISCHARGE

EOF
}

SHOW_ALL=
SHOW_BATT=
SHOW_MISC=
GOT_OPTS=

while getopts ab:hm OPT
do
GOT_OPTS=y
case ${OPT} in
a) SHOW_ALL=y;;
b) if [ ${OPTARG} -eq 0 -o ${OPTARG} -eq 1 ]
then
SHOW_BATT=${OPTARG}
else
SHOW_BATT=y
fi
;;
h) show_help
exit 0
;;
m) SHOW_MISC=y;;
\?) show_help
exit 1
;;
esac
done

if [ "$GOT_OPTS" != y ]
then
show_help
exit 1
fi

if [ "$SHOW_ALL" == y ]
then
show_misc
show_batt 0
show_batt 1
else
if [ -n "$SHOW_MISC" ]
then
show_misc
fi
if [ -n "$SHOW_BATT" ]
then
show_batt $SHOW_BATT
fi
fi
</pre>

Serial Ultrabay Slim DVD-ROM Drive

2025-04-11T07:49:38Z

ThinkGNU: The kernel, Linux doesn't play DVDs. If it can be changed via software means, it's not firmware.

__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;">
=== Serial Ultrabay Slim DVD-ROM Drive (43N3212) ===
This is an optical drive that slides into a Serial Ultrabay Slim.
=== Features ===
* Read/Write capabilities:
** CD-ROM, CD-R, CD-RW (24x read speed)
** DVD-ROM, DVD±R, DVD±R DL, DVD±RW, DVD±RW DL (8x read speed)
* Tray loading
* Activity LED
{{footnotes|
#This model requires its original optical drive's faceplate and mounting bracket to be swapped onto the Serial Ultrabay Slim DVD-ROM Drive, otherwise the drive will not fit in properly. It also requires the black plastic stub located at the back of the DVD-ROM drive to be removed to fit in as well, due to the lack of an eject mechanism (and the fact that it may prevent the drive's installation).
}}
</div>
|style="vertical-align:top" |
[[image:UltraBay Slim Optical Drive.gif|192px]]
|}
=== Part numbers ===
==== Sony DDU7940H ====
* 45N7521 (45N7582)
==== Sony DDU7930H ====
* 45N7521 (45N7520)
==== LG DU20N ====
* 45N7485 (45N7484)
==== LG DU10N ====
* 42T2541 (42T2540)
==== Panasonic UJ8C2 ====
* 45N7619 (45N7618)

=== Linux support ===
If connected at boot time, the drive is normally {{path|/dev/sr0}}.

==== Problem regarding reading video DVDs ====
When playing a region-coded video DVD for the first time using a GNU/Linux player, you may get errors such as the following:
libdvdread: Invalid IFO for VMGM (VIDEO_TS.IFO)
This is caused by the DVD driver's region never having been set. Use <tt>regionset</tt> to set some region and retry. It is important that you choose the region code wisely, as you will '''not''' be able to read any other regions, and you can only change the region 4 times before it becomes permanent.

With older drives you could use libdvdread to bypass a drives region restrictions, but this doesn't work in some drives, particularly those from Panasonic. Panasonic DVD drives actually refuse to read out-of-region media, and implement RPC-2 fully. This cannot be worked around in any way short of patches to the drive's internal software, which '''are not''' available anywhere.

== Models supporting this accessory ==
* {{P70}}{{footnote|1}}, {{P71}}{{footnote|1}}
* {{W500}}, {{W510}}, {{W520}}, {{W530}}, {{W540}}{{footnote|1}}, {{W541}}{{footnote|1}}, {{W700}}, {{W700ds}}, {{W701}}, {{W701ds}}
* {{T400}}, {{T400s}}, {{T410}}, {{T410i}}, {{T410s}}, {{T410si}}, {{T420}}, {{T420i}}, {{T420s}}, {{T420si}}, {{T430}}, {{T430i}}, {{T430s}}, {{T430si}}, {{T440p}}{{footnote|1}}, {{T500}}, {{T510}}, {{T510i}}, {{T520}}, {{T520i}}, {{T530}}, {{T530i}}, {{T540p}}{{footnote|1}}
* {{L410}}{{footnote|1}}, {{L412}}{{footnote|1}}, {{L420}}{{footnote|1}}, {{L421}}{{footnote|1}}, {{L430}}{{footnote|1}}, {{L440}}{{footnote|1}}, {{L510}}{{footnote|1}}, {{L512}}{{footnote|1}}, {{L520}}{{footnote|1}}, {{L530}}{{footnote|1}}, {{L540}}{{footnote|1}}, {{L560}}{{footnote|1}}, {{L570}}{{footnote|1}}
* {{R400}}, {{R500}}
* {{ThinkPad X200 UltraBase}}, {{ThinkPad UltraBase Series 3}}

[[Category:Ultrabay Devices]]

S3 Savage IX8

2025-04-11T07:45:59Z

ThinkGNU: I inspected the binary with readelf and it's a GNU/Linux and X.org binary.

__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;">
=== S3 Savage IX8 or IX8+===
This is a S3 video adapter<br>
S3 is now owned by Via Technologies

The IX8 and IX8+ chips share the same PCI-ID

=== Features ===
* Chipset: S3
* PCI ID: 5333:8c12
* AGP 2X
* 8MB SGRAM video memory

=== Driver Download ===

A proprietary GNU/Linux binary and X.org Driver is available from an archive of the s3graphics websites: [https://web.archive.org/web/20130103055651if_/http://www.s3graphics.com:80/en/drivers/legacy_software_archive.aspx Savage Family GNU/Linux XFree86 4.0.3 X Server Binary and Switch Utility version 1.1.18]

</div>
|style="vertical-align:top" |
|}

=== X.Org driver ===
This chip is supported by the '[[savage]]' driver as part of the X.Org distribution.

==== ThinkPad LCD ====
Display on the internal LCD works as long as you set the monitor settings correctly. The driver does not appear
to support [[DPMS]] on the internal LCD, so it is necessary to make sure that horizontal sync and vertical refresh settings are included in the "Monitor" section of xorg.conf.

HorizSync 31.5 - 48.5
VertRefresh 50-70

==== External VGA port ====
Works. {{key|Fn}}-{{Key|F7}} switches between LCD and CRT. To use both, use [http://www.probo.com/timr/savage40.html s3switch] (on some models you need to run "'''s3switch lcd crt tv'''" even if you want only CRT and LCD, otherwise the CRT display is corrupted). You can also use [[thinkpad-acpi]] to control video output by echoing commands to {{path|/proc/acpi/ibm/video}}.

==== SVideo port ====
Works. Use [http://www.probo.com/timr/savage40.html s3switch] to change display output in software.

=== Linux fbcon Framebuffer driver ===
This chip will work with either the 'vesa' or 'savagefb' driver as part of any recent 2.4 or 2.6 kernel.

==== Dual Monitor Tip ====
The chip supports using an external monitor plus the LCD as one big monitor. This can lead to a problem
if X is configured for this, but the external monitor has been detached. This creates a ghost monitor that you
cannot see, but can move the mouse onto and applications can open windows on.

Sometimes in this situation it's necessary to grab a window from the ghost monitor and drag it into view.
This can be done by moving the mouse onto the ghost screen and then holding down the ALT key, which allows you
to click-and-drag a window back into view. To see what is on the ghost monitor, a screen capture utility like
Ksnapshot can help you. When it takes a screenshot of the entire screen, it will show the contents of the ghost
screen, even though you can't see it directly.

=== Quirks ===
==== Power Management and savagefb ====
The savagefb appears to interfere with acpi sleep. (tested on 2.6 kernels up to 2.6.12) There are also some display problems with savagefb including limiting boot text to a 800x600 window centered in a 1024x768 display and problems with libdirectfb. For those reasons, vesafb is recommended as the framebuffer driver.<br />
The 800x600 boot-text problem can be resolved by altering the savagefb.c (pre-2.6.20) or savagefb_driver.c (2.6.20 and later) and then recompiling the Kernel or the respective module. To do that, open the savagefb_driver.c, for example under ''<Kernel Root>/drivers/video/savage'' in the 2.6.20 release. Now, locate the following function:
<pre>static struct fb_var_screeninfo __devinitdata savagefb_var800x600x8 = {
.accel_flags = FB_ACCELF_TEXT,
.xres = 800,
.yres = 600,
.xres_virtual = 800,
.yres_virtual = 600,
.bits_per_pixel = 8,
.pixclock = 25000,
.left_margin = 88,
.right_margin = 40,
.upper_margin = 23,
.lower_margin = 1,
.hsync_len = 128,
.vsync_len = 4,
.sync = FB_SYNC_HOR_HIGH_ACT | FB_SYNC_VERT_HIGH_ACT,
.vmode = FB_VMODE_NONINTERLACED
};</pre>

Alter the lines ''.xres'', ''.yres'', ''.xres_virtual'' and ''.yres_virtual'' to reflect your chosen resolution. Recompile and reinstall the Kernel, reboot or reload the module and the savagefb should use the new resolution.

==== Video-related System Lockups ====
Some quirks in the interactions between the OS and the Savage hardware can cause system lockups, especially due to high video load and 3D rendering operations. For a more complete description of this problem and the workarounds, see the [[Problem with video related system lockup]] page.

==== The Black 'X' (old X pointer) Problem ====
On some systems a black 'X' (which is actually the old default XFree86 pointer) appears frozen in the middle of the screen inside of X Windows. This problem can be remedied by setting

Option "SWCursor" "on"

in xorg.conf. Also see the [[Problem with black X]] page for more information.

==== 3D Acceleration Quirks ====
If 3D acceleration is not working on your system (after installing the DRM savage module), or 3D programs are exhibiting strange behavior, one of the following changes may fix the problem. First, most Savage chips do not have enough video memory to support 3D textures and acceleration with a frame buffer depth of 24 bits. Therefore, you may need to change "DefaultDepth 24" to "DefaultDepth 16" in the "Screen" section of xorg.conf (and of course provide the appropriate subsection for 16 bit depth if it is not present). Also, adding one of both of the following configuration options to the "Device" section of your xorg.conf may solve the video quirks (also explained in the [[Problem with video related system lockup|video related system lockup]] page)

Option "BusType" "PCI"
Option "DmaMode" "None"

On Debian based systems you need the package '''libgl1-mesa-dri''' to enable 3d acceleration. Deborphan may decide it is just a futile library, but that is false.

==== Blank screen ====

Symptoms:

* X starts but nothing shows up on screen, hard drive led shows normal activity up to login
* /etc/init.d/xorg.conf does not exist, so X.org is using autoconfiguration which fails
* /var/log/Xorg.0.log does not show any relevant errors or warnings

This happened on a T20 running Debian Etch and Lenny.

Workaround is to add DmaType and BusType as "PCI" in /etc/X11/xorg.conf:

Section "Device"
Identifier "S3 Inc. 86C270-294 Savage/IX-MV"
Driver "savage"
BusID "PCI:1:0:0"
Option "DmaType" "PCI"
Option "BusType" "PCI"
EndSection

=== ThinkPads this chip may be found in ===
* {{A22e}}
* {{T20}}, {{T21}}, {{T22}}

[[Category:Video Controllers]]

ATI Mobility FireGL V3200

2025-04-11T07:37:32Z

ThinkGNU: X.Org is not Linux. Linux's terminal emulator is called fbcon.

__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;">

This is a ATI video adapter

== Features ==
* Chipset: ATI RV380 (M24) - Similar to [[ATI Mobility Radeon X600]]
* PCI ID: 1002:3154
* PCI Express x16
* 128MB GDDR1 video memory
</div>
|style="vertical-align:top" |
|}

== X.Org driver ==
Works fine with xorg 7.0.0

=== ThinkPad LCD ===
Display on the internal LCD works as long as you set the monitor settings correct.

=== External VGA port ===

==== SuSE ====

Works fine using ATI [[fglrx]] driver version 8.19.10 configured with fglrxconfig into clone mode (display shows full resolution, external CRT shows full resolution with higher refresh rate).
This was tested using SuSE 9.2 with a Thinkpad T43p.

==== Ubuntu Gutsy ====
Works fine using Catalyst 7.12.
If you get corrupted output in OpenGL, set Anti-Aliasing in the Catalyst Control Center and it works fine magically.

==== Ubuntu Dapper ====

On an ''Ubuntu Dapper'' (xorg 7.0.0) external vga/ monitor/ beamer works fine with the following in {{path|/etc/xorg.conf}}. I used the free ati driver shipped with Dapper.

<pre>

# insert after section 'Screen' with identifier 'Default Screen'

##################################################################################
# MergedFB2 from http://mg.pov.lt/xorg.conf
##################################################################################

Section "Device"
Identifier "MergedFB ATI"
Driver "ati"
BusID "PCI:1:0:0"
Option "DynamicClocks" "on"
Option "MergedFB" "true"
Option "CRT2Position" "RightOf"
# This allows X to use MergedFB if the external monitor is not connected
# when I start X. The ranges are taken from DDC values of the CTX monitor
# I use at the office; as listed in Xorg.log.
Option "CRT2HSync" "30-81"
Option "CRT2VRefresh" "56-76"
# The next line lets me switch between dual-head and several clone modes
# of varying resolutions with xrandr.
# modified by jensens
Option "MetaModes" "1400x1050-1280x1024 1400x1050-1024x768 1400x1050 1280x1024 1024x768 800x600 640x480"
# A newer version of the radeon driver has an option that disables vertical
# scrolling for the 1024x768 part.
Option "MergedNonRectangular" "true"
# In 1024x768-1280x1024 mode the DPI is correct (100), but in all other
# modes it is weird. Try to override
Option "MergedDPI" "100 100"
EndSection

Section "Screen"
Identifier "MergedFB Screen"
Device "MergedFB ATI"
Monitor "Generic Monitor"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1400x1050" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection
##################################################################################

# replace ServerLayout with this lines:

Section "ServerLayout"
Identifier "Default Layout"
#Screen "Default Screen"
Screen "MergedFB Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
InputDevice "stylus" "SendCoreEvents"
InputDevice "cursor" "SendCoreEvents"
InputDevice "eraser" "SendCoreEvents"
InputDevice "Synaptics Touchpad"
EndSection
</pre>

{{NOTE|The built-in switching of resolutions does not work with this setting! Use the Gnome applet '''Grandr''' - it works fine.}}

{{HINT|To switch off external VGA port and save some battery you can use the command '''sudo radeontool dac off'''.}}

=== SVideo port ===
??

=== DVI port ===
??

== Proprietary ATI driver ==
The [[fglrx]] driver adds 3D acceleration.

== Linux fbcon Framebuffer driver ==
??

== ThinkPads this chip may be found in ==
* {{T43p}}

[[Category:Video Controllers]]

Hard drive firmware update

2025-04-11T07:36:35Z

ThinkGNU: Lenovo calls them "firmware", so the user figures it's something else than software, but in fact it's just proprietary software.

Lenovo provides ''Hard drive firmware update utilities'' in the form of bootable iso-images. There are at least two such different iso-images, each of them contains software updates for quite a few different Lenovo laptops. They are different by the method they use to boot. One uses [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-63685 harddrive emulation bootimage], and the other uses [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-62282 floppy emulation bootimage].

If you have an optical drive, just burn the iso-image and update the firmare. In case if you don't have an optical disk to boot it from, see [[BIOS update without optical disk]] for harddisk emulation bootimage, and [[BIOS Upgrade/X_Series]] for floppy emulation bootimage.
==Models with harddisk emulation bootimage==
{{R60}}, {{R60e}}, {{R61}}, {{R61i}}, {{R400}}, {{R500}}, {{SL300}}, {{SL400}}, {{SL500}}, {{T60}}, {{T60p}}, {{T61}}, {{T61p}}, {{T400}}, {{T500}}, {{W500}}, {{W700}}, {{X60}}, {{X60s}}, {{X60 Tablet}}, {{X61}}, {{X61s}}, {{X61 Tablet}}, {{X200}}, {{Z60m}}, {{Z60t}}, {{Z61e}}, {{Z61m}}, {{Z61p}}, {{Z61t}}
==Models with floppy emulation bootimage==
{{A20m}}, {{A20p}}, {{A21e}}, {{A21m}}, {{A21p}}, {{A22e}}, {{A22m}}, {{A22p}}, {{i1800}},
{{A30}}, {{A30p}}, {{A31}}, {{A31p}},
{{G40}}, {{G41}},
{{R40}}, {{R40e}},
{{R50}}, {{R50p}}, {{R51}}, {{R52}},
{{T20}}, {{T21}}, {{T22}}, {{T23}},
{{T30}},
{{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}},
{{X20}}, {{X21}}, {{X22}}, {{X23}},
{{X30}}, {{X31}}, {{X32}},
{{X40}}, {{X41}}, {{X41 Tablet}}

Code/ibm-acpi-0.12a-2.6.17-fan.patch

2025-04-11T07:30:07Z

ThinkGNU: Put patch in <pre> block

<pre>
--- drivers/acpi/ibm_acpi.c.orig 2006-08-22 19:04:43.000000000 +0900
+++ drivers/acpi/ibm_acpi.c 2006-08-22 19:10:28.000000000 +0900
@@ -1466,6 +1466,7 @@
{
int len = 0;
int s;
+ char status_read = 0;
u8 lo, hi, status;

if (gfan_handle) {
@@ -1479,8 +1480,11 @@
if (!acpi_ec_read(fan_status_offset, &status))
len += sprintf(p + len, "status:\t\tunreadable\n");
else
+ {
len += sprintf(p + len, "status:\t\t%s\n",
- enabled(status, 7));
+ status ? "enabled" : "disabled" );
+ status_read = 1;
+ }

if (!acpi_ec_read(fan_rpm_offset, &lo) ||
!acpi_ec_read(fan_rpm_offset + 1, &hi))
@@ -1488,6 +1492,16 @@
else
len += sprintf(p + len, "speed:\t\t%d\n",
(hi << 8) + lo);
+
+ if (status_read) {
+ if (status & 0x40)
+ len += sprintf(p + len, "level:\t\tdisengaged\n");
+ else if (status & 0x80)
+ len += sprintf(p + len, "level:\t\tauto\n");
+ else
+ len += sprintf(p + len, "level:\t\t%d\n", status);
+ }
+
}

if (sfan_handle)
@@ -1496,7 +1510,10 @@
" (<level> is 0-7)\n");
if (!gfan_handle)
/* all except 570, 600e/x, 770e, 770x */
- len += sprintf(p + len, "commands:\tenable, disable\n");
+ len += sprintf(p + len,
+ "commands:\tenable, disable, level <level>\n"
+ " \t(<level> is 0-7, auto "
+ "or disengaged)\n");
if (fans_handle)
/* X31, X40 */
len += sprintf(p + len, "commands:\tspeed <speed>"
@@ -1517,7 +1534,8 @@
/* 570, 770x-JL */
if (!acpi_evalf(sfan_handle, NULL, NULL, "vd", level))
return -EIO;
- } else if (!gfan_handle && strlencmp(cmd, "enable") == 0) {
+ } else if (!gfan_handle && ( (strlencmp(cmd, "enable") == 0) ||
+ (strlencmp(cmd, "level auto") == 0) ) ) {
/* all except 570, 600e/x, 770e, 770x */
if (!acpi_ec_write(fan_status_offset, 0x80))
return -EIO;
@@ -1525,6 +1543,17 @@
/* all except 570, 600e/x, 770e, 770x */
if (!acpi_ec_write(fan_status_offset, 0x00))
return -EIO;
+ } else if (!gfan_handle &&
+ strlencmp(cmd, "level disengaged") == 0) {
+ /* all except 570, 600e/x, 770e, 770x */
+ if (!acpi_ec_write(fan_status_offset, 0x40))
+ return -EIO;
+ } else if (!gfan_handle &&
+ sscanf(cmd, "level %d", &level) == 1 &&
+ level >=0 && level <= 7) {
+ /* all except 570, 600e/x, 770e, 770x */
+ if (!acpi_ec_write(fan_status_offset, level))
+ return -EIO;
} else if (fans_handle &&
sscanf(cmd, "speed %d", &speed) == 1 &&
speed >= 0 && speed <= 65535) {
</pre>

Code/tp-fancontrol.conf

2025-04-11T07:29:30Z

ThinkGNU: Put config file in <pre> block.

<pre>
# config file for tp-fancontrol

#
# The temparature shift will shift the trip points for different fan speeds.
#
# A positive value means that the trip-point is at a higher temperature and
# thus the fan is less noisy. A negative shift lets the fan start earlier.
# The default value is 0.
#
#TEMP_SHIFT=10

#
# True if logging to syslog should be enabled. If zero no logging to syslog
# is enabled. All output will appear on console. This option implies QUIET=1.
# The default value is 1.
#
#LOG_SYSLOG=0

#
# If no logging to syslog is on, the output will be verbose. To be less
# verbose set QUIET to 1. The default value is 1.
#
#QUIET=1

#
# The file to store the pid of the currently running fan-control daemon in.
# The default value is /var/run/tp-fancontrol.pid
#
#PIDFILE=/var/run/tp-fancontrol.pid
</pre>

Code/tp-fancontrol.init

2025-04-11T07:28:57Z

ThinkGNU: Put script in <pre> block, so it can be copy-pasted

<pre>
#! /bin/sh
### BEGIN INIT INFO
# Provides: tp-fancontrol
# Default-Start: 2 3 4 5
# Default-Stop: S 0 1 6
### END INIT INFO
# Copyright (c) 2006 Ronald Aigner <ra3@os.inf.tu-dresden.de>

set -e

DAEMON=/usr/bin/tp-fancontrol
NAME=tp-fancontrol
DAEMONUSER=root
PIDDIR=/var/run
PIDFILE=$PIDDIR/tp-fancontrol.pid
DESC="Thinkpad CPU fan control"

test -x $DAEMON || exit 0

# source config file; edit that file to configure this script
TEMP_SHIFT=0
LOG_SYSLOG=1
QUIET=1
if [ -e /etc/tp-fancontrol.conf ]; then
. /etc/tp-fancontrol.conf
fi

start_it()
{
PARAMS=-d
if [ -e $PIDFILE ]; then
echo "$DESC already running. Stop first."
exit 1
fi
if [ "$TEMP_SHIFT" != "0" ]; then
PARAMS=$PARAMS" -s $TEMP_SHIFT"
fi
if [ "$LOG_SYSLOG" = "1" ]; then
PARAMS=$PARAMS" -l"
else
if [ "$QUIET" = "1" ]; then
PARAMS=$PARAMS" -q"
fi
fi
PARAMS=$PARAMS" -p $PIDFILE"

echo -n "Starting $DESC: $NAME ... "
$DAEMON $PARAMS
if [ "$?" = "0" ]; then
echo "Success."
else
echo "Error while starting: $?"
fi
}

stop_it()
{
if [ -e $PIDFILE ]; then
echo -n "Stopping $DESC ... "
$DAEMON -k
if [ "$?" = "0" ]; then
echo "Success."
else
echo "Error while stopping: $?"
fi
else
echo "$DESC not running."
fi
}

restart_it()
{
if [ -e $PIDFILE ]; then
stop_it
sleep 2
fi
start_it
}

case "$1" in
start)
start_it
;;
stop)
stop_it
;;
reload|force-reload|restart)
restart_it
;;
*)
echo "Usage: /etc/init.d/$NAME {start|stop|reload|restart|force-reload}" >&2
exit 1
;;
esac

exit 0
</pre>

Code/tp-fancontrol

2025-04-11T07:28:10Z

ThinkGNU: Put script in <pre> block, so it can be copy-pasted

<pre>
#!/bin/bash

# tp-fancontrol 0.3.02 (http://thinkwiki.org/wiki/ACPI_fan_control_script)
# Provided under the GNU General Public License version 2 or later or
# the GNU Free Documentation License version 1.2 or later, at your option.
# See http://www.gnu.org/copyleft/gpl.html for the Warranty Disclaimer.

# This script dynamically controls fan speed on some ThinkPad models
# according to user-defined temperature thresholds. It implements its
# own decision algorithm, overriding the ThinkPad embedded
# controller. It also implements a workaround for the fan noise pulse
# experienced every few seconds on some ThinkPads.
#
# Run 'tp-fancontrol --help' for options.
#
# For optimal fan behavior during suspend and resume, invoke
# "tp-fancontrol -u" during the suspend process.
#
# WARNING: This script relies on undocumented hardware features and
# overrides nominal hardware behavior. It may thus cause arbitrary
# damage to your laptop or data. Watch your temperatures!
#
# WARNING: The list of temperature ranges used below is much more liberal
# than the rules used by the embedded controller firmware, and is
# derived mostly from anecdotal evidence, hunches and wishful thinking.
# It is also model-specific (see http://thinkwiki.org/wiki/Thermal_sensors).

# Temperature ranges, per sensor:
# (min temperature: when to step up from 0-th fan level,
# max temperature: when to step up to maximum fan level)
THRESHOLDS=( # Sensor ThinkPad model
# R51 T41/2 Z60t T43-26xx
# min max # ---------- ------- ----- ----- ---------------------------
50 70 # EC 0x78 CPU CPU ? CPU
47 60 # EC 0x79 miniPCI ? ? Between CPU and PCMCIA slot
43 55 # EC 0x7A HDD ? ? PCMCIA slot
49 68 # EC 0x7B GPU GPU ? GPU
40 50 # EC 0x7C BAT BAT BAT Sys BAT (front left of battery)
40 50 # EC 0x7D n/a n/a n/a UltraBay BAT
37 47 # EC 0x7E BAT BAT BAT Sys BAT (rear right of battery)
37 47 # EC 0x7F n/a n/a n/a UltraBay BAT

45 60 # EC 0xC0 ? n/a ? Between northbridge and DRAM
48 62 # EC 0xC1 ? n/a ? Southbridge (under miniPCI)
50 65 # EC 0xC2 ? n/a ? Power circuitry (under CDC)

47 58 # HDD -> -> -> Hard disk internal sensor
47 60 # HDAPS -> -> -> HDAPS readout (same as EC 0x79)
)

LEVELS=( 0 2 4 7) # Fan speed levels
ANTIPULSE=( 0 1 1 0) # Prevent fan pulsing noise at this level
# (reduces frequency of fan RPM updates)

OFF_THRESH_DELTA=3 # when gets this much cooler than 'min' above, may turn off fan
MIN_THRESH_SHIFT=0 # increase min thresholds by this much
MAX_THRESH_SHIFT=0 # increase max thresholds by this much
MIN_WAIT=180 # minimum time (seconds) to spend in a given level before stepping down

IBM_ACPI=/proc/acpi/ibm
HDAPS_TEMP=/sys/bus/platform/drivers/hdaps/hdaps/temp1
PID_FILE=/var/run/tp-fancontrol.pid
LOGGER=/usr/bin/logger
INTERVAL=3 # sample+refresh interval
SETTLE_TIME=6 # wait this many seconds long before applying anti-pulsing
RESETTLE_TIME=600 # briefly disable anti-pulsing at every N seconds
SUSPEND_TIME=5 # seconds to sleep when receiving SIGUSR1
DISK_POLL_PERIOD=15 # poll period in seconds for disk sensors (it changes slowly and is expensive to read)
HITACHI_MODELS="^(HTS4212..H9AT00|HTS726060M9AT00|HTS5410..G9AT00|IC25[NT]0..ATCS0[45]|HTE541040G9AT00|HTS5416..J9(AT|SA)00)"
SEP=',' # Separator char for display

WATCHDOG_DELAY=$(( 3 * INTERVAL ))
HAVE_WATCHDOG=`grep -q watchdog $IBM_ACPI/fan && echo true || echo false`
HAVE_LEVELCMD=`grep -q disengaged $IBM_ACPI/fan && echo true || echo false`

QUIET=false
DRY_RUN=false
DAEMONIZE=false
AM_DAEMON=false
KILL_DAEMON=false
SUSPEND_DAEMON=false
SYSLOG=false
DISK_POLL_TIME=-$DISK_POLL_PERIOD

usage() {
echo "
Usage: $0 [OPTION]...

Available options:
-s N Shift up the min temperature thresholds by N degrees
(positive for quieter, negative for cooler).
Max temperature thresholds are not affected.
-S N Shift up the max temperature thresholds by N degrees
(positive for quieter, negative for cooler). DANGEROUS.
-t Test mode
-q Quiet mode
-d Daemon mode, go into background (implies -q)
-l Log to syslog
-k Kill already-running daemon
-u Tell already-running daemon that the system is being suspended
-p Pid file location for daemon mode, default: $PID_FILE
"
exit 1;
}

while getopts 's:S:qtdlp:kuh' OPT; do
case "$OPT" in
s) # shift thresholds
MIN_THRESH_SHIFT="$OPTARG"
;;
S) # shift thresholds
MAX_THRESH_SHIFT="$OPTARG"
;;
t) # test mode
DRY_RUN=true
;;
q) # quiet mode
QUIET=true
;;
d) # go into background and daemonize
DAEMONIZE=true
;;
l) # log to syslog
SYSLOG=true
;;
p) # different pidfile
PID_FILE="$OPTARG"
;;
k) # kill daemon
KILL_DAEMON=true
;;
u) # suspend daemon
SUSPEND_DAEMON=true
;;
h) # short help
usage
;;
\?) # error
usage
;;
esac
done
[ $OPTIND -gt $# ] || usage # no non-option args

# no logger found, no syslog capabilities
$SYSLOG && [ ! -x $LOGGER ] && SYSLOG=false || :

if $DRY_RUN; then
echo "$0: Dry run, will not change fan state."
QUIET=false
DAEMONIZE=false
fi

# Read the temperature sensor on new Hitachi drivers without spinning up the
# disk or unloading its head (this cannot be done using standard SMART).
# Works only with drivers/ide or new libata. Equivalent to hdparm -H in >=6.7.
read_hitachi_temp() { perl - "$@" <<'EOPERL' # do it in Perl
#!/usr/bin/perl
$dev="$ARGV[0]" or die "No device given.\n";
$HDIO_DRIVE_CMD=0x031f;
$args=pack("cccc",0xf0,0,0x01,0); # Sense Condition command
open(DEV,"<",$dev) or die "open(\"$dev\"): $!\n";
if (ioctl(DEV,$HDIO_DRIVE_CMD,$args)) {
$nsect=(unpack("cccc",$args))[2];
if ($nsect==0 || $nsect==0xff) {
die "Temperature over/underflow.\n";
} elsif ($nsect==0x01) { # Linux<=2.6.18 doesn't return ATA registers
die "Old Linux kernel, readout not supported.\n";
} else {
printf "%d\n", $nsect/2-20;
}
} else {
die "ioctl(\"$dev\",HDIO_DRIVE_CMD,SENSE_CONDITION): $!\n"
}
EOPERL
}

update_disk_temp() {
if (( SECONDS >= DISK_POLL_TIME + DISK_POLL_PERIOD )); then
LAST_DISK_TEMP="-128"
for DEV in {sda,hda}; do
if [[ -b "/dev/$DEV" ]]; then
local MODEL=`cat /sys/block/$DEV/device/model`
if [[ "$MODEL" =~ "$HITACHI_MODELS" ]]; then
if HTEMP=`read_hitachi_temp "/dev/$DEV" 2>/dev/null`; then
LAST_DISK_TEMP="$HTEMP"
break
fi
fi
fi
done
DISK_POLL_TIME=$SECONDS
fi
}

thermometer() { # output list of temperatures
# 8 basic temperatures from ibm-acpi:
[[ -r $IBM_ACPI/thermal ]] || { echo "$0: Cannot read $IBM_ACPI/thermal" 2>&1 ; exit 1; }
read THERMAL < $IBM_ACPI/thermal
read X Y1 Y2 Y3 Y4 Y5 Y6 Y7 Y8 Z1 Z2 Z3 JNK < <(echo "$THERMAL")
[[ "$X" == "temperatures:" ]] || { echo "$0: Bad readout: \"$THERMAL\"" >&2; exit 1; }
echo -n "$Y1 $Y2 $Y3 $Y4 $Y5 $Y6 $Y7 $Y8 ";
# 3 extra temperatures from ibm_acpi:
if [[ -n "$Z1" && -n "$Z2" && -n "$Z3" ]]; then
# ibm_acpi provided extra sensors from at EC offsets 0xC0 to 0xC2?
echo -n "$SEP $Z1 $Z2 $Z3 "
else
[ -r $IBM_ACPI/ecdump ] || { echo "$0: Cannot read $IBM_ACPI/ecdump" 2>&1; exit 1; }
perl -e 'm/^EC 0xc0: .(..) .(..) .(..) / and print hex($1)." ".hex($2)." ".hex($3)." " and exit 0 while <>; exit 1' < $IBM_ACPI/ecdump
fi
# 1 Disk drive temperatures:
echo -n "$SEP $LAST_DISK_TEMP "
# 1 HDAPS temperature (optional):
if [ -r $HDAPS_TEMP ]; then
Y="`cat $HDAPS_TEMP`"
(( "$Y" > 100 )) || echo -n "$Y " # the HDAPS readouts are nonsensical right after resume
fi
return 0
}

speedometer() { # output fan speed RPM
sed -n 's/^speed:[ \t]*//p' $IBM_ACPI/fan
}

setlevel() { # set fan speed level
local LEVEL=$1
if ! $DRY_RUN; then
if $HAVE_LEVELCMD; then
echo "level $LEVEL" > $IBM_ACPI/fan
else
case "$LEVEL" in
(auto) LEVEL=0x80 ;;
(disengaged) LEVEL=0x40 ;;
esac
echo 0x2F $LEVEL > $IBM_ACPI/ecdump
fi
fi
}

getlevel() { # get fan speed level
perl -e 'm/^EC 0x20: .* .(..)$/ and print $1 and exit 0 while <>; exit 1' < $IBM_ACPI/ecdump
}

log() {
$QUIET || echo "> $*"
! $SYSLOG || $LOGGER -t "`basename $0`[$$]" "$*"
}

cleanup() { # clean up after work
$AM_DAEMON && rm -f "$PID_FILE" 2> /dev/null
log "Shutting down, switching to automatic fan control"
if ! $DRY_RUN; then
if $HAVE_LEVELCMD; then
echo enable > $IBM_ACPI/fan
else
echo 0x2F 0x80 > $IBM_ACPI/ecdump
fi
if $HAVE_WATCHDOG; then
echo watchdog 0 > $IBM_ACPI/fan # disable watchdog
fi
fi
}

floor_div() {
echo $(( (($1)+1000*($2))/($2) - 1000 ))
}

set_priority() {
! $DRY_RUN && renice -10 -p $$
}

init_state() {
IDX=0
NEW_IDX=0
START_TIME=0
MAX_IDX=$(( ${#LEVELS[@]} - 1 ))
SETTLE_LEFT=0
RESETTLE_LEFT=0
FIRST=true
RESTART=false
}

control_fan() {
# Enable the fan in default mode if anything goes wrong:
set -e -E -u
trap "cleanup; exit 2" HUP INT ABRT QUIT SEGV TERM
trap "cleanup" EXIT
trap "log 'Got SIGUSR1'; setlevel 0; RESTART=true; sleep $SUSPEND_TIME" USR1
if ! $DRY_RUN && $HAVE_WATCHDOG; then
log "Activating watchdog with delay $WATCHDOG_DELAY sec"
echo "watchdog $WATCHDOG_DELAY" > $IBM_ACPI/fan
fi

init_state
log "Starting dynamic fan control"

# Control loop:
while true; do
# Get readouts
update_disk_temp # don't do this in a subshell, it's stateful
TEMPS=`thermometer`
$QUIET || SPEED=`speedometer`
$QUIET || ECLEVEL=`getlevel`
NOW=`date +%s`
if echo "$TEMPS" | grep -q "[^ 0-9$SEP\n-]"; then
echo "Invalid character in temperatures: $TEMPS" >&2; exit 1;
fi

# Calculate new level index by placing temperatures into regions of "Z" values:
# Z >= 2*I means "must be at index I or higher"
# Z = 2*I+1 is hysteresis: "don't step down if currently at I+1"
# The set of temperatures for each Z value are as follows, denoting d=(MAX-MIN)/(2*(MAX_IDX-1)) :
# Z=0: {-infty..MIN-OFF_THRESH_DELTA) Z=1: {MIN-OFF_THRESH_DELTA..MIN}
# Z=2: {MIN..MIN+d} Z=3: {MIN+d..MIN+2d}
# Z=4: {MIN+2d..MIN+3d} Z=5: {MIN+3d..MIN+4d} ...
# Z=2*MAX_IDX: {MAX..infty}

# Enforce minimum time in this level before stepping down:
MAX_Z=$(( IDX>0 ? ( NOW>START_TIME+MIN_WAIT ? 2*(IDX-1) : 2*IDX ) : 0 ))

# Go over all sensors and compute the Z value; compute the maximum Z and a pretty-printed string:
SENSOR=0
Z_STR="$MAX_Z+"
TEMP_STR="";
for TEMP in $TEMPS; do
if [[ "$TEMP" == "$SEP" ]]; then # ignore this (a separator for visual aid)
Z_STR="${Z_STR}$SEP"
TEMP_STR="${TEMP_STR}$SEP "
continue
fi
[ $((2*SENSOR+2)) -le ${#THRESHOLDS[@]} ] ||
{ echo "Too many sensors, not enough values in THRESHOLDS" 2>&1; exit 1; }
if [[ $TEMP == -128 || $TEMP == 128 ]]; then
Z='_'; TEMP='_' # inactive sensor
else
MIN=$((THRESHOLDS[SENSOR*2] + MIN_THRESH_SHIFT))
MAX=$((THRESHOLDS[SENSOR*2+1] + MAX_THRESH_SHIFT ))
[[ $MAX -le $MIN ]] && \
{ echo 'Reversed temperature thresholds (shifted too much?)' 2>&1; exit 1; }
if (( TEMP < MIN - OFF_THRESH_DELTA )); then
Z=0
else # compute Z value for this sensor (see above):
Z=$(( `floor_div $(( 2*(TEMP-MIN)*(MAX_IDX-1) )) $((MAX-MIN))` + 2 ))
[ $Z -ge 1 ] || Z=1
[ $Z -le $((2*MAX_IDX)) ] || Z=$((2*MAX_IDX))
fi
[ $MAX_Z -gt $Z ] || MAX_Z=$Z
fi
Z_STR="${Z_STR}${Z}"
TEMP_STR="${TEMP_STR}${TEMP} "
(( ++SENSOR ))
done
[ $SENSOR -gt 0 ] || { echo "No temperatures read" >&2; exit 1; }

HYS=$(( (MAX_Z == 2*IDX-1) && ++MAX_Z )) # hysteresis
NEW_IDX=$(( MAX_Z/2 ))

# Interrupted by a signal?
if $RESTART; then
init_state
log "Resetting state"
continue
fi

# Transition
$FIRST && OLDLEVEL='?' || OLDLEVEL=${LEVELS[$IDX]}
NEWLEVEL=${LEVELS[$NEW_IDX]}
$QUIET || echo "L=$OLDLEVEL->$NEWLEVEL EC=$ECLEVEL RPM=`printf %4s $SPEED` T=($TEMP_STR) Z=$Z_STR"
if [ "$OLDLEVEL" != "$NEWLEVEL" ]; then
START_TIME=$NOW
log "Changing fan level: $OLDLEVEL->$NEWLEVEL (temps: $TEMP_STR)"
fi

setlevel $NEWLEVEL

sleep $INTERVAL

# If needed, apply anti-pulsing hack after a settle-down period (and occasionally re-settle):
if [ ${ANTIPULSE[${NEW_IDX}]} == 1 ]; then
if [ $NEWLEVEL != $OLDLEVEL -o $RESETTLE_LEFT -le 0 ]; then # start settling?
SETTLE_LEFT=$SETTLE_TIME
RESETTLE_LEFT=$RESETTLE_TIME
fi
if [ $SETTLE_LEFT -ge 0 ]; then
SETTLE_LEFT=$((SETTLE_LEFT-INTERVAL))
else
setlevel disengaged # disengage briefly to fool embedded controller
sleep 0.5
RESETTLE_LEFT=$((RESETTLE_LEFT-INTERVAL))
fi
fi

IDX=$NEW_IDX
FIRST=false
done
}

if $KILL_DAEMON || $SUSPEND_DAEMON; then
if [ -f "$PID_FILE" ]; then
set -e
DPID="`cat \"$PID_FILE\"`"
if $KILL_DAEMON; then
kill "$DPID"
rm "$PID_FILE"
$QUIET || echo "Killed process $DPID"
else # SUSPEND_DAEMON
kill -USR1 "$DPID"
$QUIET || echo "Sent SIGUSR1 to $DPID"
fi
else
$QUIET || echo "Daemon not running."
exit 1
fi
elif $DAEMONIZE ; then
if [ -e "$PID_FILE" ]; then
echo "$0: File $PID_FILE already exists, refusing to run."
exit 1
else
set_priority
AM_DAEMON=true QUIET=true control_fan 0<&- 1>&- 2>&- &
echo $! > "$PID_FILE"
exit 0
fi
else
[ -e "$PID_FILE" ] && echo "WARNING: daemon already running"
set_priority
control_fan
fi
</pre>

Code/build-experimental-X

2025-04-11T07:27:42Z

ThinkGNU: Put script in <pre> block.

<pre>
#!/bin/bash
# Script to fetch and build X.org (incl. XCB and pixman), DRI, Mesa and
# xkeyboard-config from CVS and GIT, and save full git snapshots of their
# source and installation.
#
# Default action:
# - Create/update a git repository for each module, under $HOME/3d-pit.
# - Install all modules, under $HOME/3d-pit/install
# - Make $HOME/3d-pit/install a git repository to track the installed binaries
# - Make $HOME/3d-pit a git super-repository which tracks all of the above
# using the submodule mechanism of git >= 1.5.3.
#
# Each of these can be disabled via command line (see the code table below).
#
# Source: http://thinkwiki.org/wiki/How_to_compile_an_experimental_X_server
# See also:
# http://wiki.x.org/wiki/ModularDevelopersGuide
# http://wiki.x.org/wiki/GitPage
# http://gitweb.freedesktop.org
# http://dri.freedesktop.org/wiki/Building
# http://www.mesa3d.org/repository.html
# http://www.mesa3d.org/install.html
# http://web.telia.com/~u89404340/touchpad
# http://www.freedesktop.org/wiki/Software_2fXKeyboardConfig
# http://gitweb.freedesktop.org/?p=xorg/util/modular.git;a=blob;f=build.sh

#############################################
# X.org setup
# This is a list of modules that are in flux and likely to be related to
# whatever you're testing (or are required for the build), sorted by
# build order (see util/modular/build.sh for dependencies).
# Check CVS and the above URLs for other modules.
# For exhaustive list, see
# get -qO - http://gitweb.freedesktop.org/ \
# | perl -ne 'print "$1\n" if m!<a href="/\?p=([^;]+);a=summary">!' \
# | egrep '^xcb/|^xorg/|^pixman/'

XORG_MODULES=(
xorg/util/macros
xorg/proto/{bigreqs,composite,fixes,damage,gl,input,kb,pm,randr,resource,xext,xcmisc}proto
xorg/proto/{fontcache,fonts,kb}proto
xorg/proto/{render,scrnsaver,video}proto
xorg/proto/{x11,xf86bigfont,xf86dga,xf86dri,xf86misc,xf86vidmode,xinerama}proto
xcb/proto
xorg/lib/lib{xtrans,Xau,Xdmcp}
xcb/libxcb
xorg/lib/lib{X11,ICE,SM,Xt,Xmu,Xcomposite,Xrender,Xdamage,Xcursor,Xi,Xinerama}
xorg/lib/lib{Xfont,Xfontcache,Xft}
xorg/lib/lib{xkbui,Xrandr,Xv,XvMC,Xxf86dga,Xxf86misc,Xxf86vm,pciaccess}
pixman
xorg/xserver
xorg/driver/xf86-video-ati
xorg/driver/xf86-input-{mouse,keyboard,joystick,evdev}
xorg/app/{xkbutils,xkbcomp,setxkbmap,xrandr,xsetpointer,xbacklight}
)

#############################################
# Init

FETCH=true
BUILD=true
RECONFIGURE=false # Reconfigure everything even if unchanged from last run
MAKE_CLEAN=false # If true, run "make clean" before building.
GIT_CLEAN=false # Use "git clean" to delete all non-source files before building.
SUPERMODULE=true # Take meta-snapshots using Git super/submodule

for OPT in "$@"; do
case "$OPT" in
(--no-fetch) FETCH=false ;;
(--no-build) BUILD=false ;;
(--no-supermodule) SUPERMODULE=false ;;
(--reconfigure) RECONFIGURE=true ;;
(--make-clean) MAKE_CLEAN=true ;;
(--git-clean) GIT_CLEAN=true ;;
(*) echo "Unknown option" >&2; exit 1 ;;
esac
done

PIT=$HOME/3d-pit # Download and build here
DEST_SUBDIR=install # Install in this subdirectory of $PIT
USE_XCB=false # Use XCB?
FLAGS='-O2 -g -march=pentium-m'

DEST=$PIT/$DEST_SUBDIR

trap "echo Aborting.; exit 1" ERR
set -E

#############################################
# Support functions

die() {
echo "$*"
exit 1
}

run() {
echo "@`pwd`: $@"
"$@" || { echo "ERROR: Command \"$*\" failed in `pwd`"; exit 1; }
}

nothing_to_commit() {
git status > /dev/null # Force check of files for which only the timestamp changed.
git diff --quiet HEAD > /dev/null
}

fetch_from_git() {
PARENT_DIR="$1"
GIT_REP="$2"
MODULE="$3"
DIR="${4:-$MODULE}"
FULLDIR="$PARENT_DIR/$DIR"
RELDIR="${FULLDIR#$PIT/}"
if [ -d "$FULLDIR" ]; then
cd "$FULLDIR"
ORIG_HEAD=`git rev-parse HEAD`
run git pull
NEW_HEAD=`git rev-parse HEAD`
[[ "$ORIG_HEAD" == "$NEW_HEAD" ]] || run git shortlog ORIG_HEAD..HEAD | cat
else
run cd "$PARENT_DIR"
run git clone "$GIT_REP/$MODULE" "$DIR"
cd "$DIR"
git gc
fi

add_to_supermodule "$RELDIR"
}

fetch_from_cvs() {
CVS_SERVER="$1"
DIR="$2"
GITIGNORES="$3"

run cd $PIT
if [ ! -d $DIR ]; then
grep -qF $CVS_SERVER ~/.cvspass || run cvs -d $CVS_SERVER login
run cvs -z3 -d $CVS_SERVER co $DIR

cd $PIT/$DIR
run git init
fi

cd $PIT/$DIR
run cvs -z3 update -ACPd -I .gitignore -I .git
find . -name .cvsignore | while read X; do cp "$X" "${X%/.cvsignore}/.gitignore"; done
echo -e "$GITIGNORES" >> .gitignore
run git add .
nothing_to_commit || run git commit -a -m "`date +'Fetched at %Y-%m-%d %H:%M:%S'`"

# We could use git-cvsimport instead, but that's way too slow:
# mkdir -p $PIT/$DIR
# cd $PIT/$DIR
# git-cvsimport -v -d "$CVS_SERVER" -r origin

add_to_supermodule "$DIR"
}

#############################################
# Handing git super/submodules

if $SUPERMODULE; then
which git-submodule >&/dev/null || \
die "Error: git >= 1.3.5 required for submodule support. Try --no-supermodule."

run mkdir -p $PIT
cd $PIT
if [ ! -d .git ]; then
run git init
echo -e 'xorg/autoconf.cache' > .gitignore
run git add .gitignore
run git commit -m 'initial'
fi

# Add new submodule's repository to the supermodule's .gitmodules
add_to_supermodule_gitmodules() {
SUBDIR="$1"
GIT_CONFIG=$PIT/.gitmodules git config "submodule.$SUBDIR.path" "$SUBDIR"
GIT_CONFIG=$PIT/.gitmodules git config "submodule.$SUBDIR.url" "$SUBDIR"
}

add_to_supermodule() {
cd $PIT
# add_to_supermodule_alternates "$1"
add_to_supermodule_gitmodules "$1"
run git add "$1"
}
else
add_to_supermodule() { true; }
fi

#############################################
# Directory hashes for change detection

LAST_HASH=.last_dir_hash

dir_hash() {
find . $ -name $LAST_HASH -o -path ./.git -prune $ -o -type f -ls | sort | md5sum
}

dir_hash_changed() {
$RECONFIGURE || [ ! -f $LAST_HASH ] || [ "`dir_hash`" != "`cat $LAST_HASH`" ]
}

save_dir_hash() {
dir_hash > $LAST_HASH
}

#############################################
# Fetching and building libDRM and DRM kernel drivers

fetch_drm() {
echo "########### Fetch DRM ###########"
DRM_GIT=git://anongit.freedesktop.org/git/mesa
fetch_from_git "$PIT" "$DRM_GIT" drm
}

build_libdrm() {
echo "########### Build libdrm ###########"
run cd $PIT/drm
! $GIT_CLEAN || run git clean -x -d
if dir_hash_changed; then
run ./autogen.sh
CFLAGS="$FLAGS" run ./configure --prefix=$DEST --quiet
save_dir_hash
fi
! $MAKE_CLEAN || run make clean
run make
save_dir_hash
run make install
save_dir_hash
}

build_drm_modules() {
echo "########### Build DRM kernel modules ###########"
run cd $PIT/drm/linux-core
! $GIT_CLEAN || run git clean -x -d
! $MAKE_CLEAN || run make clean
run make DRM_MODULES="radeon"
run sudo sh -c \
'rm -fv /lib/modules/`uname -r`/kernel/drivers/char/drm/*.ko; \
cp -v *.ko /lib/modules/`uname -r`/extra/; \
/sbin/depmod -a'
}

#############################################
# Fetching Mesa

fetch_mesa() {
echo "########### Fetching Mesa ###########"
MESA_GIT=git://anongit.freedesktop.org/git/mesa
run mkdir -p $PIT
run cd $PIT
fetch_from_git "$PIT" "$MESA_GIT" mesa
}

#############################################
# Building Mesa (do this after installing base X.org libraries

build_mesa() { (
echo "########### Building Mesa ###########"
# This uses both old-style and new-style vars, to support older Mesa snapshots.
run cd $PIT/mesa
export DRM_SOURCE_PATH=$PIT/drm
export PKG_CONFIG_PATH="$DEST/lib/pkgconfig:$PKG_CONFIG_PATH"
export DRM_SOURCE_PATH="$PIT/drm"
export DESTDIR=$DEST INSTALL_DIR=$DEST
export DRI_DRIVER_INSTALL_DIR=$DEST/lib/dri
export DRI_DIRS='r300 r200 r128 radeon'
export OPT_FLAGS="$FLAGS"
export PATH="$DEST/bin:$PATH"
run mkdir -p $DRI_DRIVER_INSTALL_DIR
! $GIT_CLEAN || run git clean -x -d
! $MAKE_CLEAN || run make clean
if [ -e configs/current ]; then
run make -e
else
run make -e linux-dri-x86
fi
run make -e install
run cp -v lib/*_dri.so $DRI_DRIVER_INSTALL_DIR
) }

#############################################
# Fetching X.org

fetch_xorg() {
echo "########### Fetching (selected) X.org modules ###########"
XORG_GIT=git://anongit.freedesktop.org/git
run mkdir -p $PIT/xorg
for D in "${XORG_MODULES[@]}"; do
if [[ $D == xcb/* ]] && ! $USE_XCB; then continue; fi
fetch_from_git $PIT/xorg "$XORG_GIT" "$D" "${D#xorg/}"
done
}

#############################################
# Building and installing X.org
# (On repeated runs we avoid rerunning autotools if nothing changed.)

build_x_module() { (
D="${1#xorg/}"
echo "########### Building xorg/$D ###########"
export PATH="$DEST/bin:$PATH"
export PKG_CONFIG_PATH="$DEST/lib/pkgconfig:$PKG_CONFIG_PATH"
export ACLOCAL="${AC_LOCAL:-aclocal} -I $DEST/share/aclocal"
export LD_LIBRARY_PATH="$DEST/lib:$LD_LIBRARY_PATH"

if [ $D == "xserver" ]; then
CONF_OPT="--with-mesa-source=$PIT/mesa --enable-xorg --disable-dmx --disable-xvfb --disable-xnest --disable-xprint --disable-freetype --disable-xselinux"
elif [ $D == "lib/libX11" ] && ! $USE_XCB; then
CONF_OPT="--with-xcb=no"
else
CONF_OPT=
fi

run cd $PIT/xorg/$D
! $GIT_CLEAN || run git clean -x -d
if dir_hash_changed; then
CFLAGS="$FLAGS" run sh autogen.sh --prefix=$DEST --quiet $CONF_OPT
# --cache-file=$PIT/xorg/autoconf.cache
save_dir_hash
fi
! $MAKE_CLEAN || run make clean
run make
save_dir_hash
run make install
save_dir_hash

if [ $D == "pixman" ]; then # as of 2007-08-07 pixman needs this hack:
[ -e $DEST/include/pixman.h ] || run ln -fs pixman-1/pixman.h $DEST/include/pixman.h
fi
) }

build_xorg() {
run cd $PIT/xorg
run mkdir -p $DEST/share/aclocal
run mkdir -p $DEST/var/log
for D in "${XORG_MODULES[@]}"; do
if [[ $D == xcb/* ]] && ! $USE_XCB; then continue; fi
build_x_module $D || return 1
done
run sudo sh -c "chown -v root $DEST/bin/Xorg; \
chmod -v 4750 $DEST/bin/Xorg"
}

#############################################
# Fetching and building xkeyboard-config

fetch_xkeyboard_config() {
echo "########### Fetching xkeyboard-config ###########"
XKBC_CVS=":pserver:anoncvs@cvs.freedesktop.org:2401/cvs/xkeyboard-config"
XKBC_DIR=xkeyboard-config
XKBC_GITIGNORES='install-sh\nmissing\npo/stamp-it'
fetch_from_cvs "$XKBC_CVS" "$XKBC_DIR" "$XKBC_GITIGNORES"
}

build_xkeyboard_config() { (
echo "########### Building xkeyboard-config ###########"
run cd $PIT/xkeyboard-config
run ./autogen.sh
export PKG_CONFIG_PATH="$DEST/lib/pkgconfig:$PKG_CONFIG_PATH"
export PATH="$DEST/bin:$PATH"
CFLAGS="$FLAGS" run ./configure --quiet --prefix=$DEST \
--with-xkb-base=$DEST/share/X11/xkb --with-xkb-rules-symlink=xorg
run make
# "make install" replaces share/X11/xkb/compiled.tmp with a junk symlink, so override it:
mv $DEST/share/X11/xkb/compiled $DEST/share/X11/xkb/compiled.tmp
run make install
rm -f $DEST/share/X11/xkb/compiled
mv $DEST/share/X11/xkb/compiled.tmp $DEST/share/X11/xkb/compiled
) }

#############################################
# Fetching and building the synaptics driver

fetch_synaptics() {
echo "########### Fetch synaptics ###########"
SYN_GIT=http://web.telia.com/~u89404340/touchpad/synaptics/.git
fetch_from_git "$PIT" "$SYN_GIT" '' synaptics
}

build_synaptics() { (
echo "########### Build synaptics ###########"
run cd $PIT/synaptics
export PKG_CONFIG_PATH="$DEST/lib/pkgconfig:$PKG_CONFIG_PATH"
export PATH="$DEST/bin:$PATH"
export CPATH="$DEST/include:$CPATH"
! $GIT_CLEAN || run git clean -x -d
! $MAKE_CLEAN || run make clean
run make
run make install PREFIX="$DEST" MANDIR="$DEST/share/man"
#run cp -v synaptics_drv.so $DEST/lib/xorg/modules/input/
) }

#############################################
# Creating a script which sets env vars

create_xsetenv() {
echo "Creating $DEST/bin/xsetenv"
cat <<EOF > $DEST/bin/xsetenv || die "Can't create $DEST/bin/xsetenv"
export PATH="$DEST/bin:$PATH"
export LD_LIBRARY_PATH="$DEST/lib:$LD_LIBRARY_PATH"
export LIBGL_DRIVERS_PATH=$DEST/lib/dri
EOF
}

#############################################
# Actual fetching and building:

if $FETCH; then
fetch_drm
fetch_mesa
fetch_xorg
fetch_xkeyboard_config
fetch_synaptics
fi
if $BUILD; then
build_libdrm
build_drm_modules
build_xorg
build_mesa
build_xkeyboard_config
build_synaptics
create_xsetenv
fi

#############################################
# Saving install and super state to git commits:

if $BUILD; then
echo "########### Record installation dir commit ###########"
cd $DEST
if [ ! -d .git ]; then
run git init
echo '/var/log' > .gitignore
run git add .gitignore
run git commit -a -m "initial"
fi
run git add .
if ! nothing_to_commit; then
run git commit -a -m "`date +'Installed at %Y-%m-%d %H:%M:%S'`"
run git gc
fi
add_to_supermodule "$DEST_SUBDIR"
fi

if $SUPERMODULE; then
echo "########### Record supermodule commit ###########"
cd $PIT
nothing_to_commit || run git commit -m "`date +'Snapshot at %Y-%m-%d %H:%M:%S'` `$FETCH && echo fetch` `$BUILD && echo build`"
fi

#############################################

echo
echo "Done."
! $FETCH || echo "Run '. $DEST/bin/xsetenv' to point env vars to this installation."
</pre>

Code/ibm acpi-extra-thermal.patch

2025-04-11T07:27:02Z

ThinkGNU: Put patch in <pre> block

<pre>
--- a/drivers/acpi/ibm_acpi.c 2006-03-20 06:53:29.000000000 +0100
+++ b/drivers/acpi/ibm_acpi.c 2006-07-19 01:55:52.000000000 +0200
@@ -1229,28 +1229,46 @@ static int thermal_read(char *p)
if (!thermal_tmp_supported)
len += sprintf(p + len, "temperatures:\tnot supported\n");
else {
- int i, t;
+ int i;
char tmpi[] = "TMPi";
- s8 tmp[8];
+ /*
+ * A few ThinkPads (e.g. R52, T43) have 3 unnamed sensors. We
+ * want their values as well.
+ */
+ static const size_t named_count = 8;
+ static const size_t unnamed_count = 3;
+ static const size_t unnamed_addresses[] = { 0xC0, 0xC1, 0xC2 };
+ static const size_t total_count = named_count + unnamed_count;
+ s8 tmp[total_count];

if (thermal_updt_supported)
if (!acpi_evalf(ec_handle, NULL, "UPDT", "v"))
return -EIO;

- for (i = 0; i < 8; i++) {
+ for (i = 0; i < named_count; i++) {
+ int t;
tmpi[3] = '0' + i;
if (!acpi_evalf(ec_handle, &t, tmpi, "d"))
return -EIO;
- if (thermal_updt_supported)
- tmp[i] = (t - 2732 + 5) / 10;
- else
- tmp[i] = t;
+ tmp[i] = (s8)t;
}

- len += sprintf(p + len,
- "temperatures:\t%d %d %d %d %d %d %d %d\n",
- tmp[0], tmp[1], tmp[2], tmp[3],
- tmp[4], tmp[5], tmp[6], tmp[7]);
+ for (i = 0; i < unnamed_count; ++i) {
+ size_t address = unnamed_addresses[i];
+ u8 t;
+ if (!acpi_ec_read(address, &t))
+ return -EIO;
+ tmp[i+named_count] = (s8)t;
+ }
+
+ len += sprintf(p + len, "temperatures:\t" );
+ for (i = 0; i < total_count; ++i) {
+ int value = thermal_updt_supported
+ ? (tmp[i] - 2732 + 5) / 10
+ : tmp[i];
+ len += sprintf(p + len, "%d%c", value,
+ i == total_count - 1 ? '\n' : ' ');
+ }
}

return len;
</pre>

Code/tp-bat-balance

2025-04-11T07:26:38Z

ThinkGNU: Put script in <pre> block, so it can be copy-pasted. Finally a good license.

<pre>
#!/usr/bin/perl
# Keep two ThinkPad batteries (system battery and UltraBay) at similar charge levels
# during discharge by switching back and forth. This reduces wear on the UltraBay
# battery, compared to the hardware's default strategy of fully draining the UltraBay
# battery before switching to the system battery.
# WARNING: This script is experimental and uses undocumented hardware features.
# WARNING: If this script crashes, your battery may be forced to keep draining until empty.
# Distributed under the terms of the GNU General Public License v2 or later.

use strict;
use warnings;
use File::Slurp;

my $thresh = 3; # difference between battery charge levels that justifies switching (hysteresis)

my $default_discharge = 0; # the battery that's discharged as first priority by the BIOS
my $smapi_dir = '/sys/devices/platform/smapi';

my $ac_connected;
my @bat_installed;
my @bat_remaining;
my @bat_state;
my @bat_power_avg;
my @bat_force_discharge;

$SIG{'INT'} = $SIG{'QUIT'} = $SIG{'TERM'} = sub { die("# Killed by SIG$_[0]\n"); };

sub read_chomp_file {
my ($filename) = @_;
my ($x) = read_file($filename) or die "Cannot read $filename\n";
chomp($x);
return $x;
}

# Read battery status from tp_smapi sysfs interface
sub read_status {
$ac_connected = read_chomp_file("$smapi_dir/ac_connected");
for my $b (0..1) {
$bat_installed[$b] = read_chomp_file("$smapi_dir/BAT$b/installed");
$bat_force_discharge[$b] = read_chomp_file("$smapi_dir/BAT$b/force_discharge");
if ($bat_installed[$b]) {
$bat_remaining[$b] = read_chomp_file("$smapi_dir/BAT$b/remaining_percent");
$bat_state[$b] = read_chomp_file("$smapi_dir/BAT$b/state");
$bat_power_avg[$b] = read_chomp_file("$smapi_dir/BAT$b/power_avg") / 1000.0;
}
else { $bat_state[$b] = 'none'; } #This var needs to always have a value for print_bat to not break. This covers the case of starting the program without a battery in the bay/slot.
}
}

# Print status to stdout (ASCII graphics)
sub print_status {
print " ";
sub print_bat {
my ($b) = @_;
my ($ll,$lr,$rl,$rr) = $b ? ('-','>','<','-') : ('<','-','-','>');
my $icon = sprintf("[%3s]", $bat_installed[$b] ? $bat_remaining[$b]."%" : "");
my $arrow;
my $state = $bat_state[$b];
if ($state eq 'charging') {
$arrow = sprintf("$ll--%4.1f--$lr", $bat_power_avg[$b]);
} elsif ($state eq 'discharging') {
$arrow = sprintf("$rl--%4.1f--$rr", -$bat_power_avg[$b]);
} elsif ($state eq 'idle' || $state eq 'none') { #Added none to cover case with no battery in slot when program was started.
$arrow = " ";
} else {
die "Unknown state $state for battery $b";
}
print($b ? "$arrow$icon" : "$icon$arrow");
}
print_bat(0);
print($ac_connected ? ' {AC} ' : ' { } ');
print_bat(1);
print("\n");
}

# Choose which battery to discharge
sub choose_discharge {
sub set_force_discharge {
my ($b,$on) = @_;
return if $b!=$default_discharge; # the non-default battery will be discharged only when necessary anyway
return if $bat_force_discharge[$b]==$on;
write_file("$smapi_dir/BAT$b/force_discharge", ($on?'1':'0')) or die ("Cannot write to $smapi_dir/BAT$b/force_discharge: $!\n");
print("# setting force_discharge on battery $b to $on\n");
$bat_force_discharge[$b] = $on;
}

if ($ac_connected || !$bat_installed[0] || !$bat_installed[1]) {
for $b (0..1) {
set_force_discharge($b,0);
}
} else {
if ($bat_remaining[0] > $bat_remaining[1] + $thresh) {
set_force_discharge(0,1);
set_force_discharge(1,0);
} elsif ($bat_remaining[1] > $bat_remaining[0] + $thresh) {
set_force_discharge(0,0);
set_force_discharge(1,1);
}
}
}

while (1) {
read_status;
print_status;
choose_discharge;
sleep(5);
}

END {
print("# Cleanup\n");
write_file("$smapi_dir/BAT0/force_discharge", ('0'));
write_file("$smapi_dir/BAT1/force_discharge", ('0'));
}
</pre>

Code/undervolt-pentium-m-2.6.13.1.patch

2025-04-11T07:25:46Z

ThinkGNU: Put patch in <pre> block

<pre>
--- linux-2.6.13.1-vanilla/arch/i386/kernel/cpu/cpufreq/speedstep-centrino.c 2005-09-10 05:42:58.000000000 +0300
+++ linux-2.6.13.1/arch/i386/kernel/cpu/cpufreq/speedstep-centrino.c 2005-10-18 04:46:01.000000000 +0200
@@ -54,6 +54,7 @@ enum {
CPU_DOTHAN_A1,
CPU_DOTHAN_A2,
CPU_DOTHAN_B0,
+ CPU_DOTHAN_C0,
CPU_MP4HT_D0,
CPU_MP4HT_E0,
};
@@ -63,6 +64,8 @@ static const struct cpu_id cpu_ids[] = {
[CPU_DOTHAN_A1] = { 6, 13, 1 },
[CPU_DOTHAN_A2] = { 6, 13, 2 },
[CPU_DOTHAN_B0] = { 6, 13, 6 },
+ [CPU_DOTHAN_C0] = { 6, 13, 8 },
[CPU_MP4HT_D0] = {15, 3, 4 },
[CPU_MP4HT_E0] = {15, 4, 1 },
};
@@ -94,6 +97,12 @@ static struct cpufreq_driver centrino_dr
.frequency = (mhz) * 1000, \
.index = (((mhz)/100) << 8) | ((mv - 700) / 16) \
}
+/* Likewise, for processors with 133MHz FSB. */
+#define OP133(mhz, mv) \
+ { \
+ .frequency = (mhz) * 1000, \
+ .index = (((mhz)/133) << 8) | ((mv - 700) / 16) \
+ }

/*
* These voltage tables were derived from the Intel Pentium M
@@ -202,7 +211,26 @@ static struct cpufreq_frequency_table ba
OP(1700, 1484),
{ .frequency = CPUFREQ_TABLE_END }
};
+
+/* Intel Pentium M 750, drastically undervoltaged */
+static struct cpufreq_frequency_table pentium_m_750[] =
+{
+ /* MHz mV */
+ OP133( 800, 700),
+ OP133(1066, 780),
+ OP133(1200, 828),
+ OP133(1333, 876),
+ OP133(1466, 924),
+ OP133(1600, 972),
+ OP133(1733, 1020),
+ OP133(1866, 1068),
+ { .frequency = CPUFREQ_TABLE_END }
+};
+
#undef OP
+#undef OP133

#define _BANIAS(cpuid, max, name) \
{ .cpu_id = cpuid, \
@@ -225,6 +253,12 @@ static struct cpu_model models[] =
BANIAS(1500),
BANIAS(1600),
BANIAS(1700),
+ {
+ .cpu_id = &cpu_ids[CPU_DOTHAN_C0],
+ .model_name = "Intel(R) Pentium(R) M processor 1.86GHz",
+ .max_freq = 1866000,
+ .op_points = pentium_m_750
+ },

/* NULL model_name is a wildcard */
{ &cpu_ids[CPU_DOTHAN_A1], NULL, 0, NULL },
</pre>

Code/ibm-acpi-0.12a-2.6.14-fan.patch

2025-04-11T07:25:21Z

ThinkGNU: Put patch in <pre> block

<pre>
--- drivers/acpi/ibm_acpi.c.orig 2005-11-01 19:47:44.262270250 +0100
+++ drivers/acpi/ibm_acpi.c 2005-11-01 20:16:16.081252250 +0100
@@ -1465,6 +1465,7 @@ static int fan_read(char *p)
{
int len = 0;
int s;
+ char status_read = 0;
u8 lo, hi, status;

if (gfan_handle) {
@@ -1477,9 +1478,11 @@ static int fan_read(char *p)
/* all except 570, 600e/x, 770e, 770x */
if (!acpi_ec_read(fan_status_offset, &status))
len += sprintf(p + len, "status:\t\tunreadable\n");
- else
+ else {
len += sprintf(p + len, "status:\t\t%s\n",
- enabled(status, 7));
+ status ? "enabled" : "disabled");
+ status_read = 1;
+ }

if (!acpi_ec_read(fan_rpm_offset, &lo) ||
!acpi_ec_read(fan_rpm_offset + 1, &hi))
@@ -1487,6 +1490,14 @@ static int fan_read(char *p)
else
len += sprintf(p + len, "speed:\t\t%d\n",
(hi << 8) + lo);
+ if (status_read) {
+ if (status & 0x40)
+ len += sprintf(p + len, "level:\t\tdisengaged\n");
+ else if (status & 0x80)
+ len += sprintf(p + len, "level:\t\tauto\n");
+ else
+ len += sprintf(p + len, "level:\t\t%d\n", status);
+ }
}

if (sfan_handle)
@@ -1495,7 +1506,10 @@ static int fan_read(char *p)
" (<level> is 0-7)\n");
if (!gfan_handle)
/* all except 570, 600e/x, 770e, 770x */
- len += sprintf(p + len, "commands:\tenable, disable\n");
+ len += sprintf(p + len,
+ "commands:\tenable, disable, level <level>\n"
+ " \t(<level> is 0-7, auto "
+ "or disengaged)\n");
if (fans_handle)
/* X31, X40 */
len += sprintf(p + len, "commands:\tspeed <speed>"
@@ -1516,7 +1530,8 @@ static int fan_write(char *buf)
/* 570, 770x-JL */
if (!acpi_evalf(sfan_handle, NULL, NULL, "vd", level))
return -EIO;
- } else if (!gfan_handle && strlencmp(cmd, "enable") == 0) {
+ } else if (!gfan_handle && ( (strlencmp(cmd, "enable") == 0) ||
+ (strlencmp(cmd, "level auto") == 0) ) ) {
/* all except 570, 600e/x, 770e, 770x */
if (!acpi_ec_write(fan_status_offset, 0x80))
return -EIO;
@@ -1524,6 +1539,17 @@ static int fan_write(char *buf)
/* all except 570, 600e/x, 770e, 770x */
if (!acpi_ec_write(fan_status_offset, 0x00))
return -EIO;
+ } else if (!gfan_handle &&
+ strlencmp(cmd, "level disengaged") == 0) {
+ /* all except 570, 600e/x, 770e, 770x */
+ if (!acpi_ec_write(fan_status_offset, 0x40))
+ return -EIO;
+ } else if (!gfan_handle &&
+ sscanf(cmd, "level %d", &level) == 1 &&
+ level >=0 && level <= 7) {
+ /* all except 570, 600e/x, 770e, 770x */
+ if (!acpi_ec_write(fan_status_offset, level))
+ return -EIO;
} else if (fans_handle &&
sscanf(cmd, "speed %d", &speed) == 1 &&
speed >= 0 && speed <= 65535) {
</pre>

Code/tp-fancontrol-basic

2025-04-11T07:24:42Z

ThinkGNU: Put script in <pre> block, so it can be copy-pasted

<pre>
#!/bin/bash

# This script dynamically controls fan speed on some ThinkPad models
# according to user-defined temperature thresholds. It implements its
# own decision algorithm, overriding the ThinkPad embedded
# controller. It also implements a workaround for the fan noise pulse
# experienced every few seconds on some ThinkPads.
#
# The script requires the ibm_acpi patch at
# http://thinkwiki.org/wiki/Patch_for_controlling_fan_speed
#
# WARNING: This script relies on undocumented hardware features and
# overrides nominal hardware behavior. It may thus cause arbitrary
# damage to your laptop or data. Watch your temperatures!
#
# This file is placed in the public domain and may be freely distributed.

LEVELS=( 0 2 4 7) # Fan speed levels
UP_TEMPS=( 52 60 68 ) # Speed increase trip points
DOWN_TEMPS=( 48 56 64 ) # Speed decrease trip points

ANTIPULSE=( 0 1 0 0) # Prevent fan pulsing noise at this level
# (this also prevents fan speed updates)

IBM_ACPI=/proc/acpi/ibm
FAN=$IBM_ACPI/fan
INTERVAL=3
VERBOSE=true
DRY_RUN=false

[[ "$1" == "-t" ]] && { DRY_RUN=true; echo "$0: Dry run, will not change fan state."; }

# Enable the fan in default mode if anything goes wrong:
set -e -E -u
$DRY_RUN || trap "echo enable > $FAN; exit 0" EXIT HUP INT ABRT QUIT SEGV TERM

thermometer() { # output list of temperatures
read X Y < $IBM_ACPI/thermal
[[ "$X" == "temperatures:" ]] || {
echo "$0: Bad temperatures: $X $Y" >&2
exit 1
}
echo "$Y";
}

speedometer() { # output fan speed
cat $FAN | sed '/^speed/!d; s/speed:[ \t]*//'
}

IDX=0
MAX_IDX=$(( ${#LEVELS[@]} - 1 ))
SETTLE=0

while true; do
TEMPS=`thermometer`
$VERBOSE && SPEED=`speedometer`

# Calculate new level
NEWIDX=$IDX
DOWN=$(( IDX > 0 ))
for TEMP in $TEMPS; do
# Increase speed as much as needed
while [[ $NEWIDX -lt $MAX_IDX ]] &&
[[ $TEMP -ge ${UP_TEMPS[$NEWIDX]} ]]; do
(( NEWIDX ++ ))
DOWN=0
done
# Allow decrease (by one index)?
if [[ $DOWN == 1 ]] &&
[[ $TEMP -gt ${DOWN_TEMPS[$(( IDX - 1 ))]} ]]; then
DOWN=0
fi
done
if [[ $DOWN == 1 ]]; then
NEWIDX=$(( IDX - 1 ))
fi

# Transition
OLDLEVEL=${LEVELS[$IDX]}
NEWLEVEL=${LEVELS[$NEWIDX]}
$VERBOSE && echo "tpfan: Temps: $TEMPS Fan: $SPEED Level: $OLDLEVEL->$NEWLEVEL"
$DRY_RUN || echo level $NEWLEVEL > $FAN

sleep $INTERVAL

# If needed, apply anti-pulsing hack after a settle-down period:
if [[ ${ANTIPULSE[${NEWIDX}]} == 1 ]]; then
if [[ $NEWLEVEL == $OLDLEVEL ]]; then
if [[ $SETTLE -ge 0 ]]; then
(( SETTLE -= INTERVAL ))
else
$DRY_RUN || echo level disengaged >> $FAN
sleep 0.5
fi
else
SETTLE=6
fi
fi

IDX=$NEWIDX
done
</pre>

Code/fan-enable-extended

2025-04-11T07:23:59Z

ThinkGNU: Script in <pre> block

<pre>
#!/bin/sh

# fan control-script
#
# based upon ibm-acpi 0.11 (experimental=1 !)
#
# eliminates anoying "fan always on" in battery mode
# works with hysteresis (DELTA) so that always-turn-on/turn-off is avoided
# fan acivates at MAXTEMP and cools down CPU, GPU etc. to MAXTEMP-DELTA than the fan is turned off
# furthermore detects if AC is on and gives back fan control to default behaviour than
#
# one can change MAXTEMP and DELTA to individual values
# but take care of your THINKPAD don`t melt it!
#
# have fun!
# mk 05.05.05

MAXTEMP=51
DELTA=4

SWITCHTEMP=$MAXTEMP

#make sure the script doesn't leave the fan off on error
trap "echo enable > /proc/acpi/ibm/fan" EXIT

while [ 1 ];
do
for ac in `sed s/state:// < /proc/acpi/ac_adapter/AC/state`
do
if [ "$ac" = "off-line" ]; then
fan=no
for temp in `sed s/temperatures:// < /proc/acpi/ibm/thermal`
do
test $temp -gt $SWITCHTEMP && fan=yes
done

if [ "$fan" = "yes" ]; then
command='enable'
SWITCHTEMP=`expr $MAXTEMP - $DELTA`
else
SWITCHTEMP=$MAXTEMP
command='disable'
fi
else # ac-adapter on -> set fan control to standard behaviour
command='enable'
fi

echo $command > /proc/acpi/ibm/fan
sleep 15
done
done
</pre>

Code/fan-enable-basic

2025-04-11T07:23:40Z

ThinkGNU: Script in <pre> block

<pre>
#!/bin/sh

MAXTEMP=50

while [ 1 ];
do
fan=no

for temp in `sed s/temperatures:// < /proc/acpi/ibm/thermal`
do
test $temp -gt $MAXTEMP && fan=yes
done

command='disable'
test "$fan" = "yes" && command='enable'
echo $command > /proc/acpi/ibm/fan

sleep 20
done
</pre>

Code/fan-enable-safe

2025-04-11T07:23:16Z

ThinkGNU: Script in <pre> block. Why is it proprietary?

<pre>
#!/bin/sh

# july 2005 Erik Groeneveld, erik@cq2.nl
# It makes sure the fan is on in case of errors
# and only turns it off when all temps are ok.

IBM_ACPI=/proc/acpi/ibm
THERMOMETER=$IBM_ACPI/thermal
FAN=$IBM_ACPI/fan
MAXTRIPPOINT=65
MINTRIPPOINT=60
TRIPPOINT=$MINTRIPPOINT

echo fancontrol: Thermometer: $THERMOMETER, Fan: $FAN
echo fancontrol: Current `cat $THERMOMETER`
echo fancontrol: Controlling temperatures between $MINTRIPPOINT and $MAXTRIPPOINT degrees.

# Make sure the fan is turned on when the script crashes or is killed
trap "echo enable > $FAN; exit 0" HUP KILL INT ABRT STOP QUIT SEGV TERM

while [ 1 ];
do
command=enable
temperatures=`sed s/temperatures:// < $THERMOMETER`
result=
for temp in $temperatures
do
test $temp -le $TRIPPOINT && result=$result.Ok
done
if [ "$result" = ".Ok.Ok.Ok.Ok.Ok.Ok.Ok.Ok" ]; then
command=disable
TRIPPOINT=$MAXTRIPPOINT
else
command=enable
TRIPPOINT=$MINTRIPPOINT
fi
echo $command > $FAN
# Temperature ramps up quickly, so pick this not too large:
sleep 5
done
</pre>

Code/fan-enable.init

2025-04-11T07:21:50Z

ThinkGNU: Script in pre block

<pre>
#!/bin/sh

N=/etc/init.d/fan

set -e

case "$1" in
start)
# make sure privileges don't persist across reboots
if [ -d /var/run/fan ] && [ "x`ls /var/run/fan`" != x ]
then
touch -t 198501010000 /var/run/fan/*
fi
fan.sh & # Script from above
;;
stop|reload|restart|force-reload)
killall fan.sh
echo enable > /proc/acpi/ibm/fan
;;
*)
echo "Usage: $N {start|stop|restart|force-reload}" >&2
exit 1
;;
esac

exit 0
</pre>

Code/ibm-fancontrol.init

2025-04-11T07:21:24Z

ThinkGNU: Everything in a pre block. GPLv2-only? Sad!

<pre>
#!/sbin/runscript
# 2005 Gilbert Tiefengruber
# Distributed under the terms of the GNU General Public License v2
# IBM Fancontrol init script for IBM Thinkpad laptops (tested with R50)
# This init script was written for gentoo 2005.1, kernel 2.6.12
# You need the ibm_acpi kernel module version 0.11 or greater
# load the module with experimental=1 to enable the fan controls

depend() {
need localmount
}
checkconfig() {
if [ ! -e /proc/acpi/ibm/fan ]; then
eerror "The ibm_acpi module must be loaded with (experimental=1)"
return 1
fi
}
start() {
checkconfig || return 1
ebegin "Starting ibm-fancontrold"
start-stop-daemon --quiet -p /var/run/ibm-fancontrold.pid -m -b --start -a /usr/sbin/ibm-fancontrold
eend ${?}
}
stop() {
ebegin "Stopping ibm-fancontrold"
start-stop-daemon --stop --quiet -p /var/run/ibm-fancontrold.pid
eend ${?}
}
</pre>

Code/ibm-acpi-0.11-2.6.13-fan.patch

2025-04-11T07:20:41Z

ThinkGNU: Everything in a pre block so it's readable.

<pre>
--- ibm-acpi-0.11-orig/ibm_acpi.c 2005-03-17 12:06:16.000000000 +0200
+++ ibm-acpi-0.11/ibm_acpi.c 2005-10-26 06:21:57.000000000 +0200
@@ -1488,11 +1488,18 @@ static int fan_read(char *p)
} else {
/* all except 570, 600e/x, 770e, 770x */
if (!acpi_ec_read(fan_status_offset, &status))
len += sprintf(p + len, "status:\t\tunreadable\n");
- else
+ else {
len += sprintf(p + len, "status:\t\t%s\n",
- enabled(status, 7));
+ status ? "enabled" : "disabled");
+ if (status & 0x40)
+ len += sprintf(p + len, "level:\t\tdisengaged\n");
+ else if (status & 0x80)
+ len += sprintf(p + len, "level:\t\tauto\n");
+ else
+ len += sprintf(p + len, "level:\t\t%d\n", status);
+ }

if (!acpi_ec_read(fan_rpm_offset, &lo) ||
!acpi_ec_read(fan_rpm_offset + 1, &hi))
len += sprintf(p + len, "speed:\t\tunreadable\n");
@@ -1506,9 +1513,12 @@ static int fan_read(char *p)
len += sprintf(p + len, "commands:\tlevel <level>"
" (<level> is 0-7)\n");
if (!gfan_handle)
/* all except 570, 600e/x, 770e, 770x */
- len += sprintf(p + len, "commands:\tenable, disable\n");
+ len += sprintf(p + len,
+ "commands:\tenable, disable, level <level>\n"
+ " \t(<level> is 0-7, auto"
+ "or disengaged)\n");
if (fans_handle)
/* X31, X40 */
len += sprintf(p + len, "commands:\tspeed <speed>"
" (<speed> is 0-65535)\n");
@@ -1528,17 +1538,29 @@ static int fan_write(char *buf)
/* 570, 770x-JL */
if (!acpi_evalf(sfan_handle, NULL, NULL, "vd", level))
return -EIO;
} else if (!gfan_handle &&
- strlencmp(cmd, "enable") == 0) {
+ ( (strlencmp(cmd, "enable") == 0) ||
+ (strlencmp(cmd, "level auto") == 0) ) ) {
/* all except 570, 600e/x, 770e, 770x */
if (!acpi_ec_write(fan_status_offset, 0x80))
return -EIO;
} else if (!gfan_handle &&
strlencmp(cmd, "disable") == 0) {
/* all except 570, 600e/x, 770e, 770x */
if (!acpi_ec_write(fan_status_offset, 0x00))
return -EIO;
+ } else if (!gfan_handle &&
+ strlencmp(cmd, "level disengaged") == 0) {
+ /* all except 570, 600e/x, 770e, 770x */
+ if (!acpi_ec_write(fan_status_offset, 0x40))
+ return -EIO;
+ } else if (!gfan_handle &&
+ sscanf(cmd, "level %d", &level) == 1 &&
+ level >=0 && level <= 7) {
+ /* all except 570, 600e/x, 770e, 770x */
+ if (!acpi_ec_write(fan_status_offset, level))
+ return -EIO;
} else if (fans_handle &&
sscanf(cmd, "speed %d", &speed) == 1 &&
speed >= 0 && speed <= 65535) {
/* X31, X40 */
@@ -1751,9 +1773,9 @@ static int __init setup_notify(struct ib

return 0;
}

-static int device_add(struct acpi_device *device)
+static int ibmacpi_device_add(struct acpi_device *device)
{
return 0;
}

@@ -1769,9 +1791,9 @@ static int __init register_driver(struct

memset(ibm->driver, 0, sizeof(struct acpi_driver));
sprintf(ibm->driver->name, "%s/%s", IBM_NAME, ibm->name);
ibm->driver->ids = ibm->hid;
- ibm->driver->ops.add = &device_add;
+ ibm->driver->ops.add = &ibmacpi_device_add;

ret = acpi_bus_register_driver(ibm->driver);
if (ret < 0) {
printk(IBM_ERR "acpi_bus_register_driver(%s) failed: %d\n",
</pre>

Code/tp-theft-basic

2025-04-11T07:19:28Z

ThinkGNU: Put everything in a pre block, so that script is readable.

<pre>
#!/usr/bin/perl
# tp-theft v0.1 (http://thinkwiki.org/wiki/Script_for_theft_alarm_using_HDAPS)
# This script uses the HDAPS accelerometer found on recent ThinkPad models
# to emit an audio alarm when the laptop is tilted. In sufficiently
# populated environments, it can be used as a laptop theft deterrent.
#
# This file is placed in the public domain and may be freely distributed.

use strict;
use warnings;

##############################
# Siren volume and content

# Audio volume (0..100)
my $volume = 70;

# Synthesize a siren for 1.0 seconds:
my $play_cmd = "sox -t nul /dev/null -t ossdsp /dev/dsp synth 1.0 sine 2000-4000 sine 4000-2000";

# Play a file:
# my $play_cmd = "play keep_your_hands_off_me.wav";

##############################
# Other tweakables

my $thresh = 0.20; # tilt threshold (increase value to decrease sensitivity)
my $interval = 0.1; # sampling interval in seconds
my $depth = 10; # number of recent samples to analyze
my $pos_file='/sys/devices/platform/hdaps/position';
my $verbose = 1;

##############################
# Code

sub get_pos {
open(POS,"<",$pos_file) or die "Can't open HDAPS file $pos_file: $!\n";
$_=<POS>;
m/^$(-?\d+),(-?\d+)$$/ or die "Can't parse $pos_file content\n";
return ($1,$2);
}

sub stddev {
my $sum=0;
my $sumsq=0;
my $n=$#_+1;
for my $v (@_) {
$sum += $v;
$sumsq += $v*$v;
}
return sqrt($n*$sumsq - $sum*$sum)/($n*($n-1));
}

my (@XHIST, @YHIST);
my ($x,$y) = get_pos;
for (1..$depth) {
push(@XHIST,$x);
push(@YHIST,$y);
}
my $alarm_file; # flags ongoing alarm (and stores saved mixer settings)

while (1) {
my ($x,$y) = get_pos;
shift(@XHIST); push(@XHIST,$x);
shift(@YHIST); push(@YHIST,$y);
my $xdev = stddev(@XHIST);
my $ydev = stddev(@YHIST);

# Print variance and history
print "X: v=$xdev (".join(',',@XHIST).") Y: v=$ydev (".join(",",@YHIST).")\n" if $verbose>1;

my $tilted = $xdev>$thresh || $ydev>$thresh;

if ($tilted && !(defined($alarm_file) && -f $alarm_file)) {
print "ALARM\n" if $verbose>0;
$alarm_file = `mktemp /tmp/hdaps-tilt.XXXXXXXX` or die "mktemp: $?";
chomp($alarm_file);
system('/bin/bash', '-c', <<"EOF")==0 or die "Failed: $?";
( trap \"aumix -L -f $alarm_file > /dev/null; rm -f $alarm_file" EXIT HUP QUIT TERM
aumix -S -f $alarm_file &&
aumix -v $volume -w 100 &&
$play_cmd) &
EOF
}

select(undef, undef, undef, $interval); # sleep
}
</pre>

Lenovo Security Suite

2025-04-11T07:15:30Z

ThinkGNU: It appears there was never a screenshot available, so remove that section.

==Description==

===Software Requirements===

* Windows 7 - 32 and 64 bits

===Hardware Requirements===

==Download==
* Windows 7 - Version 2.0.13.0 [http://support.lenovo.com/ec/en/downloads/ds018434]

[[Category:Software]]
[[Category:Windows 7 Lenovo Software]]

Installing openSuSE 10.3 on a ThinkPad X61

2025-04-11T07:11:56Z

ThinkGNU: Linux is not an OS like windows, it is a kernel.

This article describes installation of openSUSE 10.3 on a ThinkPad X61 performed in February 2008.

(This is english translation of a [http://www.abclinuxu.cz/blog/linux/2008/3/lenovo-thinkpad-x61-3-instalace-opensuse-10.3 czech blogpost] originally published on [http://www.abclinuxu.cz Abclinuxu.cz])
== Hardware configuration ==
* Lenovo ThinkPad {{X61}} [http://www-307.ibm.com/pc/support/site.wss/product.do?template=/product.do?template=%2Fproductpage%2Flandingpages%2FproductPageLandingPage.vm&sitestyle=lenovo&brandind=10&familyind=374625&machineind=374632&modelind=375122&partnumberind=0&subcategoryind=0&doctypeind=100&doccategoryind=0&operatingsystemind=49979&validate=true 7675-7KU]
* Intel [[Intel_Core_2_Duo_(Merom)|Core 2 Duo]] T7300 2.0GHz CPU
* 4 GiB DDR2 667 MHz RAM
* 12.1" 1024x768 TN LCD
* Intel [http://en.wikipedia.org/wiki/Intel_GMA#GMA_X3100 GMA X3100] graphics
* Hitachi 120 GB 5400 RPM SATA HDD
* [[AD1984|AD1984 HD Audio 1.0]] aka Intel HD Audio integrated soundcard
* Intel [http://www.intel.com/design/network/products/lan/controllers/82566.htm 82566 Gigabit Ethernet] (Intel PRO/1000)
* Intel [[Intel_PRO/Wireless_4965AGN_Mini-PCI_Express_Adapter|Wireless WiFi Link 4965AGN]]
* [[ThinkPad_Bluetooth_with_Enhanced_Data_Rate_(BDC-2)|Bluetooth 2.0 EDR]]
* SGS Thomson [[Integrated_Fingerprint_Reader|fingerprint reader]]
* 8-cell 5.2 Ah Li-Ion battery
* [[UltraBase X6]] docking station with a DVD-RAM/R/RW drive

{{cmdroot|lspci}}
<pre>00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network Connection (rev 03)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Contoller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation 82801HBM (ICH8M-E) LPC Interface Controller (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03)
02:00.0 Memory controller: Intel Corporation Turbo Memory Controller (rev 01)
03:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61)
05:00.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba)
05:00.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04)</pre>

{{cmdroot|hwinfo --short}}
<pre>cpu:
Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz, 2000 MHz
Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz, 2000 MHz
keyboard:
/dev/input/event0 AT Translated Set 2 keyboard
mouse:
/dev/input/mice TPPS/2 IBM TrackPoint
monitor:
Generic Monitor
graphics card:
Lenovo 965 GM
Lenovo Mobile GM965/GL960 Integrated Graphics Controller
sound:
Lenovo Thinkpad T61
storage:
Lenovo 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller
Lenovo 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller
network:
eth0 Lenovo 82566MM Gigabit Network Connection
wlan0 Intel Lenovo Thinkpad T61
network interface:
lo Loopback network interface
eth0 Ethernet network interface
wmaster0 Network Interface
wlan0 WLAN network interface
disk:
/dev/sda SAMSUNG HM250JI (the original Toshiba has been replaced)
partition:
/dev/sda1 Partition
/dev/sda2 Partition
/dev/sda3 Partition
cdrom:
/dev/sr0 HL-DT-ST DVDRAM GSA-U10N
usb controller:
Lenovo Thinkpad T61
Lenovo Thinkpad T60
Lenovo Thinkpad T61
Lenovo 82801H (ICH8 Family) USB UHCI Controller #1
Lenovo 82801H (ICH8 Family) USB UHCI Controller #2
Lenovo 82801H (ICH8 Family) USB2 EHCI Controller #1
bios:
BIOS
bridge:
Lenovo Mobile PM965/GM965/GL960 Memory Controller Hub
Intel 82801H (ICH8 Family) PCI Express Port 1
Intel 82801H (ICH8 Family) PCI Express Port 2
Intel 82801 Mobile PCI Bridge
Lenovo 82801HBM (ICH8M-E) LPC Interface Controller
Lenovo RL5c476 II
hub:
Linux 2.6.22.17-0.1-default uhci_hcd UHCI Host Controller
Linux 2.6.22.17-0.1-default uhci_hcd UHCI Host Controller
Linux 2.6.22.17-0.1-default ehci_hcd EHCI Host Controller
Linux 2.6.22.17-0.1-default ehci_hcd EHCI Host Controller
Linux 2.6.22.17-0.1-default uhci_hcd UHCI Host Controller
Linux 2.6.22.17-0.1-default uhci_hcd UHCI Host Controller
memory:
Main Memory
firewire controller:
Lenovo R5C832 IEEE 1394 Controller
bluetooth:
Broadcom BCM2045B
unknown:
FPU
DMA controller
PIC
Timer
RTC
Keyboard controller
PS/2 Controller
Lenovo 82801H (ICH8 Family) SMBus Controller
Intel Turbo Memory Controller
Lenovo R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter</pre>

{{cmdroot|cat /proc/cpuinfo}}
<pre>processor : 0 [the second core says '1']
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz
stepping : 10
cpu MHz : 2001.000
cache size : 4096 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm constant_tsc
pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr lahf_lm
bogomips : 3994.33
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:</pre>

== {{OpenSUSE}}: What does and what doesn't work ==
The following list is applicable to a openSUSE-patched kernel 2.6.22.17-0.1.
=== Working HW ===
* (+) CPU frequency changing
* (+) graphical interface (X.org) including brightness setting
* (-) save to RAM (needs small fix to get working) and save to disk (works)
* (-) docking station
* (+) DVD burner in the UltraBay slot (hotplug not tested)
* (+) USB 2.0
* (+) wired Ethernet
* (+) wireless Ethernet, with some minor problems
* (+) sound (hda_intel) -- modem needs to be enabled in BIOS
* (-) Fn keyboard shortcuts
* (+) Bluetooth (including indication LED)
* (+) TrackPoint
* (+) Firewire
* (+) Cardbus slot
* (+) fingerprint reader (with ThinkFinger, KDM & KScreensaver is unusable)
* (+) SD card reader
* (+) serial and parallel port on the docking station
* (+) wireless killswitch
* (-) other power management functions

=== Not working/not tested HW ===
* (N/T) winmodem ([http://gentoo-wiki.com/HOWTO_slmodem should work with slmodem driver])
* (N/T, don't have) WWAN modem (GrmlWiki says [http://wiki.grml.org/doku.php?id=lenovo_x61s#wan at least one version is supported])
* (N/W) [[HDAPS|Lenovo Harddrive Active Protection System]] (missing support in the openSUSE kernel)
* (N/T, don't have) [http://en.wikipedia.org/wiki/Turbo_Memory Intel Turbo Memory] (the driver doesn't exist; maybe it works as a drive cache => no driver needed)
* (N/T) [http://en.wikipedia.org/wiki/Trusted_Platform_Module Trusted Platform Module] (supported by the [[Tpmdd|Linux TPM Driver]], in kernel since version 2.6.10)
{{HINT|(+) sign means that the HW works right out of the box, (-) that the HW needs some (mostly simple) configuration, was not tested (N/T) or doesn't work at all (N/W).}}
== X.Org configuration ==
The following configuration reflects Clone setting with Samsung 245B, a low-end WUXGA (1920x1200) TN LCD using <code>intel</code> driver from X.org connected via VGA. If you're not planning to use external display, you can use the default <code>xorg.conf</code> generated by SaX during installation, it just works (TM) ;-)

{{path|/etc/X11/xorg.conf}} (display settings part)
<pre>Section "Monitor"
DisplaySize 518 323
HorizSync 30-81
Identifier "ExternalLCD"
ModelName "SyncMaster 245B"
Option "DPMS"
VendorName "Samsung"
VertRefresh 60-75
Modeline "1920x1200" 154.00 1920 1968 2000 2080 1200 1203 1209 1235
Option "DPI" "96x96"
EndSection

Section "Monitor"
DisplaySize 245 184
HorizSync 30-81
Identifier "InternalLCD"
ModelName "ThinkPad LCD 1024x768"
Option "DPMS"
VendorName "Lenovo"
VertRefresh 60-75
Modeline "1024x768" 69.71 1024 1080 1184 1344 768 769 772 798
Modeline "800x600" 48.91 800 840 920 1040 600 601 604 627
Modeline "640x480" 24.70 640 656 720 800 480 481 484 498
EndSection

Section "Screen"
DefaultDepth 24
SubSection "Display"
ViewPort 0 0
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
ViewPort 0 0
Depth 24
Modes "1024x768" "800x600" "640x480"
EndSubSection
Device "Device0"
Identifier "InternalScreen"
Monitor "InternalLCD"
EndSection

Section "Screen"
DefaultDepth 24
SubSection "Display"
ViewPort 0 0
Depth 16
Modes "1920x1200" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
ViewPort 0 0
Depth 24
Modes "1920x1200" "1024x768" "800x600" "640x480"
EndSubSection
Device "Device1"
Identifier "ExternalScreen"
Monitor "ExternalLCD"
EndSection</pre>
This screen configuration requires two graphic adapters. One physical and the second virtual. Configuration excerpt follows:
<pre>Section "Device"
BoardName "X3100"
Driver "intel"
Identifier "Device0"
Screen 0
Option "MonitorLayout" "CRT,LFP"
Option "MetaModes" "1920x1200,1024x768"
VendorName "Intel"
Option "FramebufferCompression" "on"
#Option "AccelMethod" "exa"
EndSection

Section "Device"
BoardName "X3100"
Driver "intel"
Identifier "Device1"
Screen 1
Option "MonitorLayout" "CRT,LFP"
VendorName "Intel"
EndSection</pre>
You can also download the whole [http://akela.mendelu.cz/~xgrmela1/recenze-x61/files/xorg.conf xorg.conf]. Setting X.org with this configuration causes some problem to Mplayer, you need to add <code>xineramascreen=0</code> to your Mplayer config. The other problem is that my KDE seems no to accept screen size reported by the second LCD. Therefore, the DPI is set too low and fonts are '''huge'''. This could be solved (at least in KDE) by setting force 96x96 DPI in KDE Control center (Fonts setttings).

{{NOTE|The 3D output using this configuration is pretty slow, for example the Tuxracer is hardly playable. When the external display is disconnected, it runs perfectly}}

=== Screen brightness & flickering problem ===
You maybe heard about the brightness problem on recent Lenovo machines. The problems are mainly cause by a different count of supported brightness levels what causes the screen to be too dark. This is solved in recent <code>thinkpad_acpi</code> kernel module, the openSUSE kernel includes this fix. The other problem is a [[Problem_with_display_remaining_black_after_resume|blank screen after resume from suspend to RAM]], however this could be fixed easily by changing <code>s2ram</code> configuration.

Some users report screen flickering when changing brightness. This is caused by the way X.org changes brightness level, on a recent X, you should be able to solve this by calling {{cmduser|xrandr --output LVDS --set BACKLIGHT_CONTROL native}}.
{{NOTE|OpenSUSE 10.3 uses probably too old X.Org for this command to work, exits <code>X Error of failed request: BadName (named color or font does not exist)</code>}}.

The older BIOSes had a bug which not only affected Windows but GNU/Linux too. The laptop had, when resumed from suspend to ram, turned the backlight at maximum. Installing [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-67983 newer BIOSes] from Lenovo's site solves this. The newer BIOSes also solve weird USB interrupt bug which looks in <code>dmesg</code> like this:
<pre>irq 21: nobody cared (try booting with the "irqpoll" option)
[<c014e3b6>] __report_bad_irq+0x36/0x75
[<c014e5d0>] note_interrupt+0x1db/0x217
[<f885fa1e>] usb_hcd_irq+0x21/0x4e [usbcore]
[<c014dadd>] handle_IRQ_event+0x23/0x51
[<c014ed3d>] handle_fasteoi_irq+0x86/0xa6
[<c0106552>] do_IRQ+0x55/0x6f
[<c0127fa0>] irq_exit+0x53/0x6b
[<c0115d1b>] smp_apic_timer_interrupt+0x71/0x7d
[<c010487b>] common_interrupt+0x23/0x28
=======================
handlers:
[<f885f9fd>] (usb_hcd_irq+0x0/0x4e [usbcore])
Disabling IRQ #21</pre>

== Suspend ==
=== Save to disk ===
Save to disk works perfectly out-of-box. You only need to have enough swap (i've got 4 gigs of RAM and 1 gig of swap...thought it should't, it works :-))

=== Save to RAM ===
Save to RAM doesn't work right out-of-the-box, [http://en.opensuse.org/Projects_KPowersave KPowersave] when asked to suspend the PC, reports an error. The problem is in the way [http://en.opensuse.org/S2ram S2ram] works. The developers maitain [http://suspend.cvs.sourceforge.net/suspend/suspend/whitelist.c?view=markup a whitelist] with needed switches for the exact machine (or event it's model) and my ThinkPad was not listed. I've reported it and now, models 7673, 7674 and 7675 are present in the whitelist (= no need to edit anything, it should just work).

When your model is not listed, you can try launching the <code>s2ram</code> with -f (force) switch, it will ignore the whitelist. 61-series ThinkPads with 64-bit are supposed to be suspended with <code>-a 3</code> parameter (<code>acpi_sleep</code> + <code>s3_mode</code>), the whole command will look like this:
{{cmdroot|s2ram -f -a 3}}

{{HINT|When you got Suspend to RAM working on you laptop, [http://en.opensuse.org/S2ram#How_to_contact_the_authors_of_s2ram.3F let the developers know] so they can add your model to the whitelist.}}

When you try it and the laptop seems to resume from sleep fine, you can edit {{path|/etc/pm/config.d/sleep}} to tell the S2ram, how it should suspend your particulral laptop.
<pre># cat /etc/pm/config.d/sleep
S2RAM_OPTS="-f -a 3"</pre>
You can also use the <code>SUSPEND_MODULES="<module names>"</code> option to set which modules should be unloaded before suspend. This was not needed on my configuration.

After this, the suspend to RAM will work from utilities like KPowersave. When using docking station, it is useful to disable suspend based on lid closing. The laptop consumes about 160 mW of power when in suspend state.

== Trackpoint ==
The configuration is described in [[Trackpoint]] site, here on ThinkWiki. My own configuration follows:
<pre>:
:
Section "InputDevice"
Driver "mouse"
Identifier "Mouse[1]"
Option "Buttons" "11"
Option "Device" "/dev/input/mice"
Option "Name" "ThinkPad Trackpoint"
Option "Protocol" "explorerps/2"
Option "Vendor" "Lenovo"
Option "EmulateWheel" "on"
Option "EmulateWheelTimeOut" "200"
Option "EmulateWheelButton" "2"
Option "YAxisMapping" "4 5"
Option "XAxisMapping" "6 7"
Option "ZAxisMapping" "4 5"
EndSection
:
:
Section "ServerLayout"
InputDevice "Mouse[1]" "CorePointer"
EndSection
:
:</pre>
The wheel emulation works fine, but it has problem with some web browsers (probably fixable by disabling the middle button in the browser). The press-to-select ({{cmdroot|echo -n 1 > /sys/devices/platform/i8042/serio1/press_to_select}}) feature works also fine but requires more power for the mouse to generate click than the regular touchpad.

== Sound ==
The computer includes a integrated soundcard, Intel High Definition Audio, particularly Analog Device 82801H chip. This soundcard could be used with AD1984 driver included in ALSA 1.0.15 (Linux 2.6.23). Thought openSUSE 10.3 only includes ALSA 1.0.14, the sound does work (ALSA is probably patched) out of box.

{{NOTE|The winmodem must be enabled in BIOS for soundcard to work}}

Internal mic does work, you're only required to set Internal Mic volume in some sound utility (like <code>alsamixer</code>).

== SD card reader ==
SD/SDHC/SDIO card reader works out-of-box including indication LED. It's [[SD_Card_slot|Ricoh Co Ltd R5C822]] reader and it's connected to the PCI bus. The reader is supported by the <code>sdhci</code> module from kernel 2.6.17-rc1 what means that openSUSE 10.3 supports it. The sequential read speed it about 3.5 MiB/s, nothing special.

== CardBus slot ==
Nearby the SD card reader, the Cardbus slot could be found. Lenovo declares that it should support even the ExpressCard cards using an adapter (but this is gonna be probably some kind of emulation). Regardless of the ExpressCard support, it runs 32-bit CardBus and older 16-bit PCMCIA cards fine.

== Wired Ethernet ==
The laptop has a quite common gigabit Ethernet adapter Intel 82566MM, better known as Intel PRO/1000 Gigabit Ethernet. The <code>e1000</code> driver is in the kernel, network connection works out-of-box.

== Wireless Ethernet ==
The wireless Ethernet adapter Intel Wireless WiFi Link 4965ANG works immediately with kernel module <code>iwlwifi</code> after installation but the problem is the openSUSE driver is too old. After Online Update, the installed version is 1.1.10 which works pretty good [http://bughost.org/bugzilla/show_bug.cgi?id=1581 unless your're planning to use WPA Enterprise authentication] (EAP-TLS, EAP-TTLS). This is solved in the latest GIT unstable versions (no stable version works fine). Refer to the [http://intellinuxwireless.org/?p=iwlwifi Intel site] for more info how to get the newest code.

{{HINT|Some users choose to replace the Intel WiFi card with Atheros one, distributed as [[ThinkPad 11a/b/g Wireless LAN Mini Express Adapter]]. The <code>madwifi</code> seems to be more stable and since the Atheros adapter is distributed by Lenovo, there are no [[Problem_with_unauthorized_MiniPCI_network_card|problems with unathorized MiniPCI network card]]}}

The [http://bughost.org/bugzilla/show_bug.cgi?id=1209 LED indicatior does work] in kernels after 2.6.24.

I've tested the adapter even with the [http://ndiswrapper.sourceforge.net/joomla/ NDISwrapper] but with no usable result. Because i've got 64-bit kernel, i've got to use 64-bit Windows drivers. Sadly, when the drivers are installed, the NDISwrapper crashes with a SEGFAULT.

== Bluetooth ==
Lenovo used the Bluetooth adapter BCM2045B made by Broadcom and connected to the USB bus. The hardware is correctly recognized, no configuration is required. The {{key|Fn}}{{key|F5}} keyboard shortcut doesn't work out of box but you can enable it using script on page [[ThinkPad Bluetooth with Enhanced Data Rate (BDC-2)]].

== Fingerprint reader ==
The [[Integrated_Fingerprint_Reader|fingerprint reader]] (made by SGS Thomson Microelectronics) works out of box and could be even [http://en.opensuse.org/Using_Fingerprint_Authentication configured in YasT]. You only need to set the fingerprints in every user account that will be using this device. After that, you can login using your fingers :-)

How easy and working this seems to be, the truth is that you cannot use KDM to login and KScreensaver (resp. <code>kdesktop_lock</code>) to lock your desktop. The KDM just don't know you have some fingerprint reader and the KScreensaver crashes and needs to be killed from the terminal. Also, the KDE password dialogs (<code>kdesu</code>) don't know how to use the fingerprint reader. Fingerpint works correctly when used from console. There is already a [http://bugs.kde.org/show_bug.cgi?id=116682 KDE bug] filled at the Bugzilla.

{{HINT|You can use GDM instead of KDM to be able to login using fingerprint reader}}

The alternative binary driver [http://www.upek.com/support/dl_linux_bsp.asp <code>bioapi</code>] seems to solve all the problems but it's installation is [[How_to_enable_the_integrated_fingerprint_reader_with_BioAPI|a bit complicated]].

You can also use [[How to enable the integrated fingerprint reader with fprint|fprint]].

== ACPI -- hotkeys ==
(HW) does mean that the key works independently on the operating system installed. Some (for example {{key|Fn}}{{key|F4}}) are captured by the KPowersave utility.
=== Working keys ===
These keys work automatically out-of-box, after installation.
* {{key|Fn}}{{key|F2}} lock screen (ACPI -- <code>ibm/hotkey HKEY 00000080 00001002</code>)
* {{key|Fn}}{{key|F4}} save to RAM (ACPI -- <code>ibm/hotkey HKEY 00000080 00001004</code>)
* {{key|Fn}}{{key|F12}} save to disk (ACPI -- <code>ibm/hotkey HKEY 00000080 0000100c</code>)
* {{key|Fn}}{{key|PgUp}} enable display LED ([[ThinkLight]]) (ACPI -- <code>ibm/hotkey HKEY 00000080 00001012</code>, HW)
* {{key|Volume Up}} turn Volume Up (HW)
* {{key|Volume Down}} turn Volume Down (HW)
* {{key|Disable sound}} disable sound (X11 -- <code>XF86AudioMute</code>, HW)
{{NOTE|The sound needs to be enabled after installation using Volume Up key, the software mixer is not enough}}

=== Working, but not assigned keys ===
These keys are working but aren't assignet to any application. The ACPI keycodes could be caputured using <code>acpid</code>, the X11 keycodes could be used in some application as keyboard shortcuts.
* {{key|Fn}}{{key|F8}} (ACPI -- <code>ibm/hotkey HKEY 00000080 00001008</code>)
* {{key|Fn}}{{key|F9}} (ACPI -- <code>ibm/hotkey HKEY 00000080 00001009</code>)
* {{key|Fn}}{{key|Up}} stop playback (X11 -- <code>XF86AudioStop</code>)
* {{key|Fn}}{{key|Down}} start playback / pause (X11 -- <code>XF86AudioPlay</code>)
* {{key|Fn}}{{key|Left}} previous track (X11 -- <code>XF86AudioPrev</code>)
* {{key|Fn}}{{key|Right}} next track (X11 -- <code>XF86AudioNext</code>)
* {{key|Page right}} page left (X11 -- <code>XF86Back</code>)
* {{key|Page left}} page right (X11 -- <code>XF86Forward</code>)
* {{key|Fn}}{{key|Home}} backlight up (ACPI -- <code>ibm/hotkey HKEY 00000080 00001010</code>)
* {{key|Fn}}{{key|End}} backlight down (ACPI -- <code>ibm/hotkey HKEY 00000080 00001011</code>)
* {{ibmkey|ThinkVantage|#495988}} (ACPI -- <code>ibm/hotkey HKEY 00000080 00001018</code>)
* {{key|Fn}}{{key|F1}} (ACPI -- <code>ibm/hotkey HKEY 00000080 00001001</code>)
* {{key|Fn}}{{key|F3}} (ACPI -- <code>ibm/hotkey HKEY 00000080 00001003</code>)
* {{key|Fn}}{{key|F5}} (ACPI -- <code>ibm/hotkey HKEY 00000080 00001005</code>)
* {{key|Fn}}{{key|F6}} (ACPI -- <code>ibm/hotkey HKEY 00000080 00001006</code>)
* {{key|Fn}}{{key|F7}} (ACPI -- <code>ibm/hotkey HKEY 00000080 00001007</code>)
* {{key|Fn}}{{key|F8}} (ACPI -- <code>ibm/hotkey HKEY 00000080 00001008</code>)
* {{key|Fn}}{{key|F9}} (ACPI -- <code>ibm/hotkey HKEY 00000080 00001009</code>)
* {{key|Fn}}{{key|F10}} (ACPI -- <code>ibm/hotkey HKEY 00000080 0000100a</code>)
* {{key|Fn}}{{key|F11}} (ACPI -- <code>ibm/hotkey HKEY 00000080 0000100b</code>)

The {{key|Fn}}{{key|Home}} and {{key|Fn}}{{key|End}} keys should work again without the need to configure them in kernel 2.6.24 using <code>thinkpad_acpi</code> 0.18.

== Docking station ==
This particlar model is shipped with a [[UltraBase X6]] docking station. The dock works mostly out of box, but it needs to be configured to work perfectly (eg. automatically change screen resolution after docking). OpenSUSE has a utility set called [http://en.opensuse.org/Dockutils Dockutils] which handles the docking process. If you want to get you dock working better, please see the [[UltraBase X6]] article.

== Power management ==
The CPU frequency scaling works automatically after installation and could be set using KPowersave or sys filesystem (more on this in [[How to make use of Dynamic Frequency Scaling]]).

The [http://www.lesswatts.org/ LessWatts.org] gives some examples, how one can make the laptop even more power-saving. I use the follwing combination of settings:

{{cmdroot|cat /etc/rc.d/boot.local}}
<pre>#! /bin/sh

# Linux Powersave
# scheduler power savings
echo 1 > /sys/devices/system/cpu/sched_mc_power_savings

# power on the WiFi adapter
echo 5 > /sys/bus/pci/drivers/iwl4965/0000\:03\:00.0/power_level

# HDD power management, sleep after 5 mins
hdparm -B128 -S60 /dev/sda > /dev/null

# HDD writebacks after 5 mins
echo 3000 > /proc/sys/vm/dirty_writeback_centisecs

# HDD I/O grouping
echo 5 > /proc/sys/vm/laptop_mode

# disable Wake On LAN
ethtool -s eth0 wol d</pre>

The following configuration results in:
* brightness 44%, Bluetooth + WiFi enabled, CPU in Powersave mode: 14.6 W ([http://www.lesswatts.org/projects/powertop/ PowerTOP] long-term 13.2 W)
* brightness 44%, Bluetooth + WiFi disabled, CPU in Powersave mode: 12.4 W
* brightness 44%, Bluetooth + WiFi disabled, CPU in Powersave mode, [[ACPI_fan_control_script|fan disabled]]: 11.2 W
{{HINT|More power savings could be achieved using tickless kernel and various SATA, ACPI and USB patches. Intel says that it could save up to 2 watts more.}}

== Used files list ==
* [http://akela.mendelu.cz/~xgrmela1/recenze-x61/files/xorg.conf /etc/X11/xorg.conf]
* [http://akela.mendelu.cz/~xgrmela1/recenze-x61/files/sleep /etc/pm/config.d/sleep]
* [http://akela.mendelu.cz/~xgrmela1/recenze-x61/files/10x61 /etc/X11/xinit/xinitrc.d/10x61]
* [http://akela.mendelu.cz/~xgrmela1/recenze-x61/files/boot.local /etc/rc.d/boot.local]

CT-65550

2025-04-11T07:09:15Z

ThinkGNU: X.Org is not Linux. Linux's terminal emulator is fbcon.

__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;">
=== CT-65550 ===
This is a Chips and Technologies video adapter

=== Features ===
* Chipset: CT HiQV
* PCI ID: 102c:00e0
* 1MB EDO DRAM
* Interface: PCI 2.1
</div>
|style="vertical-align:top" |
|}

=== X.Org driver ===
This chip is supported by the 'chips' driver as part of the X.Org distribution

==== ThinkPad LCD ====
Display on the internal LCD works as long as you set the monitor settings correct.

==== External VGA port ====
??
=== Linux fbcon Framebuffer driver ===
??

=== ThinkPads this chip may be found in ===
* {{310}}, {{310D}}, {{310E}}, {{310ED}}

[[Category:Video Controllers]]