Difference between revisions of "Talk:Systemd-boot"

From ArchWiki
Jump to: navigation, search
(LTS kernels: new section)
m (Some questions: removed closed discussion)
 
(40 intermediate revisions by 15 users not shown)
Line 1: Line 1:
The link to documentation on freedesktop is currently giving a 503 and providing "guru meditation". Does anybody happen to be a guru and available to meditate on XID: 890648862? --[[User:Margali|cfr]] ([[User talk:Margali|talk]]) 03:22, 24 March 2013 (UTC)
+
== About reboot into firmware configuration interface ==
 +
If I remember correctly, isn't that one of the entries that are auto-generated by gummiboot, along with windows entries? [[User:Moviuro|Moviuro]] ([[User talk:Moviuro|talk]]) 12:41, 15 March 2015 (UTC)
 +
: AFAIK, there aren't any autogenerated default options in the Gummiboot boot manager to reboot into the firmware. I only have the autodetected {{ic|efiboomgr}} entry which appears when Windows is installed and the entries I defined manually. -- [[User:wget|wget]] ([[User talk:wget|talk]]) 13:08, 15 March 2015 (UTC)
 +
: I spent some time googleing about this issue. Without success. So it would save time and pain to add some working example. It's a useful feature. --[[User:Cschlote|Cschlote]] ([[User talk:Cschlote|talk]]) 00:26, 16 March 2015 (UTC)
 +
:: http://wstaw.org/w/3gSV/ And I don't have a Reboot into device firmware entry, nor the EFI default loader [[User:Moviuro|Moviuro]] ([[User talk:Moviuro|talk]]) 22:35, 21 March 2015 (UTC)
 +
::: I already found several real machines, which will either show none of these entries, or just one of them. Only a VM shows all entries. --[[User:Cschlote|Cschlote]] ([[User talk:Cschlote|talk]]) 12:32, 23 March 2015 (UTC)
 +
:::: Well, this picture was taken on my Dell Latitude (E6430). [[User:Moviuro|Moviuro]] ([[User talk:Moviuro|talk]]) 15:28, 23 March 2015 (UTC)
  
== Mount /boot and efivarfs ==
+
== $esp pseudo-var ==
  
Now systemd automatic detect ESP and mount it as {{ic|/boot}}. Also systemd mount {{ic|efivarfs}}. You no longer mount {{ic|/boot}} manually or add entry in the {{ic|/etc/fstab}}. If you try mount {{ic|/boot}} manually or from {{ic|/etc/fstab}} {{ic|gummiboot install}} command will fail.
+
I'd suggest replacing {{ic|$esp}} that's prominent in the article with the standard {{ic|/boot}}, i.e. replace
 +
:{{ic|$esp}} is used to denote the mountpoint in this article.  
 +
with
 +
:In this article, {{ic|/boot}} is used as the mountpoint.
 +
And replace {{ic|$esp}} instances accordingly. Changing the mountpoint is immediate to anyone who wants to do so, so another pseudo-var isn't required.
  
Details:
+
In addition, it's confusing to those who wish to go with the recommended {{ic|/boot}} mountpoint. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 10:33, 5 January 2016 (UTC)
# findmnt /boot
+
TARGET SOURCE    FSTYPE OPTIONS
+
/boot  systemd-1 autofs rw,relatime,fd=36,pgrp=1,timeout=300,minproto=5,maxproto=5,direct
+
+
# findmnt efivarfs
+
TARGET                    SOURCE  FSTYPE  OPTIONS
+
/sys/firmware/efi/efivars efivarfs efivarfs rw,nosuid,nodev,noexec,relatime
+
  
