Enough with the 4IFIR. It's off-topic if it isn't about sys-clk.
See if you have everything needed:"sys-clk does not seem to be running, please check that it is correctly installed and enabled"
How do i fix this?
See if you have everything needed:
Though now that video is a bit outdated since you can use OC suite out-of-the-box for Erista in case you have a Erista and I don't think you need to add any line to hekate settings for their latest .KIP, atmosphere should load it automatically and just work, you also don't use the sys-clk he have listed cause OC Suite has it all and fully working now.
Resuming what you need is:
- Tesla Menu;
- nx-ovlloader;
- SaltyNX 0.4.0a hotfix;
- Status monitor;
- NX-FPS;
- OC Suite and OC suite .KIP (both downloads are on their github, don't use the loader.kip from the video, by default with latest OC suite on Erista you will get 1862mhz on the memories instead of the video ".kip" 1996mhz as it seem that frequency might not work for all Eristas).
I did not changed the paste. I dont want to overclock, just use dock clocks or underclock.The video has all links listed.
If you didn't change thermal paste don't go nuts with the OC, but for example you can at least use docked clocks fine and increase a bit on the CPU while having better memory frequency too and if you get any or many crashes set the memories to 1600mhz in the overlay which is the max stock while docked and test again...
Again, i dont plan to overclock, just use dock, maximum clocks that nintendo allows.ps: You shouldn't really have problems, but you must understand the risks with OC, anything could go wrong at any time or reduce slightly or high the life of certain components depending on what you do and even having a lot of sysmodules in atmosphere might make it crash even if it has nothing to do with the actual OC, NOBODY IS TO BE BLAMED...
Idk whay you did wrong but it works perfectly on my erista switch and also with the new update the temperature are not going high when OC, max. temp I got was 45C with max OC. Maybe you should read the instructions before touching anything.Well, this is what i got after using Cooler3D's BS.
And some random crashes on a CPU intensive game.
Tried it just for the lols, and turns out it's a lolz itself
My case is... I can't use the dock without disable 4IFIR, if the app is active when I put the console on the dock, crash atmosphere and reboot in to Hekate.Idk whay you did wrong but it works perfectly on my erista switch and also with the new update the temperature are not going high when OC, max. temp I got was 45C with max OC. Maybe you should read the instructions before touching anything.
Idk whay you did wrong but it works perfectly on my erista switch and also with the new update the temperature are not going high when OC, max. temp I got was 45C with max OC. Maybe you should read the instructions before touching anything.
I just tested the mod...Idk whay you did wrong but it works perfectly on my erista switch and also with the new update the temperature are not going high when OC, max. temp I got was 45C with max OC. Maybe you should read the instructions before touching anything.
Oh, that's exactly it. Is it still a big problem to turn it on on my main mSD?@guilty6669 The reason why you are getting such better USB speed performance is because that mod enabled USB 3.0 support in atmosphere system.setting.ini which is built into it by default. You can just add that line into the system_setting.ini in stock, unmodified atmosphere to get the USB speed boost. The only reason why it's disabled is because it messes with wirelesses connections and signals.
Do you have ram overclocking enabled by chance"sys-clk does not seem to be running, please check that it is correctly installed and enabled"
How do i fix this?
Higher RAM frequencies above 1600 have a chance of auto-corrupting the emuNAND on boot and also during games. The higher and higher the clockspeed the higher the risk. There's a huge chance of corruption at this clockspeed because of how high it is and I bet there isn't a warning either that this is extra dangerous, not to mention how this is likely overvolted up the ass which is not good for the longevity of the RAM.2400MHz RAM OC has been deployed. Compatible with all RAM vendors.
More info and link to download:
t.me/kefir_switch/48074/60445
The voltages are almost stock (slightly higher) and the timings are short, the performance benefits are huge, and it works on most of the Mariko consoles, no corruptionsHigher RAM frequencies above 1600 have a chance of auto-corrupting the emuNAND on boot and also during games. The higher and higher the clockspeed the higher the risk. There's a huge chance of corruption at this clockspeed because of how high it is and I bet there isn't a warning either that this is extra dangerous, not to mention how this is likely overvolted up the ass which is not good for the longevity of the RAM.
I believe you about the performance increases though I know of someone in the 60FPS Discord this has crashed which isn't surprising.The voltages are almost stock (slightly higher) and the timings are short, the performance benefits are huge, and it works on most of the Mariko consoles, no corruptions
And what if I told you than NO actual cases of FS corruption were found during testing? Remember, 4IFIR uses lots of custom optimizations and even a custom build of Hekate called 4ekateI believe you about the performance increases though I know of someone in the 60FPS Discord this has crashed which isn't surprising.
View attachment 352197
There's a good reason why the project whose code you are using says to always make a backup before enabling RAM OC because it can cause corruption. Don't lie and say there's no chance of corruptions.
Also you really should talk about this in the 4IFIR thread.
ffs2400MHz RAM OC has been deployed. Compatible with all RAM vendors.
More info and link to download:
t.me/kefir_switch/48074/60445
@linuxares you must add kefir to this nowEnough with the 4IFIR. It's off-topic if it isn't about sys-clk.
and it works on most of the Mariko consoles
So "compatible" doesn't mean "working effectively" I guess.Compatible with all RAM vendors.
Compatible means working effectively on Samsung, Hynix and Micron RAM with good timings, and only 700 mv voltage, on some good RAM chips, voltage can be dropped lower than 600 mvffs
@linuxares you must add kefir to this now
Post automatically merged:
So "compatible" doesn't mean "working effectively" I guess.
700mv minor overvoltCompatible means working effectively on Samsung, Hynix and Micron RAM with good timings, and only 700 mv voltage, on some good RAM chips, voltage can be dropped lower than 600 mv
The voltages are almost stock (slightly higher) and the timings are short, the performance benefits are huge, and it works on most of the Mariko consoles, no corruptions