Jump to content
GhostRaider

[GUIDE] MSI H81M Motherboards - Basics of a Computer Build - Budget Hackintosh Builds - UEFI Dualboot - OS X El Capitan WIP*

156 posts in this topic

Recommended Posts

Advertisement

rc3KeZm.png
Note: Users who are installing OS X Yosemite or earlier versions of OS X do not need to read this section!
 
So what is this System Integrity Protection (SIP) that Apple is implementing in OS X El Capitan and future versions of OS X? To simplify this as much as possible, basically Apple will restrict users from modifying the System folder, bin folder, usr folder, and sbin folder. Some of these folders are already hidden by default. 
 
Apple's attempt of locking down the system from being modified by hackers, viruses, trojans, and so on isn't bad at all. In fact, who doesn't want to use a computer thats really secured? 
 
There is a problem, and that problem is the Hackintosh. How does System Integrity Protection (SIP) affect the Hackintosh? 
 
This affects kernel extensions, also known as kexts for short. 
 
As you well know, kexts play a big role in a Hackintosh. Kexts enable all sorts of stuff like power management, graphics, and audio. The most important and well known kext, FakeSMC, allows OS X to boot on PCs. In OS X Yosemite and earlier versions of OS X, all you had to do was to use Kext Utility or some other kext installer to install kexts to /System/Library/Extensions. Or if you didn't want to do that, you could have installed them in the Clover kext folders. With Clover, you could have also patched kexts on-the-fly without ever replacing an existing kext.
 
The good news is that the development team behind Clover have successfully found a way to allow kext injection from the CLOVER/kexts/ folder for OS X El Capitan. So if Clover can inject kexts again, what's the problem?
 
Starting from Clover version r3253, we have some new values to play with in Clover's plist file. Remember, to take advantage of these new features, you must upgrade your Clover bootloader to version r3253 or higher. If this portion of the code isn't there as shown below, then it must be added manually by editing the plist file. However, these values can also be set using the newest version of Clover Configurator in the RtVariables section.

<key>RtVariables</key>
<dict>
<key>CsrActiveConfig</key>
<string>0x67</string>
<key>BooterConfig</key>
<string>0x28</string>
</dict> 

uBKrYFZ.png
If you are using Clover Configurator, in the RT Variables section, we have two new keys, CsrActiveConfig and BooterConfig. For now, do not worry about BooterConfig, just accept that it has to be set to 0x28. 
 
Remember the rootless=0 flag? If not, it used to disable SIP and allow unsigned kexts in OS X El Capitan but it's useless now so there's no point in enabling that. We must move forward and use CsrActiveConfig to allow access.
 
CsrActiveConfig has a value set to 0x67. What does that mean? This value disables SIP and allows the user to install kexts in the /System/Library/Extensions and /Library/Extensions folder without problems.
 
If you want to know what is happening behind the scenes, this is what happens:
 

1. Setting CsrConfig to value 0x67

 
1 CSR_ALLOW_UNTRUSTED_KEXTS 
1 CSR_ALLOW_UNRESTRICTED_FS
1 CSR_ALLOW_TASK_FOR_PID
0 CSR_ALLOW_KERNEL_DEBUGGER
0 CSR_ALLOW_APPLE_INTERNA
1 CSR_ALLOW_UNRESTRICTED_DTRACE1
1 CSR_ALLOW_UNRESTRICTED_NVRAM
 
Well what does that all mean? Remember that a 1 enables that option and 0 disables that option. There are some options here that we will ignore since they don't have a significant impact. These are the important options to look at:
 
CSR_ALLOW_UNTRUSTED_KEXTS

  • Allows OS X to use unsigned kexts.

CSR_ALLOW_UNRESTRICTED_FS

  • Allows the user to manipulate the file system.

That should clear things up. Let's look at another configuration.
 
2. Setting CsrConfig to value 0x03
 
1 CSR_ALLOW_UNTRUSTED_KEXTS 
1 CSR_ALLOW_UNRESTRICTED_FS
0 CSR_ALLOW_TASK_FOR_PID
0 CSR_ALLOW_KERNEL_DEBUGGER
0 CSR_ALLOW_APPLE_INTERNA
0 CSR_ALLOW_UNRESTRICTED_DTRACE1 
0 CSR_ALLOW_UNRESTRICTED_NVRAM
 
It seems that unsigned kexts are enabled as well as access to the file system. Isn't that what you need in order to have a working Hackintosh? The answer is YES!
 
So basically wouldn't it be better to use 0x03 instead of 0x67? Again, you are correct! Now, the reason why the default setting is 0x67 is to make sure that you are able to install OS X and run OS X with no problems. We want to install OS X and configure it as quickly as possible. 
 
After installation, and after you have installed Clover, you can change CsrActiveConfig to have a value of 0x03. Everything will still work. Notice that we are incrementing the security of our Hackintosh.
 
Let's look at another configuration.
 
3. Setting CsrConfig to value 0x01
 
1 CSR_ALLOW_UNTRUSTED_KEXTS 
0 CSR_ALLOW_UNRESTRICTED_FS
0 CSR_ALLOW_TASK_FOR_PID
0 CSR_ALLOW_KERNEL_DEBUGGER
0 CSR_ALLOW_APPLE_INTERNA
0 CSR_ALLOW_UNRESTRICTED_DTRACE1 
0 CSR_ALLOW_UNRESTRICTED_NVRAM
 
We still have unsigned kexts working but we now have restricted the file system. Be careful with this setting. This configuration basically prevents you from installing kexts since you do not have access to the file system.
 
However, if you have installed all of the kexts you need to have a working system and the kext cache has been rebuilt to include those kexts, then you can use this configuration. The hassle with this option is that you need to enable 0x03 again if Apple has replaced a patched native kext during an update, like AppleHDA, and then you would have to change it back to 0x01 after you patched it again. Of course if the patches are injected by Clover, then you don't have to worry about anything as the cache gets patched, not the kext itself. If security is very important to you, then this option will probably be the best for you.
 
What about this configuration?
 
4. Setting CsrConfig to value 0x00
 
0 CSR_ALLOW_UNTRUSTED_KEXTS 
0 CSR_ALLOW_UNRESTRICTED_FS
0 CSR_ALLOW_TASK_FOR_PID
0 CSR_ALLOW_KERNEL_DEBUGGER
0 CSR_ALLOW_APPLE_INTERNA
0 CSR_ALLOW_UNRESTRICTED_DTRACE1 
0 CSR_ALLOW_UNRESTRICTED_NVRAM
 
Clearly you're the ultimate Hackintosher if you use this one!   :gun: But seriously, this is also a good option. This basically enables SIP to its fullest potential. The way you use this option is when you have completely working system. Do not use this option if you are going to update OS X. Only use this configuration when you won't need to manipulate any kexts or the file system or do any OS X update (software updates likes iTunes or security updates are okay). What's the benefit? You will have a secured hackintosh.
 
Now that you get an idea of the different configurations for CSR, how do you install a kext?
 
The same way you do now! Install the kexts in S/L/E or /L/E and use Kext Utility to rebuild cache and permissions! Else any kexts that are independent can go in CLOVER/kexts/10.x.
 

After that, you decide what SIP configuration you want!

MElIPFF.png

Everyone in the Hackintosh scene knows who Intel is right? If not, then they are a company who makes processors for computers. You may have seen Intel stickers on various desktop and laptop computers as well as Intel products online and in electronic stores. For Hackintosh users, Intel processors are the only processors to consider as they are currently used on all Apple Mac products. 

 

So if Apple uses Intel processors, does it mean that OS X will work on any Intel processor? Theoretically yes, but in practice it can be a huge pain in the butt.

 

The main problem that people can run into when a Hackintosh computer is using an unsupported processor is an instant reboot. An unsupported processor is basically an Intel processor that was never used on an Apple Mac computer. For example, Intel Pentium and Intel Celeron processors have never been used on Apple's Mac product lineup.

 

Does it mean that you cannot use an Intel Celeron or an Intel Pentium processor? Well no, in fact, with a little bit of tweaking in Clover's settings, we can make these processors work! Basically what happens is that by injecting a certain value using Clover, we can fool OS X into thinking that is a typical normal processor that is compatible with OS X. Using Clover Configurator, in the Kernel and Kexts Patches section we have a box called FakeCPUID.

QHbWk6X.png

The FakeCPUID box is used to set a processor value. So what values go in there? Good question. The chart below should help.

 

WruV0Q1.png

 

The values that go in the FakeCPUID box are on the CPUID column. Okay, so then how does one determine what value to choose for an unsupported processor? Unfortunately, this is a trial and error situation. Luckily for many people, by doing a google search or asking around in the forums, you will find the answer. 

 

Example 1) Suppose that for some unknown reason you want to use an Intel® Pentium G3258 processor. How do you make it work?

  • First of all, we know that this processor was never used in any Mac computer.
  • Have we searched on Google or asked around in the forums?
  • Do we even know which OS X version this processor supports?
  • What SMBIOS should we use?

