Switch-OC-Suite

[nguetto]

well you can check ini file again to make sure. don't just guess. it could have been replaced while updating, etc. if the line is there and still don't work, reply again and i'll be glad to help.

i check with my erista console and works fine for me

Post automatically merged: May 3, 2023

well it meant more like don't trust some dangerous software like oc-suite to be safe, not about your skills following. even Kazushime seemed to not fully understand correct way of implementing OC features, and for me, I absolutely have no idea

I am doing research, but I doubt I can correctly implement OC features. That's why I reverted all changes i made, and dropped feature to enable 2397 CPU on mariko.

Thanks Meha for pointing out the potential updating of the hekate ini ! I was able to get it to work ! Thank you for your work on this !

So for the Erista people out there with the same issue, here is what happened to me. Somehow my hekate ini file got corrupted, so eventhough the kip1 line was added it, was still not working. The corrupted hekate ini looked like this:

========
[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=64
autohosoff=0
autonogc=1
updater2p=1
bootprotect=0

{--- Stock ---}

[OFW/Stock (No CFW)]
emummc_force_disable=1
fss0=atmosphere/package3
stock=1
icon=bootloader/res/stock_boot.bmp

{------ Atmosphere ------}

[AMS emu/sysMMC (fusee)]
payload=bootloader/payloads/fusee.bin
icon=bootloader/res/boot_fusee.bmp
{}
kip1patch=nosigchk
kip1=atmosphere/kips/loader.kip

€Òý ‘3§”Ã@ ‘!¤@ù ùþ
===========


Strange characters at the end made me suspicious. So I went to grab a clean hekate ini and re-added the kip1 line again in the clean file. Then it worked. I am booting the CFW from sysnand (not that it changes much provided you add the line in both blocks like I did). Note that it was not necessary to edit or delete the minerva bso. Here is what the clean hekate ini looked like:


=========

[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=100
autohosoff=0
autonogc=1
updater2p=1
bootprotect=0

{--- Stock ---}
[OFW on Device Memory]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/stock_boot.bmp

{------ Atmosphere ------}
[CFW on MicroSD Card]
fss0=atmosphere/package3
kip1patch=nosigchk
kip1=atmosphere/kips/loader.kip
cal0blank=1
emummcforce=1
icon=bootloader/res/emummc_fss0_boot.bmp

{------ Atmosphere ------}
[CFW on Device Memory]
fss0=atmosphere/package3
kip1patch=nosigchk
kip1=atmosphere/kips/loader.kip
cal0blank=1
emummc_force_disable=1
icon=bootloader/res/sys_fss0_boot.bmp

{------ Atmosphere ------}
[Emu if Enabled - Sys if Not]
payload=bootloader/payloads/fusee.bin
icon=bootloader/res/fusee_boot.bmp

{}

============

Hope it helps someone else out there, cheers !

 

[Pacote]

Thansk nguetto

That was the issue here also

My .ini had a few garbed chars at the end so I created a new one and Voila, Mem OC working now (and as yo usaid, no need to remove minerva lib)

 

[TeleTubby666]

Does anyone know why the MEM clock changes twice after every TitleID change?

[2023-05-03 11:28:37.004] === sys-clk-OC 2023/04/24 ===
[2023-05-03 11:28:45.982] Set MEM Vdd2 volt to 1125 mV: OK
[2023-05-03 11:28:45.998] Parsed cust config from "/atmosphere/kips/loader.kip"
[2023-05-03 11:28:46.795] Ready
[2023-05-03 11:28:46.811] [mgr] Profile change: Docked
[2023-05-03 11:28:46.820] [cfg] Reading /config/sys-clk-oc/config.ini
[2023-05-03 11:28:46.856] [mgr] sys-clk-OC status: enabled
[2023-05-03 11:28:46.879] [mgr] TitleID change: 0100000000001000
[2023-05-03 11:28:46.932] [mgr] Memory clock change: 1600.0 MHz
[2023-05-03 11:28:46.943] [mgr] Memory clock set : 2131.2 MHz
[2023-05-03 11:28:48.480] [mgr] Memory clock change: 1600.0 MHz
[2023-05-03 11:28:48.493] [mgr] Memory clock set : 2131.2 MHz
[2023-05-03 11:29:27.309] [mgr] TitleID change: 0100AE00096EA000
[2023-05-03 11:29:27.844] [mgr] Memory clock change: 1600.0 MHz
[2023-05-03 11:29:27.864] [mgr] Memory clock set : 2131.2 MHz
[2023-05-03 11:29:41.570] [mgr] Memory clock change: 1600.0 MHz
[2023-05-03 11:29:41.586] [mgr] Memory clock set : 2131.2 MHz

The memory clock is globally set to 2131 MHz, no further profile is loaded.

Thank you for any help!

 

[meha]

Does anyone know why the MEM clock changes twice after every TitleID change?



The memory clock is globally set to 2131 MHz, no further profile is loaded.

Thank you for any help!

https://github.com/retronx-team/sys-clk/blob/develop/common/src/apm_profile_table.c

HOS sets clocks to perf_config the game requests. game can change perf_config several times, for example from boost mode when starting the game, to handheld 384 mode when loading is finished

 

[steverebo]

when open ovl menu and try sysclock it says "fatal error sys-clk is not running please make sure it is installed correctly and enabled, loader.kip is required to use this version of sys-clk

i floowed the instructions I dont understand what i have done wrong. Im using a switch oled with instinct v6

 

[Defaul]

Hello, i'm also having issues when trying to get to 1862. When I check by using status monitor and sysclock overlay, i'm still at 1600 My hekate files looks like so:

[config]
autoboot=0
autoboot_list=0
bootwait=0
autohosoff=0
autonogc=1
updater2p=1
backlight=100

[CFW - emuMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
kip1=atmosphere/kips/loader.kip
emummcforce=1
atmosphere=1
icon=bootloader/res/icon_payload.bmp


--
Not sure what the problem is here. I've attached a screen of my path and loader.kip being used.

 

[bbert]

Any chance to support fusee payload.

 

[Ethelbert]

Any chance to support fusee payload.

Hi, it supports fusee.
Just put everything in, don't add any extra line to hekate_ipl.ini and that's it.
I do that, chainload fusee from Hekate and it works.

 

[Pacote]

Hello, i'm also having issues when trying to get to 1862. When I check by using status monitor and sysclock overlay, i'm still at 1600 My hekate files looks like so:

[config]
autoboot=0
autoboot_list=0
bootwait=0
autohosoff=0
autonogc=1
updater2p=1
backlight=100

[CFW - emuMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
kip1=atmosphere/kips/loader.kip
emummcforce=1
atmosphere=1
icon=bootloader/res/icon_payload.bmp


--
Not sure what the problem is here. I've attached a screen of my path and loader.kip being used.

Did you created this loader with the online tool?

Also, just delete the .ini file

create a new one and just copy and paste the text just posted.

Just to be sure add the line below at the end

{}


Save, reboot and try again.

 

[Frisk_]

Works like a charm, thank you for this.

I use 1224/768/1862 in dock with an erista for totk. Seems great so far and safe.

 

[MSco]

I am on mariko console (Switch OLED) and would like to play totk with overclocked MEM higher than 1600 MHz (this shold be 1996 MHz, right?).
Which CPU and GPU is the maximum, that I can use without having a risk to damage the hardware?

And what is the temperature cap for this console? I could monitor this on Status Monitor Overlay.

 

[Rahkeesh]

Looking at the readme, there is no GPU overclock for Erista?

Is this considered unsafe or useless now? Even sys-clock let you push up to 900ish while docked/official charger.

 

[meha]

[Update]

implemented advanced configuration : gpu undervolt feature for mariko.

I have no guarantee that changing dvfs table will actually create correct voltage table, it's just for testing purposes. so don't use unless necessary.

*online configurator is compatible with older and newer version
** some consoles have problem booting so removed for now. will fix when I get back from travel. sorry for inconvenience

 

[AngryCinnabon]

Is it "okay" to use the higher clocks while in handheld mode? (iirc i was running 844 GPU, 1326 CPU and 1996 RAM) I don't want to damage my switch after having it repaired. Sorry if this is a stupid question, just trying to make sure I don't ruin my switch as fast as I did last time if at all. Basically what happened to my switch was that it wouldn't charge to 100% and would die suddenly at 60%, idk if that was because of switch oc suite or not though.

 

[meha]

Is it "okay" to use the higher clocks while in handheld mode? (iirc i was running 844 GPU, 1326 CPU and 1996 RAM) I don't want to damage my switch after having it repaired. Sorry if this is a stupid question, just trying to make sure I don't ruin my switch as fast as I did last time if at all. Basically what happened to my switch was that it wouldn't charge to 100% and would die suddenly at 60%, idk if that was because of switch oc suite or not though.

I can't say OC-Suite is safe, but if you play within 'safe' settings, it should generally be okay, but don't max out clocks if unnecessary

 

[AngryCinnabon]

I can't say OC-Suite is safe, but if you play within 'safe' settings, it should generally be okay, but don't max out clocks if unnecessary

Yeah, I never go near the max clocks, honestly all I ever do is the ram overclock and the aforementioned clocks for pokemon violet. Thanks for the response

 

[Nakamichi]

I can't say OC-Suite is safe, but if you play within 'safe' settings, it should generally be okay, but don't max out clocks if unnecessary

It doesnt have to be. The risks of overclocking should be common knowledge and just to be safe its mentioned on the github once again.

As long as everyone can make their own informed decision everyone should be able to do with their own property whatever they want.

Even if things go terribly and a switch were to actually break its not a life and death situation anyway.

For my part im incredibly thankful that you are doing this. Your efforts make the switch so much more useable for me and it increases my fun immensely. Thank you so much!

 

[Volkaru]

Wanting to jump back into this. Before I start pushing it past the base sys clk config, I do have a question about the speedo number. Searching hasn't turned up much. For a Mariko unit what is considered a good number there?
I'm a bit concerned already about my thermals.
During heavy load in TotK at 1785/921/1600 I push 45-50c, while I've heard others barely go above 35-40 with similar OCs.
My reported speedo in hekate are 1677 cpu, 1690 gpu, and 1696 SoC. Any insight on how that stacks up is appreciated, thanks!

 

[M7L7NK7]

Hope it isn't really 1690 gpu

 

[Volkaru]

Hope it isn't really 1690 gpu