Jump to content
fantomas1

[pre-releases] macOS Sierra

769 posts in this topic

Recommended Posts

Advertisement

No Metal support for NVS 4200M  :(

attachicon.gifgfx.jpg

Nvidia has poor api support in windows/os x /linux so dont be to shocked 

Share this post


Link to post
Share on other sites

HD4600 works OOTB. Check your SMBIOS in clover or Defaults.plist in Ozmosis.

EDIT: I saw you have a mobile chipset. You could try ig platform edits in Clover. Ask @RehabMan

Share this post


Link to post
Share on other sites

Mobile HD4600 works same as before. You can therefore manually binmod all the necessary graphics related kexts & libraries or install Rehabman's FakePCIID kexts and inject desktop dev id 0412 through DSDT or Clover.

 

My personal experience with HD4600 on Sierra DP1 is that some displayed items can be a little buggy, for instance the text for filenames when browsing folders. It's not really an issue but it is noticeable to me.

Share this post


Link to post
Share on other sites

manually binmod all the necessary graphics related kexts & libraries

Note that those "binmods" are incomplete and unstable. FakePCIID is the way to go, it is brute force and complete.

Share this post


Link to post
Share on other sites

@notnice, @TheRacerMaster, @mnfesq,

 

Saw your messages with regards to the Broadcom BCM9432Z no longer working in macOS Sierra DP1.

I have made available a patch in the post-installation forum:

 

http://www.insanelymac.com/forum/topic/312759-fix-macos-sierra-dp1-bcm94532z-wifi/

 

Thanks a million. Works great for me.  :thumbsup_anim:

 

Also, how's X99 power management? I'm booted without XMCP as it causes a panic, but I think I have NullCPUPM injected and am getting stepping and a Geekbench score like none other... 21K easily, whereas El Cap struggled to ever give me 19K... http://browser.primatelabs.com/geekbench3/7126535 

Share this post


Link to post
Share on other sites

A Windows disk cleanup clone ! ?

post-448675-0-70473100-1467109559_thumb.jpg

 

 

Bug or feature ?

 

El Capitan                                                           Sierra

 

post-448675-0-92425500-1467125688_thumb.jpgpost-448675-0-51568100-1467125697_thumb.jpg

Share this post


Link to post
Share on other sites

Bug or feature ?

 

 

I would say feature, since they are into "minimalistic" design..

 

Anyways, is there a new Sierra DP out yet?? they usually put it out around this time..

Share this post


Link to post
Share on other sites

There are many things to be corrected, let's not wait
both of  DP1, even the patches made now
may suffer changes in the final version or even
in the next DP.

Share this post


Link to post
Share on other sites

I am currently running El Capitan and everything runs perfectly including handoff, imessage, continuity, icloud etc.

 

I use a MacPro 3,1 SMBIOS profile.

 

When I eventually update to Sierra on my hackintosh, will I have to change my SMBIOS to a different machine or will the update process allow for the MacPro 3,1 SMBIOS profile to install?  Note that I have a real Mac Pro 3,1 as well and have managed to get Sierra installed on that with little hassle.

Share this post


Link to post
Share on other sites

 

Thanks for your response but I'm not sure it really answers my question. I know you can run Sierra on a Mac Pro 3,1 - I've done it and written a guide as well on how to do it.

 

My question is more around are we, the hackintosh community who have largely been using the SMBIOS Mac Pro 3,1 profile going to have to change it going forward for Sierra or can we continue to happily run our Mac Pro 3,1 profiles?  As I say, I know initially we can get the initial Dev release running - but that doesn't answer the longer term. I wonder if people have a view on that?

Share this post


Link to post
Share on other sites

Thanks for your response but I'm not sure it really answers my question. I know you can run Sierra on a Mac Pro 3,1 - I've done it and written a guide as well on how to do it.

 

My question is more around are we, the hackintosh community who have largely been using the SMBIOS Mac Pro 3,1 profile going to have to change it going forward for Sierra or can we continue to happily run our Mac Pro 3,1 profiles?  As I say, I know initially we can get the initial Dev release running - but that doesn't answer the longer term. I wonder if people have a view on that?

MacPro3,1 never really made sense to begin with, especially for proper PM & hardware support (AirPlay mirroring/QuickSync). You want to use something that matches your hardware. For most desktops (with LGA115x - SNB/IVB/HSW/BDW/SKL) desktops, an iMac SMBIOS usually makes sense.

Share this post


Link to post
Share on other sites

MacPro3,1 never really made sense to begin with, especially for proper PM & hardware support (AirPlay mirroring/QuickSync). You want to use something that matches your hardware. For most desktops (with LGA115x - SNB/IVB/HSW/BDW/SKL) desktops, an iMac SMBIOS usually makes sense.

 

Right. That makes sense.

 

Well, given I'm up and running using a Mac Pro 3,1 profile on El Capitan and everything works - and given that I used real ROM / MLB data from a Mac Pro 3,1 (I used a unique serial number and other data though - just used valid ROM / MLB data for iMessage) am I best to stick with that?  I don't have a ROM / MLB to use from an iMac, and nor do I feel inclined in changing it all and going through the trouble of getting it all working again if I don't have to.

Share this post


Link to post
Share on other sites

I have everything running very smoothly with MacOS Sierra DP1 with the minor exception of keyboard assignment (which will likely get worked out eventually.  However, there is one thing that concerns me:  I get a KP with the AMDRadeonX4000.kext.  When I delete the kext from S/L/E, it boots just fine.  I think that the KP occurs after the point I would get to delete it if I booted with -S so it's not critical even when I install DP2 (assuming the same problem persists.)  The thing is, it makes no sense that the X4000 kext would cause a KP for me since I only have the Intel HD4000 GPU activated in the BIOS.  Is there a boot arg that might allow me to keep the X4000 kext in S/L/E without getting a KP?  Does anyone else (possibly on an HP laptop) have a similar problem?

Share this post


Link to post
Share on other sites

Thanks for your response but I'm not sure it really answers my question. I know you can run Sierra on a Mac Pro 3,1 - I've done it and written a guide as well on how to do it.

 

My question is more around are we, the hackintosh community who have largely been using the SMBIOS Mac Pro 3,1 profile going to have to change it going forward for Sierra or can we continue to happily run our Mac Pro 3,1 profiles?  As I say, I know initially we can get the initial Dev release running - but that doesn't answer the longer term. I wonder if people have a view on that?

List of Macs Compatible with MacOS Sierra 10.12

According to Apple, the official compatible hardware list of Macs capable of running Mac OS Sierra 10.12 is as follows:

  • MacBook Pro (2010 and later)
  • MacBook Air (2010 and later)
  • Mac Mini (2010 and later)
  • Mac Pro (2010 and later)
  • MacBook (Late 2009 and later)
  • iMac (Late 2009 and later)

This list of supported Macs is offered directly from Apple, shown during the MacOS Sierra debut presentation at WWDC 2016 conference.

 

is not supported, and as said by TheRacemaster you need to use a SMBIOS that matches your hardware.

but maybe you have an old computer(core 2 duo) and want to install it a you can use the old trick of change: /System/Library/CoreServices/PlatformSupprt.plist 

adding to MacPro 3,1.

Share this post


Link to post
Share on other sites

List of Macs Compatible with MacOS Sierra 10.12

According to Apple, the official compatible hardware list of Macs capable of running Mac OS Sierra 10.12 is as follows:

  • MacBook Pro (2010 and later)
  • MacBook Air (2010 and later)
  • Mac Mini (2010 and later)
  • Mac Pro (2010 and later)
  • MacBook (Late 2009 and later)
  • iMac (Late 2009 and later)

This list of supported Macs is offered directly from Apple, shown during the MacOS Sierra debut presentation at WWDC 2016 conference.

 

is not supported, and as said by TheRacemaster you need to use a SMBIOS that matches your hardware.

but maybe you have an old computer(core 2 duo) and want to install it ai you can use the old trick of change: /System/Library/CoreServices/PlatformSupprt.plist 

adding to MacPro 3,1.

 

So does that mean I need a valid ROM / MLB from an iMac from one of those listed above to get iMessage working?  I'm currently using a Mac Pro 3,1 profile with El Capitan and its working great with my ASUS Z97-PRO WIFI AC motherboard and i7 4Ghz CPU. In fact, I've had to do very little customisation to get it all working. That includes USB 3, audio, ethernet, wifi, bluetooth. 

 

I didn't have to buy a separate airport wifi card to get handoff, airdrop, and continuity working - it uses the native motherboard WIFI to do it.

Share this post


Link to post
Share on other sites

So does that mean I need a valid ROM / MLB from an iMac from one of those listed above to get iMessage working?  I'm currently using a Mac Pro 3,1 profile with El Capitan and its working great with my ASUS Z97-PRO WIFI AC motherboard and i7 4Ghz CPU. In fact, I've had to do very little customisation to get it all working. That includes USB 3, audio, ethernet, wifi, bluetooth. 

 

I didn't have to buy a separate airport wifi card to get handoff, airdrop, and continuity working - it uses the native motherboard WIFI to do it.

 

No, i use a MacPro4,1 ROM/MLB without any issues i've never called Apple, right now MacPro6,1 before iMac10,1

Share this post


Link to post
Share on other sites

No, i use a MacPro4,1 ROM/MLB without any issues i've never called Apple, right now MacPro6,1 before iMac10,1

 

 

Did you just generate a fake ROM/MLB?

Share this post


Link to post
Share on other sites

 

No, like I said MLB/ROM from a genuine MacPro4,1

So now I'm confused. You said you run now a Mac Pro 6,1 profile yet you are using ROM/MLB from a Mac Pro 4,1?

 

I thought the profile and the ROM/MLB had to match?

Share this post


Link to post
Share on other sites

So now I'm confused. You said you run now a Mac Pro 6,1 profile yet you are using ROM/MLB from a Mac Pro 4,1?

 

I thought the profile and the ROM/MLB had to match?

 

In my case they don't match and it works, valid MLB/ROM from MacPro4,1 @MacPro6,1 profile and before the same MLB/ROM on other hardware with iMac10,1 profile. So the same MLB/ROM on different hardware and different SMBIOS

Share this post


Link to post
Share on other sites

In my case they don't match and it works, valid MLB/ROM from MacPro4,1 @MacPro6,1 profile and before the same MLB/ROM on other hardware with iMac10,1 profile. So the same MLB/ROM on different hardware and different SMBIOS

Ahh, OK, got it.

 

I guess I will change to the latest iMac smbios then. I have a i7 4ghz CPU and Asus z97 pro wifi ac motherboard.

 

BTW, I notice that documentation from 2014 says not to have the original machine logged into FaceTime / iMessage as the hackintosh sharing the MLB / ROM. However, I do exactly that and have no issues.

 

Thanks for your help too - I appreciate it.

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By fusion71au
      This is a brief guide on how to create a vanilla El Capitan (also same process for Sierra) OS X Installer USB with an updated prelinked kernel containing FakeSMC.

      It is tailored for those users who want to understand the “nuts and bolts” of how to create an installer and also to help brush up on their terminal skills (rather than have one made for them with the numerous automated “tools” available or even Apple’s createinstallmedia) :
       
       
      Specifically, it is also a “Proof of Concept” which shows that installation is possible without even having to rely on boot loader kext injection.

      Prerequisites
      Existing Yosemite installation (or Mavericks - see post#4 for steps 7,8) “Install OS X El Capitan.app" downloaded to the Applications folder Pacifist FakeSMC.kext - Slice or Kozlek branch Bootloader - Clover or Chameleon 8GB or larger USB drive (16GB recommended), formatted HFS+ (MBR or GUID) named “Installer”  
      Procedure
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Open OS X terminal and type the following lines, followed by <Enter> after each line.
          The image restore and file copying may take a while to complete, and at the end of the process, the Installer volume is renamed to “OS X Base System"....
       
      sudo -s hdiutil attach /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/SharedSupport/InstallESD.dmg asr restore -source /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg  -target /Volumes/Installer -erase -format HFS+ -noprompt -noverify rm /Volumes/OS\ X\ Base\ System/System/Installation/Packages cp -av /Volumes/OS\ X\ Install\ ESD/Packages /Volumes/OS\ X\ Base\ System/System/Installation cp -av /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg /Volumes/OS\ X\ Install\ ESD/BaseSystem.chunklist /Volumes/OS\ X\ Base\ System diskutil unmount /Volumes/OS\ X\ Install\ ESD exit 3.  Right click on the “OS X Base System” Volume and click “Get Info”
       

      4.  Click on the lock icon and untick “Ignore ownership on this volume”
       

      5.  Extract/Copy the El Capitan Kernels folder into /System/Library/ of the USB with Pacifist.  NB It is found in the "Essentials.pkg" in /System/Installation/Packages
       

      6.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel —> OG.prelinkedkernel
       

      7.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of the installer USB using Finder.
       

      8.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel…..
       
      sudo -s chmod -R 755 /Volumes/OS\ X\ Base\ System/Library/Extensions chown -R 0:0 /Volumes/OS\ X\ Base\ System/Library/Extensions touch /Volumes/OS\ X\ Base\ System/System/Library/Extensions kextcache -u /Volumes/OS\ X\ Base\ System exit Any errors should be noted but the output below is normal e.g.


      9. Install your Bootloader targeting the OS X Base System volume
       
       
       
       
      10.  Boot your system with the USB without injected kexts into the OS X Installer GUI....
       
       
       
       
       
      Post Install
      The original prelinked kernel in a fresh install of El Capitan will also lack FakeSMC ie it will only be linked to Apple signed kexts.  In order to boot into El Capitan the first time around without boot loader kext injection, the PLK needs to be rebuilt for the El Capitan volume like we did for the installer:
       
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel for the El Capitan volume —> OG.prelinkedkernel
      3.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of El Capitan using Finder
      4.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel.  In this example, the El Capitan volume is named "El_Capitan" - change if you have named it something else...
      sudo -s chmod -R 755 /Volumes/El_Capitan/Library/Extensions chown -R 0:0 /Volumes/El_Capitan/Library/Extensions touch /Volumes/El_Capitan/System/Library/Extensions kextcache -u /Volumes/El_Capitan exit 5. Install your Bootloader targeting the El Capitan volume.  This step is only necessary if you are installing El Capitan on a new drive without existing boot loader (not required if installing on a disk with existing boot loader beside Yosemite).
      6. Reboot your system without injected kexts into El Capitan!
       
       
      Other links
      The All-In-One Guide to Vanilla OS X for beginners
       
      Updates for Sierra and High Sierra   Custom Prelinkedkernel Generator Tool I have made a custom prelinkedkernel generator "PLK.tool" for Sierra + El Capitan.  Instructions:   1.  Download and extract the attached BaseSystem_PLK.tool.zip into your ~/Downloads folder.   2.  Copy any extra kexts necessary for booting your hack to ~/Downloads/BaseSystem/ExtraKexts (e.g. FakeSMC, VoodooPS2Controller), making sure SIP is disabled. 3.  Copy BaseSystem.dmg to ~/Downloads/BaseSystem  4.  Open terminal and run the following commands... cd ~/Downloads/BaseSystem chmod +x PLK.tool ./PLK.tool ---> supply your admin password ---> will place your new custom prelinkedkernel on the desktop.       macOS High Sierra bypass Firmware and MBR checks in post#13.
      BaseSystem_PLK.tool_ElCap.zip
      BaseSystem_PLK.tool_Sierra.zip
      BaseSystem_PLK.tool_Mojave.zip (need to run in Mojave to avoid dependency errors)
       
      BaseSystem_PLK.tool_Catalina.zip
    • By shinho73
      Hello everyone. I managed to install AMD Sierra V5(10.12.6) on my old AMD A8 7600 PC(Mother Board-A58M-E, GPU- Palit Geforce GT730 DDR3). Everything is working except the GPU. The GT730 DDR3 GF108 is natively supported on Sierra, but for some reason, it is not working. On Clover Config, "Inject Nvidia" is selected, no Nvidia Web, and nv_disable=1. On "About This Mac" it just says " NVIDIA Chip Model 3 MB".
      I have attached config.plist. Can someone look at it please? Any help will be greatly appreciated. Thank you. 





      config.plist
    • By fusion71au
      Clover r5050 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.15 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r5050 for VMware.zip". Mount Clover-v2.5k-5050-X64.iso by double clicking on it.
      2. Mount your VM's EFI System Partition eg in terminal
      sudo diskutil mount disk0s1   3. Copy EFI folder from step 1 into the EFI partition
      4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file
      5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu.
       
      Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
    • By Slice
      I successfully installed macOS 10.11.6 and Windows 7 Pro SP1 in UEFI mode on the laptop.
      I know, there are detailed guides here and on osxlatitude.com but I was not agree with them and carefully check and test every step to tune my Mac.
       
      Hardware
      Intel® Core� i5-3320M CPU @ 2.60GHz, speedstep works with Clover default settings
      Chipset Intel 7 series, no patches needed
      Video: IntelHD4000 or NVS5200M switchable in BIOS, work in both cases
      LAN; Intel 82579LM, works with IntelMausiEthernet.kext v2.2.1
      Audio: IDT 92HD93BXX, works with VoodooHDA 2.9.0.
      SDHC reader O2Micro; works with native AppleSDHC.kext with Clover Arbitrary properties.
      USB3.0 works natively if not disabled in DSDT
      PS2 keyboard and touchpad works with VoodooPS2.
      WiFi: Dell Intel WiFi was replaced by Dell DW1520, Broadcom BCM943224HMS. DeviceID=4353
      LCD Screen 1366x768
      BIOS A12. Initially was A02. Then I flashed A23 and found it is quite bad. The screen is full of artefacts. Flash A12 and all is OK. Not tested other versions.
      For some reason BIOS can switched from Intel to Nvidia by itself so I have to do my solution working independent on this state.
       
      WiFi
      It is not working OOB although it has DeviceID known to Apple. The reason is WhiteList in the driver.
      I set MacModel as MacBookPro10,1 while the WiFi will work on MacBookAir. I make a patch in Clover.
      As well a patch for channels.
      I deleted a kext Brcm4331 because it has the same DeviceID. Let kext Brcm4360 to work alone.
       
      VideoCards
      In Bios we can set Optimus = Enable/Disable
      If Enable then we have two videocards Intel first and Nvidia second. In this case additional SSDT-3.aml will switch off Nvidia.
      If Disable then we have only Nvidia card. It will work if Board-ID taken from iMac13,2.
      But here there is contradiction with WiFi with required Board-ID from MacBookAir.
      So I take MacModel as MacBookPro10,1 which is most close by CPU IvyBridge.
      Set BoardID like iMac13,2 to make Nvidia working.
      Patch BoardID in Brcm4360 to make WiFi working.
      Now I have
      Inject->
      ->Intel=YES
      ->Nvidia=YES
      and SSDT-3.aml in ACPI\patched folder. This SSDT will switch off Nvidia if Intel card ON.
      For Intel graphics there is a patch against 8 apples at start.
      This Nvidia 5200 is Fermi and works in ElCapitan.
       
      Brightness
      No special kexts.
      The brightness controlled by keys F1,F2 and slider in Control Panel in both case Intel or Nvidia. Details here  #72 
       
      DSDT and SSDT
      This is very long story and finally I have working sleep in both cases Intel or Nvidia.
       
      Sensors
      I use my HWSensors3 with FakeSMC 3.5.2.
      I got monitoring:
      CPU temperature
      GPU temperature
      GPU main frequency
      GPU shader frequency
      Battery state % full, time to charged or time to empty.
      Battery voltage dinamically.
      Battery amperage dynamically. I can see it changes on heavy games.
      HDD temperature.

       
      Audio
      I like VoodooHDA and have no problems with it.
      The sound is clear, loud, and switchable between internal speaker and headphone.
      Mic is working.
       
      Bluetooth
      Just tested with BTFirmwareUpdate.kext and it works in 10.11.6. I not needed it so switched off by wireless switch at right side.
      For 10.13.6 there is other kext BRCMInjector.
       
      Keyboard, Touchpad and Touchstick
      Post #14
      I made my fork of the VoodooPS2 driver, take here sources and release version
      https://github.com/SergeySlice/VoodooPS2-for-ALPS
       
      My config, ACPI files and kexts are in attachment.
      05.12.2017
      EFI.7z
       
      EDITED:
      Better DSDT in the post #6.
      Sleep working even when AC inserted.
       
      EDITED 06.12.2018
      Now I have HighSierra and this is my EFI folder. Note, HighSierra is possible only with Intel graphics (Optimus is enabled in BIOS)
       

       
       
      Welcome to discussion!
      EFI-E6430.7z
      BRCMInjector.kext.zip
    • By MaLd0n
      ---TUTORIAL---

      https://olarila.com/forum/viewtopic.php?f=50&t=8685
       
      --Original Post--
       
      https://olarila.com/forum/viewtopic.php?f=97&t=11237
       
      --Bios/UEFI Settings--
       
      *Update bios/uefi to F7+*
      1- Go to M.I.T./Advanced Frequency Settings tab
       
      Extreme Memory Profile (X.M.P.) - Profile 1
       
      2- Go to BIOS tab
       
      CSM Support - Disabled
       
      3- Go to Peripherals/Thunderbolt(TM) Configuration tab
       
      Security Level - No Security
      Thunderbolt USB Support - Enabled
      GPIO3 Force Pwr - Enabled
       
      4- Go to Chipset tab
       
      Internal Graphics - Enable
       
      ---CLOVER FOLDER---
      *Use this folder with FULL DSDT PATCHED
      EFI CLOVER Z390 DESIGNARE.zip
       
      ---OPENCORE FOLDER---
      *Use this folder with FULL DSDT PATCHED
      EFI OPENCORE Z390 DESIGNARE.zip
       
      ---DSDT patch requests is here---
       
      https://olarila.com/forum/viewtopic.php?f=19&t=1131
       
      ---HARDWARE---
       
      --MOBO

      GIGABYTE Z390 DESIGNARE
      -Link
      https://www.amazon.com/Z390-DESIGNARE-Gigabyte-Thunderbolt-Motherboard/dp/B07K8RJZRG/ref=sr_1_1?keywords=Z390+DESIGNARE&qid=1565492390&s=electronics&sr=1-1

      --PROCESSOR

      Intel Core i9-9900K
      -Link
      https://www.amazon.com/Intel-i9-9900K-Desktop-Processor-Unlocked/dp/B005404P9I/ref=sr_1_1_sspa?keywords=Intel+Core+i9-9900K&qid=1553358099&s=gateway&sr=8-1-spons&psc=1

      --COOLER

      CORSAIR H100i RGB PLATINUM AIO Liquid CPU Cooler
      -Link
      https://www.amazon.com/CORSAIR-H100i-PLATINUM-Liquid-Cooler/dp/B07JWB5BSN/ref=sr_1_4?keywords=WATER+COOLER+CPU&qid=1565492509&s=gateway&sr=8-4

      --MEMORY

      Corsair CMW32GX4M2C3200C16 Vengeance RGB PRO 32GB (2x16GB) DDR4 3200 (PC4-25600)
      -Link
      https://www.amazon.com/Corsair-CMW32GX4M2C3200C16-Vengeance-PC4-25600-Desktop/dp/B07GTG2T7L/ref=sr_1_15?keywords=memory+ddr4+32&qid=1553358238&s=gateway&sr=8-15

      --GPU

      MSI RX Vega 64 AIR Boost 8G OC
      -Link
      https://www.amazon.com/MSI-RX-64-AIR-8G/dp/B07DH7S1X1/ref=sr_1_2?keywords=vega+64+gigabyte&qid=1565492819&s=electronics&sr=1-2

      --SSD

      Samsung 970 EVO 1TB SSD (MZ-V7E1T0BW) NVMe M.2 V-NAND
      -Link
      https://www.amazon.com/Samsung-970-EVO-1TB-MZ-V7E1T0BW/dp/B07BN217QG/ref=sr_1_1?keywords=s+samsung+970+evo+1tb&qid=1565493002&s=electronics&sr=1-1

      --POWER SUPPLY

      EVGA Supernova 1000 P2 80+ Platinum, 1000W ECO Mode Fully Modular 
      -Link
      https://www.amazon.com/EVGA-Supernova-Platinum-Crossfire-220-P2-1000-XR/dp/B00EKJQM5E/ref=sr_1_3?keywords=power+supply+1000w&qid=1565493196&s=gateway&sr=8-3

      --WIRELESS

      TP-Link Archer T9E
      -Link
      https://www.amazon.com/TP-Link-Archer-T9E-Beamforming-Technology/dp/B00TQEX7AQ/ref=sr_1_1?keywords=TP-Link+Archer+T9E&qid=1553358397&s=gateway&sr=8-1

      --CASE

      Thermaltake Core P5 Tempered Glass Black Edition ATX Open Frame Panoramic Viewing
      -Link
      https://www.amazon.com/Thermaltake-Tempered-Panoramic-Certified-CA-1E7-00M1WN-03/dp/B01N4IGVSC/ref=sr_1_2?keywords=Thermaltake+Core+P5&qid=1565493567&s=gateway&sr=8-2

      --DSDT Patches--
      -FIX ACPI ERRORS -FIX OEM SSDTs to AVOID ERRORS AND WARNINGS -REMOVE UNUSED SCOPES / DEVICES -HIGH PRECISION EVENT TIMER -SATA -DMAC -REMOVE PROBLEMATIC AND UNUSED DEVICES -FIX K.P in REBOOT -SLPB -DARWIN / WINDOWS 2015 -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -REAL TIME CLOCK -ARTC -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -LAN -FWHD -USBX -PMCR -PPMC -XSPI -CNVW -GMM -IMEI -EC -PNLF -ARPT -GFX0 -NVME -DTGP -ACQUIRE MUT0 0XFFFF -MUTEX MUT0 0x00 -EXTERNAL REFERENCES -UNKNOWNOBJ -HDMI / HDAU -FULL RENAMED DEVICES ---SCREENSHOTs---




















      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
      Thanks to KGP for SSDT Thunderbolt
      Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad, Sampath007, onemanosx, erroruser, Jenny David, Olarila Facebook Community, Hackintosh Facebook Community and many others!
      We're all here to have fun and learn from each other!
×