Jump to content
ErmaC

Clover General discussion

21,117 posts in this topic

Recommended Posts

Advertisement
On 12/21/2019 at 10:22 AM, Florin9doi said:


43:194  0:000  Preparing kexts injection for arch=i386 from EFI\CLOVER\OEM\VMware7,1\kexts\10
43:194  0:000  Preparing kexts injection for arch=i386 from EFI\CLOVER\OEM\VMware7,1\kexts\10_normal
43:194  0:000  Preparing kexts injection for arch=i386 from EFI\CLOVER\OEM\VMware7,1\kexts\10.5
43:194  0:000  Preparing kexts injection for arch=i386 from EFI\CLOVER\OEM\VMware7,1\kexts\10.5_normal
43:194  0:000  Preparing kexts injection for arch=i386 from EFI\CLOVER\OEM\VMware7,1\kexts\10.5.8.0
43:194  0:000  Preparing kexts injection for arch=i386 from EFI\CLOVER\OEM\VMware7,1\kexts\10.5.8.0_normal

10.5.8.0 seems wrong 

Sure it is. I'll have a look soon.

Share this post


Link to post
Share on other sites
2 hours ago, luky35 said:

I like the name of this theme in the picture, or where I find it

 

Thanks,

 

It's a @Badruzeus  theme called: Mojave. You can find it via CloverThemeManager (I think) or Badruzeus repo on GitHub ('MyCloverThemes'). I only customize the logo :)

Share this post


Link to post
Share on other sites

Did we still need "FSInject.efi" in CLOVER?? When i install Clover, i read the description of FSInject.efi and it's written "Provide injection of kernel extensions from Clover folder.". Honestly, i can boot without this driver,, So when i must use it???

 

image.png.d3e8b3a3bc9b43c5bab13f41c09ffab6.png

 

I just use this driver right now


image.png.c454f587e8a46badb08f1ab7b961365a.png

Share this post


Link to post
Share on other sites
11 hours ago, Andres ZeroCross said:

Did we still need "FSInject.efi" in CLOVER?? When i install Clover, i read the description of FSInject.efi and it's written "Provide injection of kernel extensions from Clover folder.". Honestly, i can boot without this driver,, So when i must use it???

 

 

 

I just use this driver right now


 

The description is not correct.

Actually FSInject allows you to ForceLoad kexts form /S/L/E

Share this post


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

The description is not correct.

Actually FSInject allows you to ForceLoad kexts form /S/L/E

What does ForceLoad mean? Does it load them like the kexts in the Clover folder? Does it force load all the kexts in /S/L/E? None from /L/E?

Share this post


Link to post
Share on other sites
2 hours ago, joevt said:

What does ForceLoad mean? Does it load them like the kexts in the Clover folder? Does it force load all the kexts in /S/L/E? None from /L/E?

Original comment from Dmazar is here Post#30 Using extra kexts and skipping kernelcache

But OS changed and rules changed.

We can write

	<key>KernelAndKextPatches</key>
	<dict>
		<key>ForceKextsToLoad</key>
		<array>
			<string>\System\Library\Extensions\AMDRadeonX4000.kext</string>
		</array>

to patch the kext on the fly. Same for /L/E. Volume assumed same as boot.efi used to load cache.

It is needed because some system kexts are not present in kernelcache because they are not loaded by default.

Share this post


Link to post
Share on other sites

I didn't see any new kext structure folder  on Clover_v2.5k_r5101

second issue I have 

my VoodoI2C touchpad don't work during installation but with Opencore work my touchpad during installation

my touch was working earlier version of clover boot loader I think this is kext injection bug

when I install VoodoI2C.kext in system L/E then work fine

anyone can tell me about that

Share this post


Link to post
Share on other sites

The installer doesn’t create these folders. Create some if you need.

VoodooI2c is one of the reason I’ve created these folder possibility. So I confirm the voodooI2c not working in installer is NOT because of these new folder name.

just create a 10_install folder and put the complete version of voodoops2controller in it and you’ll be able to install.

Share this post


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

