Board:lenovo/x60/Installation
The wiki is being retired!
Documentation is now handled by the same processes we use for code: Add something to the Documentation/ directory in the coreboot repo, and it will be rendered to https://doc.coreboot.org/. Contributions welcome!
These Coreboot/Libreboot flashing instructions are designed for the Lenovo X60, X60s, X60 tablet, T60 and T60p.
Libreboot Flashing Procedure (Easy Method)
- Note: Libreboot is not officially part of the coreboot project. Do not contact coreboot for support; instead, contact the libreboot community.
The Libreboot distribution distributes pre-compiled ROM images along with scripts and instructions for easy flashing. Choose between these two guides:
- Official Libreboot Documentation - Official documentation created by the Libreboot developers themselves.
- Note: If you choose to follow the Official Libreboot Documentation, make sure to follow the Lenovo BIOS Backup procedure details below.
- BASLQC Libreboot ThinkPad Guides - Vastly streamlined unofficial Libreboot installation guide. Organized in a more straightforward fashion, and has a few tips and tricks for specific devices.
- ThinkPad X60 and X60 Tablet
- ThinkPad T60 (Intel GPU)
- Macbook 2 1
- ThinkPad T60/T60p (ATI GPU) - Requires proprietary VGABIOS.
Back up Official Lenovo BIOS (Libreboot)
It is STRONGLY RECOMMENDED to back up the vendor BIOS; each vendor BIOS image has a unique, unrecoverable ID. Do not use another laptop's vendor BIOS image.
- Download, extract, and build the latest Libreboot binaries.
- From the
libreboot_bin/
folder, enter theflashrom/
folder.cd flashrom
- Run both of these commands to backup the BIOS to
factory.bin
(don't panic, nothing is being installed):sudo ./flashrom_lenovobios_sst -p internal -r factory.bin
sudo ./flashrom_lenovobios_macronix -p internal -r factory.bin
- If a
factory.bin
file was created in theflashrom/
folder, the Lenovo BIOS has been backed up successfully. If not, try the commands again. Copy this dump to a safe place. - Return to the
libreboot_bin/
folder.cd ..
Coreboot Flashing Procedure (Advanced)
Below is a procedure that describes all the steps needed to flash Coreboot, in fine detail.
The Libreboot scripts have fully automated this complicated process, so these instructions have been expanded for educational purposes.
Briefing
- Some SPI Flash chips require special flashrom patches.
- Flash chips can be identified by various commands (REMS*, RDID etc.). Some of them reply with an ID for the vendor and the exact chip model; others just reply with a single byte.
- Unfortunately, the vendor BIOS forbids higher quality identification commands, so flashrom must be patched to use the lower quality opcodes.
- This type of patch will never be merged upstream, so it must be applied manually.
- The BUCTS register bit must be flipped before flashing Coreboot.
- The bucts utility can be used to flip the bit.
- This register bit doubles as a unique safety net that allows the vendor BIOS and Coreboot to coexist.
- Just unplug the CMOS battery to return to the vendor BIOS, in case Coreboot doesn't boot.
- The Coreboot ROM has to be specially patched to prevent it from overwriting the vendor BIOS.
- If the vendor BIOS gets overwritten, it would defeat the purpose of the BUCTS safety net.
- Just use this convenient little Bash one-liner to leave some free space at the beginning of the ROM.
dd if=coreboot.rom of=top64k.bin bs=1 skip=$[$(stat -c %s coreboot.rom) - 0x10000] count=64k; dd if=coreboot.rom bs=1 skip=$[$(stat -c %s coreboot.rom) - 0x20000] count=64k | hexdump; dd if=top64k.bin of=coreboot.rom bs=1 seek=$[$(stat -c %s coreboot.rom) - 0x20000] count=64k conv=notrunc
- It is important to figure outwhat type of flashchip is on the motherboard..
- Early Coreboot developers had to disassemble the entire laptop just to take a peek at the flashchip. A magnifying glass is needed to read the tiny text burned on top of the chip.
- The Libreboot installation scripts have an ingenious new brute-force method of identifying the flashchip.
- First, build two patched flashrom binaries, one for SST and one for Macronix. Then try both of the binaries until you find one that works.
- Seems way too simple, but it's way better than ripping out the motherboard just to look at a chip.
Flashrom Patch Definitions
Flashrom must be patched to use RES SPI identification and spi_chip_write_1
for your flash chip, and to set the flash chip model_id
to the RES opcode.
Below are the definitions that must be patched into flashrom/flashchips.c
:
- SST25VF016B
- .probe -
probe_spi_res2
- .model_id -
0x41
- .write -
spi_chip_write_1
- .probe -
- MX25l1605D
- .probe -
probe_spi_res1
- .model_id -
0x14
- .write -
spi_chip_write_1
- .probe -
- Atmel ??? (T60 Only?)
- Use -p internal:laptop=force_I_want_a_brick instead of -p internal, when running flashrom
- No patches necessary. You still need to do 2 flashing rounds, with the bucts/dd trick outlined in this guide.
These definitions were painstakingly discovered from excessively long and hardly informative flashchip documentation, mailing lists, and the output of flashrom. These definitions been confirmed to work after rigorous testing, See this wiki page for more information.
- Flashrom Pastebin - Thinkpad R60 Flashrom Output - Probing for SST SST25VF016B.RES2, 2048 kB: probe_spi_res2: id1 0xbf, id2 0x41
- Coreboot Mailing List - Invalid OPCODE - Allows us to infer that the model_id for
SST25VF016B
is 0xbf - Coreboot Mailing List - Bricked Lenovo T60
- Donderclumpen - Coreboot on Macbook 2,1] - Found
id1 0xbf, id2 0x2541
there, which corroborates with the inference from Peter Stuge. - SST - SST25VF016B Official Datasheet
What You Need
- The flashrom source (at least r1613 to make sure the laptops are whitelisted to work with flashrom)
- Flashrom patches for SST and Macronix flashchip support (provided in the next section).
- The bucts utility.
- Dependencies (Debian/Ubuntu/Trisquel):
- Version Control -
sudo apt-get install subversion git
- Build Essentials -
sudo apt-get -y install build-essential
- flashrom -
sudo apt-get install libpci-dev pciutils zlib1g-dev libftdi-dev
- Coreboot -
sudo apt-get install libncurses-dev iasl libc6-dev bison flex git
- GRUB2 (optional) -
sudo apt-get install bison libopts25 libselinux1-dev autogen m4 autoconf help2man libopts25-dev flex libfont-freetype-perl automake autotools-dev libfreetype6-dev texinfo ttf-unifont
- Version Control -
Patch Flashrom
This method uses the brute force flashchip identification method used in the Libreboot flashing scripts. The idea is, if the patched flashrom can't identify the chip, it won't do anything; so why not try both patches?
The most reliable method to identify the flashchip is to visually identify it; but flipping the motherboard requires complete disassembly.
First, build both the SST and Macronix patches of Flashrom.
Step 1: Build Normal Flashrom
- Obtain the latest
flashrom
source code with Subversion:svn co svn://flashrom.org/flashrom/trunk flashrom
- Build
flashrom
using themake
command.make
- Rename the
flashrom
binary toflashrom_orig
.mv flashrom flashrom_orig
Step 2: Build SST-patched Flashrom
- Open the
flashchips.c
file in theflashrom
source code folder. - Use Ctrl-F to find the
SST25VF016B
entry. - Modify the
.probe
,.model_id
, and.write
definitions with the following values.- .probe -
probe_spi_res2
- .model_id -
0x41
- .write -
spi_chip_write_1
- .probe -
- The result should look something like this:
{ .vendor = "SST", .name = "SST25VF016B", .bustype = BUS_SPI, .manufacture_id = SST_ID, .model_id = 0x41, .total_size = 2048, .page_size = 256, .feature_bits = FEATURE_WRSR_EITHER, .tested = TEST_OK_PREW, .probe = probe_spi_res2, /* unimportant code statements in between, leave them alone */ .write = spi_chip_write_1, .read = spi_chip_read, .voltage = {2700, 3600}, },
- Build
flashrom
using themake
command.make
- Rename the
flashrom
binary toflashrom_lenovobios_sst
.mv flashrom flashrom_lenovobios_sst
Step 3: Build Macronix-patched Flashrom
- Use Ctrl-F to find the
SST25VF016B
entry. - Modify the
.probe
,.model_id
, and.write
definitions with the following values.- .probe -
probe_spi_res1
- .model_id -
0x14
- .write -
spi_chip_write_1
- .probe -
- The result should look something like this:
{ .vendor = "Macronix", .name = "MX25L1605D/MX25L1608D/MX25L1673E", .bustype = BUS_SPI, .manufacture_id = MACRONIX_ID, .model_id = 0x14, .total_size = 2048, .page_size = 256, .feature_bits = FEATURE_WRSR_WREN, .tested = TEST_OK_PREW, .probe = probe_spi_res1, /* unimportant code statements in between, leave them alone */ .write = spi_chip_write_1, .read = spi_chip_read, /* Fast read (0x0B), dual I/O supported */ .voltage = {2700, 3600}, },
- Build
flashrom
using themake
command.make
- Rename the
flashrom
binary toflashrom_lenovobios_macronix
.mv flashrom flashrom_lenovobios_macronix
Step 4: Rename the Vanilla Flashrom Binary
We renamed the untouched flashrom binary to flashrom_orig
, so that it wouldn't be overwritten. Now we need to restore the original name.
- Rename the
flashrom_orig
binary toflashrom
.mv flashrom_orig flashrom
Back up Official Lenovo BIOS
It is STRONGLY RECOMMENDED to back up the vendor BIOS; each vendor BIOS image has a unique, unrecoverable ID. Do not use another laptop's vendor BIOS image.
- Enter the
flashrom/
folder.cd flashrom
- Run both of these commands to backup the BIOS to
factory.bin
(don't panic, nothing is being installed):sudo ./flashrom_lenovobios_sst -p internal -r factory.bin
sudo ./flashrom_lenovobios_macronix -p internal -r factory.bin -c "MX25L1605"
- If a
factory.bin
file was created in theflashrom/
folder, the Lenovo BIOS has been backed up successfully. If not, try the commands again. Copy this dump to a safe place. - Return to the
libreboot_bin/
folder.cd ..
Build the Coreboot ROM
- See Build HOWTO for how to build ROM images in coreboot.
- (optional) If you need to obtain and embed the VGABIOS in Coreboot (e.g. T60 with ATI GPU, text in SeaBIOS), follow this procedure.
- Here is a clearer guide which shows exactly how to build Coreboot, set up the
.config
file, and embed the VGABIOS.
Patch Coreboot ROM
The BUCTS switch provides a safety net in case Coreboot does not run the first time; just unplug the CMOS battery to return to the vendor BIOS.
This patch prevents the Coreboot ROM from overwriting the vendor BIOS (which would destroy the safety net). Choose one method:
Method 1: One-line Patcher
- Place the
coreboot.rom
file in the current folder. - Run this one-liner to patch the ROM in one command:
dd if=coreboot.rom of=top64k.bin bs=1 skip=$[$(stat -c %s coreboot.rom) - 0x10000] count=64k; dd if=coreboot.rom bs=1 skip=$[$(stat -c %s coreboot.rom) - 0x20000] count=64k | hexdump; dd if=top64k.bin of=coreboot.rom bs=1 seek=$[$(stat -c %s coreboot.rom) - 0x20000] count=64k conv=notrunc
Method 2: Verbose Method
- Copy the built
coreboot.rom
to theflashrom
source code folder. - Run the
dd
command below to shift the first 64K of data fromcoreboot.rom
dd if=coreboot.rom of=top64k.bin bs=1 skip=[(stat -c %s coreboot.rom) - 0x10000] count=64k
- Run the dd command below to display the first 64k of
coreboot.rom
dd if=coreboot.rom bs=1 skip=[(stat -c %s coreboot.rom) - 0x20000] count=64k | hexdump
- Verify that the complete range is filled with
ff
bytes before proceeding.- The output of the
dd
command above must EXACTLY match the text below. If not, the coreboot image needs to be rebuilt with the second-to-last 64kbyte block unused.0000000 ffff ffff ffff ffff ffff ffff ffff ffff *0010000
- The output of the
- Run the
dd
command below:dd if=top64k.bin of=coreboot.rom bs=1 seek=[(stat -c %s coreboot.rom) - 0x20000] count=64k conv=notrunc
- Source: gmane.linux.bios Mailing List - LinuxBIOS on T60 - Peter Stuge's Method of installing Coreboot on the X60.
Install Coreboot (First Flash)
First, install Coreboot alongside the vendor BIOS.
- Copy the
coreboot.rom
to theflashrom/
folder. - Run
su
to become root. - Run
bucts 1
- Flash Coreboot (run both of these commands, whichever works first):
sudo ./flashrom_lenovobios_sst -p internal -w coreboot.rom
sudo ./flashrom_lenovobios_macronix -p internal -w coreboot.rom
- This will take a while, and will spit out a few errors (since half the flashchip is write protected).
- Check to make sure that the errors match the following:
Reading old flash chip contents... done.
Erasing and writing flash chip... spi_block_erase_20 failed during command execution at address 0x0
Reading current flash chip contents... done. Looking for another erase function.
spi_block_erase_52 failed during command execution at address 0x0
Reading current flash chip contents... done. Looking for another erase function.
Transaction error!
spi_block_erase_d8 failed during command execution at address 0x1f0000
Reading current flash chip contents... done. Looking for another erase function.
spi_chip_erase_60 failed during command execution
Reading current flash chip contents... done. Looking for another erase function.
spi_chip_erase_c7 failed during command execution
Looking for another erase function.
No usable erase functions left.
FAILED!
Uh oh. Erase/write failed. Checking if anything has changed.
Reading current flash chip contents... until done.
Apparently at least some data has changed.
Your flash chip is in an unknown state.
- If the errors are an exact match, the flash was successful.
- If they don't match, DO NOT TURN OFF YOUR LAPTOP. Flash again.
- Power cycle the machine (i.e. a cold boot, not just a reboot). Your laptop will reboot into Coreboot.
- Note: SeaBIOS will not display anything without a proprietary VGABIOS blob. However, Linux should work fine after booting.
- Sources: Peter's mail - Mailing List Thread 1 - Mailing List Thread 2
Recover from Failed Flash with Bucts
- Note: If you forgot to set
bucts 1
, or forgot to patch the Coreboot ROM; your laptop has been bricked, and requires hardware flashing for recovery.
bucts sets a register that lives on the RTC well, ie. it is powered by the same source that keeps the clock alive. Usually that's a CMOS battery on the mainboard.
- Unscrew the keyboard (check Lenovo Hardware Maintenence Manual for more info).
- Remove the keyboard.
- Unplug the CMOS battery (it's a yellow circle).
- Wait a few seconds, and plug it back in.
- Reassemble the ThinkPad.
- Turn the ThinkPad back on.
- On the ThinkPad x60 series, bucts issues might also be solved by "discarging RTC", which is done by pressing the power button 5 times for 10 seconds.
Afterwards, the register should be reset and the system should boot into the vendor BIOS.
Install Coreboot (Second Flash)
Next, flash Coreboot a second time to overwrite the vendor BIOS.
- Run
su
to become root. - Enter the
flashrom
folder. - Run
./flashrom -p internal -w coreboot.rom
- This will successfully overwrite the entire flash chip with no errors, including the last 64k that were write protected with the factory BIOS.
- If it complains about 3 different flashchips (in the case of macronix chip), do this instead:
- Run
./flashrom -p internal -w coreboot.rom -c "MX25L1605D/MX25L1608D/MX25L1673E"
- Run
bucts 0
- Reboot the laptop. Coreboot has been successfully installed.
Recovery with a Hardware Firmware Flasher
If you had a bad flash you will need to use a hardware flasher to reflash the BIOS.
The BASLQC provides a more comprehensive guide to hardware BIOS flashing below, with research on a Raspberry Pi-based hardware flasher: (Not a Coreboot project)
The libreboot project also has picture guides showing disassembly and external flashing instructions (these 3 links are to the libreboot project. Contact libreboot, *not* coreboot, for support):
The libreboot guides linked above are based on the information below from the coreboot project:
Required/advised hardware and informations
- X60 Hardware Maintenance Manual or T60 Hardware Maintenance Manual for disassembling the laptop
- An SO-8 IC clip, like the Pomona 5250 for instance.
- An external flashrom programmer
Disassembling the ThinkPad
Follow the X60 Hardware Maintenance Manual or T60 Hardware Maintenance Manual to disassemble the laptop, until you can access the BIOS chip.
(photos needed)
- On the X60, the BIOS chip is on the bottom of the motherboard, under a layer of protective black tape.
- On the T60, the BIOS chip is just under the palmrest, but blocked by a magnesium frame (which you will have to remove).
Bus Pirate + SOIC Clip Configuration
Below is a diagram of how to plug the Bus Pirate into the SOIC Clip, with colors based on [dangerousprototypes.com/docs/Common_Bus_Pirate_cable_pinouts the Seeed Studio pinout.] Your cable colors may differ (such as the Sparkfun layout).
8765 ---- | | ---- 1234
- CS (white)
- MISO (black)
- not used
- GND (brown)
- MOSI (gray)
- CLK (purple)
- not used
- 3.3V (red) - Depends on chip
Make sure the pinouts are correct; otherwise, Bus Pirate will fail to detect a chip, or it will "detect" an 0x0
chip.
Finally, make sure that the Pomona clip makes contact with the metal wires of the chip. It can be a challenge, but keep trying.
How to supply power to the flashchip
There are two ways to supply power to the chip: plugging in an AC adapter (without turning it on), and using the 8th 3.3v pin.
I have found that the SST chips work best with the 8th pin, while the Macronix chips require an AC Adapter to power up.
Your results may vary.
Reading the Flashchip with Bus Pirate
- Visually inspect (with a magnifying glass) the type of flashchip on the motherboard.
- Clip the Pomona SOIC-8 Clip onto the flashchip. Make sure that the Bus Pirate is connected to it as shown above.
- download and extract the Libreboot binaries, and enter the
libreboot_bin/flashrom
folder.
cd libreboot_bincd flashrom
If it is an SST, run this command:
sudo ./flashrom_lenovobios_sst -p buspirate_spi:dev=/dev/ttyUSB0 -r test.rom
If it is a Macronix, run this command:
sudo ./flashrom_lenovobios_macronix -c "MX25L1605"; -p buspirate_spi:dev=/dev/ttyUSB0 -r test.rom
Next, check the md5sum of the dump:
md5sum test.rom
Run the flashrom
command again to make a second dump. Then, check the md5sum of the second dump:
md5sum test.rom
If the md5sums match after three tries, flashrom
has managed to read the flashchip precisely (but not always accurately). You may try and flash Libreboot now.
Flashing Libreboot with Bus Pirate
Note: replace
/path/to/libreboot.rom
with the location of your chosen ROM, such as../bin/x60/libreboot_usqwerty.rom
):
If your chip is SST, run this command:
sudo ./flashrom_lenovobios_sst -p buspirate_spi:dev=/dev/ttyUSB0 -w /path/to/libreboot.rom
If your chip is Macronix, run this command:
sudo ./flashrom_lenovobios_macronix -c "MX25L1605" -p buspirate_spi:dev=/dev/ttyUSB0 -w /path/to/libreboot.rom
Once that command outputs the following, the flash has completed successfully. If not, just flash again.
Reading old flash chip contents... done.Erasing and writing flash chip... Erase/write done.Verifying flash... VERIFIED.
Howto (old)
0. wire the pomona clip to a programmer that way:
From the #coreboot IRC Channel on FreeNode servers:
Oct 01 15:35:48 <CareBear\> one important thing is that when you connect the clip to the X60 you should not connect all pins [...] Oct 01 15:36:22 <CareBear\> only connect these pins: 1, 2, 4, 5, 6 [...] Oct 01 15:37:21 <CareBear\> also important: first connect charger to laptop, then connect the clip [...] Oct 01 17:49:41 <CareBear\> GNUtoo-desktop : the mainboard must be powered off, but with the charger connected [...] Oct 01 17:50:39 <CareBear\> um, that way there is no way anything will break [...] Oct 01 17:51:00 <CareBear\> it is important not to connect 3v3 from the outside Oct 01 17:51:39 <CareBear\> because the correct power sequencing is not known, and if any other rail must come on before the standby 3v3 then the machine may well break when 3v3 is applied from the outside [...] Oct 01 17:52:48 <CareBear\> it may also be fine - but it is unknown what happens [...] Oct 01 17:53:47 <CareBear\> not supplying 3v3 from the outside is safer Oct 01 17:54:25 <CareBear\> and because the machine is powered off, there is no risk of the chipset accessing the flash chip
In another hand I didn't follow that and wired it without powering the mainboard(mainboard disconnected from power plug, no battery in) and with all pins and it worked...
- Disassemble carefully the laptop, the SO-8 chip is on the bottom of the mainboard...
- connect the pomona clip to the BIOS chip
- flash coreboot or the BIOS
- remount the laptop
See also In-System Programming
Coreboot standard configuration
- It's now the default that when running SeaBios, that it (instead of coreboot) runs the VGA option rom.
See VGA_support for details on how to include the VGA BIOS image.
VBIOS replacement (native graphics)
The VGA option ROM (see above) is proprietary. Under devices in menuconfig, disable loading option ROM,s and enable 'Native graphics initialization'. Use the GRUB payload.
TODO: add notes here for how to patch coreboot for T60 native graphics (it's in libreboot already, or on 5345 on coreboot gerrit).
Recently tested revisions on the X60
See the most recent board-status submissions
970ad7076388b3ef98988121170df86196d493b4 coreboot-4.0-5534-g970ad70
8496c4dbec41b3a9284fc29b0dcd97fc8946223b coreboot-4.0-5045-g9bf05de
Recently tested revisions on the T60
See the most recent board-status submisssions
a172ea546992c3f6f6a99b4dbaabbdae4c959707 4.0-5611-ga172ea5
9bf05de5ab2842fc83cea8da5e9058417fc4bc24 4.0-5045-g9bf05de