Hi,
I tried a FAI installation with UEFI clients.
What I did in the end is surely not optimal. But perhaps
it's interesting for some people on this list
or you can give me some advice when I didn't do things
the "fai way".
The FAI server runs Debian/Sid (January 2014),
the clients get Whe
> On Mon, 3 Feb 2014 19:10:54 +0100, Meik Hellmund
> said:
> I tried a FAI installation with UEFI clients.
> What I did in the end is surely not optimal. But perhaps
> it's interesting for some people on this list
> or you can give me some advice when I didn't do thing
Hi,
I continue to work through getting Debian Buster deployed to new
hardware... I'm now trying to get it configured so the target uses uefi
to boot. I've managed to get most of it but I'm missing something.
In Shell.log I'm seeing this:
= shell: GRUB_EFI/10-setup =
ainsl: append
> On Mon, 25 Nov 2019 16:53:24 -0800, CSCI Technician
> said:
> The related classes defined are GRUB and GRUB_EFI. GRUB_PC is not
> defined. What I'm not sure how to fix is to get grub-install to realize
> this is an efi and not a bios install so that it should be using t
Hi Florian,
Thanks for the reply. Yes I did.
The disk seems to be partitioned correctly and the packages that get
installed are the efi versions.
What I'm not sure is if there is a class flag or something that I'm missing.
Cheers,
Merlin
On 11/26/19 4:33 AM, Florian Goth wrote:
Hi Merlin,
On 11/26/19 6:08 AM, Thomas Lange wrote:
On Mon, 25 Nov 2019 16:53:24 -0800, CSCI Technician said:
> The related classes defined are GRUB and GRUB_EFI. GRUB_PC is not
> defined. What I'm not sure how to fix is to get grub-install to realize
> this is an efi and not a bios in
On 11/26/19 6:08 AM, Thomas Lange wrote:
On Mon, 25 Nov 2019 16:53:24 -0800, CSCI Technician said:
> The related classes defined are GRUB and GRUB_EFI. GRUB_PC is not
> defined. What I'm not sure how to fix is to get grub-install to realize
> this is an efi and not a bios in
> On Tue, 26 Nov 2019 09:07:00 -0800, CSCI Technician
> said:
> I have updated my FAI install and NFSROOT to one of the latest
> versions... however my config still needs to be updated. I noticed this
> when comparing some of the scripts in my config directory vs those in
Replying to my own question in case anyone else is looking at this
thread for answers...
As Sven Schumacher confirmed (messages with blank subject so they may
not be part of this thread), yes the client needs to PXE boot with UEFI.
Once I adjusted my dhcpd.conf and added the efi versions of s
Diese Nachricht wurde eingewickelt um DMARC-kompatibel zu sein. Die
eigentliche Nachricht steht dadurch in einem Anhang.
This message was wrapped to be DMARC compliant. The actual message
text is therefore in an attachment.--- Begin Message ---
I'm building a UEFI image for Debian Bookworkm, but w
efore in an attachment.
> From: Laura Smith
> To: fully automatic installation for Linux
> Subject: UEFI boot dropping to startup.nsh prompt
> Date: Wed, 10 Apr 2024 09:01:08 +
> I'm building a UEFI image for Debian Bookworkm, but when I load the qco
On Mon, 2021-02-08 at 12:31:22 -0600, John G Heim wrote:
> In these days when so many of us are working from home, I thought I'd give a
> tip I discovered today on how to trigger an FAI install remotely.
>
> For years I've been triggering an FAI install remotely by wiping the hard
> drive and hopi
> On Fri, 17 Sep 2021 11:06:30 +0200, Steffen Grunewald
> said:
> That would either involve additions to GRUB_EFI/10-setup itself, or two
> extra scripts 09-x and 11-x which would have to communicate e.g. via
> ${LOGDIR}/bootorder ...
> I can imagine using an extra class,
Seasons greeting to everyone,
there's something that didn't let me rest since I discovered it.
A while back I had suggested to restore the UEFI BootOrder that was in effect
before GRUB-EFI was installed:
On Fri, 2021-09-17 at 11:24:52 +0200, Thomas Lange wrote:
> > On Fri, 17 Sep 2021 11:06:3
Hi all,
I'm wondering whether this issue concerning bad/wrong UEFI boot order
after a fai installation already was resolved in the meantime (since
September, 2021)?
https://lists.uni-koeln.de/pipermail/linux-fai/2021-September/012770.html
The idea was to e.g. add a few lines in
c
Hi
for one-time changes in the boot order, you can use
efibootmgr --bootnext
and set this to the network device. From man efibootmgr:
BootNext - the boot entry which is scheduled to be run on next
boot. This supercedes BootOrder for one boot only, and is
deleted by the boot
Oh, you can set an efi boot entry inactive using -A
Maybe this helps changing the boot device, without changing the
overall boot order.
--
regards Thomas
Hi,
I found this code that move the first boot entry (which is expected to
be the new entry after an installation) to the end of the boot list.
https://community.theforeman.org/t/efi-boot-order-with-centos-7-network-boot-vs-local-boot/10529/2
# the EFI boot manager is only installed on UEFI host
Diese Nachricht wurde eingewickelt um DMARC-kompatibel zu sein. Die
eigentliche Nachricht steht dadurch in einem Anhang.
This message was wrapped to be DMARC compliant. The actual message
text is therefore in an attachment.--- Begin Message ---
Hi Thomas,
> I wonder why the second machine has tw
# prior to disk partioning collect the UEFI boot order
efibootmgr
---
root@jammysrv:/srv/fai/config# less
/var/log/fai/remote-logs/l65/last/fai.log
---Output
[...]
Calling hook: partition.GRUB_EFI
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0001,0002,0003,0004,,0005
Boot* ubunt
20 matches
Mail list logo
