@steptoe said in Booting from SD Card with SSD Storage vs full SSD Install:

You DO have to leave the SD card in though, as it reads the boot sequence from the SD card before passing all control to the external SSD or hard drive

No, that's not required on the Pi4.

I've just tried with google kickstarts and it work !

Yes, you can create your own launchers if you wish and maybe a new system that would be used to launch the apps.
If you know the command that starts the app from the CLI, then just add it in a shell script .sh file and create a system that would launch .sh files directly.

@orbian No problem. Glad it worked. Keep them all in that folder, you'll find its a lot easier that way

@mitu

I can confirm the problem is still present in Retropie 4.8, is caused by the PS3 joystick driver and with Pi 3 only, the Pi 4 version, doesnt happen this. Thanks

@guestdreemurr how are you trying to install? RetroPie has to be installed within a preinstalled supported Linux OS (Debian/Ubuntu/Linux mint etc).

See the instructions in the docs https://retropie.org.uk/docs/Debian/

Just me thinking that, works great now! Thanks!

Now the only thing not working is sound on the VIC-20, weird sound is working on the C64 side of things.

@mitu

Ok, so had a bit of time to tinker, and I can confirm that Joycons are working perfectly in 4.7.19. Seems it's a bug in 4.8.

Now - any tips on getting them to sync at startup - I find I have to be very precise to the moment I turn them on during boot up, otherwise they don't pair!

@RobbyThomas2525 Please don't open several topics for the same issue. I've merged your topics.
Please provide all the info asked in https://retropie.org.uk/forum/topic/3/read-this-first, this will help diagnosing the issue you're having.

@sleve_mcdichael Thanks

@mitu Discovered my problem. There were actually two theme.xml files that needed editing, the first in the root of the designated theme and a second copy in the retropie subfolder.

Sure enough, modifying both theme.xml files got the font working!

I am a newbie and don't know anything about programming. But I tried to install new Retropie 4.8 on a Armbian Bullseye and I think I could compile almost everything.
I made a Image from the tinker board retropie for anyone who wants to test it or wants to make it better.
I uploaded the image file to my nextcloud. If anyone interested, here is the link:

https://waltikon.mooo.com/index.php/s/3Le33bX2YCZFKFC

I compiled everything, which was to be compiled there. It seems like everything works fine but I can't give any kind of support. If you want to test this image, be my guest. :-)

I am a newbie and don't know anything about programming. But I tried to install new Retropie 4.8 on a Armbian Bullseye and I think I could compile almost everything.
I made a Image from the tinker board retropie for anyone who wants to test it or wants to make it better.
I uploaded the image file to my nextcloud. If anyone interested, here is the link:

https://waltikon.mooo.com/index.php/s/3Le33bX2YCZFKFC

I compiled everything, which was to be compiled there. It seems like everything works fine but I can't give any kind of support. If you want to test this image, be my guest. :-)

@mitu said in Request for RetroPie build instructions for Odroid C4:

@retropi19 said in Request for RetroPie build instructions for Odroid C4:

Sorry whats PR

PR means Pull Request, the most common way for an external developer to send patches/modifications to a Git-hosted project (such as RetroPie).

Unfortunately i don't know from this things.someone else has to send it.

I've taken a look at this, it's a SDL2/Mesa issue (see here) which gets triggered with the KMSDRM video driver.

TL;DR - using SDL_Quit in an atexit handler will lead to a segfault in this particular scenario. Various other programs have implemented alternative ways to cleanup SDL's state without triggering this bug (see here, here or the patch sent by @psyke83 for gzdoom here).

We'll see if the upstream projects wants to prevent this crash, which otherwise is harmless.

See if the adapter has any firmware upgrades that fixes that. You never know.