Howdy all, my name ain't betsy it's actually my truck and the reason I am here. I have purchased a raspberry pi 5 8G and with the help of a friend who has been in linux since we were both kids, I have got it setup on dietpi, or debian 13 trixie lite version. We are setting it up to run a tuner with a Moates QH and also the diyaudiohead unit mod, but for now I'm just on the tuner and I have a personal want for this. He took the time with me last night setting this up with wine, pi-apps, getting wine and the tuner to load automatically upon startup, and setting up plymouth to change the boot splash screen to my truck and have it set up to show that splash screen longer than just the one frame it was doing. I would like to have that splash screen up for the duration of the boot so the boot text doesn't show and preferably not go away until all the auto start software is done booting, but this itself isn't necessary. I am VERY new to linux, last time I touched it, I was 12 and he had put manjaro on a dell optiplex my parents gave me, so do forgive me if I'm lacking information that would make it easier for y'all to assist or if this has been done already I was unable to find it for my situation. As such what I do know is I'm essentially in a lite trixie, no GRUB, just startx and plymouth, with Pi-apps and openbox as well as the browser which I'm using at this moment to make this thread. Any help at the very least finding a starting point for research would be greatly appreciated
New on Linux, Raspberry pi questions
@BetsyF150 welcome to linux.org 
I am moving this to our Single Board Computers subforum, where our Pi people may be able to assist.
Good luck.
Chris Turner
wizardfromoz
I am moving this to our Single Board Computers subforum, where our Pi people may be able to assist.
Good luck.
Chris Turner
wizardfromoz
Thank ya and sorry for the misplacement@BetsyF150 welcome to linux.org
I am moving this to our Single Board Computers subforum, where our Pi people may be able to assist.
Good luck.
Chris Turner
wizardfromoz
I'm not familiar with SBCs, like Pi, but I suspect you want to research 'quiet splash'. That's a boot configuration option that should keep the splash screen up instead of showing the text behind the boot process.
I had seen that in another post elsewhere but they had GRUB on their system as they were using PiOS and not lite, any idea where I’d be adding that in the distro without it?
Hey sorry for the first reply turns out I have that enabled on Plymouth already from my friend helping me, didn’t even know
You've already got it set to quiet splash, and it's still showing you the text during the boot process?
Correct, from how he has explained it, it is either xorg and auto login starting or the pi restarting graphics drivers and pulling that up, it all shoots by so fast I’m not sure I could get a decent pic of video of it, he did say he believes plymouths end service waits on the login so we could change it to wait for other applications and extend the runtime, or possibly set up an application to run after the head unit and tunerpro open up. But this is over message and I’d prefer not to bug him too much due to personal family health things in his life at this moment
As that is the case, I'm not sure how to move forward from here. It could be that there are conflicting commands in the configuration, and it might even be some kernel logging settings.
Hopefully, someone will have an idea.
Hopefully, once something is found I can either reply to this directly or with a link to a thread that is just a complete solution, whichever is easier for the forum and anyone who may be looking to do something similar in the future
Welcome to the forums
This is Not my particular area, but after some searching, problems with the Plymouth splash screen are not too uncommon, some of the suggestions found on various sites are,
first check logs/debugging files for errors if nothing is pointing you to errors then check the DRM Modesetting Drivers to ensure your system is using the right drivers, Check initramfs to make sure its configured and set up correctly, if you're using your own image for the splash screen then make sure it is compatible and properly configured. and check kernel boot parameters. Parameters like quiet and splash should be set so Plymouth starts early and overprints the boot messages.
This is Not my particular area, but after some searching, problems with the Plymouth splash screen are not too uncommon, some of the suggestions found on various sites are,
first check logs/debugging files for errors if nothing is pointing you to errors then check the DRM Modesetting Drivers to ensure your system is using the right drivers, Check initramfs to make sure its configured and set up correctly, if you're using your own image for the splash screen then make sure it is compatible and properly configured. and check kernel boot parameters. Parameters like quiet and splash should be set so Plymouth starts early and overprints the boot messages.
I’ll give these a goals and see what happens
What I believe is happening is that the kernel is showing you (through the console) the logs of what is going on.
It's possible to change the logging level, that is the level of events (by severity). You can tell the kernel not to log (and thus not send it to the console) events that are greater than level 2. (Level 2 is actually level 3, because it starts counting from zero.)
The following isn't about direct links. The goal is to share the 'AI' blurb at the top of the search page.
See this to learn about setting it in GRUB:
What I'd do is change it from GRUB to see if it works. If it works, you can permanently modify the settings.
But, first read this:
That will explain the logging levels. If you tell the kernel to only log at a certain level, it should only output events that are at that level. You'll want to see important events in the event of a system failure. So, that's why I said level 2 above. If you set it to level 2, it will only show you the logs for 0, 1, and 2.
However...
I can't think of a time when I've actually done this. That means I have no experience with this. It looks easy enough. I'm not even 100% sure that it will solve your problem.
It's possible to change the logging level, that is the level of events (by severity). You can tell the kernel not to log (and thus not send it to the console) events that are greater than level 2. (Level 2 is actually level 3, because it starts counting from zero.)
The following isn't about direct links. The goal is to share the 'AI' blurb at the top of the search page.
See this to learn about setting it in GRUB:
What I'd do is change it from GRUB to see if it works. If it works, you can permanently modify the settings.
But, first read this:
That will explain the logging levels. If you tell the kernel to only log at a certain level, it should only output events that are at that level. You'll want to see important events in the event of a system failure. So, that's why I said level 2 above. If you set it to level 2, it will only show you the logs for 0, 1, and 2.
However...
I can't think of a time when I've actually done this. That means I have no experience with this. It looks easy enough. I'm not even 100% sure that it will solve your problem.
Similar threads
