For the complicated option (I have not tried this btw :) get one of those backwards compatible PS3s and make it dual bootable with Linux, run PS2 games on the straight ps os and maybe other emu's on the Linux boot?
:) I see youtube videos of people doing some of that but don't really know if the whole thing is possible. Might be fun to look into though if you have too much time?
edit: and maybe you could try to find an broken PS2 to just use the enclosure, take apart the PS3 and fit it into the PS2 shell. Voila! A PS2 made out of a ps3! :)
@mitu Is solved now if I changed the theme and worked everything. I just have in some psx games issues with te control but is minimal. Thank you for all. Now is time to play after the hard work of configuration almost 3 weeks wow!
Thank you @mitu for all help. I almost finish my image from other posts you helped me to solve. In the case of the game pads I write a solution worked for me, just in case someone is lost and can be useful. This is the solution:
Finally I could make work two 8bitdo SN30 Pro 2 game pads. I used the firmware V1.2 and worked pretty with this same technique. However, I wanted to try with the latest V1.3 firmware to see what happens and I could make work. Fighting with the retro arena setup and also retropie setup both versions in the bluetooth script, it just worked for me the first time and after the first time is impossible, at least for me, to pair again by the horrible error Already exists bluez.org. Something is stored in the cache or somewhere after the first pairing but I could not find information in any place. Most of posts run from a real solution and they mention “my solution was begin with a fresh image and problem solved”. I made that but if you have a mistake, like in my case, is an endless loop over and over again and no solution. Then this is what I did:
First I made a copy, to have safe the original file “/etc/dbus-1/system.d/bluetooth.conf”. Then I replaced that file with this:
At this is step it will pair although and is possible it can says cannot connect. No matter this is not a thing to be afraid. If it doesn’t connect or says fail to connect in specific: Turn OFF if it is ON the game pad. Turn ON again normally the game pad and type again step 7 (connect with the mac address command).
It can says a couple (2 or 3) times is not possible connect but no matter it will do. Simply is turn OFF the game pad and ON again and give the “connect” command again. Once say successfully connected is give this command:
8.-trust “mac address of the gamepad”
9.-Return the original file “/etc/dbus-1/system.d/bluetooth.conf”, deleting the one of pastebin above described. Just in case. I used the pastebin temporary just to pair, after pair there is no sense to keep it.
If in the step 6 of pairing says already exists bluez.org or simply never connected in step 7 then is type first to see the devices paired:
After that is check if i there the game pad. If it’s there then is give now:
remove “mac address of the gamepad”
One is successfully removed is back to step 5.
Once is paired, and connected, because It will pair for sure, also will be detected ALL the buttons by emulation station. I have two gamepads and both were detected including after reboot and latest firmware. I tested this like 10 times to be sure, including making tests downgrading and upgrading firmware in the game pads and always worked at the end. I write this just in case someone has a problem as me and want time and loss time beginning from fresh image and is wanted to save time.