Bug #16229

Boot Loader Menu documentation does not support 32-bit UEFI

Added by intrigeri 2018-12-17 12:29:42 . Updated 2020-04-06 21:54:34 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Hardware support
Target version:
Start date:
2018-12-17
Due date:
% Done:

0%

Feature Branch:
Type of work:
End-user documentation
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

https://tails.boum.org/doc/first_steps/startup_options/#boot_menu assumes syslinux, which is correct on all platforms but 64-bit computers with a 32-bit UEFI firmware (that we started supporting a couple years ago; e.g. cheap netbooks, tablets and so on) where the user will instead see a GRUB menu. FTR, there one needs to press “e” instead of TAB, edit the correct line and finally press F10 or CTRL+x to boot.

FTR, I’ve just learned that some Thinkpad X200 + Libreboot also end up in the 32-bit GRUB UEFI bootloader menu.

I’ll let you judge whether better supporting this (probably tiny) part of our user base is worth making this doc more complicated to follow for everybody else.


Subtasks


Related issues

Blocks Tails - Feature #17247: Core work 2020Q1 → 2020Q2: Technical writing Confirmed

History

#1 Updated by sajolida 2018-12-18 17:56:17

I’ve also seen the GRUB menu on several regular laptops I think.

I ignored this so far because I thought that the difference was only aesthetic.

But indeed, if people have to press “e” and “Ctrl+X” it’s important to document.

#2 Updated by sajolida 2018-12-18 17:56:33

  • blocks Feature #15941: Core work 2018Q4 → 2019Q2: Technical writing added

#3 Updated by intrigeri 2019-04-11 13:50:20

  • related to Feature #15806: Use GRUB for USB boot on EFI 64-bit added

#4 Updated by intrigeri 2019-04-11 13:56:26

Note that with Feature #15806 (needed for Feature #6560), the GRUB UI will become the default for 64-bit EFI boot too, which is probably the most common kind of configuration Tails runs on these days; syslinux will remain for legacy BIOS and DVD boot though. So the work done here is a worthwhile investment.

Also, it would be awesome if you could take a quick look this month at the GRUB UI to add boot options and tell us, with your UX hat on, how much worse it is than the syslinux one: if it’s too big a regression, we need to budget time on Feature #15806 to improve the UX of our GRUB menu (which will require both UX + design work and coding work), which can significantly impact the total cost of the Secure Boot project.

#5 Updated by sajolida 2019-04-17 13:54:07

On my Mac I see a Boot Loader Menu on a plain gray background and without a Tails logo. Isn’t this GRUB?

There I can do “Tab” and “Enter” like in syslinux so I’m confused.

@intriger: How can I test the GRUB menu?

#6 Updated by intrigeri 2019-04-17 14:01:57

> On my Mac I see a Boot Loader Menu on a plain gray background and without a Tails logo. Isn’t this GRUB?

No, that’s syslinux UEFI 64-bit.

> intrigeri: How can I test the GRUB menu?

Given you have no UEFI 32-bit hardware handy I think you have two options:

  • Basically, any Debian system with GRUB (currently our GRUB menu is not more fancy than that: it has 2 entries just like our syslinux menu, and tells the user to press some keybinding to edit the currently selected boot option, after which one needs to press F10 or CTRL-x IIRC to boot the system).
  • A build from the wip/bugfix/12146-syslinux-fixes+uefi branch. I could have Jenkins build one for you if the previous option is not satisfying.

#7 Updated by sajolida 2019-05-03 12:24:40

In the GRUB of my Debian, I see very nice inline help at the bottom of the screen: on the 1st screen to instruct me to press ‘e’ to edit and on the 2nd screen to instruct me to press Ctrl-x to boot.

Another thing that is more complicated than with syslinux is the fact that GRUB have many more lines. The line with the boot options is label ‘linux’ and you have to navigate to it.

But yeah, given how rarely these options should be used, the UX of GRUB is fine.

Next steps are to:

#8 Updated by intrigeri 2019-05-03 14:21:15

> But yeah, given how rarely these options should be used, the UX of GRUB is fine.

Thanks!

#9 Updated by sajolida 2019-07-18 16:56:06

  • blocks Feature #16711: Core work 2019Q3 → 2019Q4: Technical writing added

#10 Updated by sajolida 2019-07-18 16:56:09

  • blocked by deleted (Feature #15941: Core work 2018Q4 → 2019Q2: Technical writing)

#11 Updated by sajolida 2019-10-03 20:53:36

  • Assignee deleted (sajolida)

#12 Updated by sajolida 2020-01-05 16:29:16

  • blocks Feature #17247: Core work 2020Q1 → 2020Q2: Technical writing added

#13 Updated by sajolida 2020-01-05 16:29:20

  • blocked by deleted (Feature #16711: Core work 2019Q3 → 2019Q4: Technical writing)

#14 Updated by sajolida 2020-03-21 22:55:09

  • Status changed from Confirmed to In Progress
  • Assignee set to sajolida
  • Target version set to Tails_4.5
  • Parent task set to Feature #15806

I’m working on this as part of Feature #15806.

#15 Updated by sajolida 2020-03-21 23:00:07

#16 Updated by sajolida 2020-03-25 05:13:35

  • Status changed from In Progress to Needs Validation
  • Assignee changed from sajolida to cbrownstein

This is also solved by doc/17492-secure-boot.

#17 Updated by sajolida 2020-04-06 21:54:34

  • Status changed from Needs Validation to Resolved
  • Assignee deleted (cbrownstein)