On 23/11/22 18:22, Samuel Sieb wrote:
On 11/22/22 22:45, Stephen Morris wrote:
On 23/11/22 12:04, Samuel Sieb wrote:
On 11/20/22 23:54, Stephen Morris wrote:
I am getting the following error message displayed before the
display of the grub boot menu, can someone explain to me what this
means and why it is occurring in F37 when it was never produced in
F36, and what I need to do to rectify it?
error:
../../grub-core/kern/efi/sb.c:169:prohibited by secure boot policy
That's not a file you'll find on your system. That's just
identifying where in the grub code that the error message is coming
from. As you say the grub-gfxmode command isn't working now, I
would assume that's what is causing the error message because it's
not allowed with secure boot enabled. You most likely have to stay
with the graphics mode that is initialized by the BIOS.
Thanks Samuel. Are you saying that grub command is not allowed if F37
because F37 is now booting via grub with full secure boot enabled,
whereas with the way F36 booted that grub command was honoured and
the menus and theme were displayed in that resolution with full
secure boot enabled?
That was just a guess and I think it was wrong now. I checked the
source and that error message is related to file loading. I would
have to see your config file to make a guess about what file it was
trying to load.
I bookmarked an article under Windows in Firefox but the bookmark is not
showing up under linux, that specifies the error is being produced by
the "loadfont" statement in grub.cfg, and occurs because of the
statements GRUB_TERMINAL_OUTPUT=gfxterm and GRUB_GFXMODE=3840x2160
being in /etc/default/grub and a particular version of grub2-efi, where
grub2-efi in a secure boot environment requires the default grub unicode
font or any font being loaded by any grub theme to be self signed. The
article specifies that there is potentially a fix in the testing
repositories for F35, F36 and F37, but is suggesting the updated package
may not be suitable for public consumption yet. An alternative offered
to fix the issue is to downgrade grub2\*.
I could try the updates and see what happens.
The link to the bugzilla article is below.
https://bugzilla.redhat.com/show_bug.cgi?id=2144113
regards,
Steve
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
