Jump to content
ErmaC

Clover problems report & features request

790 posts in this topic

Recommended Posts

Hi, I've had problems with clover (r5096) when I updated it from this clover https://github.com/Dids/clover-builder/releases. My machine was very slow and crashed 2 times today due to a kernel panic while only surfing the web. Had to revert back to my previous version of clover from that link and it's fine and back to normal.

Edited by Qola

Share this post


Link to post
Share on other sites
Advertisement
3 hours ago, Qola said:

Hi, I've had problems with clover (r5096) when I updated it from this clover https://github.com/Dids/clover-builder/releases. My machine was very slow and crashed 2 times today due to a kernel panic while only surfing the web. Had to revert back to my previous version of clover from that link and it's fine and back to normal.

 

Your Dids link redirect to r5093 release (not 5096). You can use official Clover repo: CloverBootLoader

Share this post


Link to post
Share on other sites
5 hours ago, Slice said:

AFAIK Catalina requires SSE4,2 instructions absent in this CPU.

My MacPro3,1 (not Hackintosh) runs Catalina without SSE4.2. Catalina AMD graphics drivers may require SSE4.2 (or a workaround). I use dosdude1's Catalina Patcher.

https://forums.macrumors.com/threads/macos-10-15-catalina-on-unsupported-macs.2183772/

Something similar may be needed for old Hackintosh PCs.

Share this post


Link to post
Share on other sites
7 hours ago, Slice said:

AFAIK Catalina requires SSE4,2 instructions absent in this CPU.

No, it does not, CPUs with SSE4.1 can run Catalina, but they are blocked by the telemetry plugin. If patched or removed the telemetry plugin, Catalina works fine on CPUs with SSE 4.1 . The dosdude1 app has a patch for that too. There are some Macs that have SSE 4.1 but not SSE 4.2 and there are some people on Macrumors with unsupported Macs who use Clover there. Catalina works fine on my machine for now and I do not think this has anything to do with the fact that I can not update or re-install Clover after one install. I have posted a link with some contents, you can check the files and see and how it works without SSE 4.2, and also about the error.

On GitHub, I see a new Clover build, 5077, but only sources, not installer. 

Edited by Vyzantion

Share this post


Link to post
Share on other sites
5 hours ago, Matgen84 said:

 

Your Dids link redirect to r5093 release (not 5096). You can use official Clover repo: CloverBootLoader

 

 

Yes I'm using that release(5093, Dids). 5096 https://github.com/CloverHackyColor/CloverBootloader/releases has been buggy for me it crashed my system and forced me to reinstall Catalina using(Dids 5093 release)

Share this post


Link to post
Share on other sites

Clover build 5097 fails to install over 5070, like the previous ones. Issue still present. No new information in the installer log. Perhaps shall I totally remove Clover then reinstall it? I do not know how to do that.

Edited by Vyzantion

Share this post


Link to post
Share on other sites
3 hours ago, Vyzantion said:

Clover build 5097 fails to install over 5070, like the previous ones. Issue still present. No new information in the installer log. Perhaps shall I totally remove Clover then reinstall it? I do not know how to do that.

 

First Method:

For reinstall a clean r5097:

  • Mount EFI partition and cut your previous folder on Desktop and unmount
  • Install the new release of Clover in EFI partition
  • Copy/Paste CLOVERX64.efi et BOOTX64.efi from the new Clover to the right place in EFI Folder on your desktop
  • Mount EFI partition, delete the new release of Clover 
  • Copy/Paste your EFI folder on Desktop to EFI Partition and unmount

2nd Method:

  • Download CLOVERX64.efi from Release on Official Repo
  • Keep it in any folder, rename a copy to BOOTX64.efi
  • Copy both files to the right place in EFI Folder

 

Sorry for my bad english

Edited by Matgen84

Share this post


Link to post
Share on other sites
7 hours ago, Matgen84 said:

 

First Method:

For reinstall a clean r5097:

  • Mount EFI partition and cut your previous folder on Desktop and unmount
  • Install the new release of Clover in EFI partition
  • Copy/Paste CLOVERX64.efi et BOOTX64.efi from the new Clover to the right place in EFI Folder on your desktop
  • Mount EFI partition, delete the new release of Clover 
  • Copy/Paste your EFI folder on Desktop to EFI Partition and unmount