The installer doesn’t create these folders. Create some if you need.

VoodooI2c is one of the reason I’ve created these folder possibility. So I confirm the voodooI2c not working in installer is NOT because of these new folder name.

just create a 10_install folder and put the complete version of voodoops2controller in it and you’ll be able to install.

I didn't understand please tell me clearly 

Where can i create 10_install folder

Share this post


Link to post
Share on other sites
On 12/20/2019 at 11:08 AM, n.d.k said:

You don't have to rename anything.  Ok to make it clear for someone not understand it well.

 

- Create a file name VolumeLabel.txt on Desktop

- Open it with text editor and write #EFI or any name you want with # in front on the first line, then save it.

- Mount the EFI partition (the one you install the clover on) and open up Finder click EFI on the left pane.

- Drag the VolumeLabel.txt file to it (the root, not into the EFI folder)

- Rename VolumeLabel.txt to .VolumeLabel.txt and it will disappear from the Finder since it's a hidden file name.

Done!

 In Finder, you can use Shift + Command + . to show/hide the hidden files. 

It still says Clover Boot from EFI when I do the following:

2013505507_ScreenShot2019-12-26at1_08_55PM.jpg.a14382691f9c434eb7e47b7b65127615.jpg

Share this post


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

I didn't understand please tell me clearly 

Where can i create 10_install folder

Снимок экрана 2019-12-26 в 21.31.12.png

22 minutes ago, pkdesign said:

It still says Clover Boot from EFI when I do the following:

2013505507_ScreenShot2019-12-26at1_08_55PM.jpg.a14382691f9c434eb7e47b7b65127615.jpg

Is it Clover version from latest github sources? Not from release.

Share this post


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

Снимок экрана 2019-12-26 в 21.31.12.png

Is it Clover version from latest github sources? Not from release.

VoodoI2C.kext is not working during installation but with Opencore work 

VoodooI2C was working fine during installation earlier version of clover

i think that something has been changed in clover bootloader

Anyone have idea

Share this post


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

VoodoI2C.kext is not working during installation but with Opencore work 

VoodooI2C was working fine during installation earlier version of clover

i think that something has been changed in clover bootloader

Anyone have idea

You should modify VoodooI2C.kext/Contents/Info.plist to have this line

Снимок экрана 2019-12-27 в 23.28.36.png

Share this post


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

You should modify VoodooI2C.kext/Contents/Info.plist to have this line

Снимок экрана 2019-12-27 в 23.28.36.png

on latest VoodoI2C.kext v2.3  already have modified with OSBundleRequired Root

I tried already didn't get work during installation I think this is clover issue 

on OpenCore bootloader is working fine

 

Share this post


Link to post
Share on other sites
On 11/11/2019 at 7:53 PM, Pene said:

 

Hi Slice,

 

Thank you for the response. But I think I didn't explain myself well.

0Bh is the location of of the "Attributes", not it's content.

The content is newSmbiosTable.Type17->Attributes = 1 in case of Single-Rank DIMMs and newSmbiosTable.Type17->Attributes = 2 in case of Dual-Rank DIMMs.

But this information is *already present* in SMBIOS, without us doing anything special in Clover.

 

He sent me two dmidecodes from a booted Mac, for each case, with the different DIMMs installed. Look:

 

This is the non-working case with the Single-Rank DIMMS: (notice the RANK: 1, it is present in smbios and read from the Attributes address at 0Bh):


Handle 0x1101, DMI type 17, 40 bytes
Memory Device
	Array Handle: 0x1000
	Error Information Handle: No Error
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 8192 MB
	Form Factor: DIMM
	Set: 1
	Locator: DIMM0
	Bank Locator: BANK 1
	Type: DDR4
	Type Detail: Synchronous Unbuffered (Unregistered)
	Speed: 2998 MT/s
	Manufacturer: Corsair
	Serial Number: 0000000000000000
	Asset Tag: Not Specified
	Part Number: CMW16GX4M2C3000C15
	Rank: 1
	Configured Clock Speed: 2133 MT/s
	Minimum Voltage: 1.2 V
	Maximum Voltage: 1.2 V
	Configured Voltage: 1.2 V

