ThinkWiki - User contributions [en]

Category:W510

2011-08-16T09:02:26Z

Xdeller: /* Hardware notes */

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== ThinkPad W510 ===

==== Standard Features ====

* One of the following [[Intel Core i7]] processors:
** Intel Quad Core Processor i7 720QM (1.6GHz 1066MHz 6MB L3)
** Intel Quad Core Processor i7 820QM (1.73GHz 1066MHz 8MB L3)
** Intel Quad Core Extreme Processor i7-920XM (2.0GHz 1333MHz 8MB L3)
* [[NVIDIA Quadro FX 880M]] with 1GB DDR3
* One of the following [[TFT display|TFT displays]]:
** 15.6" TFT display with 1366x768 (HD) resolution with LED backlight
** 15.6" TFT display with 1600x900 (HD+) resolution with LED backlight
** 15.6" TFT display with 1920x1080 (FHD) resolution with LED backlight
** 15.6" TFT display with 1920x1080 (FHD) resolution with LED backlight Multi Touch
* 2GB (1 DIMM) or 4GB (2 DIMMs) [[PC3-10600]] memory standard upgradable to 16GB (4 DIMM slots)
*One of the following storage options:
** 320GB 7200rpm 2.5" SATA HDD Available with [[Full Disk Encryption (FDE)]]
** 320GB 7200rpm 2.5" SATA HDD
** 500GB 7200rpm 2.5" SATA HDD
** 128GB 1.8" SATA SSD
** 160GB 1.8" SATA SSD
** 256GB 1.8" SATA SSD
* [[Intel Gigabit Ethernet (10/100/1000) PCI-Express]]
* Intel HD Audio with a [[CX20585]] codec
* [[ThinkPad Modem (MDC-3.0, 56kbps HDA)]]
* [[Ultrabay|Ultrabay Enhanced]] with one of the following:
** [[Serial UltraBay Enhanced DVD Burner II]]
* [[MiniPCI Express slot]] 1 with one of the following:
** [[Intel Centrino Ultimate-N 6300]]
** [[Intel Centrino Advanced-N + WiMAX 6250]]
* [[MiniPCI Express slot]] 2 with one of the following:
** None (empty)
** [[Qualcomm Gobi 2000]] WWAN with GPS
* [[ExpressCard slot|ExpressCard/34 slot]]
* [[Lenovo Integrated Smart Card Reader]] (Optional)
* [[Ricoh 5-in-1 MultiCard Reader|5-in-1 MultiCard Reader]]
* 2.0MP [[Integrated camera]] on select models
* [[Huey PRO Colorimeter]] by X-Rite on select models
* [[Embedded Security Subsystem|Trusted Computing Group TPM 1.2]]
* [[Active Protection System]]
* [[Integrated Fingerprint Reader]] on select models
* [[ThinkPad Bluetooth with Enhanced Data Rate (BDC-2.1)|Bluetooth]] on select models
* [[UltraNav]] (TrackPoint / Touchpad combo)
* [[Firewire Port|Firewire 400]] (IEEE1394a)
* [[DisplayPort]]
* [[Intel Active Management Technology (AMT)]] on select models

</div>
|style="vertical-align:top" |
[[Image:ThinkPadW510.jpg|ThinkPad W510|300px]]
|}

=== Linux Installation ===

As of 2010-03-01 the following problems exist with the W510 under Linux:

