Based on this output, I think you'd need to set in EmulationStation the Audio Card to Device.

To get the name of the mixer (volume control), run

amixer scontrols -c Device

and choose the 1st entry and set it as Audio Device. For instance, in my case, the USB audio card is named 'Controller':

amixer scontrols -c Controller Simple mixer control 'PCM',0 Simple mixer control 'Headset',0

I would use PCM as the AudioDevice settings in ~/.emulationstation/es_settings.cfg:

<string name="AudioCard" value="Controller" /> <string name="AudioDevice" value="PCM" />

This should fix the audio not working (or the volume slider rather) in EmulationStation.

For Amiberry, I'm not sure why it's not working - maybe it's trying to use the 'default' card and it's not working ?

Try following the advice here and create a /home/pi/.asoundrc file containing

defaults.pcm.!card 1 defaults.ctl.!card 1

@cook1e_mr
Different seller, but it was these: Ebay

@kyussgaming
https://retropie.org.uk/docs/Transferring-Roms/
here is the methods of getting roms to the pis sd card
or probably the best way is to use an external USB drive and its just plug and play using this method
https://retropie.org.uk/docs/Running-ROMs-from-a-USB-drive/

@mitu said in Pi4 - How can safe remove USB Pendrive ??:

You can exit EmulationStation and then, from the command line, run

sudo umount /media/usb0

If your USB drive is mounted on another folder than /media/usb0, substitute /media/usb0 with the proper folder name.

It's apparently the best solution... what i have do:
F4 to exit from ES.
mount (to found corrent usb)
used sudo umount
copyed all my news roms from pc and now also the image snap and some gamelist.xml from my personal system
type exit from console to restart es and....

all now works whitout any issue.

Thanks for all.

@baconbandage Run the following command - with the gamepad plugged in - and post the output

cat /proc/bus/input/devices

Try testing the gamepad with the jstest utility. Exit EmulationStation and run

jstest /dev/input/js0

You should get a listing with the gamepad's input types (buttons/joysticks/etc.) and you can press the buttons/D-Pad/move joysticks to see if they are registering. You can exit the test by pressing Ctrl+C.

@crush ... Ok testing complete. The powered hub will work with or without the adapter pulling power from the adapter if present.

--> Shutdown Pi.
--> Add USB hub *unpowered.
--> Add USB audio.
--> Bring back up.
Result: Same odd behavior with the controller etc. on different newer hub.

-->Shutdown Pi.
--> Plug in power adapter to USB hub.
--> Turn on.
Result: Everything works as expected.

So in my case it was a voltage issue with the X-Arcade and the USB audio being on the same USB hub.

See the Docs on how to transfer games/roms to your RetroPie installation.
The easiest method is via file shares, from a PC in the same network. USB should be used when you don't have a network connection and yes, you can keep what info/files you have on it, RetroPie only looks in the retropie folder on the USB.

Ok, I guess there is not much I can do.
Thanks @lostless
Can anybody recommend an adapter that works?

@mitu I think I did. My wifi dongle and hub arent working but they work in retropie without issue, no drivers.

@mitu Yeah, unfortunately even though they are physically different PCBs, they detect as the same type (Generic Dragonrise USB Controller)

@darkwriter shoot! I just saw this. I had the exact same problem with my sn30pro controllers. Start+B for USB. I wish I had been here yeasterday to post. The manual gives zero clues about this. Glad they work now.

David

Thank you both.

@mitu LOL... Don't I feel like an idiot... Figured it was something silly and it is.

@mitu ok cool thank you.

@G30FF I did not realize the wired version had that limitation, that's good to know

You're right, I've edited my post accordingly.

@XEntombmentX Ah shucks that happened to me the first time too.
For future reference, when done transferring files, right click the disk in the manager and select "Flush Cache to Disk" and then it's ok to remove the drive.
I should have mentioned that.

Glad it solved your initial problem.

@Crush Thank you so much! That worked perfectly

The EEPROM is outside the OS, so changing the OS wouldn't have helped.
As I said, you'll need to use the stable version to get USB-MSD boot working, by default rpi-eeprom-update will use the critical update version - as you found out in your latest update.