There's no resolution related setting in EmulationStation - are you sure you haven't set-up the resolution in your desktop ?
Please post the EmulationStation log taken after starting EmulationStation with

emulationstation --debug

@abj ok

If you're using the standalone emulator and not the libretro core, then it's normal. The hotkey enable button/shortcuts are generally available only for libretro cores (emulators names lr-<something>).

No, use a PS1 emulator.

Yes, it's a typo on the documentation page - thanks for the heads up. I fixed it, the change should be published soon.

@ExarKunIv It did not work for my Xbox S wireless controller, but it did work for my Dualsense. Once that was connected, all I had to do was start the binding process by pressing enter on the keyboard while selecting the first binding and then going down the binds with my Dualsense. Thanks!

@mitu I have. On the Pi, when I plug into the second HDMI port I don't get any display at all. And I've tried all three HDMI ports on the back of the TV as well.

ok, it's got to be the Pi. I just found a backup from 3 years ago. Did the same thing. Audio played fine for the first few clicks, then went out. I'm going to contact them to see if they concur, but since everything software-wise seems correct, that's got to be it.

Check if the mapping corresponds with the one described in the docs - see the previous link I posted. If you wish to change the mapping, then you can do so by using the core input remaping menus in RetroArch.
You can also try using the standalone emulator to check whether the default mapping for it is better suited for your needs.

If it has a dongle, then it's not a Bluetooth contrller. If it's not working with a PC, then the dongle/controller may be fake or defective. Complain to the vendor and ask for a replacement/RMA.

There's a core option to force the menu on.

@mitu thanks, I'll try it!

@thewillrussell Then the samples you are using are wrong.
As for romsets, make sure the samples you are using are meant for the arcade emulator you are using.

@mitu thankfully I just figured out how to do that and had putty set up so I’m back to ES.
I’ve also learned that the Pi is still running after Kodi crashes. It just sends my tv to no signal so I thought it shut off.

Hey @mitu.

Just what I was after. jstest is exactly what I wanted. As yet I haven't done anything with evtest or sdl2-jstest, but I've taken notes and they are now in the tool box for continued retro-pie adventures.

Again. Thanks very much for your help.

Rob

@DaveWins182 said in Retropie Drive Partition Issue with Kodi:

Any idea how I could remedy this? Thanks in advance!

Don't use /dev/sdX[Number] in your /etc/fstab, add the mount point based on the partition's UUID(s) (see https://wiki.archlinux.org/title/Fstab#File_system_UUIDs). This way the order of the USB devices is not relevant and the mount points will be always correct.

Please use English as this is an Enlish speaking forum. When asking for support, please add the info requested in https://retropie.org.uk/forum/topic/3/read-this-first, as much as you can.