Leap 15.2 boot and displayport


Just wanted to report I have installed Leap 15.2 on an HP ZBook 17 G6.

Hard drives are partially encrypted (not every partition).

Just wanted to report that almost everything seems to work.

One small glitch is that when I have a second monitor plugged in to the mini-displayport connection, the system hangs while booting (after entering the disk passwords).

If that same monitor is connected with hdmi, the system boots fine.

My work-around is to unplug the monitor until machine is booted.

This problem is not crippling, merely a nuisance.

Any suggestions would be appreciated.



A wild guess. There might be a kernel module that is needed for the monitor but which is not included in the “initrd”.

Maybe run (as root)


but be sure that the monitor is plugged in before running.

I don’t know whether that will help, but it won’t hurt to try.

What exactly do you mean by “hang”? Does boot ever complete, but just take a long time? Can you find out more precisely when the hang occurs by examining dmesg or journal? If persistent journal is enabled, you can examine the tail end of the journal from the prior boot thus:

sudo journalctl -b -1 -e

You can page backwards if necessary to find password entry, then work forwards. You can redirect journal to disk and then upload to http://susepaste.org/ or http://pastebin.com/ so we can take a look if you can’t ID a problem point on your own. There may be clues also in /var/log/Xorg.0.log or /var/log/Xorg.0.log.old, which you might find by comparing the two logs.

I am quite embarrassed to report that this problem did not repeat itself.

In an attempt to respond to the questions above, I set up a video camera to film the boot process. I did this because it appears that HP’s bios remains involved after the kernel is selected at the boot prompt. I say this because HP’s splash screen appears again after the kernel begins to load. Because of this, I was uncertain how much of the process would be reflected in the logs and wanted to document the failure exactly before I went to the logs.

So I set up the camera, and swiveled the laptop stand to squarely face the camera, began recording, and turned the system on. After a half dozen or so failures previously, this time the system completed it’s boot.

I don’t remember getting any significant updates today.

The only thing I can imagine is that jiggling the displayport cable may have allowed a pin on the set to be readable (when it wasn’t before) and thus reported that it was ready and therefore the system continued uninterrupted.

So this mysterious problem may still be mysterious, but it seems to be no longer a problem. (We shall see.)

I appreciate the interest and the prompt responses to help.

If there is anything else I need to provide, Please let me know and I will do so.

Thanks again all.


I’m glad things are working, even if we are not sure what caused the problem.

Thanks for reporting back.