Please try “keep bluetooth scanning” fix from here:
https://github.com/RetroPie/RetroPie-Setup/wiki/Setting-up-a-Bluetooth-controller

I suppose your bluetooth dongle is not up after a reboot. If you connect a controller over usb a script will enable your bluetooth controller. So it is only necessary to connect “one” controller once if dongle is not enabled after boot.

[quote=115931]Ok, so I can’t do the first USB method as I’m in Windows (So, as you said, there’s only the 56MB partition available)[/quote]
i’m not sure i understand this. you don’t need to see the SD card file structure on windows if you’re doing the USB method – (reiterating the video) you put the USB in the pi whilst retropie is running, and it will create a folder structure. connect the USB to your pc then put the roms in the relevant directories on the USB, and then you put it in the pi and it will transfer everything to your SD card. you never need to access the SD card on your PC.

/tmp/runcommand.log will have information in it after a successful OR unsuccessful rom load. you must be looking in the wrong place. try running a rom that does work and checking for it.

are you reinstalling your system and then doing all this USB drive mapping before you actually get a neogeo game to run? it’s difficult to see where your problems are because you seem to be doing lots of things at once. a fresh retropie install will run a correctly sourced neogeo rom, if it has the right bios installed. there’s no configuration needed.

So I have found that in my case it was a directory ownership issue. I must have upset the permissions when adding roms to the folders (I do seem to recall renaming the Snes folder by accident and changing it back).

To solve the issue I ran the Retropie setup script and chose the option to ‘Reset ownership/permissions of /home/pi/Retropie/roms’.

After that I ran the ‘Start USB rom service’ option and all of my missing roms showed up on next reboot.

I am fairly new to Retropie and I am guessing that this must be a somewhat common problem if there is a dedicated script for fixing it, but searching the forums, this was the first post I found on the matter.

Hope the solution is this straightforward for everyone else having a similar issue.

Just use a usb switch to cut power to the pi completely and it will work fine with your auto hdmi switch. Here’s the one I use: https://www.adafruit.com/products/1620

Just make sure to shutdown in emulationstation first to avoid corrupting the card.

I have the same issue. Sound works in games etc. because I have configured the defaults to point to my USB hardware, but volume level changes fail and related errors persist. I think it’s because of calls to the simple channel element “PCM” which is no longer available when I enable my USB audio as the default. In my case, it’s a C-Media adapter that responds to the channel element named “Headphone”.

One promising I idea I was trying was to setup an ALSA plugin that makes my USB hardware mirror everything sent to the built-in audio. This requires undoing the USB default settings so the built-in audio becomes the default again and the “PCM” named element is available. That eliminated the errors, but not every emulator had audio. If we could make this audio syncing work with some ALSA expertise, that would solve the issue for everyone, regardless of their USB card’s channel element names. It’s beyond my knowledge of ALSA setup–the trial and error takes so long because I don’t know what exactly I am doing!

I am having the same problem. Ever since RetroPie v3.4, it appears that the automatic USB rom service somehow gets interrupted and doesn’t finish. I have had to manually copy the files over myself.

I too am having the same issue. I am running a fairly clean copy of Retropie v3.4 on a Raspberry Pi 2. So far the only changes I have made are to add a couple of bluetooth devices and a Udev rule for one of them.

I am attempting to load the roms from a 16Gb SanDisk USB formatted to Fat32 with less than 2Gb of data on it using Retropie’s built in copy service.

All the roms copied across for systems named A-S(Scummvm), up until it got the the Snes folder where I had a 0% success rate. The same applied to the ZXSpectrum. The files look fine to me, the folder structure has not been changed from when the copy service created them. At the moment I am at a loss as to why they don’t copy across, but I will continue to investigate when I get the chance.

does anyone still have the fix files? both the links in the thread 404’ed. I am using a raphnet nes2usb and the joysticks are shwing up as the same index

