Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


tonyx86 last won the day on April 11

tonyx86 had the most liked content!


About tonyx86

  • Rank
    InsanelyMac Sage

Recent Profile Visitors

3,571 profile views
  1. I'm currently experimenting with a few changes suggested by @glasgood here that seem to have improved display wake behavior. I'm still testing, so these changes are NOT yet included in my EFI baseline included in the EliteDesk.zip archive attached to post #1. Added igfxonln=1 to boot args: results in consistent and reliable display wake from sleep - even after repeated sleep / wake cycles Changed darkwake=2 to darkwake=3: appears to result in simultaneous display wake from sleep (with darkwake=2, one display may wake a second or two before the other) Added igfxagdc=0 to replace the AGDC kext patch and disabled the AGDC kext patch: no change in behavior, but it should be more reliable for future versions of macOS to use WhateverGreen to disable AGDC My current CLOVER config.plist is attached. If you use this config.plist, you must replace all XX-MASKED-XX values with your own. config.plist.zip
  2. Thank you! Adding igfxonln=1 appears to have improved display wake. I had a kext patch that mimicked igfxagdc=0, so I disabled the kext patch and added boot arg igfxagdc=0 (no difference in behavior as a result of this change). I think that after changing darkwake=2 to darkwake=3, both displays consistently wake simultaneously (where with darkwake=2, one display might wake a second or two before the other), but I'm not certain there is a difference resulting from the darkwake change. With these changes, I don't need to inject EDID - display sleep/wake seems perfect. I'll test for a while before declaring success. My test results for different ig-platform-ids are here. 07009B3E resulted in black screens at boot. 0000923E is best for me. I currently have device-id undefined, so it defaults to 0x3e92 for my i7-8700T / UHD 630. To be honest, I thought that my displays were working perfectly and sleep/wake was working without issues until I started experimenting with injecting EDID. There must be something that I changed that now requires me to use igfxonln=1, but I can't figure out what that change might be. Part of my experimentation included different display color profiles (System Preferences -> Displays -> Color) and I factory-reset my LCD displays. Regardless, it does seem that igfxonln=1 does the trick. Thanks again!
  3. After injecting EDID properties on my HP EliteDesk 800 G4 Mini, I have started noticing changes in sleep/wake behavior. Sometimes my unit doesn't sleep when left unattended and sometimes my unit wakes to dark screens. I have removed the injected EDID properties until I have more time to test. Without injected EDID, my displays sometimes take a few more seconds to wake, but my system consistently sleeps and wakes reliably.
  4. You're very welcome. Glad this helps you. EDIT: I just re-read your post and believe I may have misinterpreted your question/issue. Two possibilities I can think of are I am using DP->DVI adapters, so my graphics device properties set connector type to 0x0004. If you have DP ports without DP->DVI adapter, you will need to change your connector type to 0x0400. Your USB port mapping may be different. The USB port mapping for the micro may be different from the mini. Try removing SSDT-UIAC.aml from EFI/CLOVER/ACPI/patched and enable the USB port limit patches in config.plist. If you are using Clover Configurator, open the config.plist, navigate to Kernel and Kext Patches, enable the two USB port limit patches (I have them disabled) and save your config.plist. Clover Configurator: Kernel and Kext Patches If this "fixes" your problem, you will need to create your own USB port mapping for the micro. I used Hackintool to create the SSDT-UIAC.aml for the mini.
  5. Have you (or anyone else) looked at the M.2 NGFF WLAN BCM94360NG 802.11ac Bluetooth 4.0 WiFi Card? I don't need Wi-Fi/Bluetooth in my HackMini8,1 (not yet), so I haven't replaced the factory-installed Intel card. I'm wondering if the BCM94360NG fits without modification in the Wi-Fi M.2 slot?
  6. EDIT: After posting this, I have been noticing a change in sleep / wake behavior. Sometimes, my system doesn't sleep and sometimes it wakes to dark screens. I have removed my injected EDID properties until I get time to test this more thoroughly. If you inject EDID properties in order to resolve slow display wake from sleep, be prepared to test and confirm proper sleep/wake operation. ------------------------------------------------------------------------------- My displays wake from sleep even faster (now almost immediate) after injecting EDID (created with Hackintool) for each of my displays. Thank you @glasgood for his tip here. I will add this to the config.plist that I include with a future EFI update attached to post #1 in this thread; however, users will need to generate their own EDID patches that are specific to their displays. The EDID for each display is injected with graphics property key AAPL0X,override-no-connect, where X is the display number. EDIT: I prefer my display temperature/color with the unpatched EDID. In order to realize the faster wake benefit without changing my display properties, I copied the detected display EDID (copied EDID from IORegistryExplorer after booting without the AAPL0X,override-no-connect properties) into the AAPL0X,override-no-connect device properties in my config.plist. Now my display color/temps are their default, but the displays wake instantly from sleep.
  7. @glasgood Outstanding work. Very nice bus patching diagram!
  8. @glasgood I'm not sure I understand your system's current state. Did I understand correctly that IM19,2 and IM19,1 didn't work (USB issues), so you're using MM8,1? If that's correct, then am I also correct in understanding that your only remaining display issue is that display wakes one minute after the system wakes? If that's true, what did you do to "fix" wake from sleep? Note that I found that my displays wake faster from sleep after I simplified my graphics device properties as discussed here. @glasgood Unfortunately, I don't know anything about OC, so if the issues have anything to do with the order of kext loading or ACPI patches, I'm at a loss.
  9. I edited my previous post and wanted to make sure you saw this: You may want to try SMBIOS MacModel iMac19,2 if you haven't already. See this post here.
  10. You may also want to play with connector flags. As I recall, the following influenced sleep / wake behavior of my UHD 630 (which is now sleeping / waking perfectly): Intel ME must be enabled (BIOS setting) connector flags must be set (see here when I was experimenting with device properties) @glasgood One other thing: You may want to try SMBIOS MacModel iMac19,2 if you haven't already. See this post here. Good luck!
  11. @glasgood Excellent work! I'm glad my HP EliteDesk 800 G4 Mini guide helped you! You just may inspire me to learn and create an OC solution for my rig. Nice job!
  12. I'm posting this for those who are curious about VRAM and am not suggesting any changes. My configuration baseline is still running with 1536 MB VRAM which is the UHD 630 default and I don't see any performance benefits when running with 2048 MB VRAM. ------------------------------------------------------ The macOS supported UHD 630 VRAM sizes are 0x40000000 (1024 MB), 0x60000000 (1536 MB) and 0x80000000 (2048 MB). When graphics device property framebuffer-unifiedmem is unspecified, VRAM defaults to 1536 MB. When framebuffer-unifiedmem is set to 0x80000000 (Reverse Byte Order 0x00000080), VRAM is 2048 MB. I tried setting framebuffer-unifiedmem to 2048 MB, but don't notice any difference in graphics performance (as measured by GeekBench 5). The only difference I see is that macOS now sees 2048 MB VRAM. *** NOTE *** This guide indicates that patching framebuffer-unifiedmem is not recommended.
  13. Headkaze is definitely the one to help. Would you mind posting your IORegistryExplorer dumps for the two cases (with and without WEG)?
  14. This question is for anyone who has a thorough understanding of WEG and what / how it does its "magic." I'd like to better understand what WEG is doing to patch my UHD 630 graphics (working perfectly with WEG). I have attempted to patch my UHD 630 graphics here without WEG, but after a few reboots, graphics has glitches during boot (before the login prompt) and sometimes graphics boots to black screens (with monitors on). I would appreciate some suggestions from someone who knows how WEG works and what it is doing to help me understand why my "manual" patches here don't work when WEG works fine. What am I missing? EDIT: I suspect that there are other UHD 630 graphics attributes that WEG is defining and that I have not defined with my manual patches. Thank you.
  15. EDIT: After posting this, I have encountered graphics issues following a few reboots. Specifically, there are display glitches before the login prompt appears and sometimes, the system boots to black screens (with monitors on). Clearly, there is something that WEG does that I have not captured in these patches. I am reverting to my WEG baseline and welcome any suggestions for running without WEG. It's not that I don't like WEG - I just want to fully understand what it is doing. ------------------------------------------------------------------------------------ @Zenith432 Your post inspired me to create a Clover config.plist for my UHD 630 that does not require WhateverGreen. See here for the result.