Jump to content

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

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
    • Installation
    • Post-Installation
    • DSDT and SSDT
    • Hardware Components and Drivers
    • 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 10 results

  1. Hi guys, My computer hardware is i signature. Currently, 10.12.6 is perfect and my EFI is here. Problem Description: When I tried to boot 10.13 DP5, I encountered AppleACPIPlatform problem: Typical Causes and Solutions: After searching google for couple of days and with the help of @PMheart I found Alext James (@TheRacerMaster)'s article : http://alextjam.es/debugging-appleacpiplatform/ Because signed char become negative when bigger than 0x7f, Apple rewrote isprint method but seems to forget to cast char to unsigned. Thus, if OemId, Signature、OemId、OemTableId or AslCompilerId in any ACPI table contains a char greater than 0x7f, it will cause a memory overflow. Most people can solve by: dropping MATS/BGRT table( or other table ) add FixHeaders_20000000 in clover ACPI patch Modify MATS/BGRT/other table and change that char to lower than 0x80 But sadly none worked for me I dropped all of my ACPI tables except DSDT and APIC, cuz I cannot boot without these two I searched for APIC and DSDT, none of their OemId, Signature、OemId、OemTableId or AslCompilerId contains char greater than 0x7f Untypical Situation: I took a video of my boot process using -verbose, debug=0x100, keepsyms=1 : see online : https://www.dropbox.com/s/p4eztglltdtqxyb/boot.mp4?dl=0 In the trace, the boot process stuck at isspace other than isprint. Out to curiosity, I decompiled AppleACPIPlatform and saw isspace looks like this: _isspace: 000000000001f5cf push rbp ; CODE XREF=_AcpiUtStrtoul64+71, _AcpiUtStrtoul64+89 000000000001f5d0 mov rbp, rsp 000000000001f5d3 lea rax, qword [__ctype] 000000000001f5da mov al, byte [rdi+rax] 000000000001f5dd and al, 0x20 000000000001f5df shr al, 0x5 000000000001f5e2 pop rbp 000000000001f5e3 ret And in C language it looks like this: int _isspace(int arg0) { rax = (int)__ctype[arg0]; return (rax & 0x20) >> 5; } It uses __ctype as an array and rdi, which acts as argument in assembly language, as a pointer to find some char and put it into al. I checked the length of __ctype is 256, thus any normal byte, which is 16 bits, won't caus overflow. However, Apple didn't cast arg0 to unsigned char. Thus, any char that's greater than 0x7f will also cause an overflow. Follw the trace, I found _AcpiUtStrtoul64 the source code is here. Looks like it just uses a loop to judge whether it's a space. No other useful information were found during further dig. New Discovery and Dilemma Occasionally, i decompiled two programs written to test signed and unsigned char, and were surprised to find, the only difference between 'cast to unsigned' and 'stay signed' in assembly language is that when delivering argument, unsigned used 'movzx' and singed used 'movsx'. In assembly language, arguments are delivered by register rdi. So, I think, if I change 'movsx' to 'movzx' then this problem can be solved. Here's where isspace is called inside _AcpiUtStrtoul64: 0000000000001153 mov qword [r14], 0x0 000000000000115a movsx edi, byte [r15] 000000000000115e test edi, edi 0000000000001160 je loc_12b5 0000000000001166 mov dword [rbp+var_2C], esi 0000000000001169 xor eax, eax 000000000000116b call _isspace 0000000000001170 lea rbx, qword [r15+1] 0000000000001174 test eax, eax 0000000000001176 je loc_118d loc_1178: 0000000000001178 movsx edi, byte [rbx] ; argument #1 for method _isspace, CODE XREF=_AcpiUtStrtoul64+99 000000000000117b xor eax, eax 000000000000117d call _isspace 0000000000001182 inc rbx 0000000000001185 test eax, eax Note that edi is the lower 32 bit of rdi . However, after patching in Clover, it stucks that line 0000000000001178 . And checking the register printed, register edi is empty. That means something's wrong when executing movzx . If I do not change movsx to movzx, at the panic scene we can see in the above video that register rdi is 0x00000000 ffffffa4 , thus edi is 0xffff ffa4 . Obviously, the char that caused the problem should be A4. However, I searched APIC but didn't find A4. There is a A4 in DSDT but I have no idea how to modify. BIOS rom, all of my ACPI tables and modified dsdt/ssdt can be found in attachment. Need Someone's Help So, here I'm at a very embarrassed stage don't know where's wrong even what to do next... Maybe something's wrong with one of my ACPI tables? Or with AppleACPIPlatform? Or with AppleSMCRTC? I'm pretty sure I'm not alone with this question, someone willing to dig into it please check my raw ACPI tables, BIOS ROM, modified DSDT/SSDT and my current EFI folder. Thanks very much. BIOS ROM: x7946.rom.zip Modified DSDT/SSDT, perfect on 10.10 - 10.12.6: dsdt+ssdt.zip Original ACPI Tables: OriginACPI.zip
  2. Hi, I have a long itching problem: Supermicro X9Dai Dual Socket with two Sandy Bridge-E E5-2670. Yosemite running fine and all is working well including Power Management with patched AICPUPM.Kext (If anyones interested, throw me a line, glad to send my config) But the Setup works only with HT disabled, eg. 16 Cores. If I enable HT to 32 Logical Cores, I get Kernel Panic @ Boot, backtrace is AICPUPM.kext. With Mavericks, everything worked fine (had to use the ACPI/PCI Drivers from 10.9.1 though because it got terrible unresponsive if using the newer ones. So is there a hardlimit in the Darwin 14.X.X Kernel somewhere to not allow more than 16 Cores or is it maybe a ACPI DSDT Problem? Is there maybe a Kernel patch which could work? Thanks for help! Mike
  3. (Mistakenly posted in 'Installation Guides' at first) Hi, A couple of weeks back I took the plunge and upgraded my system from Yosemite (10.10.5) to Sierra 10.12.6. Reason for doing that was that I wanted to upgrade my graphics card from a GTX 960 to a GTX 1060. I followed Rampagedev's procedure and used his DMG to upgrade. I also installed the nvidia web driver 378.05.05, and I installed an Intel 750 PCIe NVME SSD, using Pikeralpha's NVME patch and included the NVME drivers from a Gigabyte Z97 board on the GA-X79-UD3, as the X79 board originally does not support NVME. So, I can boot from the Intel SSD, but it takes about 3 or random 4 kernel panics and reboots before I get to a login prompt. Once logged in everything works fine and the system is stable. I saw the same behaviour when everything was still on a SATA SSD, so I do not suspect the NVME drivers and patches to be the culprit. The KPs can happen at different stages during boot, sometimes even when I am logging in. But once logged in, everything is ok. Another thing that bothers me is USB3. I installed USBXHCI_FL1009.kext, also from the Rampagedev DMG, but the results are flaky. A USB3 USB-stick is recognised, as is my card reader, but an external (bus-powered) USB3 drive from Seagate is completely ignored when inserted. I did turn off USB3 during the upgrade, but it is switched back on now. The original install was with Mavericks, and I upgraded that too to Yosemite. I never tried a clean install as that would take a lot of work to migrate and relicense all my apps. So, in terms of system goodies: Mobo: Gigabyte GA-X79-UD3 CPU: Intel 4930k OS: Sierra 10.12.6 Nvidia web driver: 378.05.05 GPU: MSI GTX1060 3GB Boot drive: Intel 750 NVME PCIe SSD Clover: 4220 Anyone that can help to solve the kernel panics and the USB3 issue? Enclosed my complete EFI folder, IOreg, ACPI tables and kextstat.txt. Any help is appreciated. Thanks. Toms MacPro.ioreg.zip EFI.zip Send me Toms MacPro.zip

    Asus Sabertooth X79

    Version (BIOS 3408, 3501)


    This is the DSDT file I'm using on my Hackintosh. There are NO sounds edits, as I am using an M-Audio sound card. See my signature for more info. Benefits are that my hack boots up in 25 seconds and shuts down in three. 98 kexts loaded viewed in kext helper. Sleep is working using SleepEnabler by sk.triaxis(1.0.0) Compiled in BIOS VERSION 3408 works ok with very latest BIOS VERSION 3501
  5. Hi, I recently installed 10.8.2 to a USB HDD for a test install and I have some problems. I have installed MiniITX's GA-X79-UD3 DSDT.aml and AppleHDA.kext from Interim Ivy Bridge HDA thread and AHCIPortInjector.kext along with FakeSMC.kext NullCPU....kext, intel e1000 lan kext and SleepEnabler.kext. I get audio and can boot just fine with : npci=0x2000 GraphicsEnabler=No. However even after installing sleepenabler i get white screen with unmoving mouse every time I try to get it to sleep, which goes away when i press a few times the mouse buttons or press the H/W Sleep button. I am on F11 Bios(the dsdt was for that version and have disabled USB3.0). Why can't I get it to sleep? Can someone share a DSDT.aml that would enable native power management? I want sleep to work so I can get my ATi HD7970 to work(enable OpenGL and Q/E).
  6. Took me a while to get Yosemite up and running, but I think I'm at a pretty good spot right now. Runs pretty smoothly and is for the most part stable. This should work on all X79 boards. Current Config: Asus Sabertooth X79 -- Bios 4701 (Latest as of June 23 2014) -- Optimized Defaults -> XMP -- CSM disabled / Secure boot = OTHER OS Intel i7 4930k EVGA GTX650 GPU (flashed for UEFI.... email support and they'll send you a BIOS file but you need to use Windows to install it) 32GB Corsair 1866MHz Memory A bunch of SSDs Other stuff (Bluetooth 4 adapter, Wifi PCI adapter, Trackpad, Apple Keyboard) What you'll need: 10.10 Installer bash script (http://www.insanelymac.com/forum/topic/298521-easy-yosemite-1010-usb-installer-updated/) Clover v2747 (http://sourceforge.net/projects/cloverefiboot/) Clover config.plist edited by RampgeDev (http://www.insanelymac.com/forum/index.php?app=core&module=attach&section=attach&attach_id=142844) OS X Yosemite DP (from Mac Developer Center) DP2 Patch (see Pike's comments here: http://pikeralpha.wordpress.com/2014/06/17/os-x-v10-10-yosemite-update-1-build-14a261i/) RampageDev X79 DMG (http://rampagedev.wordpress.com/dsdt-downloads/asus-x79/) Mirone AppleHDA edit ALC982 v2 (http://www.insanelymac.com/forum/topic/298663-applehda-for-yosemite-dp2/) Pike's ssdtPRgen.sh (https://github.com/Piker-Alpha/ssdtPRGen.sh) MacIASL (http://sourceforge.net/projects/maciasl/) Kext Wizard (http://www.insanelymac.com/forum/topic/253395-kext-wizard-easy-to-use-kext-installer-and-more/) HWMonitor (http://sourceforge.net/projects/hwsensors/) I'll assume some familiarity with the hackintosh process. I'll note some dead-ends I took so you can either 1) figure out how to make these methods work; or 2) avoid them. 1. Make your USB. Disk Utility -> Parition -> 1 -> Name it "Install" -> Make sure USB type is GUID. Format. Follow directions here: http://www.insanelymac.com/forum/topic/298521-easy-yosemite-1010-usb-installer-updated/ 2. Install Clover. Select new USB. Install to ESP/UEFI. DriversUEFI64 -> Check EMUVariable64/AptioFix. You also might need to install HFSPlus.efi instead of VBoxHFS-64.efi (see here: http://rampagedev.wordpress.com/os-x-10-8-mountain-lion/ Step 2 under Clover). I've found that this is not necessary in Yosemite as it was in Mavericks, but I do it anwyay as apparently HFSPlus.efi is faster. YMMV. 3. Go to EFI partition /EFI/CLOVER/ Copy Rampage's edited plist above. Don't use one on his DMG. 4. Load MacIASL. Open up relevant SSDT on Rampage's DMG. Search for HDEF. Change LayoutID from 01 to 04 (explain why later). E.g.: "layout-id", Buffer (0x04) { 0x04, 0x00, 0x00, 0x00 } Save. Copy to /EFI/CLOVER/ACPI/patched/. Now your USB is ready. 5. Navigate to /EFI/CLOVER/kexts. Create directory 10.10. Go to rampage's SSD and copy Kexts for USB, FakeSMC, and IntelLAN. 6. Set BIOS to boot USB. Install. Note: if you installed config.plist correctly, you shouldn't need to do this, but you'll need bootflag npci=0x2000 to boot into installer. 7. On reboot, select your new Installation. (This is different from Mavericks where you need to go into the installer again.) 8. Go through all the setup processes. 9. Install clover again, but this time on your normal HD. Copy config.plist again. Also copy your edited SSD. (Basically do steps 2 through 4 again, just dont edit the SSDT as you already did.) 10. Install FakeSMC/Intel LAN, USB driver again using KextWizard, this time to /System/Library/Extensions. 11. Eject USB, Restart, enter BIOS, select your drive to boot to. Reboot, make sure everything works. 12. You currently have no PM and are stuck at 1.2GHz. (I was.) Run Pike's SSDT generation script. Rename to SSDT-1.aml. Load it in MacIASL and change APLF from 01 to 04 (this fixes being stuck at 1.2 GHz). E.g: Name (APLF, 0x04) Go to terminal. Run "diskutil list". Find the drive your Yosemite install is on and mount EFI partition: "sudo diskutil mount /dev/diskXs1" where X = your drive number. Copy SSDT-1.aml to /EFI/CLOVER/APCI/patched/" 13. Reboot. Install HWMonitor and make sure you're not stuck at 1.2GHz. You should also have working PM now. 14. Install DP2. The download from the Developer Center (at least for me) installed DP1. Using App Store download of Update 1 (DP2) wouldn't install. Instead I downloaded the patch directly and installed. See Pike's instructions in comments here: http://pikeralpha.wordpress.com/2014/06/17/os-x-v10-10-yosemite-update-1-build-14a261i/. Download OSXUpd1010Patch.pkg and install it. Reboot and check System Information -> Software to make sure you are now on 14a261i (I.e., DP2). 15. Install sound. Download mirone's edited kext. Go to System Information -> Audio and make sure the SSDT is injecting Layout 4. Install Mirone's edited kext with Kext Wizard. Fix permissions and rebuild caches. Make sure you rebuild the kernel cache or the kext won't load. 16. Reboot, but add boot flag kext-dev-mode=1 This is necessary because the above Kext won't load otherwise. 17. Check sound works (System Preferences -> Sound -> Output). Now let's add AppleHDA to Kext Exception List so we can avoid kext-dev-mode=1. Go to /S/L/E/. Copy AppleKextExceptionList to desktop. Edit it (If you use ATOM.io texteditor you can just open it in the text editor, awesome!). Go to Contents/Info.plist. Navigate to: <key>OSKextSigExceptionHashList</key> Then add this to the end: <key>com.apple.driver.AppleHDA</key> <string>1111.1</string> <key>com.apple.driver.AppleHDAHardwareConfigDriver</key> <string>1111.1</string> <key>com.apple.driver.KextExcludeList</key> <string>1111.1</string> Save. Use Kext Wizard to install Kext to /S/L/E/. Repair Permissions and Rebuild caches. 18. Reboot. Don't use kext-dev-mode=1 flag anymore. You should boot fine. 19. Enjoy! NOTES: 1. I have had the odd crash that I don't usually see in Mavericks, but this is to be expected. 2. I could not get sound working use my typical method, which is autopatching using Clover (see: https://github.com/toleda/audio_CloverALC). The kext doesn't load and when I use kext-dev-mode=1 the system crashes on boot. 3. Likewise, I couldn't use Pike's method of patchign AppleHDA described here: http://pikeralpha.wordpress.com/2014/06/30/new-style-of-applehda-kext-patching-for-yosemite/. Same problem as above. 4. When pairing my Trackpad through Bluetooth it asks for a code. 0000 works fine. 5. To be able to log in to the App Store, I had to go to /Library/Preferences/SystemInformation/ and delete the preferences and network interfaces.plist. After restarting access was fine. The problem here is en0 needs to be the Eternet adapater and for some reason on 10.10 it puts my Wifi card first. Otherwise, I'm enjoying a fully functional Yosemite Beta DP2! Credits: RampageDev (http://rampagedev.wordpress.com/ Pike (http://pikeralpha.wordpress.com/) Mirone (http://www.insanelymac.com/forum/topic/298663-applehda-for-yosemite-dp2/) Snatch (http://www.insanelymac.com/forum/topic/298521-easy-yosemite-1010-usb-installer-updated/) toleda (https://github.com/toleda/) Clover (http://sourceforge.net/projects/cloverefiboot/)
  7. Hi there, First of all, I want to say thanks to everyone at insanelymac.com, and RampageDev! I found a ton of useful information here, and thanks to that, was able to build my very first Hackintosh on X79 platform! (not the easiest but I wanted to do it on my gaming rig ) Just finished 10.9 update before upgrading CPU to IB-E 4930K (was using i7 3820 before), and with the patched kernel, I'm now able to boot into OS X 10.9. I have everything working fine excepted for 2-3 glitches. Now, my rig, so you can have an idea: MB: ASRock X79 Fatal1ty Professional CPU: i7 4930K GPU#1: 670GTX GPU#2: 670GTX I'm DSDT Free 'cause DSDT provided by RampageDev in his unified DMG doesn't seem to work on my config this time. Former install, with 2.2 BIOS and i7 3820, it was OK, the DSDT allowed my system to boot up, and to use KEXT provided by RampageDev inside his DMG. So I had to change some KEXT in order to get Network and Audio back. For the Network, I used the modified binary AppleBCM5701Ethernet for Mavericks that has to be put inside AppleBCM5701Ethernet.kext, and edited Info.plist to add device "16b1". For the Sound, I used HDAEnabler1.kext alongside modified AppleHDA.kext for Realtek ALC898. Now, the things I would like to correct, in order to have a fully functional and usable OS 1. Sometimes, boot stops right after having loaded GPUSensors.KEXT... and then nothing happens... Is that because of the outdated sensors KEXT's inside FakeSMC? I'm not quite sure because those KEXT are almost the last ones to be loaded, and, when the system boots up, even if HardwareMonitor reports wrong temperatures, GPU Sensors seem to work OK... 2. I'm having the iMessage "Call Apple Support" error message AGAIN (!!!!!) Any thoughts about that? 3. I can't boot when I install a generated SSDT into /Extra folder. I assume SSDT is correct since I'm using SSDTPRgen.command script that I already used to generate a i5-4770 SSDT which is fully functional... I have tried this when I was still using the i7 3820, didn't retry with i7 4930K though... Do I really have to disable SpeedStep in BIOS in order to achieve proper CPUPowerManagement under OS X? That would be quite annoying since I'm also using this rig as my Windows gaming rig... 4. I can't get properly read temperatures with Hardware Monitor... Does someone know if there exist new sensor KEXT's? PS: I can properly boot into my former 10.8.5 installation that I kept on my backup SSD if it can be useful to enable iMessage (working on 10.8.5, but I didn't log out from service... too scared I cannot log back in ) Thanks!
  8. I have been researching this for over a year through many different resources (including searching Tony's infamous site, and InsanelyMac), and I have pretty much come out empty handed. A friend on Reddit suggested I ask around in here, and I realized this is kind of the central and historical hub for OSX86! I am excited to see such well organized information on loading OSX/MacOS onto a non-Mac computer! I have just recently started asking in the forums, and I have been constantly getting the same responses from other forums I have tried. These responses mostly are kind of subjective, moot points, and sometimes, downright rude. I'm trying to keep things polite and courteous, and so I will lay down what I am trying to do upfront. I would LIKE to be able to build a rig on which I can boot to Windows for gaming/Windows related tasks, and also boot to MacOS for recording/editing audio and video. I would LIKE to have a high performance setup that goes beyond normal 4-core, x16 PCIe lane specs in current gaming i7 setups. We have reached a limit on core speed for the near future, for the most part, and it has become necessary to use more cores, alongside applications that can utilize those cores, to get more performance out of a system. I have looked at real world performance with the i7-6700K and other 4 core processors in the same class, and I don't see it easily pulling the weight I want to throw at it now, much less in the future as software evolves. I am not really interested in hearing the argument about how I don't need more than 4 cores. I am not just gaming here. I've heard this far too many times for it to be worth saying again, but do as you wish. I need low-latency round-trip capabilities for audio so I can monitor with effects ON (wet) while I overdub new tracks. This requires more cores to balance the load. I am not really interested in hearing about how i7 performs much better than XEON, performance vs. price. For my needs, it doesn't necessarily do that. My needs require large amounts of floating point Ops for video rendering, and, while some i7s can do this quite well, server class processors tend to do this better. I can go either way on this though. I have already heard these comments and have taken them into account. I am fully aware of the fact that X99 (and X79?) chipsets are a nightmare to work with on OSX. I am NOT fully aware as to how much of a nightmare, or what is nightmarish about them. No one seems to have a response to those questions. Just that I shouldn't bother. I have found scattered info on some problems with those chipsets, but I don't really have the full picture on why they are difficult or even not possible for my needs. I am seriously interested in rolling up my sleeves, learning some new things, and getting my hands dirty (and possibly very frustrated) figuring out, on my own, how to make a build work! Of course, I cannot do this completely on my own, hence the need for this large wealth of knowledge you all have here! Here are my desired specs for my system: 8 Core i7 or Xeon with over 3GHz and made within the last 3-4 generations. 32GB of the fastest RAM compatible with my system either stock speed or OC (if i7 system is chosen, of course) At least a single GeForce 900 series Nvidia graphics card (or the GeForce 10 series if we have those working in builds now) USB 3.0/3.1 (if possible) The fastest SSD I can use with my setup, whether that be a SATA III drive, a Raid setup, or a PCIe, M.2, or other fast I/O system FireWire connection, or, if possible (which, by my research, seems pretty bleak right now) some Thunderbolt connections At least 2x16 PCIe slots Water cooling system to keep noise down and increase longevity of my system (CPU and GPU) I am seriously, and humbly, asking for your advice on where I should start looking for components to my build. I'm willing to go the distance (or even pioneer groundbreaking new techniques haha!) for getting these specs to work. Is it possible to get a stable build with +4 cores that can do what I need it to do? I already know a system like this would rock out with gaming on Windows, but can I semi-reliably use it for recording/UHD video editing? Remember, I don't rely on this system for money, I have another job (or two) ;^) I would just like to be able to do this for extra money at some point and possibly work it into a business. I just need something that will work for the most part right now. Can anyone here help me in understanding the known limitations of the systems that fit my desired specs? Or perhaps, have some other ideas I haven't considered? I'm open to any replies, even (sigh) including the typical ones I mentioned above, especially if they shed light on the subject. Thank you so much in advance! Mikey P
  9. Using a DSDT that was extracted on a different build with different devices installed, may not work on your system even if you have an identical motherboard and BIOS. If you still would like to try a DSDT edited and extracted by another, rampagedev is the best place to get it. The DSDT edits in this guide are specifically for the Asus Rampage IV Extreme - Socket 2011 - X79 Motherboard, but some may work on similar systems. This guide will walk you through extracting and editing a DSDT from your specific RIVE build using DSDTSE v2 beta. Before We Start A DSDT is a translation of your system's BIOS so: 1) Make sure you are updated to the BIOS you want to extract the DSDT from and set up your BIOS completely and correctly for your system. 2) Make sure you have all your PCI devices installed in the locations you want them before you continue. 3) Remove DSDT.aml from /Extra, if present, or reboot using the "DSDT=No" boot flag. Getting Started Download and open DSDTSE V2 Beta and my list of patches. files.osx86.net/downloads.php?do=file&id=3099&act=down&actionhash=guest http://www.insanelymac.com/forum/index.php?app=core&module=attach&section=attach&attach_id=121230 On the main pane, click "Extract DSDT". Your DSDT will be extracted from your active BIOS in a "Decompiled" window. Click compile. You will be presented with a "Compile error" window. Click "OK". An "Error" window will open showing you all the current errors, warnings, and remarks. Note there are lots of errors. Close the window. Click "Fixcompile". The DSDT should compile successfully and another "Code" window will open. In the "Code" window, note that the DSDT's errors have all been fixed except for one warning. Close the "Code" window. Patching Open my list of DSDT Patches and lets start patching. 1) Add Method DTGP: Copy "Method DTGP" from the list. Click on the right side of the " { " that follows the "DefinitionBlock". Hit the Right Arrow key. The cursor should be at the very start of the next line. Hit enter to make a space. Use the Up-Arrow key to move the cursor up to that space. Paste in "Method DTGP" there. You can change "Name (TMAC, "R4E 3404")" to read whatever you'd like it to. Example: Name (TMAC, "BIG BOB'S BIG DSDT"). I've only added this so I can see what version I've opened for future editing. Click "Fix Compile". 2) Cleaning up unnecessary stuff: Note: This one is not necessary and adds no functionality. Scroll down to Name (OSVR, Ones). Comment out the OS's. Also see example in my list of DSDT patches. Click "Fix Compile". 3) Fix the SIOS Warning: Copy "SIOS Warning" fix. Type "sios" in the search window and click search. Scroll to the bottom of the method and add a space right before the last " } " . Paste the fix in that space. Click "Fixcompile". Note that the last warning is no longer present in the "Code" widow that opens. 4) Get the LPC controller to load and use native OS X kexts: Copy the Device (SBRG) fix from the list. Search for "sbrg". Move the "Decompiled" window over to the left side of your screen so that the left side of the window is cut off right at the edge of the D in "Device (SBRG)". Scroll down until you find the " } " that lines up the the same spot as the D from "Device (SBRG)". This is where SBRG's sub device chain ends. Move the window back over so you can see all of the left side again. Select from right side of the " } " that you found, all the to the left edge. Paste over it with the Device (SBRG) fix from the list. Click "Fixcompile". 5) Remove dedicated IRQs from devices to later give them to the High Precision Event Timer: Type "IRQNoFlags ()" without the " " into the search box. Click "Next". The first match will be in "Device (PIC)". Select from the right edge of "{2}" below it, all the way up to the far left edge of "IRQNoFlags ()". Hit Delete. Click next again. It should now find "{0}" in "Device (TMR)". Delete it. Click next. You should now find "{8}" in "Device (RTC0). Delete it. Click next. You should find "{13}" in "Device (COPR)". Leave this one alone. Click "Next". Continue the same process and delete all the "{1}"s from "Device (PS2K)". Delete all the "{12}"s from "Device (PS2M)". Note: If you are using a PS2 mouse or keyboard, you may need to find different IRQ values to use instead of {1} and {12}. 6) Give Device (HPET) 4 dedicated IRQ values to use so it doesn't try to steal any from USB: Search "hpet" and paste in fix -as in my example on the list. Click "Fixcompile". 7) Add sub-device "Device (BUS0)" to "Device (SMB)" to load native SMBus kexts: Search "Device (SMB)" and paste in fix over the last " } " before the next device. Also see my example on the list. "Fixcompile". 8) Add Device (HDEF) to the end of Device (PCI0) to enable onboard audio with the "Interim IvyBridge" kext from Toleda: Search "Device (PCI0)". Find the end of the device chain the same way we did in the "Device (SBRG)" fix. It's a LONG ways down. For me, the PCI0 device chain starts at line 1670 and ends at line 6286. Paste the fix over the last " } " in the device chain. "Fixcompile". 9) Add AAPL,clock-id 2 to PEX1-4 to allow sleep (SleepEnabler.kext is necessary) while USB 3.0 storage is plugged in: Search "Device (PEX" and hit next until you find "Device (PEX1)". Paste patch in between "Name" and "OperationRegion". Repeat for "Device (PEX2)", "Device (PEX3)", and "Device (PEX4)". Fixcompile. Note: Any drives plugged into USB 3 ports will be force ejected upon wake. They will then automatically remount. This may be solved in the future with more USB 3.0 support from Apple. Fixcompile. Finishing Up Click on the "Compile" tab to get into the compile section. Check the "Autofix errors" box and the "Fixes report" box. Click the "Compile" button. Click the "Gimme my DSDT" button. A finder window will open containing your edited DSDT. It will be named "DSDT.aml". Drag "DSDT.aml" into your "/Extra" folder. Delete or overwrite the old DSDT.aml if one is present. If you haven't installed a boot loader yet, and don't have an "/Extra" folder, place "DSDT.aml" in /Extra after you've installed a boot loader. Verification On the "Main Pane", in the second box, under "Registry Info", click "Get". This will open IORegistryExplorer and show you all the devices loaded and information about them. 1) In the search box of the newly opened IOReg window, enter "hpet". With HPET selected on the left twirl open the disclosure triangle for "IOInteruptSpecifiers". In the "Values" column, the first pair of numbers (they are displayed as Hexadecimals and you will need to convert them to decimal using something like HexDecBin.app) -are the IRQs that HPET is using. You should have, 0c (12), 08, 02, and 01. 2) Find "SBRG" and note that AppleLPC shows up as a sub-device and that it has the native OS X driver loaded. 3) Find "SMB". Note that the device we added, "BUS0", shows up in the device tree and it is using the native OS X driver. 4) At "EUSB" and "USBE", you should see the"AAPL,clock-id" we added. 5) At "PEX1", "PEX2", "PEX3", and "PEX4", you should see the"AAPL,clock-id" we added. 6) Note that "HDEF" should now be present and loaded. Shilohhs_R4E_DSDT_Patches 2.rtf.zip Interim_898_Lion_AppleHDA.zip
  10. Hey guys! Took me about a whole day to figure this out but I finally got macOS Sierra (latest GM release) working for my board. Here are the specs of my Hackintosh. Mobo: Gigabye X79-UP4 Proc: i7-3930K Mem: 4x8GB 1866Mhz Corsair Video: NVIDIA GTX 680 SSD: Mac Here's my EFI (change them to just EFI and put at your EFI partition): X79-UP4 Files.zip For Audio: https://www.dropbox.com/s/kq1ce8dhkecnvox/audio_cloverALC-120_v1.0b0.command?dl=0 https://www.dropbox.com/sh/nvk89cddwe58c3h/AAAqdic9IrzXSBGKbFUvuM_ba?dl=0 Instructions: 1. Burn macOS Sierra your usual way. Put this EFI folder to your EFI installer partition. Upon installation bootup, change the nv_drv=1 to nv_disable=1 until installation completes etc. 2. When you first get to your desktop (still with nv_disable=1), run the AGDPFix program to get full resolution for your NVIDIA card. (If after booting, the screen is black, hard restart then make sure to change the nv_drv=1 to nv_disable=1) 3. To enable audio, mount your EFI partition then drag the audio_clover file to Terminal. Reboot and everything should work now. Congratulations! Everything works (USB3, SATA, Audio, Video, etc) (Sleep I'm not really sure as I seldom leave my Hack on when not in use) I hope this could help some people to save you guys time and energy from figuring it out. Cheers!