2nd Method:

  • Download CLOVERX64.efi from Release on Official Repo
  • Keep it in any folder, rename a copy to BOOTX64.efi
  • Copy both files to the right place in EFI Folder

 

Sorry for my bad english

Sorry, what you said does not make sense. First method can not be understood and the second is much too simple. I can not install Clover more then once on the Macintosh HD.

Edited by Vyzantion

Share this post


Link to post
Share on other sites
9 hours ago, Vyzantion said:

Sorry, what you said does not make sense. First method can not be understood and the second is much too simple. I can not install Clover more then once on the Macintosh HD.

 

The two temporary methods works perfectly. If you do not understand, I'm not for nothing. Do as you see.

 

BOOTX64 and CLOVERX64 are the same file with two different name: one in EFI/BOOT and other in EFI/CLOVER. In Clover Repo in GitHub, you can find the PKG and  CLOVERX64 from Release Tag.

 

Good luck for solve your issue. I repeat: These are two temporary methods before solving it.

 

Post the install log and complete your signature: maybe others users can help you.

Edited by Matgen84
nd

Share this post


Link to post
Share on other sites
4 hours ago, Matgen84 said:

 

The two temporary methods works perfectly. If you do not understand, I'm not for nothing. Do as you see.

 

BOOTX64 and CLOVERX64 are the same file with two different name: one in EFI/BOOT and other in EFI/CLOVER. In Clover Repo in GitHub, you can find the PKG and  CLOVERX64 from Release Tag.

 

Good luck for solve your issue. I repeat: These are two temporary methods before solving it.

 

Post the install log and complete your signature: maybe others users can help you.

No, I did not meant that I do not understand how it works, I meant I do not understand what to do.

Share this post


Link to post
Share on other sites
3 hours ago, Vyzantion said:

No, I did not meant that I do not understand how it works, I meant I do not understand what to do.

 

What you have to do first is: post the installLog file, complete your signature  (config...). Which type of Clover Installation, you do: Legacy, ESP, etc.

Share this post


Link to post
Share on other sites
5 hours ago, Matgen84 said:

 

What you have to do first is: post the installLog file, complete your signature  (config...). Which type of Clover Installation, you do: Legacy, ESP, etc.

My specs are: 
Asus P5P41TED motherboard, a legacy (BIOS) motherboard

Intel Core2Duo E8500

2 gb ddr 3 ram

Nvidia GeForce 6500

I have posted the contents of EFI partitions of former installations into a downloadable link a few days ago, I think the link still works. Did you meant another install log then the one in there?

I use the default installation method for Clover legacy, I only add Install Clover in the ESP and (sometimes) Clover Preferences Panel. Yesterday I have discovered that Slice and his team has taken over the development of FakeSMC, FakeSMC plugins and HWMonitor. The pen drive is made using the last years FakeSMC, but since yesterday I have upgraded FakeSMC and its plugins and Realtek internet kext. Voodoo PS2 kext from Slice of 2019 does not work, so I use the 2018 version from RehabMan. I also Voodoo HDA Audio repackaged by Chris1111 from this board, in classical mode. And, of course, I install a patched version of Catalina using the dosdude1 app, mostly because of the an issue that the internal hard-drives are invisible to the Catalina installer. From the dosdude1 app I use the SIP disable patch, Intel IDE controller patch, USB Inject patch, Legacy check compatibility patch.

Any more information required?

I have upgraded Clover in a previous installation those days like this: Installed Clover on the pen driver, then replaced any file and folder from there into Macintosh HD and its EFI partition, checking its content in mirror like, even the files from the usr folder. It worked, more or less. I do know if I can do this too ofter, I was thinking to use the files in the Clover iso. 

 

Share this post


Link to post
Share on other sites
On 10/19/2019 at 2:59 PM, Vyzantion said:

Sorry, what you said does not make sense. First method can not be understood and the second is much too simple. I can not install Clover more then once on the Macintosh HD.

Well, it makes perfect sense - if you understand what is being asked, or perhaps is willing to try following simple steps.

 