And this is the non-working case with the Dual-Rank DIMMS: (notice the RANK: 2, it is present in smbios and read from the Attributes address at 0Bh):


Handle 0x1100, DMI type 17, 40 bytes
Memory Device
	Array Handle: 0x1000
	Error Information Handle: No Error
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 8192 MB
	Form Factor: DIMM
	Set: 1
	Locator: DIMM0
	Bank Locator: BANK 0
	Type: DDR4
	Type Detail: Synchronous Unbuffered (Unregistered)
	Speed: 3200 MT/s
	Manufacturer: G Skill Intl
	Serial Number: 0000000000000000
	Asset Tag: Not Specified
	Part Number: F4-3200C16-8GTZB
	Rank: 2
	Configured Clock Speed: 2133 MT/s
	Minimum Voltage: 1.2 V
	Maximum Voltage: 1.2 V
	Configured Voltage: 1.2 V

This is the only real difference between the chips.

He has two pairs of chips that it is working OK for install with them (one pair is 2x8GB - GSKILL the other is 2x16GB - CORSAIR). Both of these are working OK for install and both are with "Rank: 2".

He has only one pair with "Rank: 1" (they are more rare I think), but install keeps giving the error with them in all cases, also if using only a single DIMM, also when using both DIMMs.

 

I don't know what we should be doing with this information, I was mentioning it as maybe together we can understand what is going on here...

 

I tried, on my system, to add:

newSmbiosTable.Attributes = 1 

