search

calasanmarko / TurboMac

Stops CPU throttling on Intel-based Macs
GNU General Public License v3.0
56 stars 7 forks source link

Which identifier should I be using? #2

Open XMesc opened 2 years ago

XMesc commented 2 years ago

Hi, I am new to this site so if I am doing something wrong I hope you can forgive me.

I would like to ask which of the following disk identifiers should I use?

Disk List

And I would also like to know if using this alternative is an improvement over using software like "VoltageShift" to modify the MSR values (it has less impact on the processor or some sort of thing).

Thank you.

calasanmarko commented 2 years ago

I would like to ask which of the following disk identifiers should I use?

You should use the identifier of the volume where the OS is installed, which from your screenshot seems to be disk1s5.

And I would also like to know if using this alternative is an improvement over using software like "VoltageShift" to modify the MSR values (it has less impact on the processor or some sort of thing).

It's the same thing as using something like VoltageShift or PCM, except that this being a kernel extension has the advantage of loading early in the boot process, which means much shorter boot times if your issue is a broken battery or something similar.

Feel free to follow up with any additional issues.

XMesc commented 2 years ago

Thanks for the quick response!

I gave a try, every step went smooth until the step 6 of the Big sur and higher guide. Here is a screenshot of the command. Screen Shot 2022-02-26 at 7 55 18 PM

calasanmarko commented 2 years ago

No problem! You missed the sudo at the beginning of the command, hence the operation not being permitted.

XMesc commented 2 years ago

Didn't use sudo cause Im already on su since the beginning of the process, tried with sudo and the outcome is the same. None of the earlier commands gave me trouble, just this one. SIP is also disabled.

PD. Im on Mac OS Monterey if that's relevant.

calasanmarko commented 2 years ago

I see. Maybe there is some sort of problem trying to create a snapshot from within the root home folder.

tried with sudo and the outcome is the same

All the commands or just the one giving you the error?

If the second one, try running all the commands from the beginning with sudo so the mount is created in a regular user's home folder.

XMesc commented 2 years ago

Also thought on that, same outcome. Screen Shot 2022-02-26 at 8 31 14 PM

In case that we don't solve the issue is there a way to revert the changes done? I can use VoltageShift in the meantime.

calasanmarko commented 2 years ago

Check if Secure Boot is on (different from SIP). If so, try turning it off first to see what happens.

Because the bless command failed all changes will be reversed after a restart.

What specific device are you using?

XMesc commented 2 years ago

Will try, stay with me.

I'm on a Macbook Pro 13-inch from early 2015, running Monterey and an I5 CPU.

XMesc commented 2 years ago

Secureboot was disabled already :(. Guess I’ll have to stick with VoltageShift and do some research. Thank you for your assistance!

calasanmarko commented 2 years ago

Oh well I don't think those have Secure Boot anyway.

Let's try one more thing - post csrutil authenticated-root status

XMesc commented 2 years ago

On my way.

XMesc commented 2 years ago

Didn't work neither, prolly the problem is on my end. Thank you so much for bearing with me.

calasanmarko commented 2 years ago

No I meant post a screenshot of the result of the command, running it does nothing by itself. Sorry for being unclear.

XMesc commented 2 years ago

Oh my bad, this is the result.

“Authenticated Root status: enabled”

calasanmarko commented 2 years ago

Ah well there it is!

My mistake, I neglected to mention in the README that you should also run csrutil authenticated-root disable from Recovery mode to disable Authenticated Root. Do that and it should work.

XMesc commented 2 years ago

Well I still got to learn a thing or two haha. I just disabled FileVault so this may take a while until its decrypted. Will try when its done and update here so you can check it tomorrow. Thanks!

Also since now there are 99% chances that the process works which are the methods to revert the changes?, so I can have them at hand when my battery gets replaced.

PD. When the snapshot successfully creates I can enable again the authentication-root?

calasanmarko commented 2 years ago

No problem whatsoever.

To revert the changes just follow the installation instructions up to and including the sudo mount ... part, then:

  1. Run sudo rm -rf ~/nonroot/System/Library/Extensions/TurboMac2.kext
  2. cd to the safe location where you previously stored IOPlatformPluginFamily.kext
  3. Run sudo cp -rf IOPlatformPluginFamily.kext ~/nonroot/System/Library/Extensions/IOPlatformPluginFamily.kext

Then continue onward with the sudo kextcache -i / then sudo bless ... part.

I know that this whole thing is a hassle and I will work on automating it when I'm less busy.

PD. When the snapshot successfully creates I can enable again the authentication-root?

I don't think so but you can try. Not that anything will go wrong, I just think it will revert the installation. If so then I guess that's an easier uninstallation method lol (I would still recommend doing it properly though, for cleanup's sake).

calasanmarko commented 2 years ago

Any updates? Does it work now?