Figured I'd share the error I was getting. Firstly, you need to be using Python 3+ for the version of ansible.

sudo pip install ansible

Downloading/unpacking ansible Downloading ansible-2.4.1.0.tar.gz (6.7MB): 6.7MB downloaded Running setup.py (path:/tmp/pip-build-f2xlqxxd/ansible/setup.py) egg_info for package ansible no previously-included directories found matching 'ticket_stubs' no previously-included directories found matching 'hacking' Requirement already satisfied (use --upgrade to upgrade): jinja2 in /usr/local/lib/python3.4/dist-packages (from ansible) Requirement already satisfied (use --upgrade to upgrade): PyYAML in /usr/local/lib/python3.4/dist-packages (from ansible) Requirement already satisfied (use --upgrade to upgrade): paramiko in /usr/local/lib/python3.4/dist-packages (from ansible) Requirement already satisfied (use --upgrade to upgrade): cryptography in /usr/local/lib/python3.4/dist-packages (from ansible) Requirement already satisfied (use --upgrade to upgrade): setuptools in /usr/local/lib/python3.4/dist-packages (from ansible) Requirement already satisfied (use --upgrade to upgrade): idna>=2.1 in /usr/local/lib/python3.4/dist-packages (from cryptography->ansible) Requirement already satisfied (use --upgrade to upgrade): asn1crypto>=0.21.0 in /usr/local/lib/python3.4/dist-packages (from cryptography->ansible) Requirement already satisfied (use --upgrade to upgrade): six>=1.4.1 in /usr/local/lib/python3.4/dist-packages (from cryptography->ansible) Installing collected packages: ansible Running setup.py install for ansible changing mode of build/scripts-3.4/ansible from 644 to 755 changing mode of build/scripts-3.4/ansible-playbook from 644 to 755 changing mode of build/scripts-3.4/ansible-pull from 644 to 755 changing mode of build/scripts-3.4/ansible-doc from 644 to 755 changing mode of build/scripts-3.4/ansible-galaxy from 644 to 755 changing mode of build/scripts-3.4/ansible-console from 644 to 755 changing mode of build/scripts-3.4/ansible-connection from 644 to 755 changing mode of build/scripts-3.4/ansible-vault from 644 to 755 no previously-included directories found matching 'ticket_stubs' no previously-included directories found matching 'hacking' changing mode of /usr/local/bin/ansible to 755 changing mode of /usr/local/bin/ansible-doc to 755 changing mode of /usr/local/bin/ansible-galaxy to 755 changing mode of /usr/local/bin/ansible-connection to 755 changing mode of /usr/local/bin/ansible-console to 755 changing mode of /usr/local/bin/ansible-inventory to 755 changing mode of /usr/local/bin/ansible-vault to 755 changing mode of /usr/local/bin/ansible-playbook to 755 changing mode of /usr/local/bin/ansible-config to 755 changing mode of /usr/local/bin/ansible-pull to 755 Could not find .egg-info directory in install record for ansible Successfully installed ansible Cleaning up...

Looks good so far, but...

ansible --version

ERROR! Unexpected Exception, this is probably a bug: unsupported operand type(s) for %: 'bytes' and 'bytes' the full traceback was: Traceback (most recent call last): File "/usr/local/bin/ansible", line 85, in <module> mycli = getattr(__import__("ansible.cli.%s" % sub, fromlist=[myclass]), myclass) File "/usr/local/lib/python3.4/dist-packages/ansible/cli/__init__.py", line 38, in <module> from ansible.inventory.manager import InventoryManager File "/usr/local/lib/python3.4/dist-packages/ansible/inventory/manager.py", line 44, in <module> IGNORED_EXTS = [b'%s$' % to_bytes(re.escape(x)) for x in C.INVENTORY_IGNORE_EXTS] File "/usr/local/lib/python3.4/dist-packages/ansible/inventory/manager.py", line 44, in <listcomp> IGNORED_EXTS = [b'%s$' % to_bytes(re.escape(x)) for x in C.INVENTORY_IGNORE_EXTS] TypeError: unsupported operand type(s) for %: 'bytes' and 'bytes'

