Gigabyte Z690 Aero G + i5-12600K + AMD RX 6800 XT

[mattbatt]

Actually I’m wondering if that was just a lucky fluke! There isn’t a logical explanation that I can think of.

Remember when you wrote that @CaseySJ? After more testing, here's what I have discovered regarding i9-13xxx series CPU's and CPUFriend.kext and it's companion CPUFriendDataProvider.kext. I ran into some very abnormal circumstances. Benchmark was Speedometer 2.1 in Safari (which is a great benchmark for webpage rendering).

Problem 1 - Creating the DataProvider Kext​

Many people don't realize ssdtPRGen.sh and one-key-cpufriend won't build the CPUFriendDataProvider.kext on a Z790 with a i9-13900KF. Maybe the 'F' version of my CPU is not supported, but either way, I could not use those tools.

Another tool I tried was CPUFriendFriend.command which runs Terminal and allows me to input perameters to build the dataprovider kext. This was unsuccessful because the performance never changed in MacPro 7,1 but rather remained very poor. See conclusion.

Problem 2 - Corruption​

If you update the OS - even with a security patch - and you do not first delete CPUFriend.kext and CPUFriendDataProvider.kext from the EFI folder (and then change the config file, obviously) CPUFriendDataProvider.kext becomes corrupted and will no longer power-manage the CPU. This is evidence by an idle of 13 watts at 39C changing into an idle of 69 watts at 70C - tested again and again - with no programs running.

I tested just disabling the kexts in the config file, then updating the OS, it will still become corrupted. When removed completely from the EFI, it works after the update.

Another part of the corruption, for my system, was restart and shut down began hanging for a few minutes and then on reloading the OS, seeing a 'this computer ran into an error, was not shut down properly' message. When the CPUFriendDataProvider.kext was properly restored, not only did my idle temp go back down but shut down and restart now work.

Problem 3 - Restoration​

This by far is the trickiest part of the puzzle: if the CPUFriendDataProvider.kext becomes corrupted (evidenced by high idle power usage and hanging on shut down or restart), simply copying over the kext that was previously proven to run now does not run. In the past, by changing the serial number and SMBIOS, I got it to work. But this latest time, even that did not work.

I had saved three different CPUFriendDataProvider.kext's from various people's EFI's that are similar systems to mine. Attached is the one that worked this most recent time.

It's almost as if the kext gets cached somewhere and cannot be reset and only by either loading a different one or convincing the system that the computer is different, things worked.

I did permission rebuild, clean NVRAM - nothing worked. What worked was loading a CPUFriendDataProvider.kext that I had not used previously and that happened to work for my system.

​

Conclusion​

iMacPro 1,1

• CPUFriend and CPUFriendDataProvider are not necessary for CPU performance increase
• Without CPUFriendDataProvider, idle wattage rises from 10 watts to 50 watts after 40 seconds, with CPUFriendDataProvider idle remains at 10 watts
• Once CPUFriendDataProvider.kext gets corrupted, idle will rise to 50 watts and shut down/restart won't work but performance is the same

MacPro 7,1

• Idles at 15 watts without CPUFriendDataProvider but has drastically reduced CPU performance
• CPUTopologyRebuild.kext does not help performance if there is no CPUFriendDataProvider
• Once CPUFriendDataProvider.kext gets corrupted, idle watts rise to 69 watts and shut down/restart do not work but the performance is unaffected

Benchmarks​

Speedometer 2.1 in Safari:
i9-9900k 64 GB Ram: 249
Mac Studio M2 Ultra, 64 GB RAM: 424
Mac Book Pro M3 Max 48 GB RAM, 16c/40c: 581
i9-13900KF iMacPro 1,1 64 GB RAM without CPUFriendDataProvider.kext: 526
i9-13900KF iMacPro 1,1 64 GB RAMwith CPUFriendDataProvider.kext: 523
i9-13900KF MacPro 7,1 64 GB RAMwithout CPUFriendDataProvider.kext: 251
i9-13900KF MacPro 7,1 64 GB RAMwith CPUFriendDataProvider.kext: 520

 

[mattbatt]

Hi @CaseySJ sorry to bother you: regarding my post above about CPUdatafriend.kext, I did unfortunately confirm that after wake from deep sleep, energy on idle does rise and restart fails.

