Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Paul Menzel <pmenzel@molgen.mpg.de>
Subject: efivarfs fails with `No such device` when EFI runtime is missing
To:     Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc:     linux-efi@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Message-ID: <b075e45e-365a-dafb-503c-615c41168b0d@molgen.mpg.de>
Date:   Tue, 11 May 2021 22:55:03 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.10.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Precedence: bulk

Dear Linux folks,


I migrated a 32-bit GNU/Linux installation from BIOS to EFI. Trying to 
edit the entries in UEFI’s Boot Manager with `efibootmgr`, I got the error:

     EFI variables are not supported on this system

`sudo modprobe efivarfs` fails with

     No such device

After several tries, I found

     [    0.000000] efi: No EFI runtime due to 32/64-bit mismatch with 
kernel

logged by Linux, and then I found the Stack Overflow thread *How could 
32bit kernel read efivars from 64bit UEFI?* [1].

I would have thought, setting EFI variables is just directly writing to 
some storage. But probably not.

Could the error message for the efivarfs load failure be improved, that 
*device* means the runtime service (if I am not mistaken)?


Kind regards,

Paul


[1]: 
https://stackoverflow.com/questions/46610442/how-could-32bit-kernel-read-efivars-from-64bit-uefi