Difference between revisions of "BIOS Upgrade"
(→X Series) |
(→T Series) |
||
| Line 544: | Line 544: | ||
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-63024 1.04] | | [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-63024 1.04] | ||
| | | | ||
| − | | [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-63027 1.04] | + | | [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-63027 1.04] (CD) |
| | | | ||
| | | | ||
| Line 602: | Line 602: | ||
|- | |- | ||
| {{X60}}, {{X60s}} | | {{X60}}, {{X60s}} | ||
| − | |||
| | | | ||
| − | | | + | | |
| + | | | ||
| | | | ||
| | | | ||
Revision as of 10:31, 15 April 2006
|
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. NOTE!
In one case (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.
|
Before You Begin
Updating the BIOS in Linux (with few exceptions) is not officially supported by IBM. However there are work arounds.
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 clearly state that you must update the BIOS first, then immediately update the Control Program. 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 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
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 BIOS-Bootsplash). 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 mntfloppy look like a dos floppy, and no read errors were displayed, you have a pretty good chance that the floppy image is usable.
Downloads
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.
Another possibility which works even without a CD-drive or network is to boot the disk image via the grub initrd mechanism.
Be aware that IBM officially does not support this! The official statement to my support request was:
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
But it seems to be possible as Mathias Dalheimer describes this 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 other vendors to flash the BIOS from bootable CD-ROMs.
Some interesting but very technical information about the used flash tool can be found 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 can also create a floppy image by using Ken Kato's VMware's back. It is a free Windoze tool that creates a virtual floppy drive and allows you to produce an image file ready to be ISO'ed. Note: you might have to 'manually' (through application's interface) assign the virtual drive a volume letter in order to be seen by IBM's application (as, by default, it seems not to do it).
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 cabextract method 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 $ man mkisofs.
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 |
| A20p (2629-6VU) |
|
| A21e (2628-JXU) |
|
| R31 |
|
| R40 |
|
| R50 (1836-3SU) |
|
| R51 (1829) |
|
| R51 (1830-RM7) |
|
| R51 (2887) |
|
| T20 |
|
| T22 |
|
| T23 |
|
| T40 |
|
| T40p |
|
| T41 |
|
| T41p |
|
| T42 |
|
| T42p |
|
| T43 |
|
| X20 |
|
| X21 |
|
| X22 |
|
| X23 |
|
| X30 |
|
| X31 |
|
| X40 |
|
Does not work:
| Model | Tested by |
Please note that testing this is at your own risk!!!
Updating via Grub and a Floppy Image
Floppy images may be booted from Grub via a utility called MEMDISK, which may be compiled from the SYSLINUX source. Copy the compiled memdisk image and the floppy image to your boot directory and configure grub as follows:
title Bios Flash kernel /boot/memdisk initrd /boot/FILENAME.img
Again, proceed at your own risk. This was tested on an R51 type 2888.
Updating with Network Boot Image
BIOS, Embedded Controller (EC), CD/DVD and Harddisk firmware disks can be booted over the network with PXELINUX as part of the 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.
Check List
The following is important to remember:
- You must update both the Control Program and the BIOS at the same time if your current Control Program is not compatible with the new BIOS (see below)
- 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
When the Control Program and the BIOS need updating, have both update disks or CDs ready. Update the Control Program first and the system should switch itself off when finished. Insert the BIOS update disk and proceed to update the BIOS. When it's all finished, enter setup, reset the settings to their defaults and reboot. Enter setup again and tweak the settings as necessary.
- 240
- 240X
- 365C
- 365CD
- 365CS
- 365CSD
- 365E
- 365ED
- 365X
- 365XD
- 380
- 380D
- 380E
- 380ED
- 385D
- 385ED
- 380XD
- 385XD
- 380Z
- 390
- 390E
- 390X
- 560
- 560E
- 560X
- 560Z
- 570
- 570E
- 600
- 600E
- 600X
- 750
- 750CS
- 755C
- 755CS
- 755CE
- 755CSE
- 755CD
- 755CX
- 755CV
- 755CDV
- 760C
- 760CD
- 760L
- 760LD
- 760E
- 760ED
- 760XD
- 765D
- 765L
- 760EL
- 760ELD
- 760XL
- 770
- 770E
- 770ED
- 770X
- 770Z
- A20m
- A20p
- A21e
- A21m
- A21p
- A22e
- A22m
- A22p
- A30
- A30p
- A31
- A31p
- G40
- G41
- R30
- R31
- R32
- R40
- R40e
- R50
- R50p
- R50e
- R51
- R51e
- R52
- T20
- T21
- T22
- T23
- T30
- T40
- T40p
- T41
- T41p
- T42
- T42p
- T43
- T43p
- T60
- T60p
- X20
- X21
- X22
- X23
- X24
- X30
- X31
- X32
- X40
- X41
- X41 Tablet
- X60
- X60s
- Z60m
- Z60t
- TransNote