First method preserves your current working Clover install, configuration, kernel extensions and drivers, while leaving the EFI/ESP partition clear and ready to receive a fresh new install of Clover. Afterwards, you dump your working configuration, kernel extensions and drivers back where they belong.

 

Second method is that simple since it only updates the required EFI file for your system to boot with the newer Clover version.

 

Both pretty much ends with the same result, but one gets an install via a package, whereas the other is a plain file copy.

Share this post


Link to post
Share on other sites

It seems that RC scripts are not working for me in Catalina? Specifically 70.disable_sleep_proxy_client.local.

 

I noticed my machine was waking up every 2 hrs.

 

Seems /System/Library/ read only in Catalina so if I tried manually to run the script all I get is errors.

 

had to do

 

"sudo mount -uw /" then run "killall Finder" and copy a modified version over so sleep issue now gone. 

 

 

Edited by mitch1
.

Share this post


Link to post
Share on other sites
53 minutes ago, Alex HQuest said:

Well, it makes perfect sense - if you understand what is being asked, or perhaps is willing to try following simple steps.

 

First method preserves your current working Clover install, configuration, kernel extensions and drivers, while leaving the EFI/ESP partition clear and ready to receive a fresh new install of Clover. Afterwards, you dump your working configuration, kernel extensions and drivers back where they belong.

 

Second method is that simple since it only updates the required EFI file for your system to boot with the newer Clover version.

 

Both pretty much ends with the same result, but one gets an install via a package, whereas the other is a plain file copy.

As I said, I can not install Clover the second time. I have tried similar solutions regarding mounting EFI, deleting Clover and installing it. I get the same error message, when I try to install. 

Share this post


Link to post
Share on other sites
It seems that RC scripts are not working for me in Catalina? Specifically 70.disable_sleep_proxy_client.local.
 
I noticed my machine was waking up every 2 hrs.
 
Seems /System/Library/ read only in Catalina so if I tried manually to run the script all I get is errors.
 
had to do
 
"sudo mount -uw /" then run "killall Finder" and copy a modified version over so sleep issue now gone. 
 
 
fixed it from clover app of vector sigma.

나의 SM-N960N 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites

Getting ACPI namespace lookup errors and boot failure with Clover r5100 9014888 (with changes to Clover's dsdt fixes)...

  70103181_ACPINamespaceLookupErrors.thumb.JPG.091860ff54273d03ac38d03e7f079de6.JPG

 

This is for my legacy desktop system (system no 2 in my signature).  No problem with Clover r5099 6852bd3.

 

Edit:  Fixed after commit r5101_ba2c47c :).

Edited by fusion71au
Fixed after r5101_ba2c47c

Share this post


Link to post
Share on other sites

@Slice
thanks for implementing the mask patching to clover .
i am trying to use the mask kernel patches from opencore to clover.
but it doesnt seem to work.

can you confirm that this is correct way of mask patching in clover ? 

       FIND: 833D0000 00000074 008B5DBC
    REPLACE: 00000000 00000100 00000000
   MASKFIND: FFFF0000 00FFFFFF 00FFFFFF
MASKREPLACE: 00000000 00000F00 00000000

 

Share this post


Link to post
Share on other sites
5 hours ago, XLNC said:

@Slice
thanks for implementing the mask patching to clover .
i am trying to use the mask kernel patches from opencore to clover.
but it doesnt seem to work.

can you confirm that this is correct way of mask patching in clover ? 


       FIND: 833D0000 00000074 008B5DBC
    REPLACE: 00000000 00000100 00000000
   MASKFIND: FFFF0000 00FFFFFF 00FFFFFF
MASKREPLACE: 00000000 00000F00 00000000

 

You want to get the result 833Dxxxx xx000174 xx8B5DBC where x is arbitrary?

This is correct way. Just sure about Capital letters.

 

On 12/7/2019 at 6:36 PM, XLNC said:

@Slice Hi !
I want make a clover feature request .
Can the XHCI Port limit patch feature of Opencore be added to clover ?

Thanks !

A bootloader should not be a collector for patches.

Share this post


Link to post
Share on other sites
On 12/25/2019 at 9:47 AM, Slice said:

You want to get the result 833Dxxxx xx000174 xx8B5DBC where x is arbitrary?

This is correct way. Just sure about Capital letters.

 

A bootloader should not be a collector for patches.

 

