24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system

Bug #2063983 reported by twelfth
38
This bug affects 7 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Config: Ryzen 5 5600X with Radeon 6700 XT GPU, a Navi22 card.

Using xUbuntu.

I had been daily driving the 24.04 nightly iso since March. About a week ago, I took a kernel update via apt and rebooted. The result was that the system would hard freeze to a black screen after the initial kernel messages cleared from the screen. Ctrl-Alt-Del did nothing, switching terminals (ctrl-alt-f#) did nothing, had to hard power off to regain control of the system.

I tried various fixes, none of which permanently stuck. This includes nomodeset in grub, rebooting into safe mode, checking for proprietary drivers. Safe mode allowed me to reboot once more into desktop, but then any subsequent reboots would result in a black screen lockup.

Suspending while able to use the desktop before reboot would cause a black screen lockup did not seem to cause any issues.

3 days before 24.04 was officially released, I reflashed the most recent installer iso to my thumbdrive, copied my home folder to my RAID and did a full wipe and fresh install.

First reboot after installation always went to the desktop. Subsequent reboots always resulted in a black screen lockup.

Memtest cleared without errors.

Again tried various fixes, nomodeset, safe mode, drivers. The only consistency was that regardless of what I could do to regain control or what I did differently when doing a wipe and reinstall, I would always reboot to a black screen.

Once 24.04 was officially released, I again did a full wipe and reinstall and encountered all of the above same issues as before.

After mentioning this in #ubuntu on libera, someone suggested a kernel downgrade.

24.04 as installed was using 6.8.0-31.31

Using Mainline, I downgraded to the next minor version below 6.8 that was considered stable. 6.7.10

Problem went away. No more black screen on boot, no more hard power offs required to be able to use my system again, no suspend issues. Was not necessary for me to do anything else to maintain a consistent successful reboot to desktop.

Did yet another full wipe and fresh install of 24.04, only installing Mainline upon first reboot to install 6.7.10, using Grub Customizer to edit the default grub option to boot the 6.7.10 kernel instead.

No issues.

I apologise that I did not collect logs during this process.

---

For those affected by this issue, this was my fix:

Install 24.04, reboot, at the desktop, open a terminal window and add the following PPAs:

sudo add-apt-repository ppa:cappelikan/ppa
sudo apt update
sudo apt install mainline

sudo add-apt-repository ppa:danielrichter2007/grub-customizer
sudo apt-get update
sudo apt-get install grub-customizer

Run mainline-gtk, install kernel version 6.7.10

run grub-customizer, move "Ubuntu, with Linux 6.7.10-060710-generic" to top of list, making it the default option. Save and reboot.

affects: ubuntu → linux (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Xavier MOGHRABI (xavier-moghrabi-gmail) wrote :

I had the same issue while trying to upgrade to Kubuntu 24.04 or install Kubuntu 24.04 from scratch. I get a black screen at startup.

My graphic card is also an AMD GPU : Radeon RX 7800 XT.

Revision history for this message
twelfth (twelfth) wrote (last edit ):

I forgot to mention in my summary that I could not duplicate any of the issues I was having when I swapped out the Radeon 6700XT for a GeForce 1070 in my Desktop and repeated the process of doing a full wipe and reinstall of 24.04. I plan to repeat these steps with my current configuration (Ryzen CPU and 6700XT GPU) after swapping out the SSD so I can collect logs as requested of me in #ubuntu on Libera.

twelfth (twelfth)
description: updated
description: updated
Revision history for this message
Jarmo Ilonen (trewas) wrote :

Some additional information on my system with AMD Ryzen 5 8600G w/ Radeon 760M Graphics.

This is a new system originally installed with Ubuntu 23.10 which worked ok. After upgrading to 24.04 the same thing started happening: blank screen after boot. Works when booted from 24.04 live USB, but after installation I could not figure out permanent fix for blank screen. It does work in safe mode (nomodeset), but of course quite slowly.

When I installed SSH server in safe mode and rebooted back to blank screen, I could login remotely even though the system looked dead. Nothing stood out in the logs, looked like the system thought it was working normally. Magic sysrq also works.

I went back to 23.10 for now, but a couple of week old logs from booting 24.04 are available if they might be useful.

Revision history for this message
twelfth (twelfth) wrote :

Screenshot of my grub-customizer configuration that resolved my boot to blackscreen issue.

description: updated
Revision history for this message
Tom Reynolds (tomreyn) wrote :

I think it would be quite helpful if any of you could file separate bug reports of testing a fresh 24.04 install of any flavour and could gather the full kernel log from when the system booted to black screen, with AMD graphics. That's because this can have many different causes, and we do not know the root causes for what you're describing are identical at this point.

While obviously what you report is correct and a real issue for each of you, developers need to identify root causes across ideally multiple installations of the same type and in the same or similar environment.

However, from a developers' perspective, all we have so far is a few reports of "under some (possibly different) circumstances, an unsupported upgrade to 24.04 resulted into the system booting to a black screen, with some (different models of) AMD graphics. Having seperate reports including logs which *may* (should) point to the root cause would certainly help understanding whether these are isolated corner cases with similar symptoms but different root causes, or whether there really is a generic issue affecting some or many amdgpu driven devices with the 24.04 LTS GA kernel.

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

I think this bug also affects Intel GPUs. I did an installation today that resulted in a black screen without "nomodeset". See:
https://bugs.launchpad.net/ubuntu/+bug/2063877

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

... oh yes, I had the same problem with AMD Radeon Integrated Graphics; see the same bug report:
https://bugs.launchpad.net/ubuntu/+bug/2063877

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

I followed this advice (mentioned above): https://www.reddit.com/r/Kubuntu/comments/1cdko49/comment/l1uf573/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

It seems that "quiet splash" is the actual problem, not "nomodeset" (solution).

I edited the GRUB entry as follows (with results added):

1) With only "quiet splash" (no "nomodeset"), default installation, fresh install of Kubuntu 24.04: only black screen, nothing happens.

2) Add "nomodeset" to "quiet splash": everything works perfectly. Also works permanently with editing of /etc/default/grub.

