Jump to content
crazylegsmurphy

Clover: Yosemite Sleep/Hibernate – GA-Z87X-UD5

20 posts in this topic

Recommended Posts

Hello Everyone,

 

 

So after weeks of testing and tweaking, it seems that this is the only noticeable issue I have with my Hackintosh.

 

Basically, what happens is that the computer will go to sleep after 1.5 hours as per the setting in “System Preferences.” It will sleep, and wake normally within a certain amount of time as well.

 

The problem is that after a certain amount of hours not being woken up, the computer will restart itself. I will wake up in the morning and find it sitting at the Clover boot screen.

In an attempt to fix this, I have turned off “Wake for Network” and “Restart on Power Failure”. I have also turned off some settings in OS X such as “Wake for Network” and “Nap”.

 

I have also attempted to set the Hibernate to setting “0” but this has had no affect.

At this point it is probably an issue with the settings, but I don’t have enough understanding to know what setting to change, or where. If someone could help me look at this, I would really appreciate it.

 

….

 

 

SPECS:

 

 

GA-Z87X-UD5 TH

 

NVIDIA GeForce GTX 780 3072 MB (SC)

 

Corsair Vengeance LP - 16 GB 1600 DDR3 RAM

 

3.5 GHz Intel Core i7 (OC to 4.3 GHz)

 

Rosewill PCI WiFi card

 

Samsung Evo 840 500GB SSD (OS X)

 

SanDisk 120 GB (Windows 8.1)

 

SanDisk 120 GB (Storage)

 

Seagate Barracuda 3 TB HDD

 

 

….

 

 

FILES:

 

Here are my Config.plist, DSDT.aml, and SSDT.aml files.

 

http://jeffwalker.ca/hackintosh/CLM-Hackintosh.zip

Share this post


Link to post
Share on other sites
Advertisement

Thanks, Slayer.

I have read similar things. Unfortunately, it still isn't working. 

On that link you sent, steps 1 - 8 work as described. When I attempt to start in Hibernate mode, the screen goes blank and nothing happens. I can cancel hibernate mode and boot normally, but that is all.

As for the rest of the article, I simply don't have enough experience with Clover/Hibernate/Etc to fix the issue. All I want the PC to do is act like it did with my previous version of Mavericks where the computer would sleep, and wake up when I press a button. Now, rebooting into Clover is quite annoying as it will just sit there with the screen on, blasting the fans, and sucking up power for hours.

 

Share this post


Link to post
Share on other sites

Thanks, Slayer.

 

I have read similar things. Unfortunately, it still isn't working. 

 

On that link you sent, steps 1 - 8 work as described. When I attempt to start in Hibernate mode, the screen goes blank and nothing happens. I can cancel hibernate mode and boot normally, but that is all.

 

As for the rest of the article, I simply don't have enough experience with Clover/Hibernate/Etc to fix the issue. All I want the PC to do is act like it did with my previous version of Mavericks where the computer would sleep, and wake up when I press a button. Now, rebooting into Clover is quite annoying as it will just sit there with the screen on, blasting the fans, and sucking up power for hours.

 

 

Just to make sure i understand, what you want to get is only sleep or you want to get hibernate as well (which requires a lot more experimentation with slide values and Clover efi drivers) ?

If it is only for sleeo you may try with sudo pmset -a hibernatemode 0 or 3.  For me 0 works well as i don't need hibernate, in fact its useless for me.

Share this post


Link to post
Share on other sites

Just to make sure i understand, what you want to get is only sleep or you want to get hibernate as well (which requires a lot more experimentation with slide values and Clover efi drivers) ?

If it is only for sleeo you may try with sudo pmset -a hibernatemode 0 or 3.  For me 0 works well as i don't need hibernate, in fact its useless for me.

 

I don't really care if it hibernates. I just want the PC to "sleep" so it's not sucking power all night.

 

I think I already set the hibernate mode to 0, perhaps I should try 3. 

Share this post


Link to post
Share on other sites

I don't really care if it hibernates. I just want the PC to "sleep" so it's not sucking power all night.

 

I think I already set the hibernate mode to 0, perhaps I should try 3. 

Yeah give it a shot with mode 3.  Also what do you have in your drivers64UEFI ? Many od the drivers have a significant impact on Sleep, i am using the followings:

-EmuleVariables64 - This one is only usefull if you have problems in storing the NVRAM variables with your Bios.

-FSinject-64

-HSFPlus

-OsxAptioFixDrv-64

-OsxFatBinaryDrv-64

Share this post


Link to post
Share on other sites

I'm setting it to mode 3. I'll see what it looks like in the morning.

 

I have the same things in my drivers64UEFI as you, except I have "PartitionDxe-64" as well. 

 

The only thing I can think of is that my SSDT.aml isn't setup right with my config for Pstates or something. Unfortunately, while I did the best to set it up based on my system, I'm not sure it is all correct.

 

 

I appreciate the help though, honestly. 
 

Share this post


Link to post
Share on other sites

Last night I cleared the logs, and set hibernate mode to 3 (it was 0). The result was that my PC was off this morning, and would not wake up via the mouse or keyboard.

 
When I turned on the power, the Clover boot screen said that OS X was Hibernated, but I cancelled hibernation, and booted normally.
 
There were no errors in the log files.

Share this post


Link to post
Share on other sites

It seems that nothing I do is helping, and I simply don't have enough information to go any further. 

 

My only solution is to see if I can't extend the sleep, so I might avoid the hibernation.

 

So, is there any way I can extend the time that the computer takes until it decides to hibernate? For example, it will sleep perfectly for X amount of hours, during which time I can wake it up normally. Can I set OS X to not hibernate until say, 15 hours have past? That would give me enough time to sleep during the night, and still catch it before it goes into hibernate mode. If I don't get to it within 15 hours, then I'll just boot normally and deal with having to start over where I left off.

Share this post


Link to post
Share on other sites

It seems that nothing I do is helping, and I simply don't have enough information to go any further. 

 

My only solution is to see if I can't extend the sleep, so I might avoid the hibernation.

 

So, is there any way I can extend the time that the computer takes until it decides to hibernate? For example, it will sleep perfectly for X amount of hours, during which time I can wake it up normally. Can I set OS X to not hibernate until say, 15 hours have past? That would give me enough time to sleep during the night, and still catch it before it goes into hibernate mode. If I don't get to it within 15 hours, then I'll just boot normally and deal with having to start over where I left off.

