"Wrong EFI loader signature" boot message - but it boots anyway

[retry3]

I am running fossapup64 off live CD.
During boot up, right after it says it is loading initrd, comes a starred statement "Wrong EFI loader signature".
the boot up continues and I eventually get into Fossapup64, OK as far as I can tell.

Should I be concerned about the Wrong Signature message ?
I am old and slow and a permanent beginner.
Thanks

[ozsouth]

@retry3 - consensus from internet is "if it works, don't worry". I last saw this message when booting recent puppies on non-uefi hardware, even though I used a non-uefi bootloader (grub4dos). For uefi machines, having secure boot & tpm disabled in bios & using syslinux bootloader instead of grub, I do not get this message.

[user1111]

Just ignore it. Unless you're specifically booting using secure methods/signatures. For BIOS ...etc. type boots (which I boot myself and see the same message) no efi signature will even exist so the system is just flagging that the signature was wrong.

[retry3]

Thanks ozsouth & rufwoOf, much appreciated,

[mikewalsh]

@retry3:-

Yup, I'll confirm that. The set-up I use is like many here; a UEFI system, but booting in 'legacy' mode. I get the same message, too.....but since Fossapup boots and runs just fine, as Ruffers says, "if it works, why worry?"

I'd ignore it, personally.

Mike.

[bigpup]

What is the computer?
Make and model?

[retry3]

@Mikewalsh -
Thanks, that sort of clears things up a little more.

@bigpup - Sorry for not including full info, trying to save on keystrokes;
PC make: Lenovo
Model: 7637AC6 (desktop) ThinkCentre
Intel(R) Core(TM) 2 Duo CPU
Ram 4.00 GB
BIOS - LENOVO 5CKT54AUS, 9/7/2009
Windows 10

Bought 2018 refurbished
Is there a Puppy command that will show the system info the same way as Windows does ?

Thanks to all

[rockedge]

Is there a Puppy command that will show the system info the same way as Windows does ?

Yes,
Menu -> System -> Pup-Sysinfo and then Sys-Specs -> Base Report

[bigpup]

BIOS - LENOVO 5CKT54AUS, 9/7/2009

If this is a UEFI bios and it is that old.
They were still trying to get all the bugs out of UEFI and still working on exactly what it would or would not do.
There really was no set way for it to work, what it would look for, how it would react, etc....
A lot of it was up to the computer manufactures and how they wanted their UEFI to work.

The last few years everyone has settled on what UEFI would do and how it would work.

I wonder if that warning is just telling you that something other than Windows is trying to be used.
Puppy Linux is not providing the expected signature that Windows will provide.

As they say.
If it is not broken!
Do not try to fix it.

funny none of the UEFI computers I have give that message.
But they are using much newer versions of UEFI.
All of mine are personal computers or ones I built from a bunch of after market parts.

The ThinkCentre is a line of business-oriented desktop computers

they probably have UEFI access restrictions set tighter than a personal computer will have.

[retry3]

Thanks rockedge & bigpup, your comments help clarify things.

I never try to "fix" things like that, I was just afraid it was a warning that a disaster was building up.

[Grey]

I recently had this error message. It turned out that signatures from the previously installed version of Linux Mint remained in the UEFI boot settings. I deleted these items in UEFI and cleaned up the /EFI folder on the hard drive. After that, the error message went away.