Black screen on restart after update: fix "nomodeset"

Bug #2068793 reported by Fred Jupiter
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
New
Undecided
Unassigned

Bug Description

Kubuntu 22.04
Updated to Kernel 5.15.0-107-generic on 6 June 2024 (I think)
Notebook HP 17-ca1010ng
AMD Ryzen 5 3500U
AMD Radeon Vega 8 (IGP)

Expected:
After updating via Muon (incl. the kernel, see above, I think), the computer should restart normally.

Actual:
After the HP logo, the computer displays a black screen, backlit. Nothing happens, completely unresponsive.

Workaround:
Temporary:
Add "nomodeset" before "quiet splash" via editing of GRUB menu.

See: https://askubuntu.com/questions/162075/my-computer-boots-to-a-black-screen-what-options-do-i-have-to-fix-it

Permanent:
Edit /etc/default/grub: the line "GRUB_CMDLINE_LINUX_DEFAULT=". Add the word "nomodeset" before "quiet splash".
- Run "sudo update-grub"

Revision history for this message
Fred Jupiter (fredjupiter) wrote :

oh yes, the key to press for the GRUB menu after booting with a modern (U)EFI bios is: ESC, not Shift (as mentioned in the link above).

Revision history for this message
rfc (rfc0) wrote :

The "black screen after reboot" symptom is equivalent to the symptom from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2068738

But, the linux kernel version mentioned in this bug report is Kernel: 5.15.0-107-generic, not 5.15.0-112.

It is possible that the kernel version in this bug report was mistaken, or it could be a different issue causing the same symptom.

There is a similar report mentioning 5.15.0-107 here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2068735

Revision history for this message
Mario Limonciello (superm1) wrote :

AFAIK It's a bad backport to 5.15 stable. If it's what I think, here's the fix (IIRC).

https://<email address hidden>/

Try applying that to your 5.15 kernel.

Revision history for this message
Fred Jupiter (fredjupiter) wrote :

Yes, the broken kernel probably actually is Kernel 5.15.0-112-generic.

I help people over the phone, or very quickly, and then I don't have access to the machines any more.

I was able to have a quick look just now: Kernel 5.15.0-112-generic is the most current. I assume this kernel is causing the trouble.

Sorry about the wrong information.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.