Github messages for voidlinux
 help / color / mirror / Atom feed
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:51:42 +0200	[thread overview]
Message-ID: <20231018155142.ahc681WnTLuPYuWs6N99kKsmA5_xwR8j2gyzh1RZneo@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: 550 bytes --]

New comment by gc-user on void-packages repository

https://github.com/void-linux/void-packages/issues/46758#issuecomment-1768779394

Comment:
2. Ok, I see. Maybe I'll do that, too - or adding the fbcon line to kcl permanently. The EFI binary has some message after booting the BE about USB (can't recall the details right now and don't know where the log is stored, as it's not in "/var/log/everything/current".

3. That's in /boot/config-[kernel_version]. It's also the output of "zcat /proc/config.gz |grep FONT". See also initial post above.


  parent reply	other threads:[~2023-10-18 15:51 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
2023-10-18 15:29 ` zdykstra
2023-10-18 15:51 ` gc-user [this message]
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=20231018155142.ahc681WnTLuPYuWs6N99kKsmA5_xwR8j2gyzh1RZneo@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).