You can run xboxdrv only for the psp system, if that works for you. I think the Xboxdrv doc page has some examples on how to run it only on specific systems, by using the Runcommand's onstart/onend scripts.

@truglodite said in How can I boot RetroPie from NVMe or SSD (without SD)?:

I am guessing retropie still will write heavily to the sd card despite roms being on an external, correct? Not sure if sd wear is a big deal with retropie, so figured I'd ask if it was and if there's a similar way to mitigate.

Not really, gaming is not a write-heavy process. Game saves and save states are written to the ROM's folder by default and unpacking .zip ROMs is usually done in RAM.
There is no constant write load using RetroPie, like a monitoring/data collection/aggregation process entails, so a good sdcard and proper power source is usually enough.

@markyh444 Thanks will try it later on

Better option is to bring up the retroarch menu (select + top button) then go to "Quick Menu > Options" and set "Invert Y Axis" to "Enabled".

Thanks @muldjord The "xenon+2" bit works because "/opt/retropie/supplementary/skyscraper/Skyscraper -p amiga -s screenscraper --query romnom=xenon+2 Xenon2_v1.7_CDTV.lha" scrapes no problem. I have the scraped image now from that file/scrape. My plan is to get Skyscraper use a local image now I have it.

I tried sha1 and crc, neither of them work. For some reason it just doesn't like my .cue/.iso copy of Xenon 2 CDTV.

Scraping for Amiga can be a bit tricky especially if, like me, you're determined to use specific roms rather than common ones.

I've sorted it. I ran an update and menu appeared that wasn't there before, I went into change console fonts and selected large. And it's clear and readable.

@AdamBeGood as far as he is not able to give some Information about his setup as mitu requested he might also not be able to configure a keyboard.
I guess he wants a plug and play system and uses a prebuilt image without carying about how things are working.
I recommend to buy a Nintendo or Playstation.

I have a similar issue but reversed. If I set the volume anywhere between 0 and 60% in the ES Sound menu, there is no audio when the video snaps are playing. If I set the volume anywhere between 60 and 100%, the volume grows proportionally when the video snaps are playing. However, the correct volume is used while games are playing.

Therefore, if I set the volume high enough to hear the video snaps, my in-game volume is often too high.

All of this started when I began to troubleshoot why some video snaps where causing ES to crash. Using the HW Accelerated OMX player fixed the issue and changing a few other ES Sound menu options finally made the Sound adjustment work. I believe the key fix was changing "PCM" to "Speaker" so that it would match what is shown under the volume control when running 'alsamixer' via SSH. After they matched, the volume setting worked and was retained instead of reverting back to 0.

Any idea why I have a mismatch between video snap volume and in-game volume?

Video Snap >>> 60 to 100% = 0 to 100%
In Game >>> 0 to 100% = 0 to 100%

OK I got it fixed, it was copying the games to the SD card and not running them.

Some psx games are not compatible with Dualshock controller . You have to change the controller, from quick menu, to standard.

nevermind...after running the tests, and rebooting the Raspberry, the joystick was detected.

@andrewsi starting it from gdb inside a ssh session could work to have text mode, unless you tried that. But could be it wont break on correct location either then. Not used gdb that much for such problems

@mitu said in Corrupt after every reboot:

What resolution is your display and how is it connected ? Have you tried forcing a specific resolution through raspi-config ?

Ok, thank you for pointing me in the right direction, I forced the resolution, which fixed that on start up, then it got me thinking., that was only for the system level, so I started poking around the retropie configs, and set the audio to HDMI, and changed the audio driver to SD12 and everything seems to be working now

After a fair bit of trial and error, just wondering if anyone has any further pointers - could a fullscreen window (rather than just fullscreen) potentially work for this? I'm envisaging the full screen being the size of the widescreen, with the window being 4:3 - potentially the emulator would still register the hit outside of the displayed screen. I'm struggling with the Retroarch GUI options for this though.

@mitu said in RetroPie Setup no Longer Working After Failed Update.:

The error message is quite clear - have you tried running the commands recommended ?

I honestly didn't even notice that until after you pointed it out lmao. Thank you, it worked!

@windg I don't think so. At least I didn't do anything more with my ext4 usb ssd. Here's the relevant part of my fstab:

PARTUUID=2c31bca2-b1f4-4466-ab20-3a347852ba2c /media/usb0 ext4 defaults,noatime 0 1 /media/usb0/roms /home/pi/RetroPie/roms none bind,bg 0 0

Some notes:

I generally prefer UUIDs over device names (e.g. /dev/sda1) in the case that the latter is changed by the system someday for reasons™ (or perfidy 😛 ). I'm using two mounts, because my drive has a roms directory that I mount in ~/RetroPie/roms (with the option bind that mounts directories in directories) after mounting the drive itself in /media/usb0. I did that to be able to have other directories on the drive as well, since its 250 GB exeed the size of my rom collection by far. The option bg should tell the system to retry the second mount in the background, in case the first mount isn't completed yet. But I'm not sure this option is still viable in the current version of mount/fstab.

Ah, so that was it, thanks! I tried to update it without removing the older version first.

@BuZz thank you!!! really appreciate the help.