@mitu I had a look at the configuration/tool menu and found an option over there to generate the steam list of games. Thank you so much!

Hi,

Thanks for your prompt reply.
Sorry for not having fully specified my config.
When writing this very post, I was going through the template for it using the link you provided and came across the question 'usb devices connect'. At this point I thought of trying starting Amiberry without having my 2 Xbox (original) controllers connected, which are in turn connected to my USB hub.
And guess what...this did the trick! Amiberry now starts fine. I'm able to reproduce the issue so this is really the problem. Disconnecting either one of the 2 controllers will also work. But 2 at the same time won't work. I'm not having any other issues with both connected at the same time. I have a 5A PSU and never seen the rainbow logo with this setup except immediately after power on (bios screen).

I hope this may help anyone else stumbling upon this in the future.

@rafaz182 having the same issue with 4.7.1. Downgraded to 4.6 with a new flash but stopped working after doing an "apt upgrade" on 4.6 - did this fix you posted worked on 4.7.1?

@pscotto1234 said in Bluetooth RetroPie Setup Script Issues:

@spaceace said in Bluetooth RetroPie Setup Script Issues:

Hi, All.

Thank you for this thread. I found it AFTER I clicked the button to order my controller! I now have the 8BitDo SN30 Pro+ controller working flawlessly on a Raspberry Pi 4B, with RetroPie 4.7.1 on updated OS.

Before I attempted to pair, the pad was connected via USB to the Ultimate Software application for a firmware update. I also configured a Switch profile, with star(★) as turbo button.

I followed these steps before pairing, too. I consider these safe steps, as it only disables an unused SIM card driver and delays bluetooth start for two seconds at boot.

So, then...
$ sudo nano /lib/systemd/system/bluetooth.service
$ sudo nano /lib/systemd/system/bthelper@.service
$ sudo rm /etc/udev/rules.d/99-bluetooth.rules
$ sudo reboot
$ sudo /home/pi/RetroPie-Setup/retropie_setup.sh
Configuration / Tools -> bluetooth
hack OFF
power on controller by holding Y + start one second (Switch mode)
hold in pair button for three seconds
leds will rotate like knight rider
Register and Connect to Bluetooth Device
on "Searching" screen, pressing some buttons can help
choose "Pro Controller"
DisplayYesNo
Setup the udev rule
hold start three seconds to turn pad off
reboot
turn on controller
configure input
GOOD

I have the pad in Switch mode. To select the profile with turbo, press both sticks (L3+R3) and the heart/home button will light up. Hold a button and press star(★) to enable/disable turbo. It will stay in Switch mode with profile, so now all you have to do is hold the start button to turn it on or off.

Hope that helps. Cheers.

It works fine Smith DS4. Later I'll give it a try using a sixaxis controller.
@spaceace thank you so much!!!

Sixaxis works as well!!!

@jdotfite

I reached out to losernator and he was kind enough to provide an explanation and a quick fix:

"Piemarquee2 gets the rom name from the list of running processes, and game-specific options should affect that.

It seems that mk.zip.cfg was recognized as a rom file
quick fix : rename marquee "mk.png" into "mk.zip.png"

I created a duplicate mk.png and mk.zip.png to take care of the menu and in-game and all is good now!

@mitu Amazing, thanks. I'll try this later and see if I can get everything updated

Are you running RetroPie/EmulationStation from a desktop session ?

@mitu I confirmed that the initial freeze reported in November is not the same as the freeze I am experiencing. I also confirmed that this commit in ES-dev from 26-Feb is causing my RPi4B freeze. Only trying to understand why, since I'm certain that when I first received this commit, everything was fine with my system, and had been for quite sometime. I only started noticing random freezes after updating RPi software with sudo apt update and sudo apt full-upgrade on June 12th, 2021.

HYPOTHESIS #1: Something in the commit may be incompatible with the latest vlc-bin: 3.0.12-0+deb10u1+rpt2.

I ruled out overclocking, as I receive the freeze as often overclocking as not overclocking.

Kernel and firmware also may be ruled out. I rolled back to January, well before I noticed issues and freeze still occurs. Possible user-error on my part, but I doubt it.

I also compiled a version of vlc (version 11) but I failed to get it to render with the screensaver (or video snaps)... I may try again to prove or disprove my hypothesis above.

Beyond that, I'm out of ideas. Something changed since that commit. Not sure how many people are running ES-dev. The improvements are remarkable. But to remain stable, I'll have to stick with stable.

Hope this information is helpful.

@papinist I've literally updated from 4.4 to 4.7 yesterday. See my post here about the steps I took:

https://retropie.org.uk/forum/topic/29033/upgrading-to-retropie-4-7-1-are-these-the-correct-steps?_=1609350446790

It might help a bit?

@clyde said in Updating 4.6.x to 4.7.1:

My 4.6 installation became 4.7 just by the normal update process

And as I just checked, it's 4.7.1 now. So yes, it went all the way from 4.6 to 4.7.1. 🙂