@Slice Hi!
I enabled debug in clover to see why patches are not applying and saw that clover is showing error on all mask kernel patches present in the kernel patches list.

eg:

Patch[0]: commpage_populate -remove rdmsr
==> Success : 1 replace done

Patch[1]: cpu_topology_sort -disable _x86_validate_topology
==> Error : 0 replace done

Patch[2]: cpuid_set_cache_info - cpuid 0x8000001D instead 0
==> Error: 0 replace done

and so on ......


Here are the kernel patches that are shown above debug:

 COMMENT : commpage_populate -remove rdmsr
    FIND : B9A00100 000F32
 REPLACE : 0F1F8000 000000

 COMMENT : cpu_topology_sort -disable _x86_validate_topology
    FIND : E80000FF FF
MASKFIND : FF0000FF FF
 REPLACE : 0F1F4400 00

 COMMENT : cpuid_set_cache_info - cpuid 0x8000001D instead 0
    FIND : 31C031DB 31C931D2 0FA24189 C6000000 00000000 74
MASKFIND : FFFFFFFF FFFFFFFF FFFFFFFF FF000000 0000FFFF FF
 REPLACE : B81D0000 8031DB31 C931D20F A24189C6 0F1F4000 EB


These same patches work fine in Opencore on catalina.
So not sure whats wrong, maybe any issue in the mask patching logic in clover ?


Thanks !

