Bugzilla – Bug 1200945
"Failed to start setup of virtual console" during boot process
Last modified: 2022-07-05 06:15:45 UTC
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:101.0) Gecko/20100101 Firefox/101.0 Build Identifier: I have executed a update with "zypper dup" today for openSUSE Tumbleweed. Then I have received the message "Failed to start setup of virtual console" during the boot process (before the Tumbleweed logo). I can find following information in the boot.msg: <7>[ 4.823650] systemd[1]: Started Journal Service. <6>[ 4.828570] usb 1-10: new full-speed USB device number 5 using xhci_hcd <6>[ 4.985823] usb 1-10: New USB device found, idVendor=8087, idProduct=0026, bcdDevice= 0.02 <6>[ 4.985826] usb 1-10: New USB device strings: Mfr=0, Product=0, SerialNumber=0 <6>[ 5.642805] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input5 <6>[ 5.645297] intel_pmc_core INT33A1:00: initialized <6>[ 5.646703] Consider using thermal netlink events interface <3>[ 5.648355] ACPI Error: Needed [Integer/String/Buffer], found [Package] 00000000ebdb357e (20211217/exresop-469) <3>[ 5.648363] ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [ToHexString] (20211217/dswexec-431) <3>[ 5.648370] ACPI Error: Aborting method \ADBG due to previous error (AE_AML_OPERAND_TYPE) (20211217/psparse-529) <3>[ 5.648377] ACPI Error: Aborting method \_SB.HIDD._DSM due to previous error (AE_AML_OPERAND_TYPE) (20211217/psparse-529) <4>[ 5.648385] ACPI: \_SB_.HIDD: failed to evaluate _DSM (0x3003) <6>[ 5.648962] input: Intel HID events as /devices/platform/INT33D5:00/input/input6 <6>[ 5.657078] ACPI: AC: AC Adapter [AC] (on-line) <6>[ 5.659996] ACPI: button: Sleep Button [SLPB] <6>[ 5.660071] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input7 <6>[ 5.660146] ACPI: button: Lid Switch [LID] <6>[ 5.660178] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input8 <6>[ 5.660214] ACPI: button: Power Button [PWRF] <6>[ 5.751993] thermal LNXTHERM:00: registered as thermal_zone3 <6>[ 5.751996] ACPI: thermal: Thermal Zone [THM0] (55 C) <6>[ 5.752423] intel_pch_thermal 0000:00:12.0: enabling device (0000 -> 0002) <6>[ 5.752720] thinkpad_acpi: ThinkPad ACPI Extras v0.26 <6>[ 5.752723] thinkpad_acpi: http://ibm-acpi.sf.net/ <6>[ 5.752724] thinkpad_acpi: ThinkPad BIOS N2XET27W (1.17 ), EC N2XHT18W <6>[ 5.752725] thinkpad_acpi: Lenovo ThinkPad T14 Gen 1, model 20S0000NGE <6>[ 5.753504] thinkpad_acpi: radio switch found; radios are enabled <6>[ 5.753513] thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver <5>[ 5.753514] thinkpad_acpi: Disabling thinkpad-acpi brightness events by default... <6>[ 5.756302] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked <6>[ 5.761232] proc_thermal 0000:00:04.0: enabling device (0000 -> 0002) <6>[ 5.766547] intel_rapl_common: Found RAPL domain package <6>[ 5.766550] intel_rapl_common: Found RAPL domain dram <6>[ 5.769288] thinkpad_acpi: secondary fan control detected & enabled <6>[ 5.771376] mei_me 0000:00:16.0: enabling device (0000 -> 0002) <6>[ 5.774193] thinkpad_acpi: battery 1 registered (start 0, stop 100, behaviours: 0x7) The boot.log has no information in this direction. But I attach both. I add also the hwinfo output. Reproducible: Sometimes Steps to Reproduce: 1. Use a laptop Lenovo ThinkPad T14 2. Update openSUSE Tumbleweed with the version of 26th June 2022 3. Reboot 4. During reboot "Failed to start setup virtual console" Actual Results: During reboot "Failed to start setup virtual console" Expected Results: You do not receive any error messages during the reboot of openSUSE Tumbleweed.
Created attachment 859849 [details] boot.msg
The Bugzilla has got internal server errors, if I want to add log files (also as archives).
I can confirm the error message with tumbleweed release 20220627 Jun 28 11:41:47 cypod3 systemd[1]: Starting Setup Virtual Console... Jun 28 11:41:47 cypod3 systemd-vconsole-setup[539]: cannot open include file de-latin1.map Jun 28 11:41:47 cypod3 systemd-vconsole-setup[539]: syntax error, unexpected ERROR Jun 28 11:41:47 cypod3 systemd-vconsole-setup[537]: /usr/bin/loadkeys failed with exit status 1. Jun 28 11:41:47 cypod3 systemd[1]: systemd-vconsole-setup.service: Main process exited, code=exited, status=1/FAILURE Jun 28 11:41:47 cypod3 systemd[1]: systemd-vconsole-setup.service: Failed with result 'exit-code'. Jun 28 11:41:47 cypod3 systemd[1]: Failed to start Setup Virtual Console.
I can confirm the same issue on my system after today's update to TW 20220627: Operating System: openSUSE Tumbleweed 20220627 KDE Plasma Version: 5.25.1 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.2 Kernel Version: 5.18.6-1-default (64-bit) Graphics Platform: X11 Processors: 4 × AMD A8-7650K Radeon R7, 10 Compute Cores 4C+6G Memory: 14.6 GiB of RAM Graphics Processor: AMD KAVERI Output dmesg: [ 1.255777] systemd[1]: Reached target Socket Units. [ 1.257109] systemd[1]: Started Entropy Daemon based on the HAVEGE algorithm. [ 1.258117] systemd[1]: Starting Create List of Static Device Nodes... [ 1.260003] systemd[1]: Starting Journal Service... [ 1.261192] systemd[1]: Starting Load Kernel Modules... [ 1.262247] systemd[1]: Starting Setup Virtual Console... [ 1.262978] systemd[1]: Finished Create List of Static Device Nodes. [ 1.264207] systemd[1]: Starting Create Static Device Nodes in /dev... [ 1.272063] systemd[1]: Finished Create Static Device Nodes in /dev. [ 1.297858] systemd[1]: systemd-vconsole-setup.service: Main process exited, code=exited, status=1/FAILURE [ 1.298013] systemd[1]: systemd-vconsole-setup.service: Failed with result 'exit-code'. [ 1.298182] systemd[1]: Failed to start Setup Virtual Console. [ 1.299336] systemd[1]: Starting dracut ask for additional cmdline parameters... [ 1.306376] systemd[1]: Started Journal Service. [ 1.308458] alua: device handler registered [ 1.309249] emc: device handler registered [ 1.310051] rdac: device handler registered
I presume that the entry of KEYMAP in /etc/vconsole.conf does not exist in /usr/share/kbd/keymaps/xkb/. For example, only de-nodeadkeys exists instead of de-latin1-nodeadkeys. Maybe a yast-country or kbd issue.
Fix in progress *** This bug has been marked as a duplicate of bug 1200950 ***
*** Bug 1201205 has been marked as a duplicate of this bug. ***