From a62fe03d3e84150e6186f57f53029d5a9abe3d7b Mon Sep 17 00:00:00 2001 From: Alyssa Rosenzweig Date: Mon, 20 Mar 2017 20:26:48 -0700 Subject: undo breakages --- docs/install/bbb_setup.md | 93 ++++++++++---------- docs/install/c201.md | 87 ++++++++++--------- docs/install/d510mo.md | 20 +++-- docs/install/d945gclf.md | 13 ++- docs/install/ga-g41m-es2l.md | 26 +++--- docs/install/index.md | 105 ++++++++++++++--------- docs/install/kcma-d8.md | 10 ++- docs/install/kgpe-d16.md | 12 ++- docs/install/r400_external.md | 167 +++++++++++++++++------------------- docs/install/rpi_setup.md | 30 ++++--- docs/install/t400_external.md | 155 +++++++++++++++++----------------- docs/install/t500_external.md | 170 ++++++++++++++++++------------------- docs/install/t60_unbrick.md | 152 +++++++++++++-------------------- docs/install/x200_external.md | 125 +++++++++++++-------------- docs/install/x60_unbrick.md | 173 +++++++++++++++----------------------- docs/install/x60tablet_unbrick.md | 86 +++++++++---------- 16 files changed, 696 insertions(+), 728 deletions(-) (limited to 'docs/install') diff --git a/docs/install/bbb_setup.md b/docs/install/bbb_setup.md index 56608d04..03882956 100644 --- a/docs/install/bbb_setup.md +++ b/docs/install/bbb_setup.md @@ -1,4 +1,6 @@ -% How to program an SPI flash chip with the BeagleBone Black or Teensy 3.1 + +How to program an SPI flash chip with the BeagleBone Black or Teensy 3.1 +======================================================================== This document exists as a guide for reading from or writing to an SPI flash chip with the BeagleBone Black, using the @@ -26,10 +28,12 @@ flashing on the ThinkPad X200, but it should work for other targets. here is a photo of the setup for the teensy: -Onto the Beaglebone black... +Onto the Beaglebone black\... [Back to previous index](./) + + Hardware requirements ===================== @@ -100,6 +104,8 @@ Shopping list (pictures of this hardware is shown later): [Back to top of page.](#pagetop) + + Setting up the 3.3V DC PSU ========================== @@ -108,21 +114,21 @@ page](https://en.wikipedia.org/wiki/Power_supply_unit_%28computer%29#Wiring_diag You can use pin 1 or 2 (orange wire) on a 20-pin or 24-pin ATX PSU for 3.3V, and any of the ground/earth sources (black cables) for ground. -Short PS\_ON# / Power on (green wire; pin 16 on 24-pin ATX PSU, or pin +Short PS\_ON\# / Power on (green wire; pin 16 on 24-pin ATX PSU, or pin 14 on a 20-pin ATX PSU) to a ground (black; there is one right next to it) using a wire/paperclip/jumper, then power on the PSU by grounding -PS\_ON# (this is also how an ATX motherboard turns on a PSU). +PS\_ON\# (this is also how an ATX motherboard turns on a PSU). -**DO **NOT** use pin 4, 6, do **NOT** use pin 19 or 20 (on a -20-pin ATX PSU), and DO **NOT** use pin 21, 22 or 23 (on a 24-pin -ATX PSU). Those wires (the red ones) are 5V, and they **WILL** kill -your flash chip. ***NEVER*** supply more than 3.3V to your flash +**DO \*\*NOT\*\* use pin 4, 6, do \*\*NOT\*\* use pin 19 or 20 (on a +20-pin ATX PSU), and DO \*\*NOT\*\* use pin 21, 22 or 23 (on a 24-pin +ATX PSU). Those wires (the red ones) are 5V, and they \*\*WILL\*\* kill +your flash chip. \*\*\*NEVER\*\*\* supply more than 3.3V to your flash chip (that is, if it's a 3.3V flash chip; 5V and 1.8V SPI flash chips do exist, but they are rare. Always check what voltage your chip takes. Most of them take 3.3V).** You only need one 3.3V supply and one ground for the flash chip, after -grounding PS\_ON#. +grounding PS\_ON\#. The male end of a 0.1" or 2.54mm header cable is not thick enough to remain permanently connected to the ATX PSU on its own. When connecting @@ -131,10 +137,11 @@ to a thicker piece of wire (you could use a paper clip), or wedge the male end of the jumper cable into the sides of the hole in the connector, instead of going through the centre. -Here is an example set up: - +Here is an example set up:\ ![](images/x200/psu33.jpg "Copyright © 2015 Patrick "P. J." McDermott see license notice at the end of this document") + + Accessing the operating system on the BBB ========================================= @@ -150,27 +157,26 @@ Alternatives to SSH (in case SSH fails) --------------------------------------- You can also use a serial FTDI debug board with GNU Screen, to access -the serial console. - - # screen /dev/ttyUSB0 115200 -Here are some example photos: - -![](images/x200/ftdi.jpg) ![](images/x200/ftdi_port.jpg) +the serial console.\ +\# **screen /dev/ttyUSB0 115200**\ +Here are some example photos:\ +![](images/x200/ftdi.jpg) ![](images/x200/ftdi_port.jpg)\ You can also connect the USB cable from the BBB to another computer and a new network interface will appear, with its own IP address. This is -directly accessible from SSH, or screen: - -# **screen /dev/ttyACM0 115200** +directly accessible from SSH, or screen:\ +\# **screen /dev/ttyACM0 115200** You can also access the uboot console, using the serial method instead of SSH. + + Setting up spidev on the BBB ============================ Log on as root on the BBB, using either SSH or a serial console as -defined in [#bbb\_access](#bbb_access). Make sure that you have +defined in [\#bbb\_access](#bbb_access). Make sure that you have internet access on your BBB. Follow the instructions at @@ -197,24 +203,22 @@ contents of this file with: # Description: Starts LED aging (whatever that is) ### END INIT INFO - x=\$(/bin/ps -ef | /bin/grep "[l]ed_acc") - if [ ! -n "\$x" -a -x /usr/bin/led_acc ]; then + x=$(/bin/ps -ef | /bin/grep "[l]ed_acc") + if [ ! -n "$x" -a -x /usr/bin/led_acc ]; then /usr/bin/led_acc & fi Run **apt-get update** and **apt-get upgrade** then reboot the BBB, before continuing. -Check that the firmware exists: - - # ls /lib/firmware/BB-SPI0-01-00A0.* +Check that the firmware exists:\ +\# **ls /lib/firmware/BB-SPI0-01-00A0.\***\ Output: /lib/firmware/BB-SPI0-01-00A0.dtbo -Then: - - # echo BB-SPI0-01 > /sys/devices/bone\_capemgr.*/slots - # cat /sys/devices/bone\_capemgr.*/slots +Then:\ +\# **echo BB-SPI0-01 > /sys/devices/bone\_capemgr.\*/slots**\ +\# **cat /sys/devices/bone\_capemgr.\*/slots**\ Output: 0: 54:PF--- @@ -225,16 +229,14 @@ Output: 5: ff:P-O-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI 7: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-SPI0-01 -Verify that the spidev device now exists: - - # ls -al /dev/spid* +Verify that the spidev device now exists:\ +\# **ls -al /dev/spid\***\ Output: crw-rw---T 1 root spi 153, 0 Nov 19 21:07 /dev/spidev1.0 Now the BBB is ready to be used for flashing. Make this persist across -reboots: - +reboots:\ In /etc/default/capemgr add **CAPE=BB-SPI0-01** at the end (or change the existing **CAPE=** entry to say that, if an entry already exists. @@ -250,9 +252,8 @@ libreboot\_src, and put the ARM binary for it on your BBB. Finally, get the ROM image that you would like to flash and put that on your BBB. -Now test flashrom: - - # ./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 +Now test flashrom:\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512**\ Output: Calibrating delay loop... OK. @@ -262,6 +263,8 @@ Output: This means that it's working (the clip isn't connected to any flash chip, so the error is fine). + + Connecting the Pomona 5250/5252 =============================== @@ -330,12 +333,13 @@ should.** if you need to extend the 3.3v psu leads, just use the same colour M-F leads, **but** keep all other leads short (10cm or less) -You should now have something that looks like this: - +You should now have something that looks like this:\ ![](images/x200/5252_bbb0.jpg) ![](images/x200/5252_bbb1.jpg) [Back to top of page.](#pagetop) + + Notes about stability {#stability} ===================== @@ -344,7 +348,7 @@ not always. That page has some notes about using resistors to affect stability. Currently, we use spispeed=512 (512kHz) but it is possible to use higher speeds while maintaining stability. -tty0\_ in #libreboot was able to get better flashing speeds with the +tty0\_ in \#libreboot was able to get better flashing speeds with the following configuration: - "coax" with 0.1 mm core and aluminum foley (from my kitchen), add @@ -354,12 +358,11 @@ following configuration: - See this image: - He was able to flash at 50MHz (lower speeds are also fine). -Copyright © 2014, 2015 Leah Rowe - -Copyright © 2015 Patrick "P. J." McDermott -Copyright © 2015 Albin Söderqvist +Copyright © 2014, 2015 Leah Rowe \ +Copyright © 2015 Patrick "P. J." McDermott \ +Copyright © 2015 Albin Söderqvist\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/install/c201.md b/docs/install/c201.md index b481a6ec..d04ba2b0 100644 --- a/docs/install/c201.md +++ b/docs/install/c201.md @@ -1,12 +1,16 @@ -% ASUS Chromebook C201 installation guide + +ASUS Chromebook C201 installation guide +======================================= These instructions are for installing Libreboot to the ASUS Chromebook C201. Since the device ships with Coreboot, the installation instructions are the same before and after flashing Libreboot for the first time. + **If you are using libreboot\_src or git, then make sure that you built -the sources first (see [../git/#build](../git/#build)).** +the sources first (see [../git/\#build](../git/#build)).** + Look at the [list of ROM images](#rom) to see which image is compatible with your device. @@ -19,14 +23,12 @@ flashrom version. **Google's modified version of flashrom** is free software and its source code is made available by Google: -[flashrom](https://chromium.googlesource.com/chromiumos/third_party/flashrom/). - +[flashrom](https://chromium.googlesource.com/chromiumos/third_party/flashrom/).\ It is not distributed along with Libreboot yet. However, it is preinstalled on the device, with ChromeOS. Installing Libreboot internally requires sufficient privileges on the -system installed on the device. - +system installed on the device.\ When the device has ChromeOS installed (as it does initially), it is necessary to gain root privileges in ChromeOS, to be able to access a root shell. @@ -45,11 +47,15 @@ root shell. - [Debian GNU+Linux is recommended for this device](#debian) (TODO: instructions for Devuan) + + + Gaining root privileges on ChromeOS In order to gain root privileges on ChromeOS, developer mode has to be enabled from the recovery mode screen and debugging features have to be enabled in ChromeOS. + Instructions to access the [recovery mode screen](../depthcharge/#recovery_mode_screen) and [enabling developer mode](../depthcharge/#enabling_developer_mode) are available on the page @@ -62,8 +68,7 @@ or by pressing **Ctrl + D** After the system has booted, root access can be enabled by clicking on the **Enable debugging features** link. A confirmation dialog will ask -whether to proceed. - +whether to proceed.\ After confirming by clicking **Proceed**, the device will reboot and ask for the root password to set. Finally, the operation has to be confirmed by clicking **Enable**. @@ -72,11 +77,15 @@ After setting the root password, it becomes possible to log-in as root. A tty prompt can be obtained by pressing **Ctrl + Alt + Next**. The **Next** key is the one on the top left of the keyboard. + + + Preparing the device for the installation Before installing Libreboot on the device, both its software and hardware has to be prepared to allow the installation procedure and to ensure that security features don't get in the way. + Configuring verified boot parameters {#configuring_verified_boot_parameters} ------------------------------------ @@ -91,6 +100,8 @@ parameters](../depthcharge/#configuring_verified_boot_parameters): Those changes can be reverted later, when the device is known to be in a working state. + + Removing the write protect screw {#removing_write_protect_screw} -------------------------------- @@ -113,6 +124,9 @@ screw](images/c201/wp-screw.jpg)](images/c201/wp-screw.jpg) The write protect screw can be put back in place later, when the device is known to be in a working state. + + + Installing Libreboot to the SPI flash {#installing_libreboot_spi_flash} ===================================== @@ -121,6 +135,7 @@ that are used to implement parts of the CrOS security system. Libreboot is installed in the *read-only* coreboot partition, that becomes writable after removing the write-protect screw. + Installing Libreboot internally, from the device {#installing_libreboot_internally} ------------------------------------------------ @@ -132,31 +147,28 @@ transferred to the device. The following operations have to be executed with root privileges on the device (e.g. using the *root* account). In addition, the -**cros-flash-replace** script has to be made executable: +**cros-flash-replace** script has to be made executable:\ +\# **chmod a+x cros-flash-replace**\ - # chmod a+x cros-flash-replace - -The SPI flash has to be read first: - - # flashrom -p host -r flash.img +The SPI flash has to be read first:\ +\# **flashrom -p host -r flash.img**\ **Note: it might be a good idea to copy the produced flash.img file at this point and store it outside of the device for backup purposes.** -Then, the **cros-flash-replace** script has to be executed as such: - - # ./cros-flash-replace flash.img coreboot ro-frid +Then, the **cros-flash-replace** script has to be executed as such:\ +\# **./cros-flash-replace flash.img coreboot ro-frid**\ If any error is shown, it is definitely a bad idea to go further than this point. -The resulting flash image can then be flashed back: +The resulting flash image can then be flashed back:\ +\# **flashrom -p host -w flash.img**\ - # flashrom -p host -w flash.img +You should also see within the output the following:\ +**"Verifying flash\... VERIFIED."** -You should also see within the output the following: +Shut down. The device will now boot to Libreboot. -**"Verifying flash... VERIFIED."** -Shut down. The device will now boot to Libreboot. Installing Libreboot externally, with a SPI flash programmer {#installing_libreboot_externally} ------------------------------------------------------------ @@ -166,7 +178,7 @@ to be opened. The SPI flash is located next to the write protect screw. Its layout is indicated in the picture below. Note that it is not necessary to connect -**WP#** since removing the screw already connects it to ground. Before +**WP\#** since removing the screw already connects it to ground. Before writing to the chip externally, the battery connector has to be detached. It is located under the heat spreader, that has to be unscrewed from the rest of the case. The battery connector is located on @@ -182,33 +194,29 @@ transferred to the host. The following operations have to be executed with root privileges on the host (e.g. using the *root* account). In addition, the -**cros-flash-replace** script has to be made executable: - - # chmod a+x cros-flash-replace +**cros-flash-replace** script has to be made executable:\ +\# **chmod a+x cros-flash-replace**\ -The SPI flash has to be read first (using the right spi programmer): - - # flashrom -p *programmer* -r flash.img +The SPI flash has to be read first (using the right spi programmer):\ +\# **flashrom -p *programmer* -r flash.img**\ **Note: it might be a good idea to copy the produced flash.img file at this point and store it outside of the device for backup purposes.** -Then, the **cros-flash-replace** script has to be executed as such: - - # ./cros-flash-replace flash.img coreboot ro-frid +Then, the **cros-flash-replace** script has to be executed as such:\ +\# **./cros-flash-replace flash.img coreboot ro-frid**\ If any error is shown, it is definitely a bad idea to go further than this point. The resulting flash image can then be flashed back (using the right spi -programmer): +programmer):\ +\# **flashrom -p *programmer* -w flash.img**\ - # flashrom -p *programmer* -w flash.img - -You should also see within the output the following: - -**"Verifying flash... VERIFIED."** +You should also see within the output the following:\ +**"Verifying flash\... VERIFIED."** The device will now boot to Libreboot. + Debian GNU+Linux {#debian} ---------------- @@ -221,8 +229,9 @@ See . [Back to top of page.](#pagetop) -Copyright © 2015 Paul Kocialkowski + +Copyright © 2015 Paul Kocialkowski \ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/install/d510mo.md b/docs/install/d510mo.md index bf8700f3..056b90cf 100644 --- a/docs/install/d510mo.md +++ b/docs/install/d510mo.md @@ -1,29 +1,35 @@ -% D510MO flashing tutorial + +D510MO flashing tutorial +======================== This guide is for those who want libreboot on their Intel D510MO motherboard while they still have the original BIOS present. + + + Flash chip size {#flashchips} =============== -Use this to find out: - -# **flashrom -p internal -V** +Use this to find out:\ +\# **flashrom -p internal -V** [Back to top of page.](#pagetop) + + Flashing instructions {#clip} ===================== Refer to [bbb\_setup.html](bbb_setup.html) for how to set up the BBB for flashing. -This is an image of the flash chip, for reference: - +This is an image of the flash chip, for reference:\ ![](../images/d510mo/d510mo.jpg) -Copyright © 2016 Leah Rowe + +Copyright © 2016 Leah Rowe \ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/install/d945gclf.md b/docs/install/d945gclf.md index 4dabbd41..95178304 100644 --- a/docs/install/d945gclf.md +++ b/docs/install/d945gclf.md @@ -1,4 +1,6 @@ -% Intel D945GCLF flashing tutorial + +Intel D945GCLF flashing tutorial +================================ This guide is for those who want libreboot on their Intel D945GCLF motherboard while they still have the original BIOS present. @@ -6,18 +8,21 @@ motherboard while they still have the original BIOS present. For information about this board, go to [../hcl/d945gclf.html](../hcl/d945gclf.html) + + + Flashing instructions {#clip} ===================== Refer to [bbb\_setup.html](bbb_setup.html) for how to set up the BBB for external flashing. -Here is an image of the flash chip: - +Here is an image of the flash chip:\ ![](../images/d945gclf/d945gclf_spi.jpg) -Copyright © 2016 Leah Rowe + +Copyright © 2016 Leah Rowe \ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/install/ga-g41m-es2l.md b/docs/install/ga-g41m-es2l.md index cd4c129c..ef7bb97e 100644 --- a/docs/install/ga-g41m-es2l.md +++ b/docs/install/ga-g41m-es2l.md @@ -1,17 +1,23 @@ -% GA-G41M-ES2L flashing tutorial + +GA-G41M-ES2L flashing tutorial +============================== This guide is for those who want libreboot on their Intel GA-G41M-ES2L motherboard while they still have the original BIOS present. + + + Flash chip size {#flashchips} =============== -Use this to find out: - -# **flashrom -p internal -V** +Use this to find out:\ +\# **flashrom -p internal -V** [Back to top of page.](#pagetop) + + Flashing instructions {#clip} ===================== @@ -22,19 +28,16 @@ by connecting 3v3 to /CS of that chip, so you will actually need 2 test clips (you also need to connect GND on the chip that you're disabling).** -Here is an image of the flash chip: - +Here is an image of the flash chip:\ ![](../images/ga-g41m-es2l/ga-g41m-es2l.jpg) Internal flashing is possible. Boot with the proprietary BIOS and GNU+Linux. There are 2 flash chips (one is backup). -Flash the first chip: - +Flash the first chip:\ **./flashrom -p internal:dualbiosindex=0 -w libreboot.rom** -Flash the second chip: - +Flash the second chip:\ **./flashrom -p internal:dualbiosindex=1 -w libreboot.rom** NOTE: you can still boot the system with just the main flash chip @@ -48,8 +51,9 @@ NOTE: due to a bug in the hardware, the MAC address is hardcoded in coreboot-libre. Therefore, you must set your own MAC address in your operating system. -Copyright © 2016 Leah Rowe + +Copyright © 2016 Leah Rowe \ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/install/index.md b/docs/install/index.md index 947fbe8b..0e8b7ea9 100644 --- a/docs/install/index.md +++ b/docs/install/index.md @@ -1,4 +1,6 @@ -% Installing libreboot + +Installing libreboot +==================== This section relates to installing libreboot on supported targets. @@ -9,6 +11,8 @@ that has CONFIG\_STRICT\_DEVMEM not enabled. [Back to previous index](../) + + General information ------------------- @@ -48,6 +52,8 @@ Flashing via hardware methods, on system: - [ThinkPad T400](t400_external.html) - [ThinkPad T500](t500_external.html) + + Information about libreboot ROM images {#rom} ====================================== @@ -71,7 +77,7 @@ as the keymap in GNU+Linux is concerned. Keymaps are named appropriately according to each keyboard layout support in GRUB. To learn how these keymaps are created, see -[../grub/#grub\_keyboard](../grub/#grub_keyboard) +[../grub/\#grub\_keyboard](../grub/#grub_keyboard) QEMU ---- @@ -94,6 +100,8 @@ information. [Back to top of page.](#pagetop) + + How to update or install libreboot (if you are already running libreboot or coreboot) {#flashrom} ===================================================================================== @@ -103,8 +111,10 @@ any dedicated hardware. In other words, you can do everything entirely in software, directly from the OS that is running on your libreboot system. + **If you are using libreboot\_src or git, then make sure that you built -the sources first (see [../git/#build](../git/#build)).** +the sources first (see [../git/\#build](../git/#build)).** + Look at the [list of ROM images](#rom) to see which image is compatible with your device. @@ -117,8 +127,8 @@ coreboot), then the flashing instructions for your system are going to be different. X60/T60 users running the proprietary firmware should refer to -[#flashrom\_lenovobios](#flashrom_lenovobios). MacBook2,1 users running -Apple EFI should refer to [#flashrom\_macbook21](#flashrom_macbook21) +[\#flashrom\_lenovobios](#flashrom_lenovobios). MacBook2,1 users running +Apple EFI should refer to [\#flashrom\_macbook21](#flashrom_macbook21) X200 users, refer to [x200\_external.html](x200_external.html), R400 users refer to [r400\_external.html](r400_external.html), T400 users @@ -221,7 +231,7 @@ onboard ethernet chipset is located inside the flash chip. Libreboot ROM images for these laptops contain a generic MAC address by default, but this is not what you want. *Make sure to change the MAC address inside the ROM image, before flashing it. The instructions on -[../hcl/gm45\_remove\_me.html#ich9gen](../hcl/gm45_remove_me.html#ich9gen) +[../hcl/gm45\_remove\_me.html\#ich9gen](../hcl/gm45_remove_me.html#ich9gen) show how to do this.* It is important that you change the default MAC address, before @@ -243,14 +253,13 @@ ROM image, and it should work.** Flash chip size --------------- -Use this to find out: - -# **flashrom -p internal -V** +Use this to find out:\ +\# **flashrom -p internal -V** All good? --------- -Excellent! Moving on... +Excellent! Moving on\... Download the *libreboot\_util.tar.xz* archive, and extract it. Inside, you will find a directory called *flashrom*. This contains statically @@ -263,56 +272,66 @@ what CPU architecture you have (e.g. i686, x86\_64) and use the appropriate executable. It is also possible for you to build these executables from the libreboot source code archives. -How to update the flash chip contents: +How to update the flash chip contents:\ \$ **sudo ./flash update [yourrom.rom](#rom)** + + Ocassionally, coreboot changes the name of a given board. If flashrom complains about a board mismatch, but you are sure that you chose the -correct ROM image, then run this alternative command: - +correct ROM image, then run this alternative command:\ \$ **sudo ./flash forceupdate [yourrom.rom](#rom)** -You should see **"Verifying flash... VERIFIED."** written at the end + + +You should see **"Verifying flash\... VERIFIED."** written at the end of the flashrom output. **Shut down** after you see this, and then boot up again after a few seconds. + +[Back to top of page](#pagetop) + + + ThinkPad X60/T60: Initial installation guide (if running the proprietary firmware) {#flashrom_lenovobios} ================================================================================== **This is for the ThinkPad X60 and T60 while running Lenovo BIOS. If you already have coreboot or libreboot running, then go to -[#flashrom](#flashrom) instead!** +[\#flashrom](#flashrom) instead!** **If you are flashing a Lenovo ThinkPad T60, be sure to read -[../hcl/#supported\_t60\_list](../hcl/#supported_t60_list)** +[../hcl/\#supported\_t60\_list](../hcl/#supported_t60_list)** + **If you are using libreboot\_src or git, then make sure that you built -the sources first (see [../git/#build](../git/#build)).** +the sources first (see [../git/\#build](../git/#build)).** + **Warning: this guide will not instruct the user how to backup the original Lenovo BIOS firmware. These backups are tied to each system, and will not work on any other. For that, please refer to .** + **If you're using libreboot 20150518, note that there is a mistake in the flashing script. do this: *rm -f patch && wget -O flash https://notabug.org/vimuser/libreboot/raw/9d850543ad90b72e0e333c98075530b31e5d23f1/flash && chmod +x flash*** -The first half of the procedure is as follows: - +The first half of the procedure is as follows:\ \$ **sudo ./flash i945lenovo\_firstflash [yourrom.rom](#rom).** -You should see within the output the following: + +You should see within the output the following:\ **"Updated BUC.TS=1 - 64kb address ranges at 0xFFFE0000 and 0xFFFF0000 are swapped"**. -You should also see within the output the following: - +You should also see within the output the following:\ **"Your flash chip is in an unknown state"**, **"FAILED"** and - "DO NOT REBOOT OR POWEROFF" +**"DO NOT REBOOT OR POWEROFF"**\ Seeing this means that the operation was a **resounding** success! **DON'T PANIC**. @@ -321,65 +340,75 @@ See this link for more details: If the above is what you see, then **SHUT DOWN**. Wait a few seconds, and then boot; libreboot is running, but there is a 2nd procedure -***needed*** (see below). +**\*needed\*** (see below). -When you have booted up again, you must also do this: -\$ **sudo ./flash i945lenovo\_secondflash [yourrom.rom](#rom)** -If flashing fails at this stage, try the following: +When you have booted up again, you must also do this:\ +\$ **sudo ./flash i945lenovo\_secondflash [yourrom.rom](#rom)** +If flashing fails at this stage, try the following:\ \$ **sudo ./flashrom/i686/flashrom -p internal:laptop=force\_I\_want\_a\_brick -w [yourrom.rom](#rom)** -You should see within the output the following: + +You should see within the output the following:\ **"Updated BUC.TS=0 - 128kb address range 0xFFFE0000-0xFFFFFFFF is untranslated"** -You should also see within the output the following: +You should also see within the output the following:\ +**"Verifying flash\... VERIFIED."** -**"Verifying flash... VERIFIED."** [Back to top of page.](#pagetop) + + MacBook2,1: Initial installation guide (if running the proprietary firmware) {#flashrom_macbook21} ============================================================================ + **If you have a MacBook1,1, refer to -[../hcl/#macbook11](../hcl/#macbook11) for flashing instructions.** +[../hcl/\#macbook11](../hcl/#macbook11) for flashing instructions.** + **This is for the MacBook2,1 while running Apple EFI firmware. If you already have coreboot or libreboot running, then go to -[#flashrom](#flashrom) instead!** +[\#flashrom](#flashrom) instead!** Be sure to read the information in -[../hcl/#macbook21](../hcl/#macbook21). +[../hcl/\#macbook21](../hcl/#macbook21). **Warning: this guide will not instruct the user how to backup the original Apple EFI firmware. For that, please refer to .** + **If you are using libreboot\_src or git, then make sure that you built -the sources first (see [../git/#build](../git/#build)).** +the sources first (see [../git/\#build](../git/#build)).** + Look at the [list of ROM images](#rom) to see which image is compatible with your device. -Use this flashing script, to install libreboot: +Use this flashing script, to install libreboot:\ \$ **sudo ./flash i945apple\_firstflash [yourrom.rom](#rom)** -You should also see within the output the following: -**"Verifying flash... VERIFIED."** + +You should also see within the output the following:\ +**"Verifying flash\... VERIFIED."** Shut down. + [Back to top of page.](#pagetop) -Copyright © 2014, 2015, 2016 Leah Rowe + +Copyright © 2014, 2015, 2016 Leah Rowe \ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/install/kcma-d8.md b/docs/install/kcma-d8.md index 161c824d..5f5c7f96 100644 --- a/docs/install/kcma-d8.md +++ b/docs/install/kcma-d8.md @@ -1,4 +1,6 @@ -% KCMA-D8 external flashing instructions + +KCMA-D8 external flashing instructions +====================================== Initial flashing instructions for kcma-d8. @@ -19,6 +21,9 @@ TODO: show photos here, and other info. preinstalled](#preinstall) - [External programmer](#programmer) + + + External programmer {#programmer} =================== @@ -30,8 +35,9 @@ motherboard, which you take out and then re-flash with libreboot, using the programmer. **DO NOT** remove the chip with your hands. Use a chip extractor tool. -Copyright © 2016 Leah Rowe + +Copyright © 2016 Leah Rowe \ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/install/kgpe-d16.md b/docs/install/kgpe-d16.md index fa28da9f..3110c804 100644 --- a/docs/install/kgpe-d16.md +++ b/docs/install/kgpe-d16.md @@ -1,4 +1,6 @@ -% KGPE-D16 external flashing instructions + +KGPE-D16 external flashing instructions +======================================= Initial flashing instructions for KGPE-D16. @@ -19,6 +21,9 @@ TODO: show photos here, and other info. preinstalled](#preinstall) - [External programmer](#programmer) + + + KGPE-D16 boards (and full systems) with libreboot preinstalled {#preinstall} ============================================================== @@ -28,6 +33,8 @@ GNU+Linux distribution. Check the [suppliers](../../suppliers) page for more information. + + External programmer {#programmer} =================== @@ -39,8 +46,9 @@ motherboard, which you take out and then re-flash with libreboot, using the programmer. **DO NOT** remove the chip with your hands. Use a chip extractor tool. -Copyright © 2015 Leah Rowe + +Copyright © 2015 Leah Rowe \ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/install/r400_external.md b/docs/install/r400_external.md index c6581615..1c8e9c83 100644 --- a/docs/install/r400_external.md +++ b/docs/install/r400_external.md @@ -1,4 +1,6 @@ -% Flashing the R400 with a BeagleBone Black + +Flashing the R400 with a BeagleBone Black +========================================= Initial flashing instructions for R400. @@ -11,12 +13,17 @@ ROM properly first. Although ROM images are provided pre-built in libreboot, there are some modifications that you need to make to the one you chose before flashing. (instructions referenced later in this guide) + + + Libreboot T400 {#t400} ============== You may also be interested in the smaller, more portable [Libreboot T400](t400_external.html). + + Serial port {#serial_port} ----------- @@ -24,6 +31,8 @@ EHCI debug might not be needed. It has been reported that the docking station for this laptop has a serial port, so it might be possible to use that instead. + + A note about CPUs ================= @@ -38,6 +47,8 @@ Quad-core CPUs Incompatible. Do not use. + + A note about GPUs ================= @@ -54,17 +65,20 @@ initialization works all the same. CPU paste required ================== -See [#paste](#paste). +See [\#paste](#paste). + + Flash chip size {#flashchips} =============== -Use this to find out: - - # flashrom -p internal -V +Use this to find out:\ +\# **flashrom -p internal -V**\ [Back to top of page.](#pagetop) + + MAC address {#macaddress} =========== @@ -78,6 +92,8 @@ image before flashing it. It will be written in one of these locations: ![](images/t400/macaddress0.jpg) ![](images/t400/macaddress1.jpg) ![](images/x200/disassembly/0001.jpg) + + Initial BBB configuration ========================= @@ -115,95 +131,73 @@ for SOIC-8 (clip: Pomona 5250): Disassembly ----------- -Remove all screws: - -![](images/r400/0000.jpg) - -Remove the HDD and optical drive: - -![](images/r400/0001.jpg) - -Remove the hinge screws: - +Remove all screws:\ +![](images/r400/0000.jpg)\ +Remove the HDD and optical drive:\ +![](images/r400/0001.jpg)\ +Remove the hinge screws:\ ![](images/r400/0002.jpg) ![](images/r400/0003.jpg) -Remove the palm rest and keyboard: - +Remove the palm rest and keyboard:\ ![](images/r400/0004.jpg) ![](images/r400/0005.jpg) -Remove these screws, and then remove the bezel: - +Remove these screws, and then remove the bezel:\ ![](images/r400/0006.jpg) ![](images/r400/0007.jpg) Remove the speaker screws, but don't remove the speakers yet (just set -them loose): - +them loose):\ ![](images/r400/0008.jpg) ![](images/r400/0009.jpg) ![](images/r400/0010.jpg) -Remove these screws, and then remove the metal plate: - +Remove these screws, and then remove the metal plate:\ ![](images/r400/0011.jpg) ![](images/r400/0012.jpg) ![](images/r400/0013.jpg) -Remove the antennas from the wifi card, and then start unrouting them: - +Remove the antennas from the wifi card, and then start unrouting them:\ ![](images/r400/0014.jpg) ![](images/r400/0015.jpg) ![](images/r400/0016.jpg) ![](images/r400/0017.jpg) ![](images/r400/0018.jpg) ![](images/r400/0019.jpg) -Disconnect the LCD cable from the motherboard: - +Disconnect the LCD cable from the motherboard:\ ![](images/r400/0020.jpg) ![](images/r400/0021.jpg) ![](images/r400/0022.jpg) ![](images/r400/0023.jpg) -Remove the hinge screws, and then remove the LCD panel: - +Remove the hinge screws, and then remove the LCD panel:\ ![](images/r400/0024.jpg) ![](images/r400/0025.jpg) ![](images/r400/0026.jpg) ![](images/r400/0027.jpg) -Remove this: - +Remove this:\ ![](images/r400/0028.jpg) ![](images/r400/0029.jpg) -Remove this long cable (there are 3 connections): - +Remove this long cable (there are 3 connections):\ ![](images/r400/0030.jpg) ![](images/r400/0031.jpg) ![](images/r400/0032.jpg) ![](images/r400/0033.jpg) -Disconnect the speaker cable, and remove the speakers: - +Disconnect the speaker cable, and remove the speakers:\ ![](images/r400/0034.jpg) Remove the heatsink screws, remove the fan and then remove the -heatsink/fan: - +heatsink/fan:\ ![](images/r400/0035.jpg) ![](images/r400/0036.jpg) ![](images/r400/0037.jpg) ![](images/r400/0038.jpg) -Remove the NVRAM battery: - +Remove the NVRAM battery:\ ![](images/r400/0039.jpg) ![](images/r400/0040.jpg) -Remove this screw: - +Remove this screw:\ ![](images/r400/0041.jpg) ![](images/r400/0042.jpg) -Disconnect the AC jack: - +Disconnect the AC jack:\ ![](images/r400/0043.jpg) ![](images/r400/0044.jpg) -Remove this screw and then remove what is under it: - +Remove this screw and then remove what is under it:\ ![](images/r400/0045.jpg) -Remove this: - +Remove this:\ ![](images/r400/0046.jpg) Lift the motherboard (which is still inside the cage) from the side on -the right, removing it completely: - +the right, removing it completely:\ ![](images/r400/0047.jpg) ![](images/r400/0048.jpg) Remove all screws, marking each hole so that you know where to re-insert @@ -212,23 +206,19 @@ that they were in before removal: ![](images/r400/0049.jpg) ![](images/r400/0050.jpg) Remove the motherboard from the cage, and the SPI flash chip will be -next to the memory slots: - +next to the memory slots:\ ![](images/r400/0051.jpg) ![](images/r400/0052.jpg) -Connect your programmer, then connect GND and 3.3V - +Connect your programmer, then connect GND and 3.3V\ ![](images/t400/0065.jpg) ![](images/t400/0066.jpg) ![](images/t400/0067.jpg) ![](images/t400/0069.jpg) ![](images/t400/0070.jpg) ![](images/t400/0071.jpg) A dedicated 3.3V PSU was used to create this guide, but at ATX PSU is -also fine: - +also fine:\ ![](images/t400/0072.jpg) -Of course, make sure to turn on your PSU: - +Of course, make sure to turn on your PSU:\ ![](images/x200/disassembly/0013.jpg) Now, you should be ready to install libreboot. @@ -238,11 +228,10 @@ libreboot\_util. Alternatively, libreboot also distributes flashrom source code which can be built. Log in as root on your BBB, using the instructions in -[bbb\_setup.html#bbb\_access](bbb_setup.html#bbb_access). - -Test that flashrom works: +[bbb\_setup.html\#bbb\_access](bbb_setup.html#bbb_access). - # ./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 +Test that flashrom works:\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512**\ In this case, the output was: flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) @@ -255,24 +244,18 @@ In this case, the output was: Please specify which chip definition to use with the -c option. How to backup factory.rom (change the -c option as neeed, for your flash -chip): - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r -factory.rom** - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r -factory1.rom** - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r -factory2.rom** - +chip):\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +factory.rom**\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +factory1.rom**\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +factory2.rom**\ Note: the **-c** option is not required in libreboot's patched flashrom, because the redundant flash chip definitions in *flashchips.c* -have been removed. - -Now compare the 3 images: - - # sha512sum factory*.rom +have been removed.\ +Now compare the 3 images:\ +\# **sha512sum factory\*.rom**\ If the hashes match, then just copy one of them (the factory.rom) to a safe place (on a drive connected to another system, not the BBB). This is useful for reverse engineering work, if there is a desirable @@ -280,20 +263,19 @@ behaviour in the original firmware that could be replicated in coreboot and libreboot. Follow the instructions at -[../hcl/gm45\_remove\_me.html#ich9gen](../hcl/gm45_remove_me.html#ich9gen) +[../hcl/gm45\_remove\_me.html\#ich9gen](../hcl/gm45_remove_me.html#ich9gen) to change the MAC address inside the libreboot ROM image, before flashing it. Although there is a default MAC address inside the ROM image, this is not what you want. **Make sure to always change the MAC address to one that is correct for your system.** -Now flash it: - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w +Now flash it:\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w path/to/libreboot/rom/image.rom -V** ![](images/x200/disassembly/0015.jpg) -You might see errors, but if it says **Verifying flash... VERIFIED** at +You might see errors, but if it says **Verifying flash\... VERIFIED** at the end, then it's flashed and should boot. If you see errors, try again (and again, and again); the message **Chip content is identical to the requested image** is also an indication of a successful @@ -314,6 +296,8 @@ Example output from running the command (see above): [Back to top of page.](#pagetop) + + Thermal paste (IMPORTANT) ========================= @@ -331,13 +315,15 @@ NOTE: the photo above is for illustration purposes only, and does not show how to properly apply the thermal paste. Other guides online detail the proper application procedure. + + Wifi ==== The R400 typically comes with an Intel wifi chipset, which does not work without proprietary software. For a list of wifi chipsets that work without proprietary software, see -[../hcl/#recommended\_wifi](../hcl/#recommended_wifi). +[../hcl/\#recommended\_wifi](../hcl/#recommended_wifi). Some R400 laptops might come with an Atheros chipset, but this is 802.11g only. @@ -348,10 +334,11 @@ whitelist of approved chips, and it will refuse to boot if you use an 'unauthorized' wifi card. The following photos show an Atheros AR5B95 being installed, to replace -the Intel chip that this R400 came with: - +the Intel chip that this R400 came with:\ ![](images/t400/0012.jpg) ![](images/t400/ar5b95.jpg) + + WWAN ==== @@ -362,6 +349,8 @@ track your movements. Not to be confused with wifi (wifi is fine). + + Memory ====== @@ -375,10 +364,11 @@ Make sure that the RAM you buy is the 2Rx8 density. be useful for RAM compatibility info (note: coreboot raminit is different, so this page might be BS) -The following photo shows 8GiB (2x4GiB) of RAM installed: - +The following photo shows 8GiB (2x4GiB) of RAM installed:\ ![](images/t400/memory.jpg) + + Boot it! -------- @@ -388,8 +378,9 @@ You should see something like this: Now [install GNU+Linux](../gnulinux/). -Copyright © 2014, 2015 Leah Rowe + +Copyright © 2014, 2015 Leah Rowe \ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/install/rpi_setup.md b/docs/install/rpi_setup.md index 7eed9fd1..21c8a4fc 100644 --- a/docs/install/rpi_setup.md +++ b/docs/install/rpi_setup.md @@ -1,4 +1,6 @@ -% How to program an SPI flash chip with the Raspberry Pi + +How to program an SPI flash chip with the Raspberry Pi +====================================================== This document exists as a guide for reading from or writing to an SPI flash chip with the Raspberry Pi, using the @@ -11,6 +13,8 @@ SOIC-16). [Back to previous index](../) + + [](#raspberry-pi-thinkpad-x60t60-and-macbook-21){#user-content-raspberry-pi-thinkpad-x60t60-and-macbook-21 .anchor}Raspberry Pi (ThinkPad X60/T60 and Macbook 2,1) ------------------------------------------------------------------------------------------------------------------------------------------------------------------ @@ -53,7 +57,7 @@ B+ with 40 pins, start counting from the right and leave 14 pins): 1234 ~~~ Palmrest (back) ~~ - Pin # SPI Pin Name BP (Seeed) BP (Spkfun) [Beagleboard Black](http://beagleboard.org/Support/bone101#headers) [Raspberry Pi](images/rpi/0000.jpg) + Pin \# SPI Pin Name BP (Seeed) BP (Spkfun) [Beagleboard Black](http://beagleboard.org/Support/bone101#headers) [Raspberry Pi](images/rpi/0000.jpg) -------- -------------- ------------ ------------- --------------------------------------------------------------------- ------------------------------------- 1 CS White Red Pin 17 24 2 MISO Black Brown Pin 21 21 @@ -156,7 +160,7 @@ successfully. If not, just flash again. ### [](#raspberry-pi-pinout-diagrams){#user-content-raspberry-pi-pinout-diagrams .anchor}Raspberry Pi Pinout Diagrams - MCP 3008 Pin Pi GPIO Pin # Pi Pin Name + MCP 3008 Pin Pi GPIO Pin \# Pi Pin Name ----- ---------- ---------------- -------------------- 16 `VDD` 1 `3.3 V` 15 `VREF` 1 `3.3 V` @@ -206,7 +210,7 @@ GPG signature as well. x86# gpg --keyserver prefered.keyserver.org --recv-keys 0x656F212E - x86# for signature in \$(ls *.sig); do gpg --verify \$signature; done + x86# for signature in $(ls *.sig); do gpg --verify $signature; done Extract NOOBS and libreboot. @@ -281,7 +285,7 @@ text. ![](images/rpi/0002.jpg) - Pin # SPI Pin Name Raspberry Pi Pin \# + Pin \# SPI Pin Name Raspberry Pi Pin \# -------- -------------- --------------------- 1 *not used* *not used* 2 3.3V 1 @@ -289,7 +293,7 @@ text. 4 *not used* *not used* 5 *not used* *not used* 6 *not used* *not used* - 7 CS # 24 + 7 CS\# 24 8 S0/SIO1 21 9 *not used* *not used* 10 GND 25 @@ -363,8 +367,8 @@ GPIO Pinouts: ![](images/rpi/0009.png) ![](images/rpi/0010.png) -> *Diagram made by ["Pacman" from Win-Raid -> Forums*](http://www.win-raid.com/t58f16-Guide-Recover-from-failed-BIOS-flash-using-Raspberry-PI.html) +> \*Diagram made by ["Pacman" from Win-Raid +> Forums\*](http://www.win-raid.com/t58f16-Guide-Recover-from-failed-BIOS-flash-using-Raspberry-PI.html) SOIC Pinouts: @@ -421,14 +425,12 @@ box.](http://www.flashrom.org/RaspberryPi) - [Win-Raid - Recover from Failed BIOS Flashing using Raspberry Pi](http://www.win-raid.com/t58f16-Guide-Recover-from-failed-BIOS-flash-using-Raspberry-PI.html) -Copyright © 2014, 2015 Lawrence Wu - -Copyright © 2015 snuffeluffegus <> - -Copyright © 2015 Kevin Keijzer <> -Copyright © 2016 Leah Rowe +Copyright © 2014, 2015 Lawrence Wu \ +Copyright © 2015 snuffeluffegus <>\ +Copyright © 2015 Kevin Keijzer <>\ +Copyright © 2016 Leah Rowe \ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/install/t400_external.md b/docs/install/t400_external.md index ac20a2e5..e8576284 100644 --- a/docs/install/t400_external.md +++ b/docs/install/t400_external.md @@ -1,4 +1,6 @@ -% Flashing the T400 with a BeagleBone Black + +Flashing the T400 with a BeagleBone Black +========================================= Initial flashing instructions for T400. @@ -14,6 +16,9 @@ the screws on page 144 (with title "1130 Keyboard bezel") are swapped and if you follow the HMM you will punch a hole through the bezel in the upper right corner. + + + T400 laptops with libreboot pre-installed {#preinstall} ========================================= @@ -23,6 +28,8 @@ GNU+Linux distribution. Check the [suppliers](../../suppliers) page for more information. + + Serial port {#serial_port} ----------- @@ -30,6 +37,8 @@ EHCI debug might not be needed. It has been reported that the docking station for this laptop has a serial port, so it might be possible to use that instead. + + A note about CPUs ================= @@ -43,6 +52,8 @@ Quad-core CPUs Incompatible. Do not use. + + A note about GPUs ================= @@ -59,17 +70,20 @@ initialization works all the same. CPU paste required ================== -See [#paste](#paste). +See [\#paste](#paste). + + Flash chip size {#flashchips} =============== -Use this to find out: - -# **flashrom -p internal -V** +Use this to find out:\ +\# **flashrom -p internal -V** [Back to top of page.](#pagetop) + + MAC address {#macaddress} =========== @@ -83,6 +97,8 @@ image before flashing it. It will be written in one of these locations: ![](images/t400/macaddress0.jpg) ![](images/t400/macaddress1.jpg) ![](images/x200/disassembly/0001.jpg) + + Initial BBB configuration ========================= @@ -121,90 +137,72 @@ for SOIC-8 (clip: Pomona 5250): The procedure ------------- -Remove *all* screws, placing them in the order that you removed them: - +Remove *all* screws, placing them in the order that you removed them:\ ![](images/t400/0001.jpg) ![](images/t400/0002.jpg) -Remove those three screws then remove the rear bezel: - +Remove those three screws then remove the rear bezel:\ ![](images/t400/0003.jpg) ![](images/t400/0004.jpg) ![](images/t400/0005.jpg) ![](images/t400/0006.jpg) -Remove the speakers: - +Remove the speakers:\ ![](images/t400/0007.jpg) ![](images/t400/0008.jpg) ![](images/t400/0009.jpg) ![](images/t400/0010.jpg) ![](images/t400/0011.jpg) -Remove the wifi: - +Remove the wifi:\ ![](images/t400/0012.jpg) ![](images/t400/0013.jpg) -Remove this cable: - +Remove this cable:\ ![](images/t400/0014.jpg) ![](images/t400/0015.jpg) ![](images/t400/0016.jpg) ![](images/t400/0017.jpg) ![](images/t400/0018.jpg) -Unroute those antenna wires: - +Unroute those antenna wires:\ ![](images/t400/0019.jpg) ![](images/t400/0020.jpg) ![](images/t400/0021.jpg) ![](images/t400/0022.jpg) ![](images/t400/0023.jpg) -Remove the LCD assembly: - +Remove the LCD assembly:\ ![](images/t400/0024.jpg) ![](images/t400/0025.jpg) ![](images/t400/0026.jpg) ![](images/t400/0027.jpg) ![](images/t400/0028.jpg) ![](images/t400/0029.jpg) ![](images/t400/0030.jpg) ![](images/t400/0031.jpg) -Disconnect the NVRAM battery: - +Disconnect the NVRAM battery:\ ![](images/t400/0033.jpg) -Disconnect the fan: - +Disconnect the fan:\ ![](images/t400/0034.jpg) -Unscrew these: - +Unscrew these:\ ![](images/t400/0035.jpg) ![](images/t400/0036.jpg) ![](images/t400/0037.jpg) ![](images/t400/0038.jpg) -Unscrew the heatsink, then lift it off: - +Unscrew the heatsink, then lift it off:\ ![](images/t400/0039.jpg) ![](images/t400/0040.jpg) -Disconnect the power jack: - +Disconnect the power jack:\ ![](images/t400/0041.jpg) ![](images/t400/0042.jpg) -Loosen this: - +Loosen this:\ ![](images/t400/0043.jpg) -Remove this: - +Remove this:\ ![](images/t400/0044.jpg) ![](images/t400/0045.jpg) ![](images/t400/0046.jpg) ![](images/t400/0047.jpg) ![](images/t400/0048.jpg) -Unscrew these: - +Unscrew these:\ ![](images/t400/0049.jpg) ![](images/t400/0050.jpg) -Remove this: - +Remove this:\ ![](images/t400/0051.jpg) ![](images/t400/0052.jpg) -Unscrew this: - +Unscrew this:\ ![](images/t400/0053.jpg) Remove the motherboard (the cage is still attached) from the right hand -side, then lift it out: - +side, then lift it out:\ ![](images/t400/0054.jpg) ![](images/t400/0055.jpg) ![](images/t400/0056.jpg) @@ -214,23 +212,19 @@ later): ![](images/t400/0057.jpg) ![](images/t400/0058.jpg) ![](images/t400/0059.jpg) ![](images/t400/0060.jpg) ![](images/t400/0061.jpg) ![](images/t400/0062.jpg) -Separate the motherboard: - +Separate the motherboard:\ ![](images/t400/0063.jpg) ![](images/t400/0064.jpg) -Connect your programmer, then connect GND and 3.3V - +Connect your programmer, then connect GND and 3.3V\ ![](images/t400/0065.jpg) ![](images/t400/0066.jpg) ![](images/t400/0067.jpg) ![](images/t400/0069.jpg) ![](images/t400/0070.jpg) ![](images/t400/0071.jpg) A dedicated 3.3V PSU was used to create this guide, but at ATX PSU is -also fine: - +also fine:\ ![](images/t400/0072.jpg) -Of course, make sure to turn on your PSU: - +Of course, make sure to turn on your PSU:\ ![](images/x200/disassembly/0013.jpg) Now, you should be ready to install libreboot. @@ -240,11 +234,10 @@ libreboot\_util. Alternatively, libreboot also distributes flashrom source code which can be built. Log in as root on your BBB, using the instructions in -[bbb\_setup.html#bbb\_access](bbb_setup.html#bbb_access). - -Test that flashrom works: +[bbb\_setup.html\#bbb\_access](bbb_setup.html#bbb_access). - # ./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 +Test that flashrom works:\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512**\ In this case, the output was: flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) @@ -257,24 +250,18 @@ In this case, the output was: Please specify which chip definition to use with the -c option. How to backup factory.rom (change the -c option as neeed, for your flash -chip): - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r -factory.rom** - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r -factory1.rom** - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r -factory2.rom** - +chip):\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +factory.rom**\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +factory1.rom**\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +factory2.rom**\ Note: the **-c** option is not required in libreboot's patched flashrom, because the redundant flash chip definitions in *flashchips.c* -have been removed. - -Now compare the 3 images: - - # sha512sum factory*.rom +have been removed.\ +Now compare the 3 images:\ +\# **sha512sum factory\*.rom**\ If the hashes match, then just copy one of them (the factory.rom) to a safe place (on a drive connected to another system, not the BBB). This is useful for reverse engineering work, if there is a desirable @@ -282,20 +269,19 @@ behaviour in the original firmware that could be replicated in coreboot and libreboot. Follow the instructions at -[../hcl/gm45\_remove\_me.html#ich9gen](../hcl/gm45_remove_me.html#ich9gen) +[../hcl/gm45\_remove\_me.html\#ich9gen](../hcl/gm45_remove_me.html#ich9gen) to change the MAC address inside the libreboot ROM image, before flashing it. Although there is a default MAC address inside the ROM image, this is not what you want. **Make sure to always change the MAC address to one that is correct for your system.** -Now flash it: - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w +Now flash it:\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w path/to/libreboot/rom/image.rom -V** ![](images/x200/disassembly/0015.jpg) -You might see errors, but if it says **Verifying flash... VERIFIED** at +You might see errors, but if it says **Verifying flash\... VERIFIED** at the end, then it's flashed and should boot. If you see errors, try again (and again, and again); the message **Chip content is identical to the requested image** is also an indication of a successful @@ -316,6 +302,8 @@ Example output from running the command (see above): [Back to top of page.](#pagetop) + + Thermal paste (IMPORTANT) ========================= @@ -333,13 +321,15 @@ NOTE: the photo above is for illustration purposes only, and does not show how to properly apply the thermal paste. Other guides online detail the proper application procedure. + + Wifi ==== The T400 typically comes with an Intel wifi chipset, which does not work without proprietary software. For a list of wifi chipsets that work without proprietary software, see -[../hcl/#recommended\_wifi](../hcl/#recommended_wifi). +[../hcl/\#recommended\_wifi](../hcl/#recommended_wifi). Some T400 laptops might come with an Atheros chipset, but this is 802.11g only. @@ -350,10 +340,11 @@ whitelist of approved chips, and it will refuse to boot if you use an 'unauthorized' wifi card. The following photos show an Atheros AR5B95 being installed, to replace -the Intel chip that this T400 came with: - +the Intel chip that this T400 came with:\ ![](images/t400/0012.jpg) ![](images/t400/ar5b95.jpg) + + WWAN ==== @@ -364,6 +355,8 @@ track your movements. Not to be confused with wifi (wifi is fine). + + Memory ====== @@ -377,10 +370,11 @@ Make sure that the RAM you buy is the 2Rx8 density. be useful for RAM compatibility info (note: coreboot raminit is different, so this page might be BS) -The following photo shows 8GiB (2x4GiB) of RAM installed: - +The following photo shows 8GiB (2x4GiB) of RAM installed:\ ![](images/t400/memory.jpg) + + Boot it! -------- @@ -390,8 +384,9 @@ You should see something like this: Now [install GNU+Linux](../gnulinux/). -Copyright © 2015 Leah Rowe + +Copyright © 2015 Leah Rowe \ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/install/t500_external.md b/docs/install/t500_external.md index a3176cc8..accaac32 100644 --- a/docs/install/t500_external.md +++ b/docs/install/t500_external.md @@ -1,4 +1,6 @@ -% Flashing the T500 with a BeagleBone Black + +Flashing the T500 with a BeagleBone Black +========================================= Initial flashing instructions for T500. @@ -6,12 +8,17 @@ This guide is for those who want libreboot on their ThinkPad T500 while they still have the original Lenovo BIOS present. This guide can also be followed (adapted) if you brick your T500, to know how to recover. + + + Libreboot T400 {#t400} ============== You may also be interested in the smaller, more portable [Libreboot T400](t400_external.html). + + Serial port {#serial_port} ----------- @@ -19,6 +26,8 @@ EHCI debug might not be needed. It has been reported that the docking station for this laptop has a serial port, so it might be possible to use that instead. + + A note about CPUs ================= @@ -33,6 +42,8 @@ Quad-core CPUs Incompatible. Do not use. + + A note about GPUs ================= @@ -49,17 +60,20 @@ initialization works all the same. CPU paste required ================== -See [#paste](#paste). +See [\#paste](#paste). + + Flash chip size {#flashchips} =============== -Use this to find out: - -# **flashrom -p internal -V** +Use this to find out:\ +\# **flashrom -p internal -V** [Back to top of page.](#pagetop) + + MAC address {#macaddress} =========== @@ -73,6 +87,8 @@ image before flashing it. It will be written in one of these locations: ![](images/t400/macaddress0.jpg) ![](images/t400/macaddress1.jpg) ![](images/x200/disassembly/0001.jpg) + + Initial BBB configuration ========================= @@ -111,26 +127,20 @@ for SOIC-8 (clip: Pomona 5250): The procedure ------------- -Remove all screws: - -![](images/t500/0000.jpg) - +Remove all screws:\ +![](images/t500/0000.jpg)\ It is also advisable to, throughout the disassembly, place any screws and/or components that you removed in the same layout or arrangement. -The follow photos demonstrate this: - +The follow photos demonstrate this:\ ![](images/t500/0001.jpg) ![](images/t500/0002.jpg) -Remove the HDD/SSD and optical drive: - +Remove the HDD/SSD and optical drive:\ ![](images/t500/0003.jpg) ![](images/t500/0004.jpg) -Remove the palm rest: - +Remove the palm rest:\ ![](images/t500/0005.jpg) ![](images/t500/0006.jpg) -Remove the keyboard and rear bezel: - +Remove the keyboard and rear bezel:\ ![](images/t500/0007.jpg) ![](images/t500/0008.jpg) ![](images/t500/0009.jpg) ![](images/t500/0010.jpg) ![](images/t500/0011.jpg) ![](images/t500/0012.jpg) @@ -138,109 +148,88 @@ Remove the keyboard and rear bezel: If you have a WWAN/3G card and/or sim card reader, remove them permanently. The WWAN-3G card has proprietary firmware inside; the technology is identical to what is used in mobile phones, so it can also -track your movements: - +track your movements:\ ![](images/t500/0013.jpg) ![](images/t500/0017.jpg) ![](images/t500/0018.jpg) -Remove this frame, and then remove the wifi chip: - +Remove this frame, and then remove the wifi chip:\ ![](images/t500/0014.jpg) ![](images/t500/0015.jpg) ![](images/t500/0016.jpg) -Remove the speakers: - +Remove the speakers:\ ![](images/t500/0019.jpg) ![](images/t500/0020.jpg) ![](images/t500/0021.jpg) ![](images/t500/0022.jpg) ![](images/t500/0023.jpg) ![](images/t500/0024.jpg) ![](images/t500/0025.jpg) -Remove the NVRAM battery (already removed in this photo): - +Remove the NVRAM battery (already removed in this photo):\ ![](images/t500/0026.jpg) When you re-assemble, you will be replacing the wifi chip with another. These two screws don't hold anything together, but they are included in your system because the screw holes for half-height cards are a different size, so use these if you will be installing a half-height -card: - +card:\ ![](images/t500/0027.jpg) -Unroute the antenna wires: - +Unroute the antenna wires:\ ![](images/t500/0028.jpg) ![](images/t500/0029.jpg) ![](images/t500/0030.jpg) ![](images/t500/0031.jpg) -Disconnect the LCD cable from the motherboard: - +Disconnect the LCD cable from the motherboard:\ ![](images/t500/0032.jpg) ![](images/t500/0033.jpg) -Remove the LCD assembly hinge screws, and then remove the LCD assembly: - +Remove the LCD assembly hinge screws, and then remove the LCD assembly:\ ![](images/t500/0034.jpg) ![](images/t500/0035.jpg) ![](images/t500/0036.jpg) -Remove the fan and heatsink: - +Remove the fan and heatsink:\ ![](images/t500/0037.jpg) ![](images/t500/0038.jpg) ![](images/t500/0039.jpg) -Remove this screw: - +Remove this screw:\ ![](images/t500/0040.jpg) Remove these cables, keeping note of how and in what arrangement they -are connected: - +are connected:\ ![](images/t500/0041.jpg) ![](images/t500/0042.jpg) ![](images/t500/0043.jpg) ![](images/t500/0044.jpg) ![](images/t500/0045.jpg) ![](images/t500/0046.jpg) ![](images/t500/0047.jpg) ![](images/t500/0048.jpg) ![](images/t500/0049.jpg) -Disconnect the power jack: - +Disconnect the power jack:\ ![](images/t500/0050.jpg) ![](images/t500/0051.jpg) Remove the motherboard and cage from the base (the marked hole is where -those cables were routed through): - +those cables were routed through):\ ![](images/t500/0052.jpg) ![](images/t500/0053.jpg) Remove all screws, arranging them in the same layout when placing the screws on a surface and marking each screw hole (this is to reduce the -possibility of putting them back in the wrong holes): - +possibility of putting them back in the wrong holes):\ ![](images/t500/0054.jpg) ![](images/t500/0055.jpg) -Also remove this: - +Also remove this:\ ![](images/t500/0056.jpg) ![](images/t500/0057.jpg) -Separate the motherboard from the cage: - +Separate the motherboard from the cage:\ ![](images/t500/0058.jpg) ![](images/t500/0059.jpg) The flash chip is next to the memory slots. On this system, it was a -SOIC-8 (4MiB or 32Mb) flash chip: - +SOIC-8 (4MiB or 32Mb) flash chip:\ ![](images/t500/0060.jpg) -Connect your programmer, then connect GND and 3.3V - -![](images/t500/0061.jpg) - +Connect your programmer, then connect GND and 3.3V\ +![](images/t500/0061.jpg)\ ![](images/t400/0067.jpg) ![](images/t400/0069.jpg) ![](images/t400/0070.jpg) ![](images/t400/0071.jpg) A dedicated 3.3V PSU was used to create this guide, but at ATX PSU is -also fine: - +also fine:\ ![](images/t400/0072.jpg) -Of course, make sure to turn on your PSU: - +Of course, make sure to turn on your PSU:\ ![](images/x200/disassembly/0013.jpg) Now, you should be ready to install libreboot. @@ -250,11 +239,10 @@ libreboot\_util. Alternatively, libreboot also distributes flashrom source code which can be built. Log in as root on your BBB, using the instructions in -[bbb\_setup.html#bbb\_access](bbb_setup.html#bbb_access). - -Test that flashrom works: +[bbb\_setup.html\#bbb\_access](bbb_setup.html#bbb_access). - # ./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 +Test that flashrom works:\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512**\ In this case, the output was: flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) @@ -267,24 +255,18 @@ In this case, the output was: Please specify which chip definition to use with the -c option. How to backup factory.rom (change the -c option as neeed, for your flash -chip): - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r -factory.rom** - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r -factory1.rom** - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r -factory2.rom** - +chip):\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +factory.rom**\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +factory1.rom**\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +factory2.rom**\ Note: the **-c** option is not required in libreboot's patched flashrom, because the redundant flash chip definitions in *flashchips.c* -have been removed. - -Now compare the 3 images: - - # sha512sum factory*.rom +have been removed.\ +Now compare the 3 images:\ +\# **sha512sum factory\*.rom**\ If the hashes match, then just copy one of them (the factory.rom) to a safe place (on a drive connected to another system, not the BBB). This is useful for reverse engineering work, if there is a desirable @@ -292,20 +274,19 @@ behaviour in the original firmware that could be replicated in coreboot and libreboot. Follow the instructions at -[../hcl/gm45\_remove\_me.html#ich9gen](../hcl/gm45_remove_me.html#ich9gen) +[../hcl/gm45\_remove\_me.html\#ich9gen](../hcl/gm45_remove_me.html#ich9gen) to change the MAC address inside the libreboot ROM image, before flashing it. Although there is a default MAC address inside the ROM image, this is not what you want. **Make sure to always change the MAC address to one that is correct for your system.** -Now flash it: - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w +Now flash it:\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w path/to/libreboot/rom/image.rom -V** ![](images/x200/disassembly/0015.jpg) -You might see errors, but if it says **Verifying flash... VERIFIED** at +You might see errors, but if it says **Verifying flash\... VERIFIED** at the end, then it's flashed and should boot. If you see errors, try again (and again, and again); the message **Chip content is identical to the requested image** is also an indication of a successful @@ -326,6 +307,8 @@ Example output from running the command (see above): [Back to top of page.](#pagetop) + + Thermal paste (IMPORTANT) ========================= @@ -343,13 +326,15 @@ NOTE: the photo above is for illustration purposes only, and does not show how to properly apply the thermal paste. Other guides online detail the proper application procedure. + + Wifi ==== The T500 typically comes with an Intel wifi chipset, which does not work without proprietary software. For a list of wifi chipsets that work without proprietary software, see -[../hcl/#recommended\_wifi](../hcl/#recommended_wifi). +[../hcl/\#recommended\_wifi](../hcl/#recommended_wifi). Some T500 laptops might come with an Atheros chipset, but this is 802.11g only. @@ -360,10 +345,11 @@ whitelist of approved chips, and it will refuse to boot if you use an 'unauthorized' wifi card. The following photos show an Atheros AR5B95 being installed, to replace -the Intel chip that this T500 came with: - +the Intel chip that this T500 came with:\ ![](images/t400/0012.jpg) ![](images/t400/ar5b95.jpg) + + WWAN ==== @@ -374,6 +360,8 @@ also track your movements. Not to be confused with wifi (wifi is fine). + + Memory ====== @@ -387,10 +375,11 @@ Make sure that the RAM you buy is the 2Rx8 density. be useful for RAM compatibility info (note: coreboot raminit is different, so this page might be BS) -The following photo shows 8GiB (2x4GiB) of RAM installed: - +The following photo shows 8GiB (2x4GiB) of RAM installed:\ ![](images/t400/memory.jpg) + + Boot it! -------- @@ -400,8 +389,9 @@ You should see something like this: Now [install GNU+Linux](../gnulinux/). -Copyright © 2015 Leah Rowe + +Copyright © 2015 Leah Rowe \ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/install/t60_unbrick.md b/docs/install/t60_unbrick.md index 1ce8d588..47bc3d06 100644 --- a/docs/install/t60_unbrick.md +++ b/docs/install/t60_unbrick.md @@ -1,10 +1,14 @@ -% ThinkPad T60: Recovery guide + +ThinkPad T60: Recovery guide +============================ This section documents how to recover from a bad flash that prevents your ThinkPad T60 from booting. [Back to previous index](./) + + Table of Contents ----------------- @@ -13,37 +17,36 @@ Table of Contents - [Brick type 2: bad rom (or user error), system won't boot](#recovery) + + Brick type 1: bucts not reset. {#bucts_brick} ============================== You still have Lenovo BIOS, or you had libreboot running and you flashed -another ROM; and you had bucts 1 set and the ROM wasn't dd'd.* or if -Lenovo BIOS was present and libreboot wasn't flashed. - +another ROM; and you had bucts 1 set and the ROM wasn't dd'd.\* or if +Lenovo BIOS was present and libreboot wasn't flashed.\ +\ In this case, unbricking is easy: reset BUC.TS to 0 by removing that yellow cmos coin (it's a battery) and putting it back after a minute or -two: - -![](../images/t60_dev/0006.JPG) - -*Those dd commands should be applied to all newly compiled T60 ROM +two:\ +![](../images/t60_dev/0006.JPG)\ +\ +\*Those dd commands should be applied to all newly compiled T60 ROM images (the ROM images in libreboot binary archives already have this -applied!): - +applied!):\ dd if=coreboot.rom of=top64k.bin bs=1 skip=\$\[\$(stat -c %s -coreboot.rom) - 0x10000\] count=64k - +coreboot.rom) - 0x10000\] count=64k\ dd if=coreboot.rom bs=1 skip=\$\[\$(stat -c %s coreboot.rom) - 0x20000\] -count=64k | hexdump - +count=64k | hexdump\ dd if=top64k.bin of=coreboot.rom bs=1 seek=\$\[\$(stat -c %s -coreboot.rom) - 0x20000\] count=64k conv=notrunc - +coreboot.rom) - 0x20000\] count=64k conv=notrunc\ (doing this makes the ROM suitable for use when flashing a system that still has Lenovo BIOS running, using those instructions: . (it says x60, but instructions for t60 are identical) + + bad rom (or user error), system won't boot {#recovery} =========================================== @@ -58,80 +61,62 @@ you can't boot the system, making this difficult. In this situation, external hardware (see hardware requirements above) is needed which can flash the SPI chip (where libreboot resides). -Remove those screws and remove the HDD: - +Remove those screws and remove the HDD:\ ![](../images/t60_dev/0001.JPG) ![](../images/t60_dev/0002.JPG) -Lift off the palm rest: - +Lift off the palm rest:\ ![](../images/t60_dev/0003.JPG) Lift up the keyboard, pull it back a bit, flip it over like that and -then disconnect it from the board: - +then disconnect it from the board:\ ![](../images/t60_dev/0004.JPG) ![](../images/t60_dev/0005.JPG) ![](../images/t60_dev/0006.JPG) -Gently wedge both sides loose: - +Gently wedge both sides loose:\ ![](../images/t60_dev/0007.JPG) ![](../images/t60_dev/0008.JPG) -Remove that cable from the position: - +Remove that cable from the position:\ ![](../images/t60_dev/0009.JPG) ![](../images/t60_dev/0010.JPG) Now remove that bezel. Remove wifi, nvram battery and speaker connector -(also remove 56k modem, on the left of wifi): - +(also remove 56k modem, on the left of wifi):\ ![](../images/t60_dev/0011.JPG) -Remove those screws: - +Remove those screws:\ ![](../images/t60_dev/0012.JPG) -Disconnect the power jack: - +Disconnect the power jack:\ ![](../images/t60_dev/0013.JPG) -Remove nvram battery: - +Remove nvram battery:\ ![](../images/t60_dev/0014.JPG) -Disconnect cable (for 56k modem) and disconnect the other cable: - +Disconnect cable (for 56k modem) and disconnect the other cable:\ ![](../images/t60_dev/0015.JPG) ![](../images/t60_dev/0016.JPG) -Disconnect speaker cable: - +Disconnect speaker cable:\ ![](../images/t60_dev/0017.JPG) -Disconnect the other end of the 56k modem cable: - +Disconnect the other end of the 56k modem cable:\ ![](../images/t60_dev/0018.JPG) -Make sure you removed it: - +Make sure you removed it:\ ![](../images/t60_dev/0019.JPG) -Unscrew those: - +Unscrew those:\ ![](../images/t60_dev/0020.JPG) -Make sure you removed those: - +Make sure you removed those:\ ![](../images/t60_dev/0021.JPG) -Disconnect LCD cable from board: - +Disconnect LCD cable from board:\ ![](../images/t60_dev/0022.JPG) -Remove those screws then remove the LCD assembly: - +Remove those screws then remove the LCD assembly:\ ![](../images/t60_dev/0023.JPG) ![](../images/t60_dev/0024.JPG) ![](../images/t60_dev/0025.JPG) -Once again, make sure you removed those: - +Once again, make sure you removed those:\ ![](../images/t60_dev/0026.JPG) Remove the shielding containing the motherboard, then flip it over. @@ -139,25 +124,20 @@ Remove these screws, placing them on a steady surface in the same layout as they were in before you removed them. Also, you should mark each screw hole after removing the screw (a permanent marker pen will do), this is so that you have a point of reference when re-assembling the -system: - +system:\ ![](../images/t60_dev/0027.JPG) ![](../images/t60_dev/0028.JPG) ![](../images/t60_dev/0029.JPG) ![](../images/t60_dev/0031.JPG) ![](../images/t60_dev/0032.JPG) ![](../images/t60_dev/0033.JPG) -Now wire up the BBB and the Pomona with your PSU. - +Now wire up the BBB and the Pomona with your PSU.\ Refer to [bbb\_setup.html](bbb_setup.html) for how to setup the BBB for -flashing. - +flashing.\ **Note, the guide mentions a 3.3v DC PSU but you don't need this on the T60: if you don't have or don't want to use an external PSU, then make sure not to connect the 3.3v leads mentioned in the guide; instead, connect the AC adapter (the one that normally charges your battery) so -that the board has power (but don't boot it up)** - -![](../images/t60_dev/0030.JPG) - +that the board has power (but don't boot it up)**\ +![](../images/t60_dev/0030.JPG)\ Correlate the following with the BBB guide linked above: POMONA 5250: @@ -176,76 +156,64 @@ Flashrom binaries for ARM (tested on a BBB) are distributed in libreboot\_util. Alternatively, libreboot also distributes flashrom source code which can be built. -SSH'd into the BBB: - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w +SSH'd into the BBB:\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w yourrom.rom** -It should be **Verifying flash... VERIFIED** at the end. If flashrom +It should be **Verifying flash\... VERIFIED** at the end. If flashrom complains about multiple flash chip definitions detected, then choose one of them following the instructions in the output. -Put those screws back: - +Put those screws back:\ ![](../images/t60_dev/0047.JPG) -Put it back into lower chassis: - +Put it back into lower chassis:\ ![](../images/t60_dev/0048.JPG) -Attach LCD and insert screws (also, attach the lcd cable to the board): - +Attach LCD and insert screws (also, attach the lcd cable to the board):\ ![](../images/t60_dev/0049.JPG) -Insert those screws: - +Insert those screws:\ ![](../images/t60_dev/0050.JPG) On the CPU (and there is another chip south-east to it, sorry forgot to take pic) clean off the old thermal paste (with the alcohol) and apply new (Artic Silver 5 is good, others are good too) you should also clean -the heatsink the same way - +the heatsink the same way\ ![](../images/t60_dev/0051.JPG) Attach the heatsink and install the screws (also, make sure to install -the AC jack as highlighted): - +the AC jack as highlighted):\ ![](../images/t60_dev/0052.JPG) -Reinstall that upper bezel: - +Reinstall that upper bezel:\ ![](../images/t60_dev/0053.JPG) -Do that: - +Do that:\ ![](../images/t60_dev/0054.JPG) ![](../images/t60_dev/0055.JPG) Re-attach modem, wifi, (wwan?), and all necessary cables. Sorry, forgot to take pics. Look at previous removal steps to see where they go back to. -Attach keyboard and install nvram battery: - +Attach keyboard and install nvram battery:\ ![](../images/t60_dev/0056.JPG) ![](../images/t60_dev/0057.JPG) Place keyboard and (sorry, forgot to take pics) reinstall the palmrest -and insert screws on the underside: - +and insert screws on the underside:\ ![](../images/t60_dev/0058.JPG) -It lives! - +It lives!\ ![](../images/t60_dev/0071.JPG) ![](../images/t60_dev/0072.JPG) ![](../images/t60_dev/0073.JPG) Always stress test ('stress -c 2' and xsensors. below 90C is ok) when -replacing cpu paste/heatsink: - +replacing cpu paste/heatsink:\ ![](../images/t60_dev/0074.JPG) -Copyright © 2014, 2015 Leah Rowe + +Copyright © 2014, 2015 Leah Rowe \ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/install/x200_external.md b/docs/install/x200_external.md index adb0dae8..ccfab1ae 100644 --- a/docs/install/x200_external.md +++ b/docs/install/x200_external.md @@ -1,4 +1,6 @@ -% Flashing the X200 with a BeagleBone Black + +Flashing the X200 with a BeagleBone Black +========================================= Initial flashing instructions for X200. @@ -16,6 +18,9 @@ followed (adapted) if you brick your X200, to know how to recover. - [Memory](#memory) - [X200S and X200 Tablet users: GPIO33 trick will not work.](#gpio33) + + + X200 laptops with libreboot pre-installed {#preinstall} ========================================= @@ -25,20 +30,23 @@ GNU+Linux distribution. Check the [suppliers](../../suppliers) page for more information. + + Flash chip size {#flashchips} =============== -Use this to find out: - -# **flashrom -p internal -V** +Use this to find out:\ +\# **flashrom -p internal -V** The X200S and X200 Tablet will use a WSON-8 flash chip, on the bottom of the motherboard (this requires removal of the motherboard). **Not all X200S/X200T are supported; see -[../hcl/x200.html#x200s](../hcl/x200.html#x200s).** +[../hcl/x200.html\#x200s](../hcl/x200.html#x200s).** [Back to top of page.](#pagetop) + + MAC address {#macaddress} =========== @@ -53,6 +61,8 @@ image before flashing it. It will be written in one of these locations: ![](images/x200/disassembly/0002.jpg) ![](images/x200/disassembly/0001.jpg) + + Initial BBB configuration {#clip} ========================= @@ -91,21 +101,20 @@ header), for SOIC-8 (clip: Pomona 5250): This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack. Here is a photo of the SOIC-8 flash chip. The pins are labelled: + + Look at the pads in that photo, on the left and right. Those are for SOIC-16. Would it be possible to remove the SOIC-8 and solder a SOIC-16 chip on those pins? **On the X200S and X200 Tablet the flash chip is underneath the board, in a WSON package. The pinout is very much the same as a SOIC-8, except -you need to solder (there are no clips available). - -The following image shows how this is done:** - -![](images/x200/wson_soldered.jpg "Copyright 2014 Steve Shenton see license notice at the end of this document") - +you need to solder (there are no clips available).\ +The following image shows how this is done:**\ +![](images/x200/wson_soldered.jpg "Copyright 2014 Steve Shenton see license notice at the end of this document")\ In this image, a pin header was soldered onto the WSON. Another solution might be to de-solder the WSON-8 chip and put a SOIC-8 there instead. Check the list of SOIC-8 flash chips at -[../hcl/gm45\_remove\_me.html#flashchips](../hcl/gm45_remove_me.html#flashchips) +[../hcl/gm45\_remove\_me.html\#flashchips](../hcl/gm45_remove_me.html#flashchips) but do note that these are only 4MiB (32Mb) chips. The only X200 SPI chips with 8MiB capacity are SOIC-16. For 8MiB capacity in this case, the X201 SOIC-8 flash chip (Macronix 25L6445E) might work. @@ -117,47 +126,39 @@ This section is for the X200. This does not apply to the X200S or X200 Tablet (for those systems, you have to remove the motherboard completely, since the flash chip is on the other side of the board). -Remove these screws: - +Remove these screws:\ ![](images/x200/disassembly/0003.jpg) Push the keyboard forward, gently, then lift it off and disconnect it -from the board: - +from the board:\ ![](images/x200/disassembly/0004.jpg) ![](images/x200/disassembly/0005.jpg) Pull the palm rest off, lifting from the left and right side at the back -of the palm rest: - +of the palm rest:\ ![](images/x200/disassembly/0006.jpg) Lift back the tape that covers a part of the flash chip, and then -connect the clip: - +connect the clip:\ ![](images/x200/disassembly/0007.jpg) ![](images/x200/disassembly/0008.jpg) On pin 2 of the BBB, where you have the ground (GND), connect the ground -to your PSU: - +to your PSU:\ ![](images/x200/disassembly/0009.jpg) ![](images/x200/disassembly/0010.jpg) -Connect the 3.3V supply from your PSU to the flash chip (via the clip): - +Connect the 3.3V supply from your PSU to the flash chip (via the clip):\ ![](images/x200/disassembly/0011.jpg) ![](images/x200/disassembly/0012.jpg) -Of course, make sure that your PSU is also plugged in and turn on: - +Of course, make sure that your PSU is also plugged in and turn on:\ ![](images/x200/disassembly/0013.jpg) This tutorial tells you to use an ATX PSU, for the 3.3V DC supply. The PSU used when taking these photos is actually not an ATX PSU, but a PSU that is designed specifically for providing 3.3V DC (an ATX PSU will -also work): - +also work):\ ![](images/x200/disassembly/0014.jpg) Now, you should be ready to install libreboot. @@ -167,11 +168,10 @@ libreboot\_util. Alternatively, libreboot also distributes flashrom source code which can be built. Log in as root on your BBB, using the instructions in -[bbb\_setup.html#bbb\_access](bbb_setup.html#bbb_access). - -Test that flashrom works: +[bbb\_setup.html\#bbb\_access](bbb_setup.html#bbb_access). - # ./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 +Test that flashrom works:\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512**\ In this case, the output was: flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) @@ -184,24 +184,18 @@ In this case, the output was: Please specify which chip definition to use with the -c option. How to backup factory.rom (change the -c option as neeed, for your flash -chip): - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r -factory.rom** - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r -factory1.rom** - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r -factory2.rom** - +chip):\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +factory.rom**\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +factory1.rom**\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +factory2.rom**\ Note: the **-c** option is not required in libreboot's patched flashrom, because the redundant flash chip definitions in *flashchips.c* -have been removed. - -Now compare the 3 images: - - # sha512sum factory*.rom +have been removed.\ +Now compare the 3 images:\ +\# **sha512sum factory\*.rom**\ If the hashes match, then just copy one of them (the factory.rom) to a safe place (on a drive connected to another system, not the BBB). This is useful for reverse engineering work, if there is a desirable @@ -209,20 +203,19 @@ behaviour in the original firmware that could be replicated in coreboot and libreboot. Follow the instructions at -[../hcl/gm45\_remove\_me.html#ich9gen](../hcl/gm45_remove_me.html#ich9gen) +[../hcl/gm45\_remove\_me.html\#ich9gen](../hcl/gm45_remove_me.html#ich9gen) to change the MAC address inside the libreboot ROM image, before flashing it. Although there is a default MAC address inside the ROM image, this is not what you want. **Make sure to always change the MAC address to one that is correct for your system.** -Now flash it: - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w +Now flash it:\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w path/to/libreboot/rom/image.rom -V** ![](images/x200/disassembly/0015.jpg) -You might see errors, but if it says **Verifying flash... VERIFIED** at +You might see errors, but if it says **Verifying flash\... VERIFIED** at the end, then it's flashed and should boot. If you see errors, try again (and again, and again); the message **Chip content is identical to the requested image** is also an indication of a successful @@ -243,13 +236,15 @@ Example output from running the command (see above): [Back to top of page.](#pagetop) + + Wifi ==== The X200 typically comes with an Intel wifi chipset, which does not work without proprietary software. For a list of wifi chipsets that work without proprietary software, see -[../hcl/#recommended\_wifi](../hcl/#recommended_wifi). +[../hcl/\#recommended\_wifi](../hcl/#recommended_wifi). Some X200 laptops come with an Atheros chipset, but this is 802.11g only. @@ -260,11 +255,12 @@ whitelist of approved chips, and it will refuse to boot if you use an 'unauthorized' wifi card. The following photos show an Atheros AR5B95 being installed, to replace -the Intel chip that this X200 came with: - +the Intel chip that this X200 came with:\ ![](images/x200/disassembly/0016.jpg) ![](images/x200/disassembly/0017.jpg) + + WWAN ==== @@ -275,6 +271,8 @@ track your movements. Not to be confused with wifi (wifi is fine). + + Memory ====== @@ -287,10 +285,11 @@ work in some cases. Make sure that the RAM you buy is the 2Rx8 density. -In this photo, 8GiB of RAM (2x4GiB) is installed: - +In this photo, 8GiB of RAM (2x4GiB) is installed:\ ![](images/x200/disassembly/0018.jpg) + + Boot it! {#boot} -------- @@ -300,6 +299,8 @@ You should see something like this: Now [install GNU+Linux](../gnulinux/). + + X200S and X200 Tablet users: GPIO33 trick will not work. {#gpio33} -------------------------------------------------------- @@ -308,8 +309,7 @@ disable the flashing protections by the descriptor and stop the ME from starting (which itself interferes with flashing attempts). The theory was proven correct; however, it is still useless in practise. -Look just above the 7 in TP37 (that's GPIO33): - +Look just above the 7 in TP37 (that's GPIO33):\ ![](../hcl/images/x200/gpio33_location.jpg) By default we would see this in lenovobios, when trying flashrom -p @@ -340,10 +340,11 @@ here: On a related note, libreboot has a utility that could help with investigating this: -[../hcl/gm45\_remove\_me.html#demefactory](../hcl/gm45_remove_me.html#demefactory) +[../hcl/gm45\_remove\_me.html\#demefactory](../hcl/gm45_remove_me.html#demefactory) + -Copyright © 2014, 2015 Leah Rowe +Copyright © 2014, 2015 Leah Rowe \ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/install/x60_unbrick.md b/docs/install/x60_unbrick.md index a5bb9eef..19b1abb8 100644 --- a/docs/install/x60_unbrick.md +++ b/docs/install/x60_unbrick.md @@ -1,10 +1,14 @@ -% ThinkPad X60: Recovery guide + +ThinkPad X60: Recovery guide +============================ This section documents how to recover from a bad flash that prevents your ThinkPad X60 from booting. [Back to previous index](./) + + Table of Contents ================= @@ -13,36 +17,35 @@ Table of Contents - [Brick type 2: bad rom (or user error), system won't boot](#recovery) + + Brick type 1: bucts not reset. {#bucts_brick} ============================== You still have Lenovo BIOS, or you had libreboot running and you flashed -another ROM; and you had bucts 1 set and the ROM wasn't dd'd.* or if -Lenovo BIOS was present and libreboot wasn't flashed. - +another ROM; and you had bucts 1 set and the ROM wasn't dd'd.\* or if +Lenovo BIOS was present and libreboot wasn't flashed.\ +\ In this case, unbricking is easy: reset BUC.TS to 0 by removing that yellow cmos coin (it's a battery) and putting it back after a minute or -two: - -![](../images/x60_unbrick/0004.jpg) - -*Those dd commands should be applied to all newly compiled X60 ROM +two:\ +![](../images/x60_unbrick/0004.jpg)\ +\ +\*Those dd commands should be applied to all newly compiled X60 ROM images (the ROM images in libreboot binary archives already have this -applied!): - +applied!):\ dd if=coreboot.rom of=top64k.bin bs=1 skip=\$\[\$(stat -c %s -coreboot.rom) - 0x10000\] count=64k - +coreboot.rom) - 0x10000\] count=64k\ dd if=coreboot.rom bs=1 skip=\$\[\$(stat -c %s coreboot.rom) - 0x20000\] -count=64k | hexdump - +count=64k | hexdump\ dd if=top64k.bin of=coreboot.rom bs=1 seek=\$\[\$(stat -c %s -coreboot.rom) - 0x20000\] count=64k conv=notrunc - +coreboot.rom) - 0x20000\] count=64k conv=notrunc\ (doing this makes the ROM suitable for use when flashing a system that still has Lenovo BIOS running, using those instructions: . + + bad rom (or user error), system won't boot {#recovery} =========================================== @@ -57,86 +60,68 @@ you can't boot the system, making this difficult. In this situation, external hardware (see hardware requirements above) is needed which can flash the SPI chip (where libreboot resides). -Remove those screws: - +Remove those screws:\ ![](../images/x60_unbrick/0000.jpg) -Push the keyboard forward (carefully): - +Push the keyboard forward (carefully):\ ![](../images/x60_unbrick/0001.jpg) -Lift the keyboard up and disconnect it from the board: - +Lift the keyboard up and disconnect it from the board:\ ![](../images/x60_unbrick/0002.jpg) Grab the right-hand side of the chassis and force it off (gently) and -pry up the rest of the chassis: - +pry up the rest of the chassis:\ ![](../images/x60_unbrick/0003.jpg) -You should now have this: - +You should now have this:\ ![](../images/x60_unbrick/0004.jpg) -Disconnect the wifi antenna cables, the modem cable and the speaker: - +Disconnect the wifi antenna cables, the modem cable and the speaker:\ ![](../images/x60_unbrick/0005.jpg) Unroute the cables along their path, carefully lifting the tape that holds them in place. Then, disconnect the modem cable (other end) and power connection and unroute all the cables so that they dangle by the -monitor hinge on the right-hand side: - +monitor hinge on the right-hand side:\ ![](../images/x60_unbrick/0006.jpg) Disconnect the monitor from the motherboard, and unroute the grey -antenna cable, carefully lifting the tape that holds it into place: - +antenna cable, carefully lifting the tape that holds it into place:\ ![](../images/x60_unbrick/0008.jpg) Carefully lift the remaining tape and unroute the left antenna cable so -that it is loose: - +that it is loose:\ ![](../images/x60_unbrick/0009.jpg) Remove the screw that is highlighted (do NOT remove the other one; it -holds part of the heatsink (other side) into place): - +holds part of the heatsink (other side) into place):\ ![](../images/x60_unbrick/0011.jpg) -Remove those screws: - +Remove those screws:\ ![](../images/x60_unbrick/0012.jpg) -Carefully remove the plate, like so: - +Carefully remove the plate, like so:\ ![](../images/x60_unbrick/0013.jpg) -Remove the SATA connector: - +Remove the SATA connector:\ ![](../images/x60_unbrick/0014.jpg) -Now remove the motherboard (gently) and cast the lcd/chassis aside: - +Now remove the motherboard (gently) and cast the lcd/chassis aside:\ ![](../images/x60_unbrick/0015.jpg) Lift back that tape and hold it with something. Highlighted is the SPI -flash chip: - +flash chip:\ ![](../images/x60_unbrick/0016.jpg) -Now wire up the BBB and the Pomona with your PSU. - +Now wire up the BBB and the Pomona with your PSU.\ Refer to [bbb\_setup.html](bbb_setup.html) for how to setup the BBB for -flashing. - +flashing.\ **Note, the guide mentions a 3.3v DC PSU but you don't need this on the X60: if you don't have or don't want to use an external PSU, then make sure not to connect the 3.3v leads mentioned in the guide; instead, connect the AC adapter (the one that normally charges your battery) so that the board has power (but don't boot it up)** -![](../images/x60_unbrick/0017.jpg) - +![](../images/x60_unbrick/0017.jpg)\ Correlate the following with the BBB guide linked above: POMONA 5250: @@ -149,122 +134,98 @@ Correlate the following with the BBB guide linked above: This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack. Connecting the BBB and pomona (in this image, an external 3.3v DC PSU -was used): - +was used):\ ![](images/x60/th_bbb_flashing.jpg) Flashrom binaries for ARM (tested on a BBB) are distributed in libreboot\_util. Alternatively, libreboot also distributes flashrom source code which can be built. -SSH'd into the BBB: - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w +SSH'd into the BBB:\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w yourrom.rom** -It should be **Verifying flash... VERIFIED** at the end. If flashrom +It should be **Verifying flash\... VERIFIED** at the end. If flashrom complains about multiple flash chip definitions detected, then choose one of them following the instructions in the output. Remove the programmer and put it away somewhere. Put back the tape and -press firmly over it: - +press firmly over it:\ ![](../images/x60_unbrick/0026.jpg) -Your empty chassis: - +Your empty chassis:\ ![](../images/x60_unbrick/0027.jpg) -Put the motherboard back in: - +Put the motherboard back in:\ ![](../images/x60_unbrick/0028.jpg) -Reconnect SATA: - +Reconnect SATA:\ ![](../images/x60_unbrick/0029.jpg) -Put the plate back and re-insert those screws: - +Put the plate back and re-insert those screws:\ ![](../images/x60_unbrick/0030.jpg) -Re-route that antenna cable around the fan and apply the tape: - +Re-route that antenna cable around the fan and apply the tape:\ ![](../images/x60_unbrick/0031.jpg) Route the cable here and then (not shown, due to error on my part) reconnect the monitor cable to the motherboard and re-insert the -screws: - +screws:\ ![](../images/x60_unbrick/0032.jpg) -Re-insert that screw: - +Re-insert that screw:\ ![](../images/x60_unbrick/0033.jpg) -Route the black antenna cable like so: - +Route the black antenna cable like so:\ ![](../images/x60_unbrick/0034.jpg) -Tuck it in neatly like so: - +Tuck it in neatly like so:\ ![](../images/x60_unbrick/0035.jpg) -Route the modem cable like so: - +Route the modem cable like so:\ ![](../images/x60_unbrick/0036.jpg) -Connect modem cable to board and tuck it in neatly like so: - +Connect modem cable to board and tuck it in neatly like so:\ ![](../images/x60_unbrick/0037.jpg) -Route the power connection and connect it to the board like so: - +Route the power connection and connect it to the board like so:\ ![](../images/x60_unbrick/0038.jpg) -Route the antenna and modem cables neatly like so: - +Route the antenna and modem cables neatly like so:\ ![](../images/x60_unbrick/0039.jpg) Connect the wifi antenna cables. At the start of the tutorial, this system had an Intel wifi chip. Here you see I've replaced it with an -Atheros AR5B95 (supports 802.11n and can be used without blobs): - +Atheros AR5B95 (supports 802.11n and can be used without blobs):\ ![](../images/x60_unbrick/0040.jpg) -Connect the modem cable: - +Connect the modem cable:\ ![](../images/x60_unbrick/0041.jpg) -Connect the speaker: - +Connect the speaker:\ ![](../images/x60_unbrick/0042.jpg) -You should now have this: - +You should now have this:\ ![](../images/x60_unbrick/0043.jpg) -Re-connect the upper chassis: - +Re-connect the upper chassis:\ ![](../images/x60_unbrick/0044.jpg) -Re-connect the keyboard: - +Re-connect the keyboard:\ ![](../images/x60_unbrick/0045.jpg) -Re-insert the screws that you removed earlier: - +Re-insert the screws that you removed earlier:\ ![](../images/x60_unbrick/0046.jpg) -Power on! - +Power on!\ ![](../images/x60_unbrick/0047.jpg) -Operating system: - +Operating system:\ ![](../images/x60_unbrick/0049.jpg) -Copyright © 2014, 2015 Leah Rowe + +Copyright © 2014, 2015 Leah Rowe \ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/install/x60tablet_unbrick.md b/docs/install/x60tablet_unbrick.md index c683e3ce..b91438a1 100644 --- a/docs/install/x60tablet_unbrick.md +++ b/docs/install/x60tablet_unbrick.md @@ -1,10 +1,14 @@ -% ThinkPad X60 Tablet: Recovery guide + +ThinkPad X60 Tablet: Recovery guide +=================================== This section documents how to recover from a bad flash that prevents your ThinkPad X60 Tablet from booting. [Back to previous index](./) + + Table of Contents ----------------- @@ -13,36 +17,35 @@ Table of Contents - [Brick type 2: bad rom (or user error), system won't boot](#recovery) + + Brick type 1: bucts not reset. {#bucts_brick} ============================== You still have Lenovo BIOS, or you had libreboot running and you flashed -another ROM; and you had bucts 1 set and the ROM wasn't dd'd.* or if -Lenovo BIOS was present and libreboot wasn't flashed. - +another ROM; and you had bucts 1 set and the ROM wasn't dd'd.\* or if +Lenovo BIOS was present and libreboot wasn't flashed.\ +\ In this case, unbricking is easy: reset BUC.TS to 0 by removing that yellow cmos coin (it's a battery) and putting it back after a minute or -two: - -![](../images/x60t_unbrick/0008.JPG) - -*Those dd commands should be applied to all newly compiled X60 ROM +two:\ +![](../images/x60t_unbrick/0008.JPG)\ +\ +\*Those dd commands should be applied to all newly compiled X60 ROM images (the ROM images in libreboot binary archives already have this -applied!): - +applied!):\ dd if=coreboot.rom of=top64k.bin bs=1 skip=\$\[\$(stat -c %s -coreboot.rom) - 0x10000\] count=64k - +coreboot.rom) - 0x10000\] count=64k\ dd if=coreboot.rom bs=1 skip=\$\[\$(stat -c %s coreboot.rom) - 0x20000\] -count=64k | hexdump - +count=64k | hexdump\ dd if=top64k.bin of=coreboot.rom bs=1 seek=\$\[\$(stat -c %s -coreboot.rom) - 0x20000\] count=64k conv=notrunc - +coreboot.rom) - 0x20000\] count=64k conv=notrunc\ (doing this makes the ROM suitable for use when flashing a system that still has Lenovo BIOS running, using those instructions: . + + bad rom (or user error), system won't boot {#recovery} =========================================== @@ -59,57 +62,45 @@ flash the SPI chip (where libreboot resides). ![](../images/x60t_unbrick/0000.JPG) -Remove those screws: - +Remove those screws:\ ![](../images/x60t_unbrick/0001.JPG) -Remove the HDD: - +Remove the HDD:\ ![](../images/x60t_unbrick/0002.JPG) -Push keyboard forward to loosen it: - +Push keyboard forward to loosen it:\ ![](../images/x60t_unbrick/0003.JPG) -Lift: - +Lift:\ ![](../images/x60t_unbrick/0004.JPG) -Remove those: - +Remove those:\ ![](../images/x60t_unbrick/0005.JPG) ![](../images/x60t_unbrick/0006.JPG) -Also remove that (marked) and unroute the antenna cables: - +Also remove that (marked) and unroute the antenna cables:\ ![](../images/x60t_unbrick/0007.JPG) -For some X60T laptops, you have to unroute those too: - +For some X60T laptops, you have to unroute those too:\ ![](../images/x60t_unbrick/0010.JPG) Remove the LCD extend board screws. Also remove those screws (see blue -marks) and remove/unroute the cables and remove the metal plate: - +marks) and remove/unroute the cables and remove the metal plate:\ ![](../images/x60t_unbrick/0008.JPG) -Remove that screw and then remove the board: - +Remove that screw and then remove the board:\ ![](../images/x60t_unbrick/0009.JPG) -Now wire up the BBB and the Pomona with your PSU. - +Now wire up the BBB and the Pomona with your PSU.\ Refer to [bbb\_setup.html](bbb_setup.html) for how to setup the BBB for -flashing. - +flashing.\ **Note, the guide mentions a 3.3v DC PSU but you don't need this on the X60 Tablet: if you don't have or don't want to use an external PSU, then make sure not to connect the 3.3v leads mentioned in the guide; instead, connect the AC adapter (the one that normally charges your battery) so that the board has power (but don't boot it up)** -![](../images/x60t_unbrick/0011.JPG) - +![](../images/x60t_unbrick/0011.JPG)\ Correlate the following with the BBB guide linked above: POMONA 5250: @@ -122,27 +113,26 @@ Correlate the following with the BBB guide linked above: This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack. Connecting the BBB and pomona (in this image, an external 3.3v DC PSU -was used): - +was used):\ ![](images/x60/th_bbb_flashing.jpg) Flashrom binaries for ARM (tested on a BBB) are distributed in libreboot\_util. Alternatively, libreboot also distributes flashrom source code which can be built. -SSH'd into the BBB: - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w +SSH'd into the BBB:\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w yourrom.rom** -It should be **Verifying flash... VERIFIED** at the end. If flashrom +It should be **Verifying flash\... VERIFIED** at the end. If flashrom complains about multiple flash chip definitions detected, then choose one of them following the instructions in the output. Reverse the steps to re-assemble your system. -Copyright © 2014, 2015 Leah Rowe + +Copyright © 2014, 2015 Leah Rowe \ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative -- cgit v1.2.3-70-g09d2