From: Sqvid <Sqvid@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Unable to load such font with such kernel version
Date: Mon, 24 Jul 2023 10:25:28 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45216@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]
New issue by Sqvid on void-packages repository
https://github.com/void-linux/void-packages/issues/45216
Description:
### Is this a new report?
Yes
### System Info
Void 6.3.12_1 x86_64 GenuineIntel notuptodate rrDFFFFF
### Package(s) Affected
kbd-2.6.1_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
The kernel boots without font-related errors
### Actual behaviour
Kernel boots with the following error:
`setfont: ERROR kdfontop.c:183 put_font_kdfontop: Unable to load such font with such kernel version `
The actual functionality seems unaffected.
Downgrading to `kbd-2.5.1_1` and `xbps-reconfigur`ing the kernel series fixes the issue.
### Steps to reproduce
My kernel args are:
`root=UUID=<uuid> ro rootflags=subvol=@root rd.luks.allow-discards rd.luks.uuid=<uuid> resume=UUID=<uuid> loglevel=3 fbcon=font:TER16x32`
Then I boot and the message is right at the top of the screen at this log level.
next reply other threads:[~2023-07-24 8:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 8:25 Sqvid [this message]
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
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45216@inbox.vuxu.org \
--to=sqvid@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).