| View previous topic :: View next topic |
| Author |
Message |
enrico68
Apprentice
Joined: 21 Oct 2016
Posts: 169
|
 Posted: Thu Apr 13, 2023 7:56 am Post subject: Where should I mount the boot partition with no Windows OS? |
 |
|
Hello,
I am trying to install Gentoo on my PC, this time without Windows 10 installed. With Windows 10, I mount the Windows EFI partiton to /boot, and use that EFI partition to load Gentoo. Without Windows 10 and its EFI partiton, I created an EFI partiton for Gentoo, which I mounted at /boot.
The issue is that, after finishing the process, Gentoo will not boot. This is the first time I am trying to only have Gentoo on my PC, and maybe there is a workaround for this. Down the road, I might install another Linux distro as a backup, on a second nvme, and I would like to use Gentoo's EFI to load the second Linux distro.
Here is my simple setup for the Gentoo installation:
/dev/nvme0n1p1 EFI /boot
/dev/nvme0n1p2 Gentoo /.
Any input is much appreciated, |
|
| Back to top |
|
 |
alamahant
Advocate
Joined: 23 Mar 2019
Posts: 3879
|
| Posted: Thu Apr 13, 2023 8:11 am Post subject: |
|
|
You can mount the efi partition in
What was the grub-install invocation you used to install grub?
Also plz chroot into your system and post
| Code: |
ls -R /boot
lsblk -f
|
What kind of error did you get while booting?
_________________
 |