Just to see if it makes me also get the error (as my Rank also was 2) - but the error did not appear on my System (I don't actually have single-rank DIMMs to test with them, so I tried only to fake the rank).

 

There are many reports on the net (at other sites) about this issue, no one mentioned the Rank, but in most cases it was closed by using other DIMMs or moving the DIMMs in other slots (on boards that have more slots). So this is a memory issue, and in my opinion is is somehow related to the Rank. 

 

 

 

 

 

long time no see.

today i went home ofparents. and i checked desktop smbios type 17

Handle 0x1100, DMI type 17, 40 bytes
0000: 11 28 00 11 00 10 ff ff 40 00 40 00 00 20 09 01 
0010: 01 02 1a 80 00 55 08 03 04 00 06 01 00 00 00 00 
0020: 55 08 00 00 00 00 b0 04 

Memory Device
	Array Handle: 0x1000
	Error Information Handle: No Error
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 8192 MB
	Form Factor: DIMM
	Set: 1
	Locator: DIMM0
	Bank Locator: BANK 0
	Type: <OUT OF SPEC>
	Type Detail: Synchronous
	Speed: 2133 MHz (0.5 ns)
	Manufacturer: Samsung
	Serial Number: 090903050F06080A
	Asset Tag: Not Specified
	Part Number: M378A1K43BB1-CPB
	Rank: 1
	Configured Clock Speed: 2133 MHz (0.5 ns)
	Minimum voltage:  Unknown
	Maximum voltage:  Unknown
	Configured voltage:  1.200 V

Handle 0x1101, DMI type 17, 84 bytes
0000: 11 54 01 11 00 10 ff ff ff ff ff ff 00 00 09 02 
0010: 01 02 00 80 00 00 00 00 00 00 00 00 00 00 00 00 
0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0050: 00 00 00 00 

Memory Device
	Array Handle: 0x1000
	Error Information Handle: No Error
	Total Width: Unknown
	Data Width: Unknown
	Size: No Module Installed
	Form Factor: DIMM
	Set: 2
	Locator: DIMM1
	Bank Locator: BANK 0
	Type: <OUT OF SPEC>
	Type Detail: Synchronous
	Speed: Unknown
	Manufacturer: Not Specified
	Serial Number: Not Specified
	Asset Tag: Not Specified
	Part Number: Not Specified
	Rank: Unknown
	Configured Clock Speed: Unknown
	Minimum voltage:  Unknown
	Maximum voltage:  Unknown
	Configured voltage:  Unknown

Handle 0x1102, DMI type 17, 84 bytes
0000: 11 54 02 11 00 10 ff ff ff ff ff ff 00 00 09 03 
0010: 01 02 00 80 00 00 00 00 00 00 00 00 00 00 00 00 
0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0050: 00 00 00 00 

Memory Device
	Array Handle: 0x1000
	Error Information Handle: No Error
	Total Width: Unknown
	Data Width: Unknown
	Size: No Module Installed
	Form Factor: DIMM
	Set: 3
	Locator: DIMM2
	Bank Locator: BANK 0
	Type: <OUT OF SPEC>
	Type Detail: Synchronous
	Speed: Unknown
	Manufacturer: Not Specified
	Serial Number: Not Specified
	Asset Tag: Not Specified
	Part Number: Not Specified
	Rank: Unknown
	Configured Clock Speed: Unknown
	Minimum voltage:  Unknown
	Maximum voltage:  Unknown
	Configured voltage:  Unknown

Handle 0x1103, DMI type 17, 84 bytes
0000: 11 54 03 11 00 10 ff ff ff ff ff ff 00 00 09 04 
0010: 01 02 00 80 00 00 00 00 00 00 00 00 00 00 00 00 
0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0050: 00 00 00 00 

Memory Device
	Array Handle: 0x1000
	Error Information Handle: No Error
	Total Width: Unknown
	Data Width: Unknown
	Size: No Module Installed
	Form Factor: DIMM
	Set: 4
	Locator: DIMM3
	Bank Locator: BANK 0
	Type: <OUT OF SPEC>
	Type Detail: Synchronous
	Speed: Unknown
	Manufacturer: Not Specified
	Serial Number: Not Specified
	Asset Tag: Not Specified
	Part Number: Not Specified
	Rank: Unknown
	Configured Clock Speed: Unknown
	Minimum voltage:  Unknown
	Maximum voltage:  Unknown
	Configured voltage:  Unknown

i can't install 10.14+ now from usb installer. only need to update mojave or catalina from high sierra.

i will test smbios version and memory rank

Edited by Sherlocks

Share this post


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

 

long time no see.

today i went home ofparents. and i checked desktop smbios type 17


Handle 0x1100, DMI type 17, 40 bytes
0000: 11 28 00 11 00 10 ff ff 40 00 40 00 00 20 09 01 
0010: 01 02 1a 80 00 55 08 03 04 00 06 01 00 00 00 00 
0020: 55 08 00 00 00 00 b0 04 

Memory Device
	Array Handle: 0x1000
	Error Information Handle: No Error
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 8192 MB
	Form Factor: DIMM
	Set: 1
	Locator: DIMM0
	Bank Locator: BANK 0
	Type: <OUT OF SPEC>
	Type Detail: Synchronous
	Speed: 2133 MHz (0.5 ns)
	Manufacturer: Samsung
	Serial Number: 090903050F06080A
	Asset Tag: Not Specified
	Part Number: M378A1K43BB1-CPB
	Rank: 1
	Configured Clock Speed: 2133 MHz (0.5 ns)
	Minimum voltage:  Unknown
	Maximum voltage:  Unknown
	Configured voltage:  1.200 V

Handle 0x1101, DMI type 17, 84 bytes
0000: 11 54 01 11 00 10 ff ff ff ff ff ff 00 00 09 02 
0010: 01 02 00 80 00 00 00 00 00 00 00 00 00 00 00 00 
0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0050: 00 00 00 00 

Memory Device
	Array Handle: 0x1000
	Error Information Handle: No Error
	Total Width: Unknown
	Data Width: Unknown
	Size: No Module Installed
	Form Factor: DIMM
	Set: 2
	Locator: DIMM1
	Bank Locator: BANK 0
	Type: <OUT OF SPEC>
	Type Detail: Synchronous
	Speed: Unknown
	Manufacturer: Not Specified
	Serial Number: Not Specified
	Asset Tag: Not Specified
	Part Number: Not Specified
	Rank: Unknown
	Configured Clock Speed: Unknown
	Minimum voltage:  Unknown
	Maximum voltage:  Unknown
	Configured voltage:  Unknown

Handle 0x1102, DMI type 17, 84 bytes
0000: 11 54 02 11 00 10 ff ff ff ff ff ff 00 00 09 03 
0010: 01 02 00 80 00 00 00 00 00 00 00 00 00 00 00 00 
0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0050: 00 00 00 00 

Memory Device
	Array Handle: 0x1000
	Error Information Handle: No Error
	Total Width: Unknown
	Data Width: Unknown
	Size: No Module Installed
	Form Factor: DIMM
	Set: 3
	Locator: DIMM2
	Bank Locator: BANK 0
	Type: <OUT OF SPEC>
	Type Detail: Synchronous
	Speed: Unknown
	Manufacturer: Not Specified
	Serial Number: Not Specified
	Asset Tag: Not Specified
	Part Number: Not Specified
	Rank: Unknown
	Configured Clock Speed: Unknown
	Minimum voltage:  Unknown
	Maximum voltage:  Unknown
	Configured voltage:  Unknown

Handle 0x1103, DMI type 17, 84 bytes
0000: 11 54 03 11 00 10 ff ff ff ff ff ff 00 00 09 04 
0010: 01 02 00 80 00 00 00 00 00 00 00 00 00 00 00 00 
0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0050: 00 00 00 00 

Memory Device
	Array Handle: 0x1000
	Error Information Handle: No Error
	Total Width: Unknown
	Data Width: Unknown
	Size: No Module Installed
	Form Factor: DIMM
	Set: 4
	Locator: DIMM3
	Bank Locator: BANK 0
	Type: <OUT OF SPEC>
	Type Detail: Synchronous
	Speed: Unknown
	Manufacturer: Not Specified
	Serial Number: Not Specified
	Asset Tag: Not Specified
	Part Number: Not Specified
	Rank: Unknown
	Configured Clock Speed: Unknown
	Minimum voltage:  Unknown
	Maximum voltage:  Unknown
	Configured voltage:  Unknown

i can't install 10.14+ now from usb installer. only need to update mojave or catalina from high sierra.

i will test smbios version and memory rank

 

info.

laptop: everything is okay

desktop: always data error when install macos from usb installer on 10.14+. 

 

okay. tested it.

no effect memory rank part.

i checked my laptop. my laptop single channel ram and needed to add memory info in smbios in config to avoid memory error.

 

i added memory info in config like my laptop.

there is no problem. finally i skipped data error message when install macos catalina from usb installer. i dont know and not sure exact problem.

Edited by Sherlocks

Share this post


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

 

info.

laptop: everything is okay

desktop: always data error when install macos from usb installer on 10.14+. 

 

okay. tested it.

no effect memory rank part.

i checked my laptop. my laptop single channel ram and needed to add memory info in smbios in config to avoid memory error.

 

i added memory info in config like my laptop.

there is no problem. finally i skipped data error message when install macos catalina from usb installer. i dont know and not sure exact problem.

Hi,

What memory info did you add exactly?

Also, how does dmi dump look after you added memory info?

Share this post


Link to post
Share on other sites
1 hour ago, anmool said:

preboot log attached

preboot.log

It looks like all needed kexts are successfully loaded including VoodooI2C and VoodooPS2. I just don't know why both should be used. AFAIK PS2 is a bus and I2C is another bus. You should use one or another, but I don't know the logic of these kexts. You should ask something else.

At my side Clover does all work.

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 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 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!
    • By dgsga
      Can I propose a new subforum be created for the new OpenCorePkg OpenCore front end being created by vit9696 and others, it is a fantastic piece of work:
      https://github.com/acidanthera/OpenCorePkg
      Even at version 0.1 it runs my Mojave 10.14.4 setup very nearly flawlessly. It consists of a 10KB bootstrap BootX64.efi and a 200KB OpenCore.efi OS loader. All configuration is done using a very well documented config.plist 
       
       
×