Solution 1) By doing a little google research I have found that setting FakeCPUID to value 0x0306A0 or 0x0106E0 will make it work. That doesn't seem hard does it? There's a catch but this will be explained later.

 

We also see that this unsupported processor is based on the Haswell architecture.

 

:excl: NOTE: It is highly recommended that you use OS X Yosemite or later releases of OS X if you are planning to use unsupported processors. This solves a lot of issues. For example, OS X Yosemite has support for Haswell architecture while OS X Mountain Lion gained support for Ivy Bridge architecture. It doesn't make sense to use an architecture that was not supported on an older release of OS X. However, if you use the latest releases of OS X, then you are guaranteed that your unsupported processor will work, well with some tweaks of course.

 

So now you have to set FakeCPUID to one of those two values. Type it in or copy and paste it, your choice.

m64cM1c.png

As for what SMBIOS you should use, you will have to research on that. In the case of the Intel® Pentium G3258 processor, since we are using an Ivy Bridge CPUID, it fits well with an SMBIOS emulating an Ivy Bridge based Mac like the MacMini6,2 or iMac13,1 or iMac13,2. 

 

Okay this is great and all but if I can't boot my Hackintosh in the first place, how am I suppose to do these steps? Good question. You can use an OS X virtual machine or an existing Mac. Normally when you make an OS X USB installer, you would have to have access to OS X regardless. Then using Clover Configurator, you can open the Clover.plist file inside the OS X USB drive and make the necessary changes.

 

Example 2) Suppose that you finally were able to boot OS X with that unsupported processor and you did whatever you needed to do with it. You realized that there is no graphics acceleration, or that your screen resolution is messed up. What do you do?

 

Solution 2) This is basically the catch. Even though you may have successfully booted OS X, you will not get graphics acceleration or correct screen resolution on unsupported processors. This is very problematic on Hackintosh laptops since you cannot change the processor or add an external graphics card. However, for desktop computers, this is not a big problem. 

 

In order to get graphics acceleration using an unsupported Intel processor on a Hackintosh desktop is to buy a compatible dedicated graphics card. Once you install the graphics card on your Hackintosh, then you'll have a working Hackintosh system even if the Intel processor you chose isn't supported!

 

Even though you can get around this issue, is it worth it? Should you instead just save money and buy a compatible Intel processor? This depends on you.

 

You see, every person has his or her needs. Sometimes individuals can be in a tight financial budget but they need a Hackintosh for some unknown reason. The best decision is to save money until you are able to buy a compatible Intel processor. It takes the least amount of effort and you know that it will work. However, if you don't mind the extra hassle, then go for it! Always do some research before making a decision!

 

So if I buy a compatible Intel processor, is it guaranteed I won't run into a problem? Unfortunately you can run into problems, but it is easier to solve. Let's take a look at all compatible processors for OS X:

 

1st Generation Intel® Core™ Processors based on Westmere Architecture

  • Intel® Core™ i3
  • Intel® Core™ i5
  • Intel® Core™ i7

*Certain processor models contain Intel® HD Graphics. All processor models will not have graphics acceleration on OS X (Applies to desktop processor models only. Not to be confused with laptop processor models). 

 

2nd Generation Intel® Core™ Processors based on Sandy Bridge Architecture

  • Intel® Core™ i3
  • Intel® Core™ i5
  • Intel® Core™ i7

*Certain processor models contain Intel® HD Graphics 3000 or Intel® HD Graphics 2000 integrated graphics. Processor models containing Intel® HD Graphics 2000 will not have graphics acceleration on OS X. 

 

3rd Generation Intel® Core™ Processors based on Ivy Bridge Architecture

  • Intel® Core™ i3
  • Intel® Core™ i5
  • Intel® Core™ i7

*Certain processor models contain Intel® HD Graphics 4000 or Intel® HD Graphics 2500 integrated graphics. Processor models containing Intel® HD Graphics 2500 will not have graphics acceleration on OS X. 

 

4th Generation Intel® Core™ Processors based on Haswell Architecture

  • Intel® Core™ i3
  • Intel® Core™ i5
  • Intel® Core™ i7

*Certain processor models contain Intel® HD Graphics 4400 or Intel® HD Graphics 4600 integrated graphics.

 

5th Generation Intel® Core™ Processors based on Broadwell Architecture

  • Intel® Core™ i5
  • Intel® Core™ i7

*All processor models contain Intel® Iris™ Pro Graphics 6200 integrated graphics.

 

6th Generation Intel® Core™ Processors based on Skylake Architecture

  • No information available. Apple has not released any Mac with this processor architecture.

7th Generation Intel® Core™ Processors based on Kaby Lake Architecture

  • No information available. Apple has not released any Mac with this processor architecture.

As you can see, there are a lot of compatible processors to use on a Hackintosh. Some of these processors have compatible integrated graphics which eliminates the need to buy a separate dedicated graphics card. If you are looking for a compatible processor for your Hackintosh, these questions arise:

  • Which architecture should I buy?
  • Should I buy a processor with compatible integrated graphics?
  • Should I buy an Intel® Core™ i3, i5, or i7?
  • What version of OS X will this compatible processor support?
  • What SMBIOS should I use with a compatible processor?

Let's answer these 3 questions.

 

Question 1) Which architecture should I buy?

 

Solution 1) This depends on the motherboard CPU socket. The motherboard you bought determines what CPU is compatible for your Hackintosh. Remember that higher generation Intel® Core™ processors are usually faster and give better performance due to their architecture.

 

Question 2) Should I buy a processor with compatible integrated graphics?

 

Solution 2) This depends on you. If you want to build a Hackintosh but don't want to buy a dedicated graphics card, then a processor with a compatible integrated graphics is recommended. You will have graphics acceleration once you have configured OS X. If you want to build a Hackintosh and you plan on using a dedicated graphics card, then any compatible processor will work for you. It is recommended to buy a compatible processor with compatible integrated graphics because its gives the ability to use multiple displays and helps in certain situations where your dedicated graphics card might fail but doesn't prevent you from using OS X.

 

Question 3) Should I buy an Intel® Core™ i3, i5, or i7?

 

Solution 3) This depends on your computing needs. This should help break down the difference:

 

Intel® Core™ i3

  • Great for typical everyday tasks. 
  • Good for average gaming.
  • Good for typical photo and video editing.
  • Can cause compute intense applications to bottleneck. Bottleneck means that the CPU has reached its limit and applications cannot perform to their maximum potential. Can cause low FPS (frames per second) on some games.

Intel® Core™ i5

  • Typical tasks are handled with no problem.
  • Better for high end gaming.
  • Better for complex photo and video manipulation/editing. 

Intel® Core™ i7

  • Best performance for high end gaming.
  • Best performance for rendering, encoding, decoding videos.
  • Best performance for complex photo and video manipulation/editing.
  • Best performance for graphics animations and game building.

Remember that these comparisons are based off of computing needs, not graphics performance. 

 

If graphics performance is important to you, then the integrated graphics included on some compatible Intel® Core™ processors will disappoint you. Integrated graphics are good for non intensive graphics applications. If you try to play high end games with integrated graphics, performance will be very low as these are not designed for that. This requires the need for a dedicated graphics card.

 

Question 4) What version of OS X will this processor support?

 

Solution 4) To make your life so much easier, use OS X Yosemite or later releases. Don't question it, just embrace it.

 

Question 5) What SMBIOS should I use with a compatible processor?

 

Solution 5) Again research is key. For example, if we are using a compatible Haswell processor, we can see that the iMac14,1 and iMac14,2 fit this criteria because these models used Haswell processors. Similarly if we wanted to use a compatible Ivy Bridge processor, then the iMac13,1 and iMac13,2 fit this criteria because theses models used Ivy Bridge processors and so on.

 

Let's take a look at compatible integrated graphics processing units (IGPUs) from the Intel® Core™ processor family. Remember, only compatible IGPUs will be listed.

 

2nd Generation Intel® Core™ Processors based on Sandy Bridge Architecture

  • Intel® HD Graphics 3000

3rd Generation Intel® Core™ Processors based on Ivy Bridge Architecture

  • Intel® HD Graphics 4000

4th Generation Intel® Core™ Processors based on Haswell Architecture

  • Intel® HD Graphics 4400
  • Intel® HD Graphics 4600

5th Generation Intel® Core™ Processors based on Broadwell Architecture

  • Intel® Iris™ Pro Graphics 6200

6th Generation Intel® Core™ Processors based on Skylake Architecture

  • No information available. Apple has not released any Mac with this processor architecture.

7th Generation Intel® Core™ Processors based on Kaby Lake Architecture

  • No information available. Apple has not released any Mac with this processor architecture.

Let's investigate all these compatible IGPUs in more detail and see how to make them work on OS X.

 

1. Intel® HD Graphics 3000

 

Apple started supporting the Intel® HD Graphics 3000 IGPU with the release of OS X Lion. I did not like OS X Lion. Anyways, this IGPU works best on OS X Yosemite or later.

 

