[SOLVED] Re: [gentoo-user] WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict

[Valmor F. de Almeida]

On 7/3/20 10:51 PM, Francesco Turco wrote:

On Sat, Jul 4, 2020, at 06:35, Valmor F. de Almeida wrote:

Is there a problem ignoring the warning below? My understanding here is
that dev-python/docutils-0.16 wants a python2_7 target built that is not
in the scheduled merge (only python3_7 is). Hopefully this dependency
conflict will fix itself as python2 goes away.

Please see: https://bugs.gentoo.org/722762


This was gentoo fast.

Thanks.
--
Valmor

Re: [gentoo-user] WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict

[Francesco Turco]

On Sat, Jul 4, 2020, at 06:35, Valmor F. de Almeida wrote:
> Is there a problem ignoring the warning below? My understanding here is 
> that dev-python/docutils-0.16 wants a python2_7 target built that is not 
> in the scheduled merge (only python3_7 is). Hopefully this dependency 
> conflict will fix itself as python2 goes away.

Please see: https://bugs.gentoo.org/722762

-- 
https://fturco.net/

Re: [gentoo-user] Encrypted drive setup at login and locking on logout.

[Francesco Turco]

On Sat, Jul 4, 2020, at 04:23, Dale wrote:
>  Now that I have a spare drive, I want to encrypt it and have a mount point 
> for it, /home/dale/documents for example. What I'd like to do, when I login 
> in, it asks me for the encryption password and then mounts it. When I log 
> out, it reverses. I'm not doing all of /home because I want to separate some 
> info. I may do it later. 

I would use LUKS (warning: all data on the spare drive will be lost):
0. Partition the spare drive: parted /dev/sdx
1. Format the drive's partition with LUKS: cryptsetup luksFormat /dev/sdxn
2. Decrypt the LUKS partition: cryptsetup luksOpen /dev/sdxn documents
3. Create a filesystem on the decrypted partition: mke2fs -t ext4 -m 0 
/dev/mapper/documents
4. Add the new filesystem to /etc/fstab (use the UUID for easier matching)
5. Mount the filesystem: mount /home/dale/documents

In order to close the filesystem, you need the following steps:
1. Unmount the filesystem: umount /home/dale/documents
2. Lock the LUKS partition: cryptsetup luksClose documents

Since you use KDE you may try Vault instead, but I haven't tested that 
personally.

-- 
https://fturco.net/

[gentoo-user] WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict

[Valmor F. de Almeida]

Hello list:

Is there a problem ignoring the warning below? My understanding here is 
that dev-python/docutils-0.16 wants a python2_7 target built that is not 
in the scheduled merge (only python3_7 is). Hopefully this dependency 
conflict will fix itself as python2 goes away.



Thank you for inputs.
--
Valmor


WARNING: One or more updates/rebuilds have been skipped due to a 
dependency conflict:


dev-python/pygments:0

  (dev-python/pygments-2.6.1:0/0::gentoo, ebuild scheduled for merge) 
USE="-doc -test" ABI_X86="(64)" PYTHON_TARGETS="python3_7 (-pypy3) 
-python3_6 (-python3_8) (-python3_9)" conflicts with
dev-python/pygments[python_targets_python2_7(-),python_targets_python3_7(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-),-python_single_target_python3_9(-)] 
required by (dev-python/docutils-0.16:0/0::gentoo, installed) USE="" 
ABI_X86="(64)" PYTHON_TARGETS="python2_7 python3_7 (-pypy3) -python3_6 
(-python3_8) (-python3_9)"

[gentoo-user] Re: custom mount fstab

[Nikos Chantziaras]

On 03/07/2020 16:33, Tamer Higazi wrote:

Hi people,

I had a problem with docker on gentoo and found the solution for all my 
problems with a custom mount command:


|sudo mount -t cgroup -o none,name=systemd cgroup /sys/fs/cgroup/systemd 
Can anybody of you tell me how to add that one in /etc/fstab file ? 


I use docker and I don't have to add anything like that to fstab. 
systemd mounts it automatically. However:


https://wiki.gentoo.org/wiki/Docker#Docker_service_fails_because_cgroup_device_not_mounted_.28systemd.29

So make sure to emerge systemd with the "cgroup-hybrid" USE flag set.

[gentoo-user] Encrypted drive setup at login and locking on logout.

[Dale]

Howdy,

As some know, I been playing with encryption recently.  I got doing it
on the command line and using veracrypt for USB sticks down.  I use
Veracrypt for those that I want to work on windoze as well, I hope
anyway.  Now I'm moving on to something else. 

Now that I have a spare drive, I want to encrypt it and have a mount
point for it, /home/dale/documents for example.  What I'd like to do,
when I login in, it asks me for the encryption password and then mounts
it.  When I log out, it reverses.  I'm not doing all of /home because I
want to separate some info.  I may do it later. 

I did some googling but maybe my search terms aren't good enough.  I
mostly find for /home as a whole but not separate parts of it.  When I
add in Gentoo does some things differently, it may be that this isn't
even doable.  Also, my user password and password for the encryption
will be different.  I'm using KDE but anything that will work as part of
KDE or along with KDE will be fine with me. 

Does anyone have a howto they can link to?  Is this even doable? 

Thanks.

Dale

:-)  :-) 

Re: [gentoo-user] USB ext2 flash drive - No space left on device

[Dale]

the...@sys-concept.com wrote:
> On 07/03/2020 03:12 PM, the...@sys-concept.com wrote:
>> I have a USB flash drive with ext2 file system and when I try to copy a
>> file I get an error "No space left on device"
>>
>> df -Th
>> Filesystem Type  Size  Used Avail Use% Mounted on
>> /dev/sdb1  ext2  944M  1.4M  943M   1% /run/media/thelma/UUI
>>
>> df -i
>> Filesystem   Inodes  IUsedIFree IUse% Mounted on
>> /dev/sdb1 61440 21614191% /run/media/thelma/UUI
>>
> Here is more info:
>
> tune2fs -l /dev/sdb1
> tune2fs 1.43.6 (29-Aug-2017)
> Filesystem volume name:   UUI
> Last mounted on:  /run/media/thelma/UUI
> Filesystem UUID:  4348ab9b-f3ec-4908-b11b-73a460882cd5
> Filesystem magic number:  0xEF53
> Filesystem revision #:1 (dynamic)
> Filesystem features:  ext_attr resize_inode dir_index filetype
> sparse_super large_file
> Filesystem flags: signed_directory_hash
> Default mount options:user_xattr acl
> Filesystem state: not clean with errors
> Errors behavior:  Continue
> Filesystem OS type:   Linux
> Inode count:  61440
> Block count:  245504
> Reserved block count: 0
> Free blocks:  241291
> Free inodes:  61419
> First block:  0
> Block size:   4096
> Fragment size:4096
> Reserved GDT blocks:  59
> Blocks per group: 32768
> Fragments per group:  32768
> Inodes per group: 7680
> Inode blocks per group:   480
> Filesystem created:   Wed Oct  7 08:28:52 2015
> Last mount time:  Fri Jul  3 15:25:24 2020
> Last write time:  Fri Jul  3 15:27:21 2020
> Mount count:  2594
> Maximum mount count:  -1
> Last checked: Wed Oct  7 08:28:52 2015
> Check interval:   0 ()
> Lifetime writes:  61 MB
> Reserved blocks uid:  0 (user root)
> Reserved blocks gid:  0 (group root)
> First inode:  11
> Inode size: 256
> Required extra isize: 28
> Desired extra isize:  28
> Default directory hash:   half_md4
> Directory Hash Seed:  dbea2a4c-9588-4364-a8de-96e68f24db09
> FS Error count:   126
> First error time: Sat Jun  6 19:33:04 2020
> First error function: mb_free_blocks
> First error line #:   1470
> First error inode #:  13
> First error block #:  1589
> Last error time:  Fri Jul  3 15:27:21 2020
> Last error function:  __ext4_new_inode
> Last error line #:884
> Last error inode #:   0
> Last error block #:   0
>
>


I notice this little bit.


Filesystem state: not clean with errors

and

FS Error count:   126


It may be that it was removed while still mounted.  Maybe a file system
check would help??

I did some googling.  For the instances I found like this, people took
all files off the USB device, re-partitioned and reformatted the device
and then copied the files back.  That seemed to be the cleanest and
easiest solution.  If checking the file system doesn't help, that may be
your next option.  I might add, some had to do that with new USB sticks
straight out of the box.

I also saw mentions of inodes but generally, that didn't turn out to be
the problem.  I think you can check those with df -i. 

Hope that helps or someone else comes along with a better idea.

Dale

:-)  :-) 

Re: [gentoo-user] USB ext2 flash drive - No space left on device

[thelma]

On 07/03/2020 03:52 PM, Jack wrote:
[snip]
> 
> This looks like a possible issue.
>> Filesystem state: not clean with errors
> I'd start by unmounting it and trying fsck.

