I just completed setting up the USB loader and it’s working great. I had some trouble, but a fresh flash and a reformat of my drive did the trick. Thanks for the help and advice!

@martinfr said in RPi 1 Model B only reports 256MB RAM under RetroPie:

To my surprise, the OS only reports 256MB of memory (checked through ssh).
Is that expected? If not, how can I tell it to use the full 512MB?

I think so - the rest of the memory may be reserved for the GPU, since it's used by both the front-end (EmulationStation) and the emulators.

ok so that may not have been my problem but i did get it paired but the only change i did was for something else which was turning off hardware acceleration cause it would crash when trying to scroll through games. dont have any idea how there connected though. but after that paired just fine.

just closing the loop here, for 1. i didn't figure out how to map the system's joystick fire button to a gamepad button but after some online searching apparently every TI994A game can be controlled solely by the keyboard - the fire key for Shamus is "q" after some trial and error (hold "q" and press the direction of fire). all good now!

We don't support 3rd party images - image your sd card with the image from retropie.org.uk/download. We don't know how the sdcard you purchased was configured or pre-installed with RetroPie.

@Yobiwan said in Daphne Resolution Issue:

What would you recommend ?

Opening a new topic and detailing what you tried so far and it's not working.

@neutrios

I have a DragonRise Inc. USB Encoder and haven't had any issues mapping the buttons in Retropie 4.6 on a Raspberry Pi 4 4GB

the config is here ...

/opt/retropie/configs/all/retroarch/autoconfig/DragonRise Inc. Generic USB Joystick .cfg

and inside the .cfg is my button mapping

input_device = "DragonRise Inc. Generic USB Joystick "
input_driver = "udev"
input_enable_hotkey_btn = "6"
input_l_btn = "0"
input_load_state_btn = "0"
input_up_btn = "10"
input_left_btn = "11"
input_state_slot_decrease_btn = "11"
input_select_btn = "6"
input_right_btn = "9"
input_state_slot_increase_btn = "9"
input_r_btn = "5"
input_save_state_btn = "5"
input_y_btn = "4"
input_x_btn = "3"
input_menu_toggle_btn = "3"
input_down_btn = "8"
input_start_btn = "7"
input_exit_emulator_btn = "7"
input_b_btn = "1"
input_reset_btn = "1"
input_a_btn = "2"

@DavidDraper said in Issue with multiple "USB Controller " controllers...:

/opt/retropie/configs/all/retroarch/autoconfig
I thought whatever is in there is automatically copied into
/opt/retropie/configs/all/retroarch-joypads;

It's the same folder, the latter is a symlink to the former.

pi@retropie $ file /opt/retropie/configs/all/retroarch-joypads /opt/retropie/configs/all/retroarch-joypads: symbolic link to /opt/retropie/configs/all/retroarch/autoconfig

@freddyja script.zip is not avalaible, I can't use this guide.

@tpo1990 I am still having trouble with music, even though it is set to "MIDI Only".

Console states "COULDN'T HANDLE MUSIC FILE CASA1" - do I need to copy some files over?

Thanks so much for your work on this and all the other Ports, it's really appreciated!

Edit: I've resolved this by downloading .ogg files and placing them in data1/music, and then selecting "All Codecs".

I didn't it, because i won't dissamble the GPi to connect the keyboard. So i have restored the SD-Card from Backup-File to save time. Now the WiFi works fine. It's a pity that I still don't know what the cause is. I've opened the wpa_supplicant.conf file to see any difference.

country=DE^M ctrl_interface=DIR=/var/run/wpa_supplicantGROUP=netdev^M update_config=1^M network={^M ssid="NETWORK"^M psk="PASSWORD"^M key_mgmt=WPA-PSK^M priority=1^M # RETROPIE CONFIG START network={ ssid="NETWORK" psk="PASSWORD" } # RETROPIE CONFIG END

It seems the same. But, it works. There must be another error.

Just to give a conclusion to the thread, I tried a whole bunch of stuff. I tried jscal, evdev-joystick, updating the kernel, downloading some different files... but ultimately, this is what worked:

https://retropie.org.uk/forum/post/227102

I installed hid-nintendo as described in the post and everything just worked like it was supposed to after rebooting the machine. It makes you reconfigure the controller, but after that, it just works.

The installer looks pretty simple - did it create the retrogame.cfg file in /boot ? Are you running the installer as root (via sudo), as indicated in the instructions ?

Well, you could download the new SDL2 based version and replace the existing one. Since it's better to unpack the archive on the Linux system, you can run from the terminal

wget http://spatula-city.org/~im14u2c/intv/dl/jzintv-20200712-linux-rpi-sdl2.zip sudo mc /opt/retropie/emulators/jzintv

This will download the new version and open up MC with the location of the existing jzintv version on the left pane. On the right pane, browse for the .zip file you downloaded and then just press Enter over the selected file, you'll see the contents of the archive and you'd be able to copy the new jzintv binary over to the left.

Next to mame2003, I can recommend its enhanced fork mame2003-plus and another arcade emulator called Final Burn Neo that is under ongoing development. But beware that every emulator needs its very own romset for the games to work, see Validating, Rebuilding, and Filtering Arcade ROMs.

@wiuenright said in Are you having problems running Roms from SSD Pi4???? + Question:

Whenever I plug into the USB 3.0 it just writes non stop. I don't know what the problem is. Could it be the enclosure??? Is the lack of USB speed going to make a noticeable difference in gaming? Any ideas why this could be happening?

Try looking at the system's messages when you plug in the drive, by running dmesg -w (CTRL+C to interrupt) on the console and see if any errors are displayed.

Make sure you've updated your system (sudo apt update && sudo full-upgrade) to get the latest stable USB firmware and kernel/firmware release.

There's a sticky topic in the RPI forums here for troubleshooting problematic USB3 SSDs, you might want to take a look and see if your enclosure's USB SSD adapter could be one of the models reported with issues.

Oh great, thank you! This is my first real try with using RetroPie so I'm not familiar with some of how it works 😄