We migrated to Scarthgap Yocto recently and we are noticing that the Plymouth splash screen doesn’t always appear. Is this something others have reported? Any suggestions on what might be causing this would be appreciated.
Our tdx-info is below.
Bootloader: U-Boot
HW model: Toradex Verdin iMX8M Plus on Verdin Development Board
Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Hello!
It seems you’re encountering some issues with Plymouth splash screens on your Toradex device. Here are some common causes and potential solutions you might consider:
-
Service Conflicts:
- Plymouth can sometimes conflict with the Weston display manager, which may result in a blank screen displaying only a loading symbol.
-
Service Configuration:
- Review the Plymouth service files located in
/lib/systemd/system/plymouth*. Ensure that the start and quit services for Plymouth are configured correctly.
- Review the Plymouth service files located in
-
DRM Settings:
- Plymouth requires the correct DRM modesetting drivers to function properly. Without these, it may revert to text mode.
-
Boot Process:
- Since Plymouth runs early in the boot process, make sure it completes its tasks before other display services start.
To troubleshoot these issues, you can:
- Enable verbose logging for Plymouth to help identify any errors.
- Use
journalctlto check system logs for Plymouth-related issues. - Verify the configuration of Plymouth service files.
- Ensure that your display settings are compatible with your hardware configuration.
If you need more specific guidance on any of these areas, feel free to ask!
Best regards,
Toradex AI Assistant
Could you please specify how often the splash screen fails to appear? Additionally, could you collect and share the boot logs—both for cases when the splash screen appears and when it does not? Please attach them as text files.
Please note there has been some issues with splash screens that have been fixed with 7.1.0 nightly pre-release. Are you able to try this?
Hi @alex.tx,
It is difficult to describe the failure rate as it tends to work more often than not immediately after the firmware is written to the eMMC and then start to fail more and more over time until it never shows up at boot. I have attached two boot logs from when the splash screen appeared (splash_success_#.txt) and two where it did not appear (splash_fail_#.txt).
splash_fail_1.txt (52.5 KB)
splash_fail_2.txt (52.8 KB)
splash_success_1.txt (46.6 KB)
splash_success_2.txt (46.7 KB)
The only difference I see is that the “Finished Terminate Plymouth Boot Screen.” message is present in the failures but not the successful logs.
I was using 7.1.0 for a period of time but found that I was have issues with the Basler MIPI camera we are using which weren’t present on 7.0.0. This issue was described in the following thread:
I am not sure if the underlying issue we had with 7.1.0 has been fixed.
Thank you
Have you tested your camera with the 7.2.0 release?
Please check this thread for more details:Plymouth boot animation gets killed in few seconds
Hi @alex.tx,
I upgraded to BSP 7.2.0 and I have the same camera issue I had with BSP 7.1.0. Please see the log file below:
BSP_7_2_0.txt (57.1 KB)
The Plymouth splash screen failed to show on two out of six boot sequences with 7.2.0 so I should just continue with 7.0.0.
I examined the link you provided but, in our case, we are not modifying any of the systemd services for Plymouth. Should we attempt to modify them? Also, do we need to look into using an initramfs to start the splash screen earlier?
Thank you
Hi Aaron,
We are looking to verify some things internally here first and then get back to you.
Best regards,
Michael Park
Toradex