diff options
Diffstat (limited to 'docs/install')
| -rw-r--r-- | docs/install/index.md | 26 | ||||
| -rw-r--r-- | docs/install/rpi_setup.md | 2 | ||||
| -rw-r--r-- | docs/install/t500_external.md | 7 |
3 files changed, 19 insertions, 16 deletions
diff --git a/docs/install/index.md b/docs/install/index.md index d4ac2f13..b54dca15 100644 --- a/docs/install/index.md +++ b/docs/install/index.md @@ -62,10 +62,12 @@ they don't have to build anything from source on their own. The ROM images in each archive use the following at the end of the file name, if they are built with the GRUB payload: `*_*keymap*_*mode*.rom` -Available `modes`: `vesafb` or `txtmode`. The `vesafb` ROM images -are recommended, in most cases; `txtmode` ROM images come with -MemTest86+, which requires text-mode instead of the usual framebuffer -used by coreboot native graphics initialization. +Available modes: vesafb or txtmode. The vesafb ROM images are recommended +for regular use, but when flashing for the first time use txtmode version, +as it comes with Memtest86+, which requires text-mode instead of the usual +framebuffer used by coreboot native graphics initialization. +Machine should be tested with Memtest86+ after each reassembly or changing +from vendor bios to libreboot due to differences in raminit code. `keymap` can be one of several keymaps that keyboard supports (there are quite a few), which affects the keyboard layout configuration that is @@ -169,7 +171,7 @@ ASUS KCMA-D8? ------------- If you have the proprietary BIOS, you need to flash libreboot -externally. See [kcma-d8.md](kgpe-d8.md). +externally. See [kcma-d8.md](kcma-d8.md). If you already have coreboot or libreboot installed, without write protection on the flash chip, then you can do it in software (otherwise, @@ -244,7 +246,7 @@ Flash chip size Use this to find out: - # flashrom -p internal -V + # flashrom -p internal All good? --------- @@ -264,13 +266,13 @@ executables from the libreboot source code archives. How to update the flash chip contents: -`$ sudo ./flash update `[`yourrom.rom`](#rom) +`$ 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: - `$ sudo ./flash forceupdate `[`yourrom.rom`](#rom) + `$ sudo ./flash forceupdate `[`yourrom.rom`](#rom) You should see `Verifying flash... VERIFIED.` written at the end of the flashrom output. *Shut down* after you see this, and then boot @@ -305,7 +307,7 @@ the flashing script. do this: * The first half of the procedure is as follows: -`$ sudo ./flash i945lenovo_firstflash `[`yourrom.rom`](#rom) +`$ sudo ./flash i945lenovo_firstflash `[`yourrom.rom`](#rom) You should see within the output the following: @@ -332,11 +334,11 @@ needed (see below). When you have booted up again, you must also do this: -`$ sudo ./flash i945lenovo_secondflash `[`yourrom.rom`](#rom) +`$ 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) +`$ sudo ./flashrom/i686/flashrom -p internal:laptop=force_I_want_a_brick -w `[`yourrom.rom`](#rom) You should see within the output the following: @@ -372,7 +374,7 @@ with your device. Use this flashing script, to install libreboot: -`$ sudo ./flash i945apple_firstflash `[`yourrom.rom`](#rom) +`$ sudo ./flash i945apple_firstflash `[`yourrom.rom`](#rom) You should also see within the output the following: diff --git a/docs/install/rpi_setup.md b/docs/install/rpi_setup.md index e46191e7..b083aac9 100644 --- a/docs/install/rpi_setup.md +++ b/docs/install/rpi_setup.md @@ -150,7 +150,7 @@ successfully. If not, just flash again. Pi](http://scruss.com/blog/2013/02/02/simple-adc-with-the-raspberry-pi/) - [Flashing coreboot on a T60 with a Raspberry Pi - the\_unconventional's - blog](https://blogs.fsfe.org/the_unconventional/2015/05/08/flashing-coreboot-on-a-t60-with-a-raspberry-pi/) + blog](https://web.archive.org/web/20150709043222/http://blogs.fsfe.org:80/the_unconventional/2015/05/08/coreboot-t60-raspberry-pi/) - *Pomona SOIC Clip flashing* - [Arch Linux Wiki - Installing Arch Linux on Chromebook](https://wiki.archlinux.org/index.php/Chromebook) diff --git a/docs/install/t500_external.md b/docs/install/t500_external.md index c9b85a5d..9e114bca 100644 --- a/docs/install/t500_external.md +++ b/docs/install/t500_external.md @@ -362,11 +362,12 @@ Not to be confused with wifi (wifi is fine). Memory ====== -You need DDR3 SODIMM PC3-8500 RAM installed, in matching pairs -(speed/size). Non-matching pairs won't work. You can also install a +DDR3 SO-DIMM sticks will work at PC3-8500 clock and voltage, so make sure that +timings of sticks are matched while they operate at its frequency. +Non-matching pairs won't work. You can also install a single module (meaning, one of the slots will be empty) in slot 0. -Make sure that the RAM you buy is the 2Rx8 density. +Make sure that the RAM you buy has 2Rx8 arrangement when buying 4GiB modules. [This page](http://www.forum.thinkpads.com/viewtopic.php?p=760721) might be useful for RAM compatibility info (note: coreboot raminit is |