Switch-OC-Suite

[jelbo]

U updated from AMS 1.5.4 to 1.5.5 and Switch-OC-Suite from 1.7.0 to 1.8.2, on my Mariko switch. My MEM speed doesn't go to 1862MHz anymore and is stuck on 1600MHz. What did I do wrong and what can I do to fix it?

 

[meha]

Is it safe to go online with my original cartridge of Pokemon Scarlet, when overclocking my switch using the switch oc suite?

Or are there any positive or negative experiences with that?

if you are asking if overclocking results ban: answer is no.
but oc can corrupt your nand, so backup your sysnand before using oc in sysnand

Post automatically merged: Sep 16, 2023

U updated from AMS 1.5.4 to 1.5.5 and Switch-OC-Suite from 1.7.0 to 1.8.2, on my Mariko switch. My MEM speed doesn't go to 1862MHz anymore and is stuck on 1600MHz. What did I do wrong and what can I do to fix it?

your hekate_ipl.ini file got overwritten from updating

 

[Nakamichi]

I have a spare modded oled board here and wanted to fiddle around with OC.
How exactly do i unlock all the higher, unsafe clockrates+voltages etc in oc suite?

 

[meha]

I have a spare modded oled board here and wanted to fiddle around with OC.
How exactly do i unlock all the higher, unsafe clockrates+voltages etc in oc suite?

for unsafe frequencies, put "allow_unsafe_freq=1" in sys-clk-oc config file
for voltages, it already allows unsafe emc voltages (above 1175mV, up to 1250mV)

 

[jelbo]

It's a good practice leave the loader.kip path like this

