Hi everyone! I noticed that recently the boot animation on my Fedora system has disappeared - there is no brand logo, and the spinning circle with Fedora logo has been replaced with random three dots that don’t even appear on the center of the screen. The system boots normally, it just doesn’t show the animation - interestingly enough, it does show it at shutdown, just not at boot. The same dots also appear while installing updates. How can I fix this? I tried these solutions: Restoring Plymouth theme to default and regenerating needed files (sudo plymouth-set-default-theme bgrt & sudo dracut -f) Resetting Plymouth to default (sudo plymouth-set-default-theme --reset) And stil no luck. :frowning: My system specs: Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.8.10-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i3-6006U CPU @ 2.00GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520 Manufacturer: HP Product Name: HP Laptop 15-bs0xx System Version: Type1ProductConfigId I’d be grateful for any help. :) Reproducible: Always Steps to Reproduce: 1.Boot up device 2.Wait 3.See the three dots on the upper left side of the screen instead of the manufacturer logo in the center of the screen & Fedora Logo with the spinning circle below it. Actual Results: My Fedora installation boots without the graphical logo, and displays three dots instead. Expected Results: Boot up and correctly display manufacturer logo & Fedora logo.
I’m seeing the same on my laptop - grey screen, three white dots / small squares off-centred towards the top-left of the screen. And curiously it works as expected during shutdown. I've also tried the above remedies with no success. This has only become an issue since upgrading to Fedora 40 - not an issue with Fedora 39 and earlier. Lenovo Legion 5, AMD Ryzen 7 5800H with Radeon Graphics, AMD ATI Radeon Vega Series / Radeon Vega Mobile Series, AMD ATI Radeon RX 6600/6600 XT/6600M.
Update: switching to a previous kernel version displays correct boot animation. Update: switching to an earlier kernel version restores boot animation Thanks to a helpful Reddit comment I tried switching back to an earlier kernel version. Results are as follow: Kernel Version: 6.8.11-300.fc40.x86_64 (64-bit) - animation not working during boot - displays three dots instead of the Fedora logo. Works fine at shutdown. Kernel Version: 6.8.10-300.fc40.x86_64 (64-bit) - same as above. Kernel Version: 6.8.9-300.fc40.x86_64 (64-bit) - animation works properly during boot and shutdown - displays the Fedora logo and spinning circle correctly. To sum up: this seems to be a kernel-related issue, since 6.8.11 and 6.8.10 do not display the animation correctly, while 6.8.9 does.
Same situation here. My configuration: Distro: Fedora Linux 40 (MATE-Compiz) Kernel: 6.9.4-200.fc40.x86_64 GPU: Radeon HD 6670/7670 CPU: Intel Core2 Quad Q8200 I have upgraded from Fedora 38 and never faced this issue before.
But still occurs at kernel version 6.9.4-200.fc40.x86_64. Does not occur at version 6.8.9-300.fc40.x86_64 (and I assume earlier versions as well).
I have been experiencing the same in fedora workstation 40, and posted about it in reddit. It seems that others are also getting this.
So far the only solution is to use kernel version 6.8.9 - all subsequent ones display broken boot animation.
Same here, with Fedora 40 Xfce. Began after upgrade to 6.9 kernel.
Recently there have been a number of reports (bug 2183743, bug 2276698, bug 2283839) about the plymouth boot splash not showing properly on PCs using AMD GPUs. And looking at the comments from different reporters here many of you are using an AMD GPU too. The problem without plymouth and AMD GPUs is that the amdgpu driver is a really really big driver, which easily takes up to 10 seconds to load on older PCs. The delay caused by this may cause plymouth to timeout while waiting for the GPU to be initialized, causing it to fallback to the 3 dot text-mode boot splash. There are 2 workaround for this depending on the PCs configuration: 1. With older AMD GPUs the radeon driver is actually used to drive the GPU but even though it is unused the amdgpu driver still loads slowing things down. To check if this is the case for your PC start a terminal in a graphical login session and run: "lsmod | grep -E '^radeon|^amdgpu'" this will output something like this: amdgpu 17829888 0 radeon 2371584 37 The second number after each is the usage count. As you can see in this example the amdgpu driver is not used. In this case you can disable the loading of the amdgpu driver by adding "modprobe.blacklist=amdgpu" to your kernel commandline: sudo grubby --update-kernel=ALL --args="modprobe.blacklist=amdgpu" 2. If the amdgpu driver is actually used on your PC then plymouth not showing can be worked around by telling plymouth to use the simpledrm drm/kms device created from the EFI framebuffer early on boot, rather then waiting for the real GPU driver to load. Note this depends on your PC booting in EFI mode. To do this run: sudo grubby --update-kernel=ALL --args="plymouth.use-simpledrm" After using 1 of these workarounds plymouth should show normally again on boot (and booting should be a bit faster).
Hi Hans, Thank you for responding! The command ""lsmod | grep -E '^radeon|^amdgpu'" does not return any results, but I ran this command instead: lspci -k | grep -EA3 'VGA|3D|Display' Which provided these results for my laptop: Subsystem: Hewlett-Packard Company Device 8329 Kernel driver in use: i915 Kernel modules: i915 -- 01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 Mobile] (rev 83) Subsystem: Hewlett-Packard Company Radeon R7 M520 Kernel driver in use: radeon Kernel modules: radeon, amdgpu You were right - in my case the Radeon driver was used to run the AMD GPU, but AMDGPU driver was loaded anyway, breaking Plymouth. I followed your instructions and blacklisted the AMDGPU driver by running: sudo grubby --update-kernel=ALL --args="modprobe.blacklist=amdgpu" It just so happened that I also received an update to Kernel 6.9.9 - after installing the update and rebooting Plymouth functions properly with the newest kernel - Fedora logo and the spinning circle are displayed correctly. Thank you for all your help!
(In reply to Hans de Goede from comment #8) > Recently there have been a number of reports (bug 2183743, bug 2276698, bug > 2283839) about the plymouth boot splash not showing properly on PCs using > AMD GPUs. > > And looking at the comments from different reporters here many of you are > using an AMD GPU too. > > The problem without plymouth and AMD GPUs is that the amdgpu driver is a > really really big driver, which easily takes up to 10 seconds to load on > older PCs. The delay caused by this may cause plymouth to timeout while > waiting for the GPU to be initialized, causing it to fallback to the 3 dot > text-mode boot splash. > > There are 2 workaround for this depending on the PCs configuration: > Actually, I went a third route - the issue for me wasn't due to the fact that I had an older card - my card was pretty new. I was sure the issue was related to a race condition, or timing, or something of that order - hence I wanted to force the amdgpu module to be loaded as early in the process as possible. So did a little research on dracut (very difficult to find useful Fedora documentation unfortunately - I had to use Gentoo and Arch docs) and I configured dracut to load the amdgpu module early by adding a file `/etc/dracut.conf.d/00-amdgpu.conf` with the following contents: ` force_drivers+=" amdgpu " ` and then rebuilt the initramfs by executing the following command: ` dracut --force ` This seems to have solved the issue for me at least. I'd be interested to hear if anyone else find that this approach works for them. J.K.
(In reply to Jerry Kiely from comment #10) > Actually, I went a third route - the issue for me wasn't due to the fact > that I had an older card - my card was pretty new. I was sure the issue was > related to a race condition, or timing, or something of that order - hence I > wanted to force the amdgpu module to be loaded as early in the process as > possible. > > So did a little research on dracut (very difficult to find useful Fedora > documentation unfortunately - I had to use Gentoo and Arch docs) and I > configured dracut to load the amdgpu module early by adding a file > `/etc/dracut.conf.d/00-amdgpu.conf` with the following contents: > > ` > force_drivers+=" amdgpu " > ` > > and then rebuilt the initramfs by executing the following command: > > ` > dracut --force > ` > > This seems to have solved the issue for me at least. I'd be interested to > hear if anyone else find that this approach works for them. > > J.K. Hey, I logged into my old Bugzilla account I haven't used in ten years to thank you for this solution. I've been puzzling over this problem since 6.8.10 came out and your procedure works perfectly, I have the nice plymouth boot screen again.
(In reply to Aiden Neal from comment #11) > Hey, I logged into my old Bugzilla account I haven't used in ten years to > thank you for this solution. I've been puzzling over this problem since > 6.8.10 came out and your procedure works perfectly, I have the nice plymouth > boot screen again. You are very welcome. Glad it helped you. J.K.