I run few time: fsck.ext2 /dev/sdb1
and it fixed the problem.

Re: [gentoo-user] USB ext2 flash drive - No space left on device

[Jack]

On 2020.07.03 17:38, the...@sys-concept.com wrote:

On 07/03/2020 03:12 PM, the...@sys-concept.com wrote:
> I have a USB flash drive with ext2 file system and when I try to  
copy a

> file I get an error "No space left on device"
>
> df -Th
> Filesystem Type  Size  Used Avail Use% Mounted on
> /dev/sdb1  ext2  944M  1.4M  943M   1% /run/media/thelma/UUI
>
> df -i
> Filesystem   Inodes  IUsedIFree IUse% Mounted on
> /dev/sdb1 61440 21614191% /run/media/thelma/UUI
>

Here is more info:

tune2fs -l /dev/sdb1
tune2fs 1.43.6 (29-Aug-2017)
Filesystem volume name:   UUI
Last mounted on:  /run/media/thelma/UUI
Filesystem UUID:  4348ab9b-f3ec-4908-b11b-73a460882cd5
Filesystem magic number:  0xEF53
Filesystem revision #:1 (dynamic)
Filesystem features:  ext_attr resize_inode dir_index filetype
sparse_super large_file
Filesystem flags: signed_directory_hash
Default mount options:user_xattr acl
Filesystem state: not clean with errors
Errors behavior:  Continue
Filesystem OS type:   Linux
Inode count:  61440
Block count:  245504
Reserved block count: 0
Free blocks:  241291
Free inodes:  61419
First block:  0
Block size:   4096
Fragment size:4096
Reserved GDT blocks:  59
Blocks per group: 32768
Fragments per group:  32768
Inodes per group: 7680
Inode blocks per group:   480
Filesystem created:   Wed Oct  7 08:28:52 2015
Last mount time:  Fri Jul  3 15:25:24 2020
Last write time:  Fri Jul  3 15:27:21 2020
Mount count:  2594
Maximum mount count:  -1
Last checked: Wed Oct  7 08:28:52 2015
Check interval:   0 ()
Lifetime writes:  61 MB
Reserved blocks uid:  0 (user root)
Reserved blocks gid:  0 (group root)
First inode:  11
Inode size:   256
Required extra isize: 28
Desired extra isize:  28
Default directory hash:   half_md4
Directory Hash Seed:  dbea2a4c-9588-4364-a8de-96e68f24db09
FS Error count:   126
First error time: Sat Jun  6 19:33:04 2020
First error function: mb_free_blocks
First error line #:   1470
First error inode #:  13
First error block #:  1589
Last error time:  Fri Jul  3 15:27:21 2020
Last error function:  __ext4_new_inode
Last error line #:884
Last error inode #:   0
Last error block #:   0


This looks like a possible issue.

Filesystem state: not clean with errors

I'd start by unmounting it and trying fsck.

Re: [gentoo-user] USB ext2 flash drive - No space left on device

[thelma]

On 07/03/2020 03:12 PM, the...@sys-concept.com wrote:
> I have a USB flash drive with ext2 file system and when I try to copy a
> file I get an error "No space left on device"
> 
> df -Th
> Filesystem Type  Size  Used Avail Use% Mounted on
> /dev/sdb1  ext2  944M  1.4M  943M   1% /run/media/thelma/UUI
> 
> df -i
> Filesystem   Inodes  IUsedIFree IUse% Mounted on
> /dev/sdb1 61440 21614191% /run/media/thelma/UUI
> 

Here is more info:

