Switch-OC-Suite

[Volkaru]

Even then another thing I didn't mention is binning plays a huge part on marikos
View attachment 370410
(This is from a really good bin)
Mariko is better for overclocking in the sense that things like 1.9/921 won't go over the limit, but higher pushes the regulators pretty hard. Its not even the board PMIC with Mariko, its the cpu/gpu regulators that are the limiting factor.

Is there a way to easily test this myself to see where my switch falls? Or does it require using a multimeter?

 

[meha]

Update (v1.3)

-update for ams 1.5.3
-advanced config: gpu undervolt for mariko
-now you can update oc-suite via AIO

 

[MSco]

-now you can update oc-suite via AIO

OMG, this is awesome! Thank you very much!

I was asking for a procedure to update switch-oc via aio updater in the aio updater thread. Did you add this feature in response to my request?

 

[meha]

OMG, this is awesome! Thank you very much!

I was asking for a procedure to update switch-oc via aio updater in the aio updater thread. Did you add this feature in response to my request?

yeah I saw your post. but hekate_ipl.ini file is not included (on purpose), so this is only for updating in same AMS version.
I could add hekate ipl as optional download in AIO, but I'm still figuring out what's best

 

[MSco]

yeah I saw your post. but hekate_ipl.ini file is not included (on purpose), so this is only for updating in same AMS version.
I could add hekate ipl as optional download in AIO, but I'm still figuring out what's best

Well yes, there is one problem: You have to decide in aio updater, if you would like to update atmosphere or switch-oc, and after each update, the aio updater reboots to hekate. And you cannot update atmosphere and switch-oc at once.

The normal case is the following: I have atm 1.5.2 and switch-oc 1.5.2, in my hekate_ipl.ini is an entry kip=atmosphere/loader.kip. Now, I have to choose, what to update first. When I now update only atmosphere, hekate will try to boot atmosphere 1.5.3 with the 1.5.2 loader.kip (which can fail). In the other case, when I choose updating switch-oc first, hekate will try to boot atmosphere 1.5.2 with the 1.5.3 loader.kip (which can also fail).

A solution for this would be to update atmosphere and switch-oc, without rebooting to hekate between the two steps. Or aioupdater may not reboot after updating switch-oc. Maybe the custom_pack.json has to be modified for this?

Edit: @meha
I think, you have to declare it as "misc", not as "ams" in custom_packs.json. Then aioupdater should be able to update switch-oc without rebooting to hekate.

 

[meha]

@MSco

it's because currently OC-Suite's entry value is "ams", so AIO sees it as updating Atmosphere.
I'll change it to misc, so you can install both AMS, and OC-Suite at once -> changed.

 

[WobbleTheHutt]

Update (v1.3)

-update for ams 1.5.3
-advanced config: gpu undervolt for mariko
-now you can update oc-suite via AIO

Thank you so much! Just in time for my TotK cart tomorrow!

Can we get details on the gpu undervolt and what it does exactly?

 

[meha]

Thank you so much! Just in time for my TotK cart tomorrow!

Can we get details on the gpu undervolt and what it does exactly?

if enabled, it decreases gpu voltage a little bit, so less power consumption

 

[Mike_77712]

Dummy here, is this 4ifir? I'm currently using sys clk but worried I might break something if I combine the two

 

[linuxares]

Dummy here, is this 4ifir? I'm currently using sys clk but worried I might break something if I combine the two

No, this is OC-Suite.

 

[SkyDark719]

if enabled, it decreases gpu voltage a little bit, so less power consumption

Thanks for continue updating this tool, I found that I need to configure the kip to use "GPU Undervolt" on Mariko, I'll use that.

 

[WobbleTheHutt]

if enabled, it decreases gpu voltage a little bit, so less power consumption

Nice! Was wondeing exactly how much and how to calculate my amperage draw based on my speedo tables. If it's a good enough bin I can go faster!

 

[MSco]

No, this is OC-Suite.

@meha
Should I remove all sys-clk directories and sys-clk itself, when using Switch-OC? or does switch-oc automatically disable sys-clk?

 

[meha]

@meha
Should I remove all sys-clk directories and sys-clk itself, when using Switch-OC? or does switch-oc automatically disable sys-clk?

OC-Suite overwrites sys-clk sysmodules, so you just copy everything in SdOut
and although sys-clk config is compatible, the config directory different (/config/sys-clk-oc)