Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

Henties

Members
  • Content count

    17
  • Joined

  • Last visited

About Henties

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
    Male
  • Location
    Namibia
  1. Hi everyone. When my Skylake hack wakes from sleep it sometimes just freezes. After a reboot, when I run - pmset -g log | grep -i fail - I get the output as per the attached jpg. I would appreciate if someone could help me in deciphering what these messages mean and where could I look to find the cause of these failures. Any suggestions are much appreciated.
  2. Lilu — kext and process patcher

    In my quest to enable Hardware encoding as well as mirroring on both of my hacks, one a Skylake and the other a Haswell build, I needed to to remove Lilu.kext as well as NvidiaFixup.kext ( both at version 1.2.1) and revert back to AGDP.fix to fix the black screen issue during boot. Details have been published here: https://www.hackintosh-forum.de/index.php/Thread/30859-Quicksync-Virtual-Screen-Abst%C3%BCrze-und-iGPU-ded-GPU-mit-Grafikbeschleunigung/?pageNo=21post379614 at post #393. Greetings
  3. Hang ten I have a GA- Z170X-HD3 rev. 1.0 mobo yours may be similar to mine but that is where it also all ends. By the way I am on bios F20 for my mobo. Make sure that you don't have any typos when you created your SSDT-USB.aml, that will certainly screw things up. Don't use that file from somebody else unless the mobo as well as bios specs are exactly the same as yours. Attached find my zipped Clover folder used with my GA-Z170X-UD3 mobo. To make it a bit leaner I only removed the theme folder from Clover. Edit In the interim I have converted my 2 El Capitan hdds, originally setup with Clover for legacy booting for my old and ancient rigs, to UEFI booting. For the converted El Capitan hdd now running on my GA-Z170X-UD3 mobo I just copied the Clover setup I use for Skylake, with a different iMessage of cause. Likewise I did the same with the El Capitan hdd now running on my GA-Z97X-UD3H build. With both I have no problems with sleep, wake from sleep or whatever. My computer cases all have a drive slipway at the top of their boxes, so whenever I want to use a different operating system I just slide in the hdd for that particular opsys. Simple and straightforward. I sometimes need El Capitan functionality, for some time to come I guess, because code signing "Kodi" under Sierra is broken. The developer of the code signing method for El Capitan is currently still working on a solution for Sierra, until he succeeds I still need El Capitan available just for code signing Kodi for my Apple TV 4's Enjoy ! CLOVER.zip
  4. My sleep is working in ALL respects on both of my builds.
  5. Find my XOSI-WIN10.aml file embedded in the attached zip folder. No special switches needed in config.plist for this file to be read during startup, its presence in Clover ACPI/patched is all that is required. In my config.plist, under the ACPI heading I have absolutely nothing checked at all, the only entry is in DSDT patches to change _OSI to XOSI. Under the Boot section I have only checked the following: Verbose - I like to see what is happening during the boot process. darkwake=8 - preferred by me even during my El Capitan adventure :-) YMMV dart=0 - this has always been required for previous builds as well. kext-dev-.mode=1 - makes it easier to apply the AGDP.fix should a future Sierra update by Apple require the application of this patch. - System running with no output on monitors. I opted not to patch my DSDT for this as that adds an extra level of complexity and it would most likely break with the next Bios update which I will apply as soon as it is elevated by Gigabyte from beta to production for my mobo . All the foregoing is for my Skylake build. One of my previous posts in this thread point out the differences and the approach I followed for my Haswell build, which works properly as well in ALL respects. This is about it. All the foregoing would not have been possible to achieve without RehabMan's efforts and dedication in this and many other aspects of the hackintosh scene, Thanks RehabMan. OMG my signature is totally outdated will have to fix that sometime soon :-)
  6. No further comment other than what follows. I agree with your sentiments however I strongly believe what is achievable with a Gigabyte board without patching a DSDT is also achievable with your ASUS mobo, It might just require a little bit more effort and patience. The end result and longer term benefits stemming from that, is just awesome. Cheers
  7. Good luck with your sleep endeavours. Originally I also considered patching the DSDT's of my builds however I decided against it as that would just add another level of, in my view at least, complexity. The systems have to be maintained and preferably also survive a future bios update , which I believe is imminent, for my GA-Z97X-UD3H build. Injecting patches via Clover is for me the preferred method for a desktop, as Clover handles this kind of chore flawlessly and with ease, ensuring maintainability at the same time.
  8. Hi sorry for taking so long to respond to your earlier post #34 I can confirm again that both my Skylake GA-Z170X-UD3 as well as my Haswell GA-Z97-UD3 build have no sleep problems at all. I achieved that without DSDT.aml patches whatsover, I only mapped my USB ports properly, created a SSDT-USB.aml for the ports I wanted and placed that into the ACPI patched folder, then I used USBInjectAll.kext in /L/E to control all that. That was done for the Skylake build. For my Haswell build I approached the sleep issue slightly different though, necessitated because of huge architectural differences between a Haswell and Skylake based system. 1. Changed _OSI to XOSI 2. Changed EHC1 to EHO1 3. Changed EHC2 to EHO2 Above to mainly disable Apple's built in injectors. 4. Added XOSI-WIN10.aml 5. Created a SSB-USB.aml containing all the USB ports that I mapped with a USB-2 device as well as a USB-3 device. Quite a laborious process but worth it. 6. Eliminated unwanted ports with a boot arg in my config.plist file. and ensured that these are indeed not loaded during the boot process with USBInjectAll.kext in /L/E That is basically it and works perfectly for me. I have also mildly overclocked both systems to 4.4 gigs and control that with a ssdt.aml file in ACPI/patched appropriately generated with a ssdtPRGen shell script by Piker-Alpha. That is about it. All the information needed to accomplish this was obtained by carefully reading and studying RehabMan's excellent guides and instructions. One issue worth mentioning perhaps is that one sleep issue, which I discovered before the Sierra 10.12.2 upgrade, was with my Corsair Hydro Cooler 1000i V2 and in particular its USB interface. As soon as that is connected to any native USB port on the mobo, sleep will not work at all. The machine will wake up virtually immediately it has entered sleep. That problem I resolved by moving the USB cable for that cooler to a USB port which is not native to the mobo. For both builds I use an add on Renesas based USB-3, 2-port controller, which in turn I control with the GenericUSB.kext - also by RehabMan - placed in /L/E. It has worked ever since although software to controll the cooler with is only available for Windows. Hoping this will help you to sort your sleep issues out as well.
  9. I have no issues that I am aware of after the 10.12.2 upgrade on either my GA-Z97X-UD3H Haswell build or my GA-Z170X-UD3 Skylake build. However still testing, for the Z170X I had to apply the AGPDfix.app to get my GTX-970 functioning, but that was all.
  10. VoodooHDA on Sierra

    Thank you. I am impressed, will try and work through that guide and see how far I can get. Hoping I can "push your button for help" should I get stuck, which is most likely. :-) Feedback I walked through that excellent guide and encounter problems with renaming HDAS to HDEF, the data values did not work for me, instead used "SERBUw==" and "SERFRg==" respectively in their place to make it work. My energy monitor now sports some interesting and additional setting ticks, not living ones thou. :-) My Sierra Skylake rig now sleeps and wakes up, however on wake-up, sound is dead, need to shutdown and cold reboot to get it back. This seems to be a problem that a number of Skylake Z170 mobo Sierra opsys users encounter. Also not sure whether rig will wake up after longer terms sleep, that was also a problem before this ALC patch. At least AppleHDA is now stock standard and should at least survive future Apple updates to it. Would appreciate if you could also assist with loss of sound during sleep. Keep well
  11. VoodooHDA on Sierra

    I am struggling as well with audio on a GA Z170-Gaming K3 mobo which uses the Realtek 1150 codec. I rename HDAS to HDEF with SSDT injection. but to no avail. Am fed up struggling with AppleHDA and have been trying to install VoodooHDA however I lack the knowledge to get it right. I need a write up as to what I need, where to get the stuff from and how to set it up. Without that I am lost. Slice and many others claim VoodooHDA is working on Sierra sysdef 17.1 but such statements don't get me closer to getting something that is obviously good, to work by myself, so please somebody knowlegable help me. The furthest I have gotten with VoodooHDA is a message that says "no HDA device detected." at that stage AppleHDA was already removed from my system S/L/E. VoodooHDA is now my only hope it seems.
  12. I have the same sleep problem however I do not have a BT device at all. I am using a GA-Z170-Gaming K3 mobo, i7 6700K, GTX 970 and with pmset -g assertions it tels me "Idle sleep preventers: IODisplayWrangler" and the output of sudo pmset -g log | grep -i failure yields "Darkwake Exit Failure during wake due to 0x34053000000032:". To me it appears to be Nvidia driver related. Your thoughts ? I did some further tests by removing USBinject all kext and also removed the port count increase in config.plist. Now my is finally sleeping like it should.
  13. Thanks for the feedback. I never had to use anything in El Capitan to get the GTX 285 working as I am using native built in drivers. In El Capitan I only have KP's when I try using the Nvidia web drivers. To me that is strange because the web drivers are specifically built for sysdef 5.1 machines and directly support the old GTX 285, at least that is according to Nvidia the distributors of the web drivers. All other sysdefs used with the web driver are classified as beta efforts by Nvidia. I believe that my hardware matches sysdef 5.1 Apple MacPro's fairly closely, although I could be wrong and would welcome some guidance in this regard as well. I am running Clover 3763 without a DSTD.aml. In my AppleGraphicsDevicePolicy.kext my Mac-board ID is already set to "none" without me having had to do anything, unless there is something else I need to do that I am unaware of, if so kindly elaborate, as I am sure that if I get the web drivers working in El Capitan my Sierra problems will also be over. As I metioned earlier the mere presence of the web driver causes the machine to be unusable, I cannot even get into Vesa graphics mode, the machine KP's before reaching the desktop. The only cure to return the machine to normal is to remove the web drivers. What appears to me has happened is that the new built in drivers in Sierra inherited some code from the older web drivers that were used for El Capitan and that is why Sierra is also not working for me. Again therefore getting the 15A1004 web drivers working in El Capitan will probably reveal what needs to be done to get Sierra working with it's built in or web drivers. Some more thoughts on that would be most welcome.
  14. I can only install or upgrade to Sierra 16A323, via USB stick with all of these switches enabled: 1) nv_disable=1 2) Inject Nvidia 3) Nvidia single 4) Nvidia generic Removing any one of these switches causes KP's and or reboots before the desktop is reached. Mobo X58A-UD3R V 2 Bios FH CPU i7 930 GPU GTX 285 Sysdef 5.1 or 12.1 or 14.2 using built in Nvidia drivers. All on Legacy Clover 3763 install. Once installed I can run Sierra in Vesa mode only with all the switches that I had to use during installation still applied. Again removing any one of these switches causes KP's and or reboots before the Sierra desktop is reached. In El Capitan I have no problems to run the latest 10.11.6 version. If however I attempt to use the Nvidia Web driver in El Capitan then the identically same problem manifests itself with one difference, the switches seem to have no effect at all. The machine just reboots or KP's merely because of the presence of the Nvidia 15A1004 Web driver for El Capitan Uninstalling the Webdrivers returns normal operation to the machine. Switching Nvidia off in the Nvidia system pref.pane has no effect KP's or reboots still happen as regular as clockwork. Only the removal of the web drivers solve the problem for El Capitan For me this is rather strange because the Nvidia Web drivers are supposed to directly support the GTX on a sysdef 5.1 system. Anybody else having this problem and or a solution thereto ?
×