From: gc-user <gc-user@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: After update to zfsbootmenu zfsbootmenu-2.2.1_1: error mesage during boot: setfont: ERROR kdfontop.c:183 put_font_kdfontop: Unable to load such font with such kernel version
Date: Wed, 18 Oct 2023 17:13:44 +0200 [thread overview]
Message-ID: <20231018151344.nTtGiSM9WlxohM5sCZTrDdLQ1a0xo9rXLTbCCzG_koo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46758@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 936 bytes --]
New comment by gc-user on void-packages repository
https://github.com/void-linux/void-packages/issues/46758#issuecomment-1768709387
Comment:
Thanks, Zach, for your reply.
1. Kernel 6.5 is no option on my system as of now: https://github.com/void-linux/void-packages/issues/46427
2. When booting the binary release EFI from your link this error message doesn't show up.
3. Not sure if this is what you're asking about as kernel commandline:
from /boot/efi/EFI/void/refind_linux.conf:
ro quiet loglevel=0 zbm.import_policy=hostid zbm.set_hostid zbm.timeout=4
FYI:
- Adding "fbcon=nodefer" (suggested in the https://github.com/void-linux/void-packages/issues/45216) to the end of the kcl in rEFInd for one-time-use makes the error message disappear.
- Commenting out "CONFIG_FONT_TER16x32=y" and rebuilding initramfs for the kernel and zfsbootmenu as well as vmlinz for zfsbootmenu afterwards didn't change anything.
next prev parent reply other threads:[~2023-10-18 15:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 9:32 [ISSUE] " gc-user
2023-10-18 9:35 ` [ISSUE] [CLOSED] " classabbyamp
2023-10-18 9:35 ` classabbyamp
2023-10-18 13:39 ` zdykstra
2023-10-18 15:13 ` gc-user [this message]
2023-10-18 15:29 ` zdykstra
2023-10-18 15:51 ` gc-user
2023-10-18 15:58 ` zdykstra
2023-10-18 16:21 ` gc-user
2023-10-18 16:27 ` zdykstra
2023-10-18 16:34 ` gc-user
2023-10-18 16:38 ` zdykstra
2023-10-18 20:10 ` gc-user
2023-10-18 20:13 ` zdykstra
2023-10-19 9:16 ` gc-user
2023-10-19 9:17 ` gc-user
2023-10-29 8:41 ` gc-user
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231018151344.nTtGiSM9WlxohM5sCZTrDdLQ1a0xo9rXLTbCCzG_koo@z \
--to=gc-user@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).