Since we are using Clover Bootloader, the team behind Clover did not implement a direct way to enable the Intel® HD Graphics 3000 IGPU. Problem?  :unsure:

 

No problem.  ^_^

 

Let's open up Clover Configurator. We are interested in the Devices section.

EazDrjw.png

In order fix this problem, we are going to add some properties. We need this information first to get started:

 

1) Device

2) Key

3) Value

4) Value Type

 

Click on the "+" button at the bottom of the Add Properties box. Follow the instructions below.

 

1) Device

 

In the Device box, type in:

IntelGFX

2) Key

 

In the Key box, type in:

AAPL,snb-platform-id

3) Value

 

In the Value box, type in:

10000300

4) Value Type

 

In the Value Type box, select "data".

 

Now, we will need to fake the ID of the Intel® HD Graphics 3000 IGPU. In the same Devices section, there is a Fake ID area. We are only interested in the IntelGFX box.

 

In the IntelGFX box, type:

0x01268086

In the end, you should have something like this:

 

TKQnFgq.png

 

We are almost done. All that's left is to go to the Graphics section and enable "Inject Intel".

CvkowDB.png

As for the SMBIOS to use, you could use MacPro3,1 or MacMini5,1 as a test since these use Sandy Bridge processors. Otherwise use an SMBIOS that similarly matches your Hackintosh (i.e. MacPro3,1). That's it for enabling QE/CI (graphics acceleration) for Intel® HD Graphics 3000 on the desktop!

 

​*Video ports enabled using this method are DP, DVI, and HDMI. Multiple monitor support using only the IGPU might not work with this method. Framebuffer edits may be required to enable multiple monitor support or to enable custom video ports using only the IGPU. The built-in VGA ports on motherboards are not supported on OS X.

 

*Credit to RehabMan and Toleda.

 

2. Intel® HD Graphics 4000

 

Apple started supporting the Intel® HD Graphics 4000 IGPU with the release of OS X Mountain Lion. OS X Mountain Lion is like Windows XP in the Mac world. Excellent release, but we have to move on. Anyways, this IGPU works best on OS X Yosemite or later.

 

Compared to the method used by the Intel® HD Graphics 3000 IGPU, enabling this IGPU is easier. 

 

Let's open Clover Configurator and go to the Graphics section.

ceR2eKc.png

In the ig-platform-id box, type in:

0x0166000A

Next, enable "Inject Intel". You should now have something like this:

 

JQ4AbI6.png

 

As for the SMBIOS, select a model that uses an Ivy Bridge processor. Otherwise use an SMBIOS that similarly matches your Hackintosh (i.e. MacPro3,1).

 

That's it for enabling QE/CI (graphics acceleration) for Intel® HD Graphics 4000 on the desktop!

 

*Video ports enabled using this method are DP, DVI, and HDMI. Multiple monitor support using only the IGPU might not work with this method. Framebuffer edits may be required to enable multiple monitor support or to enable custom video ports using only the IGPU. The built-in VGA ports on motherboards are not supported on OS X.

 

*Credit to RehabMan and Toleda.

 

3. Intel® HD Graphics 4400

 

Well this is an interesting one. From what we know, Apple never used Intel® HD Graphics 4400 on there Mac computers. That's right, Apple has won the war on the Hackintosh and has left Hackintoshes with the Intel® HD Graphics 4400 IGPU out in the cold.  :cry:

 

...well this is true if you somehow ended up having a Hackintosh with Intel® HD Graphics 2000 or Intel® HD Graphics 2500. If you are one of them, I hope that you have found a solution to this.

 

But jokes aside, the good news is that Intel® HD Graphics 4400 is supported! I think this was kind of obvious.  :P Anyways, this IGPU works best on OS X Yosemite or later.

 

The question is, how do we do this?

 

Well, we will need 2 kexts from RehabMan. We will need "FakePCIID.kext" and "FakePCIID_Intel_HD_Graphics.kext". You can get them from the link here: https://bitbucket.org/RehabMan/os-x-fake-pci-id/downloads. Just download the latest version and extract the ZIP archive file. These are the 2 kexts you will be working with:

 

8glMurP.png

 

These kext files will go to Clover's kext folder. You may need to mount the EFI partition to gain access to the Clover folder. Once you are inside the Clover folder, go to Kexts and open the folder corresponding to the version of OS X you are using (For example, if you are using OS X Yosemite, then Clover will load kexts inside the 10.10 folder and so on). Drag or copy the two kexts into the corresponding folder.

jLU7qGo.png

Now, we can open Clover Configurator. We will need to fake the ID of the Intel® HD Graphics 4400 IGPU. Go to the Devices section and you will see that there is a Fake ID area. We are only interested in the IntelGFX box.

 

In the IntelGFX box, type in:

0x04128086

You should now have something like this:

 

BNCAPqH.png

 

Now, go to the Graphics section. In the ig-platform-id box, type in:

0x0D220003

Next, enable "Inject Intel". You should now have something like this:

 

GzRE7nd.png

 

As for the SMBIOS, select a model that uses a Haswell processor. Otherwise use an SMBIOS that similarly matches your Hackintosh (i.e. MacPro3,1).

 

That's it for enabling QE/CI (graphics acceleration) for Intel® HD Graphics 4400 on the desktop!

 

*Video ports enabled using this method are DP, DVI, and HDMI. Multiple monitor support using only the IGPU might not work with this method. Framebuffer edits may be required to enable multiple monitor support or to enable custom video ports using only the IGPU. The built-in VGA ports on motherboards are not supported on OS X.

 

*Credit to RehabMan and Toleda.

 

4. Intel® HD Graphics 4600

 

Do I smell another IGPU that was not used on any Mac computer? Yes, indeed. Apple again has defeated us. It's over.  :cry:

 

...eh not quite. But the war isn't over yet, it is just the beginning!  :boxing:

 

Anyways, this IGPU works best on OS X Yosemite or later. Let's go to work!

 

Let's open Clover Configurator and go to the Graphics section.

ceR2eKc.png

In the ig-platform-id box, type in:

0x0D220003

Next, enable "Inject Intel". You should now have something like this:

 

GzRE7nd.png

 

As for the SMBIOS, select a model that uses a Haswell processor. Otherwise use an SMBIOS that similarly matches your Hackintosh (i.e. MacPro3,1).

 

That's it for enabling QE/CI (graphics acceleration) for Intel® HD Graphics 4600 on the desktop! (I'm not joking, that's all you have to do!  :rofl:

 

*Video ports enabled using this method are DP, DVI, and HDMI. Multiple monitor support using only the IGPU might not work with this method. Framebuffer edits may be required to enable multiple monitor support or to enable custom video ports using only the IGPU. The built-in VGA ports on motherboards are not supported on OS X.

 

*Credit to RehabMan and Toleda.

 

5. Intel® Iris™ Pro Graphics 6200

 

Apple started supporting the Intel® Iris™ Pro Graphics 6200 IGPU with the release of OS X El Capitan. Only the 21.5 inch Retina 4K iMac (Late 2015) uses this IGPU. Intel has also released desktop processors containing this IGPU but the truth is, it's very rare to hear a Hackintosh having a Broadwell CPU. 

 

Aside from that, this IGPU works best on OS X El Capitan or later.

 

Open Clover Configurator and go to the Graphics section.

ceR2eKc.png

In the ig-platform-id box, type in:

0x02002216

Next, enable "Inject Intel". You should now have something like this:

 

DHaGZzh.png

 

As for the SMBIOS, select a model that uses a Broadwell processor (i.e. iMac16,2). Otherwise use an SMBIOS that similarly matches your Hackintosh (i.e. MacPro3,1).

 

That's it for enabling QE/CI (graphics acceleration) for Intel® Iris™ Pro Graphics 6200 on the desktop!

 

*Video ports enabled using this method are DP, DVI, and HDMI. Multiple monitor support using only the IGPU might not work with this method. Framebuffer edits may be required to enable multiple monitor support or to enable custom video ports using only the IGPU. The built-in VGA ports on motherboards are not supported on OS X.

 

*Credit to RehabMan and Toleda.

 

That's it for this section! Always remember to research before buying. This will make your life so much easier when building or using Hackintoshes. By researching, you also gain information on what to do if you plan on using certain hardware!  :happymac:

nb6vxd5.png

So what is the DSDT? The DSDT (Differentiated System Description Table) is a table that is part of the ACPI (Advanced Configuration Power Interface) specification. Basically it contains information about hardware and power events. The problem with DSDTs is that they are either incomplete or problematic for OS X. Those are the reasons why many people patch their DSDTs so that OS X can function properly with their PC hardware.

For this guide, I will be talking about how to compile your DSDT so that you can have it ready if you ever want to add patches in the future. For any other hardware, you will need to search the InsanelyMac forums for more information.
:moil: Yeah, eventually I'll finish this part lol

Edited by GhostRaider

Share this post


Link to post
Share on other sites

Perfect! 

 

Your guides are always very good, congratulations for their dedication and hard work!  :D

Thank you!  :)  I just like helping people out so that maybe most of their questions get answered in the guide. That's why they are kind of long lol

Share this post


Link to post
Share on other sites

I just installed 10.10 on my H81M-E33 and for the life of me I can't get the audio to install. When I try to use the command it tells me to enter a chipset and when I put in 887 it says "ALC887 v_ not supported" and asks me to use the legacy patch. I tried that and it never worked.

 

Thanks!

Share this post


Link to post
Share on other sites

I just installed 10.10 on my H81M-E33 and for the life of me I can't get the audio to install. When I try to use the command it tells me to enter a chipset and when I put in 887 it says "ALC887 v_ not supported" and asks me to use the legacy patch. I tried that and it never worked.

 

Thanks!

Sorry for the long delay, but did you end up fixing it or you still have this issue?

Share this post


Link to post
Share on other sites

Sorry for the long delay, but did you end up fixing it or you still have this issue?

Still having it, couldn't figure out what the problem was.

Share this post


Link to post
Share on other sites

a very detailed description, very good job! :)

Share this post


Link to post
Share on other sites

Still having it, couldn't figure out what the problem was.

What codec do you have then? Windows should clearly say which one you have if you have it installed. Not sure if DPCIManager on OS X would say which one you have.

 

a very detailed description, very good job! :)

I'm always trying to get complicated and weird information to something easier for an average user to understand  :)

Share this post


Link to post
Share on other sites

Bad choice to select UEFI and ESP on Clover OS X El Capitan  :)

thats not the same as the original Clover Installer, select only one of this clover option

if you want ESP , just select  this option  ;)

Share this post


Link to post
Share on other sites

Bad choice to select UEFI and ESP on Clover OS X El Capitan  :)

thats not the same as the original Clover Installer, select only one of this clover option

if you want ESP , just select  this option  ;)

I was somewhat confused about this because if you only select UEFI it still creates an EFI partition. I would assume that it would put the EFI files with the OS X installer files. There isn't a difference whether you select UEFI or ESP unless this is by design.

Share this post


Link to post
Share on other sites

I was somewhat confused about this because if you only select UEFI it still creates an EFI partition. I would assume that it would put the EFI files with the OS X installer files. There isn't a difference whether you select UEFI or ESP unless this is by design.

This is  big difference UEFI or ESP  

 

UEFI Install only Clover on EFI Partition, no boot file on USB Drive

 

ESP Install Clover on EFI Partition but also boot file on USB drive  :)

 

Select only one Clover choice and this Installer do the job 

 

thanks for your great Tutorial! 

Share this post


Link to post
Share on other sites
Thank you the for well written, easy to follow guide.

 

I also have the MSI H81M-E34. And I'm using an i3 with HD 4600 graphics - no graphics card.

 

This is my first attempt at an Hackintosh, and your guide made installation nice and simple for me.

 

But I'm missing sound via HDMI in Yosemite.

Do you know how I can enable HDMI sound - using the HDMI port on the motherboard?

Share this post


Link to post
Share on other sites

 

Thank you the for well written, easy to follow guide.
 
I also have the MSI H81M-E34. And I'm using an i3 with HD 4600 graphics - no graphics card.
 
This is my first attempt at an Hackintosh, and your guide made installation nice and simple for me.
 
But I'm missing sound via HDMI in Yosemite.
Do you know how I can enable HDMI sound - using the HDMI port on the motherboard?

 

 

Thank you, and welcome to the world of Hackintosh! Yes, HDMI audio is possible. I did not go over this step because I currently do not have an HDMI monitor with speakers on it. So I couldn't test whether it works or not. 

 

There is a great guide written by Toleda on another website that talks about how to enable this. Unfortunately due to forum rules I can't post the direct link, but go to Google and search for "Audio - HDMI Audio AppleHDA [Guide]". Should be the first link.

Share this post


Link to post
Share on other sites

Very good detailed guide! Thank you so much for your work! Love it!!!

 

I have a Pentium G3258 CPU with a MSI H81m-p33 MB, and a EVGA GTX 750 Ti.

 

Would you mind giving some instructions on how to install Yosemite on it?

 

Thank you in advance!

Share this post


Link to post
Share on other sites

@GhostRaider Very nice and Perfect  :thumbsup_anim:  :thumbsup_anim:  :thumbsup_anim:  :thumbsup_anim:

 

i have suggestion for you if you having issue in adding clover entry after Windows installation here is my Workaround   

This way added option  to Bios prompt  to Choose Windows BootManager or OtherOS (which is clover )

 

then you dont required to add EasyEFI tool . 

Share this post


Link to post
Share on other sites

Very good detailed guide! Thank you so much for your work! Love it!!!

 

I have a Pentium G3258 CPU with a MSI H81m-p33 MB, and a EVGA GTX 750 Ti.

 

Would you mind giving some instructions on how to install Yosemite on it?

 

Thank you in advance!

 

You don't really have to do anything different to what the guide says  :). I have to warn you of two things. Since you are using a Pentium CPU, you may run into a kernel panic. Are you familiar with how Clover works? Sorry that I have not covered this in the guide but for a Pentium CPU, you must enable the FakeCPU key in Clover's config.plist file.

 

I'm not sure which string will work on your motherboard. Some say that 0x0306A0 will work. Others say that 0x0106E0 will work too.

 

Basically in the Clover Config plist file find the portion that says KernelAndKextPatches, if it exists. If not then you must create it by copying and pasting the code below.

<key>KernelAndKextPatches</key>
<dict>
<key>FakeCPUID</key>
<string>0x0306A0</string>
</dict>    

If KernelAndKextPatches portion already exist in the config.plist file, then you only copy FakeCPUID and string.

<key>FakeCPUID</key>
<string>0x0306A0</string>

As you notice the string already has a value filled in for you. So if the computer does not boot, then you have to change the value inside the string to the other value i mentioned earlier.

 

The config.plist file that I'm taking about is in the MSI H81 Motherboards pack. You can choose whichever of the two Intel HD Graphics Clover files since the GPU doesn't exist on your system. By default, native NVIDIA driver won't load since you have a Maxwell card. After you have downloaded official drivers from nvidia, you can enable the drivers in the clover.plist file, again having the fakecpuid code in there as well.

 

Second, you must boot using the GTX 750TI card. Don't attempt to boot with the integrated graphics. 

 

If you don't really know what's happening here then I may have to create a custom config.plist file for you since the ones in the motherboards pack is designed for Intel Core CPUs. 

 

Well if you have questions then let me know. Might not respond to them quickly though.

 

 

@GhostRaider Very nice and Perfect  :thumbsup_anim:  :thumbsup_anim:  :thumbsup_anim:  :thumbsup_anim:

 

i have suggestion for you if you having issue in adding clover entry after Windows installation here is my Workaround   

This way added option  to Bios prompt  to Choose Windows BootManager or OtherOS (which is clover )

 

then you dont required to add EasyEFI tool . 

 

This is a great suggestion, but i'm not sure if renaming those boot files is a good thing lol

Share this post


Link to post
Share on other sites

 

This is a great suggestion, but i'm not sure if renaming those boot files is a good thing lol

not asking you to rename files (this is not necessary but only for if you have legacy bios ) but you have to install clover first on HDD and boot to USB from ESP and install it , this windows bootloader will not rule on ESP .. 

i'm testing some more WorkArounds  will update if some will more better than this 

Share this post


Link to post
Share on other sites

Thank you so much! It worked! :thumbsup_anim:

You don't really have to do anything different to what the guide says  :). I have to warn you of two things. Since you are using a Pentium CPU, you may run into a kernel panic. Are you familiar with how Clover works? Sorry that I have not covered this in the guide but for a Pentium CPU, you must enable the FakeCPU key in Clover's config.plist file.

 

I'm not sure which string will work on your motherboard. Some say that 0x0306A0 will work. Others say that 0x0106E0 will work too.

 

Basically in the Clover Config plist file find the portion that says KernelAndKextPatches, if it exists. If not then you must create it by copying and pasting the code below.

<key>KernelAndKextPatches</key>
<dict>
<key>FakeCPUID</key>
<string>0x0306A0</string>
</dict>    

If KernelAndKextPatches portion already exist in the config.plist file, then you only copy FakeCPUID and string.

<key>FakeCPUID</key>
<string>0x0306A0</string>

As you notice the string already has a value filled in for you. So if the computer does not boot, then you have to change the value inside the string to the other value i mentioned earlier.

 

The config.plist file that I'm taking about is in the MSI H81 Motherboards pack. You can choose whichever of the two Intel HD Graphics Clover files since the GPU doesn't exist on your system. By default, native NVIDIA driver won't load since you have a Maxwell card. After you have downloaded official drivers from nvidia, you can enable the drivers in the clover.plist file, again having the fakecpuid code in there as well.

 

Second, you must boot using the GTX 750TI card. Don't attempt to boot with the integrated graphics. 

 

