https://www.thinkwiki.org/w/api.php?action=feedcontributions&user=Marcusb&feedformat=atomThinkWiki - User contributions [en]2024-03-28T21:53:17ZUser contributionsMediaWiki 1.31.12https://www.thinkwiki.org/w/index.php?title=BIOS_Upgrade&diff=56139BIOS Upgrade2015-01-20T11:53:19Z<p>Marcusb: /* On Debian and Ubuntu */</p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__<br />
|style="vertical-align:top" |<br />
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.<br />
<br />
Updating the BIOS in Linux (with few exceptions) '''is not officially supported''' by Lenovo. However there are work arounds.<br />
<br />
<BR><br />
{{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.<br />
<br />
'''Proceed at your own risk!'''}}<br />
|}<br />
<br />
= Downloading New Firmware =<br />
{{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.}}<br />
<br />
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://support.lenovo.com/en_US/downloads/default.page?#|ThinkPad driver matrix].<br />
<br />
Lenovo/IBM provides firmware upgrades in a variety of packages:<br />
* Diskette<br />
* Non-diskette<br />
* Linux diskette<br />
* BIOS Utility<br />
* Bootable CD<br />
<br />
Not every type of package is available for every model.<br />
<br />
The ''BIOS Utility'' and ''Bootable CD'' packages combine the BIOS and ECP firmwares. For the other packages, there is one for each firmware.<br />
{| align="right" style="width:20em;"<br />
| {{HELP|Can an image be extracted from a "Linux diskette" .exe file?}}<br />
|}<br />
<br />
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. <br />
<br />
You may need to try different packages to find the one from which you can extract a boot image.<br />
<br />
== Two Firmwares: BIOS and ECP ==<br />
{{WARN|Flashing incompatible firmwares, or flashing them in the wrong order, may cause permanent damage to your ThinkPad.}}<br />
<br />
It is important to understand that Thinkpads from IBM have two separate firmwares: the BIOS, and the Embedded Controller Program (ECP).<br />
<br />
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'''. <br />
<br />
=== Update Order ===<br />
The Lenovo/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'''.<br />
<br />
The EC firmware is usually much better at backwards compatibility than the BIOS.<br />
<br />
{{NOTE|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.}}<br />
<br />
== Installed Firmware ==<br />
You can check the current BIOS and ECP versions on your ThinkPad by using '''dmidecode'''. For example:<br />
<br />
{{cmdroot|dmidecode -s bios-version}}<br />
<br />
1RETDRWW (3.23 )<br />
<br />
{{cmdroot|dmidecode -t 11}}<br />
<br />
# dmidecode 2.9<br />
SMBIOS 2.33 present.<br />
Handle 0x0029, DMI type 11, 5 bytes<br />
OEM Strings<br />
String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-<br />
<br />
Showing BIOS version 3.23 (1RETDRWW) and ECP version 3.04 (1RHT71WW).<br />
<br />
===DMI IDs===<br />
Please consider updating the [[List of DMI IDs]] before (and after) updating your BIOS.<br />
<br />
= Updating Firmware =<br />
<br />
Firmware flasher program can run on DOS (Lenovo PC DOS) or Windows but, unfortunately, not Linux. So ''in theory'' there are two basic steps to update the firmware (either the BIOS or the ECP) on a ThinkPad not running Windows:<br />
# Get or create a bootable image with supported OS<br />
# Boot that image and, if not started automatically, ran flasher program<br />
<br />
Recent Thinkpads have firmwares available as ''Bootable CD'' image, e.g., FILENAME.iso. If you have an optical drive there is no need to read this page any further: just download .iso image, burn it and boot to flash bios. If you are not that lucky, read on.<br />
<br />
First you need to realize that there are different ways to boot DOS on PC (theoretically it is possible to boot Windows to ran flasher, but why?...): from internal hard drive, CD drive, USB Flash drive or, as the last resort, floppy drive. Easiest way is from internal hard drive, but you'd better avoid touching it until you don't want to loose files there. [[Booting from a Floppy]] is not recommended, so there are two best options to boot: CD drive or USB Flash drive.<br />
<br />
Sparse instructions below provide you guidance how to do different parts of this pazzle but it's your duty to understand what to do and how to do that.<br />
<br />
== Create a bootable image ==<br />
<br />
In case Lenovo does not provide your laptop with ''Bootable CD'' it is possible to create one from *discket packages.<br />
<br />
=== Extracting an update image ===<br />
{{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.}}<br />
{{NOTE|Lenovo has changed the packaging format. Old bios can be extracted with [http://freshmeat.net/projects/cabextract/ '''cabextract'''], new ones with [http://innoextract.constexpr.org/ '''innoextract'''].}}<br />
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:<br />
<br />
:{{cmduser|cabextract 1iuj13us.exe}}<br />
<br />
Extracting cabinet: 1iuj13us.exe<br />
extracting 1IUJ13US.IMG<br />
extracting BIOSUPTP.EXE<br />
extracting DOBOOT.EXE<br />
extracting DOSBOOT.COM<br />
extracting DOSBOOT.SYS<br />
extracting DOSBOOT.VXD<br />
extracting DOSBOOT2.COM<br />
extracting ECTLUPTP.EXE<br />
extracting EFLASHAS.SYS<br />
extracting HDFWUPTP.EXE<br />
extracting IBMTPI.XML<br />
All done, no errors.<br />
<br />
The file we want is '''FILENAME.IMG''', with "FILENAME" being the .exe. you downloaded. E.g., {{path|1IUJ13US.IMG}}.<br />
<br />
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.<br />
<br />
==== If cabeextract/innoextract fails ====<br />
<br />
Diskette .exe for some older models can't be extracted using cabextract. For example for the latest BIOS of 390E one gets<br />
spsdilc9.exe: no valid cabinets found<br />
Since such .exe will only extract the files to a floppy, there seems to be no way to extract them using Linux. The situation is actually even more complicated, as neither Vista nor Windows 7 allow these .exe to access the floppy drive directly. Neither DosBox nor Wine were able to "fool" the programm using virtual floppies.<br />
<br />
A solution that works is to use Windows XP (works in VirtualBox too) together with [http://sourceforge.net/projects/vfd/ Virtual Floppy Drive]. Rund vfdwin.exe, go to the Driver tab and hit Install and Start. Then go to the Drive0 tab, click on Change and select A:. Finally, click on Open/Create, and click Create. This should give you a virtual floppy drive the .exe file will extract files to.<br />
<br />
Another solution is to use QEMU with a DOS diskette image to run the disk extractor.<br />
<br />
==== Testing the Image ====<br />
<br />
You can test that FILENAME.IMG is really a floppy image by running:<br />
<br />
{{cmdroot|mkdir /tmp/mntfloppy}}<br />
<br />
{{cmdroot|mount -o loop FILENAME.IMG /tmp/mntfloppy}}<br />
<br />
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:<br />
<br />
{{cmdroot|ls /tmp/mntfloppy}}<br />
$0195000.FL1 069580.PAT 06d2.HSH IBMDOS.COM TPCHKS.EXE<br />
0691.HSH 06D0.PAT 06d6.HSH LOGO.BAT UPDTFLSH.EXE<br />
0691.PAT 06D1.PAT 06d8.HSH LOGO.SCR UPDTMN.EXE<br />
0694.HSH 06D2.PAT CHKBMP.EXE PHLASH16.EXE USERINT.EXE<br />
0694.PAT 06D6.PAT COMMAND.COM PREPARE.EXE UTILINFO.EXE<br />
0695.HSH 06D8.PAT CONFIG.SYS PROD.dat lcreflsh.bat<br />
0695.PAT 06d0.HSH FLASH2.EXE QKFLASH.EXE<br />
069580.HSH 06d1.HSH IBMBIO.COM README.TXT<br />
<br />
Unmount the image after you are done testing:<br />
<br />
{{cmdroot|umount /tmp/mntfloppy}}<br />
<br />
== Booting from update image ==<br />
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.<br />
<br />
There are different ways to do that:<br />
* [[#Booting from a CD|Boot from a CD]]<br />
* [[#Booting_using_GRUB|Boot image using bootloader (e.g. GRUB)]]<br />
* [[#Booting_from_a_USB_Flash_drive|Boot from a USB Flash drive]]<br />
* [[#Booting_from_a_floppy|Boot from a floppy]]<br />
<br />
=== Booting from a CD ===<br />
{| align="right" style="width:40em;"<br />
|{{HINT|If there is a ''Bootable CD'' image available, e.g., FILENAME.iso, just download that, instead of mucking around with image files.}}<br />
|}<br />
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.<br />
<br />
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.<br />
<br />
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:<br />
<br />
{{cmdroot|genisoimage -b 1WUJ25US.IMG -c boot.catalog -o bootcd.iso 1WUJ25US.IMG}} #or older mkisofs<br />
<br />
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.<br />
<br />
You can now burn the {{path|bootcd.iso}} to a CD in your favorite CD-burning program.<br />
{{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!'''}}<br />
<br />
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 [[BIOS_Upgrade#Update_Order|proper order]].<br />
<br />
{| align="center"<br />
| {{HELP|Please, report your success/failure with flashing BIOS from the manually cooked CD (from .IMG file) here: [[BIOS_Upgrade_success_failure#Booting_from_CD]]}}<br />
|}<br />
<br />
=== Booting using GRUB ===<br />
{|<br />
| style="width:75%" | {{WARN|Many have warned '''not''' to use the SYSLINUX image-loader '''memdisk''' to boot firmware update images.}}<br />
| style="font-size:80%" | {{HELP|Who are these "many"? Link to a discussion?}}<br />
|}<br />
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]'''.<br />
<br />
Locate the '''memdisk''' file from the syslinux package. You can search for it with '''find''': <br />
<br />
{{cmdroot|find /usr -name memdisk}} #or just use "dlocate memdisk" or "locate memdisk" if these programs are installed<br />
<br />
If {{path|/usr/.../memdisk}} is not present, syslinux is not installed. You will need to install it to boot a .IMG from GRUB.<br />
<br />
Copy both the '''FILENAME.IMG''' and '''memdisk''' files into {{path|/boot}} directory. For example:<br />
<br />
{{cmdroot|cp ./FILENAME.IMG /usr/share/syslinux/memdisk /boot/}}<br />
<br />
Open {{path|/boot/grub/menu.lst}} in your favourite editor. '''Copy''' the active section into a '''new section''', and edit the new section:<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
! Parameter<br />
! Instructions<br />
! Example<br />
|-<br />
| ''title'' || Pick a name for the new section. This will show up in the GRUB boot menu. || <tt>title IBM ECP Update</tt><br />
|-<br />
| ''root'' || Do not change. This is the partition containing the {{path|/boot}} directory || <tt>root (hd0,0)</tt><br />
|-<br />
| ''kernel'' || '''/boot/memdisk''' will allow you to boot an image file. || <tt>kernel /boot/memdisk</tt><br />
|-<br />
| ''initrd'' || This is the name of the firmware-updater image file, e.g., 1IUJ13US.IMG || <tt>initrd /boot/1IUJ13US.IMG</tt><br />
|}<br />
<br />
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.<br />
<br />
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}}.<br />
<br />
{{NOTE|If both BIOS and ECP are to be updated, be sure to update them in the [[#Proper_Order|proper order]].}}<br />
<br />
{{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!'''}}<br />
<br />
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}}.<br />
<br />
==== Booting image with GRUB2 ====<br />
===== GRUB2: booting floppy Image =====<br />
With grub2, one would ''append'' the following to ''/boot/grub/grub.cfg'' :<br />
menuentry "My BIOS Upgrade" {<br />
set root=(hd0,0) #should match the others in your grub.cfg<br />
linux16 /boot/memdisk<br />
initrd16 /boot/1WUJ25US.IMG #or whatever yours is<br />
}<br />
<br />
{| align="center"<br />
| {{HELP|Please, report your success/failure with flashing BIOS from the manually cooked CD (from .IMG file) here: [[BIOS_Upgrade_success_failure#GRUB2:_Booting_floppy_Image]]}}<br />
|}<br />
<br />
===== GRUB2: booting CD Image =====<br />
You must first download the bootable iso file from the Lenovo Website.<br />
<br />
===== On Debian and Ubuntu ===== <br />
Then, on Debian and Ubuntu, you can install the grub-imageboot package, then you just have to copy the iso file in /boot/images and run update-grub:<br />
<pre><br />
sudo apt-get install grub-imageboot<br />
sudo mkdir -p /boot/images<br />
sudo cp /home/youruser/Downloads/6uuj12uc.iso /boot/images<br />
sudo update-grub<br />
</pre><br />
<br />
===== Manual method =====<br />
Otherwise, 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:<br />
<pre><br />
sudo su -<br />
cd /boot<br />
cp /home/youruser/Downloads/6uuj12uc.iso .<br />
cp /usr/share/syslinux/memdisk .<br />
ln -s 6uuj12uc.iso biosupgrade.iso<br />
</pre><br />
Now create the boot entry:<br />
<pre><br />
cat >> /etc/grub.d/40_custom <<EOF<br />
menuentry "Lenovo BIOS Upgrade" {<br />
set root=(hd0,1) # <-- check for correct numbering<br />
linux16 /boot/memdisk iso<br />
initrd16 /boot/biosupgrade.iso<br />
}<br />
EOF<br />
update-grub<br />
</pre><br />
Reboot an Select "Lenovo BIOS Upgrade".<br />
<br />
For the next Bios Upgrade you'll just need to copy the new iso file to /boot and adjust the symlink.<br />
<br />
{| align="center"<br />
| {{HELP|Please, report your success/failure with flashing BIOS from the manually cooked CD (from .IMG file) here: [[BIOS_Upgrade_success_failure#GRUB2:_Booting_CD_Image]]}}<br />
|}<br />
<br />
=== Booting from a USB Flash drive ===<br />
<br />
==== Updating the BIOS in MS-DOS mode ====<br />
(This process works for most Thinkpad models that has Windows XP, Windows Vista or Windows 7 OS)<br />
<br />
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].<br />
<br />
2. Extract the (*.ima) from the ISO BIOS image (e.g. [http://www.rarsoft.com WinRAR] will do this).<br />
<br />
3. Using a tool that can open .IMA files (such as [http://www.winimage.com/ WinImage]), extract all files to a temporary folder.<br />
<br />
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!<br />
<br />
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.<br />
<br />
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.<br />
'''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.'''<br />
<br />
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.<br />
<br />
7. Power on the laptop then enter the BIOS setup by pressing F1 and Load BIOS defaults.<br />
<br />
==== Using grub4dos (also for Linux) ====<br />
<br />
[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:<br />
* 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.)<br />
* Unpack<br />
* Insert your FAT-32 formatted pendrive<br />
* 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.<br />
* Copy the files <code>grldr</code> and <code>menu.lst</code> to the root directory of your pendrive.<br />
* Convert the ThinkPad .IMG file to a .ISO file using <code>genisoimage -b 1yuj18us.img -c boot.catalog -o 1yuj18us.iso 1yuj18us.img</code><br />
* Copy the ISO image to the root directory of your pendrive (e.g. <code>1yuj18us.iso</code>).<br />
* Edit <code>menu.lst</code> on the pendrive and include the following section (of course putting the appropriate ISO image name):<br />
<pre><br />
title thinkpad-bios<br />
map (hd0,0)/1yuj18us.iso (hd32)<br />
map --hook<br />
chainloader (hd32)<br />
boot<br />
</pre><br />
* Reboot and press F12 to select booting from USB.<br />
* 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.<br />
<br />
==== Manually creating a USB Flash drive in Linux ====<br />
<br />
Use "geteltorito" to extract the update image from ISO image, downloaded from Lenovo's drivers page. Write the extracted image to a USB Flash drive using dd. "geteltorito" is available in Ubuntu (at least in Trusty, 14.04) from package "genisoimage".<br />
* Install the genisoimage package: <code>sudo apt-get install genisoimage</code><br />
* Extract the boot image from the ISO: <code>geteltorito g6uj14us.iso > biosupdate.img</code><br />
* Install the boot image to USB Flash drive, make sure to install to the correct device! (device for me was /dev/sdb): <code>sudo dd if=biosupdate.img of=/dev/<yourusbflashdevice> bs=512K</code><br />
* Reboot and press F12 to select booting from USB.<br />
* If all went well, you should be able to boot the Thinkpad's ISO image and flash the BIOS. I tested it successfully on X1 Carbon.<br />
<br />
=== Booting from a Floppy ===<br />
{{WARN|Using a floppy disk '''is NOT recommended'''.}}<br />
<br />
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.<br />
<br />
So, why is it not recommended?<br />
# If something goes wrong, your ThinkPad may be permanently damaged<br />
# Floppy disk drives are not reliable<br />
# Floppy disks are not reliable<br />
# It only works with /dev/fd0, meaning it won't work with a USB floppy<br />
<br />
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.<br />
<br />
If you really want to do it with a floppy, some tips:<br />
* Use a clean (in the physical sense) floppy drive<br />
* Use new floppies<br />
* Test floppies for errors before starting update process<br />
* Have multiple copies of the update disks ready--if one should fail, replace it with a copy<br />
* Should DOS complain of a read error, '''only''' respond wth "Retry"<br />
<br />
{{NOTE|Should the system encounter a disk read error during the flash process, and you select "Abort", your system could be permanently damaged.}}<br />
<br />
==== Using UNetbootin ====<br />
<br />
Unetbootin 422 worked with the image files unpacked with cabextract on my x31.<br />
<br />
{{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?)}}<br />
<br />
=== Booting from a Network Boot Image ===<br />
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.<br />
<br />
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.<br />
<br />
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<br />
<br />
=After updating=<br />
Lenovo recommends reseting your BIOS settings to their factory defaults after a firmware update.<br />
<br />
Also, please consider updating the [[List of DMI IDs]] after updating your BIOS.<br />
<br />
= Special Cases =<br />
* 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.<br />
<br />
== Updating Thinkpad X Series ==<br />
The special update instructions for {{X_Series}} Thinkpads are quite long. You can find them at the page [[BIOS_Upgrade/X_Series]].<br />
<br />
== Alternative BIOS: Middleton BIOS ==<br />
Some Thinkpad models only support SATA1 in their BIOS even though the hardware is SATA2. This is a huge drawback for anyone wanting to use SSDs, because it is so much slower.<br />
<br />
Also, it is not possible to install some wireless cards, because only certain models are whitelisted by IBM/Lenovo. The Middleton Bios removes this limitation as well.<br />
<br />
Someone made these alternative BIOSes to enable SATA2 on the Thinkpad models that support this. See [http://forum.notebookreview.com/lenovo/459591-t61-x61-sata-ii-1-5-gb-s-cap-willing-pay-solution-8.html#post6501443 the 'notebook review' forum post] for download links and explanations ([http://www.ali.dj/sata-ii-support-for-lenovo-thinkpad-t61-x61-r61/ Alternative link]).<br />
<br />
Note: If your BIOS-Update tool says that no update is needed, then simply downgrade the Bios first: On Lenovo's/IBM's download page, the old Bios files are listed at the very bottom of the page.<br />
<br />
== Updating without battery or with dead battery ==<br />
<br />
This is a last-resort approach. Use this only if everything else fails.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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".<br />
<br />
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 as 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://www.mediafire.com/?36o5a8buvbjx07o 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:<br />
<br />
*updtrom /np /prep1<br />
*updtrom /np /prep2<br />
*updtrom /np /prep3<br />
*updtrom /np /romcmp /romflsh /prep4<br />
*updtrom /np /h8flsh /h8img /model<br />
<br />
Yes, you need to run updtrom five times. Hold your breath and reboot the machine. It's done.<br />
<br />
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.<br />
<br />
For the {{i1400}} follow instructions on [http://www.motherboardpoint.com/flash-ibm-thinkpad-bios-w-o-battery-t143180.html this] website. It works not only for 2611 but for 2621 types too.<br />
<br />
----<br />
<br />
{{footnotes|<br />
# 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)].<br />
}}</div>Marcusbhttps://www.thinkwiki.org/w/index.php?title=PC2-5300&diff=37935PC2-53002008-06-08T04:21:54Z<p>Marcusb: /* Available PC2-5300 memory from other manufacturers */</p>
<hr />
<div>__NOTOC__<br />
{| width="100%"<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
=== PC2-5300 ===<br />
This is DDR2-SDRAM memory at 333 MHz in 200-pin SO-DIMM form-factor.<br><br />
PC2-5300 memory is also called DDR2-667.<br />
<br />
</div><br />
|style="vertical-align:top" |<br />
[[image:so-dimm.jpg|SO-DIMM]]<br />
|}<br />
<br />
=== Available memory types from Lenovo ===<br />
{| border=1 cellspacing=0 cellpadding=2<br />
|- style="background:#ffdead;white-space:nowrap;"<br />
! Partnumber !! FRU !! Description<br />
|-<br />
| 40Y7732 || 40Y8401 || 256MB PC2-5300 DDR2 CL5 SO-DIMM<br />
|-<br />
| 40Y7733 || 40Y8402 || 512MB PC2-5300 DDR2 CL5 SO-DIMM<br />
|-<br />
| 40Y7734 || 40Y8403 || 1GB PC2-5300 DDR2 CL5 SO-DIMM<br />
|-<br />
| 40Y7735 || 40Y8404 || 2GB PC2-5300 DDR2 CL5 SO-DIMM<br />
|}<br />
<br />
=== ThinkPads that support this technology ===<br />
{| border=1 cellspacing=0 cellpadding=2<br />
|- style="background:#ffdead;white-space:nowrap;"<br />
! ThinkPad Models !! Soldered<br>On Systemboard !! DIMM<br>Slot 1 !! DIMM<br>Slot 2 !! Official<br>Max-Memory !! Unofficial<br>Max-Memory{{Footnote|1}}<br />
|-<br />
| {{T60}}, {{T60p}} || || Occupied || depends || 4GB{{Footnote|2}} {{Footnote|3}} || 4GB{{Footnote|2}} {{Footnote|3}}<br />
|-<br />
| {{R61}}, {{T61}}, {{T61p}} || || Occupied || depends || 4GB{{Footnote|2}} || 4GB{{Footnote|4}}<br />
|-<br />
| {{R60e}} || || Occupied || depends || 4GB{{Footnote|2}} {{Footnote|3}} || 4GB{{Footnote|2}} {{Footnote|3}}<br />
|-<br />
| {{X60}}, {{X60s}}, || || Occupied || Empty || 4GB{{Footnote|2}} {{Footnote|3}} || 4GB{{Footnote|2}} {{Footnote|3}}<br />
|-<br />
| {{X61}}, {{X61s}}, {{X61_Tablet}} || || Occupied || depends || 4GB{{Footnote|2}} || 4GB{{Footnote|2}} {{Footnote|3}}<br />
|-<br />
| {{Z61e}}, {{Z61m}}, {{Z61p}}, {{Z61t}} || || Occupied || Empty || 3GB || Unknown<br />
|-<br />
| {{X300}} || || Occupied || depends || 4GB{{Footnote|2}} || 4GB{{Footnote|4}}<br />
|}<br />
{{Footnotes|<br />
# See [[Unofficial maximum memory specs]]<br />
# Based on 2x 2GB DIMMs.<br />
# Due to Intel 945 chipset limitation, addressable memory will be (4GB - I/O space) ~ 3.2GB<br />
# Due to Intel 965 chipset limitation, max addressable memory is 4GB<br />
}}<br />
<br />
== Available PC2-5300 memory from other manufacturers ==<br />
{| border=1 cellspacing=0 cellpadding=2<br />
|- style="background:#ffdead;white-space:nowrap;"<br />
! Manufacturer !! Partnumber !! Description !! Tested on model<br />
|-<br />
| [http://www.crucial.com Crucial] || [http://www.crucial.com/store/partspecs.Asp?IMODULE=CT2KIT12864AC667 CT2KIT12864AC667] || 2x1 GB || {{R60e}} ([[0657-3LG]]{{Footnote|1}})<br />
|-<br />
| [http://www.crucial.com Crucial] || [http://www.crucial.com/store/partspecs.Asp?IMODULE=CT25664AC667 CT25664AC667] || 2 GB || {{T60}} ([[1951-A47]])<br />
|-<br />
| [http://www.crucial.com Crucial] || [http://www.crucial.com/store/partspecs.Asp?IMODULE=CT2KIT6464AC667 CT2KIT6464AC667] || 2x512 MB ||<br />
|-<br />
| [http://www.crucial.com Crucial] || [http://www.crucial.com/store/partspecs.Asp?IMODULE=CT12864AC667 CT12864AC667] || 1 GB ||<br />
|-<br />
| [http://www.crucial.com Crucial] || [http://www.crucial.com/store/partspecs.Asp?IMODULE=CT6464AC667 CT6464AC667] || 512 MB ||<br />
|-<br />
| [http://www.crucial.com Crucial Rendition] || RM12864AC667{{Footnote|4}} || 1 GB || {{T60}} ([[2007-49G]])<br />
|-<br />
| [http://www.transcendusa.com Transcend] || [http://ec.transcendusa.com/product/ItemDetail.asp?ItemID=TS2GIB3847 TS2GIB3847] || 2 GB || {{R60}} {{X41}}<br />
|- <br />
<br />
| [http://www.gskill.com/indexen.html G.Skill] || [http://www.gskill.com/en/f2-5400phu1-sa.html F2-5400PHU1-1GBSA] || 1 GB || {{T60p}} ([[2007-93G]]{{Footnote|2}})<br />
|-<br />
| [http://www.corsair.com Corsair] || [http://www.corsair.com/products/notebook_memory.aspx VS1GSDS667D2] || 1 GB || {{Z61m}}<br />
|-<br />
| [http://www.corsair.com Corsair] || [http://www.corsair.com/products/notebook_memory.aspx VS2GSDS667D2] || 2 GB || {{T60}} ([[2007-FSG]]) {{Z61m}} {{X60}} ([[1707-V28]])<br />
|-<br />
| [http://www.corsair.com Corsair] || [http://www.corsair.com/products/notebook_memory.aspx VS4GSDSKIT667D2] || 2x2 GB{{footnote|5}} || {{R60}} ([[9456-HTG]])<br />
|-|-<br />
| [http://www.gskill.com/indexen.html G.Skill] || [http://www.gskill.com/en/f2-5300cl5s-sa.html F2-5300CL5S-2GBSA]{{Footnote|3}} || 2 GB ||<br />
|}<br />
{{Footnotes|<br />
#The memory module that was shipped with this laptop had the same [http://www.micron.com Micron] logo as the modules from [http://www.crucial.com Crucial], which is a division of that company.<br />
# Memory for T60p spec is CL5, but this module which was CL4 works fine. The product page at [http://www.gskill.com/indexen.html G.Skill] describes it wrongly as a CL5 module.<br />
#Some users reported the RAM module is in fact overclocked from 533MHz to 677MHz, hence some systems may report 533MHz and/or CL4<br />
#Crucials website doesnt list Rendition memory, but the memory is clearly labelled as Crucial Rendition by several resellers<br />
# Due to Intel 945 chipset limitation, addressable memory will be (4GB - I/O space) ~ 3.2GB<br />
}}<br />
<br />
[[Category:Components]]</div>Marcusbhttps://www.thinkwiki.org/w/index.php?title=Category:R60&diff=37934Category:R602008-06-08T04:13:33Z<p>Marcusb: note that 945 chipset cannot address full 4 GB RAM</p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
=== ThinkPad R60 ===<br />
This page gives an overview of all ThinkPad R60 related topics.<br />
<br />
==== Standard Features ====<br />
* One of the following processors:<br />
** [[Intel Celeron M]] 1.4, 1.6 GHz CPU<br />
** [[Intel Core Duo (Yonah)]] 1.66, 1.83, 2.0, 2.2, 2.33 GHz CPU<br />
** [[Intel Core 2 Duo (Merom)]] 1.83 CPU<br />
** [[Intel Core Solo (Yonah)]] 1.66 GHz CPU<br />
* One of the following graphics adapters:<br />
** [[Intel Graphics Media Accelerator 950]] - only for 1024x768 and 1400x1050 displays<br />
** [[ATI Mobility Radeon X1300]] (64 MB)<br />
** [[ATI Mobility Radeon X1400]] (128 MB)<br />
* One of the following displays:<br />
** 14.1" TFT display with 1024x768 resolution<br />
** 14.1" TFT display with 1400x1050 resolution<br />
** 15.0" TFT display with 1024x768 resolution<br />
** 15.0" TFT display with 1400x1050 resolution<br />
** 15.0" TFT display with 1600x1200 resolution<br />
* 512 MB or 1 GB [[PC2-5300]] memory standard upgradable to 4 GB{{footnote|1}}<br />
* 40, 60, 80, 100 or 120 GB SATA HDD<br />
* One of the following Audio Controllers<br />
** [[AD1981HD]] HD Audio 1.0 controller<br />
** Intel audio controller [[Intel_82801G_HDA]] (in [[9456-6FG]] Version)<br />
* One of the following Ethernet controllers:<br />
** [[Ethernet Controllers#Intel Gigabit (10/100/1000)|Intel Gigabit Ethernet Controller]]<br />
** [[Ethernet Controllers#Broadcom Gigabit (10/100/1000)|Broadcom Gigabit Ethernet Controller]]<br />
* [[UltraBay|UltraBay Enhanced]] with the following:<br />
** CD-ROM drive<br />
** CD-RW/DVD-ROM Combo drive<br />
** DVD±RW/DVD-RAM drive<br />
* [[MiniPCI Express slot]] 1 with one of the following:<br />
** None (empty)<br />
** [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter]]<br />
** [[IBM 11a/b/g Wireless LAN Mini PCI Adapter]]<br />
** [[ThinkPad 11a/b/g Wireless LAN Mini Express Adapter]]<br />
** Bluetooth Version 2.0 + EDR <br />
* [[MiniPCI Express slot]] 2 with one of the following:<br />
** None (empty)<br />
* [[CardBus slot]] (Type 2)<br />
* [[ExpressCard slot|ExpressCard/53 slot]]<br />
* [[Embedded Security Subsystem|IBM Embedded Security Subsystem 2.0]]<br />
* [[Active Protection System|IBM Active Protection System]]<br />
* [[Integrated Fingerprint Reader]] on select models<br />
* [[Bluetooth]]<br />
* [[UltraNav]] (TrackPoint / Touchpad combo)<br />
* [http://www.ibm-laptop-batteries.co.uk/Thinkpad-R60-battery.html Thinkpad R60 battery]<br />
{{footnotes|<br />
#Due to Intel 945 chipset limitation, addressable memory will be (4GB - I/O space) ~ 3.2GB<br />
}}<br />
</div><br />
|style="vertical-align:top" |<br />
[[image:ThinkPadR60.jpg|300 px|ThinkPad R60]]<br />
|}<br />
<br />
[[Category:R Series]]</div>Marcusbhttps://www.thinkwiki.org/w/index.php?title=Talk:How_to_configure_the_TrackPoint&diff=28713Talk:How to configure the TrackPoint2007-03-13T19:57:59Z<p>Marcusb: /* shifting /sys-paths */</p>
<hr />
<div>==== /sys-configuration files ====<br />
where can i find documentation of the other files (thresh, upthresh, skipback, reach, inertia...)? [[User:Blerp|Blerp]] 01:01, 9 March 2007 (CET)<br />
<br />
==== shifting /sys-paths ====<br />
2007-03-13<br />
On my Thinkpad R60 with kernel 2.6.20, the path is {{path|/sys/devices/platform/i8042/serio1/serio2}}.<br />
<br />
On {{Fedora}} 5, with kernels 2.6.15 and forward, the path does not include <br />
{{path|serio2}}; it stops at {{path|serio0}}. <br />
<br />
Same thing on a {{Ubuntu}} Dapper install on an {{X31}}, again with kernel 2.6.15 (maybe that's the reason? [[User:Piccobello|Piccobello]] 17:02, 26 November 2006 (CET)).<br />
<br />
2006-07-18<br />
On {{Fedora}} 5, with kernels 2.6.16 and forward, the path is {{path|/sys/devices/platform/i8042/serio0/serio2}}<br />
<br />
2005-11-07<br />
OpenSuSE 10.0 has a kernel based on 2.6.13 (probably heavily patched), but the directory /sys/devices/platform/i8042/serio0/serio2 does not exist.<br />
instead, it looks like this:<br />
hoppetosse:/sys/devices/platform/i8042/serio0 # ls -l<br />
total 0<br />
-rw-r--r-- 1 root root 4096 Nov 7 18:38 bind_mode<br />
lrwxrwxrwx 1 root root 0 Nov 7 18:38 bus -> ../../../../bus/serio<br />
-r--r--r-- 1 root root 4096 Nov 7 18:38 description<br />
lrwxrwxrwx 1 root root 0 Nov 7 18:38 driver -> ../../../../bus/serio/drivers/psmouse<br />
--w------- 1 root root 4096 Nov 7 18:38 drvctl<br />
drwxr-xr-x 2 root root 0 Nov 7 18:38 id<br />
-r--r--r-- 1 root root 4096 Nov 7 18:38 modalias<br />
drwxr-xr-x 2 root root 0 Nov 7 18:38 power<br />
-rw-r--r-- 1 root root 4096 Nov 7 18:38 protocol<br />
-rw-r--r-- 1 root root 4096 Nov 7 18:38 rate<br />
-rw-r--r-- 1 root root 4096 Nov 7 18:38 resetafter<br />
-rw-r--r-- 1 root root 4096 Nov 7 18:38 resolution<br />
"description" says it's an "i8042 Aux Port". The page [[Patch to enable advanced trackpoint configuration]] seems to imply that a kernel patch is needed in order to get those features... this needs clarification.<br />
hmm. where can i find out whether "drvctrl" is what i'm looking for and what options it takes? guess it's back to RTFS...<br />
<br />
2005-10-06<br />
It seems that new version of the patch ( 2.6.12 at least ), the press to select entry in /sys is named "press_to_select" and not "ptson". I changed the page accordingly so that it complies with the [[Patch to enable advanced trackpoint configuration]] page.<br />
If you use an older version try :<br />
<br />
====Press to Select====<br />
Press to Select allows you to tap the control stick which will simulate a left click. You can enable this feature by typing the following in to a terminal (you may need to be root):<br />
<br />
:{{cmdroot|echo 1 > /sys/devices/platform/i8042/serio0/ptson}}<br />
<br />
Press to Select should now be enabled. You can disable it in a similar manner:<br />
<br />
:{{cmdroot|echo 0 > /sys/devices/platform/i8042/serio0/ptson}}<br />
<br />
==== No mouse in {{Fedora}} Core 6 ====<br />
FC6 makes an X11/xorg.conf file with no mouse section, so it's not clear how to make the TrackPoint work for scrolling. Any ideas? --[[User:Whizkid|Whizkid]] 17:36, 4 December 2006 (CET)</div>Marcusb