@herb_fargus Its an idea but I do not have any spare usb drives.

Did anyone get to the bottom of this? I have the same issue.

@BuZz

Thank you for your quick reply BuZz!
Man I feel so stupid at the end after the 404 error messages it says run apt-get update or --fix-mis
Duh! I was stupid enough to type apt-get update without the sudo command and that didn't work of course.

Now it is downloading the updates and all seems to go well. Thanks again for the quick help.
I really need to get this whole Linux command stuff into my head asap.

Thanks all, I got it all working on my new 128GB card! Joel

@samforce Can you help me? When I try to do the mount command it says it can't find the file, and when I first boot the Pi up, it says this
/bin/sh: 0: can't access tty; job control turned off
Does it have something to do with it?

Bump

@Capeman said in RetroPie on OSX MacBook via Debian via VirtualBox VM:

@johne79 said in RetroPie on OSX MacBook via Debian via VirtualBox VM:

emulation choices are really lacking on OS X

What's wrong with OpenEmu? it's just about the best emulator i've used for any computer/laptop based platform and it's Mac exclusive. RetroPie is by far the best for TV and arcades, but running it on a macbook via virtual machine seems like alot of extra work without much benefit over the more obvious choice.

OpenEmu is ok but I like the frontend interface of EmulationStation far better, just my personal preference. OpenEmu, like EmulationStation/RetroArch, is just a frontend for all the cores. ES gives me some great options for other things like Ports, DosBox included in the menus, etc. This may in fact sound crazy, but when I'm playing any kind of console emulation system, I want everything from the frontend on down to FEEL like I'm using a console, rather than feel like I'm using a Mac, or a Linux box, or whatever. ES does such a great job of being just that, for a moment my disbelief is suspended, it feels so genuine and natural. No other little OS X X's and Minimize/Maximize buttons and other little UI elements that distract my suspension of disbelief. Plus the whole way ES handles game descriptions and the like, it's exactly what I like, no complaints here, it does what I want, just the way I want it.

So i installed from source and it gave me the .sh for rogue and hipnotic. So from there i knew how to make the full version and the dopa ones. So i have them all working now.

However, the keyboard still stops working in linux stuff after playing tyrquake.

@edmaul69 what's deleted?

@BuZz Well Ok then, i'll try later. Thanks for answering my question about keeping it. :)

@Lyle_JP the libretro core needs to support it.

I was searching for an answer to this for a while myself before I figured it out on my own. I'm running version 4 of RetroPie and dispite it being mentioned that the Scraper was fixed in a previous version, I still had some troubleshooting to do. What I found in the error logs is the XML file wasn't able to be written to... in my case, they didn't exist at all, so I wrote this Bash script to create a basic XML file to start it off. After running, hopefully the built in Scraper for RetroPie will be able to save all your data.

#!/bin/bash
#RetroPie gamelist.xml setup
#by Nathaniel Dragon on 2017-02-04
for d in ~/RetroPie/roms/*; do
if [ ! -f $d/gamelist.xml ]; then
echo "Make gamelist.xml in $d"
echo '<?xml version="1.0"?><gameList />' > $d/gamelist.xml
else
echo "$d already has a file."
fi
done
#Enjoy!

I know that not everyone trying to get this to work is a programmer, although, you probably have already found out something about scripts on Linux. In case you've never written or run a Bash script before, save that code in a file on your RaspberryPi as something like "setup.sh" and then make it executable with "chmod 755 setup.sh" and finally run with "./setup.sh" ...

Unfortunatly I am unable to provide the log at this time but kodi works fine until I plug in the usb
I plugged in the usb and let retropie create the file system and then i copy all the roms into their respective folders
I have wiped the sd card and reinstalled the os several times and I get the same results each time
Also once this happens retropie will no longer let me uninstall kodi either
hopefully this helps otherwise i will have to upload the log later

just fyi, I think I figured out how to set up the Bluetooth controller properly from the start so that it defaults to p1, granted I am using an nes30 pro so if there are firmware/hardware differences with the ps3 controller this may not work but its worth a try.

install a clean image boot for the first time. plug the controller in with a wired connection to PORT 4 (bottom right USB)
***DO NOT plug in a keyboard emulationstation should detect one gamepad. go ahead and configure it first (yes it is still wired in) next go to Bluetooth settings and register it
4.a while wired in, select the register option
4.b unplug the controllers wired connection from the controller side (not necessarily from the USB side)
4.c make the controller discoverable
4.d rpi should find the device
4.e plug the controller back in and complete the registration process (set udev rules, boot options, etc.) quit and go back to emulationstation (controller still wired) press start, navigate to configure input and select it - the screen should say that it is detecting TWO controllers UNPLUG CONTROLLER. now press a button for emulationstation to recognize the controller in Bluetooth mode. configure it! unplug the USB side and reboot the rpi reboot your controller and you should be connected in Bluetooth to port0/P1.

at this point you should be able to connect a keyboard as well but USE PORT 4. I also don't bother with configuring it as an emulationstation controller... I ONLY use it to do the typing required in the back end or when searching for roms with the scraper.

the advantage of this method is that your controller shortcuts and all p1 functionality is retained EVEN IN THE MUPEN64 emulator! Using the joypad_index remapping method above works find for libretro cores but I found that playing hires n64 games I didn't have any shortcuts or even an exit for mupen64. With this method you should be good to go.

one other note: if you connect your controller to other devices like me (I travel, so I connect my nes30 pro to my laptop quite a bit) when you reconnect it to your pi, I've found that it is easiest to simply remove the device, then re-register it. you don't need to recreate the udev rule or set boot options... you just remove the device then add it back and you're good to go.

lastly, I've tested pretty successfully with adding other controllers as P2 and it works flawlessly once you get your p1 Bluetooth controller set up.

hope this helps!

Yes.
the board with white connectors is for 90% sure is a Dragonrise Inc USB encoder. It hase kinda little delay for my tastes...
Working like a charm from Retropie 4.0 and above straight from initial flashing.
Done two cabinets with this set.