although updating to Kernel 4.14 works, I recommend against it, if you want to use it for retro-gaming.. you get about 15% performance hit if you use Kernel 4.14 instead of 3.10.Also currently you need to manually install the newer xf86-video-armsoc driver to use G2D support for Kernel 4.14.

Thanks for the info meveric. The only reason really that I updated kernel was my PS3 (USB) controller just would not work properly. It worked in PPSSPP however, when I tried to configure in emulationstation, it would not record any input unless I literally started mashing buttons. A con of the later kernel also is that my the left analog stick takes control of my mouse which is a pain.

I have noticed that I was probably better off with the older kernel as things like Youtube at least worked a bit better. If I choose a 720p video on YouTube now it just is totally messed up and usually the video just turns green.

If I re-image an sd card and start a fresh, do you have any ideas about the ps3 controller?

Thanks

EDIT: COuld I possibly just downgrade the kernel or would that be a pain?

cliffyfromboro wrote:Thanks for the info meveric. The only reason really that I updated kernel was my PS3 (USB) controller just would not work properly. It worked in PPSSPP however, when I tried to configure in emulationstation, it would not record any input unless I literally started mashing buttons. A con of the later kernel also is that my the left analog stick takes control of my mouse which is a pain.

This should allow for wireless PS3 controller.. I use it quite often especially in PPSSPP. EmulationStation should work fine as well, but Kodi will have issues due to some incompatibility.

cliffyfromboro wrote:I have noticed that I was probably better off with the older kernel as things like Youtube at least worked a bit better. If I choose a 720p video on YouTube now it just is totally messed up and usually the video just turns green.

That is due to the lack of correct xf86-video-armsoc-odroid driver. The G2D part is not working with the old driver and this causes some issues.

cliffyfromboro wrote:If I re-image an sd card and start a fresh, do you have any ideas about the ps3 controller?

Thanks

Check above.. I use wireless PS3 that should work fine (you need to plug it in once for pairing).PPSSPP and retroarch based emulation should work fine.reicast (Dreamcast) should also work as I added automated controller support for PS3.

Others will probably not work (Saturn, Jaguar, Hatari, etc.) these will require manual configuration of the controller.

cliffyfromboro wrote:EDIT: COuld I possibly just downgrade the kernel or would that be a pain?

It's possible to downgrade, but you would have to fix the boot.ini manually as 3.10 only has exynos5422-odroidxu3.dtb while 4.14 uses different dtb files for XU3, XU3-Lite and XU4.You have to manually revert the boot.ini to only use exynos5422-odroidxu3.dtb again.

This then gives me a functioning PS3 controller in emulationstation which is detected as an XBOX 360 Controller. Initial controller setup breezes through with each button press detected as it should be.

I just need to figure out how to have the last command run at each boot and i'll be good to go.

EDIT: Well, I don't seem to get any input during emulation. Did input bind using RetroArch frontend and everything worked fine. Started emulationstation again and launched a game but now get no input for the game. Even the yellow text pops up saying XBOX 360 Controller configured.

retroarch uses auto configuration depending on the controller that it finds.. xboxdrv is probably not very good to use here as it totally messes with the ID the controller sends.If PS3 is working correctly it works within retroarch without any modification, as the button layout for PS3 controller is already stored within retroarch.

meveric wrote:retroarch uses auto configuration depending on the controller that it finds.. xboxdrv is probably not very good to use here as it totally messes with the ID the controller sends.If PS3 is working correctly it works within retroarch without any modification, as the button layout for PS3 controller is already stored within retroarch.

Ah, so I just need to figure out how to get the PS3 controller working properly then. I wonder, is there anything I need to install alongside sixad. When I had Raspberry Pi, I would press the PS button and the controller would rumble and the lights would flash sequentially and then the Player 1 light would light on its own. On OGST with sixad installed, all the lights stay lit after flashing. Could this indicate that it not being assigned to anything?

I know it was working in the past (same as you describe, you hit the PS button, it rumbles and it was working), but since I have issues with it as well, I will try and updating the driver tomorrow and see if that can solve it.