#ETHERNET MAC CONTROLLER FOR PROCESSOR WINDOWS#

I am wondering if there is a way to use this alternative path (_SB.05) in a custom SSDT, to trick the system to thinking your i255-v is an i255-LM port. I have been looking at the other PCIe Device files you provided and the pcidevices.dsl shows a different setup for the i255-V Ethernet port:Д®xternal (_SB_.05, DeviceObj)Дevice (_SB.05) // IOReg ACPI path Or trying to inject it with OpenCore from the /OC/Kexts folder, with the appropriate ist edit. I would expect that editing the kext to include the device id for your i255-V port would lead to a kernel panic, even after a permission repair and kernel cache rebuild. Given the way Apple have locked down the system, needing to mount the macOS drive in read-write mode etc. This kext contains the IOPCIPrimaryMatch 0x15F28086 for the LM version of the port. IONetworkingFamily.kext is located in /System/Library/Extensions and protected by the macOS system from tampering. The only kext I have seen with either device ID's is AppleIntelI210Ethernet.kext, which is a plugin for the macOS Catalina IONetworkingFamily.kext. So adding any of these kexts would be counterproductive with a zero net gain. This includes IntelMausiEthernet.kext, IntelMausi.kext, AppleIGB.kext, SmallTreeIntel82576.kext. None of the third-party Ethernet kexts I have inspected contain the device ID for either the i255-V or i255-LM ethernet port. I am wondering if it would make any difference if you used F2158680 or even 8680F215 in place of F2150000. The Dortania guide pads out the device ID with '0000'. The kernel panic image you posed above says differently. The supported i255-LM Ethernet Controller has a device ID of 15F2, which the Dortania OC guide says should work, even with the alternative ACPI path. Your board may need a different path set for the Device ID trick to work. As the Comet Lake boards are still fairly new, there may be more than two possible paths. Have you checked to see which path your Ethernet port uses? Hackintool > PCI tab should show the path for the Ethernet port. As you have the recommended device ID in your /OC/ist, associated with one of the two possible paths. Adding this F2150000 Device-ID to the DeviceProperties section of your ist, as instructed in the Comet Lake guide, is supposed to trick macOS into believing the Ethernet port is an I255-LM and using the I210 kext that is part of macOS Catalina.ДЄdding the FakePCIID kexts may not help, it may just confuse the system. I am assuming you already have a recent version of Lilu.kext installed, otherwise you would never have been able to boot your system with OpenCore.ДЄccording to the Dortania guide for Comet Lake systems you don't need any additional kexts for your I225-V Ethernet port. To get it working in Catalina you need to add these two kexts to your /OC/kexts folder and ist:Д¬opies of the two kexts are attached below. It uses an Atheros chipset that Apple stopped supporting with the release of Mojave. Your TP-Link TL-WDN4800 isn't supported in Mojave or Catalina. I'm assuming this is an issue with the way I've configured macOS, and I will try removing the SSD catalina boots from to see if that rectifies the issue.

Trying to access it leads to a blank screen no error messages or hardware reboots. I have only just encountered this as an issue when attempting to change the AURA Sync settings. I have also just noticed that I can no longer access the BIOS of my motherboard.

#ETHERNET MAC CONTROLLER FOR PROCESSOR WINDOWS#

Other issues: various graphics issues with trying to use the integrated graphics (currently using a GTX 970 as my card for my windows partition which I know is no longer supported), but these are currently more minor problems as I am waiting for the new Radeon RX6800 to be released before I upgrade.ДЄny help would be greatly appreciated, first time poster so let me know if there is any extra info required. Note: the config and EFI included below have all of the above kexts included, please note I have tried removing and replacing all of them individually to no effect Haven't really tried to fix the wifi yet as ethernet would be my primary connection anyway.ДЇixes tried so far: Several versions of IntelMausiEthernet, FakePCIID and FakePCIID_Intel_I225_V, with all iterations of enabling and disabling those three, changing the device-id for the relevant PCI-E slot (as per Dortania's guide, with the variations listed within it). Mobo uses Intel I225-V for ethernet, my wifi card is TP-Link TL-WDN4800. Building a CustoMac Hackintosh: Buyer's GuideДЇollowing Dortania's guide has led me to a (mostly) functioning build of Catalina using opencore 0.6.2, with a few issues:

Ethernet mac controller for processor