I'm having some splash screen issues. If console=tty3 it can't start the video..

reikku

Hey guys, and thanks for the awesome community support, this is the only topic i haven't found the answer To.

So i Have RPi 3b and retropie 3.7 installed 3.6 from sd image and upgraded To 3.7 via source.

I am trying To get my pie to install without any boot text and have succeeded_almost_

I have added the console=tty3, logo.nologo loglevel=3 and quiet To the /boot/cmdline.txt and still it shows all text after [failed]usb@sdaservice.service.

And after the splashvideo it shows like 20 lines of boot text.

In my own mind i Have concluded that the text after the [failed] have to be related To the loglevel=3 because it only shows after the fail, and the Console=tty3 hides the whole pack.
Few questions:

The usb/sda fail is pretty normal for many RPi, any ideas how its fixed and what it means?

How i cover the -after splash video- text

And lastly, i really want To clean the start, but is it healthy?

Sorry for the low level info but i am posting this from a phone and do not now how to save and import the logs. I am a NEWBIE!

reikku

@reikku and also i am having some issues with the assigning of the controllers. Something with the New update makes the ps3 controller To be as the #2 controller.

Any ideas, how to change it? Some controller hierarchy?

Edit: I have a Microsoft all in one media bluetooth keyboard with a dongle.

senkun

@reikku said;

In my own mind i Have concluded that the text after the [failed] have to be related To the loglevel=3 because it only shows after the fail,

yes, you have concluded rightly as all kernel messages with a loglevel smaller than the console loglevel will be printed to the console. It's still pretty verbose at loglevel 3 so your failed service will be printed. If you have ascertained that your system boots up fine and you can ignore the messages, you can increase loglevel to 2 or 1.

reikku

@senkun okay, firstly i upgraded from binary and then i set it on loglevel=2 and now it changed pretty much everything. XD

Now the splashvideo either load se or not and the emulationstation cuts mid-video, and the emulationstations own splash does not even show.

AND the usb.sdaservice fail still shows. What the frick i should do. Second whole day of tinkering with it. :D

EDIT: The network connection seems To affect it somehow?! If the network is reached, the splashvideo shows about half way through, and cuts into emulationstation, if not, it just boots regularly into emulationstation with the own splash and everything.

I_am_baffled.

senkun

@reikku

usb.sdaservice fail

perhaps related to the problem;
https://retropie.org.uk/forum/topic/297/failed-failed-to-start-usbmount-dev-sda-service

Now the splashvideo either load se or not and the emulationstation cuts mid-video, and the emulationstations own splash does not even show.

EDIT: The network connection seems To affect it somehow?! If the network is reached, the splashvideo shows about half way through, and cuts into emulationstation, if not, it just boots regularly into emulationstation with the own splash and everything.

that would happen if during boot something stalls the sequence, so it would seem it's def network related. Are you using wifi? If you check log or check the boot messages there might be something about waiting for dhcpd.

one possible fix may be to add a delay before calling omxplayer to play your splash video;

sudo nano /etc/init.d/asplashscreen

add sleep 5 in a new line just before the line where ‘omxplayer’ is called.

reikku

@senkun

Yes, i am using wifi. And it seems so, that if it finds the network at First try, everything is fine exept the emulationstation cutting the video.

And i Have allready disabled the USB ROM service, and it only got rid one of the initial two identical fail errors.

And i Will try that delay sequence. Is the value in seconds?