On 19/6/23 10:10, Wolfgang Pfeiffer wrote:
On Sat, Jun 17, 2023 at 12:56:54PM -0400, Max Pyziur wrote:
>
> I made some changes to /etc/default/grub, and here is what my current
> version looks like:
> GRUB_TIMEOUT=5
> GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
> GRUB_DEFAULT=saved
> GRUB_DISABLE_SUBMENU=true
> GRUB_DISABLE_RECOVERY="true"
> GRUB_ENABLE_BLSCFG=true
> GRUB_CMDLINE_LINUX="rhgb quiet"
This last line seems to be more or less switching off boot
messages. You sure you want that? See
https://developer.ibm.com/tutorials/l-lpic1-101-2/
" ... erase the words 'quiet', then 'rhgb'. This will stop the Red
Hat
Graphical Boot screen that fedora normally display during boot and
also stop suppressing many of the messages that are normally
generated."
> GRUB_TERMINAL_OUTPUT="gfxterm"
gfxterm: does that result in small fonts boot messages?
Upstream disabled gfxterm when resolving a security issue in grub. The
resolvers of the security issue said they were disabling it, and if the
grub maintainers wanted it enabled they could do it themselves. I
haven't checked recently if it has been enabled again.
regards,
Steve
> GRUB_FONT="/boot/grub2/fonts/RedHatMono-Medium32.pf2"
I'd remove the line above alltogether in the boot command line and see
what happens .. more on that later ..
>
>
> Please note the last two lines; one specifies the path to the font;
> the other is changed from
> GRUB_TERMINAL_OUTPUT="console"
As you remember the value in the last line above is what I have in my
grub file, and not 'gfxterm'.
I suspect with your current setup you're making things more
complicated than necessary. You already wrote that you have now
readable fonts on the console on a running system - so maybe turning
on verbose boot messages by removing "rghb quiet" plus disabling
graphical boot by ordering "GRUB_TERMINAL_OUTPUT="console"" will
help
giving you decent readable boot messages. And I suspect that without
setting up specific fonts in grub might trigger it to read
'/etc/vconsole.conf' ...
The IBM page above seems to instruct how to change boot parameters
for the current boot only:
"When you see the GRUB2 menu, you can edit the entry that you want to
modify by selecting it and then pressing e."
and thus - I think - not change your standard boot setup for the
following bootups ... So this approach seems to give a nice
environment to test boot parameters before writing them down
permanently into grub files ...
Good luck!
Wolfgang
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue