ThinkWiki - User contributions [en]

CompactFlash boot drive

2012-04-20T12:59:09Z

Mgedmin: Update link to daniel-boehmer.de by request of user boehmer on FreeNode; the old URL was already redirecting to the new one.

__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 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 PATA controller for the HDD slot can recognize both CF cards installed on a dual adapter. While newer ThinkPads, such as X41, which utilize SATA controller, can only recognize the single card installed on 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. [[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 usually used in the faster CF cards). This should not however be as much of an issue because... 
* The 100,000 write cycles applies to each address block separately in the card, not to the card as a whole 
* The flash controller automatically distribute write operations evenly (wear leveling), so that the number of writes to each address block is kept low 
Therefore, it should take years of typical real world usage to render a current flash memory card based on SLC NAND unusable 

However, manufacturers have started in 2008 using Multi-Level Cell (MLC) NAND to make SSD. MLC NAND typically has only about 10,000 write cycles. To complicate things further a company called EasyCo claims her Managed Flash Technology (MFT) "increases the write-life of Flash Disks more than 50-fold", which could be what made possible the launch of SSD based on MLC NAND. 

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/SATA 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 do not work on newer ThinkPads, including the {{X41}}, {{X41T}}, {{T43}}, {{T43p}} and {{R52}}. Because their IDE interface is actually connected to the SATA controller via an IDE-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 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}}

===CF to SATA===
These adapters are needed for newer ThinkPads with native SATA interface.
{{Todo|If someone has tested any, please add them here}}

==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 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 Linux to partition the drive with a FAT32 partition (you can boot from one of the LiveCD/LiveUSB distributions for this), and set the partition 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 has however changed it stance on this and now refuses to provide it. This utility (ATCFWCHG.COM) however can be found for download at various places (try Google).

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)

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

==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 (which since memory is 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==
*** 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 flash 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]

BIOS Upgrade

2011-03-03T17:49:06Z

Mgedmin: Added /* Unsuccessful tests */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
This page is meant to describe ways to update the BIOS on a ThinkPad that only runs Linux for users that don't have ready access to Windows. If you have Windows on your ThinkPad you can just boot into it and follow instructions on the Lenovo website.

Updating the BIOS in Linux (with few exceptions) '''is not officially supported''' by Lenovo. However there are work arounds.

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

'''Proceed at your own risk!'''}}
|}

= Downloading New Firmware =
{{WARN|Flashing the wrong firmware for your hardware may cause permanent damage to your ThinkPad. It is up to you to confirm that the firmware you are using is correct.}}

A list of links to firmware downloads can be found at [[BIOS Upgrade Downloads]] for most Thinkpad models. You can also check the Lenovo Support website's [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=TPAD-MATRIX|ThinkPad driver matrix].

Lenovo provides firmware upgrades in a variety of packages:
* Diskette
* Non-diskette
* Linux diskette
* BIOS Utility
* Bootable CD

Not every type of package is available for every model.

The ''BIOS Utility'' and ''Bootable CD'' packages combine the BIOS and ECP firmwares. For the other packages, there is one for each firmware.
{| align="right" style="width:20em;"
| {{HELP|Can an image be extracted from a "Linux diskette" .exe file?}}
|}

The ''Linux diskette'' is just the ''Diskette'' package that runs on Linux instead of Windows/DOS. It's unknown if a boot image can be extracted from it.

You may need to try different packages to find the one from which you can extract a boot image.

== Two Firmwares: BIOS and ECP ==
{{WARN|Flashing incompatible firmwares, or flashing them in the wrong order, may cause permanent damage to your ThinkPad.}}

It is important to understand that Thinkpads from IBM have two separate firmwares: the BIOS, and the Embedded Controller Program (ECP).

A given BIOS version will require a certain version of the ECP. You must read the Lenovo website and/or .txt files to confirm which BIOS is compatible with which ECP, and '''the order in which to update them'''.

=== Update Order ===