If you don't really know what's happening here then I may have to create a custom config.plist file for you since the ones in the motherboards pack is designed for Intel Core CPUs. 

 

Well if you have questions then let me know. Might not respond to them quickly though.

 

 

 

This is a great suggestion, but i'm not sure if renaming those boot files is a good thing lol

Share this post


Link to post
Share on other sites

Glad it worked for you. Have fun and remember El Capitan Releases on September 30!  B)

 

Thanks! Actually everything works except Sleep/Wake up. Sleep is fine, but I can't wake up it using mouse or keyboard, only power button. And power button will just make it restart, and the CMOS will be reset. I followed this thread:

http://www.insanelymac.com/forum/topic/298536-applertc-patch-cmos-reset/

Now it can't reboot now. The apple logo will show, but the progress bar will not even loaded a bit. Then it reboot again. Don't know what to do...

Thank you for all your help.

Share this post


Link to post
Share on other sites

Thanks! Actually everything works except Sleep/Wake up. Sleep is fine, but I can't wake up it using mouse or keyboard, only power button. And power button will just make it restart, and the CMOS will be reset. I followed this thread:

http://www.insanelymac.com/forum/topic/298536-applertc-patch-cmos-reset/

Now it can't reboot now. The apple logo will show, but the progress bar will not even loaded a bit. Then it reboot again. Don't know what to do...

Thank you for all your help.

 

It doesn't wake up from the keyboard/mouse because the USBs are not receiving power in sleep. This problem can be fixed by reading the MSI H81M Motherboard manual that came in the box. The jumpers to enable S3 state on the motherboard have to be set manually.

 

Yes, I know this is not in the guide either lol. So behind on it.  :moil:

 

After correctly setting up the jumpers, a new option on the MSI BIOS screen will appear called Wake Up Event Setup in the Advanced menu.

 

Wake should work, unless there's a problem with your graphics card. AppleRTC can be patched using clover automatically. As for not booting, you have to boot in verbose mode to see where its getting stuck.

Share this post


Link to post
Share on other sites

Thank you for your reply. I set the timeout of clover boot load to 0... So it wouldn't let me to put in boot args... Do you know any solution?