* Audio on some W510's has been "destroyed" after running for a while. It has been confirmed that speakers have melted in t400s and t410s as well, this is unrelated to Linux.
* nVidia FX 880M requires driver >= 195.36.15. Earlier versions have stability or graphics corruption problems.
* To enable brightness control in X, append 'Option "RegistryDwords" "EnableBrightnessControl=1"' to the Device-Section of xorg.conf, orginal source: http://www.nvnews.net/vbulletin/showthread.php?p=2204839#post2204839. This may result in a high-pitched whine after lowering the brightness within X. Brightness may not be lowered and raised in the same increments on Archlinux.
* Suspend not implemented yet in USB 3.0 (xhci) driver - system cannot suspend unless driver is unloaded first - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/522998
** xhci driver was renamed to xhci_hcd in Ubuntu 10.10 (Maverick Meerkat). Also, iwlagn may need to be unloaded as well - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/664398
** xhci suspend has finally been included in kernel 2.6.37. You don't need module unloading tricks anymore.
* System can only resume from suspend once - acpi related kernel crash occurs on resume (but system continues to operate), next resume shows BIOS screen and hangs - https://bugzilla.kernel.org/show_bug.cgi?id=15407
** Lenovo has issued a {{IBMDOCURL|MIGR-74858|BIOS update}} that fixes the 2nd suspend problem (c.f. bugs.launchpad.net/bugs/532374 Ubuntu bug tracker)
** TEMPORARY WORKAROUND for suspend issues: Use kernel > 2.6.33 mainline and add "acpi_sleep=sci_force_enable" to kernel arguments. This allows the system to suspend and resume multiple times without issue, however it doesn't fix it the "right" way. Lenovo BIOS update mentioned above will eliminate the need for this step.
* If running an Ubuntu PAE kernel, you can only resume from suspend once if you actually have > 4 GB of RAM. While this has the same symptoms as above, none of the workarounds work for this - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/786010
* Wired networking stuck at 10Mbit without manual change using ethtool. For Ubuntu Karmic this can easily be fixed by manually downloading and installing the [http://bit.ly/bTvbWx e1000e driver from Intel]. After installing this driver however, the wireless stopped working me.
(NOT true for me on kernel 2.6.33 ethtool says " Speed: 1000Mb/s " -[[User_talk:mstragowski|mstragowski]])

* Archlinux before version 2010.5 cannot easily be configured, as the wireless and ethernet cards both require drivers that are not present in the 2009.08 release. This may be a problem for other distros, as well. With Archlinux 2010.5, ethernet works out of the box and wireless works after kernel update.'''
* While Turbo Boost IS working properly with recent distros, built in Linux utilities do not currently show Turbo Boost activity. Intel Powertop or i7z will show actual CPU state properly, including Turbo Boost and advanced C-states. Can be verified running Ubuntu Lucid and compiling a kernel or other tasks, WHILE ON AC POWER.
* 2-finger scroll on touchpad not working even wtih gpointing-device-settings

Option "EmulateTwoFingerMinZ" "4"
Option "VertEdgeScroll" "off"
Option "HorizEdgeScroll" "off"
Option "VertTwoFingerScroll" "on"

in the synaptics section in xorg.conf solved that one for me
(EmulateTwoFingerMinZ is the relevant part here I think.)

* The fingerprint reader (USB ID 147e:2016) is recognized by fprint and should be supported. However, attempting to enroll a print results in an error "-22". Using proprietary driver found at http://www.upek.com/solutions/pc_and_networking/sdks/linux/ allows using this new chip. Using fingerprint from software http://www.pdfserver.net/fingerprint helps working with this reader.

* If you find the flashing wireless LED annoying, you can change its behavior so it will be on steady whenever the radio is powered on, and off when the radio is off. Add "options iwlcore led_mode=1" to /etc/modprobe.d/iwlcore.conf to set the LED on steady, or you can set led_mode=0 to have it flash whenever there is wireless activity (default)

* XEN and W510 - After trying numerous combinations of Linux distributions & XEN to get the W510 running a dom0 the problem was well-integrated XEN environments with no support for the W510 or new distributions (like Ubuntu) fixing driver problems but no XEN support whatsoever. I eventually found OpenSuse 11.3 milestone 7 worked pretty well with full resolution graphic support using Nouveau (2.6.34-8) in a dom0. Note: you have to enable VT-d support in BIOS if you want HVM support. Networking however was a complete headache and worked so long as no network changes were made. --[[User:Diti2202|Diti2202]] 21:25, 6 June 2010 (UTC)

* KVM and W510 - Using Ubuntu 10.04 KVM tools this works very well and is very stable with less disk-thrashing than seen with the OpenSuse11.3 and XEN. Performance seems to be en-par with that of XEN when running the same guest (desktop) VMs. Ubuntu 10.04 (latest updates) seems to support W510 hardware quite well with nouveau graphics driver. Full-screen Guest VM consoles mess up focus between host & guest environment (likely a KVM issue, not W510). --[[User:Diti2202|Diti2202]]

* Memory - Only since Bios version 1.24 you may use more than 3GB under amd64 Linux --[[User:carpf|carpf]])

Workarounds:'''

* On Ubuntu Karmic, Wireless can be enabled by installing linux-backport-modules-karmic. This adds missing firmware for 6000-series cards. This does not seem to work with the 2.6.31-20 kernel but I have no problems in the 2.6.31-19.
* All Versions: System cannot suspend unless <nowiki>SUSPEND_MODULES="xhci"</nowiki> (on ArchLinux with 2.6.35 the Module is called "xhci_hcd") is added to /etc/pm/config.d/unload_modules (may need to create this file) Note that this does not resolve the "crash on second resume" problem.
* On archlinux, ethernet will work after one manually installs the newest kernel26 package, while wifi requires the appropriate microcode package, iwlwifi-6000-ucode.
* The Nouveau open source nVidia driver [http://www.nvnews.net/vbulletin/showpost.php?p=2194707&postcount=20] works at full resolution without freezing (but without 3D acceleration). This driver is included in Ubuntu Lucid. Note that you may experience elevated (but safe) system temperatures when running Nouveau.
* Full touchpoint support can be activated by installing <nowiki>gpointing-device-settings</nowiki> - this allows middle click scroll, etc.
* To control brightness without the (admittedly minor) nvidia driver issues, do not add the EnableBrightnessControl option, but instead switch to a virtual console to change the brightness--this change will remain when you switch back to X.
* The CD tray's eject button being on an edge of the machine is very easy to catch by accident. The button can be disabled in Linux by issuing this command at boot:
/usr/bin/eject -i on /dev/sr0
There are multiple ways of issuing a command at boot depending on your distro. All other methods of ejecting media are unchanged.

=== Hardware notes ===
* The W510 ships with a large (nearly doubled size of the 90W version) 135W power supply. However, it is possible to plug 90W power supplies, but they get rather warm. Upon boot there's a notification message, that a power supply with reduced performance is connected. '''Note''': In order to avoid overloading the weaker power supply, the CPU is throttled drastically and usually does not go above 400 Mhz.
* If the binary nVidia drivers are not installed the system runs about 10 degrees warmer and uses a few watts more power. It seems the open source 'nouveau' driver does not have power saving functionality with the nVidia chipset. The program "nvclock" might be able to alleviate this, but I haven't tried.
* A high pitched noise can sometimes be heard when the computer is running. I was informed that this is the CPU's power management unit. If it annoys you it can be disabled in the BIOS. Also seems that it is correlated with brightness level - at maximum level noise disappears even if laptop works at bare WM without large tasks.
* The computer does not boot at all when some USB keyboards are plugged in at power on. This is a problem with the BIOS and not with Linux or Windows. The only solution is to unplug the keyboard and plug it in again once the laptop is past the BIOS screen and booting as normal.
* After upgrading to Ubuntu 10.04 the system hangs very often. Nothing unusual in dmesg or system logs. Seems to happen more often when using wireless. (see bug https://bugs.launchpad.net/bugs/576352)
** this is mostly alleviated by updating to Nvidia driver version 256 (now higher) from the SWAT reposistory for Ubuntu. https://launchpad.net/~ubuntu-x-swat/+archive/x-updates. Also throttle the clock speed of the GPU to the minimum (reducing heat) following guidelines from here: http://linux.aldeby.org/nvidia-powermizer-powersaving.html to pretty much end the hangs. Issue has been seen to exist on Windows and Ubuntu. Current Nvidia drivers (v.256+) appear to reduce (but not solve) the problem on both platforms.

[[Category:W Series]]

BIOS Upgrade/X Series

2011-08-14T19:10:28Z

Xdeller: /* Approach 10: Booting the Lenovo ISO image using Grub and SysLinux */

__TOC__

X Series Thinkpads do not have internal optical or floppy drives. If there is no Windows installed, the BIOS must be updated by booting from an USB drive or a drive that is integrated in the docking station. In recent times Lenovo provides BIOS updates in form of bootable CD images. Unfortunately, in most cases these images are intended to be used with the docking station's CD drive. If you do not own such a drive, things get complicated.

The problem is that current BIOS updates are quite large, about 3 MB in size. Booting from CDs typically works like booting from a 1.44 MB or 2.88 MB floppy disk. The floppy image is stored on the CD and is referenced in the CD's boot record. Because the BIOS update files are that large, they do not fit on such a floppy image. To resolve it, you have to either use a large harddisk image for your bootimage (e.g. in [[:Category:X200|X200]], [[:Category:X200_Tablet|X200 Tablet]] and [[:Category:X301|X301]]), or store these update files on the CD outside the virtual floppy image. For the former case, see [[BIOS update without optical disk]]. This page concerns with the later case.

To access the BIOS update files on the CD outside the bootimage, a driver for the CD drive has to be loaded. Since Lenovo's CD images are intended to be used with a docking station's CD drive, it is not possible to use them for BIOS updates by booting from an USB CD drive.

Another problem is that older X Series (like the {{X32}}) don't have bootable iso images at all. They have only two options: 1. update from Windows, 2. update using a diskette updater, which requires you to have a real floppy disk drive.

But there is hope. This page describes some approaches to solve the problems above.

Here is a brief overview of each approach:
* [[#Approach 1: Use larger boot image and create virtual CD drive]] Requires a USB CD drive. Reported to work on {{X60s}}.

* [[#Approach 2: Load an USB driver, create RAM disk and copy the files to the RAM disk]] Requires a USB CD drive. People have reported mixed results, with the flash update software freezing, depending on things like CD drive letter and type. Reported to work on {{X60s}}.

* [[#Approach 3: Alternative method using a USB stick]] Requires a USB flash drive, Microsoft Windows, and some HP software tool. Reported to work on {{X60s}}, {{X61}}.

* [[#Approach 4: Alternative method to the above "alternative method"]] Requires a USB flash drive, Microsoft Windows, and some HP software tool. Seems functionally similar to Approach 3.

* [[#Approach 5: Free Alternative method to the above "alternative method"]] Requires a USB flash drive, does not require MS Windows or any proprietary software.

* [[#Approach 6: Using a USB stick to upgrade BIOS on older X Series Thinkpads]] Requires a USB flash drive. Reported to work on {{X32}}.

* [[#Approach 7: Use syslinux to boot floppy images which are part of the IBM/ Lenovo BIOS update CD ISO files.]] Done with a {{X31}} to upgrade the EC to version 1.08 and the BIOS to 3.02.

= Approach 1: Use larger boot image and create virtual CD drive =

The CD images provided by Lenovo can be modified such that a BIOS update is possible -- without loading any drivers. I ([[User:Joachim_Selke|Joachim Selke]]) successfully updated my Thinkpad {{X60s}} using the following method.

My first idea was to take Lenovo's ISO CD image and modify it such that a USB CD drive can be used instead the CD drive in the docking station. Unfortunately, simply replacing the drivers is not enough. While doing the BIOS update, the USB ports seem to get disabled or something like that. To circumvent this problem I tried to create a RAM disk, copy the needed files to this RAM disk, and then use this RAM disk as some kind of virtual CD drive. However, there were some problems with this approach as reported below. For a description of this old approach see the section "Approach 2: Load an USB driver, create RAM disk and copy the files to the RAM disk" below. I developed a new approach to solve this problem and will describe it here.

The idea is to create a new bootable ISO image that is large enough to hold the original ISO file. This can be done by switching from the virtual floppy drive used by Lenovo's update disk to a virtual hard disk drive (for details, see the El Torito standard). Instead of loading the CD drive driver provided by Lenovo we load the [[http://www.oocities.com/jadoxa/shsucdx/index.html SHSUCD drivers]]. This driver enables us to create a virtual CD drive from Lenovo's original ISO file.

I wrote a script to automate this steps and create a new ISO file from Lenovo's ISO file. This new ISO file can directly be used to update the BIOS. My script takes four arguments:
<ol>
<li>the filename of Lenovo's original ISO file (e.g. <tt>/home/selke/Desktop/7buj23uc.iso</tt>)</li>
<li>the filename of the new ISO file to be created (e.g. <tt>/home/selke/Desktop/out.iso</tt>)</li>
<li>the location of shsucdrd.exe (e.g. <tt>/home/selke/Desktop/shsucdrd.exe</tt></li>
<li>the location of shsucdx.com (e.g. <tt>/home/selke/Desktop/shsucdx.com</tt></li>
</ol>

Both shsucdrd.exe and shsucdx.com can be downloaded from [http://www.oocities.com/jadoxa/shsucdx/index.html].

To sum up, an example call of the script would be <tt>convertlenovo.sh /home/selke/Desktop/7buj23uc.iso /home/selke/Desktop/out.iso /home/selke/Desktop/shsucdrd.exe /home/selke/Desktop/shsucdx.com</tt>

Note that you need recent versions of the following tools:
<ul>
<li>mkdosfs (for Fedora users: contained in the package dosfstools)</li>
<li>mkisofs</li>
</ul>

The script runs perfectly on my Fedora 11 system (it should also run without problems on Fedora 7, 8, 9, 10 and other popular distributions). If there are problems, please tell me ([[User:Joachim_Selke|Joachim Selke]]).

Further note that the script at some point requires you to enter the root password since it must mount a disk image. As far as I know, this cannot be done without root privileges.

What does the script do? I will give a short overview:
<ol>
<li>Extract the boot floppy image from Lenovo's bootable ISO file.</li>
<li>Create a new boot hard disk image and copy both the boot sector and the files from Lenovo's boot floppy image to the new image.</li>
<li>Copy Lenovo's ISO image to the new hard disk image.</li>
<li>Also copy the SHSUCD drivers to the hard disk and change autoexec.bat and config.sys accordingly. When booting this hard disk image a new virtual CD drive will be created by SHSUCD. This virtual CD drive will have Lenovo's original ISO disc "inserted."</li>
<li>Create a new ISO file that only consists of the boot image given by the bootable hard disk image just created.</li>
</ol>

Some additional notes:
<ul>
<li>Currently, the script is not able to handle spaces in file names properly. Thus, the file names and directory path names used when calling the script should not contain spaces.</li>
<li>The file name of the original ISO file (7buj23uc.iso in the example above) must follow the DOS 8.3 file name conventions; otherwise SHSUCD will not be able to load the ISO image.</li>
</ul>

Here is the complete script (save it as <tt>convertlenovo.sh</tt>):

<pre>
#!/bin/bash

# Written by Joachim Selke (mail@joachim-selke.de), 2007-12-28

# Known bugs:
# - spaces in file names make trouble at the moment (so try to avoid spaces),
# I will fix that later
# - some users seem to have problems with some of the sed statements,
# I currently have no idea what is wrong there ... (please report those bugs)

CDIMAGE=$1 # location of Lenovo's CD image
NEWCDIMAGE=$2 # filename of ISO file to create
SHSUCDRD_EXE=$3 # location of shsucdrd.exe
SHSUCDX_COM=$4 # location of shsucdx.com

MB_HDD=50 # HDD image size in megabyte (base 1000)

TMPDIR=`mktemp -d`
ISODIR=`mktemp -d`

HDDIMG=$ISODIR/hdd.img # filename of HDD image to create
FLOPPYIMG=$TMPDIR/floppy.img # filename of floppy image to create

##############################################################################

# This script extracts the floopy boot image from bootable ISO images
#
# Written by Joachim Selke (mail@joachim-selke.de), 2007-04-07

ISOFILE=$CDIMAGE
IMAGEFILE=$FLOPPYIMG

if [ ! -r $ISOFILE ]; then
echo $ISOFILE: file does not exist or is not readable
exit 1
fi

if [ -z $IMAGEFILE ]; then
echo Error: no image file specified
exit 1
fi

ISOFILESIZE=`stat -c %s $ISOFILE`

# collect El Torito data
# see http://www.phoenix.com/NR/rdonlyres/98D3219C-9CC9-4DF5-B496-A286D893E36A/0/specscdrom.pdf for reference

BOOTCATALOGPOINTERBYTE=$((17 * 0x800 + 0x47))

if [ $ISOFILESIZE -lt $(($BOOTCATALOGPOINTERBYTE + 4)) ]; then
echo ISO file is too short, possibly damaged
exit 1
fi

# absolute pointer to first sector of boot catalog:
BOOTCATALOG=`od -A n -t x4 -N 4 -j $BOOTCATALOGPOINTERBYTE $ISOFILE | tr -d [:blank:]`

BOOTCATALOGBYTE=$((0x$BOOTCATALOG * 0x800))

echo Boot catalog starts at byte $BOOTCATALOGBYTE

if [ $ISOFILESIZE -lt $(($BOOTCATALOGBYTE + 32 + 2)) ]; then
echo ISO file is too short, possibly damaged
exit 1
fi

# media type of boot image
# only floppy disk images are supported by this script
BOOTMEDIATYPE=`od -A n -t x1 -N 1 -j $(($BOOTCATALOGBYTE + 32 + 1)) $ISOFILE | tr -d [:blank:]`

if [ $BOOTMEDIATYPE -eq 1 ]; then
echo Boot media type is 1.2M floppy disk
IMAGEBLOCKS=$((1200 / 2))
elif [ $BOOTMEDIATYPE -eq 2 ]; then
echo Boot media type is 1.44M floppy disk
IMAGEBLOCKS=$((1440 / 2))
elif [ $BOOTMEDIATYPE -eq 3 ]; then
echo Boot media type is 2.88M floppy disk
IMAGEBLOCKS=$((2880 / 2))
else
echo Boot media type is $((0x$BOOTMEDIATYPE)). This type is not supported yet.
exit 1
fi

# absolute pointer to start of boot image
BOOTIMAGE=`od -A n -t x4 -N 4 -j $(($BOOTCATALOGBYTE + 32 + 8)) $ISOFILE | tr -d [:blank:]`

BOOTIMAGEBYTE=$((0x$BOOTIMAGE * 0x800))

echo Boot image starts at byte $BOOTIMAGEBYTE

if [ $ISOFILESIZE -lt $((0x$BOOTIMAGE * 0x800 + $IMAGEBLOCKS * 0x800)) ]; then
echo ISO file is too short, possibly damaged
exit 1
fi

echo Extracting boot image ...

dd if=$ISOFILE of=$IMAGEFILE bs=2K count=$IMAGEBLOCKS skip=$((0x$BOOTIMAGE))

echo Finished

##############################################################################

NO_HEA=16 # heads
NO_SECT=63 # sectors per cylinder/track
B_SECT=512 # bytes per sector

B_CYL=$(($NO_HEA * $NO_SECT * $B_SECT)) # bytes per cylinder/track

NO_CYL=$(($MB_HDD * 1000 * 1000 / $B_CYL)) # cylinders/tracks per head

echo -n -e "Cylinders: $NO_CYL\nHeads: $NO_HEA\nSectors per track: $NO_SECT\nBytes per sector: $B_SECT\n"

echo Creating empty image ...
dd if=/dev/zero of=$HDDIMG bs=$B_CYL count=$NO_CYL >/dev/null 2>&1

echo Creating partition structure ...
echo -n -e "o\n n\n p\n 1\n \n \n t\n 6\n a\n 1\n w\n" | /sbin/fdisk -b $B_SECT -C $NO_CYL -H $NO_HEA -S $NO_SECT $HDDIMG >/dev/null 2>&1

echo Writing master boot record ...
echo -n -e "\
\xFA\xB8\x00\x10\x8E\xD0\xBC\x00\xB0\xB8\x00\x00\x8E\xD8\x8E\xC0\
\xFB\xBE\x00\x7C\xBF\x00\x06\xB9\x00\x02\xF3\xA4\xEA\x21\x06\x00\
\x00\xBE\xBE\x07\x38\x04\x75\x0B\x83\xC6\x10\x81\xFE\xFE\x07\x75\
\xF3\xEB\x16\xB4\x02\xB0\x01\xBB\x00\x7C\xB2\x80\x8A\x74\x01\x8B\
\x4C\x02\xCD\x13\xEA\x00\x7C\x00\x00\xEB\xFE\x00\x00\x00\x00\x00\
\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
\x00\x00\x00\x00\x00\x00\x00\x00\x52\xF9\x06\x00\x00\x00\
" | dd of=$HDDIMG bs=1 conv=notrunc >/dev/null 2>&1

echo Creating primary partition ...
# extract partition, create FAT16 filesystem and copy back
PARTFILE=${HDDIMG}-PARTITION
SECT_PARTTABLE=$NO_SECT
B_PARTTABLE=$(($SECT_PARTTABLE * $B_SECT))
dd if=$HDDIMG of=$PARTFILE bs=$B_SECT skip=$SECT_PARTTABLE >/dev/null 2>&1
/sbin/mkdosfs -F 16 -h $NO_SECT $PARTFILE
# Correct physical drive number (set to 0x00, should be 0x80)
echo -n -e "\x80" | dd of=$PARTFILE bs=1 seek=36 conv=notrunc >/dev/null 2>&1
# Correct sectors per track (set to 0x0020, should be $NO_SECT)
NO_SECT_HEX1=$(echo "ibase=10; obase=16; $(($NO_SECT / 256))" | bc)
NO_SECT_HEX2=$(echo "ibase=10; obase=16; $(($NO_SECT % 256))" | bc)
NO_SECT_HEX=$(echo -n -e "\\x$NO_SECT_HEX2\\x$NO_SECT_HEX1")
echo -n -e $NO_SECT_HEX | dd of=$PARTFILE bs=1 seek=24 conv=notrunc >/dev/null 2>&1
dd if=$PARTFILE of=$HDDIMG bs=$B_SECT seek=$SECT_PARTTABLE >/dev/null 2>&1
rm -f $PARTFILE

# transfer floppy boot sector code
B_BOOTSECPARAM=62 # length of parameter block in boot sector
B_BOOTSECCODE=$(($B_SECT - B_BOOTSECPARAM)) # length of code block in boot sector
echo Copying boot sector ...
dd if=$FLOPPYIMG of=$HDDIMG bs=1 count=$B_BOOTSECCODE skip=$B_BOOTSECPARAM seek=$(($B_PARTTABLE + $B_BOOTSECPARAM)) conv=notrunc >/dev/null 2>&1

echo Copying DOS files ...
CDIMAGE_BASENAME=$(basename $CDIMAGE)
HDDDIR=$TMPDIR/hdd
FLOPPYDIR=$TMPDIR/floppy
su --command="\
mkdir $HDDDIR;\
mkdir $FLOPPYDIR;\
mount -oloop $FLOPPYIMG $FLOPPYDIR;\
mount -t msdos -oloop,offset=$(($SECT_PARTTABLE * $B_SECT)) $HDDIMG $HDDDIR;\
cp --preserve $FLOPPYDIR/ibmbio.com $HDDDIR;\
cp --preserve $FLOPPYDIR/ibmdos.com $HDDDIR;\
cp --preserve -u $FLOPPYDIR/* $HDDDIR;\
cp --preserve=timestamps $CDIMAGE $HDDDIR;\
cp --preserve=timestamps $SHSUCDRD_EXE $HDDDIR;\
cp --preserve=timestamps $SHSUCDX_COM $HDDDIR;\
cat $FLOPPYDIR/config.sys | \
sed -e 's/A:\\\/C:\\\/' | \
grep -v IBMTPCD.SYS >$HDDDIR/config.sys;\
cat $FLOPPYDIR/autoexec.bat | \
sed -e 's/LOADHIGH MSCDEX.EXE \/D:TPCD001/shsucdrd.exe \/f:$CDIMAGE_BASENAME\r\nshsucdx.com \/d:SHSU-CDR,R/' >$HDDDIR/autoexec.bat;\
umount $FLOPPYDIR;\
umount $HDDDIR;\
rm -rf $FLOPPYDIR;\
rm -rf $HDDDIR"

echo Creating ISO image ...
mkisofs -input-charset default -hard-disk-boot -b $(basename $HDDIMG) -hide boot.cat -hide $(basename $HDDIMG) -o $NEWCDIMAGE $ISODIR

rm -rf $TMPDIR
rm -rf $ISODIR

echo Completed!
</pre>

If you have any questions, feel free to ask. :-)

BTW: It would be much simpler if I simply could put the new ISO images for download somewhere. But I guess for legal reasons this will not be possible.

== Comments on Approach 1 ==

<ul>

<li>
Reported to work on:
<ul>
<li>ThinkPad X60s (1702-55G) with Plextor PX-608CU USB DVD recorder</li>
<li>ThinkPad X60 (1702-55G) with Plextor PX-608CU USB DVD recorder, upgraded BIOS from version 2.14 to 2.16</li>
<li>ThinkPad X60 (1706-GMG) with Plextor PX-608CU USB DVD recorder, upgraded BIOS from version 2.03 to 2.14</li>
<li>ThinkPad X61s (7666-36G) with Freecom FS-50 USB DVD recorder, upgraded BIOS from version 1.10 to 2.07</li>
<li>ThinkPad X300 (6476-CTO) with Nu SBW-242US USB DVD recorder, upgraded BIOS from 1.05 to 1.08</li>
<li>Thinkpad X60s (1704-44U) with Lite-On DX-20A3H, upgraded BIOS from 2.17 to 2.18</li>
<li>ThinkPad X61s (7666-36G) with Samsung SE-S224 USB DVD recorder, upgraded BIOS from version 2.07 to 2.20</li>
</ul>
</li>

</ul>

= Approach 2: Load an USB driver, create RAM disk and copy the files to the RAM disk =

I ([[User:Joachim_Selke | Joachim Selke]]) successfully updated my Thinkpad {{X60s}} using the following method.

My first idea was to take Lenovo's ISO CD image and modify it such that a USB CD drive can be used instead the CD drive in the docking station. Unfortunately, simply replacing the drivers is not enough. While doing the BIOS update, the USB ports seem to get disabled or something like that. To circumvent this problem I tried to create a RAM disk, copy the needed files to this RAM disk, and then use this RAM disk as some kind of virtual CD drive. However, there were some problems with this approach as reported below.

<ol>
<li>
Download the ISO image style BIOS update from Lenovo's website. This file will be refered to as <tt>/tmp/bios-lenovo.iso</tt>.
</li>

<li>
Extract the floppy image from this ISO image. You can use the following shell script for this task (or an alternative one from [http://userpages.uni-koblenz.de/~krienke/ftp/noarch/geteltorito/]). Simply save this code into the file <tt>/tmp/extractbootimage.sh</tt>, set the x-flag (<tt>chmod +x /tmp/extractbootimage.sh</tt>) and call it using the command <tt>/tmp/extractbootimage.sh /tmp/bios-lenovo.iso /tmp/bios-lenovo.img</tt>. The floppy image contained in the ISO image will then be saved to <tt>/tmp/bios-lenovo.img</tt>. Here is the code of the shell script:
<pre>
#!/bin/bash

# This script extracts the floopy boot image from bootable ISO images
#
# Written by Joachim Selke (mail@joachim-selke.de), 2007-04-07

ISOFILE=$1
IMAGEFILE=$2

if [ ! -r $ISOFILE ]; then
echo $ISOFILE: file does not exist or is not readable
exit 1
fi

if [ -z $IMAGEFILE ]; then
echo Error: no image file specified
exit 1
fi

ISOFILESIZE=`stat -c %s $ISOFILE`

# collect El Torito data
# see http://www.phoenix.com/NR/rdonlyres/98D3219C-9CC9-4DF5-B496-A286D893E36A/0/specscdrom.pdf for reference

BOOTCATALOGPOINTERBYTE=$((17 * 0x800 + 0x47))

if [ $ISOFILESIZE -lt $(($BOOTCATALOGPOINTERBYTE + 4)) ]; then
echo ISO file is too short, possibly damaged
exit 1
fi

# absolute pointer to first sector of boot catalog:
BOOTCATALOG=`od -A n -t x4 -N 4 -j $BOOTCATALOGPOINTERBYTE $ISOFILE | tr -d [:blank:]`

BOOTCATALOGBYTE=$((0x$BOOTCATALOG * 0x800))

echo Boot catalog starts at byte $BOOTCATALOGBYTE

if [ $ISOFILESIZE -lt $(($BOOTCATALOGBYTE + 32 + 2)) ]; then
echo ISO file is too short, possibly damaged
exit 1
fi

# media type of boot image
# only floppy disk images are supported by this script
BOOTMEDIATYPE=`od -A n -t x1 -N 1 -j $(($BOOTCATALOGBYTE + 32 + 1)) $ISOFILE | tr -d [:blank:]`

if [ $BOOTMEDIATYPE -eq 1 ]; then
echo Boot media type is 1.2M floppy disk
IMAGEBLOCKS=$((1200 / 2))
elif [ $BOOTMEDIATYPE -eq 2 ]; then
echo Boot media type is 1.44M floppy disk
IMAGEBLOCKS=$((1440 / 2))
elif [ $BOOTMEDIATYPE -eq 3 ]; then
echo Boot media type is 2.88M floppy disk
IMAGEBLOCKS=$((2880 / 2))
else
echo Boot media type is $((0x$BOOTMEDIATYPE)). This type is not supported yet.
exit 1
fi

# absolute pointer to start of boot image
BOOTIMAGE=`od -A n -t x4 -N 4 -j $(($BOOTCATALOGBYTE + 32 + 8)) $ISOFILE | tr -d [:blank:]`

BOOTIMAGEBYTE=$((0x$BOOTIMAGE * 0x800))

echo Boot image starts at byte $BOOTIMAGEBYTE

if [ $ISOFILESIZE -lt $((0x$BOOTIMAGE * 0x800 + $IMAGEBLOCKS * 0x800)) ]; then
echo ISO file is too short, possibly damaged
exit 1
fi

echo Extracting boot image ...

dd if=$ISOFILE of=$IMAGEFILE bs=2K count=$IMAGEBLOCKS skip=$((0x$BOOTIMAGE))

echo Finished
</pre>
</li>

<li>
Mount the floppy image '''as root''' using the loop device:
:{{cmdroot|mkdir /tmp/bios-lenovo.img-mnt}}
:{{cmdroot|mount -o loop /tmp/bios-lenovo.img /tmp/bios-lenovo.img-mnt}}
The image is now mounted as <tt>/tmp/bios-lenovo.img-mnt</tt>.
</li>

<li>
Download needed drivers. First download some [http://panasonic.co.jp/pcc/products/drive/other/driver/f2h_usb.exe USB drivers] from Panasonic Japan. Save the file to <tt>/tmp/f2h_usb.exe</tt> This file is a self-extracting EXE file, that can be executed under Linux using [http://www.winehq.com/ Wine]:
:{{cmduser|wine /tmp/f2h_usb.exe}}
You will be asked where to save the extracted files. Choose <tt>/tmp</tt>. A new directory <tt>/tmp/F2h</tt> containing the needed drivers will be created.

Additionally, you will need drivers for the RAM disk mentioned. Download them from the [http://sourceforge.net/projects/srdisk ReSizeable RAMDisk project]. Unzip them to <tt>/tmp/srdisk</tt>.
</li>

<li>
Let's modify the floppy image:
:{{cmduser|cp /tmp/F2h/Usbaspi.sys /tmp/bios-lenovo.img-mnt/}}
:{{cmduser|cp /tmp/F2h/USBCD.SYS /tmp/bios-lenovo.img-mnt/}}
:{{cmduser|cp /tmp/F2h/RAMFD.SYS /tmp/bios-lenovo.img-mnt/}}
:{{cmduser|cp /tmp/srdisk/srdxms.sys /tmp/bios-lenovo.img-mnt/}}
:{{cmduser|cp /tmp/srdisk/srdisk.exe /tmp/bios-lenovo.img-mnt/}}
Now add the following lines to <tt>/tmp/bios-lenovo.img-mnt/config.sys</tt> replacing the line <tt>DEVICE = A:\IBMTPCD.SYS /R /C</tt>:
<pre>
DEVICE = A:\SRDXMS.SYS
DEVICE = A:\RAMFD.SYS
DEVICE = A:\USBASPI.SYS /V
DEVICE = A:\USBCD.SYS /D:TPCD001
</pre>
Finally, edit the file <tt>/tmp/bios-lenovo.img-mnt/autoexec.bat</tt> replacing the last line (saying <tt>COMMAND.COM</tt>) by the following:
<pre>
A:\SRDISK 10000
COPY *.* D:
D:
COMMAND.COM
</pre>

Maybe the RAM disk gets a drive letter different from D: on your system. In this case, you have to change the above lines accordingly.
</li>

<li>
Unmount the floppy image (as root):
:{{cmdroot|umount /tmp/bios-lenovo.img-mnt}}
</li>

<li>
Copy the content of the original CD image to a new directory and create a new ISO file:
:{{cmdroot|mkdir /tmp/bios-lenovo.iso-mnt}}
:{{cmdroot|mount -o loop /tmp/bios-lenovo.iso /tmp/bios-lenovo.iso-mnt}}
:{{cmduser|mkdir /tmp/bios-new.iso-mnt}}
:{{cmduser|cp /tmp/bios-lenovo.iso-mnt/* /tmp/bios-new.iso-mnt}}
:{{cmduser|cp /tmp/bios-lenovo.img /tmp/bios-new.iso-mnt/boot.img}}
:{{cmdroot|umount /tmp/bios-lenovo.iso-mnt}}
:{{cmduser|mkisofs -relaxed-filenames -b boot.img -o /tmp/bios-new.iso /tmp/bios-new.iso-mnt/}}
</li>

<li>
The file <tt>/tmp/bios-new.iso</tt> is the modified ISO file. Just burn it to CD and use this CD for updating your BIOS (boot from it using your USB drive). Please give some comments here if it worked for you.
</li>

</ol>

== Comments on Approach 2 ==

<ul>

<li>
I have followed your excellent instructions. The CD booted, the update program ran but stopped working and responding while updating. Luckily the BIOS was not destroyed. Since destroying the BIOS is a very high risk, I am going to recover the original Windows on an old HD and will run the update exe update program from there.
</li>

<li>
I followed these clear instructions, and like the comment above I ended up with a CD that booted but the update program stopped working and responding. An ALT-CTRL-DELETE rebooted my x60s, and it works so the BIOS must not have been damaged. I was trying to upgrade from version 2.08 to 2.11, I wonder if these instructions are somehow particular to certain versions?
[[User:Latch|Latch]] 01:22, 14 June 2007 (UTC)
</li>

<li>
After following the above instructions, the program also stopped working while updating the BIOS. But after changing the drive letter from D: to C: (see code below), it everything worked fine. However, I had some trouble figuring out, which letter to choose over D: at first, as the BIOS Upgrade program started right away.

<pre>
A:\SRDISK 10000
COPY *.* C:
C:
COMMAND.COM
</pre>
[[User:Mtx|Mtx]], 1 August 2007, Thinkpad X61s
</li>

<li>
Flashing the bios (2.12) works for me on a X60s (using drive c). Using the DVD-R on an USB-Hub did not work. [[User:Ra|Ra]] 00:15, 21 August 2007 (UTC)
</li>

<li>
Flashing BIOS 2.14 works for me on a X60s (using drive c). 25-02-2008
</li>

</ul>

= Approach 3: Alternative method using a USB stick =

''Note: none of the above methods worked on my X60s. This method worked for me, however.'' [[User:PhilipPaeps|PhilipPaeps]] 16:41, 24 August 2007 (UTC)

This method was surprisingly painless once I convinced my ThinkPad X60s to boot DOS from a USB stick. I used VMWare and some mystical tool to get DOS on the stick. If you can find another way to get a bootable DOS stick, please update this section!

* Tell VMWare to create a virtual floppy image for you and format it under Microsoft Windows and tell it to create a system disk. You can do this by clicking into "My Computer", then right-clicking on the "Floppy" icon and selecting "Format". In the box that pops up, you need to check the box that says "Create an MS-DOS startup disk" and then click "Start".

* When you've done that, get this tool: http://www.techpowerup.com/downloads/330/mirrors.php and install it. The tool is apparantly something HP once wrote, but I have been unable to find a link to it anywhere on the HP website.

* In a command prompt again: <code>C:\DriveKey\HPUSBF.EXE E: -Q -B:A:\</code>, replacing the <code>E:</code> with the "drive letter" associated with your USB stick (you can find this letter in "My Computer" under "Removable Storage"). '''WARNING:''' this wipes anything on the USB stick. You will end up with a USB stick which appears empty at this point, but there is DOS on it somewhere.

* Now mount the BIOS update ISO image from Lenovo as a virtual CDROM using VMWare again and copy the files from it to the USB stick: <code>copy D:\*.* E:\</code>.

At this point, you may want to fiddle with the splash image, as described elsewhere on ThinkWiki.

* Reboot and press F12, tell the BIOS to boot from your USB stick.

* <code>cd flash</code> ; <code>updtflsh.exe</code>

Think happy thoughts. The ThinkPad will beep quite ominously (and loudly!) a couple of times. Do not let this worry you too much. After about three minutes, the program will ask you to press enter to restart and hopefully all will be well.

= Approach 4: Alternative method to the above "alternative method" =

This is based on the above "Alternative Method" and works on my {{X60}}.

1. Download the [[BIOS_Upgrade_Downloads|BIOS Update]] iso image and the [http://www.techpowerup.com/downloads/330/mirrors.php|HP USB Stick Formatter].

2. Now get access to Windows -- be it in an emulator, or a colleague's PC. Steps 3, 4, 5 needs Windows to complete.

3. Install the HP USB Stick Formatter.

4. Go to the directory where you installed the tool: e.g. C:\DriveKey and extract HPUSBF.EXE to a new directory HPUSBF\ (using WinRAR, 7zip or similar).

5. Run the HPUSBFW.EXE utility, selecting the location of system files as C:\DriveKey\HPUSBF, and let it format the USB stick.

6. Extract the iso image to the USB stick, for example to K:\7buj22us (K: being the USB stick).

7. On the target computer, boot with the USB stick and issue the commands "cd 7buj22us" then "command.com"

This brings up the BIOS flash interface and you can update your BIOS from here.

== Comments on Approach 4 ==

<ul>
<li>
I (Martin Aulbach) followed these clear instructions and updated my X61t (from BIOS v1.08 to v1.10) without any problems and with a nice graphic splash screen. It is not necessary to let Windows format the USB stick as a MS-DOS startup disk, as outlined in Approach 3. The HP format tool will take care of this (in Step 5) and the USB stick will boot sucessfully at startup (correct boot order provided).
</li>
<li> This update to BIOS 2.14 worked on a brand-new X61s, 2008-06-27. (adsmith)
</li>
<li> This update to BIOS 2.19 worked on a X61 (76754KU), 2009-01-21. (leonardokroeger)
</ul>

= Approach 5: Free Alternative method to the above "alternative method" =

This is functionally equivalent to the above two "alternative methods", yet does not depend on MS Windows or any other proprietary software. It updates the BIOS through a bootable USB stick, and depends upon the FreeDOS, SYSLINUX, and AdvanceMAME projects. A detailed description is provided at [http://ubuntuforums.org/showthread.php?p=5459421#post5459421].
''This method currently isn't redommended by the author "due to troubles reported by users (August 9th, 2008)".''

= Approach 6: Using a USB stick to upgrade BIOS on older X Series Thinkpads =

This method has been successfully applied for upgrading an {{X32}} Thinkpad. The previous BIOS version was 3.00d, and it was upgraded to 3.02 . Below are the steps:

1. Download the new BIOS and EC Diskette-type upgrades.

2. Make a DOS-bootable USB stick. See the section above for instructions on how to do this.

3. Copy the upgrade programs to the USB stick.

4. Make two zero-files (using dd), each with the size of a floppy disk.

5. Boot up the USB stick using QEMU, with the USB stick as hda, and the two floppy disk images as A: and B: .

6. Run the BIOS upgrade program, and select the first diskette as its destination. This will not actually upgrade the BIOS; it will only fill up the disk image.

7. Run the EC upgrade program, with the second diskette as target. Again, this will only fill up the disk image, not upgrade the EC.

8. Make two directories, C:\1 and C:\2 .

9. Copy the contents of the first diskette to C:\1 and the second diskette to C:\2 .

10. Exit QEMU, use the USB stick to boot the Thinkpad which BIOS we are going to upgrade.

11. cd into C:\1 and run command.com inside it. This will bring up the BIOS update interface, so update the BIOS.

12. After updating the BIOS, the machine will turn off by itself. Now boot again, with the same USB stick.

13. cd into C:\2 and run command.com inside it. This will bring up the EC update interface. Update the EC and wait for the machine to shut down completely.

14. Remove the USB stick. Now boot into the machine and go into BIOS setup. Right now you should see the new BIOS and EC version. If not, then something is wrong; make sure you have followed the above steps properly. Please also discuss this.

= Approach 7: Use syslinux to boot floppy images which are part of the CD ISO files. Done with a {{X31}} to upgrade the EC to version 1.08 and the BIOS to 3.02. =

1. Download the CD ISO files of the embedded controller and the BIOS.

2. loop mount these files, check for files like 1quj08us.img (EC) and 1quj19us.img (BIOS) and copy them to /boot/

3. Install the syslinux package and boot the two images with the help of the memdisk feature ( grub: kernel /boot/memdisk initrd /boot/{ec|bios}.img)

= Approach 8 : Use HP USB Format Utility and Win98Boot files to Create Bootable USB Stick =
(This process works for most X-series that has Windows XP, Windows Vista or Windows 7 OS)

1. There is an HP utility tool floating around the net called HP USB Boot Utility. This [http://blogs.oreilly.com/digitalmedia/2004/10/utility-to-make-usb-flash-driv.html can create a bootable USB flash drive using the boot/system files you have].

2. Get some [http://www.bay-wolf.com/utility/usbkey/win98boot.zip DOS (or similar) boot files] - I found something called "win98boot.zip" e.g.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

7. run UPDTFLSH.EXE $018E000.FL2

8. Follow UPDTFLSH's instructions

9. Wait flash complete and auto turn off computer.

I done it on my IBM Thinkpad X31.

Enjoy,

Tested by nm.

= Approach 10: Booting the Lenovo ISO image using Grub and SysLinux =

I ran this on my [[:Category:X100e|X100e]] L625 (Dual-Core) 3508-5EG.

Also worked on my [[:Category:X301|X301]] with the default ubuntu 10.10 memdisk (/usr/lib/syslinux/memdisk). My menu entry structure however looked like this (ext4 root/boot partition): --[[User:Blk|Blk]] 17:54, 25 November 2010 (UTC)
menuentry 'BIOS Upgrade' {
insmod ext2
set root='(hd0,msdos1)'
linux16 /boot/memdisk iso
initrd16 /boot/bios.iso
}
small note: the upgrade itself took about 2minutes (it beeped in the middle) and after rebooting i was probably in a reboot-loop. The system rebooted twice in a row after showing the "Press the ThinkVantage button..." blabla, so the third time i went into the bios, reset the default options (F9) and reconfigured it the way i had it before. Then it all worked.
Now to the original instructions (thanks mate!)

If you have trouble using your wifi card like this one: [[Problem_with_unauthorized_MiniPCI_network_card]], you may want to put modified bios files onto cdrom fs, but you may be unable even see file list at least at some newest bootable .iso provided by Lenovo.
* If your modified bios file(which you may easily got from corresponding Windows EXE) have same size, there is no problem at all because you can find beginning of this file at raw cd image and replace it by dd.
* Things got more complex if you have no Windows in dualboot and final bios file size differs, so you need to extract filesystem tree from .iso, put modified files here and finally get this stuff to boot.
** You may use IsoBuster in VirtualBox for extracting the beginning of FAT16 filesystem and therefore dd it by offset or try to search signature of filesystem first block directly(for x200s and 3.20 it was 0x11800) then put your modified BIOS images here, prepare bootable disk from scratch using Windows XP 'boot' floppy option or syslinux and finally boot resulting image via Grub & memdisk. It is a long and weird way but seems there was no easy paths if you`re using third-party wireless card which cannot be modified physically for some reason.

Basically, you download the iso of the cd for bios upgrade from Lenovo and let grub + syslinux emulate a cd-rom drive for you, running the software on the iso.

It's nice and feels safe, since either the iso boots from grub or it doesn't, but if it does, you are running the full OS and update software stack as provided and tested by Lenovo. If it doesn't your bios will not be affected and you will not have bricked your laptop.

* Download the latest bios upgrade from Lenovo website. I used version 1.25 ({{path|6xuj08uc.iso}})
* Get your hands on memdisk of syslinux. I had to compile a recent version, because my memdisk version that came with Ubuntu did not work correctly.
* To compile a recent version of syslinux (I used 3.86):
** Download the sources from http://syslinux.zytor.com/wiki/index.php/ISOLINUX (Download link in my case: http://www.kernel.org/pub/linux/utils/boot/syslinux/syslinux-3.86.tar.bz2),
** Extract the sources and issue {{cmduser|make}} in the root directory of the source.
** Once compiled, the memdisk file you need will be in {{path|syslinux-3.86/memdisk/memdisk}}
* Copy the memdisk file of syslinux to {{path|/boot/memdisk}}
* Update the grub config file: add the code snippet below to the end of the file {{path|/boot/grub/grub.cfg}}. (on Ubuntu, add it to the file {{path|/etc/grub.d/40_custom}} instead, and do a {{cmduser|sudo update-grub}} afterwards).
menuentry "Thinkpad x100e BIOS Upgrade to 1.25" {
set root='(hd0,1)' # This line should match the other menuentries in your grub.cfg
linux16 /boot/memdisk iso
initrd16 /boot/6xuj08uc.iso # Make sure this is the correct filename (a different version will have a different filename)
}
* Now reboot, press and hold shift right after the Thinkpad logo disappears and you should see an option in the grub boot menu to boot the bios upgrade cd.
* Select that option and press enter, the Lenovo bios update software should boot, and you'll get a text-menu interface.
** If you just see text on a black background and your Thinkpad no longer responds, your booting failed. At this point you are not updating the bios, so you can safely reboot using the power on/off button, recheck your config and find out what you did wrong.
* If it does boot, follow the directions carefully:
** Make absolutely sure you have power attached and a well loaded battery just in case
** The process takes around a minute
** When it asks to remove the cd and press enter to reboot, just press enter.
** You should then reboot having and updated bios.

= Approach 10A: Booting an ISO image using Grub and Syslinux for X61 =

The Lenovo ISO images for X61 (and T61) can be booted using Grub as described above, but they don't work as they are intended to be used from a cdrom drive.

Fortunately you can adapt an ISO image from a more recent model, such as the X201.
The following instructions rely on the X201 BIOS Update Bootable CD for version 1.34, filename '''6quj11uc.iso'''.
Other versions may or may not work.

Save this script as '''convert-iso.sh'''

#!/bin/bash

X201=$1 # X201 iso to use
X61=$2 # X61 update
OUT=$3 # output filename

ISO=`mktemp`
SRC=`mktemp -d`
DST=`mktemp -d`

cp $X201 $ISO

# discovered using geteltorito, to get the offset of the disk image
# and fdisk, to get the offset of the partition inside the disk image
OFFSET=71680

mount $ISO $DST -o rw,loop,offset=$OFFSET

# create a ramdisk big enough for the flash files
cat <<EOF | sed 's/$/\r/' > $DST/CONFIG.SYS
FILES=30
BUFFERS=10
DEVICE=C:\HIMEM.SYS /NUMHANDLES=120
DEVICEHIGH=C:\ramdrive.sys /E 30720
DOS=HIGH,UMB
STACKS=9,256
EOF

# copy the flash files to the ramdisk
# if not, the update will simply hang because the files cannot be accessed
#
# remove the command.com line if you need a shell
cat <<EOF | sed 's/$/\r/' > $DST/AUTOEXEC.BAT
copy FLASH\*.* d:
d:
command.com
EOF

rm -r $DST/FLASH/*
mount $X61 $SRC -r -o loop
cp $SRC/* $DST/FLASH

umount $SRC $DST
rmdir $SRC $DST

mv $ISO $OUT
echo "Done: $OUT created."

Then run the script against the X201 bios ISO and the X61 one (in this example, version 2.22, filename '''7nuj22uc.iso''').

{{cmdroot|./convert-iso.sh 6quj11uc.iso 7nuj22uc.iso X61.iso}}.

In theory this should create a file called '''X61.iso''' that can be booted using Grub and Syslinux, and which will successfully update the BIOS.

Category:X200s

2010-11-25T20:28:22Z

Xdeller:

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== ThinkPad X200s ===
This page gives an overview of all ThinkPad X200s related topics.

==== Standard Features ====
*One of the following [[Intel Celeron M]] or [[Intel Core 2 Duo (Penryn)]] processors:
** Intel Celeron M processor 723 (1.20GHz, 1MB L2, 800MHz FSB)
** Intel Celeron processor SU2300 (1.20GHz, 1MB L2, 800MHz FSB)
** Intel Core2 Solo processor SU3500 (1.40GHz, 3MB L2, 800MHz FSB)
** Intel Core2 Duo processor SU9300 (1.20GHz, 3MB L2, 800MHz FSB)
** Intel Core2 Duo processor SL9300 (1.60Ghz, 6MB L2, 1066MHz FSB)
** Intel Core2 Duo processor SU9400 (1.40GHz, 3MB L2, 800 MHz FSB)
** Intel Core2 Duo processor SL9400 (1.86GHz, 6MB L2, 1066MHz FSB)
** Intel Core2 Duo processor SL9600 (2.13GHz, 6MB L2, 1066MHz FSB)
* [[Intel Graphics Media Accelerator 4500MHD]] graphics
* One of the following [[TFT display]]s:
** 12.1" TFT display with 1440x900 (WXGA+) resolution (LED backlight) 250 nits
** 12.1" TFT display with 1280x800 (WXGA) resolution (CCFL backlight) 200 nits
** 12.1" TFT display with 1280x800 (WXGA) resolution (LED backlight) 200 nits
* 2, 3 or 4GB [[PC3-8500]] memory standard, upgradable to 4GB (Also see the [[unofficial maximum memory specs]] for this model.)
* One of the following HDD
** 80GB SSD 1.8" SATA HDD
** 128GB SSD 1.8" SATA HDD
** 160GB 5400rpm 2.5" SATA HDD
** 160GB 7200rpm 2.5" SATA HDD
** 320GB 5400rpm 2.5" SATA HDD
** 320GB 7200rpm 2.5" SATA HDD
* 5-in-1 Card Reader (MMC, SD, SDHC, MS and MS Pro)
* [[Intel Gigabit Ethernet (10/100/1000) PCI-Express]]
* [[ThinkPad Modem (MDC-3.0, 56kbps HDA)]]
* [[MiniPCI Express slot]] 1 with one of the following:
** [[ThinkPad 11b/g/n Wireless LAN Mini-PCI Express Adapter II]]
** [[Intel Wifi Link 5100 (AGN)]]
** [[Intel Wifi Link 5300 (AGN)]]
** [[Intel WiMAX/WiFi Link 5350]]
* [[MiniPCI Express slot]] 2 with one of the following:
** None (empty, not upgradable)
** None (WWAN upgradable)
* [[MiniPCI Express slot]] 3 with one of the following:
** None (empty)
** [[Intel® Turbo Memory hard drive cache]] up to 2GB
* [[ExpressCard slot|ExpressCard/54 slot]]
* [[ThinkPad_Bluetooth_with_Enhanced_Data_Rate_(BDC-2.1)|Bluetooth]] on select models
* [[Integrated Fingerprint Reader]] (Authentec 2810) on select models
* Intel HD Audio with a [[CX20561]] codec
* 1.3MP [[Integrated camera]]
* [[Embedded Security Subsystem|Trusted Computing Group TPM 1.2]]
* [[Active Protection System]]
* Battery Sizes - 4 cell, 6 cell, 9 cell (sticks out the back)
</div>
|style="vertical-align:top" |
[[Image:ThinkPadX200s.jpg|ThinkPad X200s|300px]]
|}

==== Resources ====
* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-70149 Hardware Maintenance Manual (HMM)]
*Debian Lenny install: http://comcap.free.fr/x200s.html
*Debian Sid install: http://larsgg.spaces.live.com/blog/cns!2019B2D8CDA6ED!748.entry
*Arch Linux install: http://itgen.blogspot.com/2008/12/installing-arch-linux-on-lenovo.html
*CentOS 5 install: http://wiki.centos.org/HowTos/Laptops/Lenovo/Thinkpad-X200s

The above Debian related links explain the hoop-jumping required (in early 2009) for x200s models that have the 5300 wireless card. However if you have a model containing the 5100 (e.g 7469-5KG) then a standard Debian Lenny install ('HD-media' on USB key+wireless net install) works fine and is straightforward.

==== Reviews ====
http://forum.thinkpads.com/viewtopic.php?t=67851

[[Category:X Series]]

Unofficial maximum memory specs

2010-11-24T12:44:02Z

Xdeller:

Some ThinkPads are known to support more memory than their specs say. This page gathers information about those models, how much memory they can take and what special requirements that memory must fulfill.

Have a look at the [[Memory]] page for the official memory configs and partnumbers

==Working memory configurations==
The following table gives an overview of tested memory configurations that exceed the specified limits for that ThinkPad type.

{| border="1" cellspacing="0" cellpadding="2"
! ThinkPad !! Official Max !! Unoffical Max !! BIOS !! Embedded Controller !! Memory configuration successfully tested
|- style="vertical-align:top;"
| ThinkPad {{X200s}} 7466-9QG || 4 GB || 8 GB || 3.11 || 1.06 ||
2 x KVR1333D3S9/4G.
|-
| ThinkPad {{X200}} 7459-W2H || 4 GB || 8 GB || 3.13 || 1.06 ||
2 x KVR1066D3S7/4G.
|-
| ThinkPad {{X61t}} 7764-CTO || 4 GB || 8 GB || 1.23 || ?.?? ||
2 x Generic 4GB 200-Pin DDR2.
|-
| ThinkPad {{X61t}} 7762-94G || 4 GB || 8 GB || 1.23 || 1.02 ||
2 x Kingston 4GB 200-Pin DDR2, KVR667D2S5/4G.
|-
| ThinkPad {{X61t}} 7762-95G || 4 GB || 8 GB || 1.23 || 1.02 ||
2 x Kingston 4GB 200-Pin DDR2, KVR667D2S5/4G. Ubuntu 10.10 64bit shows installed memory size of 7,7 GiB.
|-
| ThinkPad {{X61}} 7675-K2U || 4 GB || 8 GB || ?.?? || ?.?? ||
Kingston 8GB (set of 2x4GB) 200-Pin DDR2, KVR667D2S5K2/8G ''Equivalent to 2 x Kingston KVR667D2S5/4G''
|-
| ThinkPad {{T61p}} 8889-3FG || 4 GB || 8 GB || TBA || TBA ||
2 x Kingston 4GB 200-Pin DDR2, KVR667D2S5/4G.
|-
| ThinkPad {{T61p}} 6457-5GG || 4 GB || 8 GB || 2.19 || 1.08 ||
2 x Kingston 4GB 200-Pin DDR2, Model# KTL-TP667/4GB.
|-
| ThinkPad {{T61p}} 6457-7XG || 4 GB || 8 GB || 2.26 || 1.08 ||
2 x Crucial 4GB 200-Pin DDR2, Model# CT51264AC800. (PC2-6400)
|-
| ThinkPad {{T61p}} 6459-CTO || 4 GB || 8 GB || 2.26 || 1.08 ||
2 x G.Skill 4GB 200-Pin DDR2, Model # F2-6400CL6D-8GBSQ
|-
| ThinkPad {{T61p}} 6460-8YG || 4 GB || 8 GB || 2.26 || 1.08 ||
2 x Crucial 4GB 200-Pin DDR2, Model# CT2KIT51264AC667 (2x CT51264AC667)
|-
| ThinkPad {{SL500}} || 4 GB || 8 GB || ?.?? || ?.?? ||
2 x 4GB 200-Pin DDR2 PC2-5300
|-
| ThinkPad {{A31p}} 2653-R8U || 1 GB || 2 GB || 1.10 || 1.05 ||
2 x Elpida 1 GB 200-pin DDR PC2700, FRU # 31P9835
|-
| ThinkPad {{A31p}} 2653-R || 1 GB || || 1.09 || 1.05 ||
2 x Kingston 1GB 200-Pin DDR, Model# KTM - TP9828/1G
|-
| ThinkPad {{T30}} 2366-92U || 1 GB || || 2.08 || 1.06 ||
* 2 x Kingmax 1GB 200-Pin DDR SO-DIMM DDR333 PC2700, Model# MSAD42D-KI
but see [[problem with T30 not booting with 1 GiB memory module]].
* 2 x Generic Brand 1GB 200-pin DDR SO-DIMM PC2700 (p/n 89898E):
BIOS recognizes 2048MB, but Gentoo sees only 1024MB
|-
| ThinkPad {{T43p}} 2668-WTB || 2 GB || || 1.29 || 1.06 ||
* 2 x 1GB Kingston KTM TP3840/1G DDR2 533MHz
|-
| ThinkPad {{X31}} 2672-C2G || 1 GB || || 3.02 || 1.08 ||
* 2 x 1GB Kingston KVR400X64SC3A/1G DDR400MHz. Newer documentation also states 2GB, but original one did not.
* Boots with 1 bar.
|-
| ThinkPad {{X31}} 2673-C2G || 1 GB || || 3.02 || 1.08 ||
* 2 x 1GB (Team Group Inc. TSDR1024M400 DDR400MHz)
* Boots with 1 x TSDR1024M400
|-
| ThinkPad {{X41}} 2528-5FU || 1.5 GB || || 2.09 || 1.02 ||
* 1 x 2GB (Transcend TS2GIB3847 DDR2 667 MHz)
* 1 x 2GB (FRU 73P3846 DDR2 PC2-4200)
BIOS claims 2.5 GB. Diagnostic POST tests only 2 GB. Linux and XP recognize 2 GB.
|-
| ThinkPad {{X41}} 2525-F8G || 1.5 GB || 2 GB || 2.06 || 1.01 ||
* 1 x 2GB (Crucial CT25664AC667 DDR2 PC2-5300)
BIOS claims 2.5 GB. Diagnostic POST and memtest86+ both test only 2 GB. Linux and XP recognize 2 GB.
|-
| {{X41_Tablet}} 1866-6HU || 1.5 GB || || 2.03 || 1.02 ||
* 1 x 2GB (Transcend JM667QSU-2G DDR2 667 MHz)
BIOS claims 2.5GB. Diagnostic POST tests only 2GB, Linux and WindowsXP recognize 2GB.
|-
| ThinkPad {{240}} 2609-40U || 320MByte || || IRETWWW76 || n/a ||
* Any PC100 256MB memory in 16-chip configuration
|-
| ThinkPad {{240X}} || 256MByte || || unknown || n/a ||
* Some PC100 256MB memory in 16-chip configuration may work. Chipset cannot handle more than 256MB
|-
| ThinkPad {{570}} 2644-3AU || 320MB || || 1.16 IMET65WW 11/11/99 || n/a ||
* Kingston KTM-TP390X/256 256MB MODULE FRU 16P6327 - 16 chips, 8 each side
|-
| ThinkPad {{600}} ? || 288MB || || ? || ? ||
* 416MB = 256MB '''low density''' PC100 SODIMM + 128MB PC66 SODIMM + 32MB PC66 on-board. It matters which SODIMM you put in which slot. This was first reported working on the [http://zurich.csail.mit.edu/hypermail/thinkpad/2004-04/0797.html Thinkpad Mailing List], and it worked error-free for me.
The 600E (2645-8A0) with Bios INET36WW accept two modules
of 256MB.
The ram modules have 8 chips on each side.
That results in 544MB. (RAM Typ: Micron MT16LSDF3264HG-133E4 PC133 CL3 sync).
Processor is an Intel PII 366 PE, installed platform is Windows XP Pro with SP3.
|-
| ThinkPad {{770}}x 9549|| 448MB || || 1.11 IIET42WW 09/10/99 || n/a ||
* 448MB = 256MB PC100 + 128MB PC66 + internal 64MB using IBM 256MB MODULE FRU 33L3070 PC100 CL2 - 16 chips, 8 each side
* 512MB = 2 x 256MB PC100 + 64MB internal booted up as well. 512MB is due to 440LX-Chipset limitations, 64MB are overlapping or unused.
|-
|}

==Non-working memory configurations==
{| border="1" cellspacing="0" cellpadding="2"
! ThinkPad !! max. Specs !! BIOS !! Embedded Controller !! Memory configuration unsuccessfully tested
|- style="vertical-align:top;"
| ThinkPad {{A21m}} || 512MB || ? || ? ||
* 2 x Microx 144-pin 512MB PC133 SDRAM SODIMM 32x16 8C
* 1 x Microx 144-pin 512MB PC133 SDRAM SODIMM 32x16 8C
* 1 x Microx 144-pin 512MB PC133 SDRAM SODIMM 32x16 8C
:+ 1 x 144-pin 256MB PC133 SDRAM SODIMM
|- style="vertical-align:top;"
| ThinkPad {{T61p}} 6460-DVU || 4GB || 7LETC7WW (2.27) 04/08/2010 || 1.08 || 6GB: 
      4GB: Micron MT16HTS51264HY 
      2GB: Kingston KTH-ZD8000C6 
Passed Windows Memory Diagnostic (Standard), 
but system became slightly unstable, app crash every 1-2 hours, 
failed Lenovo Toolbox memory test.
|-
|}

==External Sources==
* [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-55644 IBM's official Memory compatibility page]

Category:X200s

2010-09-04T23:41:17Z

Xdeller: /* Standard Features */

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== ThinkPad X200s ===
This page gives an overview of all ThinkPad X200s related topics.

==== Standard Features ====
*One of the following [[Intel Celeron M]] or [[Intel Core 2 Duo (Penryn)]] processors:
** Intel Celeron M processor 723 (1.20GHz, 1MB L2, 800MHz FSB)
** Intel Celeron processor SU2300 (1.20GHz, 1MB L2, 800MHz FSB)
** Intel Core2 Solo processor SU3500 (1.40GHz, 3MB L2, 800MHz FSB)
** Intel Core2 Duo processor SU9300 (1.20GHz, 3MB L2, 800MHz FSB)
** Intel Core2 Duo processor SL9300 (1.60Ghz, 6MB L2, 1066MHz FSB)
** Intel Core2 Duo processor SU9400 (1.40GHz, 3MB L2, 800 MHz FSB)
** Intel Core2 Duo processor SL9400 (1.86GHz, 6MB L2, 1066MHz FSB)
** Intel Core2 Duo processor SL9600 (2.13GHz, 6MB L2, 1066MHz FSB)
* [[Intel Graphics Media Accelerator 4500MHD]] graphics
* One of the following [[TFT display]]s:
** 12.1" TFT display with 1440x900 (WXGA+) resolution (LED backlight) 250 nits
** 12.1" TFT display with 1280x800 (WXGA) resolution (CCFL backlight) 200 nits
** 12.1" TFT display with 1280x800 (WXGA) resolution (LED backlight) 200 nits
* 2, 3 or 4GB [[PC3-8500]] memory standard, upgradable to 4GB
* One of the following HDD
** 80GB SSD 1.8" SATA HDD
** 128GB SSD 1.8" SATA HDD
** 160GB 5400rpm 2.5" SATA HDD
** 160GB 7200rpm 2.5" SATA HDD
** 320GB 5400rpm 2.5" SATA HDD
** 320GB 7200rpm 2.5" SATA HDD
* 5-in-1 Card Reader (MMC, SD, SDHC, MS and MS Pro)
* [[Intel Gigabit Ethernet (10/100/1000) PCI-Express]]
* [[ThinkPad Modem (MDC-3.0, 56kbps HDA)]]
* [[MiniPCI Express slot]] 1 with one of the following:
** [[ThinkPad 11b/g/n Wireless LAN Mini-PCI Express Adapter II]]
** [[Intel Wifi Link 5100 (AGN)]]
** [[Intel Wifi Link 5300 (AGN)]]
** [[Intel WiMAX/WiFi Link 5350]]
* [[MiniPCI Express slot]] 2 with one of the following:
** None (empty, not upgradable)
** None (WWAN upgradable)
* [[MiniPCI Express slot]] 3 with one of the following:
** None (empty)
** [[Intel® Turbo Memory hard drive cache]] up to 2GB
* [[ExpressCard slot|ExpressCard/54 slot]]
* [[ThinkPad_Bluetooth_with_Enhanced_Data_Rate_(BDC-2.1)|Bluetooth]] on select models
* [[Integrated Fingerprint Reader]] (Authentec 2810) on select models
* Intel HD Audio with a [[CX20561]] codec
* 1.3MP [[Integrated camera]]
* [[Embedded Security Subsystem|Trusted Computing Group TPM 1.2]]
* [[Active Protection System]]
* Battery Sizes - 4 cell, 6 cell, 9 cell (sticks out the back)
</div>
|style="vertical-align:top" |
[[Image:ThinkPadX200s.jpg|ThinkPad X200s|300px]]
|}

==== Resources ====
* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-70149 Hardware Maintenance Manual (HMM)]
*Debian Lenny install: http://comcap.free.fr/x200s.html
*Debian Sid install: http://larsgg.spaces.live.com/blog/cns!2019B2D8CDA6ED!748.entry
*Arch Linux install: http://itgen.blogspot.com/2008/12/installing-arch-linux-on-lenovo.html
*CentOS 5 install: http://wiki.centos.org/HowTos/Laptops/Lenovo/Thinkpad-X200s

The above Debian related links explain the hoop-jumping required (in early 2009) for x200s models that have the 5300 wireless card. However if you have a model containing the 5100 (e.g 7469-5KG) then a standard Debian Lenny install ('HD-media' on USB key+wireless net install) works fine and is straightforward.

==== Reviews ====
http://forum.thinkpads.com/viewtopic.php?t=67851

[[Category:X Series]]

Intel Core 2 Duo (Merom)

2009-01-17T16:40:49Z

Xdeller:

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">

The Intel 2 Core is the successor of the [[Intel Core Duo (Yonah)]] processor. Unlike the Yonah, the Merom was designed specifically with mobile applications in mind. The Merom introduced various architectural additions such as EM64T, [[SIMD|SSSE3]] and improved the performance by up to 25 percent. The 667 MHz FSB versions are part of the "Napa" platform, while the 800MHz FSB versions are part of the "Santa Rosa" platform. The chip is also part of the hardware from both the Centrino Duo and Centrino Pro brands.

=Features=
*Dual Core
*EM64T
*[http://en.wikipedia.org/wiki/Vanderpool#Intel_Virtualization_Technology_.28Intel_VT.29 Intel Virtualization Technology ]
*XD-Bit
*[[SIMD|MMX]], [[SIMD|SSE]], [[SIMD|SSE2]], [[SIMD|SSE3]], [[SIMD|SSSE3]] instruction sets
*667 or 800 MHz FSB
*65 nm fabrication process
*4 MB or 2 MB L2-Cache with dynamic cache sizing
*[[SpeedStep|Enhanced Intel SpeedStep (EIST)]], power states: normal (C0), AutoHALT/MWAIT (C1), Stop Grant (C2), Deep Sleep (C3), [[QuickStart and Deeper Sleep|Deeper Sleep]] (C4)
</div>
|}

=Available Types and ThinkPads featuring them=
==Standard Voltage==
{| border=1 cellspacing=0 cellpadding=2
|- style="background:#ffdead;white-space:nowrap;"
! Nr. || colspan=2 | Frequency (MHz) || L2 Cache || FSB (MHz)|| VT || colspan=2 | core Voltage (V) || colspan=2 | TDP (W) || ThinkPad Models
|- style="background:#ffdead;"
! !!max. !! min. !! !! !! !! high !! low !! high freq !! low freq !!
|-
| T8300 || 2400 || 800 || 3MB || 800 || yes || 1.25 || 1 ? || ? || ? || {{X61}}, {{T61}}, {{R61}}
|-
| T7800 || 2600 || 1000 || 4MB || 800 || yes || 1.30 || 0.85-0.9 || 35 || ? || {{T61p}}
|-
| T7700 || 2400 || 1000 || 4MB || 800 || yes || 1.30 || 0.85-0.9 || 35 || ? || {{R61}}, {{T61}}, {{T61p}}
|-
| T7600 || 2333 || 1000 || 4MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{T60}}, {{T60p}}
|-
| T7500 || 2200 || 1000 || 4MB || 800 || yes || 1.30 || 0.85-0.9 || 35 || ? || {{R61}}, {{T61}}, {{X61}}
|-
| T7400 || 2166 || 1000 || 4MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{T60}}, {{T60p}}, {{Z61t}}
|-
| T7300 || 2000 || 800 || 4MB || 800 || yes || 1.30 || 0.85-0.9 || 35 || ? || {{R61}}, {{T61}}, {{X61}}
|-
| T7200 || 2000 || 1000 || 4MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{R60}}, {{T60}}, {{X60}}, {{Z61m}}, {{Z61t}}
|-
| T7100 || 1800 || 1000 || 2MB || 800 || yes || ? || 0.85-0.9 || 35 || ? || {{R61}}, {{T61}}
|-
| T5600 || 1833 || 1000 || 2MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{R60}}, {{T60}}, {{X60}}, {{Z61t}}
|-
| T5500 || 1666 || 1000 || 2MB || 667 || no || 1.30 || 0.95 || 34 || 20 || {{R60}}, {{T60}}, {{X60}}, {{Z61m}}, {{Z61t}}
|}

==Low Voltage==
{| border=1 cellspacing=0 cellpadding=2
|- style="background:#ffdead;white-space:nowrap;"
! Nr. || colspan=2 | Frequency (MHz) || L2 Cache || FSB (MHz)|| VT || colspan=2 | core Voltage (V) || colspan=2 | TDP (W) || ThinkPad Models
|- style="background:#ffdead;"
! !!max. !! min. !! !! !! !! high !! low !! high freq !! low freq !!
|-
| L7400 || 1500 || 1000 || 4MB || 667 || yes || 1.2 || 0.85 - 0.9 || 17 || ? || {{X60s}}, {{X60_Tablet}}
|-
| L7500 || 1600 || 800 || 4MB || 800 || yes || 1.1 || 0.85 - 0.9 || 17 || ? || {{X61s}}, {{X61_Tablet}}
|-
| L7700 || 1800 || 800 || 4MB || 800 || yes || 1.1 || 0.85 - 0.9 || 17 || ? || {{X61s}}, {{X61_Tablet}}
|-
| SL7100 || 1200 || 800 || 4MB || 800 || yes || 1.1 || 0.85 - 0.9 || 12 || ? || {{X300}}
|}

As you can see, the Low-Voltage CPU's work at the same Voltage as the normal CPUs when running in SLFM. With a simple tool (RMClock) you can use those lower voltages at every clock.
Intel gave other voltage-regions for the CPUs:

''the standard processor that works on a core voltage between 1.075V and 1.175V, the low voltage processors that work between 0.975V and 1.062V and finally the ultra low voltage processors that work between 0.80V and 0.975V.''

Intel doesn't think of the SLFM. With SLFM and a little bit luck, you're T-CPU can be thriftier than a LV-CPU but has more power.
With RMClock every T-CPU is thriftier than a LV-CPU, because you have the same voltage but a higher max-clock, so the sleep-states can be longer.

=Thermal Specifications=
The maximum temperature for safe operation is 100°C.

The catastrophic thermal protection temperature is 125°C.

Idle temperature is typically around 30-50°C.

Temperature at full utilisation is around 60-70°C.

These latter two values will of course depend largely on cooling systems and available airflow.

=Compiler optimisation flags=
==GCC==
In addition to the architecture independent <code>-O[0123s]</code> option hierarchy, architecture dependent optimisations are controlled by the <code>-march=<cpu-type></code> and <code>-mtune=<cpu-type></code> options. The <cpu-type> argument (not surprisingly) describes the type of cpu for which to optimise the compiled code. The <code>-mtune</code> option will generate code that is optimised for the given cpu type which will nevertheless run on cpu types other than the optimisation target. On the other hand, <code>-march</code> will attempt to optimise more aggressively at the expense of reducing portability to other cpu types. Optimisations implied by <code>-mtune</code> are a subset of <code>-march</code> optimisations, and thus it is only necessary to specify <code>-march</code> if the the maximum level of optimisation is desired.

With version of gcc before 4.3, 32-bit code should be compiled with the "prescott" as the cpu-type argument to <code>-march</code> or <code>-mtune</code> whereas 64-bit code should use the "nocona" argument. Gcc 4.3 however introduces "core2" as a valid argument to the <code>-mtune</code> and <code>-march</code> options which should be used. Alternatively, as of gcc 4.2, the "native" argument is supported. This will automatically determine the cpu-type on which compilation is taking place and apply optimisations specific to that cpu.

==Intel==
For the [http://www.spec.org/cpu2006/ SPEC CPU 2006 benchmarks], Intel used the shorthand <code>-fast</code>, which translates into <code>-O3 -ipo -static -no-prec-div -xP</code>. However, the compiler also provides the flag <code>-xT</code>, which activates the optimization for Core 2 Duo and SSSE3 (instead of SSE3 only with <code>-xP</code>).

=Microcode=
Much like software products, bugs, errata or ways to improve upon operation are often found in CPU's after they have reached the market. In some cases, the necessary changes can be applied by the end user without any change to the underlying hardware in the form of microcode updates downloadable from the manufacturer. Intel offers these microcode updates for download on their [http://downloadcenter.intel.com/Detail_Desc.aspx?ProductID=2676&DwnldID=14303&lang=eng website].

Provided the availability of the <tt>microcode</tt> and <tt>firmware</tt> kernel modules (which are enabled in the stock kernels of most distributions) and a suitable user space tool such as [http://urbanmyth.org/microcode/ microcode_ctl], one can install the updated microcode into their processors at runtime. The microcode update is volatile however, meaning that it disappears upon reboot. While this reduces the risk of applying such an update to essentially 0, it does mean that it must be applied on each boot.
==Debian==
You can install the microcode.ctl package which will take care of everything (including downloading the microcode itself) for you. Just run
{{cmdroot|aptitude install microcode.ctl}}. This package includes an init script which will run at boot to load the microcode into the processor. This script also contains a line which will remove the <tt>microcode</tt> kernel module once the operation is complete and it is no longer needed, however it is strangely commented out by default. If you want to keep your loaded modules (used memory) to a minimum, you can edit {{path|/etc/init.d/microcode.ctl}} and uncomment the line
<pre>
[ -x /sbin/modprobe ] && /sbin/modprobe -r microcode > /dev/null 2> /dev/null
</pre>
==Gentoo==
The <tt>microcode-ctl</tt> utility can be installed as follows: {{cmdroot|emerge microcode-ctl}}. This will create an init script <tt>/etc/init.d/microcode_ctl</tt>, but will not automatically set it to run on startup; to do so, run {{cmdroot|rc-update add microcode_ctl boot}}. Also, this will install an old copy of the microcode to <tt>/etc/microcode.dat</tt>; to update it, download a new copy from the link above and replace this file.

=Note on Hyper-Threading=
Note that as opposed to Pentium 4/NetBurst, current Core 2 do not support hyper-threading, and therefore there is usually no option in the BIOS to activate it. Refer to Intel's [http://www.intel.com/products/ht/hyperthreading_more.htm Hyper-Threading Technology] for a list of hyper-threading capable CPU.

=See also=
[[Intel_Core_Solo_(Yonah)|Intel Core Solo (Yonah)]]

[[Intel Core Duo (Yonah)]]

== External Links ==
*[http://www.intel.com/products/processor_number/chart/core2duo.htm Intel - Processor Numbers and Features]
*[http://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors#Mobile_processors Wikipedia - Intel Core 2 mobile microprocessors]

[[Category:Components]]