Talk:BIOS Upgrade

From ThinkWiki
Revision as of 22:53, 21 February 2006 by Andersolsson (Talk | contribs) (Upgrading BIOS and Embedded Control Program from Win XP: - Added comment)

Jump to: navigation, search

BIOS upgrade without battery

Concerning the known problem with 600 series with batteries dead too soon, it is impossible to upgrade the bios without the battery because the original ibm update program doesn't allow this. I bought an old 600E without the battery. There was one workaround, but i think for the older releases of the bios, where you just extracted files and upgraded manualy, bypassing the ibm install program. The page that describes this (i lost the link) has a list of different files, that the ones found in current release so i never did figure out what to do? I would like to upgrade because i have really old bios, where ACPI doesn't cooperate so well with the operating system, either windows or linux.

If somebody finds a workaround please help. Thanks

Bios upgrade & hidden partition

I have disabled the hidden partition to make more space for linux (24G). I still have Windows on the 14G partition. Is it safe to upgrade the BIOS without the hidden partition? I want to get a newer BIOS to fix the annoying fan issue. Thanks

- yes don't worry about it. bios upgrades have nothing to do with whats inside the harddrive.

BIOS upgrade over PXE


I have a Thinkpad X20 with a very early BIOS and Embedded Controller Program which I'd like to update. Currently, the only feasible way of doing this is over the network using PXE. I already have a fully functional PXE server using SYSLINUX, and have so far been able to boot the BIOS diskette image using MEMDISK, although I have not attempted to flash anything yet due to the warnings given on the page. Is there any safe way I can update both the Controller Program and the BIOS in the same session over the network in this manner? If not, what other methods would be suitable? I have a USB CD-ROM drive and could probably get hold of a USB floppy drive.


Update: I ended up burning CDs as described and successfully updated everything. I'd still like to know if there is a way I could do it entirely over the network, though.

RE: grub initrd

"Another possibility which works even without a CD-drive or network is to boot the disk image via the grub initrd mechanism."

0) Interesting suggestion. Might be better of in its own section.

1) Could you please elaborate?

2) My first guess (pending your elaboration) would be to "chainload" the first block of the diskimage using the grub commandline, like:

  blocklist (path)/to/diskimage
  chainloader blockvalue+1

But that's just a guess!

Paul Bolle Fri Jul 15 12:20:47 CEST 2005

bios/controller update sequence

The article says: "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"

When I look at the IBM udpate instructions for the T23, it says: "If you need to update the BIOS as well as the Embedded Controller Program, update the BIOS first."


> I would first contact IBM for clarification, but you should probably be following instructions specific to your model.

>> I did it following IBM's instructions to upgrade the BIOS first. Everything worked out great!

Firmware upgrade for Intel minipci combo card

I just purchased an Intel 10/100 Ethernet Mini-PCI Adapter with 56K Modem that has an ancient (2.0.6) firmware version. I Downloaded the update file intlbtag.EXE but cabextract was unable to find any cabfiles inside it. I tried running the program via wine and that didn't work either.

Finally I ran the program on a windows machine and created a boot floppy. Then I went through the the process of converting the floppy to a bootable cd via linux and that worked like a charm. The cd successfully updated the minipc card's firmware.

Everything worked but I ended up needing a windows box to do it. Could this have been done without windows?

Firmware upgrade for Wireless LAN MiniPCI COMBO Card using prism2_srec

