diff options
authorintrigeri <>2015-05-07 14:59:10 +0000
committerintrigeri <>2015-05-07 14:59:10 +0000
commit16ccead6a4591adbfb5ed285cbf55bc21a4f4eef (patch)
parent040d19f1592e0c9566723dce6b1e8695bb929121 (diff)
Add 32-bit UEFI status report.
1 files changed, 33 insertions, 0 deletions
diff --git a/wiki/src/blueprint/UEFI/32-bit.mdwn b/wiki/src/blueprint/UEFI/32-bit.mdwn
index 1f24e36..d88637e 100644
--- a/wiki/src/blueprint/UEFI/32-bit.mdwn
+++ b/wiki/src/blueprint/UEFI/32-bit.mdwn
@@ -37,6 +37,39 @@ What we know so far:
supporting this feature, chances are that most such machines are
dead anyway.
+Test results and ideas
+### 32-bit GRUB2 EFI chainloading 32-bit syslinux EFI
+* syslinux 32-bit EFI installed in `EFI/TAILS32`
+* GRUB 32-bit EFI installed in `EFI/BOOT/bootia32.efi`
+=> did not manage to chainload 32-bit syslinux EFI from GRUB.
+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 its support to read 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
+Not tried loading `syslinux.cfg` yet. Note that:
+* Support for `{vesa,}menu.c32` was added in GRUB upstream, but didn't
+ make it into Debian yet.
+* We'll need to load the `cpuid` module to make our `ifcpu64`
+ directives work.
+### 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
+automatically or by hand.
<a id="hardware"></a>
Potential hardware