CPU or GPU overclocking possible?


Thnx mate really appreciate!


I tried the Odroid_C2_u-boot from CoreELEC-S905.arm-9.0-nightly_20190131.tar and the max frequency is still 1536. Reverting back to the uboot from Libreelec allows 1752 again. I’ve been using these commands to write uboot onto the emmc:

dd if=Odroid_C2_u-boot of=/dev/mmcblk0 conv=fsync bs=1 count=112 status=none
dd if=Odroid_C2_u-boot of=/dev/mmcblk0 conv=fsync bs=512 skip=1 seek=1 status=none


@zaphod24 as I said in my previous message, you will have to wait for the next nightly image.

You also have to add max_freq='1752' to your config.ini.


Apologies, I thought the next nightly was tonight(time zone differences maybe?)

I’ll look at the 2/1 build.


Maybe it is, I’m not sure, it’s out of my hands nightlies, but I know that the changes definitely work because one of our developers tested them.

Make sure you have the above line in your config.ini.


It should already be included in 20190131.
Maybe you could try the config.ini change @adamg suggested.


I believe my config.ini is correct, here is /proc/cmdline:

console=ttyS0,115200 BOOT_IMAGE=kernel.img boot=UUID=0806-3045 disk=UUID=81edefdb-c665-4570-9129-23d8610c699e no_console_suspend logo=osd1,loaded,0x3f800000,1080p60hz vout=1080p60hz,enable vout_mode=hdmi hdmimode=1080p60hz cvbsmode=nocvbs mac=00:1e:06:33:dd:90 consoleblank=0 max_freq=1752 maxcpus=4 hdmitx=cec3f quiet console=tty0 systemd.show_status=auto ssh

I used the dd commands mentioned earlier with the Odroid_C2_u-boot in nightly CoreELEC-S905.arm-9.0-nightly_20190131.tar. The same dd commands work with an older u-boot from the latest Libreelec beta.


@zaphod24 another user already reported ocing works with latest nightly, link


Yeah, I saw that. I’ll give the nightly a shot tonight, but I was hoping to stay on 8.99.1 and just replace the uboot for now.


Well I’m not sure what the updater does different than what I did manually with dd and the Odroid uboot file from the latest nightly, but sure enough updating to it allows a cpu overclock again.

Sorry for the snipe hunt.