diff options
authorintrigeri <>2015-05-08 15:17:25 +0000
committerintrigeri <>2015-05-08 15:17:25 +0000
commitb6e85a4e7c03f2ce479653c7d24a598708e286ea (patch)
parent7966ff108dba6cb72911178b96b5d847a1587243 (diff)
Update the 32-bit UEFI status.
1 files changed, 12 insertions, 9 deletions
diff --git a/wiki/src/blueprint/UEFI/32-bit.mdwn b/wiki/src/blueprint/UEFI/32-bit.mdwn
index ad0fc66..56af8a3 100644
--- a/wiki/src/blueprint/UEFI/32-bit.mdwn
+++ b/wiki/src/blueprint/UEFI/32-bit.mdwn
@@ -50,18 +50,18 @@ On Tails/Jessie (GRUB 2.02~beta2-22), I get `error: unknown error.`
after typing `boot`. This likely comes from
-### 32-bit GRUB2 EFI using reading the syslinux configuration
+### 32-bit GRUB2 EFI reading the syslinux configuration at runtime
-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`, `linux16` and
-`syslinuxcfg` GRUB modules, one can boot Tails with `syslinux_configfile
+With current `feature/8471-32-bit-UEFI`, one can choose the *syslinux:
+liveamd64.cfg* menu entry, that basically load syslinux'
+`/efi/boot/liveamd64.cfg`, converting it to GRUB on the fly.
-Not tried loading `syslinux.cfg` yet. Note that:
+Then, add `nomodeset` if needed, and Tails boots.
+Note that:
* Support for `{vesa,}menu.c32` was added in GRUB upstream, but didn't
- make it into Debian yet.
+ make it into Debian yet as of 2.02~beta2-22.
* We'll need to load the `cpuid` module to make our `ifcpu64`
directives work.
@@ -69,7 +69,10 @@ Not tried loading `syslinux.cfg` yet. Note that:
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.
+automatically (e.g. with `grub-syslinux2cfg`) or by hand.
+That's what `feature/8471-32-bit-UEFI` currently does, as a way to
+quickly get things going.
<a id="hardware"></a>