Kernel 6.4 won’T boot successfully, I assumed something related to TPM (can’t enable/disable in BIOS, as Coreboot installed, so I simply pulled the TPM), but that didn’t help.
Here the journal for unsuccesfull boot:
Kernel 6.3.9 boots just fine:
[sudo] password for root:
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 08)
00:02.0 VGA compatible controller: Intel Corporation Skylake GT2 [HD Graphics 520] (rev 07)
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 08)
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
00:14.1 USB controller: Intel Corporation Device 9d30 (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #3 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
00:1f.5 Non-VGA unclassified device: Intel Corporation Device 9d24 (rev 21)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07)
Both logs stop at the same line and the log lines are truncated. Always use
journalctl --full --no-pager
journalctl output. But if kernel fails to boot it is unlikely journal will contain the reason, you need to capture console output.
Hi and many thanks!
This is what it looks like when boot freezes:
The kernel has booted. Did you try
Ctrl-Alt-F2 if you get login prompt?
Otherwise boot with
plymouth.enable=0 and without
quiet on kernel command line, it may show more information.
it was without quiet and there is no plymouth in the kernel boot line
The machine doesn’t even respond to REISUB. No VNC, no ssh. Nothing. Have to pull power cord…
So what? On boot plymouth is started and hides kernel messages.
I added “plymouth.enable=no” to kernel boot line, absolute identical output on screen, do you need a photo or do you believe me?
as the last output is network is down: might there be a problem with “ipv6.disable” in the kernel line?
Are any keyboard LEDs blinking at this point?
nope, all black … …too short to post… sigh…
debug to kernel command line.
With this kernel line
the boot goes 1 step further before freezing:
and once (!) I had a flickering screen at that stage that rebooted automatically within 3-5 sec. Graphics?
Are doing it on purpose? Where did I say to add this parameter?
debug doesn’T add anything meaningfull before the “authorization manager” message, just some “systemd-journal… Successfulyl sent some stream file descriptor to service manager” spam above…
in your second post in this thread?
You posted the same picture of bootloader screen.
OMG, really? It was with plymouth.enable=0, no quite, no resume, no ipv6.disable…
Yes, it was the first link in your post. And the second link sounded like it would be screen when freeze happened. Try to look yourself.
sorry, the boot ends here with plymouth.enable=0, no ipv6.disable and no resume
The screen flicker and reboot is not reproducible on kernel 6.4 and doesn’t occur with kernel 6.3.9
What should I do with that?
Can you boot into single user or multi-user? Just add a single
3 to kernel command line.