From aed310ac27c023b575e6ae426c1478a3843d40a5 Mon Sep 17 00:00:00 2001 From: Francis Rowe Date: Thu, 11 Sep 2014 20:10:55 -0400 Subject: Documentation: added more troubleshooting information in grub_boot_installer.html --- (limited to 'docs/howtos/grub_boot_installer.html') 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 @@

Troubleshooting

+

+ 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. +

+ +

+ In most cases, you should use the vesafb ROM's. Example filename: libreboot_ukdvorak_vesafb.rom. +

+ +

parabola won't boot in text-mode

+ +

+ Use one of the ROM images with vesafb in the filename (uses coreboot framebuffer instead of text-mode). +

+

debian-installer (trisquel net install) graphical corruption in text-mode

When using the ROM images that use coreboot's "text mode" instead of the coreboot framebuffer, -- cgit v0.9.1