From: et-rnal <et-rnal@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Unable to load such font with such kernel version
Date: Wed, 13 Sep 2023 00:06:13 +0200 [thread overview]
Message-ID: <20230912220613.jQTzuu7Dg26mjKMGmxKObcyo14qZ1y411T91H5LCuRU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45216@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 784 bytes --]
New comment by et-rnal on void-packages repository
https://github.com/void-linux/void-packages/issues/45216#issuecomment-1716564773
Comment:
> just ignore it. it's been happening for years but just didn't print a message until recently, it doesn't mean anything other than the console font couldn't be set so early in boot. it's is absolutely, 100% harmless
I understand that it's harmless, however, it's jarring and unwanted. What's even more confounding is that on a fresh install, it was suppressed. One week later, same exact rootfs installation process, the message had returned. Same exact machine, same exact peripherals etc. Seemingly zero changes, only now with the message.
I'll attempt to find a way to suppress this output and post whatever solution I find here.
next prev parent reply other threads:[~2023-09-12 22:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 8:25 [ISSUE] " Sqvid
2023-07-25 18:22 ` justinesmithies
2023-07-28 0:40 ` classabbyamp
2023-07-31 3:15 ` superiums
2023-07-31 3:23 ` classabbyamp
2023-07-31 6:46 ` superiums
2023-09-12 21:54 ` et-rnal
2023-09-12 21:57 ` classabbyamp
2023-09-12 22:06 ` et-rnal [this message]
2023-09-19 7:56 ` wastemans
2023-09-19 7:58 ` wastemans
2023-09-19 8:11 ` superiums
2023-09-19 13:38 ` wastemans
2023-09-24 10:36 ` superiums
2023-11-03 0:16 ` AlifiChiganjati
2023-12-07 3:45 ` [ISSUE] [CLOSED] " ahesford
2023-12-22 23:24 ` don-dolarson
2023-12-25 18:13 ` don-dolarson
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=20230912220613.jQTzuu7Dg26mjKMGmxKObcyo14qZ1y411T91H5LCuRU@z \
--to=et-rnal@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).