Plymouth showing black screen on boot

Ask Fedora
, ,
1

Hi kind folks, can I seek your advice in resolving this issue?

Recently, plymouth shows a black screen on boot. Looking at /var/log/boot.log, plymouth seems to be working fine:
[ OK ] Started plymouth-start.ser…e - Show Plymouth Boot Screen.
Starting plymouth-quit-wai… until boot process finishes up...

and this is my /etc/plymouth/plymouthd.conf

[Daemon]
Theme=details
ShowDelay=0

and my /etc/default/grub

GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 initcall_blacklist=simpledrm_platform_driver_init"
GRUB_DISABLE_RECOVERY="true"
GRUB_ENABLE_BLSCFG=true

Oddly enough, I still see the splash screen when my computer is turning off, just not on boot.

The splash screen works on a previous kernel version.

2

if you check the date on your boot.log I expect you will see that it is old.
Mine is from 2022.

Look in the the journal with journalctl -b 0 for logs from the boot.

It could be that akmod is building the nvidia driver when you get a black screen.

Does this happen only after an update or all the time?

3

Hi Barry, thank you so much for the response!

This happened for the first time after a kernel update, and now it happens every boot.

I think it’s a very good point that the boot log may be outdated, but it seems in my specific case, that is not the case.

running journalctl -b 0, I can still see entries where plymouth runs:

Jun 10 08:47:05 fedora systemd[1]: Starting plymouth-read-write.service - Tell Plymouth To Write Out Runtime Data..
Jun 10 08:47:05 fedora systemd[1]: Finished plymouth-read-write.service - Tell Plymouth To Write Out Runtime Data. Jun 10 08:47:05 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=plymouth-read-write comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jun 10 08:47:14 fedora systemd[1]: Starting plymouth-quit-wait.service - Hold until boot process finishes up...
Jun 10 08:47:14 fedora systemd[1]: Received SIGRTMIN+21 from PID 495 (plymouthd).
Jun 10 08:47:35 fedora systemd[1]: Received SIGRTMIN+21 from PID 495 (plymouthd). Jun 10 08:47:35 fedora systemd[1]: Finished plymouth-quit-wait.service - Hold until boot process finishes up. Jun 10 08:47:35 fedora systemd[1]: Reached target multi-user.target - Multi-User System. Jun 10 08:47:35 fedora systemd[1]: Reached target graphical.target - Graphical Interface. Jun 10 08:47:35 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=plymouth-quit-wait comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

Further, the date on /var/log/boot.log is of the correct date: ------------ Sat Jun 10 08:47:05 +08 2023 ------------ [ OK ] Started plymouth-start.ser…e - Show Plymouth Boot Screen.

EDIT: I have tried the steps listed here: Fedora 38/37/36 NVIDIA Restore Plymouth (BIOS/UEFI Users) :: If Not True Then False but to no avail.

I have also verified that the command line entry has rhgb quiet
[ 0.000000] Command line: BOOT_IMAGE=(hd0,gpt7)/vmlinuz-6.3.5-100.fc37.x86_64 root=UUID=7b492da9-e65f-4e0d-b68c-67123c046ed9 ro rootflags=subvol=root rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 initcall_blacklist=simpledrm_platform_driver_init

Further, neither Ctrl-Alt-F2 nor Esc has any impact while the boot process.

4

My issue was resolved by upgrading from kernel-6.3.5-100.fc37.x86_64 to kernel-6.3.6-100.fc37.x86_64. :slight_smile: