@bberlin1 This kind of functionality would be provided by the emulator (RetroArch with lr-pcsx-rearmed or lr-duckstation), but it's not present at the moment.

@tsukisuperior can use

sudo CC="whatever" ./retropie_setup.sh

This may not work for all modules as some module code may override it.

distcc can be used automatically by setting DISTCC_HOSTS="192.168.0.1/4,lzo" etc in the same way. It will get added to start of system PATH and added to MAKEFLAGS also.

You can write the RetroPie image directly to the drive and boot from it - assuming your PI has USB boot enabled. If USB boot is not enabled, then you'll need a sdcard to run Raspberry Pi OS and enable it from raspi-config.

We don't support 3rd party images, especially the ones loaded with ROMs and sold - RetroPie's image license is specifically non-commercial.
Ask the seller for support.

I usually do just press Ctrl+r to search the command line history, enter "setup" to get the last setup command, and press Enter to run it. But mitu's solution is much more elegant (and persistent, depending on the maximum length of your command history). 👍

By the way, one thing that you might find useful is to start the setup inside a screen session, so you can logout while setup keeps doing things like updating or scraping:

screen -dmS setup sudo ~/RetroPie-Setup/retropie_setup.sh && screen -r setup

or with mitu's alias:

screen -dmS setup rpie && screen -r setup

The && screen -r setup at the end enters the screen session immediately after its successful launch. You'll notice no difference to running setup without screen, but you can detach from it without killing setup by pressing Ctrl+aand then d (for "detach") alone. You can reattach to a running screen session by entering screen -r in the command line, optionally followed by the name of the session (e.g. screen -r setup) in the case of multiple running screen sessions.

After detaching from screen, you'll be back in the command line and you can logout normally without killing any running detached screen session. Then, you could even relogin to RetroPie from another machine and reattach yourself to your screen session from there.

Sorry for the slightly off-topic lecture, your question triggered my "sharing is caring" mode. 😇

Got it. I found the issue.

Using that CRT/HDMI video mode switcher added a two line statement to my \boot\config.txt that wasn't there before.

framebuffer_height=1920
framebuffer_width=1080

Not sure why it added this, but as soon as I commented and rebooted, my RetroPie core was back to normal size and not shrunken anymore.

I don't have many statements active in my config.txt so I noticed an extra "list" of other video related stuff at the very bottom. It seemed to have duplicated some of the entries that are in sections above and placed them in the last [all] section of the file. I commented it all out so none of it is active.

framebuffer_height=1920
framebuffer_width=1080
disable_overscan=0
hdmi_force_hotplug=1
enable_tvout=0
hdmi_group=2
hdmi_mode=82

Are you sure you downloaded the right image for your system ? The 'illegal instruction' error at the top makes me think you downloaded the image for a Rpi2/3 or Rpi4 board.

Thanks @BuZz! I had forgotten about the addSystem option. I'll have to test that out. Thanks for considering platforms.cfg too.

- George

@slippy Which port exactly ?

@tango said in SDCard Unreliable - Move all RP to USB card? Or fix SD?:

Or does it do that because I have no boot sector or boot programs on my USB stick?

If you haven't programmed the OTP bit for USB boot, the Pi will always boot from sdcard.

It works by having only the right pad for the console plugged in at a time. I'll stick to that since my daughter has a USB hub with a switch for each port on her Pi. So I can have all pads plugged in at once but only use the one I want thanks to the power button on the hub.

I've set up four kinds of pads: a NES pad, 3 SNES pads, a N64 pad and a Megadrive pad. Thanks to your setup (with retroarch.cfg files) I don't have to map the pad buttons anymore: I can just power them on and off with the button on my hub and enjoy any console that I like.

Thank you so much for my daughter & cheers from France! :-)

The hotkey is defined in the RetroPie controller config. You can then customize the hotkeys in RetroArch.

Or I believe you can set up "shift key" behavior in the I-PAC config to do the same thing.

If you still want separate buttons that's fine, was just a personal preference to have my controls be minimal.

I haven't installed any leaf buttons/sticks myself, I guess you can check the other forums here or google around for more info.

@filipinoy79 The installer checks if the Google's DNS IPs are routable from the Pi (8.8.8.8 for instance) and if that fails, it considers there is no internet available.
You can check with the command

ip -4 route get 8.8.8.8

What's the output of the above command in your case ?

Thank you for clarifying @BuZz

Answered my own question. So my workstation has 3 monitors and a TV, the pi had this issue with the TV and one of them monitors. Works absolutely fine on the other 2 monitors though, and the TV in my living room where this was going to go anyways works fine with it as well.

Anyone know why this issue is occurring?

OK will have a look, didn't even think of looking there, many thanks. I will crack on.

By accident I found out that a Chrome OS computer is actually better than Windows 10 for setting up a Pi because it can read Linux filesystems, meaning I have access to both the boot and rootfs partitions. I also found a few remarkable Android apps for SSH and VNC. I did, however, need a Windows device for setup...