Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


mfc88 last won the day on March 20 2017

mfc88 had the most liked content!

About mfc88

  • Rank

Profile Information

  • Gender
  • Location
    San Jose, Calif.

Recent Profile Visitors

2,428 profile views
  1. Sorry bud, but my knowledge of this OS stops at 10.12.3. I'm no longer using it due to its overall instability. I suggest that if you're not going to use or plan on using Mac OS specific software, and you don't want Windows, then look into Linux. It's what I've been running for several months now and it's been perfect my needs. If you are going to use Mac OS software, then either stick with El Capitan or else you'll be on your own and expect months of learning, understanding, researching and tinkering to get Sierra to work (no guarantees of stability). This community is a great place for learning/sharing if you do decide to try Sierra; but, if that sounds like too much work, then look into a VMware solution (it'll be stable, but expect slower performance due to hardware/software limitations).
  2. If you're going to use SSDTs, then it's best to separate out the devices via SSDT-{old_device_name}.AML. You have a lot of nested devices that make it rather confusing and unnecessary. The idea behind multiple SSDTs is that if one thing breaks/isn't injected/prevents booting, you can simply drop it before loading up the OS and it won't interfere with the other devices. And, these SSDTs will survive BIOS updates (custom DSDTs most likely will not -- tested and confirmed). You can use my ssdtGenApp as a starting point, then you'll want to add a "_SUN" method for PCI slots. In order to get the PCI devices to show up in the PCI device list, you'll need a "AAPL,slot-name", "name" and "model" device property. With the exception of NVME, if using HackrNVMEFamily, where you'll want to remove the original device and any D0XX/PXSX devices and then replace it with a new name (NVME), otherwise "Slot" will always be "Ethernet". Clean up the SSDTs.
  3. Absolutely. You can fork the github repo (missing Photoshop .psd icon files) or download the source. Up to you.
  4. Just wanted to preface this post by giving a huge, huge thank you to the InsanelyMac staff for all their support. Anyway, I've updated the first post. However, in that time that this thread was locked, my passions have shifted and lie with web application development. As such, support for the ssdtGenApp will stop at v0.2.2b. However, the app will still be functional and work across the X99/Z170/Z97 and H97 platforms, but may run into future problems with future OS upgrades. As such, if any current or future developers/coders would like to continue supporting it, I've attached the source files to the post as well (with plenty of source notes). You are more than welcome to modify, adjust, alter, and change the app files to suit your needs.
  5. Sorry folks, I'm just not going to put up with anymore...
  6. The ssdtGen.command file that generates the SSDTs wasn't changed from 0.2.2(v2) to what was released. Sounds like an injection issue. Try rebooting multiple times and checking. I have a feeling it'll be inconsistent. Also, you can't generate HDAS as it's already named HDEF. Whatever you're using for audio is changing your ACPI device names.
  7. Should still be there... perhaps because it's named GFX1 instead of GFX0? Try this... (remove GFX1, replace with GFX0) SSDT-GFX0.aml.zip
  8. Updated app to 0.2.2b - see change log for more details.
  9. Okay... looks like your DSDT already has it named HDEF... perhaps a kext? Also, it looks like something (kext again?) is altering some other devices. Under PEG0, it should be: GFX1 and HDAU. Instead it's: GFX1 and HDEF. You're getting motherboard (on-board) sound, yes? Also, add these patches to your config.plist, under Apci, DSDT patches ("Rename _DSM to XDSM" is optional for you): Comment: Change _OSI to XOSI Find: 5f4f5349 Replace: 584f5349 Comment: Change EHC1 to EH01 Find: 45484331 Replace: 45483031 Comment: Change EHC2 to EH02 Find: 45484332 Replace: 45483032
  10. @Rehabman Added prebuilt IASL link Added MaciASL link Restated for reference of class code Missing ACPI identities now redirected to your guide Added a real example of _DSM to RP01.PXSX Switched command to match "./patch_nvme.sh --spoof" Only thing I didn't change is _DSM->XDSM patch. If you want me to update anything, let me know.
  11. Do me a favor and dump your ACPI tables. At Clover Boot Manager screen, press F4, wait 5 seconds, then boot into the OS. Mount your drive, go to CLOVER->ACPI->origin and upload that folder. Also, it looks like SBUS isn't being completely injected. Here's a fix for that... ssdtGen_v0.2.2b.zip
  12. Go here: http://www.insanelymac.com/forum/topic/312803-patch-for-using-nvme-under-macos-sierra-is-ready/page-37?do=findComment&comment=2343228 1st link in my post is Rehabman's guide or you can use my guide below the link. Rehabman's goes in to much more depth while mine assumes you know how to type in an ACPI path and press a button. Which one you use is up to you.
  13. Need to see an IOReg without DSDT.aml installed. Otherwise, useless. Also, send me generated SSDTs. Need to make sure they're built to expected specifications. On that note, you don't have a GLAN device, which is fine. Your internet is routed thru RP03 -- ethernet and RP05 -- WIFI. So GLAN is not needed. However, HDAS should be a device (unless it's already named HDEF which results in a ssdtGen compilation error -- should not be the case if running vanilla).