*Empty MediaWiki Message*

This commit is contained in:
Daniel.plominski 2015-02-15 06:42:38 +00:00
parent 337cb9cc13
commit 2b8fa047d9
1 changed files with 33 additions and 0 deletions

View File

@ -36,6 +36,39 @@ Beispielsweise kann das Gerät zum exeplarischen Testen für das Installieren vo
== Siehe auch ==
* [http://www.thinkwiki.org/wiki/Category:T61 thinkwiki:category:T61]
== BIOS/AMT ==
BIOS-Update auf 2.30 durch Trick:
For the t61 lenovo I renamed the $01af000.fl1 to bios.rom and I renamed the $01af000.fl2 to platform.bin. Then use the winphlash tool that is apart of the bios update download from lenovo (it is in the folder you download). I browsed to the bios.rom file and ran the update with out problems. the system rebooted and came up normaly. I had the same problem with a battery error and this got around it.
I flashed the middleton BIOS for an R61i (14.1" model 7732 with firewire): battery is also dead, so I used WinPlash.exe directly, skipping WINUPTP.EXE. (As the latter insists on a charged battery.)
I renamed the image files as well, but I guess its of no importance. Initially I thought `platform.bin` is linked to from `bios.rom`, but no. It turned out that the embedded controller did not got flashed! I was lucky the new BIOS worked with the old controller.
Once rebooted into Windows, I restarted the tool and selected platform.bin, flashed it (I got a warning, see below), then canceled the reboot (be quick!), then selected bios.rom and flashed it again. And I ended up with a working system with both BIOS and EC updated.
How did I know the tool can do multiple flashes in a row without reboot?
I actually flashed bios.rom twice in the beginning, just to see the behaviour of the tool without risking too much.
How did I know platform.bin will not get flashed over the BIOS instead of updating the Embedded Controller?
Before flashing I tried the “Backup BIOS only” option a couple of times. WinPlash reads the image file in any case and checks compatibility according to the screen messages. This gave me a hint that platform.bin has to contain instructions on what to do, because the EC would never ever pass as proper system BIOS. I also tried doing backup with a random file as image, which crashed WinPhlash. So I was pretty sure the image is read for backup and it does make sense for the tool. I also noticed that the backup file is ~4MB for a BIOS backup, but only ~2MB for the EC (e.g. backup started with platform.bin instead of bios.rom).
Did I get any surprises?
Yes, the platform.bin backup-and-flash gave me a warning. "... The System Platform may be different from the Image file." WinPhlash also mentioned the version string of the (new) BIOS (e.g. 7LETC7WW and something like 7KHTR0K0, which looks like the version string of a virgin Embedded Controller). Proceed Yes/No? I thought: if it overwrites the EC now, it is exactly what I want. If it overwrites the BIOS, well, I plan to flash the BIOS again anyway, so maybe it works. (And it did!)
Anything on the timing?
The BIOS flash took like 1-2 minutes, doing 21 blocks. The EC was only 2 blocks, so it was faster. I kept an eye on the screen, because you have only 10 seconds to cancel the reboot after flashing finishes.
{{foo im HQ}}