@mitu said in RPi overclock question!: The current stable kernel/firmware limits the GPU overclocking. I think a new firmware is necessary to be able to overclock the GPU again - there was a forum topic a few days ago with details. Why are you overclocking your PI ? @mitu I'm overclocking to increase dreamcast and N64 performances. I noticed that with that OC values my pi stays under 70 Celsius degrees and dreamcast games run very well. I hope to gain some frame overclocking GPU as well but from what I understood it's not so affecting.

@elysse77 said in Do you need a GPU for retropie?: or will the integrated graphics of the 6600k be sufficient? Main issue you might encounter is a lack of proper support for the integrated gpu.

I know this topic is pretty old but I just had this happen to me. It happened because of a conflict in RetroPie auto start. I had manually entered a command line to auto start and then later chose the auto start option in RetroPie setup. Seems the two didn’t work well together. I resolved it by getting back to RetroPie setup in command line and deleted the auto start line. I’m definitely a noob so I apologize if my terminology is wrong. But I’m learning. Hope this helps someone else.

My personal settings are (with a little heat sink on the CPU and RAM: arm_freq=1500 arm_freq_min=450 gpu_freq=530 gpu_freq_min=200 core_freq=525 core_freq_min=200 sdram_freq=533 sdram_freq_min=200 over_voltage=2 over_voltage_min=-2 over_voltage_sdram=1 temp_soft_limit=70 The undervolting and lower clocks are done to lower heat during passive moments; which allows for longer boost frequencies. As soon as the heatsink is saturated (70C), the CPU throttles down to 1,2Ghz; and this is to stall this event as long as possible. Besides, there's no real noticeable difference between arm idle frequency of 450Mhz or the stock 600Mhz.

Right, got it! Thanks for replying. :-) I've set mine to: core_freq=565 v3d_freq=525 I'd previously set gpu_freq=525 and also v3d_freq=525 on this Pi3 and this was running fine with no issues or crashes. I'd considered it as good as it gets tbh. I'll continue to use the new settings above and see how it goes. No crashes so far but only had an hour on it (N64 using lr-mupen64plus as this performs better for me nowadays) thus far. See how we go. :-)

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.

Alright, thank you both for your responses. I'm going to keep looking and I will try to make it work. I'll post back if I found anything.

Okey I found the solution: https://steamcommunity.com/discussions/forum/11/558756256090837817/ By holding the menu button I could disable the scaling mode, why samsung couldn't build a menu function for that....

What kind of hardware acceleration are you talking about exactly ? What you need exactly ? There are different kinds. Yes you can enable the OpenGL open-source driver, and chromium will say that GPU acceleration is active, but from my tests, there are no benefits of running Chromium with the OpenGL open-source driver unless you need WebGL, for the contrary, you will loose video hardware acceleration for example. If there is a way to use OpenGL on RetroPie, short awnser is no. At least not an easy way, and even if you could make some emulators work, it would be worse using de open-source driver.