Lenovo x60x - Revision history

Timisch: /* Flashing on the laptop instructions. */

2013-06-13T01:10:35Z

‎Flashing on the laptop instructions.

Timisch: /* Flashing on the laptop instructions. */

2013-06-13T01:08:54Z

‎Flashing on the laptop instructions.

Stuge: Remove laptop=force_I_want_a_brick option from flashrom commands

2013-06-02T20:28:31Z

Remove laptop=force_I_want_a_brick option from flashrom commands

GNUtoo: /* Last tested revision on the X60 */

2013-05-15T00:33:15Z

‎Last tested revision on the X60

Stefanct: correct link to "peter's mail"

2013-04-12T23:09:32Z

correct link to "peter's mail"

GNUtoo: /* Last tested revision on the X60 */

2013-03-18T10:26:20Z

‎Last tested revision on the X60

GNUtoo: /* Last tested revision */

2013-03-18T10:19:07Z

‎Last tested revision

GNUtoo: /* Coreboot configuration */

2013-02-23T11:00:15Z

‎Coreboot configuration

GNUtoo: /* Last tested revision */

2013-02-23T10:59:36Z

‎Last tested revision

GNUtoo: /* Coreboot configuration */

2013-02-23T10:41:28Z

‎Coreboot configuration

@@ Line 4: / Line 4: @@
 These Lenovo laptops have a register that must be flipped before coreboot can be flashed.