tune2fs -l /dev/sdb1
tune2fs 1.43.6 (29-Aug-2017)
Filesystem volume name:   UUI
Last mounted on:  /run/media/thelma/UUI
Filesystem UUID:  4348ab9b-f3ec-4908-b11b-73a460882cd5
Filesystem magic number:  0xEF53
Filesystem revision #:1 (dynamic)
Filesystem features:  ext_attr resize_inode dir_index filetype
sparse_super large_file
Filesystem flags: signed_directory_hash
Default mount options:user_xattr acl
Filesystem state: not clean with errors
Errors behavior:  Continue
Filesystem OS type:   Linux
Inode count:  61440
Block count:  245504
Reserved block count: 0
Free blocks:  241291
Free inodes:  61419
First block:  0
Block size:   4096
Fragment size:4096
Reserved GDT blocks:  59
Blocks per group: 32768
Fragments per group:  32768
Inodes per group: 7680
Inode blocks per group:   480
Filesystem created:   Wed Oct  7 08:28:52 2015
Last mount time:  Fri Jul  3 15:25:24 2020
Last write time:  Fri Jul  3 15:27:21 2020
Mount count:  2594
Maximum mount count:  -1
Last checked: Wed Oct  7 08:28:52 2015
Check interval:   0 ()
Lifetime writes:  61 MB
Reserved blocks uid:  0 (user root)
Reserved blocks gid:  0 (group root)
First inode:  11
Inode size:   256
Required extra isize: 28
Desired extra isize:  28
Default directory hash:   half_md4
Directory Hash Seed:  dbea2a4c-9588-4364-a8de-96e68f24db09
FS Error count:   126
First error time: Sat Jun  6 19:33:04 2020
First error function: mb_free_blocks
First error line #:   1470
First error inode #:  13
First error block #:  1589
Last error time:  Fri Jul  3 15:27:21 2020
Last error function:  __ext4_new_inode
Last error line #:884
Last error inode #:   0
Last error block #:   0

[gentoo-user] USB ext2 flash drive - No space left on device

[thelma]

I have a USB flash drive with ext2 file system and when I try to copy a
file I get an error "No space left on device"

df -Th
Filesystem Type  Size  Used Avail Use% Mounted on
/dev/sdb1  ext2  944M  1.4M  943M   1% /run/media/thelma/UUI

df -i
Filesystem   Inodes  IUsedIFree IUse% Mounted on
/dev/sdb1 61440 21614191% /run/media/thelma/UUI

-- 
Thelma

Re: [gentoo-user] EFI booting problem - understanding it

[Sid Spry]

On Fri, Jul 3, 2020, at 9:52 AM, Peter Humphrey wrote:
> On Friday, 3 July 2020 03:05:34 BST Andrew Udvare wrote:
> > On 02/07/2020 06:56, Peter Humphrey wrote:
> > > But then,
> > > # bootctl set-default 30-gentoo-5.7.7.conf
> > > Failed to update EFI variable: Invalid argument
> > 
> > Probably the kernel is blocking write access to EFI. This is on purpose
> > for safety as you can damage your firmware quite easily. systemd-boot
> > and others do not have this restriction.
> 
> Is there some way for me to remove this restriction temporarily?
> 
> > You also should be careful writing to the EFI too much as the NVRAM flash 
> > may
> > not be of high quality.
> 
> Yes, I do only write to it when I have to. I hope Asus would use decent-
> quality components though.
> 

They may not have a choice. The flash memory made for "embedded" applications 
can be very low quality.
Typically I see write capability maxing out at 100k. Some devices only offer 
10k due to inappropriate cost optimization. These numbers can be particularly 
visible if there is no wear levelling, which there usually isn't.

Anything higher seems to be only available for storage applications.

> > https://lwn.net/Articles/674940/
> 
> Interesting - thanks.
> 
> > You can try using `chattr -i` against the files like:
> > 
> > chattr -i /sys/firmware/efi/efivars/Boot*
> > 
> > Then you can try with bootctl and others, but this is not guaranteed to
> > work.
> 
> Those files were already among the 17 that were mutable. It seems I 
> need to find 
> which of the other 117 files I need to make mutable.
> 
> > On my ASUS motherboard I haven't been able to write to EFI variables
> > from within Linux for a long time. I have to add my keys in the BIOS and
> > set the default in systemd-boot.
> 
> Looks like I'm in the same boat. Except that setting the default in systemd-
> boot is exactly what I can't do!
> 
> > The logic to write to a file in efivars is here:
> > 
> > https://github.com/torvalds/linux/blob/master/fs/efivarfs/file.c#L15
> > 
> > If you use strace with bootctl you'll probably see one of these errno
> > values.
> 
> I think what I'm seeing comes from this:
> 
> if (attributes & ~(EFI_VARIABLE_MASK))
>   return -EINVAL;
> 
> Perhaps I should just stop here and revert to setting the default at the UEFI 
> boot-choice screen.
> 
> Many thanks for your help, Andrew.
> 
> -- 
> Regards,
> Peter.
> 
> 
> 
> 
>

[gentoo-user] custom mount fstab

[Tamer Higazi]

Hi people,

I had a problem with docker on gentoo and found the solution for all my 
problems with a custom mount command:


|sudo mount -t cgroup -o none,name=systemd cgroup /sys/fs/cgroup/systemd 
Can anybody of you tell me how to add that one in /etc/fstab file ? 
best, Tamer |

