Discord: Rules. No profanity: Keep it clean. No torrent links or P2P of copyrighted material: We want to avoid legal trouble, so please don't share links like this in posts or comments. Flair your posts: Please make sure to flair your posts by clicking the 'flair' button below the post. Questions Must Have Adequate Information: At a minimum, you must provide your Motherboard Model, CPU, and GPU.
RAM/HDD/SSD/Monitor/Accessories are usually not the cause of issues (though you may provide them anyway). We reserve the right to remove posts that don't meet the minimum criteria. If you are asking about a Laptop, you must provide the full model number. Search Before Posting: If your question has already been posted before (even if not by you), please make sure to read the other post before posting. In the event it doesn't answer your question/problem, please link prior post you read and then ask about what you don't understand.
Browse Categories: What is a Hackintosh? A Hackintosh is a non-Apple computer that runs Mac OS X. AMD USERS READ THIS: Though technically permitted, the general consensus on Hackintoshes with AMD CPUs is that they're more trouble than they're worth. We probably won't be able to help with any AMD-related issues. OS X INSTALLERS NOTE: This sub is dedicated to legally obtained copies of OS X.
Please do not ask, or post, about things like iAtkos, Niresh, or any other modified OS X installer that may have malicious code in it! Check out the brand-new (currently outdated - pending updates) Make sure you post your Hackintosh's specifications when you ask questions. How to install macOS on a PC. Post-installation Guides. Check if your computer is compatible with Mac OS X.
Reinserted after installation using kext utility. With graphics enabler=yes. Will it work with Radeon 6470M? Or maybe 7400M? Thanks for the future reply.
Informative threads homegrown here from. posted by Additional Hackintoshing resources. Related subreddits:. I just got my first Hackintosh up and running. Here are my specs:.
Gigabyte GA-Z97N-WIFI. Intel i7-4790k. Zotac GeForce GTX 970 I got El Capitan (10.11.0) installed easily by following and I got the Nvidia web drivers installed, so the GPU is working nicely. Now I want to get the audio, wifi and bluetooth working.
I bought and swapped out a PCIe Half Mini board (BCM94352) that I should be able to get working based on, but I can't for the life of me figure out how to install the necessary kexts. Sorry for the stupid question, but can anyone help a noob out? I tried using the search function and searching other Hackintosh forums and google, but for some reason I can't find the answer to this simple question. I'm not sure what information would be useful for troubleshooting, but let me know and I'll provide whatever you need. Thanks in advance!
There are several utilities that will help you, Multibeast because a lot of the kexts are included probably being the easiest. However, with ease of use comes the price of not really understanding what is going on and not being able to chose specifically the kext, install location, or version you're installing.
Installing kexts manually is very easy. Plus this way you'll be able to put the kexts where you want. Most of the utilities just put kexts in S/L/E (System/Library/Extensions) but often texts there do not survive OS updates. Same for L/E (Library/Extensions). With Clover the easiest way to install kexts is in the EFI partition at /EFI/Clover/Kexts/Other.
Operating system specific kexts put in the 10.XX folder that corresponds to your OS. This way the bootloader will inject the kext during startup. Just mount the EFI partition of your boot drive and drag the kexts to the corresponding folders using finder. Terminal is easy to use too: To install in S/L/E get the kext you would like to install open terminal and type: sudo chmod -R 755 /PATH/TO/XXXXXX.kext sudo chown -R root:wheel /PATH/TO/XXXXXX.kext sudo cp -r -v /PATH/TO/XXXXXX.kext /System/Library/Extensions/ then rebuild cache: sudo rm -rf /System/Library/Caches/com.apple.kext.caches/Startup/. You should rebuild your permissions after that and since 10.11 you have to use a utility for that. I find KCMP Utility Pro works very nicely.
Insanelyrepairpermissions is a command line utility you can use to rebuild permissions too. Good hacking! Same for L/E (Library/Extensions). The ones there will survive minor upgrades at least.
They are supposed to, it's the location where third party tools that require kexts to work install them (such as Paragon NTFS 14). You should rebuild your permissions after that and since 10.11 you have to use a utility for that. You don't, actually. You just have to run kextcache -system-prelinked-kernel and kextcache -system-caches after setting the right permissions with the commands you've mentioned above.:). Hey do you the differences between the install locations, like S/L/E v L/E That's a good question, I'm not entirely sure if my answer is correct so don't quote me on this.:P From what I understand, S/L/E should be reserved for system kernel extensions (the ones that come with a vanilla installation) while /L/E is where third party apps are supposed to install the ones they need.
However a vanilla installation does have some in /L/E and I'm not entirely sure why that is. What does it mean to inject a kext? If I'm not mistaken, it's when you put the kexts into the EFI partition.
OS X won't load kexts outside S/L/E and /L/E, instead Clover forces it to load them anyway. How it does that I have no idea, but it's 'injecting' them into the system. Clover's the needle, the system is your arm, kexts are the vaccine:P what's the difference between injecting and putting kexts in S/L/E or L/E? Mostly preference IMHO, but there are advantages to one method over the others (again, don't quote me). Kexts in the EFI partition (the ones that are injected) will survive system updates and clean installs. They never go away.
Kexts in S/L/E may ( will?) be gone with minor system updates. At least mine did. Kexts in L/E should be left untouched during system updates. Mine survived just fine from 10.11 to 10.11.1 for example.
Personally, as a rule of thumb, I try my best to do it this way:. I do not touch S/L/E. Dummy kexts I put them into /L/E, since they don't seem to work when I tried to put them into the EFI partition. Required kexts (not dummy ones), I put them into the EFI partition and let Clover inject them into the system.
Currently I think I only have FakeSMC and VoodooPS2 there, which conveniently let me boot vanilla USB installation drives created by hand. Any kext bin patches I may need, I have set them up in Clover. At the moment I just need AppleHDA patched, so I have Clover configured to do it. Hey do you the differences between the install locations, like S/L/E v L/E That's a good question, I'm not entirely sure if my answer is correct so don't quote me on this.:P From what I understand, S/L/E should be reserved for system kernel extensions (the ones that come with a vanilla installation) while /L/E is where third party apps are supposed to install the ones they need. However a vanilla installation does have some in /L/E and I'm not entirely sure why that is. What does it mean to inject a kext?
If I'm not mistaken, it's when you put the kexts into the EFI partition. OS X won't load kexts outside S/L/E and /L/E, instead Clover forces it to load them anyway. How it does that I have no idea, but it's 'injecting' them into the system. Clover's the needle, the system is your arm, kexts are the vaccine:P what's the difference between injecting and putting kexts in S/L/E or L/E? Mostly preference IMHO, but there are advantages to one method over the others (again, don't quote me). Kexts in the EFI partition (the ones that are injected) will survive system updates and clean installs. They never go away.
Kexts in S/L/E may ( will?) be gone with minor system updates. At least mine did.
Kexts in L/E should be left untouched during system updates. Mine survived just fine from 10.11 to 10.11.1 for example. Personally, as a rule of thumb, I try my best to do it this way:. I do not touch S/L/E. Dummy kexts I put them into /L/E, since they don't seem to work when I tried to put them into the EFI partition.
Required kexts (not dummy ones), I put them into the EFI partition and let Clover inject them into the system. Currently I think I only have FakeSMC and VoodooPS2 there, which conveniently let me boot vanilla USB installation drives created by hand. Any kext bin patches I may need, I have set them up in Clover. At the moment I just need AppleHDA patched, so I have Clover configured to do it.Surinami. EFI/Clover/Kexts/Other was recently adopted by Clover as the default for cross OS kexts; any kext that is OS independent can go in there and clover will inject it every boot.
Some users have multiple versions of OS X and they have system dependent kexts that go in the corresponding folder and are injected whenever that particular OS is booted. If you inject a kext via clover I don't think (emphasis on think) you need to worry about permissions (ie those terminal commands we provided) but they certainly can not hurt. I guess one disadvantage is that the EFI partition is limited in size and say you need many kexts and have several OS versions you're booting, maybe you could run out of space on the EFI partition. So in that case it would be necessary to move kexts to S/L/E or L/E. But that would take lots of kexts (and maybe some EFI backups). I don't know what tool people are using nowadays, but to get you going, you can do it 'by hand' with no tools.
Assuming you'd like to install them to /System/Library/Extensions/, you can simply copy them there (El Capitan will complain, ignore it) and then run these two commands in the terminal to fix permissions: sudo chmod -R 755 /System/Library/Extensions/. sudo chown -R root:wheel /System/Library/Extensions/.
And then you run these two to rebuild the cache/prelinked kernel and make sure they get loaded during the next boot: sudo kextcache -system-prelinked-kernel sudo kextcache -system-caches Then reboot. Ok, I was trying to use Clover/Clover Configurator, but I have seen a lot of people putting the files directly in S/L/E. I guess I just missed the command line stuff somehow. When I follow your instructions, I get the following output for the -system-prelinked-kernel command: kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC.kext and a couple other similar outputs.
Is that cause for concern and if so, is there a way to fix it? Is there a way to tell which kexts are loading? I'm currently trying to get my wifi working by installing RehabMan's FakePCIIDBCM94352ZasBCM94360CS2.kext, but I don't know if wifi will just start working (show up in the upper right corner), or if there are further steps. I'm a bit confused by the tonymac guide I referenced above. Those invalid signature warnings are totally fine and expected.
![Radeon 6470m Kext Helper Radeon 6470m Kext Helper](https://matthieu.yiptong.ca/wp-content/uploads/2017/04/img_1860.jpg)
It just means those kernel extensions don't have a valid developer signature, but as the warning said, the system will allow them. You'll get those warnings for (not signed) third party kexts or if you modify system ones.
![Radeon 6470m Kext Helper Radeon 6470m Kext Helper](http://i.imgur.com/TPQiGsp.png)
If you get any other then it'd be a good idea to re-run those last two commands again, just to be sure. By the way, regular kexts (not dummy kexts or kexts intended to replace system ones) you can put them into your EFI partition the way mentioned below. It'll probably be safer too, but don't worry about that until you get your stuff working. Is there a way to tell which kexts are loading?
Type kextstatin the terminal, it'll get you a list of loaded texts. Alternatively you can click the Apple icon on the top left of the desktop, then About This Mac, then the System Report. On the window that opens you'll have 'Extensions' on the sidebar, click on it and wait a couple seconds. It'll show you a list of all the kexts and you can click on them to find extra information, such as if they are 'Loadable'. I'm not sure how reliable this one is though. I'm currently trying to get my wifi working by installing RehabMan's FakePCIIDBCM94352ZasBCM94360CS2.kext, but I don't know if wifi will just start working (show up in the upper right corner), or if there are further steps.
That one I'm not sure. For hardware of mine that needed kexts, it did 'just' start working, yes. You may need to modify your DSDT or inject something with Clover, but I can't help you there.
Running Clover? I have some advice. Please please. Don't install any hack-related kexts into /S/L/E/ anymore. Don't let multibeast do it either. Inject them with Clover's inject function and keep them in the kexts/10.11 folder. Pretty much designed so you don't have to worry about /E/ permissions or the kext cache; design intent with the boot loader.
Even patches to kext can be made with settings in the bootloader. Goal is to get things setup so you can run a vanilla / unchanged copy of the OS.
Another reason not to use a utility is that sometimes the utilities change things they have no need to change. I was using Kext Utility (yes that's the very creative name given to this app) to install kexts and I noticed that I couldn't mount my EFI partition.
At the time I didn't know it was Kext Utility causing the issue by messing with another unrelated kext. I ended up freaking out and reinstalling my OS and then it happened again when I unknowingly installed a new kext with it. Fortunately someone on insanelymac.com responded to my thread and I was able to restore a kext from the installer.
Since then I've installed kexts manually.