[Faild] Failed to start virtual console setup

Hey team Garuda,
Recently I did a fresh Install of Garuda OS.
After Getting everything done post installation when I rebooted my system it said
[Failed] Failed to start Setup Virtual Console

It’s irritating…

Since it’s only irritating, I guess not blocking, I assume your system is booting?
If so, you should always provide your garuda-inxi, as required by the template.
This would help troubleshooting, e.g. to check if the service below is failing.
Please provide also the output of:

systemctl status systemd-vconsole-setup.service

And also:

cat /etc/vconsole.conf
2 Likes

garuda-inxi

System:
Kernel: 6.5.9-zen2-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: hpet available: acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=f824512c-ed25-441b-9895-43b8d09686a7 rw rootflags=subvol=@
quiet resume=UUID=7eecd08e-d0a9-496f-8a87-1712b6f17e8d loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.27.9 tk: Qt v: 5.15.11 wm: kwin_wayland vt: 1
dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Laptop System: LENOVO product: 81UT v: Lenovo IdeaPad S145-15API
serial: <superuser required> Chassis: type: 10 v: Lenovo IdeaPad S145-15API
serial: <superuser required>
Mobo: LENOVO model: LNVNB161216 v: SDK0Q55724WIN
serial: <superuser required> UEFI: LENOVO v: BUCN31WW date: 02/11/2022
Battery:
ID-1: BAT0 charge: 13.1 Wh (44.3%) condition: 29.6/35.0 Wh (84.5%)
power: 15.5 W volts: 8.0 min: 7.5 model: SMP L16M2PB2 type: Li-poly
serial: <filter> status: charging cycles: 457
CPU:
Info: model: AMD Ryzen 3 3200U with Radeon Vega Mobile Gfx bits: 64
type: MT MCP arch: Zen/Zen+ note: check gen: 1 level: v3 note: check
built: 2019 process: GF 12nm family: 0x17 (23) model-id: 0x18 (24)
stepping: 1 microcode: 0x8108102
Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache:
L1: 192 KiB desc: d-2x32 KiB; i-2x64 KiB L2: 1024 KiB desc: 2x512 KiB
L3: 4 MiB desc: 1x4 MiB
Speed (MHz): avg: 2485 high: 3117 min/max: 1400/2600 boost: enabled
scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 2740 2: 1224
3: 3117 4: 2860 bogomips: 20759
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Picasso/Raven 2 [Radeon Vega Series / Radeon Mobile Series]
vendor: Lenovo driver: amdgpu v: kernel arch: GCN-5 code: Vega
process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16
ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 03:00.0 chip-ID: 1002:15d8
class-ID: 0300 temp: 67.0 C
Device-2: Syntek Integrated Camera driver: uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-5:3 chip-ID: 174f:1176
class-ID: 0e02
Display: wayland server: X.org v: 1.21.1.9 with: Xwayland v: 23.2.2
compositor: kwin_wayland driver: X: loaded: amdgpu unloaded: modesetting
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: 0
Monitor-1: eDP-1 res: 1366x768 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast surfaceless: drv: radeonsi wayland: drv: radeonsi x11:
drv: radeonsi inactive: gbm
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 23.2.1-arch1.2
glx-v: 1.4 direct-render: yes renderer: AMD Radeon Vega 3 Graphics (raven2
LLVM 16.0.6 DRM 3.54 6.5.9-zen2-1-zen) device-ID: 1002:15d8
memory: 1.95 GiB unified: no display-ID: :1.0
API: Vulkan v: 1.3.269 layers: 3 device: 0 type: integrated-gpu name: AMD
Radeon Vega 3 Graphics (RADV RAVEN2) driver: mesa radv v: 23.2.1-arch1.2
device-ID: 1002:15d8 surfaces: xcb,xlib,wayland device: 1 type: cpu
name: llvmpipe (LLVM 16.0.6 256 bits) driver: mesa llvmpipe
v: 23.2.1-arch1.2 (LLVM 16.0.6) device-ID: 10005:0000
surfaces: xcb,xlib,wayland
Audio:
Device-1: AMD Raven/Raven2/Fenghuang HDMI/DP Audio vendor: Lenovo
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 03:00.1 chip-ID: 1002:15de class-ID: 0403
Device-2: AMD Family 17h/19h HD Audio vendor: Lenovo driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 03:00.6
chip-ID: 1022:15e3 class-ID: 0403
API: ALSA v: k6.5.9-zen2-1-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 0.3.84 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter
vendor: Lenovo driver: ath10k_pci v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 bus-ID: 02:00.0 chip-ID: 168c:0042 class-ID: 0280
IF: wlp2s0 state: up mac: <filter>
Bluetooth:
Device-1: Qualcomm Atheros driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-6:4 chip-ID: 0cf3:e500
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 4.2
lmp-v: 8 status: discoverable: no pairing: no class-ID: 7c010c
Drives:
Local Storage: total: 1.36 TiB used: 10.6 GiB (0.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Silicon Power
model: SPCC M.2 PCIe SSD size: 465.76 GiB block-size: physical: 512 B
logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: ELFMB0.6 temp: 34.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD10SPZX-24Z10
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 5400 serial: <filter> fw-rev: 1A05 scheme: GPT
Partition:
ID-1: / raw-size: 454.91 GiB size: 454.91 GiB (100.00%)
used: 10.6 GiB (2.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 576 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 454.91 GiB size: 454.91 GiB (100.00%)
used: 10.6 GiB (2.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 454.91 GiB size: 454.91 GiB (100.00%)
used: 10.6 GiB (2.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 454.91 GiB size: 454.91 GiB (100.00%)
used: 10.6 GiB (2.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 9.59 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 4 dev: /dev/zram0
ID-2: swap-2 type: partition size: 10.55 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/nvme0n1p3 maj-min: 259:3
Sensors:
System Temperatures: cpu: 66.6 C mobo: N/A gpu: amdgpu temp: 66.0 C
Fan Speeds (rpm): N/A
Info:
Processes: 226 Uptime: 12m wakeups: 0 Memory: total: 12 GiB note: est.
available: 9.59 GiB used: 3.41 GiB (35.6%) Init: systemd v: 254
default: graphical tool: systemctl Compilers: gcc: 13.2.1 Packages:
pm: pacman pkgs: 1411 libs: 411 tools: octopi,paru Shell: fish v: 3.6.1
running-in: konsole inxi: 3.3.31
error: blackarch: key "F9A6E68A711354D84A9B91637533BAFE69A25079" is unknown
error: keyring is not writable
Garuda (2.6.17-1):
System install date:     2023-11-05
Last full system update: 2023-11-05
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       Probably (Run as root to verify)
Failed units:            packagekit.service systemd-vconsole-setup.service

systemctl status systemd-vconsole-setup.service

× systemd-vconsole-setup.service - Virtual Console Setup
Loaded: loaded (/usr/lib/systemd/system/systemd-vconsole-setup.service; static)
Active: failed (Result: exit-code) since Tue 2023-11-07 14:18:23 IST; 16min ago
Docs: man:systemd-vconsole-setup.service(8)
man:vconsole.conf(5)
Process: 560 ExecStart=/usr/lib/systemd/systemd-vconsole-setup (code=exited, status=1/FAILURE)
Main PID: 560 (code=exited, status=1/FAILURE)
CPU: 46ms

Nov 07 14:18:23 Pushpam-Pc systemd[1]: Starting Virtual Console Setup...
Nov 07 14:18:23 Pushpam-Pc systemd-vconsole-setup[564]: loadkeys: Unable to open file: in: No such file or di>
Nov 07 14:18:23 Pushpam-Pc systemd-vconsole-setup[560]: /usr/bin/loadkeys failed with exit status 1.
Nov 07 14:18:23 Pushpam-Pc systemd[1]: systemd-vconsole-setup.service: Main process exited, code=exited, stat>
Nov 07 14:18:23 Pushpam-Pc systemd[1]: systemd-vconsole-setup.service: Failed with result 'exit-code'.
Nov 07 14:18:23 Pushpam-Pc systemd[1]: Failed to start Virtual Console Setup.

cat /etc/vconsole.conf

File: /etc/vconsole.conf
FONT=ter-220n
KEYMAP=in

please help soon as possible…

This is the problem.
Try changing this:

KEYMAP=in

to

KEYMAP=us

and give a:

sudo dracut-rebuild

And reboot.
I’m not 100% that the us keyboard layout is correct for India, but for console it should not be a big problem.
Anyway, you can check the available keymaps with localectl list-keymaps.

Please be patient. No one is paid here, and we are all volunteers who offer some of their free time… :slight_smile:

5 Likes

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.