Boot Script ordering for USB Mount and SplashScreen

ZioDarkmage

Hello, I have looked and maybe I am missing it, but I was curious about changing the boot order on the USB Mount service and the splash screen display.

My current setup has my roms and splash screens on a USB stick utilizing the USB Rom service (easy method with USB having a folder retropie-mount) .
I can set my custom splash screen to a video and it works fine, but a static image it will not display. It always fails.

I was looking over the boot order and curious if it would be possible to move the USB mount to earlier in the stack than the Splash Screen or the Splash Screen to later (however one wishes to think of it). If this has already been covered, please point me in the proper direction.

I would prefer to not have to change where the splash screens are stored as I have seen some suggestions or hard mounting the usb drive with the fstab as I plan to change out USB sticks for games for me and games my son is allowed to play.

Capt_MorganCreek

I had the same problem with video splashscreens and it took about 10 reboots until the video showed up. Really curious to know what happens, but from the short status messages I figured the connected usb device was not yet ready and initialized.

hooperre

Sorry to res, but is this something that has been addressed? My splashcreens defaulted to my USB, however the USB isn't mounted until after the splash screen is called, IIRC. I tried posting this on reddit, but haven't got a response. Is there a solution to this?

jonnykesh

@hooperre Put your splash on your SD card. Seems like the most simple, obvious solution.

hooperre

@jonnykesh Simple, yes. Not the most practical as accessing the USB through windows is preferred to having to use Filezilla every time I want to add and remove splash screens.

jonnykesh

@hooperre You could delay launching ES until the USB is mounted. Add a sleep x variable to the launch script. Obviously this will delay the whole boot process.

hooperre

@jonnykesh said in Boot Script ordering for USB Mount and SplashScreen:

@hooperre You could delay launching ES until the USB is mounted. Add a sleep x variable to the launch script. Obviously this will delay the whole boot process.

Thanks! Is that boot/config.txt?

jonnykesh

@hooperre No, the autostart.sh script is in /opt/retropie/configs/all/
They changing the line to sleep 10; emulationstation #auto
You may need to adjust this value

hooperre

@jonnykesh Thank you for your help!

hooperre

@jonnykesh said in Boot Script ordering for USB Mount and SplashScreen:

@hooperre No, the autostart.sh script is in /opt/retropie/configs/all/
They changing the line to sleep 10; emulationstation #auto
You may need to adjust this value

This does in fact delay the launch the ES2 launch, but does not change splashscreen and usb mount orders, sadly.

jonnykesh

@hooperre Well, It won't change the mount order of the USB. This is determined by the kernel, I believe and whenever the daemon runs.
If you are calling the the splash from a USB then, you of course need to wait until the USB is mounted, otherwise it won't be called.
Have you tried increasing the sleep value? I'm not sure how far into the boot process the USB mount happens but it is one of the last processes to happen as everything else needs to be in place before it occurs.

hooperre

@jonnykesh said in Boot Script ordering for USB Mount and SplashScreen:

@hooperre Well, It won't change the mount order of the USB. This is determined by the kernel, I believe and whenever the daemon runs.
If you are calling the the splash from a USB then, you of course need to wait until the USB is mounted, otherwise it won't be called.
Have you tried increasing the sleep value? I'm not sure how far into the boot process the USB mount happens but it is one of the last processes to happen as everything else needs to be in place before it occurs.

I follow. The problem, I think, is that the splashscreen launches independent of when ES2 launches. So I'll see my boot script, I'll get the error saying the splashscreen isn't found, and then it waits an inordinate amount of time and then starts up ES2. In summation, I don't think ES2 launching has any bearing on the splashscreen process.

Thanks for sticking with me thus far. I've put it off because I know a simpler solution exists... but this is why I ~~love~~ am addicted to my Pi haha.

jonnykesh

@hooperre Have you considered turning the custom splash screen into a static video file? say 5 or ten seconds, whatever you feel is best.
You say videos on the USB work fine so just turn the static image into a video file.

hooperre

@jonnykesh said in Boot Script ordering for USB Mount and SplashScreen:

@hooperre Have you considered turning the custom splash screen into a static video file? say 5 or ten seconds, whatever you feel is best.
You say videos on the USB work fine so just turn the static image into a video file.

Truth. Good shout. I'll probably just put them on the SD card unless I can dig into the splashscreen stuff and find out how to have it start later? Not sure. I know using Filezilla if I attempt to change permissions it doesn't work and I can't add them, but I know I can do it with Putty (chmod) it works. That's the only reason I preferred to stay on the USB.