Intel Gigabit CT kext for macOS Sierra 10.12

macos-sierraThe Intel Gigabit CT Desktop ethernet PCI adapter is still one of the fastest and most robust NICs for the Hackintosh. This did not change with macOS Sierra 10.12. I’m still using the IONetworkingFamilyInjector.kext in Clover’s kext folder to override the compatibility list in Apple’s own Intel82574L.kext. However, while the installation of macOS Sierra went smoothly, I lost all network connectivity after installing Sierra. A quick look at the network kernel extensions revealed that Apple changed the driver identifier of the Intel82574L.kext, rendering the injector useless. After changing the identifier in the injector and a reboot, network connectivity was back again.

The patched injector kext is available for download here: The kext injector has to be placed into the EFI/CLOVER/kexts/10.12 folder.

intel gigabit desktop ct

The Hackintosh is still running in full protected mode (if enabled in Clover):
$ csrutil status
System Integrity Protection status: enabled.

A permanent solution?

While writing this post, I stumbled upon an alternative solution, which seems to be permanent. However, it requires flashing the Intel NIC and changing it’s device ID property. Check out this post on InsanelyMac. I’m going to try this approach in the near future since it would reduce the number of kexts in my Hackintosh rig to just one (only FakeSMC).

12 replies on “Intel Gigabit CT kext for macOS Sierra 10.12”

  1. Hi Jan

    Thanks to your original article on using the CT, I’ve been running one in my system too, and will shortly try the EFI-ROM/device ID flash, as I too like the idea of avoiding 3rd party kexts where possible.

    But on that subject, can you please tell me how USB3 is working on your system? I too have a Z97-based system (Z97 SOC Force in my case – literally!) but only solutions for fully working USB3 seem to involve extra kexts (I don’t have the knowledge to know how to fix it via editing DSDT) – so I’m just curious how you handle it on your system.

    Thanks for your time, Jeremy

    1. Jeremy, I didn’t have to add any kexts for my board to get USB 3.0 working. I works OOTB. Luckily, because I don’t understand ASL at all.


      1. Thanks for your reply, Jan – I shall try a clean install without an USB3 kexts and see how I get on! Cheers, Jeremy

      2. Sorry to trouble you again, but I wondered what system definition you’re using in Clover with Sierra? Is it still 14,2?

        1. Yes, that’s exactly what I use in Sierra. I also drop the Cpu0Ist and CpuPm tables and use ssdtPRGen generated tables instead but other than that, it’s prett y much all default settings.


        2. Hey I just looked at the USB 3 ports in more detail and it looks like the operate with USB 2 speeds as reported in System Information.


        3. hi Jan.
          thanks for the updates; I may try running vanilla and just adding a FL1100-chipped PCIe card for USB3 – they’re said to work OOB and much less hassle than messing with kexts.
          PS, just flashed my CT and it’s working great, so thanks for the info on that!

        4. PPS, I believe system info will only report that the port is USB3 if there’s something USB3 plugged into it.

  2. Hi,Jan
    I have posted in the previous hackintosh NIC article,which find out marvell 88e8050 didn’t work,after finding sometime digging internet and buying multiple cards(i have a same goal as you), finally i got a nic working out of box,which based on 88E8053,but maybe there’s problem acquiring this card outside ASIA since its only manufactured in taiwan, if VERY lucky enough maybe you could get one.
    before get this card i have though buying that intel nic,but i given up because after installed UEFI based os,i can’t change the UEFI setting to bios compatible mode,which means dos cannot be booted.
    And i would like to mention it is possible to achieve ZERO kext,if you’re using Gigabyte motherboard, you can install ozmosis,which allowing changing motherboard’s smbios info, eliminating the need of fakesmc

    1. Frisa, I’m not sure what that UEFI problem is about. However, this Intel NIC can be flashed to UEFI mode, if this is something that would help in your situation.
      I just flashed mine with the EFI-ROM and changed the device ID property. Works like a charm. No more network kexts for me :-) This adapter will work in macOS as long as Apple continues to support it.


Comments are closed.