Page 2 of 2 FirstFirst 12
Results 11 to 15 of 15

Thread: Failed to start Setup Virtual Console

  1. #11
    Join Date
    Oct 2011
    Location
    Germany (Ore Mountains)
    Posts
    423

    Default Re: Failed to start Setup Virtual Console

    Quote Originally Posted by karlmistelberger View Post
    Replace systemd's version of /etc/vconsole.conf by the following:

    Code:
    erlangen:~ # cat /etc/vconsole.conf 
    KEYMAP=de-nodeadkeys
    FONT=eurlatgr.psfu
    FONT_MAP=none
    erlangen:~ #
    Run 'zypper install --force kbd kbd-legacy dracut' and reboot.
    Works! I skipped the "zypper install" part because I reinstalled the components recently and just recreated the initial ramdisk with "dracut -f".
    For the FONT_MAP line: I removed it completely.

    Hendrik

  2. #12
    Join Date
    Oct 2014
    Location
    Rotterdam
    Posts
    140

    Default Re: Failed to start Setup Virtual Console

    Quote Originally Posted by karlmistelberger View Post
    Code:
    FONT_MAP=
    Code:
    Nov 11 05:54:26 notebook systemd-vconsole-setup[199]: KD_FONT_OP_GET failed while trying to get the font metadata: Function not implemented
    Nov 11 05:54:26 notebook systemd-vconsole-setup[199]: Fonts will not be copied to remaining consoles
    Nov 11 05:54:26 notebook systemd[1]: Started Setup Virtual Console.
    Nov 11 05:54:28 notebook systemd[1]: Starting Setup Virtual Console...
    I was seeing the same KD_FONT_OP_GET failed warning with "FONT_MAP=" but I am running already with it longer and think/thought that it is not a side effect of setting FONT_MAP to empty, at least the error ("Function not implemented") is not hinting at that.

    Did you see the error before when you were running with "FONT_MAP=none"?

    Just checked the boot log from this morning and the warning is not longer there. No update only fixed an error:
    Code:
    kwin_x11[2297]: kwin_xkbcommon: XKB: couldn't find a Compose file for locale "en_NL.UTF-8"
    by adding to /usr/share/X11/locale/locale.alias and alias from en_NL.UTF-8 to en_US.UTF-8.

    Not sure though I that fixed it.

  3. #13
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    794

    Default Re: Failed to start Setup Virtual Console

    Quote Originally Posted by marel View Post
    I was seeing the same KD_FONT_OP_GET failed warning with "FONT_MAP=" but I am running already with it longer and think/thought that it is not a side effect of setting FONT_MAP to empty, at least the error ("Function not implemented") is not hinting at that.

    Did you see the error before when you were running with "FONT_MAP=none"?

    Just checked the boot log from this morning and the warning is not longer there. No update only fixed an error:
    Code:
    kwin_x11[2297]: kwin_xkbcommon: XKB: couldn't find a Compose file for locale "en_NL.UTF-8"
    by adding to /usr/share/X11/locale/locale.alias and alias from en_NL.UTF-8 to en_US.UTF-8.

    Not sure though I that fixed it.
    "FONT_MAP=none" causes the message "dracut: Could not find FONT_MAP none!" systemd-vconsole-setup prints an informative message in both cases. Tinkering with the locale could result in side effects.
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), openSUSE Tumbleweed, KDE Plasma 5

  4. #14
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    794

    Default Re: Failed to start Setup Virtual Console

    Quote Originally Posted by hendwolt View Post
    Works! I skipped the "zypper install" part because I reinstalled the components recently and just recreated the initial ramdisk with "dracut -f".
    For the FONT_MAP line: I removed it completely.

    Hendrik
    I actually ran "zypper --non-interactive install --force kbd kbd-legacy dracut systemd". This ensures the settings survive an update of all packages involved.
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), openSUSE Tumbleweed, KDE Plasma 5

  5. #15
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    794

    Default Re: Failed to start Setup Virtual Console

    Quote Originally Posted by karlmistelberger View Post
    I actually ran "zypper --non-interactive install --force kbd kbd-legacy dracut systemd". This ensures the settings survive an update of all packages involved.
    Reinstalling these packages also ensures unpatched systemd-vconsole-setup works properly:

    Code:
    notebook:~ # cat /etc/vconsole.conf 
    KEYMAP=de-nodeadkeys
    FONT=eurlatgr.psfu
    notebook:~ # journalctl -b -u systemd-vconsole-setup.service 
    -- Logs begin at Tue 2018-11-06 00:51:53 CET, end at Mon 2018-11-12 13:09:10 CET. --
    Nov 12 13:00:43 notebook systemd-vconsole-setup[201]: KD_FONT_OP_GET failed while trying to get the font metadata: Function not implemented
    Nov 12 13:00:43 notebook systemd-vconsole-setup[201]: Fonts will not be copied to remaining consoles
    Nov 12 13:00:43 notebook systemd[1]: Started Setup Virtual Console.
    Nov 12 13:00:45 notebook systemd[1]: Starting Setup Virtual Console...
    Nov 12 13:00:45 notebook systemd[1]: Started Setup Virtual Console.
    Nov 12 13:00:45 notebook systemd[1]: Started Setup Virtual Console.
    Nov 12 13:00:46 notebook systemd[1]: Starting Setup Virtual Console...
    Nov 12 13:00:46 notebook systemd[1]: Started Setup Virtual Console.
    notebook:~ #
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), openSUSE Tumbleweed, KDE Plasma 5

Page 2 of 2 FirstFirst 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •