just activate the system.power.switch=PIN56ONOFF and, with cables connected to Pin5 and Pin6, play with the different combinations on the real switch until you find what is right.
I'll give you the REAL answer : you can emulate an piB at least in windows (and it is awfully sluggish). But you won't have any "display" but console. Don't expect to run emulatiostation ...
@eb2016 savage reboots or poweroffs cause such side effects, it's not a matter of pricy usb key. There is no.auto fsck (the linux checkdisk) on recalbox (yet)
I was on beta 6 before and all was good.
Then the recalbox autoupdater told me of a new update which I installed. That was the above mentioned version that caused all the issues.
Since I found no other solution, I now drastically wiped the entire system and did a clean re-install of beta 4. I will stay clear of updates for now, hoping that this problem will not re-appear.
I didn't get if you are also having problems with your xbox controller or not. But back to the ps3, you can't activate the xbox driver and expect the ps3 driver to work. That is clearly stated on recalbox.conf. Have you tried deactivating the xbox driver, and activating (the right) ps3 driver?
Just to be clear... don't except both activated drivers to coexist.
If that doesn't help you... buying a compatible controller is always a good idea 😉
@davidwrightini Might be caused by the fact your pi doesn't cope well with overclock frequency. Try to lower down the arm_freq parameter in your config.txt to 1250 and see if it boots ok. If so, then increase the value to 1300 and check up if it boots.
Not all Pi3 behave the same regarding overclock. And adding a small copper heatsink on both your CPU and SDRAM chips might help too (it's strongly advised when pushing frequency over 1300 Mhz and becomes mandatory if you want to reach 1400 Mhz in a stable way)
You only need it if you're scraping games. I would suggest using this to scrape your games from desktop and then transferring the gamelist.xml and stuff over.