aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorSebastian 'Swift Geek' Grzywna <swiftgeek@gmail.com>2018-06-24 08:04:36 +0200
committerSebastian 'Swift Geek' Grzywna <swiftgeek@gmail.com>2018-06-24 08:04:36 +0200
commit608c4e066dd3722269747fc61d238f1513e9237a (patch)
treedceb7b4fc53ee0e5d16c002b4291efefb2e8a117 /docs
parent57965e5ea62232fe0f0e7123ddf0d2b563718c48 (diff)
downloadlibrebootfr-608c4e066dd3722269747fc61d238f1513e9237a.tar.gz
librebootfr-608c4e066dd3722269747fc61d238f1513e9237a.zip
Clarify memtest86+ section
Diffstat (limited to 'docs')
-rw-r--r--docs/install/index.md10
1 files changed, 6 insertions, 4 deletions
diff --git a/docs/install/index.md b/docs/install/index.md
index d4ac2f13..677fd244 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