Re: [gentoo-user] EFI booting problem - understanding it

[Peter Humphrey]

On Friday, 3 July 2020 03:05:34 BST Andrew Udvare wrote:
> On 02/07/2020 06:56, Peter Humphrey wrote:
> > But then,
> > # bootctl set-default 30-gentoo-5.7.7.conf
> > Failed to update EFI variable: Invalid argument
> 
> Probably the kernel is blocking write access to EFI. This is on purpose
> for safety as you can damage your firmware quite easily. systemd-boot
> and others do not have this restriction.

Is there some way for me to remove this restriction temporarily?

> You also should be careful writing to the EFI too much as the NVRAM flash may
> not be of high quality.

Yes, I do only write to it when I have to. I hope Asus would use decent-
quality components though.

> https://lwn.net/Articles/674940/

Interesting - thanks.

> You can try using `chattr -i` against the files like:
> 
> chattr -i /sys/firmware/efi/efivars/Boot*
> 
> Then you can try with bootctl and others, but this is not guaranteed to
> work.

Those files were already among the 17 that were mutable. It seems I need to 
find 
which of the other 117 files I need to make mutable.

> On my ASUS motherboard I haven't been able to write to EFI variables
> from within Linux for a long time. I have to add my keys in the BIOS and
> set the default in systemd-boot.

Looks like I'm in the same boat. Except that setting the default in systemd-
boot is exactly what I can't do!

> The logic to write to a file in efivars is here:
> 
> https://github.com/torvalds/linux/blob/master/fs/efivarfs/file.c#L15
> 
> If you use strace with bootctl you'll probably see one of these errno
> values.

I think what I'm seeing comes from this:

if (attributes & ~(EFI_VARIABLE_MASK))
return -EINVAL;

Perhaps I should just stop here and revert to setting the default at the UEFI 
boot-choice screen.

Many thanks for your help, Andrew.

-- 
Regards,
Peter.

Re: [gentoo-user] custom mount fstab

[Tamer Higazi]

Hi Andrew,

it's on systemd.

Previously I had problems connecting with docker.
After I searched on Github, docker ran then without any problems at all.


best, Tamer

Am 3 Jul 2020 um 16:04 schrieb Andrew Udvare:



On Fri, Jul 3, 2020, 09:34 Tamer Higazi > wrote:


Hi people,

I had a problem with docker on gentoo and found the solution for
all my
problems with a custom mount command:

|sudo mount -t cgroup -o none,name=systemd cgroup
/sys/fs/cgroup/systemd
Can anybody of you tell me how to add that one in /etc/fstab file ?
best, Tamer |


Docker on OpenRC or systemd?

Also with the new cgroups or old?

AFAIK Docker doesn't work or support the new cgroups. :/

Re: [gentoo-user] custom mount fstab

[Tamer Higazi]

Thanks Michael!

I'll give it a try.


best, Tamer

Am 3 Jul 2020 um 15:46 schrieb Michael:

On Friday, 3 July 2020 14:33:52 BST Tamer Higazi wrote:

Hi people,

I had a problem with docker on gentoo and found the solution for all my

problems with a custom mount command:
|sudo mount -t cgroup -o none,name=systemd cgroup /sys/fs/cgroup/systemd

Can anybody of you tell me how to add that one in /etc/fstab file ?
best, Tamer |

I haven't used cgroups or docker, but if your mount command above is correct,
I assume something like this ought to work as far as fstab is concerned:

cgroup  /sys/fs/cgroup/systemd  cgroup  none,name=systemd  0 1

Re: [gentoo-user] custom mount fstab

[Andrew Udvare]

On Fri, Jul 3, 2020, 09:34 Tamer Higazi  wrote:

> Hi people,
>
> I had a problem with docker on gentoo and found the solution for all my
> problems with a custom mount command:
>
> |sudo mount -t cgroup -o none,name=systemd cgroup /sys/fs/cgroup/systemd
> Can anybody of you tell me how to add that one in /etc/fstab file ?
> best, Tamer |
>

Docker on OpenRC or systemd?

Also with the new cgroups or old?

AFAIK Docker doesn't work or support the new cgroups. :/

Re: [gentoo-user] custom mount fstab

[Michael]

On Friday, 3 July 2020 14:33:52 BST Tamer Higazi wrote:
> Hi people,
> 
> I had a problem with docker on gentoo and found the solution for all my
> 
> problems with a custom mount command:
> |sudo mount -t cgroup -o none,name=systemd cgroup /sys/fs/cgroup/systemd
> 
> Can anybody of you tell me how to add that one in /etc/fstab file ?
> best, Tamer |