Try this: It should sleep with no wake by mouse or keyboard only Short press the power button.

config.plist.zip

Share this post


Link to post
Share on other sites

Simple mod:

 

Added: <key>AdClockId</key>

             <string>true</string>

 

To: Devices/Usb

 

Hope it works....

 

Ps also make sure no wake by Lan in "energy saver" or in Bios is set...

Share this post


Link to post
Share on other sites

Simple mod:

 

Added: <key>AdClockId</key>

             <string>true</string>

 

To: Devices/Usb

 

Hope it works....

 

Ps also make sure no wake by Lan in "energy saver" or in Bios is set...

Isn't fixing USB clock ID supposed to let you wake up with a mouse or keyboard ?

 

crazylegsmurphy: Did you generate your SSDTs using the script from Pike ?

Also, did you try other SMBioses ?

Share this post


Link to post
Share on other sites

I have exactly the same system and the same Wake problem, after many different change i discovered that this problem, in my case, is related to the Hibernation status because after the standbydelay (see pmset) no way to wake up my system, i solved it setting:

 

 

sudo pmset -a standby 0

 

 

sudo pmset -a standbydelay 8640000

 

(standby delay is arbitrary and i set very high value just to avoid any problem)

 

FYI

 

pmset -g live

 

Active Profiles:

AC Power -1*

Currently in use:

 standby              0

 Sleep On Power Button 1

 womp                 1

 autorestart          0

 hibernatefile        /var/vm/sleepimage

 darkwakes            1

 networkoversleep     0

 disksleep            10

 sleep                1

 autopoweroffdelay    14400

 hibernatemode        0

 autopoweroff         1

 ttyskeepawake        1

 displaysleep         10

 standbydelay         8640000

 

Best

 

Francesco

 

 

 

Share this post


Link to post
Share on other sites

I have exactly the same system and the same Wake problem, after many different change i discovered that this problem, in my case, is related to the Hibernation status because after the standbydelay (see pmset) no way to wake up my system, i solved it setting:

 

 

sudo pmset -a standby 0

 

 

sudo pmset -a standbydelay 8640000

 

(standby delay is arbitrary and i set very high value just to avoid any problem)

 

FYI

 

pmset -g live

 

Active Profiles:

AC Power -1*

Currently in use:

 standby              0

 Sleep On Power Button 1

 womp                 1

 autorestart          0

 hibernatefile        /var/vm/sleepimage

 darkwakes            1

 networkoversleep     0

 disksleep            10

 sleep                1

 autopoweroffdelay    14400

 hibernatemode        0

 autopoweroff         1

 ttyskeepawake        1

 displaysleep         10

 standbydelay         8640000

 

Best

 

Francesco

 

Whoa! Nice!

 

Ok, I've set the settings, I'll report back in the morning and see what happens. Thank you.

 

 

Isn't fixing USB clock ID supposed to let you wake up with a mouse or keyboard ?

 

crazylegsmurphy: Did you generate your SSDTs using the script from Pike ?

Also, did you try other SMBioses ?

 

I generated my SSDT using a script, yes. I think it was from Pike. 

 

I haven't tried any other SMBioses....unless you mean like the System Definitions, in which case I tried a bunch. The one I have currently is the most stable.

Share this post


Link to post
Share on other sites

Francesco!

 

I'm going to leave it a bit longer, just to be sure. However, last night my PC went to sleep about 1:30am, and when I woke up today at 8:15am, my PC was quietly sleeping. I pressed the mouse button and *yawn* it woke up and was ready to go!

That is exactly what I needed it to do. If it continues to work, then that is exactly what I needed it to do, and I thank you so much!

 

I think this is about the final issue with my Mackintosh, so I'm very grateful. 


Please keep my name handy on here. Since we have basically the same system, it might be nice to be able to bounce issues off each other. If there is anything I can help with, I would be more than glad to help trouble shoot it with/for you.

Thanks again.

Jeff

Share this post


Link to post
Share on other sites

Jeff

 

Very well, i tried in may different ways without any results, i am quite sure that this solution is only a workaround because on Yosemite we have something wrong in sleep/wake processes, i am using a pretty vanilla OSX with only Toleda ALC898 AppleHDA.kext to make the audio working.

 

I am using Clover boot loader with SSDT to make HDMI audio working, in my case no DSDT.

 

My system work very well including CPU speedstep, iMessage and Airplay, to avoid any problem i preferred to use original apple AC WIFI card.

 

 

Best

 

Francesco

Share this post


Link to post
Share on other sites

I have exactly the same system and the same Wake problem, after many different change i discovered that this problem, in my case, is related to the Hibernation status because after the standbydelay (see pmset) no way to wake up my system, i solved it setting:

 

 

sudo pmset -a standby 0

 

 

sudo pmset -a standbydelay 8640000

 

(standby delay is arbitrary and i set very high value just to avoid any problem)

 

FYI

 

pmset -g live

 

Active Profiles:

AC Power -1*

Currently in use:

 standby              0

 Sleep On Power Button 1

 womp                 1

 autorestart          0

 hibernatefile        /var/vm/sleepimage

 darkwakes            1

 networkoversleep     0

 disksleep            10

 sleep                1

 autopoweroffdelay    14400

 hibernatemode        0

 autopoweroff         1

 ttyskeepawake        1

 displaysleep         10

 standbydelay         8640000

 

Best

 

Francesco

Thank's ! Solved

i had the same problem

Share this post


Link to post
Share on other sites

I just upgraded from 10.8 to 10.10.3 and noticed this issue.  When I followed the instructions provided by uniblack, the standby value never showed up.  Is 10.10.3 different or it because I have NullCPUPowerManagment.kext installed?  Would "sudo pmset -a hibernatemode 0" do the trick?

 

My pmset output after doing "pmset -a standby 0":

 

$ pmset -g live

Active Profiles:

AC Power -1*

Currently in use:

 hibernatemode        3

 womp                 1

 networkoversleep     0

 sleep                0

 Sleep On Power Button 1

 ttyskeepawake        1

 hibernatefile        /var/vm/sleepimage

 disksleep            10

 displaysleep         0

Share this post


Link to post
Share on other sites

