EFI stub: WARNING: Failed to measure data for event 1: 0x800000000000000b

English Install/Boot/Login
21

Thanks for that Malcom, on the Nvidia MOK thing as I have the Nvidia Repo set up does that contain the relevant signature or do I need to download or add one? I saw there were some changes to these in June 2024. If so where would I get them from?
Do I need to install MOK tools before for the blue screen selection thing to work with the above on a reboot or should that just work?

22

Nvidia will build their kmp when you install the nvidia-driver-G0(x)-kmp-default.
It will generate a Signature and add them to enroll on next reboot.
There you have to add it.
see:
Mok Example

Only mokutil is installed here:

zypper se -si mok
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...

S  | Name    | Type  | Version          | Arch   | Repository
---+---------+-------+------------------+--------+-----------
i+ | mokutil | Paket | 0.5.0-150600.8.3 | x86_64 | OSS
23

But you have disabled secure boot?

So no key will be build when installing the nvidia-kmp.

24

Thanks for that - I was thinking of turning on the Windows UEFI secrue boot option rather than other OS that I currently have. Assuming that would then do the MOK thing but wanted to check if I would have the correct signature etc. before trying that. I have the GO6-kmp-default Installed so that should be signed or create one then? I also have the MOKutil you mentioned - so I should be good to go with UEFI Secure boot then?

My system seems to boot & work OK despite the EFI Stub warning - so maybe I shouldnā€™t worry about that?

25

JFYI: Had this message some time ago, which disapppeared with kernel >= 6.16.4.

26

Ah thanks for the info Linux 6.16.3-1-default so maybe this weeks latest update which Iā€™ve just done might get me onto 6.16.4?

27

When secure boot isnā€™t enabled, there are no signing files in ls -al /usr/share/nvidia-pubkeys/
So you have to install the nvidia-driver-G0(x)-kmp-default once more after switching to secure boot.

But do you need secure boot??

28

TW20250904 still has kernel 6.16.3. You might want to try kernel stable from https://download.opensuse.org/repositories/Kernel:/stable/standard/

29

Then he can only use the nvidia.run file, no file from Nvidia Repo.

30

You are right, then he has to wait for one of the next TW snapshots (kernel 6.16.5 was submitted to factory yesterday).

31

I just tried a shut down and reboot after doing the latest DUP update from this week. Weirdly didnā€™t get the EFI Stub message this time even though Iā€™m still on 6.16.3 - so maybe something else in the update sorted it. I donā€™t think I need secure boot so I think Iā€™ll stay as I am currently set up on the basis of if it ainā€™t broke donā€™t fix. Thanks for all your thoughts and input. Not sure if this will have solved if for the original poster of this thread?

32

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.