3) Delete "quiet splash" in GRUB and do not add "nomodeset" (or delete "nomodeset", if previously added): everything works perfectly (see Reddit link above).

4) Delete "nomodeset", after having added it to /etc/default/grub and updated grub previously, but leave the 'original' "quiet splash": computer hangs, completely unresponsive, after showing the following code:

Booting a command list
Loading Linux 6.8.0-31-generic ...
Loading initial ramdisk ...

5) Again, boot without both "quiet splash" or "nomodeset": everything works perfectly. Also works permanently with /etc/default/grub.
It went quite fast, but after "Loading initial ramdisk ..." I think the next code line was "secure boot is enabled". It might be a problem with "secure boot" and "quiet splash". Secure boot is enabled in both my installations, so I can't try the other option ("secure boot" disabled in the EFI BIOS before installation).

Workaround (for me):
- Edit /etc/default/grub: the line "GRUB_CMDLINE_LINUX_DEFAULT=". Delete the words "quiet splash" (leave the quotation marks '').
- Run sudo update-grub

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

If you tell me how to "gather the full kernel log from when the system booted to black screen", I might try that.

Revision history for this message
Tom Reynolds (tomreyn) wrote :

Please reproduce the problem (boot to black screen). Then reboot in a way that you can use the computer and run this without rebooting again:
  sudo journalctl -k -b -1 > /tmp/kernel.log
Then attach /tmp/kernel.log to your bug report.

Thanks!

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

Notebook Lenovo V17 G4 IRU 83A20009GE (also called: Lenovo V17 Gen 4 i) with Intel Iris Xe Graphics.

- "quiet splash" deleted by me from /etc/default/grub = everything fine.
- Added "quiet splash" to /etc/default/grub again = black screen.
- Hard reset, and then deleted "quiet splash" from GRUB after ESC, editing with "e" and CTRL + x = computer starts.
- entered sudo journalctl -k -b -1 > /tmp/kernel.log in a terminal. The output is attached.

Revision history for this message
theofficialgman (theofficialgman) wrote :

likely duplicate of earlier bug reported by myself and triaged. Please read it for better information
https://bugs.launchpad.net/systemd/+bug/2063143

here is the TLDR:
"AMD kernel developer wants to classify this is as both SDDM bug and plymouth bug https://gitlab.freedesktop.org/drm/amd/-/issues/3341. amdgpu kernel driver is not ready by the time that sddm and plymouth are started in some cases (race condition). Marking this as a sddm and plymouth bug (in addition to linux) because of this.

To me it seems that at least a systemd service should be handling blocking starting GUI userspace services until the kernel drivers are actually loaded but that is just my thought. I guess the AMD developer sees this the same way you do Daniel."

Revision history for this message
Tom Reynolds (tomreyn) wrote :

This is now a mix of maybe similar seeming, but likely different issues with different root causes, also mixing AMD / Intel GPUs.

Anyone but twelfth (OP): Please remember to post separate / new bug reports - not here. To file a bug, use "ubuntu-bug linux" if you expect it to be about a packaged and supported Ubuntu Linux kernel.

I think this bug report should be closed unless twelfth can reproduce the issue with a fresh 24.04 install and provide logs as indicated above.

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

I've just read https://bugs.launchpad.net/systemd/+bug/2063143

Just two observations:
- In my two cases (AMD and Intel GPU notebooks) the black screen was 100%, not a fraction of boot processes. With "quiet splash" "on" I was never able to boot. The behaviour was also absolutely identical with AMD and Intel GPU.
- I was never using Wayland (Kubuntu "out of the box": Plasma (X11)).

Revision history for this message
Iago Alonso Alonso (aker666) wrote :

Hi,

I can confirm the same problem installing Kubuntu 24.04 with an AMD Ryzen 9 6900HX and an AMD Radeon RX 6850M XT.

The only way I could see the login screen was to go into recovery mode, try some options to see if it did anything and then hit continue to boot the system.

Regards.

Revision history for this message
Denis F. (fdees) wrote :

Hi, also has this problem after reboots with Ubuntu MATE 24.04 and HONOR MagicBook laptop with AMD Ryzen 7 3700U / Radeon Vega Mobile graphics. The only way to boot is from recovery mode.

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.