hi there everyone, I have a problem with vconsole I can’t find the solution I tried everything out there on the web.
this is the error:
ago 24 11:56:41 linux-x5uw systemd-vconsole-setup[245]: /usr/bin/loadkeys failed with error code 1.
ago 24 11:56:41 linux-x5uw systemd-vconsole-setup[245]: Input/output error
ago 24 11:56:41 linux-x5uw systemd-vconsole-setup[245]: KD_FONT_OP_GET failed while trying to get the font metadata: Input/output error
ago 24 11:56:41 linux-x5uw systemd-vconsole-setup[245]: Input/output error
ago 24 11:56:41 linux-x5uw systemd-vconsole-setup[245]: Fonts will not be copied to remaining consoles
ago 24 11:56:41 linux-x5uw systemd-vconsole-setup[245]: Input/output error
ago 24 11:56:41 linux-x5uw systemd[1]: systemd-vconsole-setup.service: Main process exited, code=exited, status=1/FAILURE
ago 24 11:56:41 linux-x5uw systemd-vconsole-setup[245]: Input/output error
ago 24 11:56:41 linux-x5uw systemd-vconsole-setup[245]: Input/output error
ago 24 11:56:41 linux-x5uw systemd[1]: systemd-vconsole-setup.service: Unit entered failed state.
ago 24 11:56:41 linux-x5uw systemd-vconsole-setup[245]: Input/output error
ago 24 11:56:41 linux-x5uw systemd[1]: systemd-vconsole-setup.service: Failed with result 'exit-code'.
ago 24 11:56:42 linux-x5uw systemd-vconsole-setup[245]: KDSKBENT: Input/output error: could not deallocate keymap 128
ago 24 11:56:52 linux-x5uw systemd-vconsole-setup[532]: KD_FONT_OP_SET failed, fonts will not be copied to tty7: Argumento inválido
ago 24 11:56:58 linux-x5uw systemd-vconsole-setup[808]: KD_FONT_OP_SET failed, fonts will not be copied to tty7: Invalid argument
this is the output of localectl
localectl
System Locale: LANG=es_ES.utf8
VC Keymap: es
X11 Layout: es
X11 Model: pc105
X11 Options: terminate:ctrl_alt_bksp
cat /etc/vconsole.conf
KEYMAP=es
**cat /etc/sysconfig/console
**
## Path: Hardware/Console
## Description: Text console settings (see also Hardware/Keyboard)
## Type: string
## Default: ""
## ServiceRestart: kbd
#
# Console settings.
# Note: The KBD_TTY setting from Hardware/Keyboard (sysconfig/keyboard)
# also applies for the settings here.
#
# Load this console font on bootup:
# (/usr/share/kbd/consolefonts/)
#
CONSOLE_FONT="eurlatgr.psfu"
## Type: string
## Default: ""
#
# Some fonts come without a unicode map.
# (.psfu fonts supposedly have it, others often not.)
# You can then specify the unicode mapping of your font
# explicitly. (/usr/share/kbd/unimaps/)
# Normally not needed.
#
CONSOLE_UNICODEMAP=""
## Type: string
## Default: ""
#
# Most programs output 8 bit characters, so you need a table to
# translate those characters into unicode. That one can be specified
# here. (/usr/share/kbd/consoletrans/)
# (Note: If your console is in utf-8 mode you don't need this.)
# If your code does not use a unicode mapping at all (because you
# e.g. explicitly specified UNICODEMAP="none") you may circumvent
# the translation via unicode, but load a map which directly maps
# 8 bit output of your program to a font position.
#
CONSOLE_SCREENMAP=""
## Type: string
## Default: ""
#
# for some fonts the console has to be initialized with CONSOLE_MAGIC.
# CONSOLE_MAGIC can be empty or have the values "(B", ")B", "(K" or ")K".
# Normally not needed (automatically handled by setfont).
#
CONSOLE_MAGIC=""
# Encoding used for output of non-ascii characters.
#
CONSOLE_ENCODING="UTF-8"
CONSOLE_SCREENMAP should not be necessary since I’m using utf-8
I don’t know how to solve it really I exhausted every possible solution out there in the web.
Is there some reason why you set your font in /etc/sysconfig/console?
In the MAN page for vconsole.conf
OPTIONS The following options are understood:
KEYMAP=, KEYMAP_TOGGLE=
Configures the key mapping table for the keyboard. KEYMAP= defaults to "us" if not
set. The KEYMAP_TOGGLE= can be used to configure a second toggle keymap and is by
default unset.
FONT=, FONT_MAP=, FONT_UNIMAP=
Configures the console font, the console map and the unicode font map.
EXAMPLE
Example 1. German keyboard and console
/etc/vconsole.conf:
KEYMAP=de-latin1 FONT=latarcyrheb-sun16
So,
You can try the same…
Did you modify /etc/sysconfig/console yourself, or was that set up by YaST or something else?
Also, it might be helpful to understand that configuring in vconsole.conf sets configurations when the object is first set up while sysconfig generally <re-writes> or otherwise modifies default configurations… Of course, it’s better to try to set things up a certain way from the beginning but sysconfig is a very convenient way to configure when it works(more or less centralized location for custom settings).
I have the same problem as reported by eatobin. Admittedly, it is not exactly the same as the original one by rocketbones. Similar to eatobin, it started on August 28, when I updated Tumbleweed using the KDE systray app. I figured it might go away by applying approx. 1000 updates today via
sudo zypper dup --no-allow-vendor-change
. However, the red FAILED message during boot-up persists. Thus I should like to bump this thread in order to maybe get to a solution.
The full error message during boot-up reads:
[FAILED] Failed to start Setup Virtual Console.
See 'systemctl status systemd-vconsole-setup.service' for details.
Starting Show Plymouth Boot Screen...
This is the systemctl report the system suggests to visit:
sudo systemctl status systemd-vconsole-setup.service
● systemd-vconsole-setup.service - Setup Virtual Console
Loaded: loaded (/usr/lib/systemd/system/systemd-vconsole-setup.service; static; vendor preset: disabled)
Active: inactive (dead) since Wed 2017-09-06 12:08:03 CEST; 14min ago
Docs: man:systemd-vconsole-setup.service(8)
man:vconsole.conf(5)
Process: 405 ExecStart=/usr/lib/systemd/systemd-vconsole-setup (code=exited, status=0/SUCCESS)
Main PID: 405 (code=exited, status=0/SUCCESS)
Sep 06 12:08:03 susytmblwdke systemd[1]: Started Setup Virtual Console.
Answering the question asked in the previous post: No, I didn’t change anything myself, it is just a Tumbleweed (German) installed fresh sometime in July and updated continuously, mostly via the KDE systray app.
I also see this issue on Tumbleweed KDE. I have not changed anything and it started a few days ago after an update and re-boot. So far it does not seem to have had any adverse effect on my system that I can determine (yet!).
Thanks for your confirmation. Shall we wait and hope the issue will go away with some update round, as I did wait one or two weeks already, or shall we file a bug report to openSUSE?
I did file other bug reports in the past, but it’s tedious - checking for duplicates, the right addressee…
Just checked the Bugzilla. Tobin (eatobin?) has reported it on 08/27. Status still is “new” in Bugzilla. The ensuing conversations don’t come to a definite resolution, at least as far as I understand them. There are indications what in fact might be the culprit. Thanks, eatobin, for your efforts with this issue!
The a.m. bug has persisted on my system as well as for other people since Augzst 2017. In fact, it has been reported to show up for someone else when updating on Jan 10, 2018; cf. the Bugzilla under Bug #1055834.
Thus I should like to ask for advice in case somebody has found a solution. I figured to try and bump this thread for this purpose. I will also try and bump the a.m. Bugzilla Bug number.
I’m having this “issue” in Leap 15. In fact, I use openSUSE from long time ago and I always had this error message in my system. The same with “watchdog didn’t stop” when I shutdown the computer. Ugly stuffs.
Not too helpful, would have been great if the error was mentioning what action was triggering the error.
The errors start before Plymouth is started so changing /usr/lib/systemd/system/plymouth-start.service will not help.
Like others I did not hack config files myself, all modifications done via Yast.
Did today boot with “systemd.log_level=debug” added to the boot line and see first systemd-vconsole-setup[180] is running fine on /dev/tty1, then it runs into errors and after that other systemd-vconsole-setup instances are started (414/419/499/537/652/703) and these are all fine.
I’ve had this error similar to the one reported by 111MilesToGo on Leap 15 startup since a few days- it started after an update (zypper up) but I can’t recall which one.
During restart or cold start, the following message would be displayed:
[FAILED] Failed to start Setup Virtual Console.
See 'systemctl status systemd-vconsole-setup.service' for details.
Starting Show Plymouth Boot Screen...
On my laptop, the error was being triggered by missing “eurlatgr.psfu” in “/usr/share/kbd/consolefonts/”.
“/usr/share/kbd/consolefonts/” had a file named “eurlatgr.psfu.gz”, but no “eurlatgr.psfu”.
The solution in my case was pretty straightforward- extracted “eurlatgr.psfu.gz” with ARK and “eurlatgr.psfu” was created in “/usr/share/kbd/consolefonts/”.
Rebooted a couple of times, the error doesn’t show up during system startup anymore.