Please add this notes to the Article.
+
:While that could make sense, we'd create an inconsistency with all the other boot loader articles, which do use $esp as well: [[GRUB]], [[Syslinux]], [[EFISTUB]] and [[rEFInd]]. Personally, I don't think that using a variable like that is creating confusion, especially after [https://wiki.archlinux.org/index.php?title=Beginners%27_guide&diff=414434&oldid=414433]. — [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 07:12, 9 January 2016 (UTC)
  
[[User:Unikum|Unikum]] ([[User talk:Unikum|talk]]) 05:44, 20 April 2013 (UTC)
+
== Keys inside the boot menu, clarification ==
: ". If you try mount /boot manually or from /etc/fstab gummiboot install command will fail." That's just not true, gummiboot install should work fine either way. What kind of error message is this supposed to cause?
+
:Either way, I don't really like adding a note about the ESP automount yet for several reasons:
+
: * the fsck is missing in the generated mount unit (this is on systemd's TODO list)
+
: * it mounts /boot with 0700 permissions. Not sure if this is intended by upstream, but it is annoying and causes warnings from pacman.
+
: * this feature isn't even documented in systemd yet
+
: * This is a systemd feature, gummiboot just happens to be the only bootloader to export the EFI variables needed for this (for now). So it's probably debatable whether to put this on the systemd wiki or the gummiboot wiki.
+
: [[User:65kid|65kid]] ([[User talk:65kid|talk]]) 07:51, 20 April 2013 (UTC)
+
:: Thanks for the explanation.
+
:: [[User:Unikum|Unikum]] ([[User talk:Unikum|talk]]) 11:54, 20 April 2013 (UTC)
+
  
== LTS kernels ==
+
once you use keys to change timeout (-,T,+,t), this setting is saved in a non-volatile EFI variable;
 
+
in this way `loader.conf` setting is overridden; a) how to clear the non-volatile EFI variable? b) how to show values of non-volatile EFI variables? --[[User:NTia89|nTia89]] ([[User talk:NTia89|talk]]) 14:22, 27 May 2016 (UTC)
Although not strictly false, I think the page is a bit misleading because somebody might well think that gummiboot can boot the LTS kernel provided only that you add the EFI menu entry manually. But as far as I know the LTS kernels cannot be booted this way because they lack the stub loader. Obviously that doesn't mean you can't install gummiboot to do something else (boot another kernel, boot a boot loader etc.) but it is a bit odd the way it is put? --[[User:Margali|cfr]] ([[User talk:Margali|talk]]) 23:41, 23 July 2013 (UTC)
+

Latest revision as of 11:13, 4 June 2016

About reboot into firmware configuration interface

If I remember correctly, isn't that one of the entries that are auto-generated by gummiboot, along with windows entries? Moviuro (talk) 12:41, 15 March 2015 (UTC)

AFAIK, there aren't any autogenerated default options in the Gummiboot boot manager to reboot into the firmware. I only have the autodetected efiboomgr entry which appears when Windows is installed and the entries I defined manually. -- wget (talk) 13:08, 15 March 2015 (UTC)
I spent some time googleing about this issue. Without success. So it would save time and pain to add some working example. It's a useful feature. --Cschlote (talk) 00:26, 16 March 2015 (UTC)
http://wstaw.org/w/3gSV/ And I don't have a Reboot into device firmware entry, nor the EFI default loader Moviuro (talk) 22:35, 21 March 2015 (UTC)
I already found several real machines, which will either show none of these entries, or just one of them. Only a VM shows all entries. --Cschlote (talk) 12:32, 23 March 2015 (UTC)
Well, this picture was taken on my Dell Latitude (E6430). Moviuro (talk) 15:28, 23 March 2015 (UTC)

$esp pseudo-var

I'd suggest replacing $esp that's prominent in the article with the standard /boot, i.e. replace

$esp is used to denote the mountpoint in this article.

with

In this article, /boot is used as the mountpoint.

And replace $esp instances accordingly. Changing the mountpoint is immediate to anyone who wants to do so, so another pseudo-var isn't required.

In addition, it's confusing to those who wish to go with the recommended /boot mountpoint. -- Alad (talk) 10:33, 5 January 2016 (UTC)

While that could make sense, we'd create an inconsistency with all the other boot loader articles, which do use $esp as well: GRUB, Syslinux, EFISTUB and rEFInd. Personally, I don't think that using a variable like that is creating confusion, especially after [1]. — Kynikos (talk) 07:12, 9 January 2016 (UTC)

Keys inside the boot menu, clarification

once you use keys to change timeout (-,T,+,t), this setting is saved in a non-volatile EFI variable; in this way `loader.conf` setting is overridden; a) how to clear the non-volatile EFI variable? b) how to show values of non-volatile EFI variables? --nTia89 (talk) 14:22, 27 May 2016 (UTC)