summaryrefslogtreecommitdiff
path: root/docs/howtos
diff options
context:
space:
mode:
authorFrancis Rowe <info@gluglug.org.uk>2014-09-12 01:10:55 +0100
committerFrancis Rowe <info@gluglug.org.uk>2014-09-12 01:10:55 +0100
commitaed310ac27c023b575e6ae426c1478a3843d40a5 (patch)
tree6d2c4a7c35f60783a077b782a8212bd905819fca /docs/howtos
parent5336f7615d30383a66c2e6d59df277f1d3aeeff6 (diff)
Documentation: added more troubleshooting information in grub_boot_installer.html
Diffstat (limited to 'docs/howtos')
-rw-r--r--docs/howtos/grub_boot_installer.html16
1 files changed, 16 insertions, 0 deletions
diff --git a/docs/howtos/grub_boot_installer.html b/docs/howtos/grub_boot_installer.html
index 38a4795..9cd05ac 100644
--- a/docs/howtos/grub_boot_installer.html
+++ b/docs/howtos/grub_boot_installer.html
@@ -65,6 +65,22 @@
<h1>Troubleshooting</h1>
+ <p>
+ Most of these issues occur when using libreboot with coreboot's 'text mode' instead of the coreboot framebuffer.
+ This mode is useful for booting payloads like memtest86+ which expect text-mode, but for GNU/Linux distributions
+ it can be problematic when they are trying to switch to a framebuffer because it doesn't exist.
+ </p>
+
+ <p>
+ In most cases, you should use the vesafb ROM's. Example filename: libreboot_ukdvorak_vesafb.rom.
+ </p>
+
+ <h2>parabola won't boot in text-mode</h2>
+
+ <p>
+ Use one of the ROM images with vesafb in the filename (uses coreboot framebuffer instead of text-mode).
+ </p>
+
<h2>debian-installer (trisquel net install) graphical corruption in text-mode</h2>
<p>
When using the ROM images that use coreboot's &quot;text mode&quot; instead of the coreboot framebuffer,