Jump to content

Search the Community: Showing results for tags 'sleep'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • InsanelyMac Lounge
    • Front Page News and Rumors
    • Reader News and Reviews
    • Forum Information and Feedback
  • OSx86 Project
    • New Releases and Updates
    • New Users Lounge
    • Developers Corner
    • Tutorials (The Genius Bar)
    • Technical FAQ
    • OSx86 Installation
    • Post-Installation
    • DSDT and SSDT
    • Hardware Components and Drivers
    • Complete Desktops
    • Notebooks
    • Netbooks
    • Tablets
    • MacMod of the Month
    • Multi-booting and Virtualisation
  • International
    • Your Language
    • Deutsch
    • Español
    • Français
    • Italiano
    • Português
    • Русский
  • Apple World
    • Mac OS X
    • Apple Computers and Hardware
    • iOS Devices
    • Mac Applications
    • Mac Programming and Development
    • iOS Programming and Development
    • Mac Gaming
    • Mac Accessories
  • Discuss and Learn
    • Windows Discussion
    • *nix
    • Apple Opinions and Discussion
    • The Great Debates
    • Internet(s), Servers, and Networks
    • Buying Thoughts, Reviews, and Recommendations
    • Mods and Overclocking
    • The Big Issues [Real Life]
  • Everything Else
    • Creativity
    • Thunderdome (Random Stuff)
    • Laughs
    • The Marketplace


  • Kexts
    • Graphics Cards
    • Audio
    • LAN and Wireless
    • Other
  • Kernels
  • Bootloaders
  • DSDTs
    • Patches
  • Pandora
  • Apps
  • Miscellaneous
  • Customization

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start




Website URL







