Homebrew RELEASE sys-clk under/overclocking sysmodule

[RaoTheConqueror]

It's not working for me. AMS 0.10.4|E, 9.2.0. No log is written and using Tesla with Status Monitor Overlay I can see my adjustments are not applied. Also, sys-clk-Editor is saying sys-clk isn't found.

How can I troubleshoot this without starting my whole sd setup from scratch?

/edit: fixed it by moving the 00FF0000636C6BFF folder from /atmosphere/titles/ to /atmosphere/contents/, where it should be since AMS 10. Automatic migration never happened.

Moving that folder fixed my issue with sysclock not coming up also, thanks!

 

[Aurora Wright]

I compiled a build that doesn't use the time service at all (which means it doesn't have timestamps in the log), as on 10.0 the service seems to be close to the session limit (I had 2345-0038 crashes with launching homebrew from the homebrew menu with this + sys-ftpd-light which also uses the time service). Source here https://github.com/AuroraWright/sys-clk

 

[p-sam]

Hey, just pushed a small update for sys-clk, so you have less chances to fatal on homebrew due to a shortage of "time" service sessions. Have fun⏱️https://t.co/9hLqTRIMRt

— 🅿️ ＳＡＭ (@p__sam) April 18, 2020

Note: this does not remove any of the features, you'll still get the timestamps on logs and csv exports. (We need those on the official build to provide you support if you have an issue anyway)

 

[mattyxarope]

I'm not sure why, but it doesn't seem to be working with gpu overclocking. I'm playing Astral Chain in hand-held mode, latest atmosphere, latest sysclk (clean install), and sysclk editor.

I use Tesla overlay and can see that it's setting the CPU and RAM, but not the GPU.

I've set a higher gpu setting for hand-held but it won't do anything. When it's plugged in it correctly sets the clock speed, however.

 

[OrGoN3]

Is there any homebrew for updating/syncing config.ini with the sys-clk-db presets?

 

[Clydefrosch]

I'm not sure why, but it doesn't seem to be working with gpu overclocking. I'm playing Astral Chain in hand-held mode, latest atmosphere, latest sysclk (clean install), and sysclk editor.

I use Tesla overlay and can see that it's setting the CPU and RAM, but not the GPU.

I've set a higher gpu setting for hand-held but it won't do anything. When it's plugged in it correctly sets the clock speed, however.

gpu clock is capped at 460 unless you charge the system for reasons that will forever elude me (the reason is supposed hardware damage through battery strain, but i feel like i could live with eventually getting a new battery if handheld performance was better for it)
if you can code and recompile, you can change it though. but most of us mortals cant

 

[Deleted User]

gpu clock is capped at 460 unless you charge the system for reasons that will forever elude me (the reason is supposed hardware damage through battery strain, but i feel like i could live with eventually getting a new battery if handheld performance was better for it)
if you can code and recompile, you can change it though. but most of us mortals cant

I really wouldn't. The switch can't handle running the gpu at docked speeds while on battery. The switch will actually shut down with an out of battery power icon after a few minutes at 716mhz or higher for gpu. At least it did for me while playing bullststorm. Anything under works but the drain on your battery is insane. A better and safer idea would be get a battery bank that supports PD and use that while in handheld mode.

 

[ZachyCatGames]

I really wouldn't. The switch can't handle running the gpu at docked speeds while on battery. The switch will actually shut down with an out of battery power icon after a few minutes at 716mhz or higher for gpu. At least it did for me while playing bullststorm. Anything under works but the drain on your battery is insane. A better and safer idea would be get a battery bank that supports PD and use that while in handheld mode.

