Switch-OC-Suite
- Thread starter meha
- Start date
- Views 136,777
- Replies 761
- Likes 32
How do you know if you are using the "Hekate-ipl bootloader"? I know that when turning on the Switch I launch Hekate then launch Atmosphere from there. Is this the "Hekate-ipl bootloader" or some other version of Hekate which I don't know about?
What matters is whether you boot with Fusee or package3. The line is needed with package3, fusee loads kips automatically.
Well, at least that's how I understand it and how it seemed to work when I tested it.
Well, at least that's how I understand it and how it seemed to work when I tested it.
I'm not sure exactly how to read this file but it looks like package3 to me
[config]
updater2p=1
{------ Atmosphere ------}
[Atmosphere FSS0 EmuMMC]
fss0=atmosphere/package3
kip1=atmosphere/kips/*
emummcforce=1
icon=bootloader/res/emu_boot.bmp
{}
[Atmosphere FSS0 SYS]
fss0=atmosphere/package3
kip1=atmosphere/kips/*
emummc_force_disable=1
icon=bootloader/res/sys_cfw_boot.bmp
{}
{-------- Stock ---------}
[Stock SYS]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/stock_boot.bmp
[config]
updater2p=1
{------ Atmosphere ------}
[Atmosphere FSS0 EmuMMC]
fss0=atmosphere/package3
kip1=atmosphere/kips/*
emummcforce=1
icon=bootloader/res/emu_boot.bmp
{}
[Atmosphere FSS0 SYS]
fss0=atmosphere/package3
kip1=atmosphere/kips/*
emummc_force_disable=1
icon=bootloader/res/sys_cfw_boot.bmp
{}
{-------- Stock ---------}
[Stock SYS]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/stock_boot.bmp
1.5.3-v1.5.1
version 1.5.1 is released
- minor dram timing adjustments
- hiopt table (GPU Undervolt 2) is fixed and now works correctly and you get much lower power draw
Last edited by meha,
Yeah, at you also have kip1=atmosphere/kips/* which should load every kip in the folder automatically, so you shouldn't need to add a separate line for the loader.
After I had updated to the latest version and the newer loader.kip file (where I only undervolted the GPU with HiOPT through the online configurator), the game I was playing (Divinity) froze on loading screen. This hasn't happened ever before with the older .kip and checked HiOPT table.
This is really weird since the gpu clock on loading screens is very low. And as far as I know, you can't really go below 610mV on mariko
Post automatically merged:
This is really weird since the gpu clock on loading screens is very low. And as far as I know, you can't really go below 610mV on mariko
Last edited by Purpeliz,
I'll give it a shot later. If it's set up incorrectly is there any chance of NAND corruption or hardware damage?
Hekate did open some new speeds in the latest release.
https://github.com/CTCaer/hekate/releases/tag/v6.0.5
I have a quick question.
I know there is 460Mhz limit for GPU in handheld mode on Erista.
But what about Mariko? Are higher frequencies for GPU available in handheld mode (not charging) on official build of Switch-OC-Suite on Mariko devices?
Thanks!
I know there is 460Mhz limit for GPU in handheld mode on Erista.
But what about Mariko? Are higher frequencies for GPU available in handheld mode (not charging) on official build of Switch-OC-Suite on Mariko devices?
Thanks!
mariko have higher limits. 1963/998 on battery. exact limits are on readme for sys-clk-oc
Does anyone know what's the limiting factor in docked gpu overclocking? Is it the total power draw? I'm wondering if i can go past the safe gpu limits if I'm keeping the cpu at stock thus potentially keeping the soc power draw lower than while running both cpu and gpu at max safe frequencies.
Last edited by landepro,
Similar threads
-
- Locked
