D
You need to recalculate the loaderpatches for loader.kip and add them to sd/bootloader/patches.ini,Whenever you recompile AMS loader.kip, the loaderpatches are changed, hope this helps you https://gbatemp.net/threads/info-on-sha-256-hashes-on-fs-patches.581550/page-7 #post-9358107
You may need to recompile sys-clk to add 1996mhz of ramNot quite sure if that can be used on an already extracted loader.kip, but I set my poor 1gb raspberry pi on a mission to build atmosphere from scratch as my pc refused to do so without errors every bloody second (virtual machine or regular install). Lucky for me it built just fine on the pi, took an awful long time but I finally got my fusee-secondary built, ran it through that program and got my recalculated loader patch. So thank you so much for the recommendation, I'd have never even thought about that myself.
Out of curiosity is 1996Mhz easily achieveable on Erista? It seems like many people can manage it, but when I tried it I just got a black screen. I thought maybe it was because I didn't change the voltage so I change the line '#define EMC_OVERVOLT 0' to #define EMC_OVERVOLT 1' in the 'ldr_pcv_patch' as it already has the voltage as 1.2v so I figured all I had to do was change the overvolt line, does that enable the overvolt or not?
Because with 1996Mhz I get a black screen through direct atmosphere, but using hekate (with minerva capping it to 1862Mhz) it boots with a 1862Mhz clock so does that mean my ram can't handle a higher clock, or did I just not actually overvolt like I thought I did? My chips are Samsung btw.
But again thanks so much to everyone for helping me with this, even if I can't get 1996Mhz I can still run everything perfectly at 1862Mhz now.
You may need to recompile sys-clk to add 1996mhz of ram
check the RetroNX discord and search for "7z", there should be a link from ZachyCatGames for a clk-test homebrew app, compile that and you will be able to read your voltages in HOS.I think maybe I just have a bad binned samsung. I'm assumung that I'm actually overvolting properly going to a max of 1.25v in both atmosphere and hekate, but I don't know of any way to actually read the voltages from the switch itself software wise to check.
So it could be that the method I mentioned in my last comment isn't actually enabling the overvolt properly, or I just have chips that can't handle the higher clocks. Since anything above 1886Mhz causes black screen on boot, so only thing could be I'm not overvolting properly or my chips can't go above 1886Mhz, at least not without a voltage higher than 1.25 which I've been told is the safe limit for erista.
(knowing me I'm probably just fucking up the overvolt though tbf to my poor little samsung ram)
check the RetroNX discord and search for "7z", there should be a link from ZachyCatGames for a clk-test homebrew app, compile that and you will be able to read your voltages in HOS.
So someone has a sys-clk made with a pulled GPU cap 460 in a handheld, 768 without a charger?
Can't find the forks? Just go to the sys-clk github repo and click the button with text "41" (currently 41 forks) on it next to the "Fork" button.Sorry but I can't find it anywhere :-/ On github too. I have Mariko model, so I dont scare.
that shouldn't be happening, what is status monitor reporting?Is this normal? Doesn't matter what mod file I create for the ram, it always reports 1331.2mhz.
I do, however notice that MK11 has basically eliminated all slowdown in the opening scenes...
Is this normal? Doesn't matter what mod file I create for the ram, it always reports 1331.2mhz.
I do, however notice that MK11 has basically eliminated all slowdown in the opening scenes...
I am using the guide in the link below(damn, can't post links). Is it possible, because I had regular sys-clk installed before, that there is a conflict?If you choose MEM = 1600 in sys-clk, use for example Status Monitor to show the "real" frequency from the applied patch (standard sys-clk will still keep showing MEM = 1600). If it keeps reporting 1331 although you picked 1600 then you have something seriously wrong.
I am not familiar with that OC Suite so can’t help you, sorry buddy. I have an Erista unit so I don’t care about CPU/GPU overclocking so this separate ram patch is perfectly fine for me.I am using the guide in the link below(damn, can't post links). Is it possible, because I had regular sys-clk installed before, that there is a conflict?
/KazushiMe/Switch-OC-Suite
I am not familiar with that OC Suite so can’t help you, sorry buddy. I have an Erista unit so I don’t care about CPU/GPU overclocking so this separate ram patch is perfectly fine for me.
You need to recompile sys_clk, but once you choose the RAM frequency you need, you won't be able to choose another frequency (lower or higher), which is permanent, instead of sys_clk, you need to take the unknown risk of too high a voltage on the switchIs this normal? Doesn't matter what mod file I create for the ram, it always reports 1331.2mhz.
I do, however notice that MK11 has basically eliminated all slowdown in the opening scenes...
It just needs to supply enough power. For example my Dell Laptop charger (USB-C) qualifies as an Official Charger.Kind of off topic questions, how does the Switch knows its been connected to an official charger? Is it because of the wattage? Or some firmware stuff?
Can you reach the "Official charger" clocks with other kind of chargers?