That’s awesome! Maybe you can help me. I’m new to the Rasberry Pi world and never heard of these things until I ran across a local guy that sells them ready to use as an arcade system with usb snes controllers and pre-loaded with thousands of old games. It is a Pi 2. It appears he used RetroPie. I know nothing about modifying these things or typing commands or scripts. I decided I want to be able to use my Logitech Harmony remote to power on/off the Pi system with the rest of my entertainment stuff. (And/or also a physical power button on the Pi would be helpful) I ran across the RemotePi add on board which is exactly what I wanted and I ordered one. I had the belief that all I had to do was attach the add on board and I was done aside from having the unit learn my selected remote button. Now I’m seeing that I may need to install a shutdown script. Can someone tell me if I really need to install a shutdown script or is it already done? At the main menu when playing the Pi I can press the start button and there is an option to power off already.

Now, since I’m a noob to this techy stuff…if I need to install something. How do I go about doing it? Ethernet hooked to my router or Windows computer? I’m sorry I’m so needy but I would love to learn more about this and am seeking kind support from you. Thanks in advance.

[quote=115986]I have ps1 games on an external drive. I do use a powered hub for it but I have it formatted fat32 and I have no issues. They seem to play just fine for me, though I haven’t played a ton of them yet.

[/quote]
My work recently gave me a 1TB usb drive, which I’m now using with my pi. I had originally formatted it as exfat. When I put a bunch of psp .iso files on it, only about 5 showed up in ES. I tried fat32 next, which wasn’t much better. After that I tried ext4, and that works flawlessly. It’s worth mentioning that I was using a USB hub because this USB drive is unpowered.

I have another usb drive permanently connected to my pi, that I believe I have formatted as fat32. That one is not on a usb hub, is powered, but is a lot slower than the ext4 drive in terms of copying roms to the pi via SSH and onto the drives. Copying files the same way to the ext4 drive is much faster. (I found this out by mistake. lol) Since they’re both going over the network and through usb, the only difference I can conclude is the file system on each drive.

[quote=115978]Apologies for my ignorance, but how would I go about formatting a usb hdd to ext4, can it be done through the raspberry pi 2 terminal? Once the drive is ext4, what would be the procedure for copying roms onto the drive using windows 7.
[/quote]
I used a GParted live cd to boot from, then formatted the drive with that. It gives you every option under the sun.

http://gparted.org/download.php

Once you have it formatted, windows can read/write to it as well.

[quote=115978]
Also, if I changed the usb port max voltage or used a powered usb hub, would that be sufficient for a non-powered usb hdd?

thanks again![/quote]
I don’t know. I’ve considered modding one of my pis to try to increase the voltage to the usb ports, but haven’t gone through with it.

A powered one would be better. (It may actually be a need.) The pi has issues when things draw too much power from it’s USB ports.

Probably. You could use a usb hdd as well if you format it with ext4. That’s what I’ve done for some systems. there are no performance issues, but the filesystem type is very important. For example with exfat, the drive won’t be fast enough and ES will only see a handful of roms before it starts up.

I recently purchased 2 Hori Fightstick Mini 4s and am very pleased by the result. I think you got little to nothing to fear when hooking it straight up though USB but no idea how well they would work with a control block.

if your having issues with symlinking just get a copy of your es_systems.cfg point all off the rom paths to your usb drive, don’t worry about the uuid it’s not too important if your just going to use 1 usb drive

oh and delete your symlinks

It doesn’t work… there exists a lot of errors…

= = = = = = = = = = = = = = = = = = = = =
Installing dependencies for 'retroarch' : RetroArch
= = = = = = = = = = = = = = = = = = = = =

Did not find needed package(s): libudev-dev libxkbcommon-dev libsdl2-dev mali-fbdev libusb-1.0-0-dev. I am trying to install them now.

= = = = = = = = = = = = = = = = = = = = =
Installing dependencies for 'sdl2' : SDL (Simple DirectMedia Layer) v2.x
= = = = = = = = = = = = = = = = = = = = =

Did not find needed package(s): devscripts debhelper dh-autoreconf libudev-dev libdbus-1-dev mali-fbdev. I am trying to install them now.
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package mali-fbdev
Could not install package(s): devscripts debhelper dh-autoreconf libudev-dev libdbus-1-dev mali-fbdev.
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package mali-fbdev
Could not install package(s): libudev-dev libxkbcommon-dev mali-fbdev libusb-1.0-0-dev.

Ok… now… find how to fix it :)