Thank you so much!

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 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 tonyx86
      This thread for installing Catalina on the Dell Latitude E6410 WITH NVIDIA GRAPHICS (BIOS A17, NVidia 3100m) will help you install a fresh installation of Catalina on your Dell Latitude E6410, it will help you upgrade from 10.15.2 to 10.15.3 (if you originally installed Catalina from this thread) and it will also help you upgrade from Mojave 10.14.6 if you have already installed Mojave by following the instructions here.  The instructions in this first post assume that you are installing Catalina in an APFS container.  If you are curious about the evolution of this solution and how sleep/wake was solved, review the Mojave installation thread.
       
      Important: This Thread is NOT intended to help you install macOS on a Latitude E6410 with Intel HD Graphics (without Nvidia graphics).  The DSDT attached to this first post (in E6410-Catalina.zip) is VERY SPECIFIC to the Nvidia graphics implementation and has not been edited for HD Graphics - there are elements required for HD Graphics that are missing from the attached DSDT and there are DSDT mods that have not been tested with HD Graphics.  Also, the kexts attached to this first post are specific to a Broadcom Wi-Fi card which must replace the original Intel Wi-Fi card.
       
      This first post will be modified to reflect lessons learned and to reflect the most current working state of my Latitude E6410 (with NVidia 3100m discrete graphics) running Catalina.  Issues, observations and performance tips are recorded toward the bottom of this first post.  My recommended CLOVER configuration is specified toward the bottom of this first post.
       
      *** If you want help with your installation, please post your issue along with problem reporting files generated using @black.dragon74's problem reporting tool.  Google 'GENERATE PROPER PROBLEM REPORTING FILES black.dragon74' to find it. ***.  If Catalina's Read-Only protections block your installation of black.dragon74's gen_debug script, please copy the attached gen_debug script to your Desktop, change script properties with the terminal command 'chmod a+x ~/Desktop/gen_debug' and run the script from your Desktop.
       
      My system is as follows:
      Dell Latitude E6410 (I7-620m, Nvidia 3100M, 8GB DDR3, 512GB SSD, 1440x900 display, BIOS: A17) Wi-Fi: Broadcom BCM 94352HMB (replaced original Wi-Fi card) BIOS (version A17) configured as follows (leave default unless listed here): Boot Sequence: USB, Internal HDD, CD/DVD, Modular Bay HDD; Boot List Option: Legacy; Integrated NIC:Enabled; Parallel Port: Disabled; Serial Port: Disabled; SATA Operation: AHCI; Misc Devices: Enable Modular Bay, Camera, External USB, Microphone, Media Card and 1394; Latitude ON Reader: Disabled; Keyboard Illumination: Auto ALS and Input; Ambient Light Sensor: Enabled; OROM Keyboard Access: Disable; TPM Security: Disable; Computrace:Deactivate; CPU XD Support: Enable; Performance: Enable all options; Power Management: Disable Wake on AC, Disable Wake on LAN/WAN, Express Charge: Standard, Charge Behavior: Enabled; Keypad: Fn Key Only; Mouse/Touchpad: Touchpad/PS-2 Mouse; USB Emulation: Enable Legacy; Fn Key Emulation: Disabled; Fastboot: Thorough; Virtualization: Enable Intel Virtualization, Disable VT for Direct I/O, Disable Trusted Execution; Wireless Switch: Bluetooth and WLAN; Wireless Device Enable: Bluetooth and WLAN;   
      Versions of the software used in this installation are listed below the installation steps.  EFI and kexts for Catalina are attached to this first post in E6410-Catalina.zip.  CLOVER configuration is specified below the installation steps.
       
      Wi-Fi connection to an Access Point is delayed when using AppleALC for sound.  Do not use Apple ALC.  Use VoodooHDA pkg 2.9.2 v14 for sound.
       
      Steps to install Catalina on a Dell Latitude E6410 (BIOS A17, NVidia 3100m)
      Make sure that your system matches my system description above (including BIOS version, Wi-Fi card, BIOS settings) If performing an upgrade from Mojave or a previous version of Catalina, backup your Mojave or Catalina partition! (Carbon Copy or similar) Download Catalina Installer Download DosDude Catalina Patcher Use DosDude Patcher to create Catalina USB Installer Delete LegacyUSBInjector.kext (we're using @RehabMan's USBInjectAll.kext with custom SSDT) and delete SIPManager.kext (CLOVER is managing SIP) from Catalina USB Installer's /Library/Extensions folder Copy all but the FakeSMC sensor kexts in E6410-Catalina.zip (attached) LE folder to the Catalina USB Installer /Library/Extensions (copy all kexts (including FakeSMC.kext) but not the FakeSMC sensor kexts) Install CLOVER Bootloader (Legacy) on USB Installer using the EFI in the E6410-Catalina.zip (attached).  Use the CLOVER configuration specified below.  Be sure to replace the XX-MASKED-XX parameters in the attached config.plist with your own values. Reset your Latitude E6410 NVRAM by doing the following (this may be important if you're making changes to your existing EFI and won't hurt anything if you're not making any changes) turn-off your laptop remove A/C power and main battery press and hold the power button for 30 seconds restore A/C power and battery Boot your Latitude E6410 from the Catalina USB Installer that you created in steps 5-8. Select "Reinstall macOS" (note that I have existing installations of Mojave and High Sierra on my Latitude E6410, so it's possible that this menu item changes to "Install macOS" if you don't have any previous macOS installations). Select your Catalina destination partition (which will be your Mojave or previous Catalina partition if you are upgrading) After the Catalina Installer reboots the first time, boot from the "macOS Installer" partition on the disk that you selected as your Catalina destination (not the macOS installer on the USB) After the Catalina Installer reboots the second time, boot the Catalina macOS Installer on the USB Select the Post Install Patcher utility Select only the following Post Install Patches (no other patches / options) Install Patch Updater Legacy Video After the Post Install Patcher reboots,  boot from the newly installed (or upgraded) Catalina partition and complete the macOS configuration Remove these kexts (if they exist) from /Library/Extensions: LegacyUSBInjector.kext, LegacyUSBVideoSupport.kext and SIPManager.kext If you are performing a fresh installation of Catalina: Install CLOVER on your boot disk and configure EFI using files in the attached E6410-Catalina.zip.  Use the CLOVER configuration below.  Your EFI Clover/kexts/Other folder needs only FakeSMC.kext, IntelMausiEthernet.kext, USBInjectAll.kext and VoodooPS2.kext.  Be sure to replace the XX-MASKED-XX parameters in the attached config.plist with your own values. Install all kexts in the attached E6410-Catalina.zip LE folder to your /Library/Extensions folder.  NOTE: These instructions assume installation of Brcm kexts in /Library/Extensions.  Read the Brcm install instructions if you're installing kexts in EFI/Clover/kexts/Other, since your installation and at least one kext WILL BE DIFFERENT. Copy HWMonitor from the application folder in the attached E6410-Catalina.zip to your Applications folder. Install VoodooHDA (I installed using the Classic method) Skip to Step 21 If you are upgrading from a previous version of Catalina using the instructions from this thread or from Mojave that you installed using the instructions here: Update Lilu.kext and replace BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext (in /Library/Extensions) with latest BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext and BrcmPatchRAM3.kext. NOTE: These instructions assume installation of Brcm kexts in /Library/Extensions.  Read the Brcm install instructions if you're installing kexts in EFI/Clover/kexts/Other, since your installation and at least one kext WILL BE DIFFERENT. Update IntelMausiEthernet.kext Remove VoodooSDHC.kext from /Library/Extensions Re-install VoodooHDA if necessary (I installed using the Classic method) Ensure PROPER kext installation: If you're manually installing kexts in /Library/Extensions, make sure that you execute the following (in terminal) cd /Library/Extensions sudo chown -R root:wheel *.kext sudo chmod -R 755 *.kext sudo kextcache -i / After you execute 'sudo kextcache -i /' you should observe that ALL kexts are allowed.  If not, your kext directory attributes are probably incorrect.  Repeat kext installation and try again. Reboot from your new/upgraded Catalina partition Welcome to macOS Catalina! Change the keyboard type to ISO (System Preferences > Keyboard > Change Keyboard Type) Swap the Command and Option keys (System Preferences > Keyboard > Modifier Keys) Set hibernatemode: In terminal, execute sudo pmset -a hibernatemode 0 sudo rm -f /var/vm/sleepimage sudo touch /var/vm/sleepimage sudo chflags schg /var/vm/sleepimage  
      Version Info at the time of this writing:
      Catalina Installer 10.15.3 CLOVER v2.5k r5103 DosDude Catalina Patcher: v1.3.0 Lilu.kext 1.4.1 AirportBrcmFixup.kext 2.0.6 BrcmFirmwareRepo.kext 2.5.1 BrcmBluetoothInjector.kext 2.5.1 BrcmPatchRAM3.kext 2.5.1 IntelMausiEthernet.kext 2.5.0
      VoodooHDA.kext 2.9.2 v14 (NOT AppleALC)
       
      What is not working (that was working in Mojave)
      SD Card Slot (had to remove VoodooSDHC.kext which caused system freeze on wake)  
      Known Issues and Their Solutions
      (No solution yet) Brightness slider does not work in System Preferences > Displays (can control brightness with Dell brightness keys).  Working on a solution later in this thread. I continue to refine the DSDT and CLOVER config.plist to optimize my Latitude E6410 for multi-booting between various macOS versions (High Sierra, Mojave and Catalina at the time of this writing). If you upgrade your Latitude E6410 EFI using my attached EFI, you may find that your Latitude E6410 is stuck in a boot-loop that ends in a white screen and reboots.  Clear your system by doing the following: turn off your laptop, remove A/C power, remove the main battery, press and hold the power button for 30 seconds, restore A/C power and battery, boot normally.  I have only found this to be necessary (very rarely) after making an EFI change, but you may find it helpful if making kext changes in /Library/Extensions as well. (Work-around - no permanent solution yet) Cannot turn on Bluetooth after shutting-down with Bluetooth off.  Work-around is to leave Bluetooth on.  I don't use Bluetooth and don't mind, so this will likely be solved by someone else.  If you experience this issue and can't turn-on Bluetooth, I have found that putting the laptop to sleep (Fn-F1) and then waking the laptop restores proper operation of Bluetooth.  I have posted a problem description, logs and problem reporting files in this thread for help with this problem. (Solved later in this thread, but not yet added to this first post) Laptop does not sleep when closing lid.  Solution is to implement Rehabman's lid polling mechanism.  This is implemented later in this thread and the laptop sleeps when the lid closes and wakes when the lid is opened. (No solution yet) No SD Card Slot (had to remove VoodooSDHC.kext) - I read somewhere that there is a solution that does not require any kexts (just a DSDT edit).  Haven't yet implemented this fix. (Not a problem that needs to be solved - leaving for historical purposes.  I am running Catalina without this.) - IOHWControl does not load under GFX0 (as observed in IORegistryExplorer).  Solution (if it needs to be solved) is to install AppleHWSensor.kext from a DosDude-patched Mojave /S/L/E in Catalina's /L/E.  Copy and install your own or use the kext attached to this post. (Solved - no further work required) Wi-Fi connection is delayed until a minute or so after boot - Use VoodooHDA and NOT AppleALC (Solved - no further work required) External USB ports do not work after waking from sleep (S3) - Upgrade Lilu.kext and replace BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext (in /L/E) with latest BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext and BrcmPatchRAM3.kext. (Solved - no further work required) Boot and shut-down time of Catalina is slower than Mojave - Upgrade Lilu.kext and replace BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext (in /L/E) with latest BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext and BrcmPatchRAM3.kext. (Solved - no further work required) Wi-Fi is not immediately available at OS startup - Upgrade Lilu.kext and replace BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext (in /L/E) with latest BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext and BrcmPatchRAM3.kext. (Solved - no further work required) Laptop freezes on wake - Remove VoodooSDHC.kext from /Library/Extensions  
      Tips for Improved Performance (on this and other older systems)
      System Preferences > Spotlight > Search Results: Uncheck all options System Preferences > Spotlight > Privacy: Add all Volumes System Preferences > Accessibility > Display: Check "Reduce motion" System Preferences > Accessibility > Display: Check "Reduce transparency"  
      Other tips
      If your fan is always running and temps are good, try pressing Fn + z (I haven't noticed this issue for a while since I completed DSDT edits for Mojave, but keeping this here for historical purposes)  
      CLOVER Installation: Use these configuration options
      Install Clover in the ESP Boot Sectors Install boot0af in MBR Clover for BIOS (legacy) booting Clover EFI 64-bits SATA BIOS Drivers, 64-bit Recommended drivers FSInject File System drivers ApfsDriverLoader Install RC scripts on target volume Themes Choose your desired theme Install Clover Preference Pane After clicking "Continue", if prompted with "This Clover package is incompatible with this version of macOS," install anyway  
      After CLOVER installation is complete Copy the following from the attached E6410-Catalina.zip ACPI patched contents config.plist (change XX-MASKED-XX values to your own) kexts/Other (remove all other kext folders) Remove christmas and new year folders from themes (if present)  
      Credits
      Thanks to those who contributed to my Mojave solution and to the DosDude team (for the incredible macOS patchers), I think this Catalina installation was the easiest macOS installation that I have experienced (so far).  Many thanks to @Slice and his team for the incredible work on CLOVER and for continuing to support old legacy systems like this.  Also, thanks to @Mieze and @headkaze and others I'm sure for maintaining the Brcm kexts.  And finally, I still prefer to manually apply patches to the DSDTs in my systems.  CLOVER offers extensive patching functionality, but I'm old-school and like to have an error-free, fully-patched DSDT with a simple CLOVER config.plist.  I think that this manual DSDT patching approach (which required an extensive review and debugging of the original unpatched DSDT in this thread) is the reason that this Latitude E6410 is such a perfect MacBookPro6,2.  Thank you @RehabMan for being a great teacher and for always insisting on problem reporting files .
       
       

      AppleHWSensor.kext.zip

      gen_debug
      E6410-Catalina-3v3.zip
    • By tlac
      Simple steps to create macOS Installer for Vmware on Linux or Windows
       
      This guide describes how you can create a Vmware image (vmdk) for installing macOS in Vmware. Most tutorials about this topic require an ISO installer file that was typically created in macOS or you have to download some preinstalled image file from unknown source. None of them are ideal. But if you follow the steps below, you will not need to access macOS and will use official and trustful sources.
       
      First of all download gibMacOS from here and set up
      https://github.com/corpnewt/gibMacOS
        Run the script to download the full macOS installer:
      on Linux: gibMacOS.command on Windows: gibMacOS.bat  
      Install qemu-img converter

      on Linux (Debian or Ubuntu):
      install qemu-tools package

      on Windows use this installer:
      https://qemu.weilnetz.de/w64/
      when you run the installer, it is enough to select the "tools" and "dll library".
       
      Convert the downloaded BaseSystem.dmg to Vmware image
      run the following commmand in that directory where BaseSystem.dmg was downloaded (somewhere here: gibMacOS-master/macOS Downloads/publicrelease/061-44387 - 10.15.3 macOS Catalina)
      on Linux:
      qemu-img convert -O vmdk -o compat6 BaseSystem.dmg recovery.vmdk on Windows:
      c:\"Program Files"\qemu\qemu-img convert -O vmdk -o compat6 BaseSystem.dmg recovery.vmdk  
      Use the previously created image to install macOS in Vmware
       
      I assume you have a patched and working Vmware already. If not, find another guide but in nutshell:
      - confirm the VT-x is supported on your Intel machine (if you are on AMD you may not able to virtualize macOS or you need to do more work)
      - install VMware Workstation or VMware Workstation Player (free for non-commercial use)
      - use an unlocker to patch the Vmware to support macOS guest
       currently this works well: https://github.com/BDisp/unlocker/
       
      So when you are here you have a patched Vmware and a Vmware image (recovery.vmdk).
      Run Vmware and create a new virtual machine by choosing macOS guest. But add another hard disk as well with selecting to use an existing virtual disk. Browse the recovery.vmdk. You will get a warning about the image is not in the latest format but choose to keep the existing format.
      After you installed the macOS, install the vmware tools as well.
       
      Tested on Windows 10 with macOS Catalina 10.15.3 in Vmware 15.5 Player
       
      Comments are welcomed.
       
    • By tonyx86
      *** I have started another thread for installing Catalina on the Dell Latitude E6410.  If you were thinking of installing Mojave, but would prefer to skip right to Catalina, click here. ***
       
      I was inspired by @duduclx post here for installing El Capitan on a Dell Latitude E6410, so I decided to install Mojave 10.14.5 and subsequently 10.14.6.  Everything works perfectly (including sleep).  I'm starting this thread hoping to help others install Mojave on their E6410s.  A brief installation guide is provided later in this first post.  The interested reader is encouraged to read the other posts in this thread to see how this solution evolved and to learn additional tips/details not provided in this first post (including dual-booting with macOS and Windows).
       
      My system is as follows:
      Dell Latitude E6410 (I7-620m, Nvidia 3100M, 8GB DDR3, 512GB SSD, 1440x900 display, BIOS: A17) MacOS: Mojave 10.14.6 (APFS) (Patched with DosDude Mojave Patcher 1.3.3) MacModel: MacBookPro 6,2 (LPCB._DSM.Name "pci8086,3b09") Kexts: Lilu 1.3.6, VoodooHDA 2.9.2, AirportBrcmFixup 2.0.0, IntelMausiEthernet 2.4.1d1, ACPIBatteryManager 1.90.1, BrcmPatchRam2.kext, BrcmFirmwareRepo.kext, VoodooPS2Controller (the "Refined ALPS Touchpad" version - release 6 developed by @Dr. Hurt and compiled by @bronxteck), not the original version), USBInjectAll (with custom SSDT-UIAC), VoodooSDHC.kext (configured as shown here). Wi-Fi: Broadcom BCM 94352HMB (with AirportBrcmFixup.kext) CLOVER (Legacy): R4961  
      Configuration items that may be different from what you have seen in other E6410 configurations
      Addition of _OFF and _ON methods to _PTS and _WAK methods respectively (to control discrete graphics in order to enable sleep/wake) LPCB._DSM patched with device-id "3b09" AND "name", "pci8086,3b09" for native Nehalem power management with MacBookPro 6,2 ECDV renamed to EC so that AppleBusPowerController loads AGP.VID._DSM patched with device-id "0a29" so that AppleGraphicsPowerManagement loads No CLOVER Generate P or Generate C States (with the correct LPCB._DSM and MacBookPro 6,2, these CLOVER options are unnecessary for this architecture and only limit max multiplier and reduce number of P states) DSDT patched to include HDAU device (device-id 0x0be3)  
      What is NOT working:
      Display brightness can be controlled with keyboard keys, but cannot be controlled with slider in Display settings. Graphics Power Management - AGPM loads (because 10de,0a29 device is injected), but there's no evidence that 3100m frequency and voltage is changing.
        What is NOT tested:
      Smartcard Reader eSata (I have this disabled in my BIOS) Firewire Port (it does appear in the Network settings, just haven't tried it) Microphone Jack PC Card Slot (I have this disabled in my BIOS)  
      What IS working:
      SLEEP IS WORKING! Everything else not mentioned above.   Speedstep/CPUPowerManagement is perfect, system temps are low, CPU multiplier operates as expected, battery life is long Shutdown is fast Display/graphics acceleration is perfect (thanks to DosDude's Mojave patcher) Brightness (adjusted with brightness keys on keyboard) works perfectly Battery Manager works (battery status is displayed in menu bar) simply by installing ACPIBatterManager.kext. Wi-Fi (after changing to Broadcom BCM94352HMB and installing AirportBrcmFixup.kext) Audio (volume adjustable, volume indicator appears in menu bar).  Switched to VoodooHDA from AppleALC after AppleALC caused slow boot due to "IOHDACodecFunction timeout." Ethernet port (with IntelMausiEthernet.kext) Broadcom BCM20702A0 Bluetooth (with BrcmPatchRam2.kext and BrcmFirmwareRepo.kext) Optical Drive External VGA (with corrected NVCAP.  Need NVCAP 04000000 00000100 0E000000 00000007 00000000 (credit: here) for working external VGA display. Headphone jack Display Port (tested using DP > HDMI adapter) Camera SD Card Reader  
      Known issues and their solutions (These issues have all been resolved, with the solutions incorporated into the attached config files.  The issues are listed here for historical purposes and no further work is needed unless stated otherwise).
      Leaving this for historical purposes, but the CLOVER USBFix is no longer necessary after finding that I had incorrectly applied the DSDT _DSM patch for Device (EHC1).  The CLOVER USBFix is not needed after fixing the DSDT..  AAPL,clock-id and device_type do not appear in IORegistry for EHC1.  Solution is to use CLOVER on-the-fly patching/fixing/renaming for EHC1 and EHC2.  Thank you, @feartech, for this tip. ALPS trackpad performance is not good with the "standard" VoodooPS2Controller.kext that I initially used.  Switching to the "Refined ALPS TouchPad driver" is a big improvement.  I've implemented and tested this on my system.  The ALPS version of VoodooPS2Controller.kext mixes up a few keys.  Need to switch the Command and Option keys (System Preferences > Keyboard > Modifier Keys) and change keyboard type to ISO European. This configuration (captured in the attached config files) uses an injected device-id (10de,0a29) for NVidia 3100m to get AGPM to load.  While I haven't observed any performance differences, a better approach may be to inject AGPM properties for device 10de,0a6c (the actual device-id for the 3100m).  This AGPM method is discussed later in this thread.  I have briefly tested this "FakeSMC.kext method" for injecting AGPM attributes without any noticeable changes in laptop/graphics behavior. IOHWControl is not loaded under AGPM (Should be AGP > VID > NVDA,Display-A@0 > NVDATesla > AGPM > gpu-control > IOHWControl as viewed in IORegistryExplorer).  It is loaded on a real MacBookPro6,2 running Mojave and is loaded on this Dell Latitude E6410 running High Sierra.  If I "Inject NVidia" via CLOVER, IOHWControl loads properly. The Dell Latitude DSDT (BIOS A17) has a bug in Method (GNOT).  In the method, the expression  If (LOr (LGreater (OSYS, 0x07D0), LLess (OSYS, 0x07D6))) always evaluates to TRUE, so the patched DSDT has no dependency on the value of OSYS.  I suspect that LOr should be replaced with LAnd, so that this expression is TRUE for variants of Windows 2001 and False for any other OS.  While this may have no affect on MacOS, it makes one wonder how such an obvious bug made it through Dell QA and is still present in BIOS A17.  Also makes one wonder whether the sleep problem (which no one has solved) was fixed in Windows to address another DSDT bug. The assigned value of ACOS and OSYS in the DSDT are conditional on the operating system.  There is no condition for "Darwin."  The solution is to add a condition for "Darwin" (making it equivalent to one of the defined operating systems (e.g. Linux, Win7, etc).  The attached config hard-codes ACOS and OSYS values equivalent to those for Linux.  Another way to handle this (different from the method employed in the attached config files) might be to override _OSI with XOSI (defined in a custom SSDT). The portType of the Internal Bluetooth device is portType=0 which, according to Rehabman's comments in SSDT-UIAC-All.dsl, is an external USB 2 port.  This should be an internal USB port (portType=2).  I learned through trial and error that the HUB1 and HUB2 definitions in Rehabman's SSDT-UIAC-ALL.dsl apply to the ports on the EHCx USB hubs.  The solution is to include the HUB1 definition in SSDT-UIAC.dsl and change portType to 2 for HP15.  This change doesn't appear to affect/fix sleep, but it may prevent instant wake if we get sleep working. There are minor differences between a real MacBookPro6,2 IORegistry dump and this HackBookPro6,2 IORegistry dump that can be resolved with simple DSDT edits.  I am now running with these changes, but haven't found these changes to make any difference in operational behavior.
      Rename Device (AC) -> Device (ADP1) Remove UID from Device (HPET) Add compatible ID "PNP0C01" to Device (HPET) Change ADP1:_STA from 0x0F to 0xFFFFFFFF Enable Ambient Light Sensor and renamed to Device (ALS0) from Device (ALS) Add compatible ID "smc-als" to ALS0 Rename LID -> LID0 Change "name" definitions to Buffers in _DSM methods Rename Device (PBTN) to PWRB Rename Device (SBTN) to (SLPB) Change HDAU.hda-gfx from "onboard-1" to "onboard-2" Change GFX0.hda-gfx from "onboard-1" to "onboard-2" Sleep / Wake does not work with the basic DSDT edits.  I have discovered that Sleep / Wake can be made to work by adding discrete graphics _OFF and _ON methods to _PTS and _WAK methods respectively (borrowed the concept and code from a working E6430 DSDT: Credit here: https://osxlatitude.com/forums/topic/9248-working-sleep-on-intel-hd-and-nvidia-nvs-on-dell-latitude-e6430-optimus-enabled-or-disabled/page/6/. The Clover boot arg should be changed to "darkwake=0" for reasons explained by @holyfield in this thread.  Leaving this for historical purposes: LCD screen is blank when waking laptop by opening lid (screen is not blank when waking with power button).  Solution is to add darkwake=8 to CLOVER boot args.  Thank you @Hervé for this tip.  
      Brief Installation Guide:
      Configure BIOS (version A17) as follows (leave default unless listed here): Boot Sequence: USB, Internal HDD, CD/DVD, Modular Bay HDD; Boot List Option: Legacy; Integrated NIC: Enabled; Parallel Port: Disabled; Serial Port: Disabled; SATA Operation: AHCI; Misc Devices: Enable Modular Bay, Camera, External USB, Microphone, Media Card and 1394; Latitude ON Reader: Disabled; Keyboard Illumination: Auto ALS and Input; Ambient Light Sensor: Enabled; OROM Keyboard Access: Disable; TPM Security: Disable; Computrace: Deactivate; CPU XD Support: Enable; Performance: Enable all options; Power Management: Disable Wake on AC, Disable Wake on LAN/WAN, Express Charge: Standard, Charge Behavior: Enabled; Keypad: Fn Key Only; Mouse/Touchpad: Touchpad/PS-2 Mouse; USB Emulation: Enable Legacy; Fn Key Emulation: Disabled; Fastboot: Thorough; Virtualization: Enable Intel Virtualization, Disable VT for Direct I/O, Disable Trusted Execution; Wireless Switch: Bluetooth and WLAN; Wireless Device Enable: Bluetooth and WLAN;  Create your MacOS installer USB (Use DosDude's Mojave Patcher for Mojave) (start with High Sierra and not Mojave if you're new to hackintosh). Install CLOVER (Legacy) on installer USB using attached EFI as your guide for patched ACPI, kexts and config.plist Install MacOS to your SSD.  When you run DosDude's Mojave Patcher, DO NOT install LegacyUSBInjector.kext - you're going to use Rehabman's USBInjectAll.kext.  Also, do not install the DosDude SIP kext (you're using CLOVER to manage SIP). Install the following kexts in /Library/Extensions:  ACPIBatteryManager.kext, AirportBrcmFixup.kext, BrcmFirmwareRepo.kext, BrcmPatchRAM2.kext, FakeSMC.kext, FakeSMC_ACPISensors.kext, FakeSMC_CPUSensors.kext, FakeSMC_GPUSensors.kext, FakeSMC_LPCSensors.kext, IntelMausiEthernet.kext, Lilu.kext, USBInjectAll.kext, VoodooPS2Controller.kext (the "Refined ALPS Touchpad driver," not the original), VoodooSDHC.kext (configured as shown here). Switch Command and Option keys to compensate for Refined ALPS driver issue (System Preferences > Keyboard > Modifier Keys).  Also change keyboard type to ISO European to fix the [ ` ~ ] key (to the left of the "1" (one) key. Install VoodooHDA Install HWMonitor application  
      Tips for Improved Performance (on this and other older systems)
      System Preferences > Spotlight > Search Results: Uncheck all options System Preferences > Spotlight > Privacy: Add all Volumes System Preferences > Accessibility > Display: Check "Reduce motion" System Preferences > Accessibility > Display: Check "Reduce transparency"  
      Other tips
      If your fan is always running and temps are good, try pressing Fn + z After applying Mojave updates, HWMonitor may not display discrete graphics attributes.  On systems with multiple displays, a second (or third display) may not be active after applying the Mojave update.  The solution to this is to run "sudo kextcache -i /" (in a terminal window) and reboot.  This will usually fix the issue.  If the issue is not fixed, run DosDude's Post Install Utility, apply the Legacy Graphics Patch, reboot and then run "sudo kextcache -i /" if necessary.  
      Credits
      In addition to those mentioned in this first post and in subsequent posts in this thread, much of this solution for the Latitude E6410 was made possible by the numerous contributions of @RehabMan.  I hope he's doing well, wherever he is.  Hopefully he has long since forgotten what a PIA I was (and still am) as I was (and still am) learning hackOS.  
       
       


      E6410-Mojave-6v2.zip
    • By kushwavez
      A really good motherboard with macOS compatible bult-in Wifi & Bluetooth

      ASUS Z170-Deluxe (with Wifi)
      BIOS: v3801
      CPU: i7-6700K 4.0 to 4.2 GHz (w/o OC)
      RAM: 1x 16 GB Corsair DDR4 2400 MHz
      GPU: Intel HD 530 (Headless) & ASUS Radeon RX 5700 OC 8 GB
      Audio: ALC 1150
      Ethernet: I219V2, I211-AT
      WiFi & Bluetooth: Broadcom BCM94360HMB Half-Mini-PCI-E
      More Specs: https://www.asus.com/Motherboards/Z170-DELUXE/specifications/
       
      Catalina 10.15.3 - Windows 10
      What is working:
      BCM94360HMB Wifi and Bluetooth AirDrop, Handoff, FaceTime, Messages, App Store, iCloud, etc. Intel HD 530 (QE/CI tested, but now I'm using it in headless) Sleep RX 5700 (QE/CI with 2 1080p monitors connected) Sound USB Ports Two Ethernet ports macOS with a light OC (4.12 GHz - 4.5 Ghz, XMP, ASUS optimal) No problem so far ASUS HyperKit with a KINGSTON NVMe SSD - 250 GB  
      What is not working:
      -  
       
      Not tested:
      VideoProc says that Hardware Decoding\Encoding is fully supported and enabled on both HD 530 and RX 5700 but I didn't test it Thunderbolt (no equipment)  
      Issues:
      None  
      BIOS Settings:
      Boot\CSM (Compatibility Support Module): Launch CSM: Disabled Boot\Secure Boot: OS type: Other OS Secure Boot State: Disabled Advanced\System agent (sa) Configuration: VT-d: Enabled Graphics Configuration: Primary Display: Auto iGPU Multi-monitor: Enabled RC6(Render Standby): Enabled DVMT Pre-Allocated: 128M Advanced\PCH Storage Configuration: SATA Mode Selection: AHCI HyperKit: Enable (if you have NVMe SSD with ASUS HyperKit) Advanced\CPU Configuration: Intel Virtualization Technology: Enabled CPU- Power Management Control: Intel SpeedStep: Enabled CPU- C-States: Enabled Intel SpeedShift: Enabled  
      Getting ready for installation:
      Download the bootpack (Clover v5098): Click here -> ASUS-Z170_catalina.zip  
      Installation:
      Create an installer with any method you know (- Mac: createinstallmedia - Windows: Transmac, Vmware, Win32diskimager) Copy my Clover folder to the USB's EFI folder Boot with the Installer USB If you have any problem (kp or freeze) boot with config_debug.plist to see what causes the issue  
      Post Installation:
      Download Clover Configurator and generate a new Serial Number for yourself  
      Some pictures:
       

       




       
       
       
      Catalina & Windows 10 Dual-Boot (clean install, on one drive):
       Boot into your Mac installer, Create 2 partitions in GUID table (1 for Win (I used FAT32 but I think it doesn't matter what you choose), 1 for Mac)
       Install Mac, boot with your USB, mount your EFI partition (use terminal or an EFI mounter app), create an EFI folder (if there is no folder), copy the CLOVER folder I attached to the EFI folder, restart
      Boot into your Win installer, Format the partition you created for Win, install. 
      Now, it's automatically booting into Windows. To use Clover open cmd in administrator, type: 
      bcdedit /set {bootmgr} path \EFI\CLOVER\CLOVERX64.efi  
      You're done! It will booting into Clover when you start the system, and you can select Win or Mac (or another OS if installed on a 3rd partition).
       
      IF YOU GETTING ERRORS DURING WINDOWS INSTALLATION (could not be formatted, etc):
      Make sure you have GPT partitions, and GPT (UEFI) installer, also disconnect all external storage drives (except the installer USB)  
      Mounting EFI from Windows:
      Open cmd in administrator mode and type: mountvol b: /s (This will mount your EFI) Open Total Commander or Explorer++ in administrator mode to manage EFI mountvol b: /d (This will unmount your EFI)  
      Notes:
       
      2020.02.11: Updated to 10.15.3 -> No problem when/after installing
      2020.01.19: Added ASUS HyperKit NVMe SSD to the "What is working" list
      2020.01.12: Tested system with OC, added more informations to BIOS settings
      2020.01.11: Added SmallTreeIntel82576.kext for 2nd Ethernet, Tested Ethernet ports
      2020.01.11: First upload
       
×