VoltageShift (maybe BigSur) problem

[eapuzzo]

I've noticed since some time a problem in using the voltageshift utility, exactly after the upgrade to BigSur it doesn't work anymore, does anyone have the same problem ?

[MarFre22]

Hi @Remmed96 !

Thanks for the feedback! I'm not using BigSur due to privacy concerns. I think it's a kext problem. I will look for any possible solution. I forgot to write on the wiki page the compatibility area and also I will put this warning.

EDIT: Wiki updated with the warning.

[Menchen]

It’s not kext problem... check your SIP and file permission.

[eapuzzo]

My SIP is disabled and I checked the permission, maybe I did something wrong, could you help me in understanding how it should be done right ?

I used these commands that I read in the official sicreative guide:

Build the kernel extension (kext) xcodebuild -target VoltageShift Change owner sudo chown -R root:wheel build/Release/VoltageShift.kext Build command line tool xcodebuild -target voltageshift

[MarFre22]

Sorry, I thought it was a kext update problem, but isn't. Also, in VoltageShift repo there is an issue related to this problem here, unfortunately, without any solution, but it's nice to take a look.

[eapuzzo]

I think I'm going back to Catalina to use voltage shift.

[Menchen]

I think I'm going back to Catalina to use voltage shift.

whats your sudo spctl --status? Also check Security & Privacy to allow the kext

Fix the permission to 0:0(root:wheel) to the file /private/var/db/KernelExtensionManagement/...... (the path in your screenshoot)

[eapuzzo]

I think I'm going back to Catalina to use voltage shift.

whats your sudo spctl --status? Also check Security & Privacy to allow the kext

Fix the permission to 0:0(root:wheel) to the file /private/var/db/KernelExtensionManagement/...... (the path in your screenshoot)

Sorry for replying after days, as soon as I have some free time I will try to apply your suggestions and let you know if I can solve it. Thank you so much for the help you are giving me.

[eapuzzo]

I think I'm going back to Catalina to use voltage shift.

whats your sudo spctl --status? Also check Security & Privacy to allow the kext

Fix the permission to 0:0(root:wheel) to the file /private/var/db/KernelExtensionManagement/...... (the path in your screenshoot)

This is my "sudo spctl --status", how can i check if the kext status in Security and Privacy? Afther that how can I Fix the permission ot 0:0 ? Sorry but I'm not really good in this kind of stuff.

[eapuzzo]

After hours lost looking for a solution I decided to go back to Catalina, everything works perfectly.

[MarFre22]

@Remmed96 Sorry, but lately I haven't had time to explore this situation. I hope to be able to explore it more soon.

[eapuzzo]

@MarFre22 Don't worry, I also notice a lot more stability with catalina so I would have downgraded regardless. Thanks a lot anyway

[eapuzzo]

@stevezhengshiqi I may have found the solution to the problem but I haven't had the chance to test it yet, by chance updating the EFI folder I noticed a difference in the info.plist file that prevented me to use VoltageShift also on Catalina, it seems that the problem is in NVRAM->Add->7C436110-AB2A-4BB-A880-FE41995C9F82. What I noticed is that in the info.plist file where I have no problems the csr-active-config parameter is "MAAAA==" or "30000000" when opened in Xcode. In the new version of info.plist it is "AAAAAA==" or "00000000" if opened in Xcode. I think that the solution of the problem also for Big Sur is to change this parameter (It serves to set the parameters of the SIP that is the System Integrity Protection so you don't risk the brick). If someone interested can try it would be helpful for everyone, I currently do not have time and I have a lot of important data on the PC for a job I'm doing, so I can not try.

[eapuzzo]

I don't remember where I found this script and I'm not the creator but I just know it's working, I'd just like to share it with anyone who needs it. VoltageShift-TW.zip

[MarFre22]

@stevezhengshiqi I may have found the solution to the problem but I haven't had the chance to test it yet, by chance updating the EFI folder I noticed a difference in the info.plist file that prevented me to use VoltageShift also on Catalina, it seems that the problem is in NVRAM->Add->7C436110-AB2A-4BB-A880-FE41995C9F82. What I noticed is that in the info.plist file where I have no problems the csr-active-config parameter is "MAAAA==" or "30000000" when opened in Xcode. In the new version of info.plist it is "AAAAAA==" or "00000000" if opened in Xcode. I think that the solution of the problem also for Big Sur is to change this parameter (It serves to set the parameters of the SIP that is the System Integrity Protection so you don't risk the brick). If someone interested can try it would be helpful for everyone, I currently do not have time and I have a lot of important data on the PC for a job I'm doing, so I can not try.

Sorry for my disappearance on this topic.

With Clover EFI after being updated with partial SIP activation, I had to turn off all kext related security options in the settings (clover's menu) to run VoltageShift kext. I've been using OpenCore EFI (only NVRAM Protection turned off in SIP) with VoltageShift v1.1, and for some reason it works.

[eapuzzo]

@stevezhengshiqi I may have found the solution to the problem but I haven't had the chance to test it yet, by chance updating the EFI folder I noticed a difference in the info.plist file that prevented me to use VoltageShift also on Catalina, it seems that the problem is in NVRAM->Add->7C436110-AB2A-4BB-A880-FE41995C9F82. What I noticed is that in the info.plist file where I have no problems the csr-active-config parameter is "MAAAA==" or "30000000" when opened in Xcode. In the new version of info.plist it is "AAAAAA==" or "00000000" if opened in Xcode. I think that the solution of the problem also for Big Sur is to change this parameter (It serves to set the parameters of the SIP that is the System Integrity Protection so you don't risk the brick). If someone interested can try it would be helpful for everyone, I currently do not have time and I have a lot of important data on the PC for a job I'm doing, so I can not try.

Sorry for my disappearance on this topic.

With Clover EFI after being updated with partial SIP activation, I had to turn off all kext related security options in the settings (clover's menu) to run VoltageShift kext. I've been using OpenCore EFI (only NVRAM Protection turned off in SIP) with VoltageShift v1.1, and for some reason it works.

I know little about this kind of thing, I just told my experience and how I solved it, I don't know if it is the best solution or the most correct but it solved my problem. Thanks for the reply.