@agrajag Yes, that's the one.

@mitu
I have now managed to get the test script to read the following data.

mame-libretro lr-mame2016 /home/pi/RetroPie/roms/mame-libretro/galaga.zip /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-mame2016/mamearcade2016_libretro.so --config /opt/retropie/configs/mame-libretro/retroarch.cfg "/home/pi/RetroPie/roms/mame-libretro/galaga.zip"

Test script:

system=$1 emulator=$2 path=$3 commandline=$4 echo $system > /home/pi/test.txt echo $emulator >> /home/pi/test.txt echo $path >> /home/pi/test.txt echo $commandline >> /home/pi/test.txt

Where do I enter the option Y for the game and how do I read this option into my script?

E.g:
if type = Y then ./script1.sh
if type = X then ./script2.sh

Edit:
Now I have a solution.
My script:

############################################################### # 4 oder 8 Wege Joystick von runcommand-onstart.sh aufgerufen # # (C) 2021 treki # ############################################################### # Namen der 4-Wege Games in /home/pi/4way.games eintragen #system=$1 #emulator=$2 #path=$3 commandline=$4 echo $commandline > /home/pi/game.name.txt #Name des 4-Wege ROMs in diesem File, welches in 4way.games geschrieben werden muss var=$(echo $commandline | grep -o -f /home/pi/4way.games) if [ -z "$var" ] then echo "8-Wege Joystick" > /home/pi/test.txt else echo "4-Wege Joystick" > /home/pi/test.txt fi

In the file /home/pi/4way.games are the names (.zip) of 4-way games.
My 4way.games file looks like this:

asteroid1 astdelux bzonec pbobble2u dkong dkong3b dkongjrb fantsia2 galaga galaxian mspacman pacman pengo phoenixt popeyebl qbert qixb spacedx supertnk tankfrce atetrisa tetrisp tron4 uniwars

Entry in /opt/retropie/configs/all/runcommand-onstart.sh :

bash "/home/pi/4or8way.sh" "$@"

@hairdyeguy said in Speeding up boot time and the necessary commands:

Tried it along side to disabeling bluetooth and rainbow splash screen + inserting the quiet flag to kernel. Booting time is now 28 seconds!
Are there more things you'd recommend?

The EmulationStation settings I mentioned in my first post - they should speed up dramatically the front-end startup.

Other services that are not strictly needed - raspi-config(?), hciuart (which you don't need if you disabled Bluetooth), rpi-eeprom-update (the Pi zero doesn't have an EEPROM).
You can also disable the swap service (dphys-swapfile) and test, but the Pi 0 has limited memory and swap may be useful if you want to install from source or run other things.

I'm not sure why the dev-mmcblk0p2.device takes so long, maybe the sdcard is not so fast (?).

There may be other - more radical - options

Well, It turns out that my sound problem was probably due to the display refresh rate not being on sync.

After many reinstalls (both OS and Retropie) I was able to make sense of all this and I now can enjoy Retropie again on my old laptop with Lubuntu 20.04.

Thank you mitu for your time, this is really appreciated.

I've "solved" by keeping "pi" as login user and disabling password when doing sudo
thanks

On a PC (Ubuntu & forks, Debian, etc.), EmulationStation should be started from a desktop environment, not from a terminal.

@redpiperbob Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

Please provide more details of your set-up - which image you downloaded and so on.

hdmi_safe will set the resolution to 640x480, if your monitor supports a higher resolution, you can set it by using hdmi_group=2 and hdmi_mode set to one of the values detailed in https://www.raspberrypi.org/documentation/configuration/config-txt/video.md. You'll probably have to add hdmi_ignore_edid=0xa5000080, my guess is that your monitor supplies a wrong EDID and the Pi tries to set the video resolution to an unsupported value.

@mitu not until now, let's see if it works!

@lilbud basically it’ll just continue to boot then next part of the os without waiting for a WiFi signal and will connect when it’s ready in the background . Without it, It’ll wait either for an connection or just timeout and then continue to boot. No need to to have a solid WiFi connection on a retro pie setup. Where you would want it is if your project requires internet or WiFi to run your project so it has WiFi before the whole OS boots.

Just as I posted this I managed to figure it out. It seams that when kodi in osmc starts a script it starts it in root directory where it has no privilages. Adding "cd /home/osmc" at the beginning of "/home/osmc/RetroPie/scripts/retropie.sh" solved the problem!

Awesome. I will check out that link. Thank you.

Hi all! I just wanted to say that I got an answer to my issue! My particular problem was due to my using a VGA to HDMI converter to use with my old VGA monitor. What fixed my problem was to edit the config.txt file and uncomment the line "hdmi_force_unplug=1". Works perfectly now. Again, thank you all for your time.

@mitu Thanks, that fixed it!

Also, for anyone else who ends up here, it's important that you run raspi-config as sudo raspi-config from the pi user. If you're already root and you run it it won't know which user to configure for autologin.

someone asked about this on reddit a few weeks back, and i told them to add it to:
/opt/retropie/configs/all/autostart.sh

expressvpn connect &
emulationstation

it seemed to work for them. here's the thread for reference.

@mitu I made it! I have deleted whole scummvm folder, rebooted and the ES finallt works!

Thank you everyone. The problem is officially solved.

@ericdave you should not edit that file but the autostart.sh. the file you edited is not meant to be user editable and will be overwritten.

I solved it!

https://retropie.org.uk/forum/topic/4057/can-t-remove-text-in-bootscreen/14

Add "clear" as the first line in /opt/retropie/configs/all/autostart.sh. Never seen that tip anywhere other than that thread, but it worked!

@mitu I don’t have a usb keyboard I can use, I have been using VNC and my laptop to set up RetroPie.

Thanks both.

Have added a 5 second delay, and it works now.

Will look at adding a powered hub.