Thankyou for the help.
Thanks to your help, I am now typing this from LEAP-15.3 running the 5.14.11 kernel. For info:
oldcpu@localhost:~> uname -a
Linux localhost 5.14.11-lp153.2.g834dddd-default #1 SMP Sun Oct 10 08:34:34 UTC 2021 (834dddd) x86_64 x86_64 x86_64 GNU/Linux
DETAILS (for any who may be curious):
The first time when running LEAP-15.3 from the 5.3.18 kernel (also with the 5.14.11 kernel installed from before) when I tried ‘mokutil’ command to import the key, I did so from /home/oldcpu, and of course it failed (with an error message it could not find the file status). I was not thinking, as when running the command the bash shell either needed to be in the /etc/uefi/certs subdirectory, or the path was needed. So I changed to the /etc/uefi/certs subdirectory and tried again with:
localhost:/etc/uefi/certs # mokutil --import 6A4E915C.crt --root-pw
That gave no error message, just a return of the root prompt, which I took as a good sign. So I rebooted and immediately obtained this in a blue screen:
Shim UEFI key management" and asked to "Press any key to perform MOK management"
I immeadiately pressed a key.
I was then presented with this menu (as before) where I had to choose:[INDENT]* continue boot
- enroll MOK
- enroll key from disk
- enroll hash from disk
[/INDENT]
This time I chose “enroll MOK”. That then presented me with this screen:[INDENT] * View key 0
- Continue
[/INDENT]
I had no idea what “View key 0” was for, so I elected to ignore that and I selected “continue” … That then presented me with this:[INDENT] Enroll the key(s)?
.
- No
- Yes
[/INDENT]
I selected “Yes” and I was prompted with a blue screen asking for a “Password”. I entered the root password. I then obtained this screen:[INDENT]Perform MOK management
.
- reboot
- Enroll key from disk
- Enroll hash from disk
[/INDENT]
I already knew that 'enrolling key from disk was the wrong approach, … and I decided if my previous actions (with entering the root password) were correct, then a reboot likely appropriate, so I selected ‘reboot’.
The PC rebooted, I selected to boot to the 5.14.11 kernel in the grub menu, and this time I had a boot success to the 5.14.11 kernel.
I am now posting immediately after that. I have yet to explore this new kernel, … and pretty much all the kernel related apps I have still installed are associated with the older 5.3.18 kernel, where I may wish to update all those other kernel related apps (but I have not done so yet). I suspect I also may wish to update the intel-media-driver app as well to a newer version.
Many thanks again to all on this thread for your help. I was DEFINITELY out of my comfort zone here … and maybe thats a good thing.
I was pleased (thanks to your help) that I was able to do this without disabling the secure boot.