Tumbleweed hangs on boot

English Install/Boot/Login
1

I have freshly installed Tumbleweed on an older Laptop.

uname -a
Linux myhost 5.17.9-1-default #1 SMP PREEMPT Wed May 18 10:03:12 UTC 2022 (eab1a2c) x86_64 x86_64 x86_64 GNU/Linux


NAME="openSUSE Tumbleweed"
# VERSION="20220527"
ID="opensuse-tumbleweed"
ID_LIKE="opensuse suse"
VERSION_ID="20220527"
PRETTY_NAME="openSUSE Tumbleweed"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:tumbleweed:20220527"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/"
DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed"
LOGO="distributor-logo-Tumbleweed"

The laptop hangs right after showing the initrd message switching to a blank console screen. There seems to be a prompt that is not shown as after pressing “return” roughly 50x, the boot process proceeds by switching to the Plymoth boot screen and booting normally. Unfortunately the log files do not show anything as this problem seems to occur prior to when logging starts. dmesg shows a boot process of 20 secs, when counting clearly starts after the prompt has been (invisibly) answered.

/var/log/boot.log starts with “Started Show Plymouth Boot Screen.”, also is starting only after the problem arises. Is there any way to get logging information from very early boot stages?

Thank you very much in advance.

2

earlyprintk=vga maybe?

3

Sure: How to Debug systemd boot process in CentOS/RHEL 7 and 8 – The Geek Diary

4

Thanks for the responses. I got the relevant output by editing the linux line from grub (pressing ‘e’ on the boot entry) and deleting options “splash=silent” and “quiet”. It turnded out that the hang was caused by an unstable time stamp counter (this is a single core machine). The solution was given right in the kernel output: adding “tsc=unstable” to the linux options (making it permanent with yast) solved the problem.

Two strange observations remain: Why is pressing return (but not other keys) influencing the tsc measurements? Why is the tsc measurement time not counted against the kernel time?