Freshly installed Debian hangs at boot when/after loading X.509 certificates.

[Meow]

Fresh Debian installation.

After transplanting the OS/swap drives to the workstation where they should be deployed, Debian fails to boot, always hanging after printing "Loaded X.509 cert: Debian Secure Boot CA ...".
No other virtual consoles can (yet) be opened, ctrl-C does not help either, only the power switch.

Never had such a thing in the past.
Not using UEFI or that "secure boot" crap.

What does one need to do, so a Debian boot drive created on one system also boots if it is being put into another computer?

Any idea what went wrong?
Hardware are various Supermicro boards.

[bw123]

I used to do stuff like that occasionally for whatever reason. It's not as easy as it sounds. Could be gpu mismatch, missing firmware, an led or other hardware, like a backlight. Systemd tries to restore a lot of stuff...

see: systemd.restore_state @ https://www.freedesktop.org/software/sy ... -line.html

Try booting to single user first, and look in the kernel ring buffer for a hint...

Code: Select all

$ man dmesg

While there, update the initramfs, before rebooting.

With systemd booting, it doesn't matter what the last "...loading" line says when it hangs, it's a parallel kinda thing now.

good luck,
bw

[bw123]

p.s. You might want to add to the topic, "Freshly... but moved to another machine."

[Aki]

Hello @Meow,

p.s. You might want to add to the topic, "Freshly... but moved to another machine."

I agree with bw123.

Can you please update the subject for the first post specifying that the disk has been moved to another computer ?

Do the two computers involved (disk donor and disk recipient) have the same graphics card/GPU?

[Aki]

Moved to the “Installation” sub-forum

[Meow]

The problem on the computer mentioned disappeared without any hint why.

Can you please update the subject for the first post specifying that the disk has been moved to another computer ?

However, meanwhile, I installed Debian onto another machine.
There the problem appeared instantly after installation, without moving the disk.
So this does not seem to matter.

Do the two computers involved (disk donor and disk recipient) have the same graphics card/GPU?

No... are there nowadays things that lock a particular Debian installation to its hardware, as we know of Windows?

There is not so much to be taken in question, all these installations were quite simple (debootstrap, tasksel)
Now I am thinking about which software installed could be the culprit, by including that X.509 crap, and needs to be blacklisted.

[Meow]

see: systemd.restore_state @ https://www.freedesktop.org/software/sy ... -line.html

Try booting to single user first, ...

Unfortunately, single-user boot attempts stop the same way, leaving the computer unresponsive except for ctrl-alt-del...

The kernel command line stuff is interesting... You might be right that it's possibly a completely different thing that makes the boot freeze.
While booting Linux, the keyboard lights go down for a moment, and at about the same time the certificate loading message appears, the keyboard lights up again.
I did about a dozen reboot attempts, hoping for the thing which makes the boot halting to disappear. It didn't disappear, but one time there appeared an additional line after the message "Loading compiled-in X.509..." before the system froze:

Code: Select all

Loaded X.509 cert 'Debian Secure Boot CA: <hex...>'

Any idea to which package(s) this belongs?
Or, any other idea what to try to avoid that problem/make it go away?

[Meow]

Maybe there exist some Grub boot options to deactivate particular things in the kernel, like "secure boot", "certificate" handling and similar showstoppers?

Edit:
It's a bit annoying... I looked forward to finally have time to play with Debian and explore it, and now this stupid boot hang issue blocking that.

Edit 2:
After all what I read last hour, it looks like that Linux nowadays even gets problems with machines configured as/running CSM... because, I really have no idea what that secure boot crap matters in CSM mode...

Edit 3:
And what I also do not understand is that on the previous install the hang disappeared after about a dozen reboots, and did not appear again after that... what is going on here?