Found 195 results

  1. Hello everyone, I'm posting a new thread on behalf of myself and a few other members here (konrad11901, blackswords and Dmitry R). We've been experiencing an unstable system after wake. My system is ab Asrock Z97M OC Formula with an i5-4670k, konrad11901 has an MSI B85-G43 Gaming with an i5-4460, blackswords has an MSI PC Mate Z97 with an i5-4690k and Dimitry R has an Asrock Z170M-ITX ac with an i3-6100. I recently got my Z97M OC Formula to replace a GA-Z87MX-D3H which suffered from corrupted memory after long sleep. I'm booting using Clover, with a patched DSDT, and an SSDT generated with PikerAlpha's ssdtPRGen.sh. I've attached the files of my configuration. Soon after wake, the log shows messages such as: 2016-03-29 11:23:21,000 kernel[0]: Unsynchronized TSC for cpu 1: 0x0000000193273184, delta 0x18e0a1aca 2016-03-29 11:23:21,000 kernel[0]: Unsynchronized TSC for cpu 2: 0x0000000193428ced, delta 0x18e0a1aed 2016-03-29 11:23:21,000 kernel[0]: Unsynchronized TSC for cpu 3: 0x00000001935de52f, delta 0x18e0a1aed followed by process crashes, usually culminating in a launchd crash, causing a kernel panic and a reboot: *** Panic Report ***panic(cpu 1 caller 0xffffff800cb9aaa4): launchd exited (signal 8, exit status 0 ) … Thread 3 crashed … We have noticed that the output of pmset -g log | grep -i failure points to various PCIe devices, most notably the graphics card. Here's my output at the moment: 2016-03-29 13:11:50 +0200 Failure Drivers Failure panic during wake due to PEG0(NVDA NVDA NVDA NVDA NVDA NVDA),IGPU(): 2016-03-29 22:45:40 +0200 Failure Drivers Failure panic during wake due to PEG0(NVDA NVDA NVDA NVDA NVDA NVDA),IGPU(): With VoodooTSCSync.kext, we've noticed launchd crashes less often, meaning waking from sleep works, apart from the other processes that do crash. My theory is that there's something wrong with the firmware of our boards, or an issue with the DSDT or with CPU power management. This underlying problem is causing a TSC sync issue, which causes problems with PCIe devices as well as processes. Does anyone know the cause? Are there more people with this issue? And can anyone explain the relationship between the TSC, the HPET and the RTC? Thanks in advance to anyone who can shed any light on this issue. Kind regards, Pieter Edit: I forgot to mention that konrad11901 discovered that when using hibernation (hibernatemode=25) in stead of sleep there are no crashes, but of course, this isn't an ideal solution. Z97M OC Formula.zip
  2. Hi there, I noticed that my system cannot sleep properly, so I run pmset. Here are the results. The strange thing is that I got "sleep 0 (sleep prevented by mds)". What does it mean? Do you think that all other parameters are good to go? Recently I managed to fix reboot on shutdown. Maybe its linked with that. iMac:~ diego$ pmset -g System-wide power settings: Currently in use: standby 1 Sleep On Power Button 1 womp 0 autorestart 0 hibernatefile /var/vm/sleepimage powernap 0 networkoversleep 0 disksleep 10 sleep 0 (sleep prevented by mds) autopoweroffdelay 28800 hibernatemode 0 autopoweroff 1 ttyskeepawake 1 displaysleep 0 tcpkeepalive 1 standbydelay 10800 Thanks!
  3. Quite the title I have chosen for this topic no? I got my Hackintosh up and running since yesterday. I followed this topic and used @MaLd0n 's CLOVER.zip files for kext installation and for the included SSDT's and DSDT. Massive thanks for that btw. The only *slight* problem I still have is when I have XMP set to profile 1 in the Gigabyte BIOS, and I put my Hackintosh to sleep and I wake it up, I get the message that all USB drives were not ejected properly. I really don't understand what's causing this problem. I currently have disabled XMP in the BIOS and the USB drives are not getting ejected when my Hack wakes from sleep. I use 16GB of Corsair DDR4 Vengeance ram which goes up to 3000MHz. I have XMP profile in CLOVER set to 1. About this Mac reports that my RAM speed is 2998 Mhz. I have a separate SSD drive with Windows on it and I do not think it utilises the full MHz of the RAM because XMP is disabled. Hopefully someone is able to help me. Hackintosh specs: Gigabyte Aorus ultimate gaming i7-8700k Corsair Vengeance DDR4 3000Mhz RAM (16GB) Nvidia GTX 1080 System def: iMac 18,3 I have my config.plist in the attached files. Hope this gives enough insight. config.plist
  4. Notebook Asus X550VX i7 - 7700hq GTX950MX - UHD630 A1718086 - 025510ec ALC255 that works only on VoodooHDA RTL8111 LAN Hwinfo https://drive.google.com/open?id=1n5rHIw-jDPCgocWJtZ0AoVlqIi6Xc7XL Not work: 1. White Screen Wake up EDID not a asolution IOREG output http://www.mediafire.com/file/u7odzbaxa7bbb6a/ioregSaved.txt and EDID http://www.mediafire.com/file/hqlapgf4luwchdf/DisplayProductID-69c.plist Image https://ibb.co/faL5wx 2. Battery info status bar sometimes goes on / off like battery has off 3. Crackle Sound using earphone using VoodooHDA Still investigation using patched iomatch voodooha info.plist The sound card can’t be using AppleALC, no sound came out using layout 3, 13, 17, 18, 27, 28, 99 I have (Mald0n) DSDT thank you for maldon for helping me http://www.mediafire.com/file/lmp5yy65rblx9ne/DSDTtitomaldon2.dsl I have re-patched again for FnKeys and Brighness Key http://www.mediafire.com/file/5rs93ij0wco99s6/DSDTtitomaldon2editv2.aml  codec dump linux https://drive.google.com/file/d/1pg2y76WvFYsO8vFY-2B_2OLyKMmkQ8Tg/view latest debug http://www.mediafire.com/file/2pjny4eq5r64ed8/debug_1383 (1).zip clover and kext https://drive.google.com/open?id=1n5rHIw-jDPCgocWJtZ0AoVlqIi6Xc7XL
  5. Can not get the system to shutdown correctly, screen will go black but the fans keep running and power light stays on. Same happens when I attempt to sleep. Any Help would be appreciated.
  6. I recently set up my hackintosh. Everything else works fine, the only issue is my monitor cannot come back from sleep. Symptom: If I click the "sleep" menu manually, the system goes to sleep fine. After the system sleeps for a while (more than a few mins, I guess it's called "deep sleep"), when I try to wake it up, the monitor wakes up but stays black screen. The machine is on. If I leave the system to time out and sleep by itself, only the monitor goes off; when I try to wake it up, same symptom as above. What I have tried (but none worked): additional boot flag: ngfxpatch=pikera additional boot flag: darkwake = 0 Customize EDID Specs: Motherboard: Gigabyte Z77x-UD5H BIOS: F16j CPU: Ivy Bridge i5-3570K CPU @ 3.40GHz (quad core) Graphics: Nvidia GTX 1050 Monitor: Dell P2715Q @ 4k / 60Hz, Display Port Wifi / Bluetooth: BCM94360CS with PCIE Onboard GPU: disabled OS: High Sierra 10.13.3 Please see attached for following files: EFI zip file: https://www.dropbox.com/s/8nun37msu9b1bva/EFI.zip?dl=0 I generated my own SSDT.aml using ssdtPRGen.sh; Other SSDT patches are copied from this repository: https://github.com/VoiletDragon/Z77X-UD5H-Clover-Hotpatch-Patches ioreg dump: https://www.dropbox.com/s/5a10k82guczaaws/macchiato.ioreg.zip?dl=0 result from following command: https://www.dropbox.com/s/0b22qcw79ovnjdg/kext-touch.txt.zip?dl=0 kextstat|grep -y acpiplat kextstat|grep -y appleintelcpu kextstat|grep -y applelpc kextstat|grep -y applehda sudo touch /System/Library/Extensions && sudo kextcache -u / I am looking forward to your suggestions. Thanks.
  7. Hello everybody I have GA-B250-HD3, and core i5 6500 CPU whith inernal graphics I'am happy that Mac OS X High Sierra on my machine is work very well, but 1 trouble is saddens me. Sleep/Hybernation dont work. I tryied to write several darkwake options in Clover, and tryied to change hibernatemode 0,3,25. I am newbie at hackintosh, and i think that if i want that sleep is working i need to patch DSDT, but i cant do it. If somebody have this motherboard too and know how repair sleep, please help. Sorry for my English, i hope somebody understood me =) UPD: I solved the problem and hibernation worked very well whith integrated graphics hd530. If you want to hibernation works: - put atached HibernationFixup.kext to /EFI/CLOVER/kexts/Other - put atached AptioMemoryFix.efi to /EFI/CLOVER/drivers64UEFI -delete EmuVariableUefi-64.efi from /EFI/CLOVER/drivers64UEFI - in terminal enter sudo pmset -a hibernatemode 25 -in config.plist add boot args: -hbfx-patch-pci=XHC -hbfx-dump-nvram and <key>StrictHibernate</key> <true/> My config.plist is atached, i hope it wil be useful AptioMemoryFix.efi HibernationFixup.kext.zip config.plist
  8. Hi guys, sorry for my English in first place. I'm having problems with sleep in high sierra, when I leave the pc it goes into sleep and reboots, same thing when I close the screen. If I use the fn keys instead the screen remains black. It works, sometimes, if I use the option from the menu. I attach the clover folder and ioreg. Thanks in advance Debug.zip
  9. Introduction With Whatevergreen.kext we already have a workaround for the AMD GPU wakeup issue which first arose with the release of El Capitan, but as a workaround is just a second class solution for a problem I decided to trace back the reason for the issue to it's origin and this post is the result of my research. As I used a R9 270X to do my research, which is the only AMD GPU I have, my patch has only been verified to work properly with this chip but according to the information sources I used, I have no reason to believe it won't work on other AMD GPU's too. In case there is still some uncertainty left in a particular point, I will mention this explicitly. Materials Used The Linux kernel sources of the Radeon driver in order to get a better understanding of the GPU's internals: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/drivers/gpu/drm/radeon?h=next-20171013 A copy of the ACPI 6.0 specs in order to find out how to dump the chip's control register space. A disassembler, e.g. objdump in Terminal or the trial version of Hopper Disassembler. What I Did As it's been a well known fact that wakeup with AMD GPUs still works with El Capitan and Sierra provided you select the IGPU as primary GPU enabled CSM and use Legacy VBIOS of the AMD GPU in BIOS setup. I was wondering what is different with UEFI VBIOS and decided to I create dumps of the GPU's control register space while using Legacy VBIOS with CSM enabled and while using UEFI VBIOS with CSM disabled in order to find out. Comparing the register space contents it became obvious where the root of the problem lies and how it can be fixed with a DSDT patch. Technical Background Using Legacy VBIOS only the primary GPU is initialized by the VBIOS, i.e. only the IGPU is initialized while the AMD GPU is left untouched. When OS X boots up the framebuffer controller kext will find the AMD GPU in vanilla state, initialize it properly and wakeup will work as expected. That's also the reason why you have to blind boot in this configuration. Using UEFI VBIOS the AMD GPU will be initialized too, provided it has a display connected to one of it's ports. You'll see the BIOS splash screen and will be able to access the BIOS settings but unfortunately macOS's framebuffer controller kext will notice that the GPU has already been initialized and skips the basic setup so that the configuration made by the VBIOS will be used and this is the point where things start to go wrong because this configuration seems to be broken causing wakeup to fail. First of all you have to locate the AMD GPU in your DSDT. In my case it can be found at _SB.PCI0.PEG0.PEGP but it needs to be renamed to GFX0 for AppleGraphicsDevicePolicy.kext (AGDP) to work properly. This can be done manually or using a Clover patch (this is what I did) and I assume that this problem has been already solved before. The reason why I mention it explicitly here, is that you should be aware of it and don't get confused when your AMD GPU has a different name in the DSDT than in IORegistry. Second, we need to get access to the GPU's control register space. According to the Linux sources, PCI Base Address Register 2 (BAR2) is used to address the control register space on Radeon HD5000, HD6000 and HD7000 GPUs. It's a 64bit base address register but newer GPUs (BONAIRE and above, i.e. Radeon HD8000 and HD9xxx) are different as the use BAR5 instead of BAR2. Unlike BAR2, BAR5 is a 32bit base address register. On my R9 270X (PITCAIRN) BAR5 is zero so that I decided to use this as an indication to use BAR2 but I must confess that I haven't checked if it works for all supported GPUs too. In case my patch doesn't work for you, be aware that this might be a pitfall! The Radeon driver's source code tells us that the first display controller engine's registers can be found starting at offset 0x6800. It also tells us a lot about the meaning of the register contents. Using Legacy VBIOS my R9 270X's display controller engine's registers are still at their default values when macOS boots: 00006800 01 00 00 00 08 80 00 0a 00 00 00 00 00 00 00 00 |................| 00006810 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006820 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006830 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006840 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006850 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006860 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006870 00 00 00 00 08 80 00 14 00 00 00 00 00 00 00 00 |................| 00006880 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006890 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 000068a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 000068b0 00 00 00 00 10 00 00 00 00 00 00 20 00 00 00 20 |........... ... | 000068c0 00 00 00 20 10 00 00 00 00 00 00 20 00 00 00 20 |... ....... ... | 000068d0 00 00 00 20 00 00 00 00 00 20 00 00 00 00 00 00 |... ..... ......| 000068e0 00 00 00 20 00 00 00 00 00 00 00 00 00 20 00 00 |... ......... ..| 000068f0 00 00 00 00 00 20 00 00 00 00 00 00 00 00 00 20 |..... ......... | With UEFI VBIOS the display controller engine's registers look quite different. Using the Linux driver sources you can easily make sense out of these values and will discover that I've got a 4K display connected to my R9 270X which is configured to it's native resolution using 32 bits per pixel. 00006800 01 00 00 00 0a 80 00 0a 00 00 00 00 00 00 00 00 |................| 00006810 00 00 00 00 00 00 00 00 00 0f 00 00 f4 00 00 00 |................| 00006820 f4 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006830 00 00 00 00 00 0f 00 00 70 08 00 00 00 00 00 00 |........p.......| 00006840 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006850 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 |................| 00006860 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006870 00 00 00 00 08 80 00 14 00 00 00 00 00 00 00 00 |................| 00006880 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006890 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 000068a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 000068b0 00 00 00 00 10 00 00 00 00 00 00 20 00 00 00 20 |........... ... | 000068c0 00 00 00 20 10 00 00 00 00 00 00 20 00 00 00 20 |... ....... ... | 000068d0 00 00 00 20 00 00 00 00 00 20 00 00 00 00 00 00 |... ..... ......| 000068e0 00 00 00 20 00 00 00 00 00 00 00 00 00 20 00 00 |... ......... ..| 000068f0 00 00 00 00 00 20 00 00 00 00 00 00 00 00 00 20 |..... ......... | The rest was just a little bit of laborious work and trial and error, comparing register contents, understanding their meanings and see what happens when you reset these registers to their default values. If you try to play around with your GPU's control registers a little bit more, be prepared to get a garbled screen for a few seconds. After all I've managed to create a DSDT patch which fixes the wrong registers while preserving screen output during boot and, most important, solves the wakeup issue. The Patch Putting things together I created a DSDT patch to fix the incorrectly initialized registers. With this patch applied, I now have working wakeup with my R9 270X under Sierra (10.12.6) using UEFI VBIOS with CSM disabled in UEFI setup. No kext patches or additional kexts are needed anymore for sleep/wake to work properly with my R9 270X anymore. I can see the BIOS splash screen on my display and can access UEFI setup but the best of all is that there hasn't been a single wakeup issue since I applied this patch. Device (PEGP) { Name (_ADR, Zero) // _ADR: Address OperationRegion (PCIB, PCI_Config, Zero, 0x0100) Field (PCIB, AnyAcc, NoLock, Preserve) { Offset (0x10), BAR0, 32, BAR1, 32, BAR2, 64, BAR4, 32, BAR5, 32 } Method (_INI, 0, NotSerialized) // _INI: Initialize { If (LEqual (BAR5, Zero)) { Store (BAR2, Local0) } Else { Store (BAR5, Local0) } OperationRegion (GREG, SystemMemory, And (Local0, 0xFFFFFFFFFFFFFFF0), 0x8000) Field (GREG, AnyAcc, NoLock, Preserve) { Offset (0x6800), GENA, 32, GCTL, 32, LTBC, 32, Offset (0x6810), PSBL, 32, SSBL, 32, PTCH, 32, PSBH, 32, SSBH, 32, Offset (0x6848), FCTL, 32, Offset (0x6EF8), MUMD, 32 } Store (Zero, FCTL) Store (Zero, PSBH) Store (Zero, SSBH) Store (Zero, LTBC) Store (One, GENA) Store (Zero, MUMD) } } In case you have in-detail questions or need AML code for debugging (code to dump BARs or to dump the GPUs control register space) please let me know. I'm willing to share all my information in order support further research. Below you can find the register dumps I created attached to this post. FAQ Do I still have to select the IGPU as the primary display? No. Although I haven't tried this on my own, user chh1 confirmed that this is no longer required when using the patch (please see http://www.insanelymac.com/forum/topic/328549-tracing-back-the-amd-gpu-wakeup-issue-to-its-origin/?do=findComment&comment=2519884). Nevertheless I still recommend to select the IGPU as primary as there is absolutely no reason not to do so, in particular as the IGPU will be unusable for multimedia acceleration on Haswell based systems when it's not the primary one (IGPU's dev id is different when it's not the primary one). ​When I boot into macOS I always end up with a black screen. Does your patch solve this problem too? No, it doesn't. This patch solves the wakeup issue, nothin more and nothing less. The black screen after boot is either the result of a connector problem (please create a connector patch for your graphics card using the well-known methods) or the result of a problem with AGPM as certain system definitions (in particular recent iMacs) select special configurations for graphics power management. In order to achieve proper operation of AGPM it is crucial that your GPUs have correct names in the DSDT matching those listed in the AGPM configuration for the system definition (IGPU for the Intel GPU and GFX0 for the AMD GPU on iMac15,1, iMac17,1 and iMac18,x). You may patch your DSDT manually or use a Clover DSDT-patch to fix the device names. Credits vit9696 for developing Whatevergreen.kext and pointing me to the right direction. RehabMan for developing ACPIDebug.kext The Linux Radeon driver kernel developers for providing me with the background information I needed. Legacy.bin.zip UEFI.bin.zip
  10. Hi! I'm facing a problem on my notebook. I have: Acer Aspire V 15 V5-591G-55TU Skylake-H PC-H i5-6300HQ - HD 530 - Skylake 4+4 GB DDR4 optimus GTX 950M (disabled) BRCM94352Z wifi Windows 8.1 & High Sierra 10.13.3 Natively sleep isn't working, there is a blank screen after sleep, so I used custom EDID Inject to get it working. Before sleep, everything is working fine, but after sleep, I couldn't open videos(on youtube or anywhere higher than 240p), pictures, FaceTime. This is a hardware decode problem, so I opened terminal and typed this: defaults write com.apple.coremedia hardwareVideoDecoder disable After this, Safari and video players could open HD or any videos after sleep, but Chrome not responding (Chrome forced hardware acceleration, and good after disabled that in advanced settings), FaceTime, Preview also not responding, and the pictures on hdd just loading too, nothing happens. Problem exist on all HS versions (13.0 - 13.3). On Sierra 10.12.6 this problem does not exists. Here I'll attach informations (ioreg, CLOVER, screenshot). Kext using at boot for skylake: Lilu, IntelGraphicsDVMTFixup, IntelGraphicsFixup. I'll appreciate any help. Aspire_V5-591G-55TU.ioreg.zip CLOVER.zip ssdt_dsdt.zip terminal-kextcache.txt.zip terminal-output.txt.zip
  11. ptcptc

    Lenovo Y520 help

    Hello, i am in need of help. I have a Lenovo Y520 i7 7700hq with working hd630 intel hd graphics. I have only 2 things to make for the best hackintosh experience on this laptop: -sleep(i will detail after) -Backlight buttons SLEEP: the laptop sleeps, but when i wake it, it wakes on login screen and reboots after 1 second. I know it's from the hd630, but it s there any solution? i can post a log or something if anyone can help! BACKLIGHT BUTTONS: the problem is that backlight control works from display settings. but Brightness from keyboard doesn't work. it is there any way i can map the acpi buttons? Thank you very much.
  12. Hi all, I recently successfully completed a dual boot with macOS Sierra 10.12.6 and Windows 10. I have a Dell XPS 15 9560 with 4k, i7, 32gb, and SK Hynix 1TB SSD. I've got pretty much everything working, however there are a couple issues I'd like help resolving if possible: #1 - I have a Dell U3818DW (38" ultrawide with built-in usb hub/"kvm"). The monitor works great over the usb-c cable! Full 3840x1600 resolution with no issues, and the usb hub/kvm works as well. I can use my keyboard and mouse no problem. The issue then is when the laptop goes to sleep... when I wake it up, the monitor works fine but the keyboard and mouse (really, the monitor's usb ports) are dead and replugging it does not fix it. The monitor will come back, the USB hub shows up under the "card" icon, but the inputs are not recognized. Built-in keyboard and mouse are unaffected. Any thoughts on this? I disabled Wake for Wifi Network Access as I've heard that causes issues, but it has no effect on this issue. #2 - I've got an Apple Watch that I use to unlock a real (late 2012 with updated wifi card) macbook pro and an i7-4790k/ASUS Maximus VII Hero-based hackintosh with an apple bcm94306 mini-pci card (with the full-size pci-e adapter + 4 antennas). I can unlock these after coming back to them with no issues. The XPS, on the other hand, stalls and stalls for about 10 seconds and then finally just shows the password box. I read somewhere that disabling Wake for Wifi Network Access can help with this, but it was already disabled when I enabled the Apple Watch unlock feature. I've tried going to the login window via the user switcher and it won't attempt apple watch unlock, so I don't know how to test if it's a sleep (bluetooth+wifi?) issue or not. #3 - Not really an issue per-se but does the trackpad support on these laptops just suck? None of my multitouch stuff works. Scrolling with 2 fingers works, 2-finger right clicking works OK, but nothing with 3 fingers works except exposé and that only works 1 of 5 tries. Cursor jumps around wildly if I accidentally rest my finger on it while another one is moving, too. I tried the extra kext in the @KNNSpeed thread but it seemed to make things worse.
  13. Hello everyone, Greetings from Brazil! I successfully installed macOS High Sierra on my computer. Everything works beautifully except Sleep. No problems on restart or shutdown. When I put the system to sleep, it restarts. Any ideas on what could be going on? I've enclosed a zip file of my Clover folder. Thank you very much for your time, kind attention and help. I really appreciate it. macOS High Sierra 10.13.2 from App Store Motherboard Gigabyte GA-G41MT-S2P F3 Intel Core 2 Quad Q9400 8 gigabytes of RAM nVidia GeForce 9500 GT with 1gb Two Samsung 500gb SATA HDs CLOVER.zip
  14. Hi all. Can somebody provide any tips on how to fix a sleep issue with my machine? Everything is working perfectly except for sleep. When I put the machine to sleep, the monitors turn off but the machine stays on, fans on full and case LEDs still lit up like the machine is still on. Wriggling the mouse or mashing keys doesn't do anything to "wake" it (I don't think it's actually asleep) and the only way to recover is to do a hard reset. I've been browsing around but I haven't yet seen somebody with the same issue so here we are. Any help would be greatly appreciated. Thanks
  15. Hi, I have a problem with sound via HDMI on GTX 750 Ti. The sound only works after sleep I put and wake up the Hackintosh from sleep. The TV gets detected before sleep in the Sound Settings, but I want to play YouTube, Play Music or anything else there is no sound coming out. After sleep it's working without a problem. So in roder to get sound via HDMI I need to start the hackintosh, put it to sleep, wake it up and then I have sound. The question is: Why the sound via HDMI doesn't work without sleep ? You can find the the system specs in the signature. Logs: https://drive.google.com/open?id=1sAcqNZCI-luSzkCkikR39UO0HC4LVDe_ https://drive.google.com/open?id=1XpVGbp77HF0R5vdUoyL9GzR2YoeLmxaH
  16. On an h67 board with limited configurable options either s1 or s3 power modes then theres a deep sleep option and wake by pcie. used to sleep but be back awake immediatly with the s3 option and be crashed but with s1 option would not sleep but display would and come back if woken. I tried rehabman auto wake usb 3 patch for dsdt and now the s3 option does not crash system but does what the s1 did before. Have implemented the ssdt for power management from piker alpha. of course have tried the other options both ways but not having success. the pmset -g and -g assertions show no preventers except the usb owners and such. have tried the clover devices fix ownership on and off but no effect. not on the machine at moment but can add the clover config and such a little later. Using a 750 ti with i7-2600 Now thinking about the kexts in clover I used some nvidiagraphicsfixup and lilu maybe blocking those helps. No that did not. config1.plist.zip DSDT.zip user’s iMac.zip
  17. Hello there everyone. I recently put together a CL hackintosh for a somebody else and it mostly works fine; however, he's been having a problem that I (so far) haven't been able to replicate. He sometimes gets odd beachballs that end up freezing the computer into needing a cold shutdown and boot; which usually in turn freeze halfway through the boot process only for a reboot to work. Recently he mentioned this happened after several hours of sleep (left the computer sleeping during the night), so I'll try reproducing it later. However, I'm trying to figure out what the actual problem might be. I've got a theory: Wake-up issues with the NVME controller. Why? I've been experiencing similar issues on my real MBP (2011) because the secondary HD ribbon cable has been coming loose. Of course, since it's just a secondary drive, it's a large inconvenience but it doesn't completely shut the computer down. It would certainly be different if this was happening with the primary drive, though. What do people think about this? It's the first time I've built a hackintosh with modern hardware (my own is Ivy Bridge) and I'd never tried NVME before, so there's been plenty of trial and error involved in this build. Stats: CPU: i7-8700 MB: Gigabyte Z370-HD3P RAM: 32 GB DDR4 Video: Asus RX580 Drives: Samsung 940 EVO, 2x 1TB HDDs. Wifi/BT: BCM94331 Other than this issue, pretty much everything seems to be working fine on 10.13.2 (with the exception of the CPU saying Unknown on "About this Mac" but I guess that's cosmetic and expected)
  18. [sOLVED] - Look at the end of this post for solution. Hi all, I have a Lenovo IdeaPad Y510p with Intel HD 4600 graphics as shown in my signature. Now, as the title says, I am having issue with my graphics. When i put the display to sleep or do anything that switches display off, like, changing resolution, putting display / system to sleep etc., after waking up it seems like there are 16-bit colours instead of normal 32-bit. Pardon the low quality capture of the glitch, as I was not able to capture the details in my {censored} camera. Anyway, this is how the bands/gradients/16-bit colours look : These are not exactly like 16-bit but they do seem like it in translucent areas (like launchpad, notification center), shadows, desktop wallpaper etc. Again, it only happens after turning display off then on. Also, just for the record, I do have QE/CI, and everything else like Power Management, Sleep, etc working perfectly. Other posts about same issue: It seems like those having Lenovo Y510p and Y410p are suffering from these problems, also a guy having an Asus K550JK, all of them having same IGPU HD4600 of course. You can see the posts linked below regarding this issue : Y510p reference here (under "Not Working" section) Asus K550JK reference here. Y410p reference here. I also made some posts regarding this issue in a thread dedicated to "Fixing IGPU" here and here. Things i've tried so far : different ig-platform-id's with patched framebuffer data. changing DVMT pre-alloc memory in BIOS and patching framebuffer to match. custom EDID Injection and all of them didn't help. Now, i have dumped the Intel Registers in both Linux and Mac. I've been trying for hours to make sense of them but i couldn't right now (but I'm trying hard). I'd appreciate it very much if somebody would take a look. Attached is the whole folder containing dumps before and after system sleep (and display sleep too) in both Linux and Mac. I could not find any solution for this issue, and if anybody has this issue or solved it or any ideas, please post here. It would be great to hear from you guys. Thanks in advance. ======= Solution : ======= Thanks to @RehabMan and @vusun123 for their suggestions coz of which the issue is fixed. @ahmed_ais, thanks for the hard work mate. You are making OS X experience in Y510p more awesome day by day. Also, thanks to all i forgot to add for their contribution and suggestions. So it turns out the solution is actually an easy one. The EDID info needed to be customised for proper functioning of the display. Specifically: Change EDID version from 1.3 to 1.4 Change basic parameter from 80 -> 90 Fix the checksum Original EDID from Darwin Dumper: header: 00 ff ff ff ff ff ff 00 serial number: 30 e4 16 04 00 00 00 00 00 17 version: 01 03 basic params: 80 23 13 78 0a chroma info: 15 d5 9e 59 50 98 26 0e 50 54 established: 00 00 00 standard: 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 descriptor 1: 1a 36 80 a0 70 38 1f 40 30 20 35 00 59 c2 10 00 00 19 descriptor 2: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 descriptor 3: 00 00 00 fe 00 4c 47 20 44 69 73 70 6c 61 79 0a 20 20 descriptor 4: 00 00 00 fe 00 4c 50 31 35 36 57 46 31 2d 54 4c 43 32 extensions: 00 checksum: 7d Modified EDID: header: 00 ff ff ff ff ff ff 00 serial number: 30 e4 16 04 00 00 00 00 00 17 version: 01 04 basic params: 90 23 13 78 0a chroma info: 15 d5 9e 59 50 98 26 0e 50 54 established: 00 00 00 standard: 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 descriptor 1: 1a 36 80 a0 70 38 1f 40 30 20 35 00 59 c2 10 00 00 19 descriptor 2: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 descriptor 3: 00 00 00 fe 00 4c 47 20 44 69 73 70 6c 61 79 0a 20 20 descriptor 4: 00 00 00 fe 00 4c 50 31 35 36 57 46 31 2d 54 4c 43 32 extensions: 00 checksum: 6c As you can see, the changes are in "version:" from 03 to 04, "basic params:" from 80 to 90 and the calculated checksum from 7D to 6C which might be different for you. Source if you need it. Intel Reg Dumps.zip Intruder’s MacBook Pro.ioreg.zip config.plist.zip
  19. Hello forum! I come asking for help. I am a programming student and am currently learning Java and Swift, including MySQL and HTML & CSS and some others, so it really is important to have a working stable build. I have achieved this! Am currently rocking my Gigabyte EP45 UD3LR with a beautifully working DSDT, with everything working, except sleep. My computer successfully sleeps, but reboots soon after waking from sleep. I am quite sure I have achieved Native CPU power management, since all required kexts are loaded, here are my specs anyway GIGABYTE EP45-UD3LR Intel Core Q6600 Nvidia Geforce 210 BCM94360CD with adapter 6GB RAM I dont know what I can do anymore to fix the sleep reboot problem. Any help apreciated. Here is my current EFI EP45-UD3lR.zip Thanks so much for this beautiful forum we all came to love
  20. alfalus

    Sleep Shutdown Problem Asus S451LB

    Hello everyone, can you help me to fix sleep and shutdown issue on ASUS laptop. Because its really strange, sometime my laptop can sleep and shutdown, but sometime when i press sleep option, the display goes blank, but the indicator power is on (cant wake), so i must hard boot to force shutdown. I'm attached that DSDT and SSDT file (origin and patched) if you can see what's wrong with my patch. And i'm attach the config.plist too. I hope someone can help me to fix this issue. Thanks in advance and sorry for my bad english. PROBLEM.zip config.plist.zip
  21. After upgrading to El Capitan (since PB1), I haven't managed to get sleep and wake working properly. It will go to sleep normally, but when I wake it up (using either the keyboard/mouse or the power button), and neither the display, usb or graphics will work. Ethernet works, since I can access my iTunes library using the Remote app on iOS. Sleep/wake worked perfectly in Yosemite. I use a GA-Z77x-UP5 TH, i7 3770K, and an AMD 6850 on an OCZ SSD. Can anyone help? I'll attach my config.plist and DSDT. DSDT_CONFIG.zip
  22. Hi guys, my Yosemite works fine on my old rig (specs see signature) and sleep works perfect. My problem is that Yosemite wakes up automatically roughly every 2 hours for a minute and then goes back to sleep. It sounds like the PowerNap feature, but I have not activated that (it doesn't show up in Energy Saver preferences anyway). Here's my log from last night: 8/5/14 2:24:48.000 AM kernel[0]: Wake reason: RTC (Alarm) 8/5/14 4:13:43.000 AM kernel[0]: Wake reason: RTC (Alarm) 8/5/14 6:02:38.000 AM kernel[0]: Wake reason: RTC (Alarm) 8/5/14 6:02:50.445 AM ntpd[212]: ntpd: wake time set +0.141756 s 8/5/14 7:51:33.000 AM kernel[0]: Wake reason: RTC (Alarm) 8/5/14 7:51:44.938 AM ntpd[212]: ntpd: wake time set +0.196362 s 8/5/14 9:40:28.000 AM kernel[0]: Wake reason: RTC (Alarm) 8/5/14 9:40:39.638 AM ntpd[212]: ntpd: wake time set +0.255238 s 8/5/14 11:29:23.000 AM kernel[0]: Wake reason: RTC (Alarm) 8/5/14 11:29:34.247 AM ntpd[212]: ntpd: wake time set +0.309745 s 8/5/14 11:59:41.000 AM kernel[0]: Wake reason: USB1 8/5/14 11:59:41.000 AM kernel[0]: The USB device WirelessControllerDevice (Port 1 of Hub at 0x3d000000) may have caused a wake by issuing a remote wakeup (2) 8/5/14 11:59:41.000 AM kernel[0]: full wake promotion (reason 1) 338 ms 8/5/14 11:59:41.513 AM WindowServer[170]: CGXDisplayDidWakeNotification [25968432798537]: posting kCGSDisplayDidWake 8/5/14 11:59:48.996 AM discoveryd[49]: Basic DNSResolver UDNSServer:: PowerState is Wakeup 8/5/14 11:59:52.230 AM ntpd[212]: ntpd: wake time set -0.403636 s The last wake obviously was me waking my computer with my trackpad. As you can see on the attached screen shot, 'Wake for Ethernet network access' is deactivated and no schedule is set - those settings are not causing the RTC wake up. From my google research, those were the common reasons for my problem. I found another article about a similar problem and that guy fixed it with changing some bonjour settings (NoMulticastAdvertisements) but I didn't try that yet because I think the problem is somewhere else. I am _not_ using any NullCPUPowerManagement.kext. I have only FakeSMC and my network kext in my clover kexts folder. Do you have any clues how I can deactivate those RTC Alarm wakes? Also what is that 'ntpd: wake time set'? Thanks! -Maxim PS: Sleep works fine in Mavericks without any RTC Alarm wake ups with basically the same clover & system set up.
  23. nyolc8

    Display Sleep problem (still)

    Hi! I have only one problem with my hackintosh since I have a hack. Display Sleep. It does not turns off my display, only freezes the screen. I had an ati radeon hd4670, now I have an ati radeon hd4830, the problem is exactly the same. I tested many things and here is the situation: - If I'm using the correct framebuffer for the vga (for hd4830 it is MotMot) then display sleep not working. - If I'm not using any framebuffer for the vga, then the display sleep working fine, but I get dual display configuration even with only one display connected. I'm using dsdt injection instead of graphics enabler (same display sleep problem present with graphics enabler too). Here's my dsdt code: Device (PEG0) { Name (_ADR, 0x00010000) Device (GFX0) { Name (_ADR, Zero) Method (_DSM, 4, NotSerialized) { Store (Package (0x26) { "@0,compatible", Buffer (0x0B) { "ATY,Motmot" }, "@0,device_type", Buffer (0x08) { "display" }, "@0,name", Buffer (0x0B) { "ATY,Motmot" }, "@1,compatible", Buffer (0x0B) { "ATY,Motmot" }, "@1,device_type", Buffer (0x08) { "display" }, "@1,name", Buffer (0x0B) { "ATY,Motmot" }, "AAPL,slot-name", Buffer (0x10) { "PCI Express x16" }, "ATY,Card#", Buffer (0x0E) { "109-B77101-00" }, "ATY,Copyright", Buffer (0x33) { "Copyright AMD Inc. All Rights Reserved. 2005-2009" }, "ATY,EFICompileDate", Buffer (0x0C) { "Oct 09 2009" }, "ATY,EFIVersion", Buffer (0x0A) { "01.00.318" }, "ATY,EFIVersionB", Buffer (0x0F) { "113-B77101-012" }, "ATY,EFIVersionE", Buffer (0x0F) { "113-B7710A-318" }, "ATY,MemRevisionID", Buffer (0x02) { 0x09, 0x00 }, "ATY,MemVendorID", Buffer (0x02) { 0x02, 0x00 }, "ATY,Rom#", Buffer (0x0F) { "113-B7710C-176" }, "device_type", Buffer (0x12) { "ATY,MotmotParent" }, "model", Buffer (0x1C) { "Sapphire ATI Radeon HD 4830" }, "name", Buffer (0x12) { "ATY,MotmotParent" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } } Can someone tell me what do I need to get display sleep working?
  24. Hi, i'm having trouble with my TC Electronic PCI cards being recognised on restarting the system (or sleep/wake) on 10.9.4. They just come up as "unrecognized device" whereas after a full power cycle they appear and work fine. I've done an AICPM patch and have generated an unedited SSDT which seems to have fixed a lot of my sleep issues and I can now mostly sleep/wake fine (ethernet works, audio works, dual monitor works). It's just this card that I'm having issues with currently. I built my hackintosh to run Logic with these cards so really keen to fix this issue (I can work around it with a power cycle but not ideal) Don't really know where to start. Don't understand DSDT editing at all. any advice would be greatfully appreciated and I'm sure it would help a lot of other musicians! thanks J Motherboard; Asus P8B75-V CPU: i7 3770 GPU: Zotac GT210 System: 10.9.4 from app store + myHack