FS#78958 - [kbd] Reporting 'Unable to load such font with such kernel version' at boot

Attached to Project: Arch Linux
Opened by IMBJR (IMBJR) - Monday, 03 July 2023, 11:41 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:18 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 9
Private No

Details

Description:
kbd now reports a loading font error on boot-up.

Additional info:
* package version: kbd 2.6.1

Steps to reproduce:
Boot into system, see the following reported, but not recording in the journal:

setfont: ERROR kdfontop.c:183 put_font_kdfontop: Unable to load such font with such kernel version

Looking at the source code:
if (errno == ENOSYS) {
KFONT_ERR(ctx, _("Unable to load such font with such kernel version"));
return -1;
}

it appears that ENOSYS is "Function not implemented". i.e. a regression or the font in question is no longer supported.
This task depends upon

Closed by  Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:18 GMT
Reason for closing:  Moved
Additional comments about closing:  https://gitlab.archlinux.org/archlinux/p ackaging/packages/kbd/issues/1
Comment by loqs (loqs) - Monday, 03 July 2023, 12:19 GMT
Was this error produced using a kernel version of 6.1.Y or older such as linux-lts?
Comment by IMBJR (IMBJR) - Monday, 03 July 2023, 15:14 GMT
Kernel version 6.4.1. I don't think it appeared for the 6.3.X kernels.
Comment by IMBJR (IMBJR) - Monday, 03 July 2023, 16:10 GMT
I just set FONT=lat2-16 in vconsole.conf on a machine that never had it set before, and under kernel 6.3.9, the message reported is:
setfont: KDFONTOP: Function not implemented

After a full upgrade, the message stays the same - i.e. it does not become setfont: ERROR kdfontop.c:183 put_font_kdfontop: Unable to load such font with such kernel version
Comment by IMBJR (IMBJR) - Monday, 03 July 2023, 16:32 GMT
Just noticed I'd set setfont as part of the BINARIES of /etc/mkinitcpio.conf, but also:

Replacing the hooks keymap and consolefont with sd-vconsole and regenerating the kernel image will remove the message.
Comment by Toolybird (Toolybird) - Monday, 03 July 2023, 23:02 GMT
There have been changes in the kernel font code. If there is a problem with `setfont' triggered by latest kernel, you'll need to report it to kbd upstream [1]

[1] https://github.com/legionus/kbd

Comment by Rodolfo (rodolfoser) - Tuesday, 04 July 2023, 19:27 GMT
i do have exact same behaviour after last upgrade.
Also my in vconsole.conf defined Keymap is not applied anymore in initramfs stage
Comment by Rodolfo (rodolfoser) - Wednesday, 05 July 2023, 01:29 GMT
i do have exact same behaviour after last upgrade.
Also my in vconsole.conf defined Keymap is not applied anymore in initramfs stage
Comment by igor (igorog) - Wednesday, 05 July 2023, 02:02 GMT
I confirm. There is this after the update.
Comment by Toolybird (Toolybird) - Monday, 07 August 2023, 07:19 GMT
https://github.com/legionus/kbd/issues/99
Comment by nl6720 (nl6720) - Tuesday, 08 August 2023, 12:16 GMT
Just to note, mkinitcpio's consolefont hook does not use the kbd project's setfont, it uses busybox's setfont. That is unless you add setfont to BINARIES in /etc/mkinitcpio.conf, of course.
Comment by Gabor (otnegy) - Tuesday, 08 August 2023, 23:15 GMT
I only got the mentioned error:
`setfont: ERROR kdfontop.c:183 put_font_kdfontop: Unable to load such font with such kernel version`
when I tried to add `BINARIES=(setfont)` to mkinitcpio.conf

otherwise i get:
`setfont: KDFONTOP: Function not implemented`

Comment by Tobias Powalowski (tpowa) - Saturday, 18 November 2023, 10:20 GMT
To not face this issue, udevadm settle needs to be called before the vconsole setup is done.
Comment by IMBJR (IMBJR) - Tuesday, 21 November 2023, 16:35 GMT
Since a recent mkinitcpio update, my work-around changes have become obsolete. I removed them and no longer see the issue.

Loading...