ThinkWiki - User contributions [en]

BIOS Upgrade

2005-03-12T13:52:34Z

SeanDague: /* The Non Diskette Updater */ realize that cabextract is all you need

__TOC__
----

==Before You Begin==

This page is meant to describe ways to update the BIOS on a Thinkpad that only runs Linux for users that don't have ready access to Windows (if you have Windows on your thinkpad you can just boot into it and follow instructions on the IBM website). Updating the BIOS in Linux (with few exceptions) '''is not officially supported''' by IBM. However there are work arounds. By following any of the instructions here you are accepting the '''very real risk''' of turning your thinkpad into a big expensive paper weight, as a firmware update gone wrong can create unfixable problems.

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

It is also '''important''' to understand that all newer thinkpads have 2 seperate firmwares, the BIOS and the Control Program. A specific version of the Control Program will only work with specific versions of the BIOS. If you go through the readme's on the IBM site they'll cleary state that '''you must''' update the Control Program first, then imediately update the BIOS. Otherwise you risk turning your thinkpad into a very nice paper weight.

==BIOS Upgrade Paths==

For every firmware (either BIOS or Control Program) update on the IBM site there are two different firmware update programs provided.

===The Diskette Updater===

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

===The Non Diskette Updater===

'''Warning: Though I've used this process on 1 version of .exe files found on ibm.com website this doesn't mean it will work for all of them. Use at your own risk'''

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

cabextract FILENAME.exe

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

mkdir mntfloppy
mount -o loop FILENAME.img mntfloppy
ls -la mntfloppy

If the results of ls -la look like a dos floppy, and no read errors were displayed, you have a pretty good chance that the floppy image is usable. Again, proceed at your own risk.

==Updating from within Windows==

If you have windows on your machine... you probably never found this page anyway as you wouldn't need it. ;) However updating the BIOS from Windows is very easy, and the supported way to do it by IBM. Simply follow the IBM instructions, as described on the respective BIOS upgrade page on the IBM site.

==Downloads==

{| border="1" cellspacing="0" cellpadding="2"
| rowspan="3"| '''Models'''
| colspan="2"| '''Non-Diskette'''
| colspan="3"| '''Diskette'''
|-
| rowspan="2"| '''BIOS'''
| rowspan="2"| '''Embedded Controller Program'''
| colspan="2"| '''BIOS'''
| rowspan="2"| '''Embedded Controller Program'''
|-
| '''Windows'''
| '''Linux'''
|-
| A31, A31p
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-44450 44450]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-45662 45662]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-44451 44451]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-45898 45898]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-45663 45663]
|-
| G40
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50672 50672]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50673 50673]
|
|
|-
| R40 (2681, 2682, 2683, 2896, 2898, 2899)
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-46055 46055]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-46143 46143]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-46061 46061]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-46144 46144]
|-
| R40 (2722, 2723, 2724, 2897)
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50320 50320]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-46143 46143]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50321 50321]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-46144 46144]
|-
| R40e
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50302 50302]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50344 50344]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50301 50301]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50343 50343]
|-
| R50/p, R51 (1829, 1830, 1831, 1836), T40/p, T41/p, T42/p
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50273 50273]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50279 50279]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50275 50275]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50277 50277]
|-
| R50e
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-55000 55000]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-54996 54996]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-55001 55001]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-54997 54997]
|-
| R51 (2883, 2887, 2888, 2889, 2894, 2895)
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-55003 55003]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-54996 54996]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-55004 55004]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-54997 54997]
|-
| T30
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-42694 42694]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-42711 42711]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-42720 42720]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-45745 45745]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-42725 42725]
|-
| X31
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50298 50298]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-53480 53480]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50308 50308]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-53479 53479]
|-
| X40
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-53881 53881]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-53882 53882]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-53883 53883]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-53885 53885]
|}

==Updating via Floppy==

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

==Updating via CD/DVD Drive==

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

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

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

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

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

Another indication that it should work is that IBM uses PHLASH16.EXE (at least on T4x/p systems) to flash the BIOS into the chip. The same tool is used by [http://www.samsungpc.com/gb/support/p35/bios/bios-instructions.html other vendors] to flash the BIOS from bootable CD-ROMs.

'''WARNING!''' Do '''not''' use the [http://syslinux.zytor.com/ SYSLINUX] image-loader [http://syslinux.zytor.com/memdisk.php MEMDISK] to boot the images! Some flash tools crash in that situation!

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

===Creating a Floppy Image===

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

dd bs=2x80x18b if=/dev/fd0 of=/tmp/floppy.img

You should verify this floppy.img as explained above.

===Creating a Bootable CD from a Floppy Image===

Once you have your floppy image, either from imaging a real floppy, or from extracting them via the Wine trick above, you need to make a boot CD out of it.

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

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

mkisofs -b bootfloppy.img -o bootcd.iso bootfloppy.img

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

You can now burn the bootcd.iso in your favorite cd burning program.

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

===Does work:===
{|
| '''Model''' || '''Tested by'''
|-
| R31 || [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/1998-January/009743.html Mathias Dalheimer]
|-
| T40 || Sean Dague (http://dague.net)
|-
| T40p || Lukas KrÃ¤henbÃ¼hl, ismo at pop dot agri dot ch
|-
| T42p || Robert Schiele <rschiele@uni-mannheim.de>, Joern Heissler <joern@heissler.de>
|-
| X40 || Robbie Stone <robbie@serendipity.cx>
|}

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

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

==Updating with Network Boot Image==

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

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

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

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

==Rentry Check List==

(With appologies to Ed Nisley)

The following is important to remember:
# You must update '''both''' the Control Program and the BIOS at the same time
# You must find versions of the Control Program and BIOS that are compatible. Not all of them are, so follow the readmes on the IBM website carefully to determine which are.
# You must update the Control Program '''before''' you update the BIOS
# All of these instructions are provided with '''no warranty'''. A bios update gone wrong for any reason can '''completely destroy''' your Thinkpad.

BIOS Upgrade

2005-03-12T13:24:45Z

SeanDague: massive update adding more step by step processes here

__TOC__
----

==Before You Begin==

This page is meant to describe ways to update the BIOS on a Thinkpad that only runs Linux for users that don't have ready access to Windows (if you have Windows on your thinkpad you can just boot into it and follow instructions on the IBM website). Updating the BIOS in Linux (with few exceptions) '''is not officially supported''' by IBM. However there are work arounds. By following any of the instructions here you are accepting the '''very real risk''' of turning your thinkpad into a big expensive paper weight, as a firmware update gone wrong can create unfixable problems.

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

It is also '''important''' to understand that all newer thinkpads have 2 seperate firmwares, the BIOS and the Control Program. A specific version of the Control Program will only work with specific versions of the BIOS. If you go through the readme's on the IBM site they'll cleary state that '''you must''' update the Control Program first, then imediately update the BIOS. Otherwise you risk turning your thinkpad into a very nice paper weight.

==BIOS Upgrade Paths==

For every firmware (either BIOS or Control Program) update on the IBM site there are two different firmware update programs provided.

===The Diskette Updater===

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

===The Non Diskette Updater===

'''Warning: Though I've used this process on 1 version of .exe files found on ibm.com website this doesn't mean it will work for all of them. Use at your own risk'''

This installer appears to be a 32bit windows exe which is designed for updating the BIOS directly from a running Windows OS. It will run under wine far enough to trick the program into giving you the .img files you need to update your BIOS.

The trick is as follows:
# Run wine FILENAME.exe from your favorite terminal
# Accept the Terms & Conditions
# Immediately type Ctrl-Z in the terminal, suspending the program

In your wine tmp dir, i.e. whatever wine thinks is C:\tmp, you will find a randomly named directory with 6 or so files. One of those files will be FILENAME.img, and be about 1.4 MB. This should be the floppy image of the updater.

You can test that this is really a floppy image by running:

mkdir mntfloppy
mount -o loop FILENAME.img mntfloppy
ls -la mntfloppy

If the results of ls -la look like a dos floppy, and no read errors were displayed, you have a pretty good chance that the floppy image is usable. Again, proceed at your own risk.

[http://www.digriz.org.uk/t40p-linux/#bios-update Source Material for this Section]

==Updating from within Windows==

If you have windows on your machine... you probably never found this page anyway as you wouldn't need it. ;) However updating the BIOS from Windows is very easy, and the supported way to do it by IBM. Simply follow the IBM instructions, as described on the respective BIOS upgrade page on the IBM site.

==Downloads==

{| border="1" cellspacing="0" cellpadding="2"
| rowspan="3"| '''Models'''
| colspan="2"| '''Non-Diskette'''
| colspan="3"| '''Diskette'''
|-
| rowspan="2"| '''BIOS'''
| rowspan="2"| '''Embedded Controller Program'''
| colspan="2"| '''BIOS'''
| rowspan="2"| '''Embedded Controller Program'''
|-
| '''Windows'''
| '''Linux'''
|-
| A31, A31p
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-44450 44450]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-45662 45662]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-44451 44451]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-45898 45898]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-45663 45663]
|-
| G40
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50672 50672]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50673 50673]
|
|
|-
| R40 (2681, 2682, 2683, 2896, 2898, 2899)
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-46055 46055]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-46143 46143]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-46061 46061]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-46144 46144]
|-
| R40 (2722, 2723, 2724, 2897)
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50320 50320]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-46143 46143]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50321 50321]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-46144 46144]
|-
| R40e
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50302 50302]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50344 50344]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50301 50301]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50343 50343]
|-
| R50/p, R51 (1829, 1830, 1831, 1836), T40/p, T41/p, T42/p
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50273 50273]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50279 50279]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50275 50275]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50277 50277]
|-
| R50e
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-55000 55000]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-54996 54996]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-55001 55001]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-54997 54997]
|-
| R51 (2883, 2887, 2888, 2889, 2894, 2895)
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-55003 55003]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-54996 54996]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-55004 55004]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-54997 54997]
|-
| T30
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-42694 42694]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-42711 42711]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-42720 42720]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-45745 45745]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-42725 42725]
|-
| X31
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50298 50298]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-53480 53480]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50308 50308]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-53479 53479]
|-
| X40
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-53881 53881]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-53882 53882]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-53883 53883]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-53885 53885]
|}

==Updating via Floppy==

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

==Updating via CD/DVD Drive==

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

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

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

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

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

Another indication that it should work is that IBM uses PHLASH16.EXE (at least on T4x/p systems) to flash the BIOS into the chip. The same tool is used by [http://www.samsungpc.com/gb/support/p35/bios/bios-instructions.html other vendors] to flash the BIOS from bootable CD-ROMs.

'''WARNING!''' Do '''not''' use the [http://syslinux.zytor.com/ SYSLINUX] image-loader [http://syslinux.zytor.com/memdisk.php MEMDISK] to boot the images! Some flash tools crash in that situation!

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

===Creating a Floppy Image===

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

dd bs=2x80x18b if=/dev/fd0 of=/tmp/floppy.img

You should verify this floppy.img as explained above.

===Creating a Bootable CD from a Floppy Image===

Once you have your floppy image, either from imaging a real floppy, or from extracting them via the Wine trick above, you need to make a boot CD out of it.

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

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

mkisofs -b bootfloppy.img -o bootcd.iso bootfloppy.img

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

You can now burn the bootcd.iso in your favorite cd burning program.

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

===Does work:===
{|
| '''Model''' || '''Tested by'''
|-
| R31 || [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/1998-January/009743.html Mathias Dalheimer]
|-
| T40 || Sean Dague (http://dague.net)
|-
| T40p || Lukas KrÃ¤henbÃ¼hl, ismo at pop dot agri dot ch
|-
| T42p || Robert Schiele <rschiele@uni-mannheim.de>, Joern Heissler <joern@heissler.de>
|-
| X40 || Robbie Stone <robbie@serendipity.cx>
|}

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

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

==Updating with Network Boot Image==

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

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

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

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

==Rentry Check List==

(With appologies to Ed Nisley)

The following is important to remember:
# You must update '''both''' the Control Program and the BIOS at the same time
# You must find versions of the Control Program and BIOS that are compatible. Not all of them are, so follow the readmes on the IBM website carefully to determine which are.
# You must update the Control Program '''before''' you update the BIOS
# All of these instructions are provided with '''no warranty'''. A bios update gone wrong for any reason can '''completely destroy''' your Thinkpad.