Edited by XLNC

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Jancey
      I used this command: diskutil info disk0s2 | grep -i "Partition UUID" | rev | cut -d' ' -f 1 | rev

      But I accidentally removed the wrong disk and now my main windows drive is not appearing in the bootloader. I can't figure out how to get it back. I tried resetting my windows drive, but I kept getting an error. I also reset my mac and reinstalled Catalina.
    • By gengstapo
      @Hervé
       
      Im having similar issue with my HS setup, dell latitute 3480, i5-7200U
      Once the hdmi plugged in, the laptop display went blank, only could see the external tv
      But, when i put my laptop to sleep & wake up again, both screen got display (hdmi still connected)
      Even the hdmi could be plugged off & in (after sleep), the laptop display is fine
       
      What could be the culprit?
      Dell’s MacBook Pro IORegistry.zip
      config.plist.zip
    • By TomZanna
      Hi, I'm trying to install Mac Os Catalina on a HP 550-132NL.
      The system has:
      i7-6700
      RAM 12 GB
      GT 730
      LAN Realtek RTL8161
      ALC3863
       
      It passes the verbose phase but after the Apple logo goes away, it gets stuck on a grey screen and I can only move the pointer.
      Can I try to boot with the iGPU?
       
      origin.zip
      CLOVER_dGPU_USB_3.zip
    • By kevin_1351
      tl;dr: VirtualSMC causes me a flood of log messages and correlated cpu spikes. FakeSMC doesn't.
       
      Hi, I have almost finalized my Huawei Matebook X Pro Opencore setup and everything is working very well besides wifi/bt ofc (which is about to change).
       
      However, I noticed how the cpu usage sometimes went up a little and when looking at the Console I could see a never-ending flood of:
      default 14:05:05.983292+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:05.982975+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:05.982996+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:06.985932+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:06.985949+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:06.986134+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:39.426574+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:39.426729+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:39.426585+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:41.431085+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:41.431097+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:41.431246+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:42.433068+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:42.433227+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:42.433078+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:43.434453+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:43.434465+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:43.434622+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:44.436155+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:44.436166+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0  
      As you can see, multiple of these per second. Another guy with the same computer is also having this issue and posted a dsdt change to fix it. This fix didn't solve anything though
      He tried to limit the Notify call by implementing a state change requirement before calling Notify.
       
      Here is the original acpi:
      Scope (_SB) { Device (LID) { Name (_HID, EisaId ("PNP0C0D") /* Lid Device */) // _HID: Hardware ID Method (_LID, 0, NotSerialized) // _LID: Lid Status { Local0 = One Local0 = ^^PCI0.LPCB.EC0.RPIN (0x05, 0x06) If ((Local0 == 0x55)) { Local0 = Zero } Else { Local0 = One } ^^PCI0.GFX0.CLID = Local0 Return (Local0) } } Device (PWRB) { Name (_HID, EisaId ("PNP0C0C") /* Power Button Device */) // _HID: Hardware ID Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0B) } } } Scope (_SB.PCI0.LPCB.EC0) { Method (_Q81, 0, NotSerialized) // _Qxx: EC Query, xx=0x00-0xFF { Local0 = ^^^^LID._LID () If ((Local0 == Zero)) { ADBG ("LID-OFF") SGOV (0x02030009, Zero) SGOV (0x02060000, Zero) } Else { ADBG ("LID-ON") SGOV (0x02030009, One) SGOV (0x02060000, One) Notify (ALSD, 0x80) // Status Change } Notify (LID, 0x80) // Status Change } } Which he changed to: 
      Scope (_SB) { Device (LID) { Name (_OLD, One) // assuming everything else.. the lid should start open? Name (_HID, EisaId ("PNP0C0D") /* Lid Device */) // _HID: Hardware ID Method (_LID, 0, NotSerialized) // _LID: Lid Status { Local0 = One Local0 = ^^PCI0.LPCB.EC0.RPIN (0x05, 0x06) If ((Local0 == 0x55)) { Local0 = Zero } Else { Local0 = One } Return (Local0) } } Device (PNLF) { Name (_HID, EisaId ("APP0002")) // _HID: Hardware ID Name (_CID, "backlight") // _CID: Compatible ID Name (_UID, 0x0A) // _UID: Unique ID Name (_STA, 0x0B) // _STA: Status } Device (PWRB) { Name (_HID, EisaId ("PNP0C0C") /* Power Button Device */) // _HID: Hardware ID Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0B) } } } Scope (_SB.PCI0.LPCB.EC0) { Method (_Q81, 0, NotSerialized) // _Qxx: EC Query, xx=0x00-0xFF { Local0 = ^^^^LID._LID () If ((Local0 == Zero)) { ADBG ("LID-OFF") SGOV (0x02030009, Zero) SGOV (0x02060000, Zero) } Else { ADBG ("LID-ON") SGOV (0x02030009, One) SGOV (0x02060000, One) Notify (ALSD, 0x80) // Status Change } If ((^^^^LID._OLD != Local0)) { Notify (LID, 0x80) // Status Change ^^^^LID._OLD = Local0 } } } Besides me not seeing any reason to declare _OLD in LID. The idea itself shouldn't be too bad right? Well, as I said, his fix didn't work.
       
      In fact, to prove that Method _Q81 doesn't have anything to do with the issue at all, I created a Clover/Opencore patch to change _Q81 to XQ81. This resulted in my lid not working at all of course, but the log flooding still persisted!
      So _Q81 doesn't have anything to do with the issue afaik.
       
      Now, further Google searches led me to a chinese post where he tied the issue to VirtualSMC. And indeed, by migrating to FakeSMC the issue is no more.
       
      Unfortunately, I'm very fond of VirtualSMC for various reasons. So I would very much like to keep it. If not I'd have to implement the old way of doing Battery monitoring etcetc. Which isn't very elegant and update proof as it requires DSDT patching.
       
      So, I do believe that the issue may very well be in the DSDT code, perhaps in the ambient light part. I'm not very skilled at this and just started studying the ACPI spec 3 days ago.
       
      Could someone please help me out? Thanks a lot in advance
       
       
      origin.zip
      OC.zip
    • By MaLd0n
      ---TUTORIAL---
      https://www.olarila.com/topic/5794-guide-install-macos-with-olarila-image-step-by-step-install-and-post-install-windows-or-mac/
       
      --Original Post--
      https://www.olarila.com/topic/6531-olarila-hackbeast-z390-designare-thunderbolt-full-dsdt-patches-clover-opencore/
       
      --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---
      https://olarila.com/files/Clover.Folder/EFI CLOVER Z390 DESIGNARE.zip
      *Use this folder with FULL DSDT PATCHED
       
      ---OPENCORE FOLDER---
      https://www.olarila.com/topic/6364-mojave-catalina-on-mobos-series-100200300-with-opencore-bootloader/
      *Use this folder with FULL DSDT PATCHED
       
       
      ---Extract one Full dump for DSDT edits, post files---
       
      RunMe.app
       
       
       
      ---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!
×