Homebrew RELEASE sys-clk under/overclocking sysmodule

[Anxiety_timmy]

Cases of failure of memory sections - 0.

My erista would like to speak up for a second there.

 

[Cooler3D]

With more detail on what I said, performance degradation refers to how a clockspeed could be set, but its producing so many errors that correcting them makes it degrade. Added to that, depending on your cpu bin the actual preformance might be in the range of 1.9-2.0, while 4ifir might want to set 2.4ghz. Gpu wise same story. Nand corruption happens because naturaly not every ram chip is made the same so a console could run at 1.9ghz ram without any overvolting, while another one cant reach 1.8 without overvolting. Heat is self explanatory (I probably should delete that ngl, because thermal paste replacements are a thing) . The last point was how erista units at those clockspeeds draw a relatively high amount of power for their boards at just 921. 18 watts is the maximum (I belive the power regulators can carry more, but only for power spikes, not for sustained load) 4ifir draws much more than that. TLDR: 4ifir can help but it will degrade your components much much faster than they should be.

Absolutely right, buddy, I couldn't have said it better myself. High overclocking values lead to accelerated wear of components.

 

[Anxiety_timmy]

Cases of processor degradation - 0.

Probably should have worded that better, but I don't mean it as your cpu is going to start preforming worse, just setting that clockspeed would make it run worse, and then setting a lower one would reduce the error correcting and make it run better. Thats at least how I understand it.

 

[Anxiety_timmy]

My erista would like to speak up for a second there.

actually no plenty of consoles have something to say about that. Not always related to 4ifir, but just ram oc in general.

 

[cucholix]

My erista would like to speak up for a second there.

I had a case of nand corruption, but was because I overclocked RAM on my Erista beyond 1862mhz.

 

[Cooler3D]

My erista would like to speak up for a second there.

Why didn't you tell me about this before? I would add your case to the description as a warning. And then everyone downloads, uses, shines with happiness, and if they complain, then it’s about minor bugs that I correct as updates.
Or... Did this happen not because of 4IFIR, but in principle during overclocking in other ways?

 

[Anxiety_timmy]

I mean I dont really think that there shouldn't be a warning if nothing has happened unless its obvious.

 

[Anxiety_timmy]

You could argue it is obvious but to quite a few people I assure you it probably isn't.

 

[Cooler3D]

I mean I dont really think that there shouldn't be a warning if nothing has happened unless its obvious.

I did not quite understand you, but just in case, I integrated several layers of antidump protection into 4IFIR. Including trying to start with OC from the SYSNAND.

 

[Anxiety_timmy]

Heh, bad wording again. What I mean was that if you know it can happen and can damage consoles, there should be a warning that "hey this can damage your console, so just be warned" or something the like.

 

[Cooler3D]

You could argue it is obvious but to quite a few people I assure you it probably isn't.

If I wanted to convince someone of something, then for a start I would unfreeze the 4thread. Obviously, that's not what I'm here for. The installation base is expanding beautifully even without a presence here.
P.s. I'm not advocating downloading 4IFIR. Just give the opportunity to do so.
Have a nice day.

 

[ZachyCatGames]

Why didn't you tell me about this before? I would add your case to the description as a warning. And then everyone downloads, uses, shines with happiness, and if they complain, then it’s about minor bugs that I correct as updates.
Or... Did this happen not because of 4IFIR, but in principle during overclocking in other ways?

I've told you in the past I've observed multiple people encounter corruption from memory OC on Erista back when I was still doing this stuff, you ignored it.

 

[Deleted member 323844]

Didn't he answer you clearly? The 4IFIR plant will blow up your grandmother, you are literally going to rape her corpse. Is the dubious performance boost in all resource-intensive games worth it? But who needs these 60 frames per second and native resolution?! In games, the main thing is the gameplay, the rest is done by the imagination...

By the way, at the moment, due to 4IFIR:
Cases of processor degradation - 0.
Cases of failure of memory sections - 0.
Damaged power regulators - 0.
Damaged system boards - 0.
Out of order consoles - 12. Kidding. 0.
Active 4IFIR installations - Tens of thousands.

And yet, I do not recommend using it, what if your console becomes the first to fail?
No, seriously, everything he described can really happen to your console, I guess.

I wasn't talking about max overclocking but an AIO solution for performance metrics and overclocking. Doesn't 4IFIR have the sys-clk frequencies? I wouldn't go over that.

 

[Cooler3D]

I wasn't talking about max overclocking but an AIO solution for performance metrics and overclocking. Doesn't 4IFIR have the sys-clk frequencies? I wouldn't go over that.

They are there. 4IFIR is equipped with a modified version of SYS-CLK.

 

[Cooler3D]