The appropriate firmware installation program for the wlan card in my R32 can be extracted using cabextract as described in the article. It contains (besides some installation programs) a disk image (1awg06ww.IMG) that seems to be a simple dos boot disk. This image contains 3 .hex files (id010001.hex, pk010100.hex, sf010402.hex) that are recognized by prism2_srec to be "srec"-files. Trying to load them to RAM yields:

   # prism2_srec -v -r wlan0 sf010402.hex
   S3 CRC-16 generation record: start=0x007E1800 len=65642 prog=1
   Start address 0x00000000
   srec summary for sf010402.hex
   Component: 0x001f 1.4.2 (station firmware)
   Interface compatibility information:
   role=Supplier variant=2 range=1-9 iface=Station Firmware-Driver (4)
   role=Actor    variant=1 range=1-1 iface=Modem-Firmware (1)
   role=Actor    variant=2 range=1-1 iface=Controller-Firmware (2)
   role=Actor    variant=1 range=4-4 iface=Primary Firmware-Driver (3)
   Wireless LAN card information:
   NICID: 0x8013 v1.0.0
   PRIID: 0x0015 v1.0.7
   STAID: 0x001f v1.3.6
   Interface compatibility information:
   PRI role=Supplier variant=1 range=1-1 iface=Modem-Firmware (1)
   PRI role=Supplier variant=2 range=1-1 iface=Controller-Firmware (2)
   PRI role=Supplier variant=1 range=4-4 iface=Primary Firmware-Driver (3)
   STA role=Supplier variant=1 range=1-9 iface=Station Firmware-Driver (4)
   PRI role=Actor    variant=2 range=1-1 iface=Controller-Firmware (2)
   STA role=Actor    variant=2 range=1-1 iface=Controller-Firmware (2)
   STA role=Actor    variant=1 range=1-1 iface=Modem-Firmware (1)
   This image is not meant to be downloaded to volatile memory.
   Incompatible update data.

Has anyone tried to flash this device using prism2_srec yet? What bothers me is, that the upgrade is for many different parts of the combo card. Does anyone have an opinion on whether this could work?

OK, I took the risk and successfully upgraded my station firmware, BUT when I tried to upgrade the primary firmware the system froze!!! The thinkpad won't start up with the miniPCI card inserted and all efforts to reflash it using the original DOS boot image failed!!!

I'm quite sure the system freeze was not caused directly by prism2_srec, because I have noticed rare system freezes since I have been using my PCMCIA wireless card. Anyway, if anyone should own a TP R32, I'd be glad if he could tell me the base address of the Wlan card, or it's PCI address.

Thinkpad r32 owner here. I want to upgrade the firmware as well. If you need any information just send an email to haftbar[a] Quickie 02:12, 1 February 2006 (CET)

Reorganization suggestion

The Downloads section is rather long. Would it be an idea to put it on a separate, new page (say: BIOS_Downloads) and link to that new page from this page?

Paul Bolle 21:27, 15 Oct 2005 (CEST)

> I agree with this suggestion.

Upgrading BIOS and Embedded Control Program from Win XP

I'm trying to upgrade the BIOS and Embedded Controller Program from Windows XP following the instructions on the Lenovo website. The problem is the instructions are not very clear about this. The instructions basically state that I must upgrade them at the same time because the Control Program does not work with the older BIOS and the BIOS does not work with the older Control Program. They also state that I should upgrade the Control Program first.

But that means I must boot into XP after having upgraded the Control Program but with the older BIOS in order to then update the BIOS. But if this works then they are actually compatible and there's a contradiction. Am I missing something? I just want to make sure I don't end up with a non-functioning unit.

I have an X23 and want the latest BIOS (v 1.32) and Control Program (v 1.30).

Maybe there should be a note about this in the article? Or maybe I'm the only one who is this stupid :)

Update: I talked to Lenovo support. The situation apparently is that though the description says that the newer control program is not compatible with the older BIOS, they are not so incompatible as to cause the machine to stop working so it is actually possible to use incompatible versions of BIOS and control program. In fact according to the support person it makes no difference if the BIOS is upgraded before the control program or vice versa. So I upgraded the control program using the executable running in Windows XP, which rebooted the computer to perform the upgrade and then I booted Windows again to upgrade the BIOS in the same manner and it all worked fine. If anyone reading this finds it useful maybe you can put it in the article? Or if you find it superfluous just delete this section.