I just upgraded from 10.8 to 10.10.3 and noticed this issue.  When I followed the instructions provided by uniblack, the standby value never showed up.  Is 10.10.3 different or it because I have NullCPUPowerManagment.kext installed?  Would "sudo pmset -a hibernatemode 0" do the trick?

 

My pmset output after doing "pmset -a standby 0":

 

$ pmset -g live

Active Profiles:

AC Power -1*

Currently in use:

 hibernatemode        3

 womp                 1

 networkoversleep     0

 sleep                0

 Sleep On Power Button 1

 ttyskeepawake        1

 hibernatefile        /var/vm/sleepimage

 disksleep            10

 displaysleep         0

This happens to me to. Using clover 3241.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By kingoffright
      Dear all,
       
      I have a external harddisk about 500GB, I installed the clover into it and the harddisk is GPT format, below is the 3 partitions details:
      FS01: EFI - disk0s1 - fat32
      FS02: install mac  image - disk0s2 -  hfs+
      FS03: install windows 10 - disk0s3 - fat32
       
      I can use this external harddisk to install Mac without issue, I use below steps to install windows 10
      enter the FS03:
      cd to efi/boot/ and excuete bootx64.efi
      after pop up the windows install screen, i click next and it shows error 'A media driver your computer needs is missing...' and the installation can not go any further.
      Firstly I use ultraiso to write the windows 10 image to a flash disk and no issue to start install window 10 so the image is working fine. Since I dont know how to write
      a wiindow installation image into harddisk partition, I used winrar extra all the files into disk0s3, am I missing some steps or actually clover not support to install windows
      by partitions, apprecating any helps.
       
    • By kushwavez
      Acer Aspire V15 V5-591G - Catalina 10.15.1
      This post will no longer updated, go for the osxlatitude link for further updates
      Original and updated link:
      https://osxlatitude.com/forums/topic/11355-acer-aspire-v-15-v5-591g-catalina-windows-10/
      (Note: mine is 55TU version, but the bootpack will work fine with another versions of 591G, for example: V5-591G-71K2, -764Z, -59PU, etc.)
      Specifications:
      - Motherboard: USOPP_SLS (Skylake-H PCH)
      - BIOS: Insyde Corp. v 1.15
      - CPU: Intel Core i5-6300HQ 2.3 GHz (Skylake)
      - GPU: NVIDIA GeForce GTX 950M 2 GB (Optimus) & Intel HD Graphics 530
      - RAM: SK hynix 4 GB DDR4 (Later I bought + KINGSTON 4 GB) 2133 MHz
      - WiFi + Bluetooth: Qualcomm Atheros QCNFA344A 5 GHz (Later -> Broadcom BRCM94352Z M.2 5 GHz WiFi + 4.0 Bluetooth)
      - Audio: Realtek HD Audio: ALC 255 
      - Ethernet: Realtek RTL8168/8111
      - Card Reader: Realtek USB 2.0 Card Reader (USB2.0-CRW)
      - Webcam: HD Webcam
      - HDD: TOSHIBA MQ01ACF032 320 GB HDD
      - SSD: SPCC M.2 230 GB SSD
      - Display: 1366x768 (15.6", Matte)
      - Battery: 6 cell 56Wh / 5040mAh
      - Connectors: 
      1x SD Card Reader 2x USB 3.0 (1x USB Charging), 1x USB 2.0 1x VGA 1x HDMI 1x 3.5mm microphone/audio combined jack connector 1x Ethernet (Rj-45) - Keyboard & Touchpad: Multi-Touch & Multi-gestures ELAN 501 Touchpad, Backlight Keyboard.
      Working:  
      - Wi-Fi (with BCM94352Z)
      - Bluetooth hand-off (With BCM94352Z)
      - Full Graphics enabled on HD 530: ig-platform-id: 0x191b0000 (HD 530 Mobile)
      - Display: if default colour profile is corrupted (blue is not actual blue but purplish) Use "Rec. ITU-R BT. 709-5" Color Profile (System Pref. -> Displays -> Color)
      - HDMI & VGA Outputs: AppleGraphicsDevicePolicy.kext Clover patch
      - Audio (ALC 255): (Internal Speakers, Internal Microphone, Headphone jack with AppleALC, ALCPlugFix -> layout-id=17)
      - Ethernet Realtek 8168/8111: RealtekRTL8111.kext
      - App Store, Messages, FaceTime, Siri, iCloud (native)
      - Integrated webcam (native)
      - 3.0 USB (native)
      - Touchpad and Keyboard (ELAN501): Fn keys are good, the weird thing is the Brightness key. On my keyboard it's Pause Break:Br-up, Fn+F12:Br-dwn-> To fix this try Karabiner (VoodoPS2Controller.kext), - for gestures try SmartTouchpad drivers
      - Battery info: Install ACPIBatteryManager.kext with Kext Utility or other installer.
      - Sleep Mode
      - SSD with TRIM enabled (to enable trim, open Terminal and write "sudo trimforce enable")
      Not working:
      - Original Wi-Fi (Qualcomm Atheros QCNFA344A):  unsupported, you need switch to BCM94352Z or just use a mini usb wifi dongle.
      - NVIDIA GeForce GTX 950M: Optimus not supported.
      - Card Reader: Unsupported -> Can't really fix because I don't have any SD Card at the moment, maybe can be fixed by adding Prod & Ven IDs to AppleStorageDevices.kext, I never used it anyway. name: "USB2.0-CRW" Prod ID: "0x0129" Ven ID: "0x0bda  (Realtek Semiconductor Corp.)"
      For Wi-Fi:
      - 1st method: You can choose an external USB wifi dongle (I used TP-Link Archer T1U (5GHz support), TP-Link has official macOS drivers, you just need to install it
      - 2nd and I think the best method: Replace your M.2 Qualcomm Card with a compatible BCM94352Z card (you will have hand-off Bluetooth too), just install the kexts (enabled with BrcmFirmwareRepo.kext, BrcmPatchRAM2.kext, FakePCIID.kext, FakePCIID_Broadcom_WiFi.kext, they're all in my attached zip). You could buy this card from ebay, aliexpress, or amazon
       
      Issues:
      - None
      BIOS Settings:
      - BIOS version 1.15 (irrelevant)
      - Secure Boot: Disabled
      - Touchpad: Advanced
      - Boot mode: UEFI
      Getting ready for Installation:
      - Download the Catalina install zip (bootpack & postinstall): acer_aspire_V591G-55TU_cata.zip
      Installation:
      - Create an installer with any method you know (- Mac: createinstallmedia - Windows: Transmac, Vmware, Win32diskimager)
      - Copy my Clover folder to the USB's EFI folder
      - Boot with the Installer USB
      - If you stuck in boot, reboot and in the Clover bootloader select "config_debug.cfg" -> you'll have more informations about the freeze
       
      Please open the README.rtf in my install zip for more informations about the USB Installer & Post installation!
      On Catalina the System folder is read-only, so you need to remount in rw to modify System/Library. 
      If you have a single RAM and getting panic at boot, then you need to edit the "config.plist" with these (SMBIOS->after "Version 1.0"):
      ->Edit "Frequency" and "Size" to match your RAM values
      <key>Version</key> <string>1.0</string> <key>Memory</key> <dict> <key>Channels</key> <integer>1</integer> <key>SlotCount</key> <integer>1</integer> <key>Modules</key> <array> <dict> <key>Slot</key> <integer>0</integer> <key>Size</key> <integer>8192</integer> <key>Frequency</key> <integer>2133</integer> <key>Type</key> <string>DDR4</string> </dict> </array> </dict> </dict>  
      PowerManagement  fix:
      Set HWPEnable=YES in Clover (already set), CPUFloor to "700", Frequency to "2300" and "3200"(Normal and Turbo, if you have i7-6700HQ version then it should be "2600", "3500") and "FrequencyVectors" from "0x0d000000" to "0x07000000" in "S/L/E/IOPlatformPluginFamily.kext/Contents/PlugIns/X86PlatformPlugin.kext/Contents/Resources/Mac-A5C67F76ED83108C.plist", MSR _xcpm_idle Patch to KernelToPatch in Clover (If you have High Sierra, change "MatchOS" to 10.13):

      <key>KernelToPatch</key> <array> <dict> <key>Comment</key> <string>MSR 0xE2 _xcpm_idle instant reboot(c) Pike R. Alpha</string> <key>Disabled</key> <false/> <key>Find</key> <data> ILniAAAADzA= </data> <key>MatchOS</key> <string>10.14</string> <key>Replace</key> <data> ILniAAAAkJA= </data> </dict> </array> Reboot, and it's 800MHz in idle state, same on Windows.
       

      Elan SmartTouchpad
      I only use scrolling, one-, double- & tripletap
      If you want to try other gestures go to this link for more informations, options (v4.6.5) ->  DETAILS ABOUT THE SMART TOUCHPAD DRIVER FEATURES
      Fn Brightness keys not working with this, tried several things without success. With VoodoPS2Controller it's working, but you'll have no gestures (neither scrolling).
       
       
      Before updating to a new version of Catalina please update kexts (and clover if necessary) to newer versions to avoid kernel panics.
      Generate a serial number with Clover Configurator.app (open up your config.plist with CC then -> SMBIOS -> Serial Number -> Generate New)
       
      Catalina & Windows 10 Dual-Boot:
      Dual-boot clean install (on one drive), UEFI Only:
       
       Boot into your Mac installer, Create 2 partitions in GUID table (1 for Win (I used FAT32 but I think it doesn't matter what you choose), 1 for Mac),   Install Mac, boot with your USB, mount your EFI partition (use terminal or an EFI mounter app), create an EFI folder (if there is no folder), copy the CLOVER folder I attached to the EFI folder, restart,  Boot into your Win installer, Format the partition you created for Win, install.   Now, it's automatically booting into Windows. To use Clover open cmd in administrator, type:  bcdedit /set {bootmgr} path \EFI\CLOVER\CLOVERX64.efi       5.  You're done! It will booting into Clover when you start the system, and you can select Win or Mac (or another OS if installed on a 3rd partition).
       
      Dual-boot with Windows installed first (on one drive), UEFI Only:
      If you already have Windows and you don't want to lose all your data there is a hope:
      I created a video from this restore method: [Hackintosh] Dual-Boot High Sierra & Windows - when Windows already installed - no data waste - UEFI
      You need bootable Mac Installer and a full system restore image (link is in my video's description).
      (You may see errors if your EFI partition is not 200 MB)
       Boot into your Windows, resize your partition or create one for Mac.  Boot into your Mac installer and in Disk Utility format the partition you created.  Restore from image: select your full system restore image.  When it's finished restoring you just need to restart, then boot to the system with your usb.  When you successfully booted to Mac desktop, mount your EFI partition (use terminal or an EFI mounter app), open EFI, you will see there is a Microsoft folder already (don't touch that!). Copy my CLOVER folder to the EFI folder then Restart.  Now, it's automatically booting into Windows. To use Clover open cmd in administrator, type:  bcdedit /set {bootmgr} path \EFI\CLOVER\CLOVERX64.efi       7.  You're done! You can select your old Windows and your new macOS!
      (Only tried with Windows 8/8.1/10. I don't know Windows 7,etc.)
       
      IF YOU GETTING ERRORS DURING MAC RESTORE:
      - Make sure you have partitions in GPT
      - Windows using 100 MB EFI and will annoy the Mac restore. Don't worry, just ignore the errors.
       
      IF YOU GETTING ERRORS DURING WINDOWS INSTALLATION (could not be formatted, etc):
      - Make sure you have GPT partitions, and GPT (UEFI) installer, also disconnect all external storage drives (except the installer USB)
       
      IF YOU USED RESTORE METHOD THEN CAN'T MOUNT YOUR EFI PARTITION (No EFI partition found):
      - It's because your EFI is not 200 MB or not an "Apple" original EFI,  but do not worry, try another EFI mounter, or mount from terminal (I used EFI mounter v3: Getting errors, but you can mount and use without problem)
      - You also could "mount" the EFI from Windows:
      1st method: open cmd in administrator mode and type:
      diskpart list vol (Now select the "System" volume,(FAT 32) For example I select 4) sel vol 4 list part (Select System type partition, for example 2) sel part 2 assign letter=b (This will "mount" your EFI partition) Open Explorer++ or TotalCommander in administrator mode to manage EFI remove letter=b (This will "unmount" your EFI) 2nd method: open cmd in administrator mode and type:
      mountvol b: /s (This will mount your EFI) Open Explorer++ or TotalCommander in administrator mode to manage EFI mountvol b: /d (This will unmount your EFI) Thanks to all OSXLatitude members for helping me out! (Jake Lo, Hervé, Bronxteck, black.dragon74)!
      Notes:
      2019.11.03: Enabled SIP caused a lots of issues so now it's disabled -> updated bootpack
      2019.11.02: Updated to 10.15.1 -> no problem when/after installing
      2019.10.09: Installed macOS Catalina 10.15 -> Updated Clover, kexts & config.plist -> no problem so far
      2019.08.18: Updated to 10.14.6 -> no problem when/after installing
      2019.06.01: Updated to 10.14.5 -> no problem when/after installing
      2019.04.25: Optimized touchpad scrolling -> updated install files
      2019.03.30: Fixed USB 3.0 ports, fixed Bluetooth crashes after sleep -> updated bootpack
      2019.03.28: Updated to 10.14.4. Unexpected crashes while updating to 10.14.4 -> fixed by updating Clover to the latest (v4910) version. Bluetooth crashes appeared -> fixed by downgraded Brcm*.kexts. Updated bootpack.
      2019.02.24: Bluetooth crashes after sleep -> fixed, updated bootpack. 
      2019.02.22: Updated to 10.14.3. Fixed HDMI Audio by installing "FakePCIID_Intel_HDMI_Audio.kext" -> fixed freezing during boot. Fixed brightness levels by installing "AppleBacklightFixup.kext". Also updated bootpack & postinstall zip down in attachments.
      2019.01.21: Removed FakeSMC.kext, SMCHelper-64.efi, replaced by VirtualSMC.kext, VirtualSMC.efi because I got random freezes when booting system (kextd stall[0], (120s): 'AppleACPICPU' -> CPU is at 100%, fans are spinning fast), also updated bootpack in the attachments "acer_aspire_v591g-55tu_clover.zip" -> Freeze continued, brought back FakeSMC, deleted VirtualSMC (caused BT crashes).
      2019.01.18: HDMI Audio is fixed, I didn't do anything HDMI Audio is not fixed, sometimes it worked but most likely not. (no idea why)
      2018.12.09: Updated to 10.14.2 -> did without any complication
      2018.11.28: Fixed combo-jack garbage sound output by installing ALCPlugFix and CodecCommander.kext
      2018.11.01: Updated to 10.14.1 -> HDMI & VGA ports are gone again. -> Fixed by "AppleIntelSKLGraphicsFramebuffer.kext" rollback from 10.14.
      2018.09.28: Updated to Mojave 10.14 -> Fixed HDMI & VGA Outputs by adding "AppleGraphicsDevicePolicy.kext" patches to config.plist, HDMI audio not working
    • By holyfield
      There are plenty of users who suggest to use darkwake=8 or darkwake=10 or darkwake=0 boot args to solve sleep issues.
       
      Are these suggestions valid at all?
       
      For first we have to clarify something about Darkwake. The DarkWake feature was for first introduced in Mac OS X Lion. This feature allows to wake up certain parts of computer from sleep, while leaving other parts in sleep mode (for example display etc). Darkwake = display stays dark when comp wakes and performs some tasks. When tasks are done, comp should go back to sleep. But on Hack's Darkwake caused several problems, for example comps went into state, where those become inaccessible and forced reboot were needed. On some cases Darkwake caused reboots too and.. Darwake is related to Power Nap which is available since OS X Mountain Lion.
       
      Disclaimer! Before posting below please read it:
       
      If you really want to get some help from Hackintosh community, learn how to leave others out of guesswork! Learn how to collect diagnostics data which can help others on solving your case. It's annoying to ask over and over to provide some diagnostics related to Hack issue. That's why there are millions on unanswered posts on Hackintosh forums, their authors doesn't respect other's actually, they do not think out of their own shoes. Your first question before posting should be, what data is needed to help me, do I have provided all data available to help me immediately?
       
       
      Darkwake and XNU
       
      Darkwake is part of XNU. 
       
       
      Darkwake behaviours are defined in IOPMrootDomain.cpp.
       
      The easiest way to check XNU version is to use terminal command uname -av. 
       
      uname -av Darwin MyHack.local 19.2.0 Darwin Kernel Version 19.2.0: Sat Nov 9 03:47:04 PST 2019; root:xnu-6153.61.1~20/RELEASE_X86_64 x86_64 According to this macOS Catalina 10.15.2 uses XNU 6153.61.1.
       
      The latest publicly available source code of XNU is 4903.241.1. So we cannot check source code of latest XNU's. Please correct me if I'm wrong. 
       
      Code below reveals that boot arg darkwake correlates to enum gDarkWakeFlags.
      PE_parse_boot_argn("darkwake", &gDarkWakeFlags, sizeof(gDarkWakeFlags));  
      So lets check the xnu-4903.241.1/iokit/Kernel/IOPMrootDomain.cpp for Darkwake flags:
      // gDarkWakeFlags enum { kDarkWakeFlagHIDTickleEarly = 0x01, // hid tickle before gfx suppression kDarkWakeFlagHIDTickleLate = 0x02, // hid tickle after gfx suppression kDarkWakeFlagHIDTickleNone = 0x03, // hid tickle is not posted kDarkWakeFlagHIDTickleMask = 0x03, kDarkWakeFlagAlarmIsDark = 0x0100, kDarkWakeFlagGraphicsPowerState1 = 0x0200, kDarkWakeFlagAudioNotSuppressed = 0x0400 }; Let's translate these values into decimals and easier to read strings
      HID Tickle Early = 1 HID Tickle Late = 2 HID Tickle None = 3 HID Tickle Mask = 3 Alarm Is Dark = 256 Graphics Power State 1 = 512 Audio Not Suppressed = 1024 HID = Human-interface devices, such as keyboards, pointing devices, and digitizers like pens and touch pads.
       
      As flags are used for bitwise operations, then we can easily notice that combinations 10 and 8 are for sure invalid now. darkwake=8 equals actually to darkwake=0 and darkwake=10 equals to darkwake=2.
       
      If we check older XNU versions, then these values are removed since XNU 2782.1.97 ( = Yosemite ):
      kDarkWakeFlagIgnoreDiskIOInDark = 0x04, // ignore disk idle in DW kDarkWakeFlagIgnoreDiskIOAlways = 0x08, // always ignore disk idle kDarkWakeFlagIgnoreDiskIOMask = 0x0C According to this boot flags darkwake=8 and darkwake=10 are obsolete if you have Yosemite or newer macOS as related flags are removed from XNU. 
       
      What is the default value for darkware boot arg?
       
      According to XNU source code the default value of boot arg darkware is 3 (darkwake=3):
      static uint32_t gDarkWakeFlags = kDarkWakeFlagHIDTickleNone; We have to clarify that xnu 4903.221.2 is used since macOS Mojave 10.14.1 and xnu 4903.241.1 is used since macOS Mojave 10.14.3. How about the latest macOS? Sadly there is no source code available. 
       
      To figure out which value is defined on latest kernel we have to download the latest available Kernel Debug Kit, which is 10.15.1 build 19B77a. By using Hopper Disassembler we see that default value on macOS Catalina 10.15.1 for gDarkWakeFlags is 0x00000003, which equals to 3.
      __ZL14gDarkWakeFlags: // gDarkWakeFlags ffffff80012b93b0 dd 0x00000003 So by default Darkwake should not post any HID Tickle's. This also reveals the secret why some users encounter issues with frozen peripheral device's on Hack's when Power Nap is enabled. To use Darkwake on Hack's require very well configured USB ports.
       
       
      Power Nap & Darkwake
       
      If you have Power Nap disabled then computer shouldn't wake automatically. On most cases darkwake boot arg affects how computers should behave on case of Power Nap enabled. If everything is configured properly you do not need define darkwake boot flag at all. Anyhow, there might be motherboards, which benefit from user defined value. But keep in mind that darkwake=8 and darkwake=10 are obsolete since Yosemite.
       
       
      Which values are valid for darkwake?
       
      As flags are used for bitwise operations, then these values are valid:
       
      darkwake=0
      darkwake=1 (darkWakePostTickle behaviour)
      darkwake=2 (darkWakePostTickle behaviour)
      darkwake=3 (darkWakePostTickle behaviour)
      darkwake=256
      darkwake=257
      darkwake=258
      darkwake=259
      .. and so on...
       
      As I'm not familiar how PE_parse_boot_argn function exactly works, I cannot say much about boot arg darkwake=0. According to source code there is no any checks or behaviours defined for darkwake=0. There is a huge chance that using darkwake=0 actually equals to darkwake=3. I hope someone can clarify from source code what exactly happens if darkwake=0 is used trough PE_parse_boot_argn, but it's obvious that darkwake=0 does not equal to darkwake=NO (or darkwake=FALSE). darkwake=0 does not disable power nap, it only affects HID tickle. Please note that darkwake=3 is combination of flags 1 & 2. 1 + 2 = 3. On case we say to the system to do early (1) and later (2) HID tickle both (3), there is no any tickle at all.
       
      Some code samples from IOPMrootDomain:
      else if (!darkWakeMaintenance) { // Early/late tickle for non-maintenance wake. if (((gDarkWakeFlags & kDarkWakeFlagHIDTickleMask) == kDarkWakeFlagHIDTickleEarly) || ((gDarkWakeFlags & kDarkWakeFlagHIDTickleMask) == kDarkWakeFlagHIDTickleLate)) { darkWakePostTickle = true; } } if (darkWakePostTickle && (kSystemTransitionWake == _systemTransitionType) && (gDarkWakeFlags & kDarkWakeFlagHIDTickleMask) == kDarkWakeFlagHIDTickleLate) { darkWakePostTickle = false; reportUserInput(); } if (powerState > maxPowerState) { DLOG("> plimit %s %p (%u->%u, 0x%x)\n", service->getName(), OBFUSCATE(service), powerState, maxPowerState, changeFlags); *inOutPowerState = maxPowerState; if (darkWakePostTickle && (actions->parameter & kPMActionsFlagIsDisplayWrangler) && (changeFlags & kIOPMDomainWillChange) && ((gDarkWakeFlags & kDarkWakeFlagHIDTickleMask) == kDarkWakeFlagHIDTickleEarly)) { darkWakePostTickle = false; reportUserInput(); } } void IOPMrootDomain::reportUserInput( void ) { #if !NO_KERNEL_HID OSIterator * iter; OSDictionary * matching; if(!wrangler) { matching = serviceMatching("IODisplayWrangler"); iter = getMatchingServices(matching); if (matching) matching->release(); if(iter) { wrangler = OSDynamicCast(IOService, iter->getNextObject()); iter->release(); } } if(wrangler) wrangler->activityTickle(0,0); #endif } As you see from code examples above, there is no any huge mystery about darkwake boot arg and you should use it mostly on case when you really need to manipulate HID tickle behaviour. On most cases it's more important to properly configure you system power management rather than paying with darkwake boot arg, which can be done via terminal command pmset.
       
       
      Power Management
       
      To check Power Management settings use terminal command:
      pmset -g Also you can use Hackintool to check power management settings:
       

       
      Power Management Settings explained:
       
      displaysleep - display sleep timer; replaces ’dim’ argument in 10.4 (value in minutes, or 0 to disable) disksleep - disk spindown timer; replaces ’spindown’ argument in 10.4 (value in minutes, or 0 to disable) sleep - system sleep timer (value in minutes, or 0 to disable) womp - wake on ethernet magic packet (value = 0/1). Same as "Wake for network access" in the Energy Saver preferences. ring - wake on modem ring (value = 0/1) powernap - enable/disable Power Nap on supported machines (value = 0/1) proximitywake - On supported systems, this option controls system wake from sleep based on proximity of devices using same iCloud id. (value = 0/1) autorestart - automatic restart on power loss (value = 0/1) lidwake - wake the machine when the laptop lid (or clamshell) is opened (value = 0/1) acwake - wake the machine when power source (AC/battery) is changed (value = 0/1) lessbright - slightly turn down display brightness when switching to this power source (value = 0/1) halfdim - display sleep will use an intermediate half-brightness state between full brightness and fully off (value = 0/1) sms - use Sudden Motion Sensor to park disk heads on sudden changes in G force (value = 0/1) hibernatemode - change hibernation mode. Please use caution. (value = integer) hibernatefile - change hibernation image file location. Image may only be located on the root volume. Please use caution. (value = path) ttyskeepawake - prevent idle system sleep when any tty (e.g. remote login session) is ’active’. A tty is ’inactive’ only when its idle time exceeds the system sleep timer. (value = 0/1) networkoversleep - this setting affects how OS X networking presents shared network services during system sleep. This setting is not used by all platforms; changing its value is unsupported. destroyfvkeyonstandby - Destroy File Vault Key when going to standby mode. By default File vault keys are retained even when system goes to standby. If the keys are destroyed, user will be prompted to enter the password while coming out of standby mode.(value: 1 - Destroy, 0 - Retain)  
      If you want to disable proximitywake the this command should be used:
      sudo pmset -a proximitywake 0  
      Recommended settings for Hack's are:
      sudo pmset -a hibernatemode 0 sudo pmset -a proximitywake 0 sudo pmset -a powernap 0 Settings above disable Hibernate, Bluetooth wake by iDevices and Power Nap.
       
      To check what might prevent computer from going into sleep we can pmset tool:
      pmset -g assertions  
      So, before using blindly darkwake boot arg to solve some sleep issues, make instead sure that USB ports and Power Management settings of your Hack are configured properly.
       
       
      Sleep & Wake
       
      Quite often Hack's users have sleep/wake issues because they don't pay attention to the fact that Apple's macOS is developed for Apple hardware in mind, not regular PC's. 
       
      Of course sleep mode isn't something that Apple has invented first. Since December 1996 ACPI superseded APM. ACPI - Advanced Configuration and Power Interface. APM - Advanced Power Management. The ACPI specification defines several states for various hardware components and devices. There are global "Gx" states and sleep "Sx" states specified.
       
      Gx Name Sx Description G0 Working S0 The computer is running and the CPU executes instructions. "Awaymode" is a subset of S0, where monitor is off but background tasks are running G1 Sleeping S1 Power on Suspend (POS): Processor caches are flushed, and the CPU(s) stops executing instructions. The power to the CPU(s) and RAM is maintained. Devices that do not indicate they must remain on may be powered off S2 CPU powered off. Dirty cache is flushed to RAM S3 commonly referred to as Standby, Sleep, or Suspend to RAM (STR): RAM remains powered S4 Hibernation or Suspend to Disk: All content of the main memory is saved to non-volatile memory such as a hard drive, and the system is powered down G2 Soft Off S5 G2/S5 is almost the same as G3 Mechanical Off, except that the power supply unit (PSU) still supplies power, at a minimum, to the power button to allow return to S0. A full reboot is required. No previous content is retained. Other components may remain powered so the computer can "wake" on input from the keyboard, clock, modem, LAN, or USB device G3 Mechanical Off   The computer's power has been totally removed via a mechanical switch (as on the rear of a PSU). The power cord can be removed and the system is safe for disassembly (typically, only the real-time clock continues to run using its own small battery)  
      Since Mac OS X Lion Apple is using DarkWake, which were wrapped into Power Nap on OS X Mountain Lion. To understand and fix macOS sleep issues we also need the knowledge about sleep states which macOS comps may have. To check log of macOS computers sleep/wake we can use pmset tool. Following terminal code prints sleep/wake history.
      pmset -g log|grep -e " Sleep " -e " Wake "  
      I to check more closely sleep history then we can recognise that macOS has at least 3 different sleep "modes":
       
      Software sleep Idle sleep Maintenance sleep  
      Software sleep
      Software sleep is trigged by computer user or by some software, which is configured to put comp sleep after certain tasks done.
       
      Idle sleep
      Idle sleep is triggered by idle timer. Each time user interacts with computer idle timer is reset. If users doesn't interact within idle timer countdown time, then Idle sleep is triggered.
       
      Maintenance sleep
      If user has enabled "Wake for Ethernet network access", then macOS goes from Idle or Software sleep into Maintenance sleep immediately. 
       
      Power Nap
      If Power Nap is enabled, then computer wakes up automatically after certain period of time, handles certain tasks and goes back to sleep. Apple's documentation reveals that behaviour of power nap doesn't depend only macOS version running on comp but at hardware and it's firmware too. Documentation clearly states that comps made on different time behave differently. which points directly that Power Nap is related to the hardware/firmware too.
       
       
      According quote above we have to very carefully choose which firmware is emulated on Hack. Changing SMBIOS on Clover/Opencore can help to solve sleep issues or cause them.
       
      An example of sleep log when powernap is enabled:
      2020-01-05 09:03:23 +0200 Sleep Entering Sleep state due to 'Idle Sleep': Using AC (Charge:0%) 21 secs 2020-01-05 09:04:29 +0200 Sleep Entering Sleep state due to 'Maintenance Sleep': Using AC (Charge:0%) 1945 secs 2020-01-05 09:37:39 +0200 Sleep Entering Sleep state due to 'Maintenance Sleep': Using AC (Charge:0%) 3187 secs 2020-01-05 10:31:33 +0200 Sleep Entering Sleep state due to 'Maintenance Sleep': Using AC (Charge:0%) 12467 secs 2020-01-05 14:00:06 +0200 Sleep Entering Sleep state due to 'Maintenance Sleep': Using AC (Charge:0%) 11312 secs 2020-01-05 17:08:40 +0200 Wake DarkWake to FullWake from Normal Sleep [CDNVA] : due to UserActivity Assertion Using AC (Charge:0%)  
      An example of sleep log, when ethernet wake and power nap is disabled:
      2020-01-03 18:15:43 +0200 Sleep Entering Sleep state due to 'Idle Sleep':TCPKeepAlive=inactive Using AC (Charge:0%) 3210 secs 2020-01-03 19:09:13 +0200 Wake Wake from Normal Sleep [CDNVA] : due to XDCI CNVW/HID Activity Using AC (Charge:0%) 207 secs 2020-01-03 19:12:40 +0200 Sleep Entering Sleep state due to 'Idle Sleep':TCPKeepAlive=inactive Using AC (Charge:0%) 165903 secs 2020-01-05 17:17:43 +0200 Wake Wake from Normal Sleep [CDNVA] : due to XDCI CNVW/HID Activity Using AC (Charge:0%) As we see from log above, computer stays in sleep without any wakes and no 'Maintenance Sleep'.
       
      So there are several variables which have effect on your computer sleep/wake behaviour and the solution that helped another people, might be useless or even worse on you case.
       
      ...
    • By Cwtf
      I just made a clean install of High Sierra on a 1TB crucial ssd. Installed clover Clover_v2.5k_r5070 into the EFI of this ssd, but when I tried to make it my default boot drive, the clover screen wouldn't come up, and left a black screen.
      I tried using the Olarilia usb drive and clover did the same thing.  The only way I can currently boot is to use my old drive with clover v2.4k_4945 then select  my new drive from the clover menu.   
       
      Do I need to install v2.4k on my new drive or is there a way I can get v2.5k working?
       
      I have a GA-x79-ud5 motherboard, AMD  rx580 graphics card and use a Sony 4k tv as my monitor.
    • By holyfield
      Description
       
      Idle Sleep issue detected on both, genuine Mac's and Hack's, where have installed latest macOS Catalina 10.15.2.
       
      Currently known about the issue:
      Issue noticed by various users after upgrading to macOS 10.15.2 Both genuine Mac's and Hack's are affected. Comps which are running on battery power are not affected as agent is disabled at battery power. macOS 10.15.2 replaces previous version of parsec-fbf agent. macOS 10.15.2 kernel uses new version of XNU 6153.61.1. macOS 10.15.1 kernel uses XNU 6153.41.3. Bot the macOS 10.15.2 and macOS 10.15.0 use the same com.apple.parsec-fbf.plist launch agent definition file. Not sure are all comps with 10.15.2 affected or only with specific system configuration Issue is not reported on any older macOS versions this far. Only Idle Sleep is affected, Software Sleep works fine. Agent can be killed via Activity Monitor, but it revives immediately again and still prevents the Idle Sleep Agent does not stop display to go into sleep, which makes hard to notice the issue on genuine Macs. Disabling parsec-fbf agent solves the issue  
      CoreParsec.framework is part of Siri
       
      pares-fbf is part of CoreParsec.framework which is installed on /System/Library/PrivateFrameworks/CoreParsec.framework.
       
      Info from /System/Library/PrivateFrameworks/CoreParsec.framework/Versions/Current/Resources/Info.plist:
      Bundle identifier: com.apple.siri.parsec.CoreParsec Privacy - Location Usage Description: Spotlight, Messages, Lookup & Safari Suggestions use your location to provide more accurate local results.  
       
      Content of com.apple.parsec-fbf.plist which defines the agent:
      <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>EnablePressuredExit</key> <true/> <key>EnableTransactions</key> <true/> <key>Label</key> <string>com.apple.parsec-fbf</string> <key>LaunchEvents</key> <dict> <key>com.apple.xpc.activity</key> <dict> <key>com.apple.parsec-fbf.flush</key> <dict> <key>AllowBattery</key> <false/> <key>Interval</key> <real>3600</real> <key>Priority</key> <string>Maintenance</string> </dict> </dict> </dict> <key>MachServices</key> <dict> <key>com.apple.parsec-fbf</key> <true/> </dict> <key>POSIXSpawnType</key> <string>Adaptive</string> <key>ProcessType</key> <string>Background</string> <key>Program</key> <string>/System/Library/PrivateFrameworks/CoreParsec.framework/parsec-fbf</string> </dict> </plist>  
      Comparison of parsec-fbf on different Catalina versions:
       
      MD5 (10.15.0/parsec-fbf) = e20c200814c4ce5fcd3ae5af7394e1d1 MD5 (10.15.1/parsec-fbf) = f3fe4e16be71798fd7d3b23be089082e MD5 (10.15.2/parsec-fbf) = a97bb8b8227c063289a6e0d43582b10f  
      parsec-fbf agent binary file's are different in each macOS Catalina version. But seems that the biggest change is made in Catalina macOS 10.15.2.
       
      Binary comparison:
       
      10.15.0/parsec-fbf = 1 742 192 bytes 10.15.1/parsec-fbf = 1 736 640 bytes 10.15.2/parsec-fbf = 1 802 832 bytes  
      Left file: 10.15.0/parsec-fbf Right file: 10.15.1/parsec-fbf 1561745 same byte(s) 58019 left orphan byte(s) 52467 right orphan byte(s) 122428 difference byte(s) Left file: 10.15.1/parsec-fbf Right file: 10.15.2/parsec-fbf 1450705 same byte(s) 129662 left orphan byte(s) 195854 right orphan byte(s) 156273 difference byte(s) Left file: ./10.15.0/parsec-fbf Right file: ./10.15.2/parsec-fbf 1443572 same byte(s) 150586 left orphan byte(s) 211226 right orphan byte(s) 148034 difference byte(s)  
      According to knowledge that issue with parsec-fbf agent is not reported before Catalina 10.15.2 and each Catalina versions has his own versions of parsec-fbc agent, then we can conclude that issue is specific to the Catalina 10.15.2 only, until reported otherwise. So no need to concern if you have macOS 10.15.1 or older. Anyway, if you upgrade to 10.15.2 and get sleep issues, you have to check your system for issue described in this post. On some cases this might look like Buletooth issue but actually it's not, because when yo disable parsec-fbf agent, sleep works immediately again.
       
      How to check?
       
      pmset -g assertions  
      If computer has Idle Sleep issue and com.apple.parsec-fbf.flush is listed in assertions, then this might be the reason of why Idle Sleep fails.
       
      An example:
      pid 321(UserEventAgent): [0x00000145000b82a0] 03:09:42 BackgroundTask named: "com.apple.parsec-fbf.flush"  
      How to check sleep log?
      pmset -g log|grep -e " Sleep " -e " Wake "  
      Reason
       
      It's unknown what exactly causes this issue. Somehow parsec-fbf agent goes into state where it prevents comp to go into Idle Sleep. Probably the latest version of parsec-fbf agent introduced in macOS 10.15.2 has some kind of bug which resets idle timer. As macOS kernel uses new version of XNU (6153.61.1), this might be somehow related to both, parsec-fbf agent and kernel.
       
      Current solution:
       
      Please note that just disabling Siri doesn't help, as parsec-fbf agent is responsible for sending Spotlight, Messages, Lookup & Safari searches data too, not only Siri searches.
      launchctl unload -w /System/Library/LaunchAgents/com.apple.parsec-fbf.plist  
      As this agent sends and flushes analytical data (Spotlight, Messages, Lookup & Safari searches) sent to Apple, no any harm happens to you, if you disable this agent, Apple just cannot spoof after you anymore. 
       
      parsec-fbf agent reads and writes files in users Cache folder: ~/Library/Caches/com.apple.parsecd. If you want flush these, you can do it manually.
       
      Flushing spoofing cache manually:
      cd ~/Library/Caches rm -R com.apple.parsecd  
       
       
×