Kernel 5.4.0-37-generic leads to black screen after grub, 5.4.0-26-generic works normally

[Freek van Hemert]

I don't know how to get more info, if anyone gives me any pointers I'd be happy to dig into it.
My laptop is an HP Elitebook 820 G3.

I expect: The screen where I enter the drive decryption key
What happens: The screen goes black after grub

It does work normally with the older kernel 5.4.0-26-generic.

Extra info:
Description: Ubuntu 20.04 LTS
Release: 20.04

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1882991

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Freek van Hemert (freekvh)]

Sorry, I think this can be closed, I kept seeing weird things on boot, I reinstalled the entire OS, this time choosing the default partitioning in stead of something self organized and I haven't had the issues since.

[Paul White (paulw2u)]

Closing at the request of the reporter in comment #2.

[byron_rs (byron-rs)]

Hello, I had the exact same error yesterday with kernel 5.4.0-37. I tried to repair / reinstalled kernel and GRUB but nothing worked. I had to revert back to kernel 5.4.0-33 on a 840G3.

[Derek (derek-shnosh)]

Vyron, how did you revert?

[Derek (derek-shnosh)]

I posted that before I was done putting relevant information in.

I have a Lenovo P51 running Kubuntu 20.04 that I just updated to 5.4.0-37 and am getting a black screen after rebooting. I was/am running Nvidia driver 440.82 and saw the DKMS process during the apt upgrade.

I tried resigning the drivers with a new key anyways, no resolve.

I then tried booting with the 5.4.0-33 kernal via advanced options, also no resolve.

[byron_rs (byron-rs)]

Hey Derek,

In my case I was able to boot on kernel 5.4.0-33.
From there I removed kernel 5.4.0-37.

There is something wrong with the update / kernel.
When I tried booting on 5.4.0-37, it's like nothing happened. Just a black screen.
I'm sure we are all facing the same issue.
It's too bad none of us can provide any log files for this bug.

Hope you can fix it!

[Derek (derek-shnosh)]

Vyron, thanks for the response.

I was able go to TTY2 (CTL-ALT-F2) and get the dpkg log from when I ran `upgrade -y`; it is attached here. Not sure what else to look at or how to TS from here.

[Derek (derek-shnosh)]

I ran `apport-bug` and copied it off to an SMB share, but am not sure it's propert etiquette, or wise, to attach publicly.

[Derek (derek-shnosh)]

I can boot fine to either kernel (5.4.0.33 or .37) if nvidia driver is not installed, using nouveau. But no matter what Nvidia driver I use (or install method) I cannot get the NVidia driver reinstalled properly.

[Derek (derek-shnosh)]

At some point I was able to purge anything installed with *nvidia* in it... reboot and get UI without `nomodeset` intervention. I then installed `nvidia-driver-435` and have left it alone since then. I'll try 440 again another time.

[Derek (derek-shnosh)]

Well "another time" came and I installed 440 again via apt and its booting fine; can only assume that the blanket purge of all things nvidia and subsequent reboots was the resolution.