summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorintrigeri <intrigeri@boum.org>2015-05-07 20:43:00 +0000
committerintrigeri <intrigeri@boum.org>2015-05-07 20:43:00 +0000
commit0d12c375ab2d07fc5643ac72f56f5cdcae421700 (patch)
tree75bfb6f026d71742f6b1e2fc31b4cec81609de14
parent2b243aa224530ead78b4493d3d0281e6ec53a857 (diff)
More 32-bit EFI GRUB data.
-rw-r--r--wiki/src/blueprint/UEFI/32-bit.mdwn9
1 files changed, 5 insertions, 4 deletions
diff --git a/wiki/src/blueprint/UEFI/32-bit.mdwn b/wiki/src/blueprint/UEFI/32-bit.mdwn
index d88637e..ad0fc66 100644
--- a/wiki/src/blueprint/UEFI/32-bit.mdwn
+++ b/wiki/src/blueprint/UEFI/32-bit.mdwn
@@ -50,12 +50,12 @@ On Tails/Jessie (GRUB 2.02~beta2-22), I get `error: unknown error.`
after typing `boot`. This likely comes from
`grub-core/loader/efi/chainloader.c`.
-### 32-bit GRUB2 EFI using its support to read syslinux configuration
+### 32-bit GRUB2 EFI using reading the syslinux configuration
Are all the syslinux configuration directives we use supported?
Apparently, at least `cpuid` isn't. `liveamd64.cfg` loads fine and
-displays a menu. After loading the `all_video`, `test`, `linux` and
-`linux16` GRUB modules, one can boot Tails with `syslinux_configfile
+displays a menu. After loading the `all_video`, `test`, `linux16` and
+`syslinuxcfg` GRUB modules, one can boot Tails with `syslinux_configfile
/efi/tails32/liveamd64.cfg`.
Not tried loading `syslinux.cfg` yet. Note that:
@@ -67,7 +67,8 @@ Not tried loading `syslinux.cfg` yet. Note that:
### 32-bit GRUB2 EFI with native configuration
-If `syslinux_configfile` is not good enough, Should not be too hard to write/generate and maintain, either
+If `syslinux_configfile` is not good enough, should not be too hard to
+write/generate and maintain a GRUB2 configuration, either
automatically or by hand.
<a id="hardware"></a>