genzai Posted November 29, 2016 Share Posted November 29, 2016 Hello Mieze, Here are the results of my testing: First i used an SSDT to inject my i211 and give it the i210 device ID (8086,1533). This appears to be what the driver looks for as it only has an IOPCIPrimaryMatch value in the info plist. after a few tries the SSDT appeared to work and IOJones showed the correct 1533 device ID. The driver did not load however. Leaving the SSDT in place i then went about creating a FakePCIID kext. I based it off the "BCM57XX as BCM57765" kext that is packaged with FakePCIID. Once I got this working, i then saw both network controllers. EN0(i219) and EN2(i210) -- not sure where EN1 went but thats probably not relevant. Both controllers showed as loaded everywhere i checked-- -System Profile showed them both under Ethernet devices, with the proper kexts associated (i211, reported as i210 with AppleIntelI210Ethernet loaded, and i219 with intelMausiEthernet loaded. - Network utility showed both devices and EN# - DPCImanger showed both devices under its network list - IOJones seemed to show both fully loaded with a lot of details under each entry - and there was a new entry for "Ethernet 2" in System Preferences>Network However despite all this the i211 port would only show as inactive in system preferences and never showed any sign of life when connected to the network (other than physical LEDs blinking). Furthermore (and very perplexing to me) with I210 "enabled" my i219 controller was also not working. It also showed a red inactive status in network preferences when it should be connected. Another odd thing is that Network Utility seemed to report activity for the i219 (though not the i210) but there was no way to get the OS to otherwise recognize either controller as connected let alone passing traffic. Removing the FakePCIID kexts brought my i219 back to life but now i am back to square one. Thoughts? Thanks! g\ Link to comment Share on other sites More sharing options...
Mieze Posted December 7, 2016 Share Posted December 7, 2016 Hello genzai, please send me the kernel logs of your machine with both NICs enabled. Thanks in advance! Mieze Link to comment Share on other sites More sharing options...
llamafilm Posted January 5, 2017 Share Posted January 5, 2017 I'd like to help with this, because I also have an i211 on my motherboard. Without any SSDT edits, I made a FakePCIID injector kext that changes device-id to 1533. I see the device in IOJones with the I210 driver attached. I see it in Network Utility as en3. (Oddly, en2 is missing. en0 is the other LAN and en1 is wifi.) I see it in Network Prefs with a red dot, and it says the cable is not plugged in. If I click on Advanced > Hardware, then System Preferences freezes and I have to force quit it. My other i218 NIC still works fine, but when I unplug it, it still shows green with an active IP address in Network Prefs. When I plug the cable back in, it works right away. No need to reboot nor disable the FakePCIID kext. This seems to be an improvement with Sierra. When I tried the same thing a few months ago on Yosemite, I got the same results as genzai, where the i218 did not work at all. I'm not very familiar with Sierra's new logging. Which log file would you like to see? FakePCIID_Intel_I211.kext.zip Sierra-Hack with fakepciid.zip Link to comment Share on other sites More sharing options...
Mieze Posted January 5, 2017 Share Posted January 5, 2017 Starting with Sierra use "log show --predicate "processID == 0" --debug" in order to retrieve kernel logs. Mieze Link to comment Share on other sites More sharing options...
llamafilm Posted January 5, 2017 Share Posted January 5, 2017 Thanks. Log attached. I spoke too soon; after another reboot, the i218 and WiFi both stopped working, Sys Prefs froze up, and when I put my mouse over the Airport symbol in the menu bar, I got a spinning beach ball. Removing the injector kext puts everything back to normal. I'm not sure why the other NICs seemed to work okay the first time. log.txt.zip Link to comment Share on other sites More sharing options...
ydeng Posted June 21, 2017 Share Posted June 21, 2017 (edited) i211 is supported by SmallTreeIntel82576.kext. Only need to put 8086 1539 in the kext and FakePCIID_Intel_Gbx. Or use patched binary below, no need for FakePCIID_Intel_Gbx http://www.insanelymac.com/forum/topic/324392-ryzen-clover-installation-guide-macos-sierra/?p=2460269 Edited July 12, 2017 by ydeng 1 Link to comment Share on other sites More sharing options...
genzai Posted July 13, 2017 Author Share Posted July 13, 2017 @ydeng, This works! Finally have the last bit of hardware on my motherboards working. Thanks so much. Please note that the DevID must be injected in both the SmallTree and FakePCIID_Intel kexts. g\ 1 Link to comment Share on other sites More sharing options...
ydeng Posted July 13, 2017 Share Posted July 13, 2017 @ydeng, This works! Finally have the last bit of hardware on my motherboards working. Thanks so much. Please note that the DevID must be injected in both the SmallTree and FakePCIID_Intel kexts. g\ Did you try the binary patched Smalltree82576? That should work too. Link to comment Share on other sites More sharing options...
genzai Posted July 14, 2017 Author Share Posted July 14, 2017 Did you try the binary patched Smalltree82576? That should work too. Nope but I prefer it this way, unless the patching can be done through clover. g\ Link to comment Share on other sites More sharing options...
ydeng Posted July 14, 2017 Share Posted July 14, 2017 Nope but I prefer it this way, unless the patching can be done through clover. g\ I provided the string replacement in the post too. Link to comment Share on other sites More sharing options...
genzai Posted July 15, 2017 Author Share Posted July 15, 2017 I provided the string replacement in the post too. can the bin patch and info.plist patch be done through clover? I think so right? can you post a bare config plist with just the kext-to-patch info? g\ Link to comment Share on other sites More sharing options...
Recommended Posts