On Wednesday, 2 October 2019 10:04:33 BST Mick wrote:
> On Tue, 1 Oct 2019 at 22:38, Peter Humphrey wrote:
> OK, 'bootctl --help' and 'man bootctl' ought to show if the installed
> version comes with the full list of options or not.
Neither of them says what should happen if an option is not sup
On Tue, 1 Oct 2019 at 22:38, Peter Humphrey wrote:
>
> On Tuesday, 1 October 2019 18:47:25 BST Mick wrote:
>
> > As I understand it this ID must be the ID bootctl itself reports.
> > However, earlier bootctl versions do not have this set-default ID
> > subcommand. If you run bootctl with no argum
On Tuesday, 1 October 2019 18:47:25 BST Mick wrote:
> As I understand it this ID must be the ID bootctl itself reports.
> However, earlier bootctl versions do not have this set-default ID
> subcommand. If you run bootctl with no arguments does it show up?
No, it behaves the same as 'bootctl stat
On Tue, 1 Oct 2019 at 16:19, Peter Humphrey wrote:
>
> On Tuesday, 1 October 2019 15:32:27 BST Mick wrote:
> > On Tue, 1 Oct 2019 at 13:18, Mick wrote:
> > > When using Secure Boot the UEFI firmware check the binaries to be
> > > loaded have been signed by Microsoft. The 'SHA256 verified' messag
On Tuesday, 1 October 2019 15:32:27 BST Mick wrote:
> On Tue, 1 Oct 2019 at 13:18, Mick wrote:
> > When using Secure Boot the UEFI firmware check the binaries to be
> > loaded have been signed by Microsoft. The 'SHA256 verified' message
> > indicates the systemd-boot binary is signed using a key
On Tue, 1 Oct 2019 at 13:18, Mick wrote:
> When using Secure Boot the UEFI firmware check the binaries to be
> loaded have been signed by Microsoft. The 'SHA256 verified' message
> indicates the systemd-boot binary is signed using a key which is
> ultimately signed by Microsoft and is contained
On Tue, 1 Oct 2019 at 12:01, Peter Humphrey wrote:
>
> On Tuesday, 1 October 2019 10:47:59 BST Neil Bothwick wrote:
> > On Tue, 01 Oct 2019 10:05:23 +0100, Peter Humphrey wrote:
> > > > Are you setting UEFI to boot from systemd-bootx64.efi or from the
> > > > kernel image? If the former, you don't
On Tuesday, 1 October 2019 10:47:59 BST Neil Bothwick wrote:
> On Tue, 01 Oct 2019 10:05:23 +0100, Peter Humphrey wrote:
> > > Are you setting UEFI to boot from systemd-bootx64.efi or from the
> > > kernel image? If the former, you don't need a copy of the kernel in
> > > the ESP.
> >
> > I could
On Tue, 01 Oct 2019 10:05:23 +0100, Peter Humphrey wrote:
> > Are you setting UEFI to boot from systemd-bootx64.efi or from the
> > kernel image? If the former, you don't need a copy of the kernel in
> > the ESP.
>
> I could run some tests to find out, but after throwing so much time and
> effo
On Monday, 30 September 2019 21:01:28 BST Neil Bothwick wrote:
> Are you setting UEFI to boot from systemd-bootx64.efi or from the kernel
> image? If the former, you don't need a copy of the kernel in the ESP.
I could run some tests to find out, but after throwing so much time and effort
into re
On Mon, 30 Sep 2019 10:02:58 +0100, Mick wrote:
> > The loader files are analogous to grub.cfg, but a thousand times
> > simpler (I may be understating that in my desire to avoid hyperbole).
> > For example, loader.conf here is
> >
> > timeout 3
> > default 00-*
> >
> > This never needs to be modi
On Mon, 30 Sep 2019 11:06:17 +0100, Peter Humphrey wrote:
> This morning I decided to bend with the wind. I let bootctl create
> those directories again, then copied the latest kernel image into
> /boot/EFI/Linux/. On running bootctl install again, everything worked
> as expected. All I had to do
On Tuesday, 24 September 2019 09:50:44 BST Peter Humphrey wrote:
> Right. After spending most of the last 10 days and some nights wrestling
> with the beast, I've got it fixed at last.
Except that I was wrong: I hadn't fixed it. I've just spent another two days
with an unbootable system finding
On Sun, 29 Sep 2019 at 13:25, Neil Bothwick wrote:
>
> On Sun, 29 Sep 2019 11:59:00 +0100, Mick wrote:
>
> > As I understand it, 'bootctl --update' can be used to update
> > systemd-boot boot manager's menu and it is looking for bootable
> > kernels by scanning /efi, /boot, and /boot/efi, or the d
On Sun, 29 Sep 2019 11:59:00 +0100, Mick wrote:
> As I understand it, 'bootctl --update' can be used to update
> systemd-boot boot manager's menu and it is looking for bootable
> kernels by scanning /efi, /boot, and /boot/efi, or the directory set
> by passing the '--path' option to it. Manual ad
On Fri, 27 Sep 2019 at 09:13, Peter Humphrey wrote:
>
> On Thursday, 26 September 2019 16:44:10 BST Mick wrote:
> > On Thu, 26 Sep 2019 at 15:47, Peter Humphrey wrote:
> > > On Thursday, 26 September 2019 10:16:54 BST Adam Carter wrote:
>
> [Snip interesting stuff]
>
> > > > I got the impression
On Thursday, 26 September 2019 16:44:10 BST Mick wrote:
> On Thu, 26 Sep 2019 at 15:47, Peter Humphrey wrote:
> > On Thursday, 26 September 2019 10:16:54 BST Adam Carter wrote:
[Snip interesting stuff]
> > > I got the impression that I would be able to UEFI boot from multiple
> > > different dev
On Thu, 26 Sep 2019 at 15:47, Peter Humphrey wrote:
>
> On Thursday, 26 September 2019 10:16:54 BST Adam Carter wrote:
> > > > The Gentoo Handbook says to create a small unformatted partition at the
> > > > beginning of the (primary?) disk, then to create a FAT-32 partition for
> > > > /boot, then
On Thursday, 26 September 2019 10:16:54 BST Adam Carter wrote:
> > > The Gentoo Handbook says to create a small unformatted partition at the
> > > beginning of the (primary?) disk, then to create a FAT-32 partition for
> > > /boot, then whatever other partitions are required.
> >
> > Another quest
>
> I got the impression that I would be able to UEFI boot from multiple
> different devices, eg a USB drive with UEFI as well as the hard disk.
>
FYI, after rebooting with the USB drive in;
# efibootmgr
BootCurrent:
Timeout: 1 seconds
BootOrder: ,0004,0001,0003,0002
Boot* Gentoo <-
>
> > The Gentoo Handbook says to create a small unformatted partition at the
> > beginning of the (primary?) disk, then to create a FAT-32 partition for
> > /boot, then whatever other partitions are required.
>
> Another question answered: yes, it has to be the primary disk. I installed
> a
> smal
On Tuesday, 24 September 2019 09:50:44 BST I wrote:
> The Gentoo Handbook says to create a small unformatted partition at the
> beginning of the (primary?) disk, then to create a FAT-32 partition for
> /boot, then whatever other partitions are required.
Another question answered: yes, it has to b
On Tuesday, 24 September 2019 19:01:27 BST Neil Bothwick wrote:
> On Tue, 24 Sep 2019 09:50:44 +0100, Peter Humphrey wrote:
> > 1. I remember, dimly, that while commissioning this machine from new,
> > I had trouble installing and running grub:2. I knew even less about
> > UEFI systems then, so
On Tue, 24 Sep 2019 09:50:44 +0100, Peter Humphrey wrote:
> The Gentoo Handbook says to create a small unformatted partition at the
> beginning of the (primary?) disk, then to create a FAT-32 partition for
> /boot, then whatever other partitions are required.
>
> Neil said above that he doesn't
...
Right. After spending most of the last 10 days and some nights wrestling with
the beast, I've got it fixed at last.
The Gentoo Handbook says to create a small unformatted partition at the
beginning of the (primary?) disk, then to create a FAT-32 partition for /boot,
then whatever other par
25 matches
Mail list logo
