I installed the beta on a system with an AMD 5500 XT. Plymouth does not display during startup, it does display on shutdown on restart.
My other system with proprietary NVIDIA drivers displays plymouth perfectly. Can someone help me out here?
Edit: I also discovered that legacy boot in the installer does not work. When I first installed on the AMD system I forgot it was in legacy boot. The install would complete and run until I shutdown or restated, then the system could not find the boot partition. After changing the BIOS to UEFI everything is alright except Plymouth not displaying on start. The screen just stays black until the log on appears.
Have you tried starting in Safe Graphics mode?
What happens?
1 Like
Have you tried starting in Safe Graphics mode?
I do not have that option…
I installed Resolute beta this past week and it was there in the options when I started in live mode (should be one/two below Try or Install Ubuntu)?
If you did not see that, perhaps the image you used was corrupt somehow?
This is on an installed system. The problem seems to be from the way the kernel loads the graphics driver.
My next step would be to add nomodeset as a temporary workaround to see what happens.
You can do this from GRUB when the computer starts and add it after quiet splash (should be a space between).
Press e to edit, find the line that starts with linux /boot/vmlinuz...
Ctrl+X to boot.
1 Like
I tried three tutorials on fixing this, no luck… I have read using nomodesetwill make the system no longer boot, so I have not got that desperate just yet. AMD graphics are open source and I never get a working plymouth. My system with NVIDIA graphics, closed source drivers, displays plymouth with any distro. Really? Just a little frustrating. After all these years you would think plymouth would just work by now.
Not sure where you read that but all that nomodeset does is to disable kernel mode setting, which prevents the system from loading advanced graphics drivers early in boot.
Instead, it falls back to a basic display mode. This helps confirm if the issue is caused by:
As I said, this is only temporary during boot to check if this is the problem.
However, if you are unwilling to try this I have another suggestion.
Start the computer and when you get to GRUB follow the instructions as above to edit the boot line.
Instead of adding something after quiet splash, remove those words and replace it with text.
Leave it within the quotation marks.
Then Ctrl+X to continue.
What happens? Are you able to spot any error messages that might be relevant?
I found this on the Arch wiki, Note that nomodeset disables KMS, which is required for AMD cards, I have watched the boot sequence, nothing stands out.The AMD system does show signs of driver issues though, such as a busy cursor after certain apps are launched.
I think plymouth may not be displaying on the AMD system because it detects the monitor resolution late in the boot process. I noticed the system with NVIDIA graphics has the resolution correct from the grub screen on. The AMD system shows a lower resolution on grub.
Problem solved! I tried this.
To change the GRUB resolution on Ubuntu, edit the /etc/default/grub file and set the GRUB_GFXMODE variable to your desired resolution, such as GRUB_GFXMODE=1920x1080. Then, run sudo update-grub to apply the changes.
When I compared the two systems the resolution grub was using was different. Wish I would have noticed that before trying a bunch of other solutions, lol. The problem was much simpler than I thought. Anyway, maybe this will help someone else having this issue. Thank you for all the suggestions.
Edit: Don’t forget to remove the hash mark on the line you edit.
1 Like