You have changed to KIOSK mode. Enter the Konami code to revert.

↑ ↑ ↓ ↓ ← → ← → B A

I know this is an old post but just in case anyone still needs holesaw recommendations, Toolstation does a great range: https://www.toolstation.com/shop/Power+Tool+Accessories/d80/Holesaws/sd1530

Another thing to make sure of is that the controller firmware is up to date.

http://support.8bitdo.com/

8bitdo has gone through many iterations of their controller software. I didn't use the 8bitdo hack but was able to connect the controller normally to a Pi Zero W using normal Bluetooth methods.

@dankcushions I've personally never had any issues with canakit chargers but I also don't overclock

@exonerated I have that the majority of the times I have my PS3 controller plugged in via USB. It stays stuck in a never ending black screen restart loop - both at startup and on exit.

If it's the same thing, I find that unplugging it usually helps.

@necrym hi.

First of all, take no offense here. If you indeed developed something and wanted to share, thank you for the effort and contributing!

Don't take offense if someone doesn't want to download a pre-compiled binary without source code from such a source. It may be with your best intention but in this day and age better safe than sorry, really.

As @herb_fargus and others said, there are other ways to share software that people are more comfortable with. Just that.

As for the ROMs and such, while the idea and argument sound reasonable at first, truth is they run inside an emulator, which in turn are for the most part open source. As such, unless there's a clear backdoor in each of those, ready to be exploited, for the most part running those ROMs will not result in any harm. Worst case scenario the emulator will crash.

Now if you'd be taking about running a pre-compiled emulator from one such website, the same concerns would apply.

Hope that helps.

I'm wondering if I might have better luck with v16 of Kodi. Is there a way to downgrade?

Thanks for the great suggestion, I wasn't aware it was on top of Raspbian Lite. Now that I know that, it doesn't make sense for me to have two versions of Raspbian!
Cheers for the speedy responses.

@griffon I hear you. Others have reported similar or related issues, and I have a similar problem on my TV as well, whereby sometimes the audio won't play until I change channels and then come back to the HDMI input on my Toshiba LCD TV.

Clumsy HDMI handshake implementations is my best guess.

@ogaspard

https://retropie.org.uk/forum/topic/3/read-this-first

Power supply?

Thanks, I tried that & it seems to have worked.

@blitzgreig You need to start by posting the information requested in this post:
https://retropie.org.uk/forum/topic/3/read-this-first

No idea what hardware you are running, what software etc.....

Just for confirmation, I tried Starfox 2 Zipped on 'lr-snes9x2010' and it ran fine (tiny bit of sound stutter here and there). Maybe you had some dodgy compression on your Zip file.

@modiggity are you using emulation station or attract mode?

Anybody got any answers for this yet?

@buzz Updated setup script and vice from binary; xvic now launched correctly with specific parameters. Also edited emulators.cfg for expanded as suggested.

Runcommand.log is here.
It shows some errors, probably just minor as cartridges seem to work perfectly.

Thanks for the fix ! Really appreciated.

I'm pretty sure I've got this sorted out now. It's set up pretty close to how the N64 layout was. I changed the rumblepak switch to requiring a hotkey to be activated. Current setup is below.

DPad R = "button(13)"
DPad L = "button(14)"
DPad D = "button(16)"
DPad U = "button(15)"
Start = "button(9)"
Z Trig = "button(6)"
B Button = "button(1)"
A Button = "button(0)"
C Button R = "axis(2+)"
C Button L = "axis(2-)"
C Button D = "axis(3+)"
C Button U = "axis(3-)"
R Trig = "button(5)"
L Trig = "button(4)"
Mempak switch = "button(11)"
Rumblepak switch = "“J0B8/B12”"

Analog axis configuration mappings

X Axis = "axis(0-,0+)"
Y Axis = "axis(1-,1+)"
Joy Mapping Stop = "J0B8/B9"