[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [sid] efibootmgr not working on linux 5.10.x & LGA1155



Hi!

pld@sojka.co wrote:
>On 4/10/21 7:52 PM, Sven Joachim wrote:
>> On 2021-04-08 22:30 +0200, Grzesiek wrote:
>>>
>>> The problem seems to be related to 5.10.x kernels & LGA1155 based systems.
>>>
>>> 1. On laptop based on i5-8250u efibootmgr works fine (all kernel versions)
>>>
>>> 2. On systems based on LGA1155 socket (i5-2500k, i7-3770):
>>> - kernels 5.10.x: efibootmgr does not work,
>>> directory /sys/firmware/efi/efivars is empty
>>> - kernel 5.8.0-2: efibootmgr woks as expected
>>>
>>> On 5.8.0-2 i get:
>>>
>>> # lsmod | grep efi
>>> efivarfs               16384  0
>>> efi_pstore             16384  0
>>> efivars                20480  1 efi_pstore
>>>
>>> There is no efivars.ko in 5.10.x. Maybe that is the problem?
>> 
>> The efivars module has indeed been removed from Debian's 5.10 kernels,
>> as it had been deprecated in favor of efivarfs for a while.
>> 
>> Which versions of efibootmgr and libefivar1 do you have installed?
>
>The problem persists since several months. Now I have:
>
># apt-list | grep efi
>efibootmgr/unstable,now 17-1 amd64 [installed]
>libefiboot1/unstable,now 37-6 amd64 [installed,automatic]
>libefivar1/unstable,now 37-6 amd64 [installed,automatic]

This line:

efivarfs               16384  0

suggests the cause of the problem for you. efibootmgr (and other tools
using libefivar) will look into both:

 * /sys/firmware/efi/vars (the old, deprecated interface that was
   removed in 5.10)
 * /sys/firmware/efi/efivars (the new interface, provided by efivarfs)

As you have efivarfs loaded but with use-count of 0, that suggests
that you don't have the efivarfs pseudo-filesystem mounted. This
should normally be automatically mounted on system boot, along with
the other pseudo-filesystems like /sys and /proc.

-- 
Steve McIntyre, Cambridge, UK.                                steve@einval.com
"We're the technical experts.  We were hired so that management could
 ignore our recommendations and tell us how to do our jobs."  -- Mike Andrews


Reply to: