Comment # 4 on bug 1055834 from Stanislav Brabec

I have read the whole upstream bug.

The error "KD_FONT_OP_SET failed,..." comes from systemd-vconsole-setup and it
is displayed if ioctl(, KDFONTOP,) fails. It has nothing to do with kbd.

Aug 30 11:57:35 linux-epth systemd-vconsole-setup[155]: Executing
"/usr/bin/setfont -C /dev/tty1 -m trivial lat9w-16.psfu"...Aug 30 11:57:37
linux-epth systemd-vconsole-setup[155]: /usr/bin/loadkeys failed with error
code 1. Really comes from kbd.

Aug 30 11:57:37 linux-epth systemd-vconsole-setup[155]: KD_FONT_OP_GET failed
while trying to get the font metadata: Input/output error

Aug 30 11:57:* linux-epth systemd-vconsole-setup[155]: Input/output error
(many times)

Aug 30 11:57:37 linux-epth systemd-vconsole-setup[155]: KDSKBENT: Input/output
error: could not deallocate keymap 128

But as both errors started to appear together, so I suspect that they are
caused by changes in the graphic subsystem (we seen similar problems in past,
after introduction of a new graphic splash).

Let's see whether it works from the early command line.