|
| Back to top |
|
|
sMueggli
Guru
Joined: 03 Sep 2022
Posts: 374
|
| Posted: Thu Apr 13, 2023 8:57 am Post subject: |
|
|
Please show also the output of
| Code: | efibootmgr
lsblk -o NAME,PARTTYPE /dev/nvme0n1p2 |
How do you boot Gentoo? Do you use a bootloader?
How do you know that Gentoo is not booting? No screen output? Error message? UEFI reloads? |
|
| Back to top |
|
|
enrico68
Apprentice
Joined: 21 Oct 2016
Posts: 169
|
| Posted: Thu Apr 13, 2023 10:43 am Post subject: |
|
|
| alamahant wrote: | You can mount the efi partition in
What was the grub-install invocation you used to install grub?
Also plz chroot into your system and post
| Code: |
ls -R /boot
lsblk -f
|
| Code: | # ls -R /boot
/boot:
EFI
System.map-6.1.19-gentoo
config-6.1.19-gentoo
grub
vmlinuz-6.1.19-gentoo
/boot/EFI:
gentoo
/boot/EFI/gentoo:
grubx64.efi
/boot/grub:
fonts
grub.cfg
grubenv
locale
themes
x86_64-efi
/boot/grub/fonts:
unicode.pf2
/boot/grub/locale:
ast.mo
ca.mo
da.mo
de.mo
de@hebrew.mo
de_CH.mo
en@arabic.mo
en@cyrillic.mo
en@greek.mo
en@hebrew.mo
en@piglatin.mo
en@quot.mo
eo.mo
es.mo
fi.mo
fr.mo
gl.mo
hr.mo
hu.mo
id.mo
it.mo
ja.mo
ko.mo
lg.mo
lt.mo
nb.mo
nl.mo
pa.mo
pl.mo
pt.mo
pt_BR.mo
ro.mo
ru.mo
sl.mo
sr.mo
sv.mo
tr.mo
uk.mo
vi.mo
zh_CN.mo
zh_TW.mo
/boot/grub/themes:
starfield
/boot/grub/themes/starfield:
COPYING.CC-BY-SA-3.0
README
blob_w.png
boot_menu_c.png
boot_menu_e.png
boot_menu_n.png
boot_menu_ne.png
boot_menu_nw.png
boot_menu_s.png
boot_menu_se.png
boot_menu_sw.png
boot_menu_w.png
dejavu_10.pf2
dejavu_12.pf2
dejavu_14.pf2
dejavu_16.pf2
dejavu_bold_14.pf2
slider_c.png
slider_n.png
slider_s.png
starfield.png
terminal_box_c.png
terminal_box_e.png
terminal_box_n.png
terminal_box_ne.png
terminal_box_nw.png
terminal_box_s.png
terminal_box_se.png
terminal_box_sw.png
terminal_box_w.png
theme.txt
/boot/grub/x86_64-efi:
acpi.mod
adler32.mod
affs.mod
afs.mod
afsplitter.mod
ahci.mod
all_video.mod
aout.mod
appleldr.mod
archelp.mod
at_keyboard.mod
ata.mod
backtrace.mod
bfs.mod
bitmap.mod
bitmap_scale.mod
blocklist.mod
boot.mod
bsd.mod
bswap_test.mod
btrfs.mod
bufio.mod
cat.mod
cbfs.mod
cbls.mod
cbmemc.mod
cbtable.mod
cbtime.mod
chain.mod
cmdline_cat_test.mod
cmp.mod
cmp_test.mod
command.lst
configfile.mod
core.efi
cpio.mod
cpio_be.mod
cpuid.mod
crc64.mod
crypto.lst
crypto.mod
cryptodisk.mod
cs5536.mod
ctz_test.mod
date.mod
datehook.mod
datetime.mod
disk.mod
diskfilter.mod
div.mod
div_test.mod
dm_nv.mod
echo.mod
efi_gop.mod
efi_uga.mod
efifwsetup.mod
efinet.mod
ehci.mod
elf.mod
eval.mod
exfat.mod
exfctest.mod
ext2.mod
extcmd.mod
f2fs.mod
fat.mod
file.mod
fixvideo.mod
font.mod
fs.lst
fshelp.mod
functional_test.mod
gcry_arcfour.mod
gcry_blowfish.mod
gcry_camellia.mod
gcry_cast5.mod
gcry_crc.mod
gcry_des.mod
gcry_dsa.mod
gcry_idea.mod
gcry_md4.mod
gcry_md5.mod
gcry_rfc2268.mod
gcry_rijndael.mod
gcry_rmd160.mod
gcry_rsa.mod
gcry_seed.mod
gcry_serpent.mod
gcry_sha1.mod
gcry_sha256.mod
gcry_sha512.mod
gcry_tiger.mod
gcry_twofish.mod
gcry_whirlpool.mod
geli.mod
gettext.mod
gfxmenu.mod
gfxterm.mod
gfxterm_background.mod
gfxterm_menu.mod
gptsync.mod
grub.efi
gzio.mod
halt.mod
hashsum.mod
hdparm.mod
hello.mod
help.mod
hexdump.mod
hfs.mod
hfsplus.mod
hfspluscomp.mod
http.mod
iorw.mod
iso9660.mod
jfs.mod
jpeg.mod
json.mod
keylayouts.mod
keystatus.mod
ldm.mod
legacy_password_test.mod
legacycfg.mod
linux.mod
linux16.mod
loadbios.mod
loadenv.mod
loopback.mod
ls.mod
lsacpi.mod
lsefi.mod
lsefimmap.mod
lsefisystab.mod
lsmmap.mod
lspci.mod
lssal.mod
luks.mod
luks2.mod
lvm.mod
lzopio.mod
macbless.mod
macho.mod
mdraid09.mod
mdraid09_be.mod
mdraid1x.mod
memdisk.mod
memrw.mod
minicmd.mod
minix.mod
minix2.mod
minix2_be.mod
minix3.mod
minix3_be.mod
minix_be.mod
mmap.mod
moddep.lst
modinfo.sh
morse.mod
mpi.mod
msdospart.mod
mul_test.mod
multiboot.mod
multiboot2.mod
nativedisk.mod
net.mod
newc.mod
nilfs2.mod
normal.mod
ntfs.mod
ntfscomp.mod
odc.mod
offsetio.mod
ohci.mod
part_acorn.mod
part_amiga.mod
part_apple.mod
part_bsd.mod
part_dfly.mod
part_dvh.mod
part_gpt.mod
part_msdos.mod
part_plan.mod
part_sun.mod
part_sunpc.mod
partmap.lst
parttool.lst
parttool.mod
password.mod
password_pbkdf2.mod
pata.mod
pbkdf2.mod
pbkdf2_test.mod
pcidump.mod
pgp.mod
play.mod
png.mod
priority_queue.mod
probe.mod
procfs.mod
progress.mod
raid5rec.mod
raid6rec.mod
random.mod
rdmsr.mod
read.mod
reboot.mod
regexp.mod
reiserfs.mod
relocator.mod
romfs.mod
scsi.mod
search.mod
search_fs_file.mod
search_fs_uuid.mod
search_label.mod
serial.mod
setjmp.mod
setjmp_test.mod
setpci.mod
sfs.mod
shift_test.mod
signature_test.mod
sleep.mod
sleep_test.mod
smbios.mod
spkmodem.mod
squash4.mod
strtoull_test.mod
syslinuxcfg.mod
tar.mod
terminal.lst
terminal.mod
terminfo.mod
test.mod
test_blockarg.mod
testload.mod
testspeed.mod
tftp.mod
tga.mod
time.mod
tpm.mod
tr.mod
trig.mod
true.mod
udf.mod
ufs1.mod
ufs1_be.mod
ufs2.mod
uhci.mod
usb.mod
usb_keyboard.mod
usbms.mod
usbserial_common.mod
usbserial_ftdi.mod
usbserial_pl2303.mod
usbserial_usbdebug.mod
usbtest.mod
video.lst
video.mod
video_bochs.mod
video_cirrus.mod
video_colors.mod
video_fb.mod
videoinfo.mod
videotest.mod
videotest_checksum.mod
wrmsr.mod
xfs.mod
xnu.mod
xnu_uuid.mod
xnu_uuid_test.mod
xzio.mod
zfs.mod
zfscrypt.mod
zfsinfo.mod
zstd.mod |
| Code: | # lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0 squashfs 4.0
sda
├─sda1 exfat 1.0 Ventoy 4E21-0000
│ └─ventoy
└─sda2 vfat FAT16 VTOYEFI 440A-1007
nvme0n1
├─nvme0n1p1 vfat FAT32 BBEF-2713 993.6M 3% /boot
└─nvme0n1p2 ext4 1.0 a256af7d-0bc0-44bb-995b-e0ad667aded3 459.6G 1% /
nvme1n1
nvme2n1 |
What kind of error did you get while booting? |
No apparent error, no message, the computer boots into the BIOS. |
|
| Back to top |
|
|
enrico68
Apprentice
Joined: 21 Oct 2016
Posts: 169
|
| Posted: Thu Apr 13, 2023 10:49 am Post subject: |
|
|
| sMueggli wrote: | Please show also the output of
| Code: | efibootmgr
lsblk -o NAME,PARTTYPE /dev/nvme0n1p2 |
| Code: |
# efibootmgr
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0001
Boot0001* UEFI: USB, Partition 2 PciRoot(0x0)/Pci(0x14,0x0)/USB(20,0)/HD(2,MBR,0x2b86ed08,0x3947000,0x10000)0000424f |
| Code: | # lsblk -o NAME,PARTTYPE /dev/nvme0n1p2
NAME PARTTYPE
nvme0n1p2 0fc63daf-8483-4772-8e79-3d69d8477de4 |
How do you boot Gentoo? Do you use a bootloader?
How do you know that Gentoo is not booting? No screen output? Error message? UEFI reloads? |
I installed Grub, and no screen output when I try to load Gentoo... |
|
| Back to top |
|
|
pietinger
Moderator
Joined: 17 Oct 2006
Posts: 4236
Location: Bavaria
|
| Posted: Thu Apr 13, 2023 11:02 am Post subject: |
|
|
Your UEFI BIOS has no entry for your grub. Usually this entry is created when installing grub. Strange. But, no problem, you can create it manually with:
| Code: | | efibootmgr -c -d /dev/nvme0n1 -p 1 -L "Gentoo" -l "\EFI\gentoo\grubx64.efi" |
After this check again with "efibootmgr" if it is set. No do a reboot. |
|
| Back to top |
|
|
enrico68
Apprentice
Joined: 21 Oct 2016
Posts: 169
|
| Posted: Thu Apr 13, 2023 11:17 am Post subject: |
|
|
Hi Pietinger,
here is the output of efibootmgr after executing the above command:
| Code: | # efibootmgr
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0000,0001
Boot0000* Gentoo HD(1,GPT,85b012d3-fe0d-cc4a-b725-8c72f016ddc2,0x800,0x200000)/File(\EFI\gentoo\grubx64.efi)
Boot0001* UEFI: USB, Partition 2 PciRoot(0x0)/Pci(0x14,0x0)/USB(20,0)/HD(2,MBR,0x2b86ed08,0x3947000,0x10000)0000424f |
Now let me do a reboot, and let's see.... |
|
| Back to top |
|
|
enrico68
Apprentice
Joined: 21 Oct 2016
Posts: 169
|
| Posted: Thu Apr 13, 2023 11:18 am Post subject: |
|
|
| No luck.... |
|
| Back to top |
|
|
pietinger
Moderator
Joined: 17 Oct 2006
Posts: 4236
Location: Bavaria
|
| Posted: Thu Apr 13, 2023 11:23 am Post subject: |
|
|
| enrico68 wrote: | | No luck.... |
What happens ? Did it boot into BIOS ?
If yes: If you boot again with Gentoo minimal Install and do immediately an "efibootmgr" is there still your entry for grub ?
(If not you have a buggy BIOS and we have to go another way)
P.S.: Do have disabled "SecureBoot" in your BIOS ? (If not disable it) |
|
| Back to top |
|
|
enrico68
Apprentice
Joined: 21 Oct 2016
Posts: 169
|
| Posted: Thu Apr 13, 2023 11:29 am Post subject: |
|
|
Yes, it booted into BIOS.
Here is the output, after chrooting back into Gentoo from the live cd:
| Code: | # efibootmgr
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0001
Boot0001* UEFI: USB, Partition 2 PciRoot(0x0)/Pci(0x14,0x0)/USB(20,0)/HD(2,MBR,0x2b86ed08,0x3947000,0x10000)0000424f
|
As you can see, the entry for grub is not there.... |
|
| Back to top |
|
|
pietinger
Moderator
Joined: 17 Oct 2006
Posts: 4236
Location: Bavaria
|
| Posted: Thu Apr 13, 2023 11:29 am Post subject: |
|
|
Have you enabled ESP flag on your /dev/nvme0n1p1 ? Check with "parted -l" You should see something like this:
| Code: | | 1 3146kB 1074MB 1071MB fat32 boot boot, esp |
If not you must do:
1.
| Code: | | parted /dev/nvme01n1 set 1 boot on |
2. Do again you entry with efibootmgr |
|
| Back to top |
|
|
enrico68
Apprentice
Joined: 21 Oct 2016
Posts: 169
|
| Posted: Thu Apr 13, 2023 11:37 am Post subject: |
|
|
| pietinger wrote: | Have you enabled ESP flag on your /dev/nvme0n1p1 ? Check with "parted -l" You should see something like this:
| Code: | | 2 3146kB 1074MB 1071MB fat32 boot boot, esp |
|
That could be it, hopefully. I used fdisk to partition the nvme. Anyways, here is my parted -l output.
| Code: | # parted -l
Model: USB SanDisk 3.2Gen1 (scsi)
Disk /dev/sda: 30.8GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 30.8GB 30.7GB primary boot
2 30.8GB 30.8GB 33.6MB primary fat16 esp
Model: Samsung SSD 970 EVO Plus 1TB (nvme)
Disk /dev/nvme0n1: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 1075MB 1074MB fat32 boot, esp
2 1075MB 538GB 537GB ext4
Model: Samsung SSD 970 EVO Plus 1TB (nvme)
Disk /dev/nvme2n1: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
Model: Samsung SSD 970 EVO Plus 1TB (nvme)
Disk /dev/nvme1n1: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags |
|
|
| Back to top |
|
|
pietinger
Moderator
Joined: 17 Oct 2006
Posts: 4236
Location: Bavaria
|
| Posted: Thu Apr 13, 2023 11:41 am Post subject: |
|
|
Maybe your UEFI BIOS accepts only ONE esp-artition. Try to disable the first one:
| Code: | | parted /dev/sda set 2 boot off |
Do again your entry. |
|
| Back to top |
|
|
pietinger
Moderator
Joined: 17 Oct 2006
Posts: 4236
Location: Bavaria
|
| Posted: Thu Apr 13, 2023 11:43 am Post subject: |
|
|
Have you enabled CSM in your BIOS (if yes, disable it) ?
(sometimes CSM is also called "legacy" ... disable it !) |
|
| Back to top |
|
|
enrico68
Apprentice
Joined: 21 Oct 2016
Posts: 169
|
| Posted: Thu Apr 13, 2023 11:54 am Post subject: |
|
|
| I can confirm CSM is disabled in the BIOS, it is set to EUFI. |
|
| Back to top |
|
|
enrico68
Apprentice
Joined: 21 Oct 2016
Posts: 169
|
| Posted: Thu Apr 13, 2023 11:57 am Post subject: |
|
|
Pietinger, let me ask you this:
last night, the first time I tried to install Gentoo without the Windows 10 EFI support, after seeing it did not boot, I installed Linux Mint, to see if it loaded, which it did. The EFI partition set by Mint was mounted to /boot/efi, and it worked, I was able to boot straight into Mint. Would this information help us? |
|
| Back to top |
|
|
pietinger
Moderator
Joined: 17 Oct 2006
Posts: 4236
Location: Bavaria
|
| Posted: Thu Apr 13, 2023 12:11 pm Post subject: |
|
|
| enrico68 wrote: | | Would this information help us? |
No. because I dont know what Mint is/was doing
Let me say what you need for an UEFI boot:
1. No CSM enabled (YES)
2. GPT on your disk (YES)
3. At minimum one partition with ESP-flag (usually modern BIOS'e accepts more than one) (YES)
4. THIS partition must be formated with FAT16 OR FAT32 (UEFI specification say both must be possible; only VERY old machines accept only FAT16)
5. A binary which is capable to do an UEFI boot; like Windows OR grub OR a Linux STUB-Kernel; this binary MUST have .efi at suffix and MUST be IN the ESP in directory \efi\ OR \efi\boot\ OR \efi\custom-name\
6. An boot entry pointing to this binary ... HERE some BIOS have a problem: They dont accept additional entries and accept only a hard-coded one:
You can have ALWAYS a boot entry which is hardcoded into UEFI: \efi\boot\bootx64.efi
(This is also the name of every binary on an USB-stick; because you dont have manually made an entry for USB-sticks) |
|
| Back to top |
|
|
enrico68
Apprentice
Joined: 21 Oct 2016
Posts: 169
|
| Posted: Thu Apr 13, 2023 12:23 pm Post subject: |
|
|
| I see...from what you're telling me, it is my BIOS that only accepts hard coded boot entries, like it does with the USB stick. If that is the issue, at least I know I did not do anything wrong and I will not waste time finding a solution which is not there...did I get your reply correctly? |
|
| Back to top |
|
|
pietinger
Moderator
Joined: 17 Oct 2006
Posts: 4236
Location: Bavaria
|
| Posted: Thu Apr 13, 2023 12:32 pm Post subject: |
|
|
| enrico68 wrote: | | ...did I get your reply correctly? |
Maybe ... I dont know ... You can proof it with your Linux Mint. Check what it has done (with "efibootmgr" and look into /boot/efi). If it has done an installation for its grub as "bootx64.efi" then you know for sure ... and you can do the same with Gentoo:
| Code: | | grub-install --target=x86_64-efi --efi-directory=/boot --removable |
It is described in: https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Bootloader#Install |
|
| Back to top |
|
|
enrico68
Apprentice
Joined: 21 Oct 2016
Posts: 169
|
| Posted: Thu Apr 13, 2023 12:39 pm Post subject: |
|
|
Tha part of the handbook that you just posted it is what I was thinking about earlier, after looking at what Mint or another distro does. Let's see how far I can go.
In the meantime, a big thank you for all your support and patience, as always, you are a very kind and helpful person, and I thank you for that! 
You are just another reminder of how great the Gentoo community is, and why Gentoo is and always will be my go to Linux distro!!
Enrico |
|
| Back to top |
|
|
enrico68
Apprentice
Joined: 21 Oct 2016
Posts: 169
|
| Posted: Thu Apr 13, 2023 12:43 pm Post subject: |
|
|
Also,
a big thank you to alamahant and sMueggli, for they tried to help me out as well, they too deserve my respect! |
|
| Back to top |
|
|
pietinger
Moderator
Joined: 17 Oct 2006
Posts: 4236
Location: Bavaria
|
| Posted: Thu Apr 13, 2023 12:49 pm Post subject: |
|
|
Enrico,
you are Very Welcome ! 
If it is true that your machine does not accept manually set UEFI entries, this means you can boot only ONE efi-binary and this one must be called bootx64.efi residing IN \efi\boot\
If you use --removable it does rename your grubx64.efi into bootx64.efi (so dont be afraid if you dont find any "grubx64.efi" anymore )
(you have luck: There exists machines which only accept Microsoft Windows ... not even a bootx64.efi ... ONLY Microsoft's .efi ...  ) |
|
| Back to top |
|
|
sMueggli
Guru
Joined: 03 Sep 2022
Posts: 374
|
| Posted: Thu Apr 13, 2023 3:16 pm Post subject: |
|
|
Do you have an Acer device?
Can you please share the input and output of the "grub-install" command (from the chroot)? And after the "grub-install" the output of "efibootmgr" to see, whether a boot entry was created at runtime?
And if you install Mint again and it is booting, please check also that "Secure Boot" is disabled:
| Code: | | dmesg | grep -i Secure |
|
|
| Back to top |
|
|
Goverp
Advocate
Joined: 07 Mar 2007
Posts: 2014
|
| Posted: Fri Apr 14, 2023 7:44 am Post subject: |
|
|
| enrico68 wrote: | | I see...from what you're telling me, it is my BIOS that only accepts hard coded boot entries, like it does with the USB stick.... |
That should not be the case on any UEFI setup that obeys the rules. However, what is also true is that those rules say that a UEFI BIOS will delete any invalid bootmanager entries - that's to say ones that it determines do not locate a real bootmanager. I'm not sure what the rules are for bootmanagers on pluggable devices such as USB sticks - at a guess, delete entries that don't match the stick currently plugged in, but do nothing if there's no stick plugged in.
As an example, I tried using the kernel EFI stub arrangement with three kernels in the EFI partition, with names "vmlinuz.efi", "vmlinuz.new.efi" and "vmlinuz.old.efi", so I could load a new kernel for testing, and when satisfied, rename current as old, new as current. However, on the next boot after doing this, BIOS noticed that the entry for "vmlinuz.new.efi" no longer pointed at a real file, so it deleted it. That meant that I'd need to fiddle with efibootmgr each time I posted a new kernel (despite the unchanged name). AFAIK, it's not a good idea to keep writing to EFIvars storage, as it typically has a limited number of refresh cycles available (in thousands, but not millions), so I gave up and installed GRUB instead!
Net of this is that if your BIOS clears a bootmanager entry, it means the BIOS can't locate a valid bootmanger where the entry pointed, so either the path is wrong, or for some reason the file located does not appear to be a valid boot manager; I don't know what criteria apply to determine "valid".
_________________
Greybeard |
|
| Back to top |
|
|
pietinger
Moderator
Joined: 17 Oct 2006
Posts: 4236
Location: Bavaria
|
| Posted: Fri Apr 14, 2023 11:14 am Post subject: |
|
|
| Goverp wrote: | | [...] AFAIK, it's not a good idea to keep writing to EFIvars storage, as it typically has a limited number of refresh cycles available (in thousands, but not millions), so I gave up and installed GRUB instead! |
YES, it is not good to change all the time EFIvars ... but it is not necessary to do it. I am using UEFI as my bootmanager and I am doing it this way:
I have two kernels in two directories: \efi\unlocked\bzImage.efi and \efi\secure\bzImage.efi with two UEFI entries pointing to them. When I get a new kernel version of my running kernel I just overwrite the old one in \efi\secure\ ... IF the rare case happens there is a problem with this new kernel THEN I can boot my "backup" kernel in \efi\unlocked (this kernel I update once a year). No need to change or update my existing UEFI entries.
Therefore IMHO the recommendation to create an UEFI entry pointing to a specific kernel version, in our Wiki, is wrong:
https://wiki.gentoo.org/wiki/Efibootmgr#Creating_a_boot_entry |
|
| Back to top |
|
|
|
Installing Gentoo
