The service appears to be “vendor preset: disabled” – Why is that?
… and most important, when I try to enable it I can “start” the service systemd-vconsole-setup but not enable it.
The service cannot be enabled/disabled because it has no "install" section in the description file
Using Ctrl+Alt+F2 to FX… does nothing. So it is not working.
Because the systemd developers (the vendor) have delivered the service with the preset set to “disabled” …
A “static” systemd unit is simply a unit without an “install” section; which means that, it can neither be enabled nor disabled.
Don’t worry, if something needs (depends on) a static unit then, it’ll be started by systemd at the appropriate point in time …
Performing a case-insensitive recursive ‘grep’ for “vconsole” in ‘/usr/lib/systemd/system/’ reveals that the plymouth-start.service “wants” the ‘vconsole-setup’ service.
Is it correct to assume that, tty1 is accessible and usable?
Does /dev/ contain any character special tty devices apart from tty1?
I’ll check the behaviour on this system without a Display Manager running – there are some other issues around X11 on AMD hardware which mean I’ll have to shutdown this session. Back in a minute or two.
Back again.
Logging into tty2 <Ctrl-Alt-F2> and then issuing ‘chvt 3’; ‘chvt 7’ (landed on the X11/sddm Display Manager login screen); ‘chvt 1’, all functioned as expected and, from each “changed to VT”, <Ctrl-Alt-F2> dropped me back into my login on tty2. ‘chvt 0’ (tty0 – used by Braille keyboards) raised an error as expected.
From your original post, it seems that only tty1 is present on your system – in ‘/etc/sysconfig/keyboard’ is ‘KBD_TTY’ set to anything other than “” ?
You can ignore the message, it won’t harm. There’s patch for it. but … my recent Leap Live image doesn’t show the message, so it may have been fixed. Is your system up to date?