kip1=atmosphere/kips/*

That way it will only load the loader.kip if present, and won't crash atmosphere in case it can't find the file or it doesn't exist. It's also useful as it loads all the .kip present in the folder (in case you have other .kip).

if you are asking if overclocking results ban: answer is no.
but oc can corrupt your nand, so backup your sysnand before using oc in sysnand

Post automatically merged: Sep 16, 2023

your hekate_ipl.ini file got overwritten from updating

/edit: it works; see below.

It keeps being stuck on 1600MHz for some reason. My /bootloader/hekate_ipl.ini file became default indeed, but has the [CFW (emuMMC)] kip1 entry as cucholix recommends (see first quote); kip1=atmosphere/kips/*. I changed it to kip1=atmosphere/kips/loader.kip again, but to no effect, also not after rebooting.

My loader.kip is the latest one from GitHub and has SHA-1 checksum e84cdc2e84799bc075469fad7631e54c96b793fe.

I have these logs, hoping they're of any help:

[2023-09-17 16:56:40.015] === sys-clk-OC 1.8.2 === [2023-09-17 16:56:47.270] Parsed cust config from "/atmosphere/kips/loader.kip" [2023-09-17 16:56:48.229] Ready [2023-09-17 16:56:48.248] [mgr] Profile change: Official Charger [2023-09-17 16:56:48.264] [cfg] Reading /config/sys-clk-oc/config.ini [2023-09-17 16:56:48.282] [mgr] sys-clk-OC status: enabled <...> [2023-09-17 16:56:54.997] [mgr] TitleID change: 0100F2C0115B6000 [2023-09-17 16:56:55.030] [mgr] CPU clock change: 1785.0 MHz [2023-09-17 16:56:55.054] [mgr] GPU clock change: 76.8 MHz [2023-09-17 16:56:55.088] [mgr] Memory clock set : 1862.4 MHz [B][2023-09-17 16:56:55.111] [mgr] Cannot set Memory clock to 1862.4 MHz[/B]

My /config/sys-clk-oc/config.ini is like this:

[values] sync_reversenx_mode=0 [0100F2C0115B6000] ; The Legend of Zelda - Tears of the Kingdom handheld_mem=1862 handheld_charging_mem=1862 handheld_charging_usb_mem=1862 handheld_charging_official_mem=1862 docked_mem=1862

/edit: it works: I had to fully reboot my console, not boot a payload and then emuMMC again from HOS. Back to TotK I go

 

[meha]

Switch OC Suite 1.8.3 is out

[Mariko]
cpu uv is fixed and now uses correct voltage, allowing higher clocks without performance drop
min cpu volt is patched to 600mV for cpu uv

[Erista]

[Common]
mhz(cpu frequency measurement utility) version 1.1 is now included

 

[TamarindoJuice]

Switch OC Suite 1.8.3 is out

[Mariko]
cpu uv is fixed and now uses correct voltage, allowing higher clocks without performance drop
min cpu volt is patched to 600mV for cpu uv

[Erista]

[Common]
mhz(cpu frequency measurement utility) version 1.1 is now included

Thanks for the update!
The online loader configurator is ready for the new voltages?

 

[meha]

Thanks for the update!
The online loader configurator is ready for the new voltages?

online configurator is always for the latest version.
it might work for older versions if not much is changed, but i don't recommend because it might allow illegal values

 

[[Truth]]

Hi @meha , I´m still using your RAM timings for 1.7.0:
https://github.com/hanai3Bi/Switch-OC-Suite/discussions/30#discussion-5372573
Can I still use them on 1.8.3 or did something significant change?

 

[Gumistret]

Hi @meha , I´m still using your RAM timings for 1.7.0:
https://github.com/hanai3Bi/Switch-OC-Suite/discussions/30#discussion-5372573
Can I still use them on 1.8.3 or did something significant change?

You can use your old timing

 

[Medel87]

You can use your old timing

From 1.7 to 1.8 timings change a little, maybe it could not work, and must be adjusted

 

[jelbo]

Sigh, for some reason my MEM OC on Erista stopped working again. It maxes out on 1600MHz. Version 1.8.3, I had it to work with that version. Booting emuMMC from Hekate. 6.0.6, HOS: 16.1.0, AMS: 1.5.5.

[2023-09-19 16:05:54.016] === sys-clk-OC 1.8.3 ===
[2023-09-19 16:06:00.858] Parsed cust config from "/atmosphere/kips/loader.kip"
[2023-09-19 16:06:01.759] Ready
[2023-09-19 16:06:01.773] [cfg] Reading /config/sys-clk-oc/config.ini
[2023-09-19 16:06:01.793] [mgr] sys-clk-OC status: enabled
[2023-09-19 16:06:01.804] [mgr] TitleID change: 0100000000001000
[2023-09-19 16:06:01.816] [mgr] CPU clock change: 1020.0 MHz
[2023-09-19 16:06:01.831] [mgr] GPU clock change: 307.2 MHz
[2023-09-19 16:06:01.844] [mgr] Memory clock change: 1331.2 MHz
[2023-09-19 16:06:02.367] [mgr] CPU clock change: 1785.0 MHz
[2023-09-19 16:06:02.378] [mgr] GPU clock change: 76.8 MHz
[2023-09-19 16:06:02.894] [mgr] CPU clock change: 1020.0 MHz
[2023-09-19 16:06:02.905] [mgr] GPU clock change: 307.2 MHz
[2023-09-19 16:06:13.780] [mgr] TitleID change: 0100F2C0115B6000
[2023-09-19 16:06:13.812] [mgr] CPU clock change: 1785.0 MHz
[2023-09-19 16:06:13.834] [mgr] GPU clock change: 76.8 MHz
[2023-09-19 16:06:13.861] [mgr] Memory clock set : 1862.4 MHz
[2023-09-19 16:06:13.888] [mgr] Cannot set Memory clock to 1862.4 MHz
[2023-09-19 16:06:21.284] [mgr] CPU clock change: 1020.0 MHz
[2023-09-19 16:06:21.334] [mgr] GPU clock change: 460.8 MHz
[2023-09-19 16:06:21.371] [mgr] Memory clock change: 1331.2 MHz
[2023-09-19 16:06:21.395] [mgr] Memory clock set : 1862.4 MHz
[2023-09-19 16:06:21.542] [mgr] Cannot set Memory clock to 1862.4 MHz
[2023-09-19 16:06:22.736] [mgr] CPU clock change: 1785.0 MHz
[2023-09-19 16:06:22.748] [mgr] GPU clock change: 76.8 MHz
[2023-09-19 16:06:22.766] [mgr] Memory clock set : 1862.4 MHz
[2023-09-19 16:06:22.782] [mgr] Cannot set Memory clock to 1862.4 MHz
[2023-09-19 16:06:26.839] [mgr] CPU clock change: 1020.0 MHz
[2023-09-19 16:06:26.859] [mgr] Memory clock set : 1862.4 MHz
[2023-09-19 16:06:26.874] [mgr] Cannot set Memory clock to 1862.4 MHz
[2023-09-19 16:06:27.414] [mgr] CPU clock change: 1785.0 MHz
[2023-09-19 16:06:27.442] [mgr] Memory clock set : 1862.4 MHz
[2023-09-19 16:06:27.459] [mgr] Cannot set Memory clock to 1862.4 MHz
[2023-09-19 16:06:31.519] [mgr] CPU clock change: 1020.0 MHz
[2023-09-19 16:06:31.530] [mgr] GPU clock change: 460.8 MHz
[2023-09-19 16:06:31.539] [mgr] Memory clock change: 1331.2 MHz
[2023-09-19 16:06:31.552] [mgr] Memory clock set : 1862.4 MHz
[2023-09-19 16:06:31.563] [mgr] Cannot set Memory clock to 1862.4 MHz

I have:
/atmosphere/contents/00FF0000636C6BFF/exefs.nsp /atmosphere/contents/00FF0000636C6BFF/flags/boot2.flag /atmosphere/kips/loader.kip /bootloader/hekate_ipl.ini /config/sys-clk-oc/config.ini /config/sys-clk-oc/log.flag /switch/.overlays/sys-clk-overlay.ovl

My hekate_ipl.ini:

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

[CFW (sysMMC)]
kip1=atmosphere/kips/loader.kip
emummc_force_disable=1
fss0=atmosphere/package3
icon=bootloader/res/icon_payload.bmp

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

[Stock]
emummc_force_disable=1
fss0=atmosphere/package3
icon=bootloader/res/icon_switch.bmp
stock=1

[Fusee]
icon=bootloader/res/icon_payload.bmp
payload=bootloader/payloads/fusee.bin

{}

Any help will be greatly appreciated.

Post automatically merged: Sep 19, 2023

I figured it out! I put the "kip1=atmosphere/kips/loader.kip" line directly underneath "kip1patch=nosigchk" and above "emummcforce=1". Not sure why the instructions fail to specify *where* exactly the new line needs to go since it's obviously crucial. Hope this helps anyone having the same issue. Take care. <3

OK for everyone who might still be struggling on their arista switch with 1862 not actually applying I fixed it by placing a copy of my hekate_ipl.ini file in both the bootloader root folder AND the bootloader/ini folder which also had a copy of hekate_ini.ipl in it. replacing it with a copy of the one in the root seems to have resolved my issue even though the cys-clk-oc logs said it was loading the kip just fine.

I also tried the two above suggestions, to no avail.

Did you ever get this to work, @elptarkus?

 

[TamarindoJuice]

Noticed that RAM overclock is not working here too. Hekate_ipl.ini edited and all.

 

[jelbo]

I got it to work, hopefully it will stick now. It could be working randomly The differences in my now working /bootloader/hekate_ipl.ini are:

autohosoff=0

and

[CFW (emuMMC)]
fss0=atmosphere/package3
cal0blank=0
emummcforce=1
kip1=atmosphere/kips/loader.kip
icon=bootloader/res/icon_payload.bmp

instead of

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

cal0blank=0 is my own choice and likely not related at all. The fix must have been the order of config entries. The kip entry below the fss0 and emummcforce entries. My full hekate_ipl.ini can be seen here.

Curious to see if this helps others as well!

 

[TamarindoJuice]

I got it to work, hopefully it will stick now. It could be working randomly The differences in my now working /bootloader/hekate_ipl.ini are:

autohosoff=0

and

[CFW (emuMMC)]
fss0=atmosphere/package3
cal0blank=0
emummcforce=1
kip1=atmosphere/kips/loader.kip
icon=bootloader/res/icon_payload.bmp

instead of

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

cal0blank=0 is my own choice and likely not related at all. The fix must have been the order of config entries. The kip entry below the fss0 and emummcforce entries. My full hekate_ipl.ini can be seen here.

Curious to see if this helps others as well!

Worked here too, thanks for the tip!

 

[BasedKiliK]

What's the consensus of overclocking, and only overclocking, on stock? With nothing illegal otherwise installed, does using tools like switch-oc-suite run the risk of a ban? For example, I'd like to improve frametimes and stabilize performance a bit when playing Monster Hunter Rise online with friends.

I ask because, once again, the overall consensus elsewhere seems mixed.

 

[linuxares]

switch-oc-suite run the risk of a ban?

Using something that isn't Nintendo sanctioned always involves a risk of getting banned.

 

[BasedKiliK]

Using something that isn't Nintendo sanctioned always involves a risk of getting banned.

I'm well aware. I've done stuff like this when extracting/injecting save files or using certain mods, with zero issues (but I was also offline). In my experience, and for others, using homebrew does not and has yet to facilitate a ban, and only certain things seem to lead to it. Overclocking on stock, however, is uncharted territory for me.

 

[meha]

I'm well aware. I've done stuff like this when extracting/injecting save files or using certain mods, with zero issues (but I was also offline). In my experience, and for others, using homebrew does not and has yet to facilitate a ban, and only certain things seem to lead to it. Overclocking on stock, however, is uncharted territory for me.

since nintendo doesnt ban Atmosphere, it also means overclocking is safe
Since it does not modify data or save

 

[AlicatFit]

Can confirm to anyone that's new and worried, that overclock is safe.If you plan on using it on your sysnand be sure you don't have pirated games on it and used it on your purchased ones you can do so without a problem.Also do not use cheats along with overclock on sysnand online and then blame the overclock it's you using the cheats and mods online that gets you banned.Using frame rate modifiers will also get you in trouble online so again don't blame the overclock, I've been using overclock online and on my console for a year now with 0 issues.