@mitu As the 16.04 still has support until 2021 I will still keep with it a little bit and continue reading the comments, if in a while there is nothing very negative about the 18.04 I upgrade. Even because this pc is an old Dual-Core Celeron that I use as a retro console and to watch some videos.

Performance-wise, if your Waveshare 3.2" is able to reach 73.7 Mhz or higher, you will get a solid 60fps on the display. In such case, you can try enabling NO_INTERLACING in config.h. SPI bus speeds 66Mhz and higher will also in practice run at 60fps. 40Mhz-60MHz generally resort to interlacing every now and then, and < 40 MHz will typically run fully interlaced (e.g. ILI9486 based displays)

This video

is running a Raspberry Pi CM3 with a Waveshare 3.2" with SPI bus at 66MHz.

gpu is slow and only supports GLES/open gl 2. open gl 2.1 isn’t different from gles in terms of featureset, and that’s what matters.

cpu/core use doesn’t matter because cpu is barely used with pi3 plus mupen64plus (thanks to the arm dynarec).

mupen64plus-gliden64 is fairly well optimised for pi at this point, in my view. ultimately the gpu’s lack of features doom it.

system bus speed is always probably a bottleneck but no amount of speed will get over the GLES/gl limitations.

@paulmartin Try looking into the options described in https://retropie.org.uk/forum/topic/672/a-stop-job-is-running-for-lsb-controlblockservice-init-script/18, either boot the Pi in 'safe mode' or mount the card from another Linux system and delete the powerblock driver start script to stop the reboot cycle.

I saw someone using sc-controller in a youtube video so you can try that

https://github.com/kozec/sc-controller

@darksavior said in You're killing Smalls... gamecondriver fails install:

@javelina1 Did you get it working without updating retropie? If you didn't, then maybe you have a wiring or config problem. Waiting for an official fix won't fix your problem. I also don't see why you changed the default gpu mem...

It did recognize my controller when I used the 4.4 image. But after all the installs, nothing after that. I must have screwed up my install process.

Regardless, I'm working with an Xbox 360 controller now. I'll await an update down the road for the gamecondriver and the 4.9.xx Kernel.

As to the memory allocation that is a side bar. Sorry to have confused you. I set my GPU to 128MB just for general purposes. It has nothing to do with the gamecondriver issue.

I'm good now, using the Xbox 360. Thanks for the help. I hope a "native" solution comes along to fix this issue.

kind regards,

-Jav

So anybody?

Is it even worth a try, to add SD in Pi3, run the script and (???) remove reboot from it... would that download the script and then install in at the next boot?

@c_death Glad you got it figured out. I got mine figured out as well. I had to follow the instructions here:

https://github.com/RetroPie/RetroPie-Setup/wiki/Bluetooth-Controller

Under the Keep bluetooth scanning part I had to add the line "sudo hciconfig hci0 up piscan" to sudo nano /etc/init.d/rc.local

Now it picks it back up every time it goes to sleep.

Thank you!

The fix has now been applied:

https://github.com/raspberrypi/linux/issues/1755