I've told you in the past I've observed multiple people encounter corruption from memory OC on Erista back when I was still doing this stuff, you ignored it.

You already told me that your patches destroyed consoles. But 4IFIR does not contain the code you wrote, so nothing to worry about. If you lazy to equip patches with protection against boot from SysNand, then you could at least warn users about this.
You, in fact, planted a brikcode to these unfortunate users.
However, after you (apparently trying to kill me with a cringe) threatened me with a copyright strike for using the GPL code, it doesn't seem so surprising anymore.

 

[ZachyCatGames]

You already told me that your patches destroyed consoles. But 4IFIR does not contain the code you wrote, so nothing to worry about. If you lazy to equip patches with protection against boot from SysNand, then you could at least warn users about this.
You, in fact, planted a brikcode to these unfortunate users.
However, after you threatened me with a copyright strike for using the GPL code, it doesn't seem so surprising anymore.

Whos patcher is used is completely irrelevant the end result is identical, I had observed similar issues in L4T as well (which "properly" supports OC without binary patching).
I'm not arbitrarily locking it (especially when I myself use it on sysmmc), and we've been warning people of the corruption risk since we first observed it.
But this does 100% confirm to me that you're a troll, so thanks.

I'm not discussing this any further as I've moved onto other more fun/interesting things and don't don't work on this shit outside of patch maintenance anymore, and am frankly uninterested in going into this bs again. Have a nice day.

Edit:
And I wouldn't have ever copyright struck that, besides the ams shit I consider it public domain.
The issues there were in that you said you'd take it down if any of the original authors were again anything, then proceeded not to.

 

[Cooler3D]

I'm not discussing this any further as I've moved onto other more fun/interesting things and don't don't work on this shit outside of patch maintenance anymore, and am frankly uninterested in going into this bs again. Have a nice day.

As far as I can remember, this is the fourth time you promise to do this, but each time you return again to generate even more cringe.

I had observed similar issues in L4T as well

Wait, that is, you also destroyed Android consoles? How many devices did your brikcode take in total?

But this does 100% confirm to me that you're a troll, so thanks.

My solution, with a much larger installbase, did not destroy a single console. Your patches, in your own words, manage to kill consoles on any operating system. At the same time, you claim that the troll of the two of us is me? How do your patches even manage to burn consoles if they don't even really overclock anything (except for a minor memory overclock)?

The issues there were in that you said you'd take it down if any of the original authors were again anything

The public versions of 4IFIR never had a single line of code written by you. You are not its original author. You are not P-Sam, Ctcaer, not a HookedBehemoth, and even not a KazushiMe. You are developer of brick-patches.

And I wouldn't have ever copyright struck that, besides the ams shit I consider it public domain.

Of course you didn't. It's one thing to try to kill me with a kringe. Another thing is to get into all the world's technews platforms - as the most miserable GPL developer. You understood it perfectly.

 

[ZachyCatGames]

As far as I can remember, this is the fourth time you promise to do this, but each time you return again to generate even more cringe.


Wait, that is, you also destroyed Android consoles? How many devices did your brikcode take in total?


My solution, with a much larger installbase, did not destroy a single console. Your patches, in your own words, manage to kill consoles on any operating system. At the same time, you claim that the troll of the two of us is me? How do your patches even manage to burn consoles if they don't even really overclock anything (except for a minor memory overclock)?


The public versions of 4IFIR never had a single line of code written by you. You are not its original author. You are not P-Sam, Ctcaer, not a HookedBehemoth, and even not a KazushiMe. You are developer of brick-patches.

L4T stuff was done by CTC, and none of this has killed consoles, simply recoverable fs corruption.
Anyway, blocked, do not make any attempt to contact me in the future, for help, information, or otherwise (I had some unpublished fixes you don't have).
Goodbye.

 

[deathblade200]

L4T stuff was done by CTC, and none of this has killed consoles, simply recoverable fs corruption.
Anyway, blocked, do not make any attempt to contact me in the future, for help, information, or otherwise (I had some unpublished fixes you don't have).
Goodbye.

don't worry if you give the code to KazushiMe he will just piggyback off of that anyway. but yeah this shit is like deja vu

 

[Cooler3D]

Anyway, blocked, do not make any attempt to contact me in the future, for help, information, or otherwise (I had some unpublished fixes you don't have).

Wait, are you kidding right? I have never asked you for help, how likely would it occur to me to turn to you for help in the future? Don't confuse yourself with CTCart and P-Sam. You are not a developer of the level for me to learn something from you. Unless, if I suddenly need to write a brikcode ...

UPD. Just look, your sycophant is right there. Do you still send him to stalker on Russian-language resources, or does he make such decisions on his own?