I have similar problem. I thought its my adapter to the monitor. I use a dongle for keyboard too. What was the interval when you got this screen freeze? I get it maybe once in a hour. Maybe its a different story on my side.

Thanks Mitu!!

It seems that adding/enabling these lines in the config.txt fixes the problem

sdtv_mode=2 #My tv is PAL
sdtv_aspect=1 #4:3
audio_pwm_mode=0
dtparam=audio=on (this one is enabled by default)

Please add more details about your system as requested in https://retropie.org.uk/forum/topic/3/read-this-first.

Thanks guys, it was the case power

@boxdrop My buttons are configured to certain keys, so it'll hopefully work.

@pandamkii You don't unzip MAME roms, this is the way they're distributed they'll not work otherwise. If you're considering adding MAME to your setup and you're a beginner, then please read the Quick Start and the topics linked on that page. It will answer most of your questions and will help you understand how MAME rom(set)s work.

@mitu

Thank you SOOOO much. You're amazing! :-D

@quicksilver Awesome, thank you for the tip and info!

@jonnykesh you are right. I am an idiot. And i set that every time i set up a pi so i should have remembered that.

I don't think that it is specific to the Xbox dongle. I am having the same issue and found this on the rpi github. It looks like the kernel is having a hard time with USB hubs.

F/W 4.14.x causes dwc_otg_handle_mode_mismatch_intr:68: messages on boot with C-Media Electronics Inc. USB PnP Sound Device

I tested this with success. But I had to set dtoverlay=dpi24 and dpi_output_format=6 to fix some incorrect colors and use the below NTSC 320x240 timing line:

hdmi_timings=320 1 23 30 34 240 1 4 3 15 0 0 0 60 0 6400000 1

@likethereindeer Thanks, but I meant at the beginning of the title so that it reads "[SOLVED] Prep a 128GB Card on Mac". So everyone can see in the topic list that the thread has already been solved. Potential helpers can then look for other problems to solve, and people with the same problem as yours know there may be a solution to be found here. :)

@mitu said in Pi3 B+ Stretch 3.5 audio out problems:

Seems similar to https://retropie.org.uk/forum/topic/17864/raspberry-pi-ridiculously-slow-when-splashscreen-service-is-enabled. Modify the /boot/config.txt and add

audio_pwm_mode=0

then restart and check if it fixes your problem.

yes! adding that line worked, thanks for the tip!

@udb23 I concur. To my own biggest surprise, I managed to get a genuine copy of the Dragon's Lair 20th Anniversary 3 DVD box (as far as I can tell, but Daphne recognizes it, too) for only 4,04€ plus 3€ shipping at the German Amazon Marketplace last month. \o/

I also expected a fraud, but for that price plus Amazon's refund guarantee, it was worth a try.

@azymuth said in Config 8bitdo + 360 (rasp 3 b+):

my 8bitdo sfc30 pro doesn't want to connect immediately on my rasp, i have to reconnect it often and it's often complicated. Have you a solution on it, to better autorun the connection ?

Make sure the controller is set to connect in 'Android mode' (see http://download.8bitdo.com/Manual/Controller/SN30pro+SF30pro/SN30pro+SF30pro_Manual.pdf) when you pair it via Bluetooth and that you're using the 'default' connect mode in RetroPie.

and second one, i would like to play on super bomberman 3 with my friend but when i connected two xbox360 controller on my raspberry, i can't play with my 8bitdo. This 3rd one not even appeared on the select menu of character.

Are the controllers configured in RetroPie ?
Please give more details about your setup - https://retropie.org.uk/forum/topic/3/read-this-first.

I had the same problem with Megadrive too. I think what screwed everything is the saving on exit...

I could not fix it no matter what I tried, so I started doing a fresh install.

It is so frustrating....

@mitu wow - thanks again - must have done this on the prevoius install and somehow forgot :-/

I think I may have found the solution to my problem.
There may be an issue with the Xin-Mo USB controllers.

The Xin-Mo controller that I have has an internal identification as: Xinmotek Xinmotek Dual Controller
In the configuration files sent to me, has it is identified as: Xin-Mo Xin-Mo Dual Arcade

Change the name in the configuration file, appears to solve the problem.