Jump to content

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



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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

Categories

  • 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

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 162 results

  1. 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
  2. Hi, this tutorial is about running your physical hackintosh installation in Windows. It's not about setting up a new OS X VM. As always it's very simple once you know, but it however took me a while to figure out the settings, especially using IDE in the VM and using the Clover/EFI partition or not. Luckily, it turned out we have to skip it, so we can leave Clover (or any other bootmanager) untouched. What's the point? If you have to do tasks in Windows, be it mining bitcoins, 3D-rendering, gaming or simply work with a windows-only software, you probably at the same time miss your OS X. The advantages over a simple new virtual machine running with your personal setup are many: Imagine you can use all your data, listen to your iTunes library, use your installed and configured programs and work with your settings. It also comes in handy when you messed up your installation for some reason and want to conveniently fix it. And last but not least don't forget you save the 25GB minimum space for a virtual disk what is probably not sooo insignificant since (I assume) most of us already switched to SSDs and only a few may have picked the models above 500GB because they are still pricy. tl;dr Gain advantages by hooking up your existing Hackintosh installation in a VM and work in your personal OS X environment whenever you like, even under Windows. If you have High Sierra with APFS installed it will most likely not work (yet), because Paragon and probably VMWare don't support the filesystem (yet). That being said, let's get started: 1. Preparing Instructions - do all possible reboots as required while installing - install Paragon HFS+ 11 or above (buy or know where) - install VMWare Player (free for private use) - install Unlocker from Insanelymac (free) 2. in VMWare, set up a new virtual machine - choose "I will install the operation system later" next > - choose "Apple Mac OS X" and "macOS 10.12" next > - choose "Store virtual Disk as a single file" next > and next> - choose 5GB Maximum disk size (we delete it later) and pick "Store in a single file" next > - Finish 3. in VMWare, configure your new machine - click on "Edit the virtual machine settings" - delete your new 5GB virtual Hard Disk (SATA) - click Add... on the bottom, select Hard Disk - select SATA (IDE works, too but I'd prefer SATA in 2017) (UPDATED) - pick "Use a physical disk" - select your harddisk with your OS X installation on it and pick "use individual partitions" - now do not select your UEFI partition, select the partition with your OS X: Example: My Sierra is on my PhysicalDrive 3 which I selected before. As we all know, the EFI partition is always the first partition (0), so my OS X (and probably yours, too) is on the second partition (1). So I check partition 1 and click next and finish. - if all is set and done, close VMWare. 4. check your VMWare .vmx file - replace the green parts with your data and move to "C:\Users\YourWindowsUsername\Documents\Virtual Machines\YourVM-Name\" - open yourVM-name.vmx with the Windows Editor and add the folowing lines only if they are missing: smc.version = "0" firmware = "efi" Click save. 5. VMWare optimization I choose half of my physical RAM, maxed out the graphics RAM and choose half of my physical CPU-Cores in the VM settings. 6. Finalize (UPDATED) Go to your VMWare program folder, right-click on vmplayer.exe and under Preferences > Compatibility > check the "Run as administrator" checkbox on the bottom. And that's it! Screenshots for reference. Now you have your OS X install available in Windows, too. If it asks you for updating the VMWare Tools, click yes or install them with one of the tools in the download section here on insanelymac. You can also add other Harddrives to your VM. What will not work: VMWares unity-mode in Windows - it's not supported for OS X yet. Gaming, the graphic is slow-ish but enough for coding, office, music and all basic tasks.
  3. THIS IS STILL WORK IN PROGRESS Laptop : Sony Vaio- SVE1712W1EB OSX version : 10.13 - High Sierra - SMBIOS - MacBookPro9,1 Motherboard : Intel HM76 Express DSDT FIX : Show Fan RPM's : Updated,now working with Latest Istat Menus and HWMonitor CPU : i7 - 3632QM (2.2Ghz- 3.2Ghz) : Dedicated Graphics : AMD Radeon HD 7650M 2048MB Full QE/CI and Resolution: Fix gradient issue with AMD Graphics the fast way : Fix Brightness issue + brightness fn keys: Fix sleep issue and naming issue with AMD Graphics : Integrated Graphics : Intel HD Graphics 4000 (can't be enabled in bios,no option) Touchpad and Keyboard : Wifi : AR9485 : Ethernet : Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller : Works out of the box Sound : Realtek ALC269 -VC1 : Battery: Works after patching : Built-in Camera : OSX version : 10.12 - Sierra - SMBIOS - MacBookPro9,1 Motherboard : Intel HM76 Express DSDT FIX : Show Fan RPM's : Updated,now working with Latest Istat Menus and HWMonitor CPU : i7 - 3632QM (2.2Ghz- 3.2Ghz) : Dedicated Graphics : AMD Radeon HD 7650M 2048MB Full QE/CI and Resolution: Fix gradient issue with AMD Graphics the fast way : Fix Brightness issue + brightness fn keys: Integrated Graphics : Intel HD Graphics 4000 (can't be enabled in bios,no option) Touchpad and Keyboard : Wifi : AR9485 : Ethernet : Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller : Works out of the box Sound : Realtek ALC269 -VC1 : Battery: Works after patching : Built-in Camera : OSX version : 10.11.6 - El Capitan - SMBIOS - MacBookPro9,1 Motherboard : Intel HM76 Express DSDT FIX : Show Fan RPM's : Updated,now working with Latest Istat Menus and HWMonitor CPU : i7 - 3632QM (2.2Ghz- 3.2Ghz) : Dedicated Graphics : AMD Radeon HD 7650M 2048MB Full QE/CI and Resolution: Fix gradient issue with AMD Graphics the fast way : Fix Brightness issue + brightness fn keys: Integrated Graphics : Intel HD Graphics 4000 (can't be enabled in bios,no option) Touchpad and Keyboard : Wifi : AR9485 : Ethernet : Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller : Works out of the box Sound : Realtek ALC269 -VC1 : Battery: Works after patching : Built-in Camera : UPDATED : October 9. 2016.
  4. Version 5.0.1.27

    1,535 downloads

    for Chipsets : RT2770; RT2870; RT3070; RT3071;RT3072; RT3370;RT3572 ;RT3573; RT5370;5372;RT5572;MT7610;MT7612;MT7650; MT7662; ;RT8070;RT9707
  5. The is the Post-Install topic following the Ryzen Clover Installation Guide for macOS Sierra. If you have yet to install Sierra on your Ryzen machine, check out that thread for help installing. Here we can discuss post install troubleshooting such as well known issues with NVIDIA Drivers, audio interfaces, etc. Here is one workaround for audio that I am using - My audio was not working and I spent days trying to get it to work (ASUS Prime X370 Pro) to no avail. Eventually I bought this for $10 and it worked immediately with no drivers or setup: https://www.amazon.com/gp/product/B072BMG9TB/ref=oh_aui_detailpage_o02_s00?ie=UTF8&psc=1 One question for starters, I am using a Radeon R9 280x with no graphics injection. If I put my Ryzen build to sleep, it changes power states correctly. When Powered back on, the monitors don't turn on. I don't know if this is related to the GPU, or just an issue in general, but in any case I would appreciate any help!
  6. Here are my Specs Processor: i7-4700MQ RAM:6GB HDD : 1TB Graphics: Intel HD Graphics 4600(QE/CI Enabled) AMD Radeon M265 Audio Card :Conexant CX20757 ​Method used to patch audio: AppleHDA Patcher's generated HDAEnabler And AppleHDA Kext Audio Works Excellent... But the microphone won't work ... even if it shows up in the input section of sound preferences..... plz help Laptop is Lenovo G510 (i7 Version)
  7. Hey Guys i have installed MacOs Sierra on my PC lately and i'm having a problem with the GPU , The system only boots if the nv_disable = 1 flag is activated , and it sucks without the graphic acceleration . I tried Nvidia Webdrivers , Kexts .... Changed the System definitions Nothing seems to work . info : I have Yosemite and el Capitan on the same PC and they r working perfectly Fine Photo from el capitan Setup :
  8. The final release of macOS Sierra are available to download. You can download it from App Store. You can consult the list of useful tips created by @fantomas: ​Download macOS 10.13 Beta.app from App Store Error "Your must enroll your Mac to download the beta" or this XCPM patches for unsupported CPUs in 10.13 CloverX64-High.efi Createinstallmedia method Kext injection works again Airport-Extreme fix No need FirmwareFeature in config.plist Clover r4084 Updated firmware/bios versions to support APFS KabyLake iMac SMBIOS details [New] Installation Notes - by @fusion71au [New] Fix for ICH10 with High Sierra. - by @SunKi Soon we'll have the methods to create a Penboot to all Hacks. You can use the createinstallmedia, and after the process been concluded just install Clover in your Pendrive. sudo /Applications/Install\ macOS\ High\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled —nointeraction EDIT: The list above will be constantly been updated as we got new methods and fixes.
  9. The final release of macOS Sierra are available to download. You can download it from App Store. You can consult the list of useful tips created by @fantomas: ​Download macOS 10.13 Beta.app from App Store Error "Your must enroll your Mac to download the beta" or this XCPM patches for unsupported CPUs in 10.13 CloverX64-High.efi Createinstallmedia method Kext injection works again Airport-Extreme fix No need FirmwareFeature in config.plist Clover r4084 Updated firmware/bios versions to support APFS KabyLake iMac SMBIOS details [New] Installation Notes - by @fusion71au [New] Fix for ICH10 with High Sierra. - by @SunKi Soon we'll have the methods to create a Penboot to all Hacks.You can use the createinstallmedia, and after the process been concluded just install Clover in your Pendrive. sudo /Applications/Install\ macOS\ High\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled —nointeraction EDIT: The list above will be constantly been updated as we got new methods and fixes. Click here to view the article
  10. I've just installed High Sierra as a new install under VMware Wkstn 12.5.7 and installed VM Tools but it's not mounting any USB HDDs that I plug in. USB flash drives are mounted OK. The USB HDD is recognised as a device (see External USB 3.0 in the attached screenshot) but Disk Utility doesn't see it. I've closed and re-opened DU a number of times. I've tried VMware Wkstn 14.0.0 and the latest VM tools but still doesn't mount. Has anyone had a similar issue or now what the problem may be? thanks Webby
  11. Hi, after installing Sierra on my machine a strange behavior has started to happen. When I leave the Desktop inactive for an amount of time, let's say 10 minutes, and then start to use it again the OS hangs for 30-45 seconds, I can still move the cursor but the interface is freeze, after that period it regain speed and fluidity and everything came back normal. I've let the Console open during this freeze in order to better understand what's going wrong in the machine and I've found plenty of this error: virtual IOReturn IOGraphicsAccelerator2::newUserClient(task_t, void *, UInt32, IOUserClient **): contexts(0) and queues (747) exceeding limit (512), failing context creation followed sometimes by this statement: kernel: Stalling for detach from nvAccelerator The error time coincide with the hangs so I suppose the problem is something related to IOGraphicsAccelerator2. I've the latest nVidia driver installed and the system works like a charm (sleep included) except for this annoying issue, that I've never experienced with the previous OS. Is anybody able to sort out what the problem is? Thanks in advance.
  12. This thread is a walkthrough on how to install Sierra. These are fully detailed instructions to make it easier for newbs. PLEASE DO NOT PM ME FOR HELP. REPLY TO THIS GUIDE BELOW. THANKS • MY SPECS: 1. Intel Core i7-4770K (De-lidded) 2. EVGA Z97 FTW (ATX) 3. Western Digital VelociRaptor 1TB 4. Corsair Vengeance Pro 16GB DDR3 2400MHz 5. OCZ Vertex 4 512 GB 6. Patriot Dual Bay 2.5" SATA 3.5" drive bay (for SSD) 7. Noctua NH-U12S 8. My case: Modified Apple Powermac G5 9. ASUS BW-12B1ST 10. EVGA GeForce GTX680 SC 11. Silverstone SST-ST1200-G Evolution Strider Gold 1200W • WHAT YOU WILL NEED: 1. macOS 10.12 Sierra [from Mac App Store] 2. A computer running an Intel Processor 3. Access to OS X on VMWare (for Windows), Mac, or Hackintosh 4. 1x supported graphics card 5. Clover v2.3k r3763 and up 6. A USB flash drive at least 8 GB 7. Update your system with the latest BIOS • STEP 1: BIOS SETTINGS 1. AHCI mode and CD/DVD first boot priority are set in the BIOS by default. Ensure your settings match these in your Z97 BIOS: a. Go to ADVANCED→ SATA Configuration→ All settings should set at default; notice that your disks won't show up here if they're connected to black Marvell SATA ports. b. Go to BOOT→ Speaker Beep; switch to 'Off'. Change Boot mode select to 'UEFI'. Continue to FIXED Boot ORDER Priorities→ Check if CD/DVD is 1st Boot (Note that your CD drive will not appear unless there is an UEFI enabled CD inside; Scroll down to Hard Disk Drive BBS Priorities to set the boot sequence of the available hard disks (Note that if at least one hard disk is not configured with EFI bootloader then 'Hard Disk Drive BBS Priorities' menu will not show up). Go to CSM Configuration; Launch CSM = 'Disabled'; This enables the bootloader menu screen to load with native HD as specified by your monitor. NOTE: If you are multi-booting with Windows 7, it is MANDATORY that Launch CSM = 'Enabled' (Launch PXE OpROM policy = 'Do not launch', Launch Storage OpROM policy = 'UEFI only', Other PCI device ROM priority = 'UEFI OpROM'); The lack of these settings can cause the following error when starting up your Windows 7 boot drive: Windows failed to start. A recent hardware or software change might be the cause. File: \EFI\Microsoft\Boot\BCD Status: 0xc000000d Info: An error occurred while attempting to read the boot configuration data It will also prevent any non-UEFI boot disks from appearing in the UEFI BIOS (e.g. CD/DVD, Windows 7 USB Keys, etc.) c. Go to ADVANCED→ Power Management→ ACPI Sleep State is S3 only (Suspend to RAM). d. Go to ADVANCED→ Graphics Configuration→ Disable internal graphics. e. Go to ADVANCED→ CPU Configuration; there is no option for Vt-d, so disable Intel Virtualization Technology (during installation). f. Go to ADVANCED→ USB Configuration→ Disable XHCI Mode. g. [OPTIONAL] Go to MEMORY; Under Memory Multiplier Configuration, set Performance Memory Profiles to XMP Profile 1. h. [OPTIONAL] Go to ADVANCED→ H/W Monitor Configuration→ Set all fan speeds to 50%. Save and Reset. • STEP 2: CREATING A BOOTABLE USB TO INSTALL OF SIERRA 10.12 1. Clover and the macOS installer are placed on separate partitions on the USB stick. This guide will use 'diskutil list' in Terminal instead of Disk Utility to format the USB with GPT partitioning for Clover UEFI support. 2. You must determine its disk identifier before you can partition the USB. Plug the USB stick into a Mac (or Hackintosh), run Terminal and type 'diskutil list'. The following screenshot will serve as a reference: As you can see the the USB stick’s identifier is /dev/disk4. 3. Type the following entry into Terminal to format the USB stick (two partitions, via GPT): diskutil partitionDisk /dev/disk4 1 GPT HFS+J "OS X" R During the process the following occurred: /dev/disk4 GPT partitioning initiated by default EFI was automatically created remainder "OS X", HFS+J is partitioned 4. It resulted in the following screenshot: Close Terminal 5. We need to download and install the latest version of Clover (here) on the USB stick. a. Run the pkg, "Change Install Location" by selecting "OS X" (partition name) as the target of the install. Use the following settings below: Make sure that it shows "Installation Complete." NOTE: When installing to HDD select "Install RC scripts on target volume" and/or "Install all RC scripts on all other boot volumes" and "Install Clover Preference Pane". 6. You must copy your kexts to the EFI/ Clover folder. You can use EFI Mounter v1.2.3 when necessary to mount the EFI partition, just use "diskutil list" first to ensure you chose the right one for the USB stick. a. Remove EFI/CLOVER/kexts/10.6, 10.7, 10.8, 10.9, 10.10, 10.11 leaving just 'Other'. Create a folder titled '10.12'. b. Copy the required kexts FakeSMC.kext, VoodooPS2Controller.kext (for PS/2 keyboard), and your ethernet kext (Intel I219-V) IntelMausiEthernet-V2.2.0 or AppleIntelE1000e v3.3.3 to the following directory: /EFI/CLOVER/KEXTS/10.12. NOTE: If you are having trouble getting Ethernet to work you can also try copying IONetworkingFamily.kext from S/L/E to /EFI/CLOVER/KEXTS/10.12 with your networking kext. 7. Use a text editor/plist editor like PlistEdit Pro to modify your config.plist manually. We must apply the following mandatory patches: a. You must add line ACPI/SSDT/DropOem=false in config.plist in order to boot without "Still waiting for root device" error. Add this <dict> entry to EFI/CLOVER/config.plist: <key>ACPI</key> <dict> <key>DSDT</key> <dict> <key>DropOEM_DSM</key> <false/> </dict> b. Use Clover’s built-in kernel patch to automatically apply the code to patch the (new) kernel after each OS X update to prevent reboot loop: <key>KernelAndKextPatches</key> <dict> <key>KernelPm</key> <true/> </dict> <key>Memory</key> <dict> c. AppleAHCIPort Clover patch disables orange drive icons. Add this <dict> entry to the config.plist: <key>KextsToPatch</key> <array> <dict> <key>Comment</key> <string>External icons patch</string> <key>Find</key> <data> RXh0ZXJuYWw= </data> <key>Name</key> <string>AppleAHCIPort</string> <key>Replace</key> <data> SW50ZXJuYWw= </data> </dict> </array> d. SMBIOS. With the config file still opened in your text/plist editor, scroll down to SMBIOS section to add the following SMBIOS system definition: <key>SMBIOS</key> <dict> <key>Manufacturer</key> <string>Apple Inc.</string> <key>ProductName</key> <string>iMac14,2</string> <key>Trust</key> <false/> </dict> NOTE: Macmini6,2, iMac13,2 and iMac13,1 support speedstep.You can also do this using Clover Configurator: In the SMBIOS section, click the magic wand to select a SMBIOS relevant to your hardware (e.g. iMac14,2) – and close the screen and File/Save. e. GUI. Here you indicate the theme you want to use that you installed by entering the title in the string. I chose to use "random" as shown below: <key>GUI</key> <dict> <key>Mouse</key> <dict> <key>DoubleClick</key> <integer>500</integer> <key>Enabled</key> <true/> <key>Mirror</key> <false/> <key>Speed</key> <integer>8</integer> </dict> <key>Scan</key> <true/> <key>Theme</key> <string>random</string> </dict> f. Boot Flag. It is necessary to use "-v" to monitor if any problems arise. Add this <dict> entry to the config.plist: <key>Boot</key> <dict> <key>Arguments</key> <string>-v</string> </dict> g. NVIDIA graphics cards especially 'Maxwell' currently lack support natively in macOS. To correct this problem, it requires System Parameter/NvidiaWeb entry. It must be disabled during installation by adding this <dict> entry to the config.plist: <key>SystemParameters</key> <dict> <key>InjectKexts</key> <string>YES</string> <key>InjectSystemID</key> <true/> <key>NvidiaWeb</key> <false/> </dict> h. SIP. Apple has implemented 'rootless' security or System Integrity Protection (SIP) (reference sources 1, 2, & 3) since 10.11 which restricts users from modifying system folders/files, and as a result it locks down system folders and files against hacks and root attacks, making the system safer. However, SIP must be disabled in order to install anything (i.e., kexts) into protected system folders. Add this <dict> entry to the config.plist: <key>RtVariables</key> <dict> <key>BooterConfig</key> <string>0x28</string> <key>CsrActiveConfig</key> <string>0x3</string> </dict> i. Audio Fix. This Haswell board comes with a Realtek ALC898 audio chip. In order to use AppleALC/CloverALC (discussed further in this guide), you must add the following patch in the config.plist: <key>KextsToPatch</key> <array> <dict> <key>Comment</key> <string>t1-10.9-10.11-AppleHDA/Realtek ALC898</string> <key>Find</key> <data> ixnUEQ== </data> <key>Name</key> <string>AppleHDA</string> <key>Replace</key> <data> mQjsEA== </data> </dict> </array> 8. Preparing OS X partition. Download macOS v10.12.0 Sierra [Mac App Store] and Right-click "Install macOS Sierra" will be in /Applications. a. Right-click "Install macOS Sierra" → Show Package Contents → Contents → ShareSupport → Double click to mount "InstallESD.dmg". b. Once "OS X Install ESD" appears, use ShowHiddenFiles to show hidden files. c. Now you will see an image called "BaseSystem.dmg" appear. Mount it by right-clicking and opening it with DiskImageMounter... NOTE: The version of Disk Utility found in El Capitan has been stripped down of its most essential features to proceed with the following instructions. Your next best option is to use a pre-modified version of the old Disk Utility. After downloading it, extract and copy it to the Desktop and type the following line in Terminal to take ownership, enabling the app to run: sudo chown -R 0:0 ~/Desktop/Disk\ Utility.app d. Open Disk Utility. Select and highlight the volume "OS X Base System", click "Restore" at the top-right, drag the volume into "Source" field, and drag the USB [OS X] partition (you already created) to the "Destination" field where you will restore the image: click the "Restore" button then "Erase"... e. After the process is complete, you'll now have (2) "OS X Base System" present in Finder. Eject the image "BaseSystem.dmg" and close Disk Utility. f. On the remaining volume "OS X Base System" (USB stick), go to System/Installation and delete Packages symlink. g. Open "OS X Install ESD" in a new Finder window, and copy the Packages folder to System/Installation folder inside "OS X Base System". h. Copy BaseSystem.chunklist, BaseSystem.dmg, AppleDiagnostics.chunklist, and AppleDiagnostics.dmg from "OS X Install ESD" and copy it to the volume root. i. Create a new folder named "Kernels" in System/Library on the USB stick. Use Pacifist v.3.2.17+ to extract "kernel" from "OS X Install ESD/Packages/Essential.pkg[/system/Library/Kernels/kernel]" and place "kernel" into System/Library/Kernels/ location. j. Use ShowHiddenFiles to hide the hidden files, and quit the application. k. With the USB installer ready, remember before restarting system to change boot priority of USB stick to first to install Sierra on the hard disk of choice. l. Highlight the USB installer from the bootloader menu screen and type kernel boot flag nv_disable=1 to avoid a blank screen (for Maxwell+ GPU's), resulting in 'No Display' signal. m. Once the installer is finished, it will automatically restart the system. Boot from the USB installer and select the drive where you installed Sierra. • STEP 3: macOS 10.12 Post-Installation 1. As the system is loading, you'll be prompted to the macOS Welcome screen. a. Select your country then click "right arrow" to go to the next screen. b. Select "My computer does not connect to the Internet." c. Select "Don’t transfer any information now." d. Do not "Enable Location Services on this Mac" e. Agree to "Terms and Conditions." f. Enter your name, password, and hint and Continue. g. Confirm "Diagnostics & Usage" h. Wait a moment for the macOS desktop to load. i. When prompted to back up any disk with Time Machine, click on the "Don't Use" button. • STEP 4: macOS 10.12 Post-Installation (Continued) 1. macOS Sierra no longer allows unsigned apps to run that did not come the App Store or identified developer. You can re-enable this function by running the following in Terminal: sudo spctl --master-disable Go to System Preferences → Security & Privacy and disable GateKeeper to allow installation of software by unidentified developers. 2. Mount the EFI partition of the USB stick with EFI Mounter v1.2.3 and copy the 'EFI' folder to the EFI partition of Sierra boot disk. 3. Install Clover v2.3k on the Sierra install HDD partition you plan to boot from. In addition to the settings configured earlier, select "Install RC scripts on target volume" and "Install Clover Preference Pane" when installing to the HDD. Installing RC scripts enables nvram variables required for iCloud and other services. It processes logs that are located in /Library/Logs/CloverEFI. You can also type bdmesg > Desktop/boot.txt in Terminal to get them manually. 4. Edit the config.plist from your boot disk in EFI/CLOVER/ by adding the following <dict> entries: a. New Method for Enabling NVIDIA Web Drivers. Boot flag nvda_drv=1 no longer works in config.plist to enable Web Drivers. A new setting under System Parameter in Clover called "NvidiaWeb" has been updated to fulfill this instead. <key>SystemParameters</key> <dict> <key>InjectKexts</key> <string>YES</string> <key>InjectSystemID</key> <true/> <key>NvidiaWeb</key> <true/> </dict> Remove Boot/Arguments/nvda_drv=1 if necessary. b. Hide UEFI partitions. To hide internal UEFI (i.e., "Boot Windows from Recovery", "Boot Windows from EFI") you have to use Scan/Legacy=false: <key>GUI</key> <dict> <key>Scan</key> <dict> <key>Legacy</key> <false/> </dict> c. Designate name of boot menu entries (Renaming Mac/Windows). In the Clover bootloader menu you will notice all EFI Windows partitions labeled "Boot Microsoft EFI boot menu from EFI [or SYSTEM]". The Windows partition is called EFI but there's also a Mac partition called EFI which is hidden by default in the Clover boot menu so it's a nonfactor. The volume names are what Clover shows by default. In order to change what the Clover boot menu shows your volume name to be you will have to specify its details under GUI/Custom/Entries section in your config.plist. There are 3 <key> tags necessary to edit in this section: Volume, FullTitle, and Type. You can refer to my personal settings below for help. E.g., in my config.plist, my macOS volume is called "SIERRA" because that's what I named the partition I installed macOS on. It can also be seen as a bootloader screen entry as "Boot Mac OS X from XXXXXXXX" where XXXXXXXX is the volume name. "FullTitle" is the name you want the entry to say, i.e.: macOS 10.12 Sierra. "Type" is where you indicate what type of OS it is, i.e.: OSX (or Windows). Tags such as "Hidden" and "Disabled" are self-explanatory, while the "NoCaches" tag designates whether you want to boot without caches. NOTE: Adding "InjectKexts" causes infinite loading on the Apple logo screen: YOU HAVE BEEN WARNED. NOTE: Having more than one Windows installation will cause multiple "Boot Microsoft EFI boot menu from EFI" items to appear In the Clover bootloader menu. To change its volume name that Clover shows it requires identifying its individual GUID and adding it as a 'string' under the Volume <key> tag. Launch the Terminal and type the following into the command line: diskutil list A list of drives will populate along with sublist of its partition scheme. Now look for the partition generally listed under your Windows disk as "EFI - NO NAME". E.g., my disk is "0" and the EFI partition is "2". I would type the following into terminal: diskutil info disk0s2 [replace 0 and 2 according to your drive and partition number] It will then printout all the info specific to that partition. All you need to use is the "Disk / Partition UUID", NOT the Volume UUID. <key>GUI</key> <dict> <key>Custom</key> <dict> <key>Entries</key> <array> <dict> <key>Volume</key> <string>A7649550-D460-49CF-9531-829D58F123DC</string> <key>FullTitle</key> <string>Windows 8</string> <key>Hidden</key> <false/> <key>Disabled</key> <false/> <key>Type</key> <string>Windows</string> <key>VolumeType</key> <string>Internal</string> </dict> <dict> <key>Volume</key> <string>EFI</string> <key>FullTitle</key> <string>Windows 10</string> <key>Hidden</key> <false/> <key>Disabled</key> <false/> <key>Type</key> <string>Windows</string> <key>VolumeType</key> <string>Internal</string> </dict> <dict> <key>Volume</key> <string>SIERRA</string> <key>FullTitle</key> <string>macOS 10.12 Sierra</string> <key>Hidden</key> <false/> <key>Disabled</key> <false/> <key>InjectKexts</key> <false/> <key>NoCaches</key> <false/> <key>Type</key> <string>OSX</string> <key>VolumeType</key> <string>Internal</string> </dict> </array> </dict> d. USB patch. Sierra 10.12 requires the port limit to be raised in order for USB 3.0 ports to be recognized. This process involves installing FakePCIID.kext as well. Add this <dict> entry to the config.plist: <key>KextsToPatch</key> <array> <dict> <key>Comment</key> <string>change 15 port limit to 20 in XHCI kext (9-series) 10.12</string> <key>Find</key> <data>g710////EA==</data> <key>Name</key> <string>AppleUSBXHCIPCI</string> <key>Replace</key> <data>g710////FQ==</data> </dict> </array> Be sure to copy FakePCIID.kext and FakePCIID_XHCIMux.kext to /EFI/CLOVER/KEXTS/10.12. NOTE: Set 'XHCI Mode' to Smart Auto in the BIOS to enable USB 3.0. 5. Remove Recovery partition. Deleting and merging a partition with 'diskutil' from the command line is the most precise method to remove the partition since it targets the recovery disk directly and merges it with the full Sierra partition. Launch the Terminal and type the following into the command line: diskutil list This will print out your drives partition scheme and look something like this: Look for "Recovery HD" and see which identifier it uses. In this screenshot it’s disk2s4. To remove that partition we use the following command (you can also use the volume name): diskutil eraseVolume HFS+ Blank /dev/disk2s4 The partition will be erased. You’ll now have a blank partition sitting around, so you’ll want to merge that with your other Sierra partition: diskutil mergePartitions HFS+ SIERRA disk2s3 disk2s4 This will merge the two partitions, with disk2s3 absorbing the space from disk2s4 and expanding, it causes data loss so don’t expect this to preserve anything. 6. NVIDIA graphics cards 'Maxwell'+ currently lack native support in macOS 10.12 so you will not be able to boot without nv_disable=1 kernel flag. a. Download and install NVIDIA Web Driver 367.15.10.05f01 to enable NVIDIA Graphics Cards because they won't work OOB without them. NOTE: Remember to go to the NVIDIA Driver Manager menu bar at the top, change the settings to use Web drivers. Changes will take effect after restart. 7. Reboot using the USB installer and choose the Sierra install drive. 8. Download CUDA 7.5.30 drivers (increases GPU computing performance) needed for 10.12 support and install. 9. [OPTION 1] Install AppleALC to enable native audio by injecting the layout id supported for ALC898 through dynamic patching without modifying any kexts. Audio will no longer be affected after each macOS update and SIP can remain enabled. More details here. NOTE: AppleHDA must be native, original and unpatched. a. Mount EFI partition and add the following entry under Devices/Audio in the config.plist to inject working layout id 1 (or 2 or 3). <key>Devices</key> <dict> <key>Audio</key> <dict> <key>Inject</key> <integer>1</integer> </dict> b. Download the latest version of AppleALC (v1.0.18) and copy it to CLOVER/kexts/10.12. NOTE: Rebuild kext cache if you have removed a modded AppleHDA to replace it with a native one by using Kext Utility or 'force rebuild cache' in Terminal: sudo –s sudo touch /System/Library/Extensions 10. [OPTION 2] Install the following patch associated with Realtek ALC898 AppleHDA Audio (by Toleda): a. Mount EFI partition, verify "Disable SIP" entry CsrActiveConfig=0x3 is in config.plist. b. Download audio_cloverALC-120.command.zip and extract "audio_cloverALC-120_v1.0d.command". c. No edits made to any native AppleHDA.kext file, 2-4 files added to Resources folder. NOTE: There may be noticeable pops before starting playback which is caused by OS X putting the audio codec to sleep. Disable AFGLowPowerState in config.plist with following <dict> entry: <key>Devices</key> <dict> <key>Audio</key> </dict> <key>AFGLowPowerState</key> <false/> </dict> If popping is still exists after using the method above, try using antipop. NOTE: There may be noticeable distortion after around 2 minutes of audio playback. Update to the latest version of Clover and add UseARTFrequency=false entry in the config.plist: <key>CPU</key> <dict> <key>UseARTFrequency</key> <false/> </dict> <key>Devices</key> <dict> 11. Create a DSDT??? (More to come later) 12. [OPTION 1] Create a SSDT (Secondary System Description Table) to configure the maximum clock speed. a. Download Pike's ssdtPRGen.sh script which should auto-copy into your home directory, 'Volumes/Users/<username>' folder. Open Terminal and type the following: curl -o ~/ssdtPRGen.sh https://raw.githubusercontent.com/Piker-Alpha/ssdtPRGen.sh/Beta/ssdtPRGen.sh b. Next, set the execute/search bits: chmod +x ~/ssdtPRGen.sh c. Run ssdtPRGen.sh script for first time without any arguments and let it download all the data that you need: ./ssdtPRGen.sh d. The Haswell.cfg should have already downloaded. e. Once finished you will have the ssdt.aml on the ~/library/ssdtPRGen/. Move it to /EFI/CLOVER/ACPI/patched. NOTE: If you come across issues try the following: ○ Use Terminal to ensure Haswell.cfg is in the 'Data' folder by typing: open ~/library/ssdtPRGen/Data ○ You can remove any previously generated and downloaded script file by typing: sudo rm -R ~/Library/ssdtPRGen ○ You can rerun another freshly downloaded ssdtPRGen.sh script with your processor type: ./ssdtPRGen.sh ○ For additional help see also: ./ssdtPRGen.sh -help 13. [OPTION 2] Create a SSDT (Secondary System Description Table) to configure the maximum clock speed. a. Download the Pike’s script v14.1 (modified for i-core processors) and put it on your desktop. Use it only for the PC it is running from. The script reads some information specific about your CPU and its number of cores. b. Open Terminal and type "sudo" then leave a space and drag the script file into the Terminal window then leave a space and type in the Turbo Speed (Maximum Turbo Frequency) for your processor and then press enter. e.g., Intel Core i7-4770K type code: sudo /Users/"YourUsername"/Desktop/ssdtPRGen.sh -TURBO 3500 Type your password when prompted and press Enter. c. Ignore the following "Error: Unknown processor model ..." since the CPU is unsupported. d. A decompiled file called SSDT.aml will generate in a hidden folder "tmp". Type "open /tmp" (no quotations) to reveal its location. e. Mount EFI using EFI Mounter v1.2.3 and place SSDT.aml into /Volumes/EFI/EFI/CLOVER/ACPI/patched/ folder. 14. Installing the following kexts/widget is optional. Mount the EFI partition to copy the kexts into the /EFI/CLOVER/KEXTS/10.12 folder. Install the widget using Launchpad → Dashboard: ○ HWSensors 6.23.1417 Binaries (with FakeSMC): Helps you monitor CPU, memory, disks, network, temperatures, fans, load/uptime, and processes. 15. Install iStat Pro 4.92 r2, a highly configurable widget that lets you monitor every aspect of your Mac including CPU, memory, disks, network, battery, temperatures, fans, load & uptime and processes. • STEP 5: Updating to 10.12.2 1. Download and install macOS Sierra 10.12.2 Combo Update and reboot. 2. After restarting, accept the popup window that prompts you to download and install the latest the NVIDIA Web Driver 367.15.10.25 to proceed. 3. Download CUDA 8.0.57 drivers needed for 10.12.2 support from NVIDIA and install and reboot. 4. Reinstall audio by patching AppleHDA with audio_cloverALC-120.command.zip [for OPTION 2]. • STEP 6: Updating to 10.12.3 1. Download and install macOS Sierra 10.12.3 Combo Update and reboot. 2. After restarting, accept the popup window that prompts you to download and install the latest the NVIDIA Web Driver 367.15.10.35f01 to proceed. 3. Download CUDA 8.0.63 drivers needed for 10.12.3 support from NVIDIA and install and reboot. 4. Reinstall audio by patching AppleHDA with audio_cloverALC-120.command.zip [for OPTION 2]. • STEP 7: Updating to 10.12.4 1. Update to the latest version of Clover v2.4k. 2. Download and install macOS Sierra 10.12.4 Combo Update and reboot. 3. After restarting, accept the popup window that prompts you to download and install the latest the NVIDIA Web Driver 367.15.10.45f01 to proceed. 4. Download CUDA 8.0.71 drivers needed for 10.12.4 support from NVIDIA and install and reboot. 5. Install NVIDIA Web Driver 378.05.05.05f01 and CUDA 8.0.81 for Pascal card support. a. Remove any trace of GPUSensors.kext or it will cause "System uptime in nanoseconds…" kernel panic if you plan to update HWSensors 6.25.1426 Binaries (with FakeSMC). b. System Parameter/NvidiaWeb can be set to "false" since the motherboard has native working hardware NVRAM. 6. Update to the latest version of FakePCIID & FakePCIID_XHCIMux. 7. Update to the latest version of AppleALC v1.1.1 accompanied with Lilu.kext [for OPTION 1]. 8. Reinstall audio by patching AppleHDA with audio_cloverALC-120.command.zip [for OPTION 2]. • OPTIONAL: Fixing Time Sync issue with macOS/Windows – Registry Fix Method NOTE: Only works for Vista/Windows 7, 8 & 10 1. Press the Win + R keyboard combination to bring up a run box, then type "regedit" followed by Enter. Confirm "yes" once UAC prompt appears. 2. When the registry editor opens, navigate to: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\TimeZoneInformation 3. Right-click on the empty space right below 'TimeZoneKeyName' and create a new DWORD (32-bit). It will appear as D-WORD On 32-bit versions of Windows 7/Vista. 4. Rename it "RealTimeIsUniversal" (without quotes and it’s case-sensitive). Double-click on the new DWORD and change its value data "0" (zero) to "1" (one) as a hexadecimal. 5. Save everything. Reboot to macOS, set the time properly and now boot back to Windows. You should notice it adjusted the correct time. NOTE: Avoid changing the time in macOS if you are running a multi-boot system. You only have to modify the time in the BIOS and in Windows followed by enabling the setting to sync the clock with online time. WORKING-config.plist-for-Z97.zip
  13. thiagodss

    Sem som

    Oi pessoal. Montei um PC para instalar o OSX com peças recomendadas, mas estou atualmente sem som. Já testei o som com um live cd do Xubuntu e rolou sem problemas. Tentei usar o AppleALC mas não obtive sucesso. Estou com o Sierra instalado, versão 10.12.2 Minha placa-mãe é uma Gigabyte GA-Z170X-UD5 com um Core i7-6700 e placa de vídeo GeForce GTX750Ti.
  14. Hi guys, I just recently bought a HP Workstation Z640 featuring: CPU: Dual XEON E5-2609 v3 Chipset: Intel C612 Chipset GPU: NVidia GTX 980 Audio: Realtek ALC221 Ram: 16GB Lan: Intel I-218 Gbit LAN PCIe: HP Z Turbo Drive 256GB SSD HP Z640 specs: http://www8.hp.com/h...x/c04400040.pdf And I wanted to try if it was possible to install OSX on this little buddy. The fact is that I'm a total newbie with Hackintosh and I don't know where to look for (fore compatibility), what to look for and how to proceed. Could you please help me? Thanks in advance,
  15. Anyone can help me? I've got brightness full after restart/boot. I've been try to reinstall clover with emuvariableUefi-64.efi and install RC Script but its still same. I even set my Nvram to Always in Clover Prefpane. I dont know i think all asus laptop has same issue with me, Any suggestion?
  16. Hello! I finally succeeded. I have an old 80GB SATA hard disk which I use to experiment with Mac OS. I had a Mac OS X 10.11 El Capitan installation complete with Office and other applications. Using Clover 3322 in iATKOS EC installer I managed to successfully boot it from within a virtual Mac in VMWare Workstation 10 (patched to support Mac OS). The SATA disk was connected to a SATA-USB adapter and then connected to the virtual Mac as a USB disk. I downloaded Sierra, but instead of creating a USB installation medium I stupidly tried to just upgrade by running the setup. The installation didn't succeed of course but while connecting and disconnecting the USB installer and the USB disk amd forcing several resets I finally screwed the partition and could not boot either in VMWare or natively in my PC. So I reinstalled El Capitan natively and then booted within VMWare. I successfully did all the upgrades up to version 10.11.6 and then downloaded Sierra again. This time I used Pandora's Box to create the USB installer. I booted the USB installer in VMWare and I installed 10.12 Sierra. For some reason it took a couple of hours, but it finally succeeded! It even made the sound and graphics work out of the box without having to install the VMWare Tools! Thank you for creating Pandora's Box! Pity I now have to reinstall all my applications...
  17. Successfully booted Sierra and installation went smooth installed. Used Pandora to creatinstallmedia But I need help with audio missing(didn't try anything yet) fix screen flickering(annoying) both graphics Nvidia 940m and intel hd 520 show as 0 mb but probably just cosmetic issue WIFI(Critical issue) mostly setups I made via bluetooth (tethering from my phone) Im attaching system specs help would be very appriciated! here is my efi clover configuration in case someone shares the same laptop and so someone may assist help would be again very much appriciated!! Efi clover configuration folder ACER ASPIRE E5-574G-52QU.htm EFI.zip
  18. Hi all. I'm after a bit of help with installing Sierra GM. The system this post pertains to is an EX58-UD5 with Nehalem i7 920 and Nvidia 480 GTX, all working perfectly since the snow leopard days. Updates have always been a case of clicking update and waiting, until now that is! I'm running 10.11.6, I've updated clover to r3726 (latest build from sourceforge), I've downloaded Sierra from the app store, clicked install, rebooted, selected the install media. Grey screen with beach ball/spinner. I can move the mouse, the system sleeps and wakes but just doesn't bring up the installer. So I updated fakesmc to 6.20.1410 (the latest I could find from HWsensors). Same issue This is usually what happens when fakesmc doesn't get loaded, but seeing as the install media is read only I can even load fakesmc through single user mode on the way in. I can't even run kextstat as it doesn't exist on the installer. I then created a USB with createmedia --nointeraction, looked on the USB and theres no sign of S/L/E or L/E to dump fakesmc into. So I put my working EFI folder (with updated clover and fakesmc, boots 10.11 ok) onto the USB. I also put my dsdt on there in the root and in ACPI/patched. Same issue, grey screen. I have tried booting with nv_disable=1 which results in the same grey screen with beach ball/spinner but at a reduced resolution. So what I plan to do next is to recreate the installer using the restore method and put fakesmc somewhere that is loaded by the kernel, but before I do I wanted to ask, does this sound like a fakesmc problem or something else. I can't see why clover would not be injecting fakesmc but I can't run kextstat from single user mode as it doesn't exist on the installer. Help!
  19. Thestral

    Sierra su Asus X54C-NS92

    Salve, da qualche anno sono possessore di un ASUS X54C-NS92 e mi piacerebbe provare OS X, sono alle primissime armi quindi vi chiedo aiuto per eseguire questa cosa, il mio PC ha un Intel Pentium B960(so che non è nativamente compatibile ma spero che si possa fare qualcosa), 6GB di ram DDR3, come scheda wifi ho una chiavetta esterna compatibile con OS X, per il touchpad non mi interessa dal momento che è rotto fisicamente. Cosa ho a disposizione: OS X su VMWare, quindi vorrei sapere con quali settaggi fare la chiavetta (Bios legacy) e come far andare il processore. Grazie in anticipo
  20. Hola gente, al fin logre instalar Sierra en mi HP probook 640 g2 con procesador I5 6200U, con tarjeta grafica intel hd520, todo funcionando correctamente, utilize el metodo de Tonymac para probooks, el audio, la grafica, el brillo esta funcionando correctamente, el problema radica en el WIFI, mi adaptador es el BCM943228Z el cual hasta lo que se no es compatible, quisiera pedirles ayuda, si es que alguien sabe como hacerlo funcionar o en locontrario que adaptador podria usa, que modelo seria compatible, ya que no es una opcion usar un usb ya que el computador solo tiene dos puertos, aparte tengo un problema con el ethernet, el cual si se desconecta el cable de red y se lo vuelve a conectar deja de funcionar, gracias de antemano.
  21. Hello everybody. I need help to understand and use some patches that Pike R. Alpha has found for XCPM on his Broadwell-E cpu on X99 board. Here's the article. My knowledge is not enough to elaborate it and apply to Clover bootloader (or, I guess to the kernel itself). I think this is going to be huge. Even for Haswell-E and Ivy Bridge-E cpus. He's found some solution to have XCPM without VoodooTSCSync.kext, MSR(0xE2) unlocked BIOSes, AppleIntelCPUPowerManagement.kext, NullCPUPowerManagement.kext, FakeCPUid flag, etc... My set up (to be in a few day, components on their way) - Motherboard Asus X99-A II - CPU Intel i7 6900K Broadwell-E - RAM 64 GB DDR4 Corsair CMK32GX4M2B3000C15R Vengeance LPX - SSD nvme Samsung MZ-V5P512BW 950PRO m.2 - Video card EVGA nVidia GTX980 TI - ASUS ThunderboltEX II/Dual PCI-E card - OS X 10.11.6 El Capitan Yes, he's on Sierra DP3, but I (and many others, I might say) still am on 10.11.6 El Capitan or earlier (Yosemite). Anybody here? Thanks in advance g.
  22. Linksys AE6000 on macOS Sierra So after a bit of work I got Sierra installed on to my MacBook Air 2,1! The only issue is wifi. To remedy this issue till I can get a new wifi card, I decided to see if I could use my Linksys AE6000 on Sierra. Requirements: Linksys AE6000(or similar RT2870 card) Yosemite RT2870 kext D-Link Pref Pane(DWA-140, thanks! @rodrigocunha) Kext Utility To get the Yosemite kext for the RT2870, I had to go through Mediatek's installer with Pacifist. I did try the Mavericks kext from the other RT2870 thread but it didn't work. The files will be attached below! (RT2870 Kext,DWA-140 Pref Pane file,Kext Utility Now to the process: I'm not sure if order matters but I had the DWA-140 Pane installed already Next drag and drop the RT2870 USB WiFi in to Kext Utility Reboot(with or without your USB Adapter attached) Your adapter should be blinking or working with the DWA-140 Utility Have fun, enjoy! RT2870USBWirelessDriver.kext.zip DWA-140WirelessUtility.prefPane.zip Kext Utility.app.zip
  23. Hi! Yesterday I downloaded Sierra and El Capitan retail and put it to my usb using [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url]. (I have tried transmac also, same result). I booted to my clover but unable to reach the installer. But when I use distro (niresh yosemite) I can install it. But yosemite was laggy so I want to try another. Boot flags I have tried: GraphicsEnabler=no GraphicsEnabler=yes cpus=1 /amd64 -x -F npci=0x2000 and 0x3000 My specs AMD Radeon 8180 HD Graphics @1GHz, 2GB RAM. The usb i used partitioned with GUID partition table. I tried on another laptop (amd and intel) and had the same result My verbose mode said in picture attached. After showing that it just shut down and booted again into clover. Sorry I haven't attached the photo
  24. Just have a couple of questions which I'm pretty sure have simple answers but I cant for the life of me figure it out 1.When I start clover I get many options. There are 3 which I don't understand, and that don't work, they are boot windows with legacy HD1 boot windows with legacy HD2 Boot windows from EFI The ones that do work are boot OS X from sierra boot microsoft efi from efi I'd like to know why those first 3 are there, and how to get rid of them. 2.I installed clover from the source forge page, clicked customize and chose install for uefi motherboards, restarted the computer, when I try to boot Sierra, I get this error "Error loading kernel cache" so I plug in my Sierra usb, clover installed on the hd starts, I chose boot Sierra from usb, that doesn't work, so what I do is go into uefi, put my usb stick first so it loads clover from the usb stick, I choose, boot OS X from Sierra (not usb) AND THAT WORKS?!?!?!?!
  25. Hello everybody, I just passed the full progress from a Windows 10 to a Dual Boot Hackintosh. After a few stupid mistakes it's working now absolutely fine. I have a Radeon 380X I set my iGPU as primary in BIOS. But I experience some issues with sleep mode. The thing is, in OSX it will just stop the video output, when pressing a key it will activate it again, but the PC itself just stays on as in normal mode (no affect). In Windows 10 there isn't the energy saver button in Start Menu. So there's no way of pressing it. By the way Shutdown and Restart work perfect. But, now it's getting interesting, when I boot my Windows through BIOS boot menu, this option is available (if I boot Windows through Clover it's not). I think it's (hopefully) not a big deal, as it's actually working in "pure Windows 10" which I think boots through legacy. I just read through all the "Sleep Issues" Thread and also used the search function but none of them fits to the issues I am experiencing. I was thinking about the "darkmode" bootflag or something with DSDT but as I'm absolutely new I'm really unsure what to do and don't want to destroy my actually running system. Thank you very much for your help! P.S. If any other informations are necessary I'm glad to provide them to you.
×