From a2db4eb3b6a4d4eba09b4a2a014ab17f0b7fa457 Mon Sep 17 00:00:00 2001 From: Francis Rowe Date: Mon, 25 May 2015 14:10:42 -0400 Subject: docs/install/index.html: Update the instructions for updating --- diff --git a/docs/install/index.html b/docs/install/index.html index d082418..3e6af0a 100644 --- a/docs/install/index.html +++ b/docs/install/index.html @@ -79,7 +79,7 @@ by coreboot native graphics initialization.

- Keymaps are named appropriate according to each keyboard layout + Keymaps are named appropriate/y according to each keyboard layout support in GRUB. To learn how these keymaps are created, see ../grub/index.html#grub_keyboard

@@ -107,6 +107,11 @@

Other arguments are available for QEMU. The manual will contain more information.

+ +

+ On GM45 hardware (with libreboot), make sure that the kvm and kvm_intel kernel modules + are not loaded, when using QEMU. +

Back to top of page. @@ -116,7 +121,14 @@

-

How to install or update libreboot (if running libreboot or coreboot)

+

How to update libreboot (if you are already running libreboot or coreboot)

+ +

+ On all current targets, updating libreboot can be accomplished without disassembly and, + therefore, without having to externally re-flash using any dedicated hardware. In other words, + you can do everything entirely in software, directly from the OS that is running on your libreboot + system. +

@@ -125,59 +137,103 @@

- These instructions work for most targets, provided that they are already running libreboot or coreboot. -

-

Look at the list of ROM images to see which image is compatible with your device.

-

- X60/T60 users with Lenovo BIOS should refer to #flashrom_lenovobios instead. - Similary, MacBook2,1 users running Apple EFI should refer to #flashrom_macbook21. -

-

- - ThinkPad T60 and X60 Tablet users: be sure to read ../hcl/index.html#supported_t60_list - or ../hcl/index.html#supported_t60_list. - -

-

- X200/R400/T400/T500 users running Lenovo BIOS should refer to x200_external.html, - r400_external.html, - t400_external.html or - t500_external.html. These machines contain the hard coded - MAC address for the onboard ethernet chipset, directly inside the SPI flash; - ich9gen shows how to change it (the default - libreboot ROM images for these machines contain a generic MAC address). -

-

- X200/R400/T400/T500 users should also note, that it is possible for the user to write-protect whole regions - of the SPI flash by using a modified descriptor. Locked regions must be flashed externally; - see x200_external.html, r400_external.html, - t400_external.html or t500_external.html. - Libreboot unlocks all regions, by default. -

-
+ +

Are you currently running the original, proprietary firmware?

+

- How to update the flash chip contents:
- $ sudo ./flash update yourrom.rom + If you are currently running the proprietary firmware (not libreboot or coreboot), + then the flashing instructions for your system are going to be different.

-
-

- 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:
- $ sudo ./flash forceupdate yourrom.rom + X60/T60 users running the proprietary firmware should refer to #flashrom_lenovobios. + MacBook2,1 users running Apple EFI should refer to #flashrom_macbook21 +

+

+ X200 users, refer to x200_external.html, + R400 users refer to r400_external.html, + T400 users refer to t400_external.html, + T500 users refer to t500_external.html

-
-
+

Are you currently running libreboot (or coreboot)?

+ +

+ X60/T60 users should be fine with this guide. If you write-protected the flash chip, please refer to + x60_unbrick.html, x60tablet_unbrick.html + or t60_unbrick.html. This probably does not apply to you. Most people + do not write-protect the flash chip, so you probably didn't either. +

+

+ Similarly, it is possible to write-protect the flash chip in coreboot or libreboot on GM45 laptops + (X200/R400/T400/T500). If you did this, then you will need to use the links above for flashing, + treating your laptop as though it currently has the proprietary firmware (because write-protected SPI flash + requires external re-flashing, as is also the case when running the proprietary firmware). +

+ +

+ If you did not write-protect the flash chip, or it came to you without any write-protection + (libreboot does not write-protect the flash chip by default, so this probably applies to you), + read on! +

+ +

MAC address on GM45 (X200/R400/T400/T500)

- 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. + Users of the X200/R400/T400/T500 take note: The MAC address for the onboard ethernet chipset + is located inside the flash chip. Libreboot ROM images for these laptops contain a generic MAC + address by default (00:F5:F0:40:71:FE), 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 + show how to do this.

-
+

+ It is important that you change the default MAC address, before flashing. It will be printed on a sticker + at the bottom of the laptop, or it will be printed on a sticker next to or underneath the RAM. Alternatively, + and assuming that your current firmware has the correct MAC address in it, you can get it from your OS. +

+ +

All good?

+ +

Excellent! Moving on...

+ +

+ Download the libreboot_util.tar.xz archive, and extract it. Inside, you will find + a directory called flashrom. This contains statically compiled executable files of + the flashrom utility, which you will use to re-flash your libreboot system. +

+ +

+ Simply use cd on your terminal, to switch to the libreboot_util directory. Inside, + there is a script called flash, which will detect 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:
+ $ sudo ./flash update yourrom.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:
+ $ sudo ./flash forceupdate yourrom.rom +

+
+ +
+ +

+ 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

-- cgit v0.9.1