The IBM documentation is sometimes unclear about the order in which these two firmwares should be updated. When in doubt (i.e. IBM didn't provide specific instructions for your model or a particular firmware update), '''update the ECP first, and then the BIOS'''. Also, make sure to do the two updates '''immediately one after the other'''.

The EC firmware is usually much better at backwards compatibility than the BIOS.

(Updaters for newer models take care of both BIOS and EC, and use automatically whatever sequence is needed, so you don't have to worry about it.)

== Installed Firmware ==
You can check the current BIOS and ECP versions on your ThinkPad by using '''dmidecode'''. For example:

{{cmdroot|dmidecode -s bios-version}}

1RETDRWW (3.23 )

{{cmdroot|dmidecode -t 11}}

# dmidecode 2.9
SMBIOS 2.33 present.
Handle 0x0029, DMI type 11, 5 bytes
OEM Strings
String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-

Showing BIOS version 3.23 (1RETDRWW) and ECP version 3.04 (1RHT71WW).

===DMI IDs===
Please consider updating the [[List of DMI IDs]] before (and after) updating your BIOS.

= Updating Firmware =

There are two basic steps to updating the firmware (either the BIOS or the ECP) on a ThinkPad not running Windows:
# Extract a bootable update image
# Boot from that image

== Extracting an update image ==
{{WARN|Though this process has been successfully tested on many versions of .exe files found on IBMs website, that doesn't mean it will work for all of them. '''Proceed at your own risk'''. Consult the testing tables farther down of this page to see other users' experience with your model Thinkpad.}}
{{NOTE|These EXE unpack procedures no longer work on more recent downloads, as Lenovo has changed the packaging format. You may still be able to unpack them using wine, or alternatively an actual (virtual) Windows machine.}}
Older .exe installers from Lenovo mostly appear to be just a wrapper license program around Windows .cab files (see [[How_to_change_the_BIOS_bootsplash_screen|BIOS-Bootsplash]]). If you install the Linux program [http://freshmeat.net/projects/cabextract/ '''cabextract'''] you can expand these .cab files directly. For example, if you downloaded {{path|1iuj13us.exe}} from Lenovo:

:{{cmduser|cabextract 1iuj13us.exe}}

Extracting cabinet: 1iuj13us.exe
extracting 1IUJ13US.IMG
extracting BIOSUPTP.EXE
extracting DOBOOT.EXE
extracting DOSBOOT.COM
extracting DOSBOOT.SYS
extracting DOSBOOT.VXD
extracting DOSBOOT2.COM
extracting ECTLUPTP.EXE
extracting EFLASHAS.SYS
extracting HDFWUPTP.EXE
extracting IBMTPI.XML
All done, no errors.

The file we want is '''FILENAME.IMG''', with "FILENAME" being the .exe. you downloaded. E.g., {{path|1IUJ13US.IMG}}.

(If this does not work for the Non-diskette .exe, try it on the Diskette .exe. It's reported, for example, that the Non-diskette .exe for BIOS version 3.23 for the T41p was not extractable, but the Diskette .exe worked perfectly, with {{cmduser|cabextract}} delivering a .IMG file.)

==== Testing the Image ====

You can test that FILENAME.IMG is really a floppy image by running:

{{cmdroot|mkdir /tmp/mntfloppy}}

{{cmdroot|mount -o loop FILENAME.IMG /tmp/mntfloppy}}

If a '''ls''' command on the image returns what looks like a DOS floppy, and no read errors were displayed, you have a pretty good chance that the image is usable. For example:

{{cmdroot|ls /tmp/mntfloppy}}
$0195000.FL1 069580.PAT 06d2.HSH IBMDOS.COM TPCHKS.EXE
0691.HSH 06D0.PAT 06d6.HSH LOGO.BAT UPDTFLSH.EXE
0691.PAT 06D1.PAT 06d8.HSH LOGO.SCR UPDTMN.EXE
0694.HSH 06D2.PAT CHKBMP.EXE PHLASH16.EXE USERINT.EXE
0694.PAT 06D6.PAT COMMAND.COM PREPARE.EXE UTILINFO.EXE
0695.HSH 06D8.PAT CONFIG.SYS PROD.dat lcreflsh.bat
0695.PAT 06d0.HSH FLASH2.EXE QKFLASH.EXE
069580.HSH 06d1.HSH IBMBIO.COM README.TXT

Unmount the image after you are done testing:

{{cmdroot|umount /tmp/mntfloppy}}

== Booting from update image ==
Now that you have a bootable image for the correct update for you hardware, you need to do is boot from that image to install the update.

There are different ways to do that:
* [[#Booting from a CD|Boot from a CD]]
* [[#Booting_using_GRUB|Boot from the image, using GRUB]]
* [[#Booting_from_a_floppy|Boot from a floppy]]
* [[#Booting_from_a_USB_Flash_drive|Boot from a USB Flash drive]]

=== Booting from a CD ===
{| align="right" style="width:40em;"
|{{HINT|If there is a ''Bootable CD'' image available, e.g., FILENAME.iso, just download that, instead of mucking around with image files.}}
|}
If you are going to update the firmware by booting from a CD, you need to turn FILENAME.IMG that you extracted above into an .iso file.

The [http://en.wikipedia.org/wiki/El_Torito_%28CD-ROM_standard%29 El Torito Bootable CD Specification] is a wonderful thing. Thanks to it, a bootable CD can be made with a bootable floppy image in such as way that the CD believes that it is a 2.88 MB floppy drive. This allows you to replace a boot floppy by a boot CD in nearly all situations.

It is very easy to create such a bootable CD ISO image in Linux using the '''mkisofs''' tool{{footnote|1}}. Run a command as follows:

{{cmdroot|genisoimage -b 1WUJ25US.IMG -c boot.catalog -o bootcd.iso 1WUJ25US.IMG}} #or older mkisofs

Where *.IMG is the name of the image file extracted above. This creates a CD with one file on it and marks that file as the boot image.

You can now burn the {{path|bootcd.iso}} to a CD in your favorite CD-burning program.
{{WARN|By following any of the instructions here you are accepting the '''very real risk''' of turning your ThinkPad into a big expensive paper weight, as a firmware update gone wrong can create unfix-able problems. '''Proceed at your own risk!'''}}

Boot from the CD to update your firmware. Remember to have [[BIOS_Upgrade#Two_Firmwares:_BIOS_and_ECP|both BIOS and ECP firmware boot-CDs]] ready, as needed, and use them in the [[#Proper_Order|proper order]].

==== Successful tests ====

{| border="1" cellspacing="0" cellpadding="2" style="font-size:80%; vertical-align:top;"
! Model
! Tested by, and comments
|-
| {{600E}} 2645-4AU ||
* George Tellalov <gtellalov_dontspamme@bigfoot.com>. BIOS 1.16 from spsdin36.exe worked perfectly with the method bootable cd from floppy image. I highly recommend this upgrade because it made my ibm-acpi module load (it wouldn't load before) and fixed some suspend to ram problems. Here's the [http://george.tellalov.info/bios_upgrade_600e_spsdin36.iso cd image] I used. Use at your own risk. You can send me a chocolate if it works for you ;)
|-
| {{600E}} 2645-5bU ||
* Mike Vincent<matchstc-putobvioushere.com>. Bios 1.16 from spsdin36.exe and then to the boot cd worked great for me. Thought I had bricked it three separate times using a "real" floppy! Each from different diskettes .The updater would start, give me the "going to take30 seconds" speech...and then access the HD for 10 minutes. Each time it would reboot fine. Did the cd as described above...worked great first time. Perhaps 10 year old seldom used floppy disc drives have some challenges?
|-
| {{600X}} 2645 ||
* Jonathan Byrne <jonathan@RemoveThisToMailMe.yamame.org>. BIOS 1.11 from spsuit55.exe worked perfectly using cabextract/CD method.
|-
| {{600X}} 2645 ||
* Andy Barnes <andy@RemoveThisToMailMe.itchypaws.co.uk>. As per Jonathan above, extracted BIOS 1.11 from spsuit55.exe using cabextract, created a CD boot image and burnt to CD. Worked flawlessly - thanks to everyone who contributed to this article!
|-
| {{A20p}} 2629-6VU ||
* Chris Pickett http://www.sable.mcgill.ca/~cpicke/. BIOS 1.11 flashed fine with cabextract/CD method.
|-
| {{A21e}} 2628-JXU ||
* Amit Gurdasani <gurdasani at yahoo dot com>. BIOS 1.13 flashed fine with cabextract/CD method. Alarmingly, after the BIOS update, the laptop beeped but did not shut down as was indicated onscreen -- that was frozen on the "do not shut down the laptop" screen. On power down and up again, the BIOS setup showed the newer BIOS image running, and Linux booted up fine. Linux ACPI didn't complain about the BIOS being too old either.
|-
| {{A31p}} 2653 ||
* Matthias Meinke largeeddy@gmx.at, BIOS 1.09 1NET15WW flashed fine with cabextract/CD method.
|-
| {{A31}} 2652 ||
* [[User:Wnoise|Aaron Denney]], BIOS 1.13 flashed fine with cabextract/CD method. The cabextract/CD method also worked for BIOS 1.10.
|-
| {{R30}} ||
* Jarrod, 30 August 2007, Thinkpad R30 Type 2656-E0M. BIOS updated to 1.40 (1CETF0WW) using floppy disk/mkisofs/cdrecord. Worked fine, no problems.
|-
| {{R31}} ||
* [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/1998-January/009743.html Mathias Dalheimer]
* Sebastian Sauer (with cabextract/CD method)
|-
| {{R40}} ||
* Matthew Lambie, http://lambie.org
* Antti S. Lankila, update to 1.27 via direct use of phlash16.exe against a BIOS image. Normal method did not work because the battery is dead.
|-
| {{R50}} 1836-3SU ||
* jlbartos <jlbartos at hotmail dot com>
|-
| {{R50e}} 1834-PTG ||
* item <item at freemail dot hu> : successfully finished with cabextract/CD method for "1wuj25us.exe" (BIOS version 1WET90WW (2.10), Release Date: 2006/12/22)
* Christos Nouskas <nouskas at gmail dot com>: upgraded to BIOS version 1WET90WW (2.10) and EC version 1VHT28WW (1.04) using GRUB (BIOS first / EC second)
|-
| {{R51}} 1829 ||
* Robert Uhl <rob dot uhl at gmx dot de>, Jellby <jellby at yahoo dot com>
|-
| {{R51}} 1830-RM7 ||
* Will Parker <stardotstar at sourcepoint dot com dot au> successfully flashed 3.20 using existing 3.04 ECP and retained custom boot splash.
|-
| {{R51}} 2887 ||
* Ingo van Lil <inguin at gmx dot de>
|-
| {{R52}} 1858 ||
* Stuart McCord <stuart dot mccord at gmail dot com> flashed both BIOS and ECP using cabextract, BIOS flashed first as on IBM website
|-
| {{T20}} ||
* Franz Hassels <fhassel at suse dot com>
|-
| {{T22}} ||
* Daniel Maier <nusse teamidiot de>
* Mathias Behrle (with cabextract/CD method, Version 1.07 => 1.12) --[[User:Mathiasb|Mathiasb]] 11:58, 14 December 2006 (CET)
* Bob Skaroff (cabextract/CD), 1.06 => 1.12
* Leo Butler (cabextract/CD), 1.11 => 1.12
|-
| {{T23}} ||
* Bart Snapp <snapp at uiuc dot edu> Note: I followed IBM's instructions to flash the BIOS '''first''' and the Embedded Controller '''second'''.
* Moy Easwaran: BIOS 1.18 / EC 1.06a via cabextract and CD-boot. The BIOS-update exe generated errors in Windows 2000.
* Joe Renes: BIOS 1.18 / EC 1.06a on 2006-03-20 via cabextract and CD-boot. Piece of cake.
* Raphael Errani: BIOS 1.20 / EC 1.06a on 2006-11-06 via cabextract and CD-boot (using mkisofs). Worked without errors. 1st Bios, 2nd EC
* Myron Getman: BIOS 1.20 / EC 1.06a on 9/10/08 via cabextract --> k3b --> CD-boot. Worked like a charm. First BIOS update with Linux!
* Leo Butler: BIOS 1.13 / EC 1.04 to 1.20/1.06a via cabextract and syslinux/memdisk boot through grub. Worked like a charm and no wasted CD.
|-
| {{T30}} ||
* Martin GÃ¼hring <guehring at gmail.com> BIOS 2.10 via cabextract the Non-Diskette BIOS -> mkisofs '''in the directory the exe was extracted''' to generate the iso -> burn the iso -> boot the CD
|-
| {{T40}} ||
* Sean Dague, http://dague.net
* Justin Mason, http://jmason.org
* Ivanhoe (Bios 3.19)
* Alessandro Raulino (roger_2) EC 3.04 & BIOS 3.23 flashed with cabextract/CD method
* Nick Jenkins, using BIOS 3.23 with the '''Non-diskette updater + cabextract method''', then [[#Creating_a_Bootable_CD_from_a_Floppy_Image|created a bootable CD from the cabextracted .IMG file]], then boot that ISO, and it worked great!
* xyz: BIOS 3.23 & EC 3.04 flashed with cabextract/CD method. No problem.
|-
| {{T40p}} ||
* Lukas KrÃ¤henbÃ¼hl, ismo at pop dot agri dot ch
* Thomas Achtemichuk, tom at tomchuk dot com. BIOS 3.15 flashed fine with cabextract/CD method
* paper, BIOS 3.23 (1RETDRWW) flashed fine with cabextract/genisoimage method.
|-
| {{T41}} ||
* Lev Givon (Bios 3.15 / EC 3.04) <lev at columbia dot edu>
* Ernesto HernÃ¡ndez-Novich (Bios 3.19 / CP 3.04) < emhn at usb dot ve >
* [http://maebmij.org James Ballantine] (Bios 3.21 / CP 3.04) using nondisk/cabextract/CDRW
* Vladimir Pycha (to Bios 3.23 / EC 3.04, from Bios 3.20 / EC 3.04) using nondisk/cabextract/CDRW. Booted with external USB optical drive (I have internal drive broken) - at the beginning of the boot sequence press PAUSE, then wait several seconds, then ENTER, then F12 and select the drive. Without pressing PAUSE I am not able to boot from USB optical/hard drive as the drive does not show in the F12 boot list menu.
|-
| {{T41p}} ||
* Nils Newman, work great. (Version: Bios 3.14 / Embedded Controller 3.04)
|-
| {{T42}} 2373-JXG ||
* magarzo <mdr.magarzo at gmail.com> (BIOS v.3.23 / Embedded Controller v.3.04 / both with cabextract to non-diskette v. plus Bootable CD)
|-
| {{T42}} ||
* Dan (BIOS 3.20 / EC 3.04, cabextract/CD method) <tronic171 at evilphb.org>
* Hirosh Dabui <hirosh@dabui.de>
|-
| {{T42p}} ||
* Robert Schiele <rschiele@uni-mannheim.de>, Joern Heissler <joern@heissler.de>, Hirosh Dabui <hirosh@dabui.de>
|-
| {{T43}} 1871-W34 ||
* Florian Boucault <florian at boucault dot ath dot cx> (Version: Bios 1.23 / Embedded Controller 1.03)
|-
| {{T43}} 1871-4AG ||
* [http://blog.martinmcdowell.com/about/contact Martin McDowell] 28-Feb-2010
* BIOS 70ET62WW (1.22) to 70ET69WW (1.29),
* ECP 70HT26WW (1.03) to 70HT28WW (1.05)
Both successfully upgraded from CD Image made from the instructions on this website.
|-
| {{T43}} 2886 ||
* Till Heikamp <t dot heikamp at geniusbytes dot com> (Bios 1.22 to 1.29, Embedded Controller 1.03 to 1.06)
|-
| {{T43}} ||
* Conrad Rentsch <Conrad dot Rentsch at t-online dot de> (Version: Bios 1.29 / Embedded Controller 1.06)
* Tom Heady <tom-thinkwiki.org@punch.net>
|-
| {{T60}} ||
* 1951 Roman Komkov <roman at komkov dot org dot ru> (Bios 1.07 to 2.13) Successfully upgraded from CD Image
* 8744-HCG Konstantin Khorenko <horenko at mail dot ru> (Bios 1.06 to 1.18) Successfully upgraded from CD Image
|-
| {{T61}} ||
* Kai Weber <kai.weber at glorybox dot org> (Bios 1.06 to 1.26) Successfully upgraded from CD Image
|-
| {{T410}} ||
* Pablo Zometa (BIOS 1.35)
|-
| {{X20}} ||
* Neil Caunt <retardis at gmail dot com>
|-
| {{X21}} ||
* Patrick Leickner <ranma at web dot de>, (BIOS 2.21->2.25 / EC 1.31->1.36) via non-disk/cabextract/mkisofs/cdrecord
|-
| {{X22}} ||
* David Emery <dave at skiddlydee dot com>, (EC 1.30, BIOS 1.32 using non-disk/cabextract/CD method)
|-
| {{X23}} ||
* Nils Faerber <nils dot faerber at kernelconcepts dot de> (Embedded Controller 1.30, BIOS 1.32 with cabextract/CD method)
|-
| {{X30}} ||
* Hella Breitkopf, [http://www.unixwitch.de/ www] (Embedded Controller 1.04, BIOS 1.07 with cabextract/CD method)
* William Roe <willroe at gmail dot com> (Embedded Controller 1.06, BIOS 1.09 - cabextract/mkisofs/wodim)
|-
| {{X31}} ||
* Grzegorz KuÅ›nierz <koniu at sheket dot org> (Embedded Controller 1.08, BIOS 3.01 with cabextract/CD method)
|-
| {{X31}} ||
* Paul Litwack <paullitwack at gmail dot com> (Embedded Controller 1.08, BIOS 3.02 with cabextract/unetbootin method)
cabextract & unetbootin are staight foward(toggle floppy image instead of iso image in unetbootin dialog)
No problems with update software.
x31 has to be cajoled into booting from usb. Boot hangs when pendrive is present. Hit the key to bring up the boot menu.
Unplug the pendrive. Let the boot menu come up. Plug in the pendrive. Select the pendrive in the boot menu and it boots.
|-
| {{X40}} ||
* Robbie Stone <robbie@serendipity.cx>
* Andy Shevchenko <andy.shevchenko@gmail.com> (Fine by cabextract/CD method)
|-
| {{Z60m}} ||
* [[User:Morle|Morle]] 01:09, 17 Nov 2007 (CEST), (Embedded Controller 1.18 and Bios 1.24 with cabextract/CD method)
|}

==== Unsuccessful tests ====
{| border="1" cellspacing="0" cellpadding="2" style="font-size:80%; vertical-align:top;"
! Model
! Tested by, and comments
|-
|<pre> </pre> 
|
|}

=== Booting using GRUB ===
{|
| style="width:75%" | {{WARN|Many have warned '''not''' to use the SYSLINUX image-loader '''memdisk''' to boot firmware update images.}}
| style="font-size:80%" | {{HELP|Who are these "many"? Link to a discussion?}}
|}
Once the bootable image, FILENAME.IMG, is extracted from the .exe, it can be booted directly through GRUB without the need of burning a CD, using the [http://syslinux.zytor.com/ SYSLINUX] image-loader '''[http://syslinux.zytor.com/memdisk.php memdisk]'''.

Locate the '''memdisk''' file from the syslinux package. You can search for it with '''find''':

{{cmdroot|find /usr -name memdisk}} #or just use "dlocate memdisk" or "locate memdisk" if these programs are installed

If {{path|/usr/.../memdisk}} is not present, syslinux is not installed. You will need to install it to boot a .IMG from GRUB.

Copy both the '''FILENAME.IMG''' and '''memdisk''' files into {{path|/boot}} directory. For example:

{{cmdroot|cp ./FILENAME.IMG /usr/share/syslinux/memdisk /boot/}}

Open {{path|/boot/grub/menu.lst}} in your favourite editor. '''Copy''' the active section into a '''new section''', and edit the new section:
{| border="1" cellspacing="0" cellpadding="2"
! Parameter
! Instructions
! Example
|-
| ''title'' || Pick a name for the new section. This will show up in the GRUB boot menu. || <tt>title IBM ECP Update</tt>
|-
| ''root'' || Do not change. This is the partition containing the {{path|/boot}} directory || <tt>root (hd0,0)</tt>
|-
| ''kernel'' || '''/boot/memdisk''' will allow you to boot an image file. || <tt>kernel /boot/memdisk</tt>
|-
| ''initrd'' || This is the name of the firmware-updater image file, e.g., 1IUJ13US.IMG || <tt>initrd /boot/1IUJ13US.IMG</tt>
|}

Do '''not''' modify the original section in {{path|/boot/grub/menu.lst}}, or you might not be able to boot back to the operating system.

If you have [[#Two_Firmwares:_BIOS_and_ECP|two firmware updates to do]], you will need a section for each firmware's FILENAME.IMG in {{path|/boot/grub/menu.lst}}.

{{NOTE|If both BIOS and ECP are to be updated, be sure to update them in the [[#Proper_Order|proper order]].}}

{{WARN|By following any of the instructions here you are accepting the '''very real risk''' of turning your ThinkPad into a big expensive paper weight, as a firmware update gone wrong can create unfix-able problems. '''Proceed at your own risk!'''}}

Reboot your computer, entering the GRUB menu and selecting ''IBM BIOS Update'', or whatever you named the new section in {{path|/boot/grub/menu.lst}}.

==== GRUB2 ====
With grub2, one would ''append'' the following to ''/boot/grub/grub.cfg'' :
menuentry "My BIOS Upgrade" {
set root=(hd0,0) #should match the others in your grub.cfg
linux16 /boot/memdisk
initrd16 /boot/1WUJ25US.IMG #or whatever yours is
}

==== Successful tests ====
{|border="1" cellspacing="0" cellpadding="2" style="font-size: 80%"
|-
! Model
! BIOS
! ECP
! Tested by
! Notes
|-
| {{R30}} 2656-64G || v.1.40 || || [[User:english.voodoo|Yuri Spirin]] ||
|-
| {{R40}} 2723 || 1OHJ11WW.IMG || 1PUJ25US.IMG || [[User:qunying|Qunying]] || memdisk from syslinux 3.70 (slackware 12.1)
|-
| {{R50e}} 1834NV1 || 1WUJ25US.IMG || || [[User:Jidanni|Jidanni]] || memdisk from syslinux-common 2:3.84+dfsg-1 (Debian), grub2 (1.96+20080724-16)
|-
| {{R51}} 2888 || || || ||
|-
| {{T23}} 2647 || 1AUJ20US.IMG || 1AHJ06US.IMG || [[User:cthon|cthon]] || memdisk from syslinux 4.02-1 (arch linux)
|-
| {{T40}} 2373 || 1RUJ37US.IMG || 1RHJ10U2.IMG || [[User:Euphoria|Euphoria]] || memdisk from syslinux 1:3.31-4 (Debian package version)
|-
| {{T40}} 2373 || 1RHJ10U2.IMG (3.04, 2004-11-15) || 1RUJ37US.IMG (3.23, 2007-07-03) || [[User:Morphics|Morphics]] || cabextract and memdisk from syslinux 3:1.36-4ubuntu5
|-
| {{T41}} 2373 || 1RUJ37US.IMG (3.23, 2007-07-03) || || [[User:Tonko|Tonko]] || Fedora 12
|-
| {{T41p}} 2373 || 1RUJ37US.IMG (3.23, 2007-07-03) || || [[User:Deggel|Deggel]] || cabextract and memdisk from syslinux 3.71 on gentoo
|-
| {{T41p}} 2373 || || || [[User:MrStaticVoid|James Lee]] ||
|-
| {{T42}} 2373 || 1RUJ37US.IMG || || [[User:Secsaba|Simon Csaba Endre]] || Ubuntu 10.04 Pre-update versions: BIOS v3.21 / ECP v3.04 After-update versions: BIOS v3.23 / ECP v3.04
|-
| {{T42p}} 2374 || 1RUJ37US.IMG || 1RHJ10U2.IMG || [[User:aderigs|Achim Derigs]] || Debian GNU/Linux sid, works with `linux16 ...' and `initrd16 ...' only
|-
| {{X31}} 2673-CBU || || || [[User:JanTopinski|Jan Topinski]] ||
|-
| {{X31}} 2672-CXU || || || [[User:TheAnarcat|TheAnarcat]] ||
|-
| {{X31}} 2672-JBU || 3.02 1QUJ19US.IMG || 1.08 1QUJ08US.IMG || [[User:twbxf4|twbxf4]] || worked flawlessly
|-
| {{X31}} 2673-58G || || || [[User:FaUl|FaUl]] ||
|-
| {{X31}} 2672-PG9 || || || [[User:Starox|Starox]] || a big moment between starting update and the updating window
|-
| {{X31}} 2672-PG9 || v3.02 1QUJ19US.IMG || v1.08 1QHJ08US.IMG || [[User:TeeLittle|TeeLittle]] || Apr 10, 2010: Using Debian 5.0 "Lenny" + package syslinux-common (Version: 2:3.71+dfsg-5). Pre-update versions: BIOS v2.11 / ECP v1.03
|-
| {{X40}} 2371 || 2.07 1uuj21us.exe || 1.62 1uhj10us.exe || [[User:Antialize|Jakob Truelsen]] || Worked on two X40-2371
|-
| {{X40}} 2386 || 2.08 1uuj22us.exe || 1.62 1uhj10us.exe || [[User:Antialize|Galen Seitz]] || memdisk from syslinux 3.61
|}
(More successful grub tests are scattered in the previous table too.)

==== Unsuccessful tests ====
{|border="1" cellspacing="0" cellpadding="2" style="font-size: 80%"
|-
! Model
! style="width:10em;" | BIOS
! ECP
! Tested by
! Notes
|-
| {{R32}} 2658-NWU || 2.16 1MUD23US.IMG || n/a || [[User:Millman12345|Mike Millman]] || Boots into the BIOS flashing program just fine, but when it comes time to start the update process, the system hangs completely. Luckily, it hangs before it actually modifies anything... A hard reboot got me back into a working system. I would not recommend this route!
|-
| {{R52e}} 1846-CGL || 1.29 76UJ28UD.IMG || 1.01 || [[User:Lacyc3|Laszlo Takacs]] || Boots into BIOS flashing program but it hangs up before the upgrade process. I used memdisk from syslinux-4.01.
|-
| {{T43}} 2668-F7G || 1.29 1YUJ18US.IMG || || [[User:Maus3273|Maus3273]] || I got into the bios program, but the machine never restarts after initiating the upgrade.
|-
| {{X41}} 2525-FAG || 2.09 74UJ15US || || [[User:Ukleinek|Uwe Kleine-König]] || booted fine (Debian syslinux 2:3.71+dfsg-5), but didn't succeed to write, just hang at "Don't restart or remove diskette etc. pp" (not bricked). Worked fine via CD method.
|-
| {{X41}} 2525-F8G || 2.06 74UJ12US.IMG 2.07 74UJ13US.IMG 2.09 74UJ15US.IMG || || [[User:ladoga|Lauri Koponen]] || hangs while initializing the actual BIOS flashing process ECP: 1.02 74HJ03US.IMG works
|-
|}

==== GRUB2 Boot CD Image ====
Download the bootable iso file from the Lenovo Website. Copy the file 'memdisk' from the syslinux package to /boot. Also create a symlink, so you do not have to change the grub configuration for each bios upgrade:
<pre>
sudo su -
cp /home/youruser/Downloads/6uuj12uc.iso
cp /usr/share/syslinux/memdisk /boot
ln -s 6uuj12uc.iso biosupgrade.iso
</pre>
Now create the boot entry:
<pre>
cat >> /etc/grub.d/40_custom <<EOF
menuentry "Lenovo BIOS Upgrade" {
set root=(hd0,1) # <-- check for correct numbering
linux16 /boot/memdisk iso
initrd16 /boot/biosupgrade.iso
}
EOF
update-grub
</pre>
Reboot an Select "Lenovo BIOS Upgrade".

For the next Bios Upgrade you'll just need to copy the new iso file to /boot and adjust the symlink.

==== Successful tests ====
{|border="1" cellspacing="0" cellpadding="2" style="font-size: 80%"
|-
! Model
! BIOS
! ECP
! Tested by
! Notes
|-
| {{X100e}} 2876-55G || 6xuj05uc.iso || || [[User:nikel]] ||
|-
| {{Edge}} || 1.17 6yuj04uc.iso || || [[User:theBro]] || Current memdisk from syslinux worked (5/2010), the one provided by Ubuntu 9.10 did not.
|-
| {{X200s}} || 1.13 6duj40uc.iso || || [[User:theBro]] || Current memdisk from syslinux worked (5/2010), the one provided by Ubuntu 9.10 did not.
|-
| {{X200s}} || 3.14 6duj41uc.iso || 1.06 || [[User:dag-|Dag Wieers]] || Using memdisk from syslinux 4.01
|-
| {{X201}} 3626-A14 || 1.15 6quj05uc.iso || 1.09 6quj05uc.iso || [[User:Alexander List|Alexander List]] || memdisk from syslinux 3.86
|-
| {{Edge 13"}} 0197-6GG || 1.18 6yuj05uc.iso || || [[User:fethio]] || Current memdisk from syslinux worked (5/2010), the one provided by Ubuntu 9.10 did not.
|-
| {{Edge 13"}} 0197-34Q || 1.21 6yuj08uc.iso || || [[User:Kapil]] || Current memdisk from syslinux debian version 2:4.02+dfsg-7
|-
| {{Edge 13"}} 0197-34Q || 1.18 6yuj05uc.iso || || [[User:Kapil]] || Current memdisk from syslinux debian version 2:4.01+dfsg-1
|-
| {{X200s}} || 3.15 6duj42uc.iso || || [[User:lawnjam]] || Memdisk 4.02 worked, the one provided by Ubuntu 10.04 did not.
|-
| {{X201}} || 1.22 6quj08uc.iso || 1.11 || [[User:dag-|Dag Wieers]] || Using memdisk from syslinux 4.03
|-
| {{T410s}} || 1.41 6uuj12uc.iso || 1.12 || regatus || Gentoo + memdisk (syslinux 4.0.3)
|-
|}

==== Unuccessful tests ====
{|border="1" cellspacing="0" cellpadding="2" style="font-size: 80%"
|-
! Model
! BIOS
! ECP
! Tested by
! Notes
|-
| {{T61}} 6466-55G || 2.27 7luj26uc.iso || 1.08 || [[User:mgedmin]] || Grub2 + memdisk (2:4.01+dfsg-3ubuntu1) booted the DOS image on the CD, which then tried to load a DOS CD-ROM driver, which then could not find the CD, and ended up with the infamous Abort, Retry, Fail.
|-
|}

=== Booting from a Floppy ===
{{WARN|Using a floppy disk '''is NOT recommended'''.}}

This is how IBM/Lenovo intended it. Use their .exe files to create a bootable floppy with the flash update on it. Boot from the floppy and there you go.

So, why is it not recommended?
# If something goes wrong, your ThinkPad may be permanently damaged
# Floppy disk drives are not reliable
# Floppy disks are not reliable
# It only works with /dev/fd0, meaning it won't work with a USB floppy

So, even though Lenovo is now offering "Linux diskette" updaters, that will create a bootable floppy under Linux, using a floppy is still not recommended. Besides, many people don't even ''have'' a floppy drive on their ThinkPad.

If you really want to do it with a floppy, some tips:
* Use a clean (in the physical sense) floppy drive
* Use new floppies
* Test floppies for errors before starting update process
* Have multiple copies of the update disks ready--if one should fail, replace it with a copy
* Should DOS complain of a read error, '''only''' respond wth "Retry"

{{NOTE|Should the system encounter a disk read error during the flash process, and you select "Abort", your system could be permanently damaged.}}

=== Booting from a USB Flash drive ===

==== Updating the BIOS in MS-DOS mode ====
(This process works for most Thinkpad models that has Windows XP, Windows Vista or Windows 7 OS)

1. Using HP USB Boot Utility, [http://blogs.oreilly.com/digitalmedia/2004/10/utility-to-make-usb-flash-driv.html create a bootable USB flash drive [http://www.bay-wolf.com/utility/usbkey/win98boot.zip DOS using Windows 98 Boot Disk Floppy Image].

2. Extract the (*.ima) from the ISO BIOS image (e.g. [http://www.rarsoft.com WinRAR] will do this).

3. Using a tool that can open .IMA files (such as [http://www.winimage.com/ WinImage]), extract all files to a temporary folder.

4. Run the HP tool, select the USB device, I used FAT32, create a DOS bootable disk and point at the win98boot folder - then "Start". Warning: this '''formats''' the USB flash drive and all data will be erased!

5. Once complete (you could test if it boots at this point), copy the extracted BIOS files from the temporary folder you created to the USB flash drive.

6. Boot from USB flash drive by pressing F11 within the BIOS boot logo. At the DOS command prompt, type "updflsh" and then follow the prompts by pressing "Y" or Enter. Make sure that you have a fully charged battery pack and the AC Adapter is firmly plugged before proceeding with the BIOS update.
'''DO NOT Power off the laptop or unplug the USB flash drive while the update is in progress or else update will fail and your computer will be unable to boot and system board may need to be serviced.'''

This process takes around 1-2 minutes. A long beep followed by a short beep will notify you that the update is complete and the system will automatically power off.

7. Power on the laptop then enter the BIOS setup by pressing F1 and Load BIOS defaults.

==== Using grub4dos (also for Linux) ====

[http://grub4dos.sourceforge.net/wiki/ grub4dos] is a GNU GRUB fork with interesting features. One of them is the ability to boot ISO images directly off USB flash drives. Contrary to the name, GRUB for DOS works fine on Linux. Follow these steps:
* Download the latest grub4dos package at http://download.gna.org/grub4dos/ (I needed 0.4.4 for my USB2 drive - 0.4.3 did not work.)
* Unpack
* Insert your FAT-32 formatted pendrive
* Run <code>sudo ./bootlace.com /dev/sdX</code>, where /dev/sdX is the device name assigned to your pendrive (use <code>sudo fdisk -l</code> to figure this out). Be very careful to get the device correct or else you could overwrite your hard drive! This creates grub4dos boot sector in MBR of the flash drive.
* Copy the files <code>grldr</code> and <code>menu.lst</code> to the root directory of your pendrive.
* Convert the ThinkPad .IMG file to a .ISO file using <code>genisoimage -b 1yuj18us.img -c boot.catalog -o 1yuj18us.iso 1yuj18us.img</code>
* Copy the ISO image to the root directory of your pendrive (e.g. <code>1yuj18us.iso</code>).
* Edit <code>menu.lst</code> on the pendrive and include the following section (of course putting the appropriate ISO image name):
<pre>
title thinkpad-bios
map (hd0,0)/1yuj18us.iso (hd32)
map --hook
chainloader (hd32)
boot
</pre>
* Reboot and press F12 to select booting from USB.
* If all went well, you should be able to boot the Thinkpad's ISO image and flash the BIOS. I tested it successfully on T400. [[User:Wanted|Wanted]] 20:23, 16 July 2010 (UTC)

==== Using UNetbootin ====

Unetbootin 422 worked with the image files unpacked with cabextract on my x31.

{{HELP|How exactly did you do this? It failed for me. Does it work only with .IMG files that are converted to .ISO files, or can .ISO files provided by Lenovo also work (how?)}}

=== Booting from a Network Boot Image ===
BIOS, ECP, CD/DVD and Harddisk firmware disks can be booted over the network with [http://syslinux.zytor.com/pxe.php PXELINX] as part of the [http://syslinux.zytor.com/ SYSLINUX] package. This requires that you have a DHCP and tftp server configured and setup properly on your network, and is probably not for the faint of heart.

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

This worked on the {{R31}}, {{X22}}, {{T21}}, {{T30}} and {{T41p}} with various firmware updates. On the {{X22}}, it worked with ECP 1.30 but '''not''' with BIOS 1.32

= Updating without battery or with dead battery =

This is a last-resort approach. Use this only if everything else fails.

The BIOS updater may refuse to update a BIOS without a battery, or if the battery charge is too low. In that case, extract the disk image with cabextract as per instructions above and dd it to an usb stick. (This will destroy the data on it, of course.) Acquire a pure DOS boot cd such as Windows 98 recovery CD and boot that.

Use F8 to abort the boot sequence of a windows 98 boot CD. If you need CD-ROM support, load CD-related things but say no to everything else. In particular, avoid loading himem.sys and doskey, as the presence of either program causes Phoenix bios flash tool phlash16.exe to abort.

Change to the volume where flash2.exe and other tools are installed, and execute "flash2.exe /u". This should bypass the battery check and perform the flashing. If that doesn't work, check if the update disk contains a tool called "phlash16.exe". This can be used directly to flash the image, and the invocation is typically "phlash16 /exit $01c80000.fl1".

This method won't work for the Thinkpad {{560X}} (and likely other older models). Since the 560X is a bit older, it won't be a big surprise if the battery is dead as a dodo. Here's how to update the bios in this case: download the spsdi833 bios update and create the update floppy. If you have trouble creating this disk, [http://rapidshare.com/files/413598837/spsdi833-bios-560X.zip.html download an archive with the files] and put them on a floppy. Don't worry about making it bootable. Also, you will need a DOS bootdisk. A Windows 98 bootdisk will be fine. Boot the system with the W98 bootdisk, do not load CD-rom support. Remove the W98 bootdisk and put the disk with the BIOS update in the drive. If you would now run UPDTFLSH you would get the battery message, so don't do that. If you open UPDTFLSH.exe with a text editor, you would find some lines about UPDTROM. UPDTROM is the actual flash tool, but you can't simply run it just like that. Run the following:

*updtrom /np /prep1
*updtrom /np /prep2
*updtrom /np /prep3
*updtrom /np /romcmp /romflsh /prep4
*updtrom /np /h8flsh /h8img /model

Yes, you need to run updtrom five times. Hold your breath and reboot the machine. It's done.

Perhaps not all these lines are necessary, but to be sure I ran them all, and this worked for me. So I suggest you do the same. This could probably be done from the harddisk as well, but I did not test that.

=After updating=
Lenovo recommends reseting your BIOS settings to their factory defaults after a firmware update.

==DMI IDs==
Please consider updating the [[List of DMI IDs]] after updating your BIOS.

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

== Updating Thinkpad X Series ==
The special update instructions for {{X_Series}} Thinkpads are quite long. You can find them at the page [[BIOS_Upgrade/X_Series]].

----

{{footnotes|
# For lots of detail on making and burning .iso files, see The Linux Documentation Project (tldp.org): [http://tldp.org/HOWTO/CD-Writing-HOWTO-3.html#ss3.1 3.1 Writing CD-ROMs (pure data)].
}}

How to enable the integrated fingerprint reader with ThinkFinger

2007-10-17T22:07:17Z

Mgedmin: fix an obvious copy & paste error

[[How to enable the fingerprint reader]] has a good explanation for using the fingerprint reader with the closed-source binary driver. But there is also an opensource project called [http://thinkfinger.sourceforge.net ThinkFinger] which does the same, but open.

== Installing ==
=== From source ===

Download thinkfinger-0.3.tar.gz from the [http://thinkfinger.sourceforge.net/ homepage] and unpack it somewhere, make sure you have the gcc compiler, libtool, pkg-config, libusb-dev and libpam0g-dev installed, then:

{{cmduser|cd thinkfinger-0.3}}

<code style="white-space:nowrap;color:#495988;background-color:white;"><nowiki>$</nowiki> ./configure --prefix=/usr --sysconfdir=/etc --with-securedir=/lib/security --with-birdir=/etc/pam_thinkfinger</code>

{{cmduser|make}}

{{cmdroot|make install}}

{{NOTE|/lib/security is the directory, where PAM assumes its modules on Debian and openSUSE, it may vary for your distro!}}

"make install" doesn't create the birdir we specified (where thinkfinger will store users' biometric info), so create it:

{{cmdroot|mkdir /etc/pam_thinkfinger}}

If everything went OK assert that you find pam_thinkfinger.so in /lib/security typing:

{{cmduser|ls /lib/security}}

=== From package ===

==== Debian ====
[http://packages.debian.org/source/experimental/thinkfinger Packages] arrived in Debian experimental on Aug 2nd, 2007 (cf. [http://bugs.debian.org/409563 bug #409563]). To access the experimental packages via apt, add the following lines to your sources.list:
<pre>
# experimental
deb ftp://mirrors.kernel.org/debian/ experimental main contrib non-free
deb-src ftp://mirrors.kernel.org/debian/ experimental main contrib non-free
</pre>
where of course you may replace mirrors.kernel.org with your mirror of choice. Just make sure that it hosts the experimental repositories.
<pre>
aptitude update
aptitude install libthinkfinger0 libpam-thinkfinger thinkfinger-tools
</pre>
should then get you up and running.

==== Fedora/Fedora Core ====
*Packages for Fedora Core 6 are available in "extras" repository (# yum install thinkfinger).
*Packages for Fedora 7 are available in the "updates" repository (# yum install thinkfinger).

==== Gentoo ====
<pre>
emerge sys-auth/thinkfinger
</pre>

==== OpenSUSE ====
openSUSE 10.2 includes the package "libthinkfinger" (version 0.1-7) - you will find newer packages [http://beta1.suse.com/private/thoenig/10.2/thinkfinger/ here].

== Testing the driver ==

Now the driver is installed and should be working. You can try it (as root) with

{{cmdroot|tf-tool --acquire}}

and

{{cmdroot|tf-tool --verify}}

This will ask you to swipe your finger three times, save the fingerprint to /tmp/test.bir and then verify your fingerprint with the bir-file.

== Configuring PAM to use ThinkFinger ==
Now you can configure PAM to use ThinkFinger:

Open {{path|/etc/pam.d/common-auth}} (In FC6, F7, and Gentoo, this file is {{path|/etc/pam.d/system-auth}}):

{{cmdroot|nano -w /etc/pam.d/common-auth}}

Add this line before any pam_unix or pam_unix2 directives:
auth sufficient pam_thinkfinger.so

If your PAM uses the pam_unix and not the pam_unix2 module, you need to pass a specific argument in
the /etc/pam.d/common-auth directive to make it consider the password entered at the pam_thinkfinger prompt.
auth required pam_unix.so try_first_pass

For instance, {{path|/etc/pam.d/common-auth}} looks like this:
auth sufficient pam_thinkfinger.so
auth required pam_unix.so nullok_secure try_first_pass

On openSUSE 10.2, it looks like this now:
auth required pam_env.so
auth sufficient pam_thinkfinger.so
auth required pam_unix2.so

Now we are ready to add users to thinkfinger. You can add a fingerprint for a user with:

{{cmdroot|tf-tool --add-user $USERNAME}}

Now the user should be able to login with his finger instead of the password.

If you would like to use thinkfinger for su, you have to enroll the fingerprint for root user with:

{{cmdroot|tf-tool --add-user root}}

{{NOTE|You should see the "Password or swipe finger:" prompt when trying to sudo or su. If you don't, you probably do not have the "User level driver support" compiled into your kernel or the "uinput" module loaded!}}

== xscreensaver/gnome-screensaver ==
{{NOTE|In Fedora 7, the package has been modified in such a way as to make doing this unnecessary.}}

If you'd like to be able to unlock your screen using the fingerprint reader, you must have current versions of xscreesaver (>~5.03) or gnome-screensaver (>~2.18.2). Then you must give yourself access to the fingerprint reader and your bir-file, because unlike login/gdm/su/sudo, both gnome-screensaver and xscreensaver do not run as root. The following procedure will make the fingerprint reader accessible to members of the "fingerprint" group.

Make the group: {{cmdroot|groupadd fingerprint}}

Save the following as {{path|/etc/udev/rules.d/60-thinkfinger.rules}} (you may need to reboot for this to take effect):
#
# udev rules file for the thinkfinger fingerprint scanner
#
# gives access to the fingerprint reader to those in the "fingerprint" group
#

# SGS Thomson Microelectronics Fingerprint Reader
SYSFS{idVendor}=="0483", SYSFS{idProduct}=="2016", SYMLINK+="input/thinkfinger-%k", MODE="0660", GROUP="fingerprint"

# the also-needed uinput device
KERNEL=="uinput", MODE="0660", GROUP="fingerprint"

Per user:

# Add him to the group: {{cmdroot|gpasswd -a $USERNAME fingerprint}}
# Make him owner of his bir-file: {{cmdroot|chown $USERNAME:root /etc/pam_thinkfinger/$USERNAME.bir}}
# Give him read-only access to his bir-file: {{cmdroot|chmod 400 /etc/pam_thinkfinger/$USERNAME.bir}}
# Give "execute only" access to everyone for the /etc/pam_thinkfinger/ directory: {{cmdroot|chmod o+x /etc/pam_thinkfinger}} (WARNING: this opens up security a little).

== GNOME ==

gksu/gksudo doesn't work correctly. It just stays invisible. When starting a su privileged application such as synaptics you will not get prompted for the password. Nevertheless you can swipe your finger and it should authenticate you. Starting synaptics twice makes gksudo visible.

There are two possibilities to solve it:
* Changing the string "Password or swipe finger:" to a plain "Password:" (like sudo normally would do) in the file pam/pam_thinkfinger.c of the thinkfinger source directory. Of course, in the console you will then only see a "Password:" instead of "Password or swipe finger:" but this is still more usefull than having gksu/gksudo crashing everytime.
* Patching libgksu with the following patch. This is also a nasty hack until a better solution is implemented.
<pre>
--- libgksu-2.0.3/libgksu/libgksu.c.orig 2007-06-17 16:00:24.000000000 +0200
+++ libgksu-2.0.3/libgksu/libgksu.c 2007-06-17 16:00:47.000000000 +0200
@@ -2663,7 +2663,7 @@
*/
for (counter = 0; counter < 50; counter++)
{
- if (strncmp (buffer, "GNOME_SUDO_PASS", 15) == 0)
+ if (strncmp (buffer, "GNOME_SUDO_PASS", 15) == 0 || strncmp (buffer, "Password or swi", 15) == 0)
break;

read_line (parent_pipe[0], buffer, 256);
@@ -2675,7 +2675,7 @@
if (context->debug)
fprintf (stderr, "brute force GNOME_SUDO_PASS ended...\n");

- if (strncmp(buffer, "GNOME_SUDO_PASS", 15) == 0)
+ if (strncmp(buffer, "GNOME_SUDO_PASS", 15) == 0 || strncmp(buffer, "Password or swi", 15) == 0)
{
gchar *password = NULL;
gboolean prompt_grab;
</pre>

== KDE ==

Integration in KDE and kdm seems not to be easily possible now. There is a filed [https://bugs.kde.org/show_bug.cgi?id=116682 bug] at kde.org where you can vote for this.

Moreover, kdm in openSUSE 10.3 crashes when pam_thinkfinger is enabled. A possible "workaround" is downgrading to thinkfinger 0.2.2.

This Howto was copied from [[Installing Ubuntu 6.06 on a ThinkPad T43#Fingerprint_Reader]] and then slightly modified.

Talk:Ultrabay Slim Super Multi-Burner Drive

2007-08-18T21:11:29Z

Mgedmin:

I doubt it could be the Matshita UJ-846-B, because that is a 12.7mm drive. Ultrabay Slim takes 9.5mm drives.

My T61 came with a multi-burner. The software (dmesg, /proc/scsi/scsi, wodim) sees it as a "HL-DT-ST DVDRAM GSA-U10N". Is that the same as Hitachi-LG Data Storage Inc. GSA-4083N, or a different model?

There are three logos on the drive itself: DVD, multi-recorder, and CD-RW. This might be help other people figure out whether they have a multi-burner or a DVD/CD-RW combo (the separate CD-RW logo misled me).

Intel 82801H HDA

2007-08-10T18:58:18Z

Mgedmin:

=== Intel High Definition Audio ===
Intel audio controller embedded with the 82801H chipset ( ICH8 chipset )

=== Features ===
* Chipset: 82801H
* Interface: PCIe
* PCI ID: 8086:284b

=== Linux ALSA driver ===

See [[AD1984]].

=== ThinkPads this chip may be found in ===
* {{T61}}
* {{R61}}
* {{X61s}}
* {{X61}}

[[Category:Components]]

Intel 82801H HDA

2007-08-10T18:57:52Z

Mgedmin:

=== Intel High Definition Audio ===
Intel audio controller embedded with the 82801H chipset ( ICH8 chipset )

=== Features ===
* Chipset: 82801H
* Interface: PCIe
* PCI ID: 8086:284b

=== Linux ALSA driver ===

See {{AD1984}}

=== ThinkPads this chip may be found in ===
* {{T61}}
* {{R61}}
* {{X61s}}
* {{X61}}

[[Category:Components]]

Talk:Installing Ubuntu 7.10 (Gutsy Gibbon) Tribe 3 on a ThinkPad T61

2007-08-09T12:13:34Z

Mgedmin:

{{HELP|This procedure is not working for me. It successfully activates the wireless card, and my network manager detects the signal from the router (great!). When I click to connect to this network, a progress bubble appears, reaches 28%, with the words "Activation stage: Configuring device." The process halts there. I have what I think is a kernel panic, although I guess it could be a hard xorg crash (mouse won't move, nothing changes on-screen, VTs refuse to appear, X zap doesn't work, etc.) Anyone have a suggestion?}}

The iwl4965 driver (Version 0.42 I think) is now included with Gutsy, you might want to remove all the firmware you installed and then reinstall linux-ubuntu-modules-2.6.22 and try that.

== Cannot boot Tribe 3 with T61 ==

I'm couldn't get Gutsy Tribe 3 CD to boot on my new widescreen T61 with Intel graphics (1280x800). Normal boot (or "safe graphics mode") gave me an initramfs shell with no explanation, selecting VGA 1024x768x32 (and the others) gave me a blank screen (with backlight on). Interestingly, when I connected an external 1280x1024 monitor before booting, the VGA popup offered that mode to me, but without it it never offered 1280x800, just 1024x768.

The Alternative install CD was somewhat better, but once it got to the actual installation step, at about 9% of the progress bar, where it installed xresprobe (IIRC), the screen suddenly went blank. I finished the installation blindly, by pressing Enter whenever the CD spun down. The system booted and detected the widescreen resolution just fine, with the minor TV-out caveat.

Note that using the monitor-TV workaround breaks xrandr, which then complains that "output TV is connected but has no modes".

Also note that to get working WiFi I had to go into the BIOS setup and set "Internal Wireless Radio Frequency" to On.

-- Marius Gedminas, 2007-08-09

Answer from DA
Try this: "When the system boots hit F1 to enter the Bios, select Config->Serial ATA (SATA) and set the SATA Controller mode option to "Compatibility"."
Or
"Must install using the alternate CD or the regular CD and hit F4 to change VGA settings to 1024x768x32 and use regular install."

These were older instructions that probably still apply if you are using Tribe 3.

Talk:Installing Ubuntu 7.10 (Gutsy Gibbon) Tribe 3 on a ThinkPad T61

2007-08-08T18:13:45Z

Mgedmin:

Talk:Installing Ubuntu 7.10 (Gutsy Gibbon) Tribe 3 on a ThinkPad T61

2007-08-08T15:30:25Z

Mgedmin: Cannot boot Tribe 3 with T61

Table of thinkpad-acpi LEDs

2006-10-23T21:06:36Z

Mgedmin: tested LEDs on my T42

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

To test please do the following and add the blinking LED to the table.

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

<div style="font-size: 92%">
{| border="1" cellspacing="0" cellpadding="2"
|+ibm-acpi LED table
|-
! ×
! LED #0
! LED #1
! LED #2
! LED #3
! LED #4
! LED #5
! LED #6
! LED #7
! ThinkLight
! Notes
|-
! colspan=11 style="text-align:center;background:#efefef;" |
|-
! {{A22p}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{A30}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! colspan=11 style="text-align:center;background:#efefef;" |
|-
! {{G41}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! colspan=11 style="text-align:center;background:#efefef;" |
|-
! [[:Category:R31|R31]]
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{R40}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{R50}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{R50p}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{R50e}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || Amber ||
|-
! {{R51}}
| Power || Battery(orange) || Battery(green) || {{Cunk}} || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || Amber || 2883-ELU
|-
! {{R52}}
| Power(green) || Battery(orange) || Battery(green) || {{Cunk}} || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || {{Cunk}} ||
|-
! {{R60}}
| Power || Battery(orange) || Battery(green) || {{Cunk}} || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || Amber ||
|-

! colspan=11 style="text-align:center;background:#efefef;" |

|-
! {{T20}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{T22}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{T23}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{T30}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{T40}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{T40p}}
| Power || Battery(orange) || Battery(green) || {{Cunk}} || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || White ||
|-
! {{T41}}
| Power || Battery(orange) || Battery(green) || {{Cunk}} || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || White || 2373-2gg
|-
! {{T41p}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{T42}}
| Power || Battery (orange) || Battery (green) || {{Cunk}} || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || White ||
|-
! {{T42p}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{T43}}, {{T43p}}
| Power || Battery (orange) || Battery (green) || {{Cunk}} || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || White ||
|-
! {{T60}}
| Power || Battery(orange) || Battery(green) || {{Cunk}} || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || {{Cunk}} || 2007-49G
|-
! colspan=11 style="text-align:center;background:#efefef;" |

|-
! {{X20}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{X24}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{X31}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{X32}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{X40}}
| Power || Battery(orange) || Battery(green) || Ultrabase || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || {{Cunk}} ||
|-
! {{X41}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{X60}}
| Power || Battery(orange) || Battery(green) || Ultrabase || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || {{Cunk}} ||
|-
! colspan=11 style="text-align:center;background:#efefef;" |

|-
! {{Z60t}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{Z61m}}
| Power || Battery(orange) || Battery(green) || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || Standby || {{Cunk}} ||
</div>

List of DMI IDs

2006-07-25T10:06:26Z

Mgedmin: /* T series */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
This page maintains a database of [http://en.wikipedia.org/wiki/Desktop_Management_Interface DMI] information which can be used to identify ThinkPad models. It is intended as an aid for driver development.
{{HELP|We need more information about older models, especially those released before 2004. Please [[#Adding_entries|add your model]] to the database.}}
|}

==DMI ID database==

<div style="font-size: 80%">
{| border="1" cellspacing="0" cellpadding="2"
|-
! Model
! <tt>system- manufa cturer</tt>
! <tt>system- product- name</tt>
! <tt>system- version</tt>
! <tt>baseboard- manufa cturer</tt>
! <tt>baseboard- product- name</tt>
! <tt>baseboard- version</tt>
! <tt>chassis- manufa cturer</tt>
! <tt>chassis- version</tt>
! <tt>bios- vendor</tt>
! <tt>bios- version</tt>
! <tt>bios- release- date</tt>
! Embedded controller
! Notes
|-
! colspan=14 style="text-align:center;background:#efefef;" |
====Numbered series====
|-
| {{600E}} 2645-5AU
|| IBM || 26455AU || Not Available || IBM || 26455AU || Not Available || IBM || Not Available || IBM || INET36WW || 11/20/1999
|| <nowiki></nowiki> ||
|-
! colspan=14 style="text-align:center;background:#efefef;" |
====A series====
|-
| {{A22p}} 2629-USG
|| IBM || 2629USG || Not Available || IBM || 2629USG || Not Available || IBM || Not Available || IBM || KYET36WW (1.09a) || 10/17/2002
|| ||
|-
! colspan=14 style="text-align:center;background:#efefef;" |
====G series====
|-
| {{G41}} 2881-75M
|| IBM || 288175M || ThinkPad G41 || IBM || 288175M || Not Available || IBM || Not Available || IBM || 1XET47WW (1.06 ) || 01/14/2005
|| <nowiki></nowiki> ||
|-
! colspan=14 style="text-align:center;background:#efefef;" |
====R series====
|-
| {{R40}} 2681-5UU
|| IBM || 26815UU || Not Available || IBM || 26815UU || Not Available || IBM || Not Available || IBM || 1OET57WW (1.23 ) || 03/23/2005
|| <nowiki></nowiki> ||
|-
| {{R52}} 1846-AQG
|| IBM || 1846AQG || ThinkPad H || IBM || 1846AQG || Not Available || IBM || Not Available || IBM || 76ET58WW (1.18 ) || 07/19/2005
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[76HT14WW-1.04 ]-</nowiki> || weird system version
|-
| {{R52}} 1846-AQG
|| IBM || 1846AQG || ThinkPad R52 || IBM || 1846AQG || Not Available || IBM || Not Available || IBM || 76ET65WW (1.25 ) || 05/18/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[76HT16WW-1.06 ]-</nowiki> ||
|-
| {{R51}} 1829-9MG
|| IBM || 18299MG || ThinkPad R51 || IBM || 18299MG || Not Available || IBM || Not Available || IBM || 1RETDOWW (3.20 ) || 02/27/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki> ||
|-
| {{R51}} 1829-L7G
|| IBM || 1829L7G || ThinkPad R51 || IBM || 1829L7G || Not Available || IBM || Not Available || IBM || 1RETDNWW (3.19 ) || 10/13/2005
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[1RHT70WW-3.03 ]-</nowiki> ||
|-
| {{R51}} 2883-ELU
|| IBM || 2883ELU || ThinkPad R51 || IBM || 2883ELU || Not Available || IBM || Not Available || IBM || 1VET69WW (1.27 ) || 03/03/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[1VHT28WW-1.04 ]-</nowiki> ||
|-
! colspan=14 style="text-align:center;background:#efefef;" |
====T series====
|-
| {{T40}} 2378-D2U
|| IBM || 2378D2U || ThinkPad T40 || IBM || 2378D2U || Not Available || IBM || Not Available || IBM || 1RETC2WW (3.03 ) || 04/07/2004
|| <nowiki></nowiki> ||
|-
| {{T40p}} 2373-G1G
|| IBM || 2373G1G || ThinkPad T40p || IBM || 2373G1G || Not Available || IBM || Not Available || IBM || 1RETDPWW (3.21 ) || 06/02/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki> ||
|-
| {{T41}} 23732FG
|| IBM || 23732FG || ThinkPad T41 || IBM || 23732FG || Not Available || IBM || Not Available || IBM || 1RET84WW (2.11 ) || 10/30/2003
|| <nowiki></nowiki> ||
|-
| {{T42}} 2373FWG
|| IBM || 2373FWG || ThinkPad T42 || IBM || 2373FWG || Not Available || IBM || Not Available || IBM || 1RETDHWW (3.13 ) || 10/29/2004
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki> ||
|-
| {{T42p}} 2373GYG
|| IBM || 2373GYG || ThinkPad T42p || IBM || 2373GYG || Not Available || IBM || Not Available || IBM || 1RETDOWW (3.20 ) || 02/27/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki> ||
|-
| {{T43}} 2686-DGU
|| IBM || 2686DGU || ThinkPad T43 || IBM || 2686DGU || Not Available || IBM || Not Available || IBM || 1YET62WW (1.27 ) || 05/18/2006
|| String 1: IBM ThinkPad Embedded Controller -[1YHT29WW-1.06 ]- ||
|-
| {{T43p}} 2668-G2G
|| IBM || 2668G2G || ThinkPad T43p || IBM || 2668G2G || Not Available || IBM || Not Available || IBM || 1YET47WW (1.08 ) || 06/09/2005
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[1YHT26WW-1.03 ]-</nowiki> ||
|-
| {{T60}} 2007-49G
|| LENOVO || 200749G || ThinkPad T60 || LENOVO || 200749G || Not Available || LENOVO || Not Available || LENOVO || 79ET62WW (1.07 ) || 06/12/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[79HT45WW-1.04 ]-</nowiki> ||
|-
| {{T60p}} 2007-83U
|| LENOVO || 200783U || ThinkPad T60p || LENOVO || 200783U || Not Available || LENOVO || Not Available || LENOVO || 79ET60WW (1.05a) || 04/18/2006 || <nowiki> String 1: IBM ThinkPad Embedded Controller -[79HT43WW-1.02 ]-</nowiki> ||
|-
|{{T41}} 2373-XNX
|| IBM || 2373XNX || ThinkPad T41 || IBM || 2373XNX || Not Available || IBM || Not Available || IBM || 1RETDOWW (3.20 ) || 02/27/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki> ||
|-
! colspan=14 style="text-align:center;background:#efefef;" |

====X series====
|-
| {{X60}} 1709-47U
|| LENOVO || 170947U || ThinkPad X60 || LENOVO || 170947U || Not Available || LENOVO || Not Available || LENOVO || 7BET44WW (1.04 ) || 03/13/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[7BHT29WW-1.02 ]-</nowiki> ||
|-
| {{X60s}} 1702-55G
|| LENOVO || 170255G || ThinkPad X60s || LENOVO || 170255G || Not Available || LENOVO || Not Available || LENOVO || 7BET44WW (1.04 ) || 03/13/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[7BHT29WW-1.02 ]-</nowiki> ||
|-
! colspan=14 style="text-align:center;background:#efefef;" |
====Z series====
|-
| {{Z60m}} 2529-FKG
|| IBM || 2529FKG || ThinkPad Z60m || IBM || 2529FKG || Not Available || IBM || Not Available || IBM || 77ET42WW (1.05 ) || 11/19/2005
|| String 1: IBM ThinkPad Embedded Controller -[77HT28WW-1.02 ]- ||
|-
| {{Z61m}} 9453-A11
|| LENOVO || 9453A11 || ThinkPad Z61m || LENOVO || 9453A11 || Not Available || LENOVO || Not Available || LENOVO || 7FET48WW (1.08 ) || 05/26/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[7FHT21WW-1.03 ]-</nowiki> ||
|-
| {{Z60t}} 2511-FEU
|| IBM || 2511FEU || ThinkPad Z60t || IBM || 2511FEU || Not Available || IBM || Not Available || IBM || 77ET42WW (1.05 ) || 11/19/2005
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[77HT28WW-1.02 ]-</nowiki> ||

|}
</div>

==Adding entries==

Click the "Edit" link on the appropriate series above and add an entry of the following form:
:<tt>!-</tt>
:<tt>| </tt>description of your model
:data line 1
:data line 2

where the two data lines are genereated by the following <tt>bash</tt> command:

<pre>
for X in system-{manufacturer,product-name,version} \
baseboard-{manufacturer,product-name,version} \
chassis-{manufacturer,version} bios-{vendor,version,release-date}; do \
echo -n "|| `sudo /usr/sbin/dmidecode -s $X` "; done; echo; \
echo "|| <nowiki><nowiki>`sudo /usr/sbin/dmidecode | grep -i 'embedded controller'`</nowiki></nowiki> ||"
</pre>

==Software using ThinkPad DMI IDs==
* [[HDAPS]] driver whitelist
* [[tp_smapi]] driver whitelist

Talk:2373-FWG

2005-10-19T07:35:14Z

Mgedmin:

What is "Cache size", exactly? Is it the size of the L1 or the L2 cache? My T40 2373-FWG has 2 megs of L2 cache integrated into the CPU.

Talk:Installing Ubuntu/Breezy on a ThinkPad T42

2005-10-19T07:33:16Z

Mgedmin: Using Fn-F6 to enable/disable Bluetooth

Why is it important to turn off dynamicClocks in radeonfb in kernels before 2.6.14?

What is wrong with the wireless on/off script that comes with Breezy and is mapped to Fn-F5 out of the box? Why replace it?

Why use noflushd when Breezy comes with laptop-mode? Just enable it in /etc/default/acpi-support.

== Using Fn-F6 to enable/disable Bluetooth ==

First, to make sure Fn-F6 is available as a hotkey, either do

echo 0xffff > /proc/acpi/ibm/hotkey

(this will work until next reboot or suspend), or change the mask in /etc/modprobe.d/ibm_acpi.modprobe.

Next, create a shell script /etc/acpi/bluetooth.sh:

#!/bin/bash
# Enable/disable builtin Bluetooth on IBM Thinkpads
if grep -q enabled /proc/acpi/ibm/bluetooth; then
echo disable > /proc/acpi/ibm/bluetooth
else
echo enable > /proc/acpi/ibm/bluetooth
fi

Next, create an event file /etc/acpi/events/ibm-bluetooth

# This is called when the user presses Fn-F6 button and calls
# /etc/acpi/bluetooth.sh for further processing.
event=ibm/hotkey HKEY 00000080 00001006
action=/etc/acpi/bluetooth.sh

You might need to restart acpid for it to start working.

Talk:Installing Ubuntu/Breezy on a ThinkPad T42

2005-10-19T07:29:49Z

Mgedmin: Questions

Installing Ubuntu/Breezy on a ThinkPad T42

2005-10-19T07:26:07Z

Mgedmin: Typo

==Generel installation==
Here comes installation instructions for {{Ubuntu}} Breezy Badger on
{{T42}} 2374-ZEP.

Get a copy of Ubuntu from [http://www.ubuntulinux.org UbuntuLinux.org].

==Kernel support==
How to get the correct kernel:
{{cmduser|sudo apt-get linux-686}}

===Kernel modules===
{{Todo|Load the different kernel modules, and their configuration}}

Important to turn off dynamicClocks in radeonfb in kernels before 2.6.14:
{{path|/etc/modprobe.d/radeonfb.modprobe}}:
options radeonfb default_dynclk=-1

ibm_acpi module:

Turning on experimental features:
{{path|/etc/modprobe.d/ibm_acpi.modprobe}}:
options ibm_acpi hotkey=enable,0xff9f experimental=1

Starting with wireless off:
{{path|/etc/modprobe.d/ipw2100.modprobe}}:
options ipw2100 disable=1

====ibm_acpi modules compilation====
Kernel 2.6.12-9 included in Breezy only included ibm_acpi version 0.8. However a version 0.11 is available, and included in 2.6.13.

[http://bugme.osdl.org/show_bug.cgi?id=4947 http://bugme.osdl.org/show_bug.cgi?id=4947]

===ACPI===
{{Todo|Hibernate, suspend, buttons, lid, speedstep}}

Modification to turn on wireless:
{{path|/etc/acpi/wireless.sh}}:
#!/bin/bash
# Find and enable/disable wireless devices

for DEVICE in /sys/class/net/*; do
if [ -d $DEVICE/wireless ]; then
# $DEVICE is a wireless device. Check if it's powered on:
if [ `cat $DEVICE/device/power/state` = 0 ]; then
# It's powered on. Switch it off.
echo -n 3 > $DEVICE/device/power/state;
echo 0
else
# It's powered off. Switch it on.
echo -n 0 > $DEVICE/device/power/state;
echo -n 0 > $DEVICE/device/rf_kill;
echo 1
fi
fi
done

==Xorg==

Relevant part:
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "Emulate3Buttons" "true"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
Identifier "Synaptics Touchpad"
Driver "synaptics"
Option "SendCoreEvents" "true"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "HorizScrollDelta" "0"
EndSection

Section "Device"
Identifier "ATI Technologies, Inc. Radeon Mobility 7500 (M7 LW)"
Driver "radeon"
BusID "PCI:1:0:0"
Option "DynamicClocks" "off"
Option "AGPMode" "4"
Option "AGPFastWrite" "yes"
EndSection

{{WARN|Options DynamicClocks "on" may hang your machine}}

==Initng==
Very great initiative for optimizing the boot process. [http://initng.thinktux.net/index.php/Main_Page Initng]

Dep packages can be found:
[http://alioth.debian.org/projects/pkg-initng/ http://alioth.debian.org/projects/pkg-initng/]

Installation:
{{cmduser|sudo dpkg -i initng_0.3.3-2_i386.deb}}

To run nice a few things and scripts need modification as follows:

====Kernel options====

To enable initng an option must be appended to the kernel load command in grub.

{{path|/boot/grub/menu.lst}}:
kernel /vmlinuz-2.6.12-9-686 root=/dev/hda9 ro quiet splash video=radeonfb init=/sbin/initng

====Runlevel====
{{path|/etc/initng/default.runlevel}}:
system
daemon/acpid
daemon/dbus
daemon/hald
daemon/vixie-cron
daemon/ifplugd
system/alsasound
system/speedstep
system/laptop-mode
daemon/syslogd
daemon/klogd
daemon/gdm
daemon/hpiod
daemon/cupsd
daemon/powernowd

===Scripts===
====dbus.i====
{{path|daemon/dbus.i}} has a few faults, on Ubuntu it is "dbus" not "dbus-1"!
service daemon/dbus {
need = system/initial system/mountfs system/bootmisc

pid_file = /var/run/dbus/pid
daemon {
DAEMON=/usr/bin/dbus-daemon
NAME=dbus
DAEMONUSER=messagebus
PIDDIR=/var/run/dbus
PIDFILE=$PIDDIR/pid
DESC="system message bus"

if [ -e /etc/default/dbus ]; then
. /etc/default/dbus
fi

if [ ! -d $PIDDIR ]; then
mkdir -p $PIDDIR
chown $DAEMONUSER $PIDDIR
chgrp $DAEMONUSER $PIDDIR
fi
if [ -e $PIDFILE ]; then
PIDDIR=/proc/$(cat $PIDFILE)
if [ -d ${PIDDIR} -a "$(readlink -f ${PIDDIR}/exe)" = "${DAEMON}" ]; then
echo "$DESC already started; not starting."
else
echo "Removing stale PID file $PIDFILE."
rm -f $PIDFILE
fi
fi
echo -n "Starting $DESC: "
$DAEMON --system $PARAMS
echo "$NAME."
}
}

====hald.i====
{{path|daemon/hald.i}}
service daemon/hald {
need = system/initial system/mountfs daemon/dbus
# use = daemon/acpid

daemon {
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
DAEMON=/usr/sbin/hald
PIDDIR=/var/run/hal
NAME=hal
DAEMONUSER=hal
DESC="Hardware abstraction layer"

if [ -f /etc/default/hal ] ; then
. /etc/default/hal
fi

if [ ! -d $PIDDIR ]; then
mkdir -p $PIDDIR
chown $DAEMONUSER:$DAEMONUSER $PIDDIR
fi

echo -n "Starting $DESC: "
$DAEMON --daemon=no $DAEMON_OPTS
echo "$NAME."
}
}

====gdm.i====

{{path|daemon/gdm.i}}, to add locale support to the GDM login screen:
service daemon/gdm {
need = system/initial system/mountfs system/hostname net/lo system/modules system/bootmisc
use = daemon/xfs system/static-modules system/coldplug system/netmount
# daemon = /usr/sbin/gdm
# daemon = /usr/bin/gdm
# daemon_args = -nodaemon
daemon {
PATH=/bin:/sbin:/usr/bin:/usr/sbin
if [ -r /etc/default/gdm ]; then
. /etc/default/gdm
if [ -z "$LANG" ]; then
:
else
export LANG
fi
fi

gdm -nodaemon
}
#pid_file = /var/run/gdm.pid
}

==Helpfull tools==
===Rovclock===
Utility to overclock and underclock the ATI radeon chip.
Can be used to underclock to reduce power, especialy when on batteries.

Get it from: [http://www.hasw.net/linux/ http://www.hasw.net/linux/]

Stable clock speeds:
Core: 100MHz
Memory: 120Mhz for LCP only, 180Mhz when using DVI out on port replicator.

Ex:
{{cmduser|sudo rovclock -c 100 -m 120}}

===noflushd===
Noflushd is a daemon that spins down disks that have not been read from
after a certain amount of time, and then prevents disk writes from
spinning them back up. It's targeted for laptops but can be used on any
computer with IDE disks. The effect is that the hard disk actually spins
down, saving you battery power, and shutting off the loudest component of
most computers.
{{cmduser|sudo apt-get noflushd}}

===ifplugd===
ifplugd is a daemon which will automatically configure your
ethernet device when a cable is plugged in and automatically
unconfigure it if the cable is pulled. This is useful on laptops with
onboard network adapters, since it will only configure the interface
when a cable is really connected.
{{cmduser|sudo apt-get ifplugd}}

{{path|/etc/default/ifplugd}}:
INTERFACES="eth0"
HOTPLUG_INTERFACES="eth0"
ARGS="-q -f -u0 -d10 -w -I -b"
SUSPEND_ACTION="stop"

===gnubiff===

gnubiff is a mail notification program that checks for mail and displays headers when new mail has arrived. Has a tray icon for gnome. Supports SSL which I needed.
[http://gnubiff.sourceforge.net/ http://gnubiff.sourceforge.net/]

{{cmduser|sudo apt-get install gnubiff}}

==Known problems==
{{Todo|List of bugs from kernel, Xorg and Ubuntu}}

Installing Ubuntu/Breezy on a ThinkPad T42

2005-10-19T07:25:37Z

Mgedmin: Fix kernel package name

==Generel installation==
Here comes installation instructions for {{Ubuntu}} Breezy Badger on
{{T42}} 2374-ZEP.

Get a copy of Ubuntu from [http://www.ubuntulinux.org UbuntuLinux.org].

==Kernel support==
How to get the correct kernel:
{{cmduser|sudo apt-get linux-686}}

===Kernel modules===
{{Todo|Load the different kernel modules, and their configuration}}

Importent to turn off dynamicClocks in radeonfb in kernels before 2.6.14:
{{path|/etc/modprobe.d/radeonfb.modprobe}}:
options radeonfb default_dynclk=-1

ibm_acpi module:

Turning on experimental features:
{{path|/etc/modprobe.d/ibm_acpi.modprobe}}:
options ibm_acpi hotkey=enable,0xff9f experimental=1

Starting with wireless off:
{{path|/etc/modprobe.d/ipw2100.modprobe}}:
options ipw2100 disable=1

====ibm_acpi modules compilation====
Kernel 2.6.12-9 included in Breezy only included ibm_acpi version 0.8. However a version 0.11 is available, and included in 2.6.13.

[http://bugme.osdl.org/show_bug.cgi?id=4947 http://bugme.osdl.org/show_bug.cgi?id=4947]

===ACPI===
{{Todo|Hibernate, suspend, buttons, lid, speedstep}}

Modification to turn on wireless:
{{path|/etc/acpi/wireless.sh}}:
#!/bin/bash
# Find and enable/disable wireless devices

for DEVICE in /sys/class/net/*; do
if [ -d $DEVICE/wireless ]; then
# $DEVICE is a wireless device. Check if it's powered on:
if [ `cat $DEVICE/device/power/state` = 0 ]; then
# It's powered on. Switch it off.
echo -n 3 > $DEVICE/device/power/state;
echo 0
else
# It's powered off. Switch it on.
echo -n 0 > $DEVICE/device/power/state;
echo -n 0 > $DEVICE/device/rf_kill;
echo 1
fi
fi
done

==Xorg==

Relevant part:
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "Emulate3Buttons" "true"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
Identifier "Synaptics Touchpad"
Driver "synaptics"
Option "SendCoreEvents" "true"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "HorizScrollDelta" "0"
EndSection

Section "Device"
Identifier "ATI Technologies, Inc. Radeon Mobility 7500 (M7 LW)"
Driver "radeon"
BusID "PCI:1:0:0"
Option "DynamicClocks" "off"
Option "AGPMode" "4"
Option "AGPFastWrite" "yes"
EndSection

{{WARN|Options DynamicClocks "on" may hang your machine}}

==Initng==
Very great initiative for optimizing the boot process. [http://initng.thinktux.net/index.php/Main_Page Initng]

Dep packages can be found:
[http://alioth.debian.org/projects/pkg-initng/ http://alioth.debian.org/projects/pkg-initng/]

Installation:
{{cmduser|sudo dpkg -i initng_0.3.3-2_i386.deb}}

To run nice a few things and scripts need modification as follows:

====Kernel options====

To enable initng an option must be appended to the kernel load command in grub.

{{path|/boot/grub/menu.lst}}:
kernel /vmlinuz-2.6.12-9-686 root=/dev/hda9 ro quiet splash video=radeonfb init=/sbin/initng

====Runlevel====
{{path|/etc/initng/default.runlevel}}:
system
daemon/acpid
daemon/dbus
daemon/hald
daemon/vixie-cron
daemon/ifplugd
system/alsasound
system/speedstep
system/laptop-mode
daemon/syslogd
daemon/klogd
daemon/gdm
daemon/hpiod
daemon/cupsd
daemon/powernowd

===Scripts===
====dbus.i====
{{path|daemon/dbus.i}} has a few faults, on Ubuntu it is "dbus" not "dbus-1"!
service daemon/dbus {
need = system/initial system/mountfs system/bootmisc

pid_file = /var/run/dbus/pid
daemon {
DAEMON=/usr/bin/dbus-daemon
NAME=dbus
DAEMONUSER=messagebus
PIDDIR=/var/run/dbus
PIDFILE=$PIDDIR/pid
DESC="system message bus"

if [ -e /etc/default/dbus ]; then
. /etc/default/dbus
fi

if [ ! -d $PIDDIR ]; then
mkdir -p $PIDDIR
chown $DAEMONUSER $PIDDIR
chgrp $DAEMONUSER $PIDDIR
fi
if [ -e $PIDFILE ]; then
PIDDIR=/proc/$(cat $PIDFILE)
if [ -d ${PIDDIR} -a "$(readlink -f ${PIDDIR}/exe)" = "${DAEMON}" ]; then
echo "$DESC already started; not starting."
else
echo "Removing stale PID file $PIDFILE."
rm -f $PIDFILE
fi
fi
echo -n "Starting $DESC: "
$DAEMON --system $PARAMS
echo "$NAME."
}
}

====hald.i====
{{path|daemon/hald.i}}
service daemon/hald {
need = system/initial system/mountfs daemon/dbus
# use = daemon/acpid

daemon {
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
DAEMON=/usr/sbin/hald
PIDDIR=/var/run/hal
NAME=hal
DAEMONUSER=hal
DESC="Hardware abstraction layer"

if [ -f /etc/default/hal ] ; then
. /etc/default/hal
fi

if [ ! -d $PIDDIR ]; then
mkdir -p $PIDDIR
chown $DAEMONUSER:$DAEMONUSER $PIDDIR
fi

echo -n "Starting $DESC: "
$DAEMON --daemon=no $DAEMON_OPTS
echo "$NAME."
}
}

====gdm.i====

{{path|daemon/gdm.i}}, to add locale support to the GDM login screen:
service daemon/gdm {
need = system/initial system/mountfs system/hostname net/lo system/modules system/bootmisc
use = daemon/xfs system/static-modules system/coldplug system/netmount
# daemon = /usr/sbin/gdm
# daemon = /usr/bin/gdm
# daemon_args = -nodaemon
daemon {
PATH=/bin:/sbin:/usr/bin:/usr/sbin
if [ -r /etc/default/gdm ]; then
. /etc/default/gdm
if [ -z "$LANG" ]; then
:
else
export LANG
fi
fi

gdm -nodaemon
}
#pid_file = /var/run/gdm.pid
}

==Helpfull tools==
===Rovclock===
Utility to overclock and underclock the ATI radeon chip.
Can be used to underclock to reduce power, especialy when on batteries.

Get it from: [http://www.hasw.net/linux/ http://www.hasw.net/linux/]

Stable clock speeds:
Core: 100MHz
Memory: 120Mhz for LCP only, 180Mhz when using DVI out on port replicator.

Ex:
{{cmduser|sudo rovclock -c 100 -m 120}}

===noflushd===
Noflushd is a daemon that spins down disks that have not been read from
after a certain amount of time, and then prevents disk writes from
spinning them back up. It's targeted for laptops but can be used on any
computer with IDE disks. The effect is that the hard disk actually spins
down, saving you battery power, and shutting off the loudest component of
most computers.
{{cmduser|sudo apt-get noflushd}}

===ifplugd===
ifplugd is a daemon which will automatically configure your
ethernet device when a cable is plugged in and automatically
unconfigure it if the cable is pulled. This is useful on laptops with
onboard network adapters, since it will only configure the interface
when a cable is really connected.
{{cmduser|sudo apt-get ifplugd}}

{{path|/etc/default/ifplugd}}:
INTERFACES="eth0"
HOTPLUG_INTERFACES="eth0"
ARGS="-q -f -u0 -d10 -w -I -b"
SUSPEND_ACTION="stop"

===gnubiff===

gnubiff is a mail notification program that checks for mail and displays headers when new mail has arrived. Has a tray icon for gnome. Supports SSL which I needed.
[http://gnubiff.sourceforge.net/ http://gnubiff.sourceforge.net/]

{{cmduser|sudo apt-get install gnubiff}}

==Known problems==
{{Todo|List of bugs from kernel, Xorg and Ubuntu}}

Rescue and Recovery

2005-10-19T07:21:09Z

Mgedmin: Fix wrapping of the warning; mention another GRUB boot success; mention T42

Rescue and Recovery version 3.0 consists of a bootable partition containing various system recovery tools, including full recovery of the preinstalled Windows XP partition. It can be activated by pressing the {{ibmkey|ThinkPad|#494949}}, {{ibmkey|Access IBM|#495988}} or {{ibmkey|ThinkVantage|#495988}} [[ThinkPad Button|Button]] during system boot. It contains a FAT filesystem (labeled "IBM_SERVICE"), and has partition type 0x12 ("Compaq diagnostics" in <tt>fdisk</tt>).

{{WARN|Consideration 6 of the Readme states:

The Master Boot Record (MBR) must be configured properly for the Rescue and Recovery application to function properly. When possible, the Rescue and Recovery application attempts to ensure the proper configuration of the BR. This can only occur if the Rescue and Recovery application is installed after other applications that requires the MBR.}}

Apparently, the MBR is not "configured properly" if LILO or GRUB has been installed in it. It is not known how to invoke Rescue and Recovery once LILO or GRUB has been installed in the MBR. There is one [http://sharadware.com/2005/07/11/suse-linux-winxp-access-ibm-on-the-thinkpad-t43/#comment-165 report] of success after changing the partition type from 0x12 to 0x0b (FAT32). Others have also reported success with this method (see the discussion page of this article).

==External Sources==
* IBM page on [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4Q2QAK ThinkVantage Rescue and Recovery].
* [ftp://ftp.software.ibm.com/pc/pccbbs/thinkvantage_en/tvtrnr3_1027en.txt Rescue and Recovery Readme]

==Models featuring this technology==
* ThinkPad {{T42}}
* ThinkPad {{T43}}, {{T43p}}
* ThinkPad {{R52}}

Talk:Rescue and Recovery

2005-10-19T07:18:27Z

Mgedmin: Success booting R&R from GRUB

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

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

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

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

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

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

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

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

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

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

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

But chances are this is a pointless hack ...

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

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

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

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

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

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

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

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

----

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

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

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

== Success booting R&R from GRUB ==

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

You can do that with GRUB:

parttype (hd0,1) 0x0b

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

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

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

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