But on a fresh start, my hack idles fine and restarts fine. Do you have any suggestion for me to test, research, learn? I really want to figure this out. I feel like I am so close

 

[CaseySJ]

Hi @CaseySJ sorry to bother you: regarding my post above about CPUdatafriend.kext, I did unfortunately confirm that after wake from deep sleep, energy on idle does rise and restart fails.

But on a fresh start, my hack idles fine and restarts fine. Do you have any suggestion for me to test, research, learn? I really want to figure this out. I feel like I am so close

You are way ahead of me on CPUFriend!

I say this only as a matter of fact and not in any way as an indictment on your efforts, that I have not examined idle and load power consumption of my Hackintoshes. I incorporated CPUFriend into the EFI for systems that use product name MacPro 7,1 only because our Geekbench scores were coming up too low. Simply switching to iMacPro 1,1 recovered those scores -- as did the use of CPUFriend.

 

[mattbatt]

You are way ahead of me on CPUFriend!

I say this only as a matter of fact and not in any way as an indictment on your efforts, that I have not examined idle and load power consumption of my Hackintoshes. I incorporated CPUFriend into the EFI for systems that use product name MacPro 7,1 only because our Geekbench scores were coming up too low. Simply switching to iMacPro 1,1 recovered those scores -- as did the use of CPUFriend.

Much appreciated for all your help @CaseySJ! I'll continue to troubleshoot, and I am thinking of possibly trying to figure out power management. Today I just was working on the computer. After a few hours, it ramped up to more energy at idle, and then would hang on restart.

Normally, it takes 40 seconds with a corrupted CPUFriend but now it's after a few hours. The thing that bothers me is the not being able to restart or shut down when this happens - I feel that there could be a deeper issue somewhere. Seems like more than one thing conflicting.

 

[jorsh]

Hey ya'll I royally messed up my boot partition. I lazily didn't take the drives out when I was reinstalling Windows and now the Mac OS drive only boots to the recovery partition instead of the OS.

I am attaching the EFI files here. Is there anything I can change to fix this without having to re-do the bootloader from scratch?

 

[CaseySJ]

** UPDATE **

EFIClone.sh in my GitHub repository is now compatible with SuperDuper! 3.8. Please read the entire post below before using.

This script is used by both Carbon Copy Cloner and SuperDuper! to automatically clone source EFI partition to destination EFI partition. Its use is optional.

EFIClone - automatic backup of the EFI partition

Okay, sorry to hear that -- I wouldn't mind helping refine your script so that it DOES work with SuperDuper but I'll jump to CCC -- I only have to make that copy once anyway right? And all future backups are just the hard drive part and the EFI will always be there (unless there's a new version...

www.tonymacx86.com

 

[marcchizzie]

Does the WiFi Intel work with Sonoma now?

 

[CaseySJ]

Hey ya'll I royally messed up my boot partition. I lazily didn't take the drives out when I was reinstalling Windows and now the Mac OS drive only boots to the recovery partition instead of the OS.

I am attaching the EFI files here. Is there anything I can change to fix this without having to re-do the bootloader from scratch?

The EFI folder looks fine. The problem you described is most likely coming from somewhere else. To troubleshoot the cause, can you do the following:

• Because there are multiple disks in your system, two or more of the may contain EFI partitions. Mount each EFI partition one by one
  • For each EFI partition that you mount, do this:
    • Open the EFI disk in Finder
    • You will see files and folders at the top level of the file hierarchy
    • Expand all the folders in the root level (no need to expand any sub-folders)
    • Capture and post a screenshot
  • Unmount the EFI partition, then mount the next EFI partition and repeat the previous bullet

 

[CaseySJ]

Does the WiFi intel work with Sonoma now?

Intel WiFi has worked with Sonoma for several months now.

But not all macOS Continuity features are supported.

 

[mikecmp]

Hoping someone can give me an idea where to start.

on occasion my hackintosh will take forever to start, when it finally does, it only recognizes the system drive and non of the other drives in the machine. Sometimes i can reboot and fix it, sometimes it seems to fix it self after a few reboots. It feels random and I am not sure how to troubleshoot it.

I recently updated to the latest version of Ventura, though this had happened before as well. Right now I grabbed oc auxiliary tools and updated Opencore just to be safe.