using the “Approach 2: Applying a Splash Screen to a Custom Image: Using Standalone Command”
its change the splash screen on startup, but the shutdown splash screen remains the torizon logo
i’m using TorizonCore OS version 6.8.0-build.22 Distro variant:“Docker” on Verdin iMX8M Mini WB on Verdin Development Board(CUSTOM)
Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Hello,
Thank you for reaching out with your question about customizing the splash screen on your Verdin iMX8M Mini with TorizonCore OS. It sounds like you’ve successfully changed the startup splash screen, but the shutdown screen still shows the default Torizon logo. This is likely because the initramfs used during shutdown hasn’t been updated with your custom image.
To resolve this, you’ll need to ensure that the initramfs for both the boot and shutdown processes includes your custom splash screen. Here’s how you can do that:
Check Current OSTree Reference: Run ostree admin status to verify your current OSTree reference.
Create a New OSTree Commit: Use the ostree-customize-plymouth.sh script to create a new OSTree commit. Make sure your custom splash screen image is included in the initramfs.
Deploy the New OSTree Commit: Apply this new commit to your device to update the initramfs for both boot and shutdown.
Reboot and Verify: Restart your device and check if the shutdown splash screen now displays your custom image.
By following these steps, you should be able to achieve the desired splash screen customization for both startup and shutdown.
If you have any more questions or need further assistance, feel free to ask.
Best regards,
Toradex AI Assistant.
Please, also check if these links can help you solve your problem:
I just did a quick test and was unable to reproduce this. My custom splash screen appears when the system starts up and it appears when I run either reboot or shutdown.
The issue you are describing use to be an issue, but it was addressed over 3 years ago. Unless you are using a very old version of TorizonCore Builder for some reason.
thank!! You hit the nail on the head!!
I have installed the version 3 but in the reference script i edited it used the version 2
alias torizoncore-builder=‘docker run --rm -it -v /deploy -v $(pwd):/workdir -v storage:/storage --net=host -v /var/run/docker.sock:/var/run/docker.sock torizon/torizoncore-builder:2’ ← changed the 2 for 3 do the trick