Only black screen on boot with AMD Barcelo and Intel Iris Xe GPU with "quiet splash" (Grub)

[Fred Jupiter]

I have a HP 17-cp1147ng notebook from the end of 2022.

The notebook worked "out of the box" with the Kubuntu 22.04 LTS. No black screen there.

I've just installed Kubuntu 24.04 LTS on it.

I get a black screen after the HP logo on starting up (first time). Only a hard reset would let me do anything with the computer again, no mouse, now keyboard, no picture.

I followed this advice (section "Black/purple screen after you boot Ubuntu for the first time"): My computer boots to a black screen, what options do I have to fix it?

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

It worked (once). So I followed the advice specified there, and went to: "How do I set 'nomodeset' after I've already installed Ubuntu?"

https://askubuntu.com/questions/38780/how-do-i-set-nomodeset-after-ive-already-installed-ubuntu

Nomodeset works permanently for booting. But after a short "test drive" I think all energy-saving states equally result in a black screen requiring a hard reset (I would have to check that by trying all kind of states [screensaver, sleep-mode etc.)

I installed only Kubuntu on the entire hard disc, with no bells and whistles.

amdgpu is installed, I checked that: xserver-xorg-video-amdgpu 23.0.0-1build1

Additional hardware information:

lspci -v | less: VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Barcelo (rev c2) (prog-if 00 [VGA controller]) DeviceName: AMD Radeon Integrated Graphics Subsystem: Hewlett-Packard Company Barcelo Flags: bus master, fast devsel, latency 0, IRQ 255, IOMMU group 11 Memory at fce0000000 (64-bit, prefetchable) [size=256M] Memory at fcf0000000 (64-bit, prefetchable) [size=2M] I/O ports at 1000 [disabled] [size=256] Memory at d0400000 (32-bit, non-prefetchable) [size=512K] Capabilities: Kernel modules: amdgpu

sudo dmidecode -s bios-version: F.03

[Fred Jupiter (fredjupiter)]

I just closed the lid of the notebook, probably entering "suspend" mode. Yes, the screen was black, frozen, no mouse no keyboard. Only a hard reset helped. The notebook started - with the help of nomodeset - like before.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/2063877/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Fred Jupiter (fredjupiter)]

I can confirm that this bug also affects the notebook Lenovo V17 G4 IRU 83A20009GE (also called: Lenovo V17 Gen 4 i) with Intel Iris Xe Graphics.

I've just installed Kubuntu 24.04 LTS on it ("secure boot" enabled in EFI Bios; otherwise simply by attaching installation USB stick). The installation worked smoothly and perfectly.

First reboot brought a black screen. Nothing at all happened after the Lenovo logo. I tried this with a hard reset a couple of times. Then I executed the following workaround.

- It's an UEFI installation, so pressed ESC key once after hard reset (after Lenovo logo).
- Edited GRUB via pressing "e".
- added "nomodeset" to line beginning "Linux ..."
- started OS with CTRL + x
- It worked, perfectly.

OS does NOT work without nomodeset.

Unlike the HP notebook (see above), the energy saving options seem to work. So this bug seems not to be so serious for the Lenovo notebook. I could return from manually induced "Standby" mode by simply pressing any key.

Editing /etc/default/grub by adding "nomodeset" to "GRUB_CMDLINE_LINUX_DEFAULT:" line works permanently as well.

lspci -v | less: 00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-P [Iris Xe Graphics] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Lenovo Raptor Lake-P [Iris Xe Graphics] Flags: bus master, fast devsel, latency 0, IRQ 255, IOMMU group 0 Memory at 6000000000 (64-bit, non-prefetchable) [size=16M] Memory at 4000000000 (64-bit, prefetchable) [size=256M] I/O ports at 3000 [size=64] Expansion ROM at 000c0000 [virtual] [disabled] [size=128K] Capabilities: <access denied> Kernel modules: i915, xe

sudo dmidecode -s bios-version: MCCN24WW

[Fred Jupiter (fredjupiter)]

Deleting "quiet splash" is the better workaround, rather than "nomodeset". I can confirm that without either "quiet splash" AND "nomodeset" in GRUB all energy saving works in the HP notebook with AMD Radeon Integrated Graphics (see above).

The following is copied from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063983 :

I followed this advice: 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

[theofficialgman (theofficialgman)]

likely duplicate of earlier reported and triaged bug 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."

yes this affects all drivers. the kernel GPU drivers are not done loading by the time that SDDM starts which results in a black screen.

[Fred Jupiter (fredjupiter)]

Okay, but I changed the heading of this bug report: Identical behaviour with "Intel Iris Xe GPU". Just to mention this. See also: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063983/comments/13