After installing new kernel how to update /boot EFI directory?
From my notes, I have:
grub-mkconfig -o /boot/grub/grub.cfg
grub-install --target=x86_64-efi --efi-directory=/boot
or should it be:
grub-mkconfig -o /boot/grub/grub.cfg
efibootmgr -c -d /dev/nvme0n1p1 -p 1 -L "Gentoo" -l /boot/grub/x86_64-efi/core.efi
Boot partition is:
/dev/nvme0n1p1Â Â =Â /boot
On 4/15/23 22:01, thelma@sys-concept.com wrote:
After installing new kernel how to update /boot EFI directory?
From my notes, I have:
grub-mkconfig -o /boot/grub/grub.cfg
grub-install --target=x86_64-efi --efi-directory=/boot
or should it be:/boot/grub/x86_64-efi/core.efi
grub-mkconfig -o /boot/grub/grub.cfg
efibootmgr -c -d /dev/nvme0n1p1 -p 1 -L "Gentoo" -l
Boot partition is:
/dev/nvme0n1p1 = /boot
This is not dual boot system, so I don't know why /boot has EFI directory
All EFI systems are supposed to have an EFI system partition (ESP). Some people use the ESP as their boot partition, while other people keep them as two separate partitions and mount the boot partition as /boot and the ESP
as /boot/EFI.
After installing new kernel how to update /boot EFI directory?
Also, learn how to boot a kernel from the grub cli, and keep a printed version of these instructions in a handy place. This has saved my butt countless times. :)
When you emerge grub, Gentoo compiles and "installs" grub (and some grub-related tools) to a directory inside your Gentoo installation, just like other applications. The catch is that grub isn't like other applications... it needs to run outside ofGentoo, before Linux starts. This means that Grub isn't very useful sitting inside your Gentoo installation.
"grub-install" copies Grub from your Gentoo installation to your hard drive / SSD / etc. This has nothing to do with your kernel, it only involves Grub. Rerun this command when you emerge updates to Grub.nothing to do with your kernel.
"efibootmgr" tells your motherboard's (U)EFI firmware where to find Grub (or any other bootloader or EFI tool). When you emerge an update for Grub (and run grub-install), the path shouldn't change, so there's no need to rerun efibootmgr. This also has
"grub-mkconfig" generates a configuration file that Grub reads while the computer is booting, and generally tells Grub what options to include in the menu Grub displays. When you update your kernel, you want to update that menu, so you SHOULD rerun "grub-mkconfig" at this time.
All EFI systems are supposed to have an EFI system partition (ESP). Some people use the ESP as their boot partition, while other people keep them as two separate partitions and mount the boot partition as /boot and the ESP as /boot/EFI. Either way, it's not related to dual-booting.
NOTE: if I remember correctly, there are USE flags that can be enabled to automatically run grub-install and grub-mkconfig when updates are installed for Grub and for kernels, respectively.
-Hypoon
On Sun, Apr 16, 2023, 00:19 <thelma@sys-concept.com <mailto:thelma@sys-concept.com>> wrote:
On 4/15/23 22:01, thelma@sys-concept.com <mailto:thelma@sys-concept.com> wrote:
> After installing new kernel how to update /boot EFI directory?
>
>Â From my notes, I have:
> grub-mkconfig -o /boot/grub/grub.cfg
> grub-install --target=x86_64-efi --efi-directory=/boot
>
> or should it be:
> grub-mkconfig -o /boot/grub/grub.cfg
> efibootmgr -c -d /dev/nvme0n1p1 -p 1 -L "Gentoo" -l /boot/grub/x86_64-efi/core.efi
>
> Boot partition is:
> /dev/nvme0n1p1Â Â =Â /boot
This is not dual boot system, so I don't know why /boot has EFI directory
Also, learn how to boot a kernel from the grub cli, and keep a printed version of these instructions in a handy place. This has saved my butt countless times. :)
On 16/04/2023 07:01, thelma@sys-concept.com wrote:
After installing new kernel how to update /boot EFI directory?
You don't need to. You only need to do that when you want to reinstall
GRUB itself into the EFI partition. The kernel is installed in /boot,
not into the EFI partition.
On 4/16/23 08:49, Lee K wrote:
Also, learn how to boot a kernel from the grub cli, and keep a printed
version of these instructions in a handy place. This has saved my butt
countless times. :)
Thanks Lee, that is really helpful hint.
A minimal EFI bootloader can show an updated menu for the new kernels
without needing to make regular writes to the EFI variable storage. I
didn't know Grub was deprecated, but there are other options. rEFInd is pretty. Syslinux is flexible.
On 16/04/2023 18:43, thelma@sys-concept.com wrote:
On 4/16/23 08:49, Lee K wrote:
Also, learn how to boot a kernel from the grub cli, and keep a printed
version of these instructions in a handy place. This has saved my butt
countless times. :)
Thanks Lee, that is really helpful hint.
Or, seeing as grub is deprecated with EFI, learn how to boot using EFI.
Don't worry, I haven't really learned either :-) I just keep a Slack
live-CD handy ...
Cheers,
Wol
Am 16.04.23 um 21:11 schrieb Mitch D.:
A minimal EFI bootloader can show an updated menu for the new kernels without needing to make regular writes to the EFI variable storage. I didn't know Grub was deprecated, but there are other options. rEFInd is pretty. Syslinux is flexible.
https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Bootloader
Default: GRUB
On 16/04/2023 18:43, thelma@sys-concept.com wrote:
On 4/16/23 08:49, Lee K wrote:Or, seeing as grub is deprecated with EFI, learn how to boot using EFI.
Also, learn how to boot a kernel from the grub cli, and keep a printedThanks Lee, that is really helpful hint.
version of these instructions in a handy place. This has saved my butt
countless times. :)
Wol, can you elaborate on why you think Grub is deprecated on EFI systems?
On Sun, Apr 16, 2023, 15:17 hitachi303 <gentoo-user@konstantinhansen.de <mailto:gentoo-user@konstantinhansen.de>> wrote:
Am 16.04.23 um 21:11 schrieb Mitch D.:
> A minimal EFI bootloader can show an updated menu for the new
kernels
> without needing to make regular writes to the EFI variable
storage. I
> didn't know Grub was deprecated, but there are other options.
rEFInd is
> pretty. Syslinux is flexible.
https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Bootloader
<https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Bootloader>
Default: GRUB
On 16/04/2023 22:30, Mitch D. wrote:
Wol, can you elaborate on why you think Grub is deprecated on EFI systems?
Because EFI is a boot manager?
Why chain-load boot managers?
Cheers,
Wol
On Sun, Apr 16, 2023, 15:17 hitachi303 <gentoo-user@konstantinhansen.de
<mailto:gentoo-user@konstantinhansen.de>> wrote:
Am 16.04.23 um 21:11 schrieb Mitch D.:
> A minimal EFI bootloader can show an updated menu for the new
kernels
> without needing to make regular writes to the EFI variable
storage. I
> didn't know Grub was deprecated, but there are other options.
rEFInd is
> pretty. Syslinux is flexible.
https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Bootloader
<https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Bootloader>
Default: GRUB
On 16/04/2023 22:30, Mitch D. wrote:
Wol, can you elaborate on why you think Grub is deprecated on EFI systems?
Because EFI is a boot manager? Why chain-load boot managers?
Cheers,
Wol
...
"grub-install" copies Grub from your Gentoo installation to your hard drive
/ SSD / etc. This has nothing to do with your kernel, it only involves
Grub. Rerun this command when you emerge updates to Grub.
...
NOTE: if I remember correctly, there are USE flags that can be enabled to automatically run grub-install and grub-mkconfig when updates are installed for Grub and for kernels, respectively.
Wol <antlists@youngman.org.uk> writes:
On 16/04/2023 22:30, Mitch D. wrote:
Wol, can you elaborate on why you think Grub is deprecated on EFI
systems?
Because EFI is a boot manager?
That is not the case any more than the classic IBM PC boot procedure is. There is technical capability for UEFI firmware to act in such a manner,
but, in practice, this is not at all the case.
The technical capability comes from the fact that boot entities have a
lil' bit of metadata attached to them.
Why chain-load boot managers?
In theory, EFI implementations should provide boot
managers. Unfortunately, in practice these boot managers are often so
poor as to be useless. The worst I've personally encountered is on
Gigabyte's Hybrid EFI, which provides you with no boot options
whatsoever, beyond choosing the boot device (hard disk vs. optical disc,
for instance). I've heard of others that are just as bad. For this
reason, a good EFI boot manager—either standalone or as part of a boot loader—is a practical necessity for multi-booting on an EFI
computer. That's where rEFInd comes into play.
- https://rodsbooks.com/refind/
Mitch,
On Sunday, 2023-04-16 07:16:09 -0400, you wrote:
...drive
"grub-install" copies Grub from your Gentoo installation to your hard
/ SSD / etc. This has nothing to do with your kernel, it only involves Grub. Rerun this command when you emerge updates to Grub.
Is this really necessary to be done manually? Shouldn't this be the job
of the Grub ebuild? My gut feeling is that having to look out for Grub updates and then to manually run "grub-install" every time is not really Gentoo-like ...
To be honest, I've run this command once during my initial Gentoo in- stall three and a half years back, but never since. And according to my
logs I've since then upgraded Grub ten times and rebuilt it four times. Should I worry? Can this be automated?
...installed
NOTE: if I remember correctly, there are USE flags that can be enabled to automatically run grub-install and grub-mkconfig when updates are
for Grub and for kernels, respectively.
Checking the USE flags for Grub and Portage I didn't find anything for automatically running "grub-install". Where else to look?
Sincerely,
Rainer
On 16/04/2023 15:22, Nikos Chantziaras wrote:
On 16/04/2023 07:01, thelma@sys-concept.com wrote:And if grub isn't installed?
After installing new kernel how to update /boot EFI directory?
You don't need to. You only need to do that when you want to reinstall
GRUB itself into the EFI partition. The kernel is installed in /boot,
not into the EFI partition.
Basically you have a choice. Install grub into EFI, and use grub as your
boot manager. Or ditch grub (the recommended route) and use EFI as your
boot manager.
On Monday, 17 April 2023 00:29:49 BST Arsen Arsenović wrote:the
Wol <antlists@youngman.org.uk> writes:
On 16/04/2023 22:30, Mitch D. wrote:
Wol, can you elaborate on why you think Grub is deprecated on EFI
systems?
Because EFI is a boot manager?
That is not the case any more than the classic IBM PC boot procedure is. There is technical capability for UEFI firmware to act in such a manner, but, in practice, this is not at all the case.
The technical capability comes from the fact that boot entities have a
lil' bit of metadata attached to them.
The ability of UEFI to boot linux kernels, as long as they are built with
EFI boot stub enabled, may render 3rd party boot managers and their boot loaders redundant. However, as already mentioned below, the flexibilityand
customisability of GRUB and other boot manager exceeds any UEFI firmwareI've
come across.
directlyWhy chain-load boot managers?
In theory, EFI implementations should provide boot
managers. Unfortunately, in practice these boot managers are often so
poor as to be useless. The worst I've personally encountered is on Gigabyte's Hybrid EFI, which provides you with no boot options
whatsoever, beyond choosing the boot device (hard disk vs. optical disc, for instance). I've heard of others that are just as bad. For this
reason, a good EFI boot manager—either standalone or as part of a boot loader—is a practical necessity for multi-booting on an EFI
computer. That's where rEFInd comes into play.
- https://rodsbooks.com/refind/
I've stopped using GRUB and have been using the UEFI firmware to boot
Gentoo for more than 10 years now. Given I have also flashed some of the MoBos' chipset with new UEFI firmware a dozen times or more, I have not experienced any MoBo failures as yet. Also, the ESP partition formattedwith
FAT32 has remained quite resilient too. No loss of data or fs corruptionyet
(keeps fingers crossed and checks backups).appreciate
My particular systems setup and use case suits this approach, but I
people who multiboot daily/frequently, or need to boot LiveISOs off thedisk
may find GRUB and friends to be a more suitable solution.
> > ><br>> > > Because EFI is a boot manager?<br>> ><br>> > That is not the case any more than the classic IBM PC boot procedure is.<br>> > There is technical capability for UEFI firmware to act in such a manner,<br>> > but, in practice, this is not at all the case.<br>> ><br>> > The technical capability comes from the fact that boot entities have a<br>> > lil' bit of metadata attached to them.<br>><br>> The ability of UEFI to boot
On Mon, Apr 17, 2023 at 4:57 AM Michael <confabulate@kintzios.com> wrote:
On Monday, 17 April 2023 00:29:49 BST Arsen Arsenović wrote:
Wol <antlists@youngman.org.uk> writes:
On 16/04/2023 22:30, Mitch D. wrote:
Wol, can you elaborate on why you think Grub is deprecated on EFI
systems?
Because EFI is a boot manager?
is.That is not the case any more than the classic IBM PC boot procedure
manner,There is technical capability for UEFI firmware to act in such a
but, in practice, this is not at all the case.
The technical capability comes from the fact that boot entities have a lil' bit of metadata attached to them.
The ability of UEFI to boot linux kernels, as long as they are builtwith the
EFI boot stub enabled, may render 3rd party boot managers and their boot loaders redundant. However, as already mentioned below, the flexibilityand
customisability of GRUB and other boot manager exceeds any UEFI firmwareI've
come across.
Why chain-load boot managers?
disc,In theory, EFI implementations should provide boot
managers. Unfortunately, in practice these boot managers are often so poor as to be useless. The worst I've personally encountered is on Gigabyte's Hybrid EFI, which provides you with no boot options whatsoever, beyond choosing the boot device (hard disk vs. optical
for instance). I've heard of others that are just as bad. For this reason, a good EFI boot manager—either standalone or as part of a boot loader—is a practical necessity for multi-booting on an EFI
computer. That's where rEFInd comes into play.
- https://rodsbooks.com/refind/
I've stopped using GRUB and have been using the UEFI firmware to bootdirectly
Gentoo for more than 10 years now. Given I have also flashed some of the MoBos' chipset with new UEFI firmware a dozen times or more, I have not experienced any MoBo failures as yet. Also, the ESP partition formattedwith
FAT32 has remained quite resilient too. No loss of data or fscorruption yet
(keeps fingers crossed and checks backups).
My particular systems setup and use case suits this approach, but Iappreciate
people who multiboot daily/frequently, or need to boot LiveISOs off thedisk
may find GRUB and friends to be a more suitable solution.
My needs are quite simple but efibootmgr, set up by the Kubuntu install
on a separate M.2 from the Windows install the machine came with, works
for
me. I always start the day in Kubuntu, then reboot to Windows if I'm
working
on music:
1) The simple view of the two installations:
mark@science2:~$ efibootmgr
BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0003,0000
Boot0000* Windows Boot Manager
Boot0003* ubuntu
mark@science2:~$
2) The more complicated view with GUIDs and such:
mark@science2:~$ efibootmgr -v
BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0003,0000
Boot0000* Windows Boot Manager
HD(1,GPT,2052c843-0057-494a-a749-e8ec3676514a,0x800,0x32000)/File(\EF
I\MICROSOFT\BOOT\BOOTMGFW.EFI)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4
.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0003* ubuntu
HD(1,GPT,2052c843-0057-494a-a749-e8ec3676514a,0x800,0x32000)/File(\EFI\UBUNTU
\SHIMX64.EFI)
mark@science2:~$
3) To get to Windows I can choose it in the OS screen if I'm sitting there but the most reliable way for me to get from Kubuntu to Windows is to just tell the system to go to Windows at the next boot using a batch file in Kubuntu:
mark@science2:~$ cat bin/RebootWindows
sudo efibootmgr -n 0000
reboot
mark@science2:~$
The 'problem' with this setup is that all of the grub/efibootmgr stuff
is on both drives and I'm never sure which drive is being used at
which time as I have Kubuntu on nvme1 and Windows boot
manager on nvme0 which I'm never comfortable with but the
Ubuntu stuff figured it out so I don't argue. Pity me if I ever have to
do a reinstall.
mark@science2:~$ df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 3.2G 3.7M 3.2G 1% /run
/dev/nvme1n1p3 916G 622G 248G 72% /
tmpfs 16G 66M 16G 1% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
/dev/nvme0n1p1 96M 32M 65M 33% /boot/efi
tmpfs 3.2G 64K 3.2G 1% /run/user/1000
mark@science2:~$
> > > On 16/04/2023 22:30, Mitch D. wrote:<br>> > >> Wol, can you elaborate on why you think Grub is deprecated on EFI<br>> > >> systems?<br>> > ><br>> > > Because EFI is a boot manager?<br>> ><gt; The technical capability comes from the fact that boot entities have a<br>> > lil' bit of metadata attached to them.<br>><br>> The ability of UEFI to boot linux kernels, as long as they are built with the<br>> EFI boot stub enabled,
> > That is not the case any more than the classic IBM PC boot procedure is.<br>> > There is technical capability for UEFI firmware to act in such a manner,<br>> > but, in practice, this is not at all the case.<br>> ><br>> &
</div></div></blockquote></div></div></div>
My needs are quite simple but efibootmgr, set up by the Kubuntu install
on a separate M.2 from the Windows install the machine came with, works for me. I always start the day in Kubuntu, then reboot to Windows if I'm working on music:
1) The simple view of the two installations:
mark@science2:~$ efibootmgr
BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0003,0000
Boot0000* Windows Boot Manager
Boot0003* ubuntu
mark@science2:~$
2) The more complicated view with GUIDs and such:
mark@science2:~$ efibootmgr -v
BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0003,0000
Boot0000* Windows Boot Manager
HD(1,GPT,2052c843-0057-494a-a749-e8ec3676514a,0x800,0x32000)/File(\EF I\MICROSOFT\BOOT\BOOTMGFW.EFI)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d. e.a.8.6.2.c.-.5.c.d.d.-.4 .e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0003* ubuntu
HD(1,GPT,2052c843-0057-494a-a749-e8ec3676514a,0x800,0x32000)/File(\EFI\UBUN TU \SHIMX64.EFI)
mark@science2:~$
3) To get to Windows I can choose it in the OS screen if I'm sitting there but the most reliable way for me to get from Kubuntu to Windows is to just tell the system to go to Windows at the next boot using a batch file in Kubuntu:
mark@science2:~$ cat bin/RebootWindows
sudo efibootmgr -n 0000
reboot
mark@science2:~$
The 'problem' with this setup is that all of the grub/efibootmgr stuff
is on both drives
and I'm never sure which drive is being used at
which time as I have Kubuntu on nvme1 and Windows boot
manager on nvme0 which I'm never comfortable with but the
Ubuntu stuff figured it out so I don't argue. Pity me if I ever have to
do a reinstall.
mark@science2:~$ df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 3.2G 3.7M 3.2G 1% /run
/dev/nvme1n1p3 916G 622G 248G 72% /
tmpfs 16G 66M 16G 1% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
/dev/nvme0n1p1 96M 32M 65M 33% /boot/efi
tmpfs 3.2G 64K 3.2G 1% /run/user/1000
mark@science2:~$
On Monday, 17 April 2023 14:31:08 BST Mark Knecht wrote:<SNIP>
2) The more complicated view with GUIDs and such:
mark@science2:~$ efibootmgr -v
BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0003,0000
Boot0000* Windows Boot Manager
HD(1,GPT,2052c843-0057-494a-a749-e8ec3676514a,0x800,0x32000)/File(\EF
e.a.8.6.2.c.-.5.c.d.d.-.4 .e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0003* ubuntu
TU \SHIMX64.EFI)
mark@science2:~$
This shows the efibootmgr is using the first disk and boots the Windows BOOTMGFW.EFI, or Ubuntu's shimX64.efi from there.
The 'problem' with this setup is that all of the grub/efibootmgr stuff
is on both drives
Are you sure?
This is where the ESP is mounted, but you'll find /boot directory is onyour /
dev/nvme1n1p3 block device, along with your kernels, initrd images and vimlinuz symlinks.
Your GRUB EFI bootable image is on /dev/nvme0n1p1, under/boot/efi/EFI/ubuntu/
willtmpfs 3.2G 64K 3.2G 1% /run/user/1000
mark@science2:~$
I would think Ubuntu installed GRUB on nvme0n1p1 ESP, which it detected by scanning your disks. If your nvme0n1p1 fails and has to be removed, you
need to create a new ESP somewhere on the ubuntu disk and then you can reinstall GRUB after you reboot with a LiveUSB, or while still runningubuntu.
<div><br></div><div>HISTORY. I bought the computer with Win 10 installed and a</div><div>second empty M.2 drive. To install Kubuntu I switched BIOS to</div><div>boot from that drive, installed Kubuntu which populated the EFI</div><div>directory withall of the stuff you're showing me. I did not know about</div><div>the efibootmgr at the time as this was my fist new MB in about 8Â </div><div>years.</div><div><br></div><div>Early on I went to Windows by changing BIOS because, for what</div><div>
luck of the draw, or that 0001 and 0002 were used at one time and no longer</div><div>present, but that's just a guess. </div><div><br></div><div>For anyone following along or reading later, there's an easily read web page</div><div>onthings you can do with efibootmgr located here:</div><div><br></div><div><a href="https://www.linuxbabe.com/command-line/how-to-use-linux-efibootmgr-examples">https://www.linuxbabe.com/command-line/how-to-use-linux-efibootmgr-examples</a><br></div><div><
</div><div>Also, the Windows app similar to efibootmgr (but untested by me) is </div><div>possibly called bootcfg.exe</div><div><br></div><div>- Mark</div></div>
One thing I haven't decoded is why Windows is 0000 and Kubuntu is 0003.
I now better understand Mitch D.'s point that the pointers to which OS to boot are not in a disk file, like the old grub configuration, but rather in Flash memory on the motherboard. I suppose the numbering is just the
luck of the draw, or that 0001 and 0002 were used at one time and no longer present, but that's just a guess.
On Monday, 17 April 2023 17:52:25 BST Mark Knecht wrote:
One thing I haven't decoded is why Windows is 0000 and Kubuntu is 0003.
See below ...
toI now better understand Mitch D.'s point that the pointers to which OS
rather inboot are not in a disk file, like the old grub configuration, but
longerFlash memory on the motherboard. I suppose the numbering is just the
luck of the draw, or that 0001 and 0002 were used at one time and no
manuallypresent, but that's just a guess.
Exactly the latter, they are no longer present. I copy kernel images
to /boot/EFI/Gentoo/ and run 'efibootmgr --create' to add entries to theUEFI
boot menu with my choice of labels. They are added being numbered incrementally. If I remove some of the older menu entries, their corresponding numbers are also removed and become available for any new bootable .efi images I may add in the future.will
In addition, if I boot with any USB drives attached, the UEFI firmware
scan such devices and add any bootable images to the UEFI boot menustored in
NVRAM, by numbering such images incrementally. This will furtherincrease the
numbers of boot menu entries, which once the USB devices are removed their entry number will become vacant and available to be reallocated.
I just took a quick glance at the ebuild, and it looks like it should print
a reminder ("Re-run grub-install to update installed boot code!") every
time you upgrade from an older version to a newer one, but it also looks
like the reminder gets skipped if you're re-emerging the same version.
https://gitweb.gentoo.org/repo/gentoo.git/tree/sys-boot/grub/grub-2.06-r4.ebuild#n314
On 17/04/2023 17:52, Mark Knecht wrote:
Later on a Kubuntu update found Windows, updated the EFI
stuff on the Windows drive and then, I see this morning,
erased everything out of the Kubuntu EFI partition but
left the partition there.
I had a similar problem trying to install SUSE to dual boot a laptop. I
made the mistake of letting Windows wipe the disk and install itself,
with the result I was left with a tiny EFI partition. I couldn't install linux because there was no room.
My latest attempt (when I get gentoo video working) will be to *add*
Windows to a working system.
Cheers,
Wol
Mitch,
On Monday, 2023-04-17 08:15:51 -0400, you wrote:
I just took a quick glance at the ebuild, and it looks like it shouldprint
a reminder ("Re-run grub-install to update installed boot code!") every time you upgrade from an older version to a newer one, but it also looks like the reminder gets skipped if you're re-emerging the same version.
https://gitweb.gentoo.org/repo/gentoo.git/tree/sys-boot/grub/grub-2.06-r4.ebuild#n314
Thankyou very much for this information. But is there anyone out there
who skims through tons of SUCCESSFUL emerge log files after every rou-
tine upgrade? Personally, I only check the logs in case of build fai- lures or conflicts.
By the way, I only see this message in the build logs for versions 2.06-
r4 and 2.06-r6, but not in older logs. So maybe that's a rather new ad- dition to the ebuild file?
Since I do my routine upgrades via a script anyway, I now retrieve the
name of the most recent Grub build log before I really start "emerge"
and after "emerge" finished, and if the two names differ and the newer
file contains this "Re-run ..." message, I now run "grub-install" from within this script. Problem solved.
But I have the vague feeling there should be a more foolproof solution.
Sincerely,
Rainer
Later on a Kubuntu update found Windows, updated the EFI
stuff on the Windows drive and then, I see this morning,
erased everything out of the Kubuntu EFI partition but
left the partition there.
On 17/04/2023 17:52, Mark Knecht wrote:
Later on a Kubuntu update found Windows, updated the EFI
stuff on the Windows drive and then, I see this morning,
erased everything out of the Kubuntu EFI partition but
left the partition there.
I had a similar problem trying to install SUSE to dual boot a laptop. I
made the mistake of letting Windows wipe the disk and install itself,
with the result I was left with a tiny EFI partition. I couldn't install linux because there was no room.
My latest attempt (when I get gentoo video working) will be to *add*
Windows to a working system.
On Monday, 17 April 2023 21:41:09 BST Wols Lists wrote:
On 17/04/2023 17:52, Mark Knecht wrote:
Later on a Kubuntu update found Windows, updated the EFI
stuff on the Windows drive and then, I see this morning,
erased everything out of the Kubuntu EFI partition but
left the partition there.
I had a similar problem trying to install SUSE to dual boot a laptop. I
made the mistake of letting Windows wipe the disk and install itself,
with the result I was left with a tiny EFI partition. I couldn't install
linux because there was no room.
My latest attempt (when I get gentoo video working) will be to *add*
Windows to a working system.
Can you not just resize the partition?
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 546 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 149:45:06 |
| Calls: | 10,383 |
| Files: | 14,054 |
| Messages: | 6,417,777 |