+ some consoles (such as mine) may randomly immediately shut off out of nowhere at higher clocks on battery.
(fwiw I've done some *very* extreme stuff with mine, but still)

 

[Clydefrosch]

I really wouldn't. The switch can't handle running the gpu at docked speeds while on battery. The switch will actually shut down with an out of battery power icon after a few minutes at 716mhz or higher for gpu. At least it did for me while playing bullststorm. Anything under works but the drain on your battery is insane. A better and safer idea would be get a battery bank that supports PD and use that while in handheld mode.

that still leaves two more gpu clock profiles that likely would help some of the games that struggle on handheld.

maybe the smallest battery bank in the world wouldn't be in the way, but even then, would that really make much of a difference?

 

[sj33]

It would be pretty irresponsible for a dev to include features knowing they cause damage, hence the option isn’t there.

 

[p-sam]

that still leaves two more gpu clock profiles that likely would help some of the games that struggle on handheld.

maybe the smallest battery bank in the world wouldn't be in the way, but even then, would that really make much of a difference?

Even the smallest battery bank helps by reducing the battery strain

 

[Clydefrosch]

I don't even really see how draining the battery fast can do anything other than shave off some lifespan of the battery itself, which seems like a choice people could make, similar to the one they make when installing cfw or homebrew or updating firmware, that has a chance to end your system right there.

If the battery can't provide the necessary juice, i would assume the system turns off or I could see it crash like when you undervolt a syytem, but I still don't see where that would physically damage the system. Maybe lose save data or corrupt files if they're written just then.
But íf that happens after a few minutes at 768mhz (there is no 716 profile), there's 3 more profiles below that to improve the sometimes abysmal performance some games have in handheld mode that should be usable. and you should be able to make some room by lowering screen brightness or limiting cpu clock in return.

tldr... is there really no way that isn't really inconvenient to improve handheld?

 

[p-sam]

I don't even really see how draining the battery fast can do anything other than shave off some lifespan of the battery itself, which seems like a choice people could make, similar to the one they make when installing cfw or homebrew or updating firmware, that has a chance to end your system right there.

If the battery can't provide the necessary juice, i would assume the system turns off or I could see it crash like when you undervolt a syytem, but I still don't see where that would physically damage the system. Maybe lose save data or corrupt files if they're written just then.
But íf that happens after a few minutes at 768mhz (there is no 716 profile), there's 3 more profiles below that to improve the sometimes abysmal performance some games have in handheld mode that should be usable. and you should be able to make some room by lowering screen brightness or limiting cpu clock in return.

tldr... is there really no way that isn't really inconvenient to improve handheld?

If you put 716Mhz in the gpu config, the effective outcome will be 691.2Mhz, since that's the nearest.
We still believe that the people wise enough to not damage their system (or do so in knowledge of what could happen) will also find the relevant parts of the code and edit it as they please. Else, those "I would assume" and "Maybe"s would end up in our Github issues and on our Discord support channels.

We had profiles before sys-clk on Lakka and Retroarch

 

[Clydefrosch]

What exactly is the correlation between understanding that I could risk damage and knowing how to read, manipulate and compile code into something that works?

 

[p-sam]

What exactly is the correlation between understanding that I could risk damage and knowing how to read, manipulate and compile code into something that works?

You're compiling your own version, and do whatever with it. If there's some sensible addition to sys-clk that does not have to do with UI or boost mode, we'd probably appreciate to receive a Pull Request for it.

 

[Clydefrosch]

That is not at all an answer to the question I asked and I think we both know that.
Because the answer to that question is: Understanding there is risks doesn't suddenly give anyone the knowledge to code.

So, anyone with the slightest bit switch related coding reputation willing to do what I can't for 20$ or something? - the offer has potentially been claimed thank you.

 

[p-sam]

That is not at all an answer to the question I asked and I think we both know that.
Because the answer to that question is: Understanding there is risks doesn't suddenly give anyone the knowledge to code.

So, anyone with the slightest bit switch related coding reputation willing to do what I can't for 20$ or something?

yeah why not hmu, not sure i have the reputation though

 

[SeongGino]

What exactly is the correlation between understanding that I could risk damage and knowing how to read, manipulate and compile code into something that works?

That is not at all an answer to the question I asked and I think we both know that.
Because the answer to that question is: Understanding there is risks doesn't suddenly give anyone the knowledge to code.

...Seriously?
You've been told, repeatedly, by both the creators and others, how inadvisable going beyond the limits instated by both Nintendo and the overclocking tool is, and have been given recourse to see the results for yourself... and you're not even willing to put in the smallest bit of effort at seeing which lines to remove for your personal theorycrafting?
Throwing simple responsibility out the window (I'll get to that); has just basic courtesy to leave this up to your own unsupported digression not crossed your mind at all? I'd say, being irresponsible enough to test docked clocks on battery should be gated off by learning to setup your own dev environment and some basic code-reading, if only to protect the greater majority from potential havoc that developers may/would get blamed for.

And for what?

(...but i feel like i could live with eventually getting a new battery if handheld performance was better for it)

Better performance? Not even taking into account the added heat caused by docked clocks? Have you felt a freshly-played docked Switch? It's even more of a lavastone than the GPD Win. That can't possibly be safe to put that level of stress on the battery alone.
By that point, if you get performance gains, it's brute-forcing past shitty programming, and it may be high-time to just not consider playing the game on the Switch at that point.

 

[Clydefrosch]

...Seriously?
You've been told, repeatedly, by both the creators and others, how inadvisable going beyond the limits instated by both Nintendo and the overclocking tool is, and have been given recourse to see the results for yourself... and you're not even willing to put in the smallest bit of effort at seeing which lines to remove for your personal theorycrafting?
Throwing simple responsibility out the window (I'll get to that); has just basic courtesy to leave this up to your own unsupported digression not crossed your mind at all? I'd say, being irresponsible enough to test docked clocks on battery should be gated off by learning to setup your own dev environment and some basic code-reading, if only to protect the greater majority from potential havoc that developers may/would get blamed for.c

And for what?

Better performance? Not even taking into account the added heat caused by docked clocks? Have you felt a freshly-played docked Switch? It's even more of a lavastone than the GPD Win. That can't possibly be safe to put that level of stress on the battery alone.
By that point, if you get performance gains, it's brute-forcing past shitty programming, and it may be high-time to just not consider playing the game on the Switch at that point.

Well, I've been told once before. And historically, people have changed their minds before so sorry for trying.

Gpu clocks up to 7xx didn't seem to be an issue for my system when freebird was still around as an option, this isn't -just- random theory crafting based on nothing but gutfeeling. I played through half of xenoblade 2 with 15xx CPU and the 6xx gpu setting in handheld back then.
Now I know that's still just circumstantial, but I'm not going to blame anyone else if this should ever lead to more severe damage than having to replace a worn out battery. And I'll be happy to support their opinion in the future if I break my thing over it too. I'll gladly be that posterchild.

From where I stand, it would be a lot more irresponsible for me to try and do this myself. People that know how this works seemingly have issues with that whole compiling stuff for no good reason. And I really have little interest to learn this type of skill either. I know that's my problem, which is why I've thrown money at it now (someone dm'd me).

I'll freely admit that 'if you're responsible, you can do it yourself' is an argument that irks me because it doesn't make much sense and if it was a reasonable option to me, I wouldn't be here trying to argue at all. It's not like being able to do it myself reduces any supposed risks either. In a worst case scenario, I'd have wasted both money for a system and time to learn something I'll never need again.
"fuck off already" would've felt like a much more honest response.

Now, as for airflow, that seems overall less impaired undocked, without the warm guts of the dock in the way of one intake, I've put better thermal paste in my system too and with tesla, there's tools to check Temps while playing now too. I'm willing to risk running my system at the Temps it normally did before the paste replacement.

Now, in the interest of me not derailing this thread any further, as I would keep replying to posts addressed at me and things are likely to repeat or escalate past this point, everyone is free to dm me if they want to tell me I'm being irresponsible and I'll stay away, ok?

 

[ZachyCatGames]

but I'm not going to blame anyone else if this should ever lead to more severe damage than having to replace a worn out battery. And I'll be happy to support their opinion in the future if I break my thing over it too. I'll gladly be that posterchild.

From where I stand, it would be a lot more irresponsible for me to try and do this myself. People that know how this works seemingly have issues with that whole compiling stuff for no good reason. And I really have little interest to learn this type of skill either. I know that's my problem, which is why I've thrown money at it now (someone dm'd me).

I'll freely admit that 'if you're responsible, you can do it yourself' is an argument that irks me because it doesn't make much sense and if it was a reasonable option to me, I wouldn't be here trying to argue at all. It's not like being able to do it myself reduces any supposed risks either. In a worst case scenario, I'd have wasted both money for a system and time to learn something I'll never need again.
"fuck off already" would've felt like a much more honest response.

Now, as for airflow, that seems overall less impaired undocked, without the warm guts of the dock in the way of one intake, I've put better thermal paste in my system too and with tesla, there's tools to check Temps while playing now too. I'm willing to risk running my system at the Temps it normally did before the paste replacement.

Now, in the interest of me not derailing this thread any further, as I would keep replying to posts addressed at me and things are likely to repeat or escalate past this point, everyone is free to dm me if they want to tell me I'm being irresponsible and I'll stay away, ok?

Not everyone is like that, unfortunately...

Heh, I know very little C++ (which sysclk is written in) and I was able to figure it out fairly quickly and easily (did some digging around for fun several hours ago after seeing all these messages, probably took less than 10 minutes to find)

It’s a fine argument. People who know what they’re doing should know how to do it themselves, especially if it’s potentially dangerous. Publicly putting out builds of that kind of stuff is a terrible idea imo
especially stuff like my, well, very... “excessive” Switch overclocking stuff

Temperatures aren’t really the issue.