I got it all working and wrote up notes on what I had to do in this post.

@rtarroyo said in Remove Initial Boot Screen:

using the terminal remotely is lightyears better, I feel stupid for not knowing that was an option.

Then please spread the word, as many people (especially Windows users) think about the terminal as backward and cumbersome, while in fact it's very powerful and no rocket science with a little willingness to learn.

I compare it sometimes to a Swiss Army knife next to the everyday knife and fork (the graphical desktop), or a look under a car's hood in addition to its dashboard. 😉

Besides remote administration, it's perfect for doing the same thing over and over, e.g. processing a big number of files (example, example).

To become even more efficient with the terminal, I can highly recommend to check out its keyboard shortcuts, especially those for Tab Completion and the Command History.

End of the noncommercial break. 🤓

Just for the record, this command removes write permissions from the file:

sudo chmod -w /boot/config.txt

Restore them only for the owner (the default) with u+w instead of -w.

But note that any script that runs with admin rights can change the file nonetheless.

edit: Ah, I noticed the logical flaw in this. The file is owned by the admin user root and it is already only editable by the owner. So removing w wouldn't make any difference in this case. 😇

What's the content of the file you deleted (es_input.cfg) ?

@bilu just to say thanks. To date, I've been underwhelmed by the PI4 performance since I swapped from my pi3.

I've been struggling with all kinds of screen tearing issues, despite overclocking to 2.1ghz.

I borrowed this configuration and everything is now running buttery smooth.

Thanks for sharing.

Sorry to resurrect this interesting topic so much later. I came to it after looking for a script that allows us to select in a menu at the start if we want to start emulationstation or the desktop. I know that it's not exactly the same as what was discussed in this thread but it's very related. I've ended up making a custom script modifying /opt/retropie/configs/all/autostart.sh, and since I think it might be useful to someone, I'll leave it here for reference (this is the new content of that autostart.sh file):

## Get WT Sizes WT_HEIGHT=18 WT_WIDTH=$(tput cols) if [ -z "$WT_WIDTH" ] || [ "$WT_WIDTH" -lt 60 ]; then WT_WIDTH=80 fi if [ "$WT_WIDTH" -gt 178 ]; then WT_WIDTH=120 fi WT_MENU_HEIGHT=$(($WT_HEIGHT-7)) ## Get Architecture ARCH=$(dpkg --print-architecture) ## Dialog Menu if [ "$ARCH" = "armhf" ] || [ "$ARCH" = "arm64" ] ; then sw=`DIALOG_ERROR=5 DIALOG_ESC=1 dialog --timeout 6 --no-cancel --title "Raspberry Pi Startup Selection Tool" --backtitle "$(cat /proc/device-tree/model)" \ --menu "Startup Options" $WT_HEIGHT $WT_WIDTH $WT_MENU_HEIGHT \ "1 EmulationStation" "Front-end of RetroPie Project" \ "2 Desktop" "Raspbian PIXEL Desktop Enviroment" \ "3 Console" "Abort auto-start and remain in console" \ 3>&1 1>&2 2>&3` else sw=`DIALOG_ERROR=5 DIALOG_ESC=1 dialog --timeout 6 --no-cancel --title "Raspberry Pi Startup Selection Tool" \ --menu "Startup Options" $WT_HEIGHT $WT_WIDTH $WT_MENU_HEIGHT \ "1 EmulationStation" "Front-end of RetroPie Project" \ "2 Desktop" "Raspbian PIXEL Desktop Enviroment" \ "3 Console" "Abort auto-start and remain in console" \ 3>&1 1>&2 2>&3` fi rc=$? #reset #no needed clear source $HOME/.bashrc case $rc in 0) case "$sw" in "1 EmulationStation") emulationstation ;; "2 Desktop") startx ;; "3 Console") echo "" ;; *) emulationstation ;; esac;; 1) emulationstation ;; 5) emulationstation ;; *) emulationstation ;; esac

This is what it looks like:

autostart_retropie_screenshot

It's set to run emulationstation by default. A timeout of 6 seconds is established, so if the user does not press any key for 6 seconds, the default option (emulationstation) is executed. I've used dialog for the menu instead of whiptailonly because this last doesn't have the --timeout option, and although you can achieve a similar effect with other tricks it's a bit more complicated, both should work fine either way.

If you're using berryboot, that has its own config.txt

Berryboot isn't supported btw, and we don't provide berryboot images for the rpi4. I wasn't sure if you meant above you installed the standard image to test after.

Great, thank you very much @BuZz !!

@ahndrooan You can edit the topic title - there's no 'solved' checkbox :).

I was actually wrong it started up again but when i connected a power supply to my hdmi av connector it stopped and has been good since i think it is a power issue and using overscan must draw less power so thats why it seemed better

@Clyde said in External Boot in my image:

@MPlay Thank you for sharing your solution.

you are welcome, my next step is set retropie to stream my game play (if possible in net play mode) in my youtube channel.

thank you and other friends for support.

@microb41 According to the Raspberrypi website, there is a pixel clock limit, ie effectively a limit to the number of pixels that can be controlled, of 1920x1200@60 Hz, so as your resolution exceeds that, it shouldn't work

You can set higher resolutions, in config.txt, but they won't work.

https://www.raspberrypi.org/documentation/configuration/config-txt/video.md

Further down on the same page, it shows you how to create a custom screen resolution, so it would be worth you looking at that to get the aspect ratio you want.

@fuzzybat23 berryboot works differently. You can mount the partition with the globally shared config.txt though - https://raspberrypi.stackexchange.com/questions/6972/location-of-berryboots-config-txt

@mitu

I've also solved the screen saver problem and added a script to trigger and Enter Key press, 8 seconds triggers this about 2 seconds after loading..

I've created a script to emulate the key press.. updated the post below:

https://retropie.org.uk/forum/post/129603

After doing what @Brigane suggested, I believe you can uninstall Attract Mode from the RetroPie-Setup.

Thanks very much

@Krisu not a good first response to get help here.

How about:

Because I asked you to. It may not be the same issue - cause may be different. Lots has changed in 2 years. The forum wouldn't work if everyone used one topic per type of issue.

Yes, give it a go from a version with the standard build and add AM from experimental. I'm sure Buzz integrated it better than I would have done, plus I could do the same to help debug if it still doesnt work.

@jukeltruck
Glad you where able to figure this one out. I double checked my system and I already had libvlc5 installed. For others reading this, this is what you type in to install it:
sudo apt-get install libvlc5