Or on Linux, do

sudo fdisk -l

Do you have a link to what you purchased? That can help give a specific answer to your equipment.

Your buttons have separate pins for the button action (micro switch) and the LED. This can be good because it means you can power the LED separate from the button functionality.

I'm going to guess you have something like this:

0_1524260873912_4ccfb34c-a7a0-407d-ad73-1d3e0ebdcab1-image.png

The two pins on the top are the switch and you can tell this because they are connected to the little grey box (which is the switch itself) The yellow is positive and the black is ground.

The bottom two are the LED and similarly you can tell because they are not connected to the switch (little box). The red is positive and the black ground. In this image the ground is daisy chained, which is fine but you can ground the led separately if you want to.

Now for the Wire connectors.
It sounds like they sent you button connectors (two wires, two pins). This can work if you are going to wire up the LED power separately, but they should have sent you 3 pin connectors that would connect to the 3 pin led button slot like this;

0_1524261463917_43920c32-d487-4097-8947-dfd2a0e68239-image.png

I'm explaining using a lot of presumptions here so I will wait and see what you have before going any further.

As for 12 volt led buttons. That is a bit odd and over powered. easiest way to test is to wire one up to a 5 volt source and see how bright it is. If it works well enough for you GREAT. If not then ramp it up to a 12 volt and see what you get. Once that is answered you can look into set ups that will work (IE external 12 volt source) or replace them with 5 volt led buttons.

@bigbugz420 said in Retropie for Raspberry Pi 3 B+?:

saves me opening a topic

You should always open a new topic and include the requested information from https://retropie.org.uk/forum/topic/3/read-this-first

@majere How are you checking the status ? A normal lsusb should list the USB adapter. If you run dmesg | tail immediately after plugging it in, you should see if it's detected, something like this should be printed:

[ 2.305588] usb 1-1.2: new full-speed USB device number 4 using dwc_otg [ 2.450005] usb 1-1.2: New USB device found, idVendor=0a12, idProduct=0001 [ 2.450023] usb 1-1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [ 2.450031] usb 1-1.2: Product: CSR8510 A10 ... [ 3.595425] Bluetooth: Core ver 2.22 [ 3.595760] NET: Registered protocol family 31 [ 3.595767] Bluetooth: HCI device and connection manager initialized [ 3.595794] Bluetooth: HCI socket layer initialized [ 3.595810] Bluetooth: L2CAP socket layer initialized [ 3.595851] Bluetooth: SCO socket layer initialized [ 3.657289] usbcore: registered new interface driver btusb

If this is the product you're using, it should work without problems.

@john0007 said in SD card use. Download retropie:

@dankcushions thanks. So can someone help me how can I download the retropie. It's giving me problems on network error and corrupted when download.

What error(s) did it give you exactly? What browser or other software did you do the download with?

The MAME 0.78 debugger code may not actually be functional in the MAME 2003 core. Someone else may know that for sure.

If you haven't, I'd suggest that you try the hacked ROM with the original MAME 0.78 software before trying to set up lr-mame2003 in order to have a baseline.

@rbair6600 Thanks for sharing your solution.

@rbaker kool thanks

Thanks for the info @Lupin !
I ended up finding this: https://www.raspberrypi.org/forums/viewtopic.php?t=130294 and updated it with your information.
So this is my working setup:

In /etc/emulationstation/es_systems.cfg, add:

<system> <name>Media</name> <fullname>Movies</fullname> <path>/home/pi/RetroPie/roms/movies</path> <extension>.avi .avi .mp4 .MP4 .mkv .MKV</extension> <command>/opt/retropie/supplementary/runcommand/joy2key.py /dev/input/js0 kcub1 kcuf1 kcuu1 kcud1 0x70 0x71 & omxplayer -o hdmi %ROM% killall joy2key.py</command> </system>

Now create a folder called movies under /home/pi/RetroPie/roms/and place your video-clips in there.

Bonus: If you want to hide the text that shows up when skipping forward/pausing and so on, change to omxplayer --no-osd -o hdmi %ROM% in the code above

It seems that you should be able to use the linux way by being in developer mode, opening crosh, and typing shell.
You then will have a bash shell, with the dd command.
Careful to use the correct device as target for dd.

I also see that the chromebook recovery utility can be used too - see here : https://www.reddit.com/r/chromeos/comments/7d02im/using_a_chromebook_to_install_an_iso_to_a_usb/

The length and quality of your HDMI cable could actually have been the culprit, as you said.
You may want to try with a better/shorter cable.
Another way could be to boost the HDMI signal by editing config.txt, see here : https://elinux.org/RPiconfig#Video But a good cable is a better solution.

Hi BittenPeach,
at the screen on your picture, enter echo "emulationstation #auto" > /opt/retropie/configs/all/autostart.sh. That should recreate your autostart.sh. Enter sudo reboot to reboot the system. It should now boot into Emulation Station like before. Let's hope that's the only thing missing.

@bluecrown You should take a look at the Docs and do some research on the forums regarding the specific emulator you are using. I don't run any playstation emulation, but I noticed there are least three (3) different PS1 emulators alone!

If you are going to ask questions about performance, do your research first, try suggestions in the documentation, and for heaven's sake, if you end up asking about something specific, don't just mention the name of the game you are plyaing--you also gotta describe in detail what emulator you are using, and depending on its capabilities, what settings you are using etc.

That said, perhaps with more detail, someone will add their experienced answer here, although this thread was about YouTube, so. . .