-For those/some models with SPI flash chips you have also to modify flashrom. Because the chipset locks down the available commands that flashrom can send to the flash chip, you also need to change the flashrom source in a way that is not suitable to upstream.  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 which is fine if there is only a small number of chips to distinguish, but won't work for the huge number of flash chips known to flashrom. The problem with the vendor BIOS is that it forbids the higher quality identification commands, so you need to force flashrom to use the lower quality opcode for the chip in your Thinkpad. You have to know the chip model beforehand (e.g. by inspection). Known models are SST25VF016B, MX25L1605D.
+For those/some models with SPI flash chips you have also to modify flashrom. Because the chipset locks down the available commands that flashrom can send to the flash chip, you also need to change the flashrom source in a way that is not suitable to upstream.  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 which is fine if there is only a small number of chips to distinguish, but won't work for the huge number of flash chips known to flashrom. The problem with the vendor BIOS is that it forbids the higher quality identification commands, so you need to force flashrom to use the lower quality opcode for the chip in your Thinkpad. You have to know the chip model beforehand (e.g. by inspection). Known models on the x60s are SST25VF016B, MX25L1605D and maybe others.
 You will need: the flashrom source, a small patch for it, and [http://git.stuge.se/?p=bucts.git the bucts utility].

@@ Line 4: / Line 4: @@
 These Lenovo laptops have a register that must be flipped before coreboot can be flashed.
-For those/some models with SPI flash chips you have also to modify flashrom. Because the chipset locks down the available commands that flashrom can send to the flash chip, you also need to change the flashrom source in a way that is not suitable to upstream.  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 which is fine if there is only a small number of chips to distinguish, but won't work for the huge number of flash chips known to flashrom. The problem with the vendor BIOS is that it forbids the higher quality identification commands, so you need to force flashrom to use the lower quality opcode for the chip in your Thinkpad. You have to know the chip model beforehand (e.g. by inspection).
+For those/some models with SPI flash chips you have also to modify flashrom. Because the chipset locks down the available commands that flashrom can send to the flash chip, you also need to change the flashrom source in a way that is not suitable to upstream.  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 which is fine if there is only a small number of chips to distinguish, but won't work for the huge number of flash chips known to flashrom. The problem with the vendor BIOS is that it forbids the higher quality identification commands, so you need to force flashrom to use the lower quality opcode for the chip in your Thinkpad. You have to know the chip model beforehand (e.g. by inspection). Known models are SST25VF016B, MX25L1605D.
 You will need: the flashrom source, a small patch for it, and [http://git.stuge.se/?p=bucts.git the bucts utility].

@@ Line 14: / Line 14: @@
 #* Change the .model_id field to the RES1 ID given in the datasheet of the flash chip
 #* Change the .write field to spi_chip_write_1
-# Run <code>flashrom -p internal:laptop=force_I_want_a_brick -r factory.bin</code>
+# Run <code>flashrom -p internal -r factory.bin</code>
 #: This step is IMPORTANT since the factory BIOS in your machine is tied to your particular system board (or "planar" in IBM FRU terms) with a unique ID not present in factory BIOS updates.
 # Run <code>dd if=coreboot.rom of=top64k.bin bs=1 skip=$[$(stat -c %s coreboot.rom) - 0x10000] count=64k</code>
@@ Line 25: / Line 25: @@
 # Run <code>dd if=top64k.bin of=coreboot.rom bs=1 seek=$[$(stat -c %s coreboot.rom) - 0x20000] count=64k conv=notrunc</code>
 # Run <code>bucts 1</code>
-# Run <code>flashrom -p internal:laptop=force_I_want_a_brick -w coreboot.rom</code>
+# Run <code>flashrom -p internal -w coreboot.rom</code>
 #: This will be slow, it will output errors for addresses 0x0 and 0x1f0000 when working with a 2 Mbyte flash chip, and it will say "FAILED!" at the end, see [http://www.flashrom.org/pipermail/flashrom/2012-April/009124.html Peter's mail] before you panic.
 # Power cycle the machine (i.e. a cold boot, not just a reboot), now starting with coreboot
-# Run <code>flashrom -p internal:laptop=force_I_want_a_brick -w coreboot.rom</code>.
+# Run <code>flashrom -p internal -w coreboot.rom</code>.
 #: This will successfully overwrite the entire flash chip, including the last 64k that were write protected with the factory BIOS.
 # Run <code>bucts 0</code>

@@ Line 92: / Line 92: @@
 == Last tested revision on the X60 ==
-  aa3f4287d40f7f3c7b1fca1af5cfa426ff4fa27f
+bd7b0cbadabb45f9131da03121a6ca284f24f35
 == Status ==
 * [[Thinkpad_X60s|Thinkpad X60s Status]]

@@ Line 26: / Line 26: @@
 # Run <code>bucts 1</code>
 # Run <code>flashrom -p internal:laptop=force_I_want_a_brick -w coreboot.rom</code>
-#: This will be slow, it will output errors for addresses 0x0 and 0x1f0000 when working with a 2 Mbyte flash chip, and it will say "FAILED!" at the end, see [http://www.flashrom.org/pipermail/flashrom/2012-April/009121.html Peter's mail] before you panic.
+#: This will be slow, it will output errors for addresses 0x0 and 0x1f0000 when working with a 2 Mbyte flash chip, and it will say "FAILED!" at the end, see [http://www.flashrom.org/pipermail/flashrom/2012-April/009124.html Peter's mail] before you panic.
 # Power cycle the machine (i.e. a cold boot, not just a reboot), now starting with coreboot
 # Run <code>flashrom -p internal:laptop=force_I_want_a_brick -w coreboot.rom</code>.

@@ Line 91: / Line 91: @@
   Oct 04 13:47:30 <patrickg>      older ~ 2.4 class ;)
-== Last tested revision ==
+== Last tested revision on the X60 ==
 d840323210433c96740545246296d65b3f2
 == Status ==
 * [[Thinkpad_X60s|Thinkpad X60s Status]]

@@ Line 76: / Line 76: @@
 # remount the laptop
-== Coreboot configuration ==
+== Coreboot standard configuration ==
 * It's advised to make SeaBios(instead of coreboot) run the VGA option rom by disabling CONFIG_VGA_ROM_RUN:
   [ ] Run VGA Option ROMs