I haven't used cgroups or docker, but if your mount command above is correct, 
I assume something like this ought to work as far as fstab is concerned:

cgroup  /sys/fs/cgroup/systemd  cgroup  none,name=systemd  0 1



signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] EFI booting problem - understanding it

[Michael]

On Friday, 3 July 2020 03:05:34 BST Andrew Udvare wrote:
> Morning all,
> 
> I'm trying to set the default boot entry via bootctl or efibootmgr. I know I
> can set it directly by pressing D at the boot selection screen, and the
> system does boot properly; I just want to understand the setup a bit
> better. I don't have the rest of systemd: this is an openrc box.
> 
> # tree -L 3 /boot
> /boot
> ├── config-5.4.48-gentoo
> ├── config-5.4.48-gentoo-rescue
> ├── config-5.7.6-gentoo
> ├── config-5.7.7-gentoo
> ├── early_ucode.cpio
> ├── EFI
> │   ├── Boot
> │   │   └── bootx64.efi
> │   ├── Linux
> │   ├── Microsoft
> │   │   ├── Boot
> │   │   └── Recovery
> │   └── systemd
> │   └── systemd-bootx64.efi
> ├── intel-uc.img
> ├── loader
> │   ├── entries
> │   │   ├── 08-gentoo-5.4.48-rescue.conf
> │   │   ├── 09-gentoo-5.4.48-rescue.nonet.conf
> │   │   ├── 30-gentoo-5.7.7.conf
> │   │   ├── 32-gentoo-5.7.7.nox.conf
> │   │   ├── 34-gentoo-5.7.7.nonet.conf
> │   │   ├── 40-gentoo-5.4.48.conf
> │   │   ├── 42-gentoo-5.4.48.nox.conf
> │   │   └── 44-gentoo-5.4.48.nonet.conf
> │   ├── loader.conf
> │   └── random-seed
> ├── System.map-5.4.48-gentoo
> ├── System.map-5.4.48-gentoo-rescue
> ├── System.map-5.7.6-gentoo
> ├── System.map-5.7.7-gentoo
> ├── vmlinuz-5.4.48-gentoo
> ├── vmlinuz-5.4.48-gentoo-rescue
> ├── vmlinuz-5.7.6-gentoo
> └── vmlinuz-5.7.7-gentoo
> 
> # bootctl status
> --->8
> Default Boot Loader Entry:
> title: Gentoo 5.4.48 (No network)
>id: 44-gentoo-5.4.48.nonet.conf
> --->8
> 
> 44-gentoo-5.4.48.nonet.conf is the last entry in /boot/loader/entries.
> 
> Man bootctl says:
> set-default ID, set-oneshot ID
>  Sets the default boot loader entry. Takes a single boot loader entry ID
> string as argument...
> 
> But then,
> # bootctl set-default 30-gentoo-5.7.7.conf
> Failed to update EFI variable: Invalid argument
> 
> ...in spite of this:
> # cat /boot/loader/entries/30-gentoo-5.7.7.conf
> title Gentoo 5.7.7
> version 5.7.7-gentoo
> linux vmlinuz-5.7.7-gentoo
> initrd=intel-uc.img
> options root=/dev/nvme0n1p4 net.ifnames=0 raid=noautodetect
> 
> ...and this:
> # mount | grep efi
> efivarfs on /sys/firmware/efi/efivars type efivarfs
> (rw,nosuid,nodev,noexec,relatime)
> 
> I've also tried telling efibootmgr to set the default.
> 
> # efibootmgr
> BootNext: 0007
> BootCurrent: 0007
> Timeout: 2 seconds
> BootOrder: 000B,0007,0006,,000C,000D
> Boot* Windows Boot Manager
> Boot0006* UEFI OS
> Boot0007* Linux Boot Manager
> Boot000B* CD/DVD Drive
> Boot000C* Hard Drive
> Boot000D* Removable Drive
> 
> Efibootmgr -n 7 seems to make no difference, as expected, but:
> # efibootmgr -N 7
> Boot entry 0001 does not exist

I can't comment on the systemd's bootctl, because I don't use it, by as I 
understand it 'efibootmgr --delete-bootnext' will clear the BootNext entry in 
UEFI settings and does not take a boot entry number as a variable on the CLI.  
I can't answer why "7" in your entry above returns a comment about "Boot entry 
0001" ... which is obviously absent.


signature.asc
Description: This is a digitally signed message part.