Crabhunter Posted October 3, 2018 Share Posted October 3, 2018 Years ago I patched my IONetworkingFamily.kext by adding AppleBCM5701Ethernet.kext into the plugins folder. This has worked fine for many versions of OSX, certainly up to Sierra, I missed High Sierra and am now trying to get Mojave up and running. Now my problem is this. If I install the complete IONetworkingFamily.kext my Ethernet works but it knocks out my WiFi. If I just put AppleBM5701Ethernet.kext in the plugins folder of the Mojave IONetworking kexts my WiFi works but Ethernet doesn't. I'm not sure where to go from here. Mike Link to comment https://www.insanelymac.com/forum/topic/335784-problem-with-ionetworkingfamilykext/ Share on other sites More sharing options...
artur_pt Posted October 3, 2018 Share Posted October 3, 2018 hello have u try to inject the atheros40 from clover/kexts ? good hack Link to comment https://www.insanelymac.com/forum/topic/335784-problem-with-ionetworkingfamilykext/#findComment-2638505 Share on other sites More sharing options...
Crabhunter Posted October 3, 2018 Author Share Posted October 3, 2018 2 hours ago, artur_pt said: hello have u try to inject the atheros40 from clover/kexts ? good hack Just tried that but no luck Link to comment https://www.insanelymac.com/forum/topic/335784-problem-with-ionetworkingfamilykext/#findComment-2638526 Share on other sites More sharing options...
Crabhunter Posted October 3, 2018 Author Share Posted October 3, 2018 37 minutes ago, Hervé said: Your injection into the PlugIns folder of IONetworkingFamily kext was probably the wrong way of proceeding on the 1st place. As it stands, IONetworkingFamily kext does contains a PlugIn called AppleBCM5701Ethernet in all versions up to Mojave. The real questions is: what patch did your replacement kext contain? If all it contained was an injection of a particular device id in the kexts's Info.plist file, it should not be too much of a surprise that, after a few years and a few OS X/macOS versions, your old kext no longer works. Why? Simply because Apple has a tendency to modify syntax of kexts's Info.plist files over time. Once you've identified your original patch details, consider applying that patch to Mojave's vanilla AppleBCM5701Ethernet.kext. I would recommend 2 x different ways to do this: through Clover's on-the-fly patching facility if you use Clover through a copy of the vanilla kext that you'll patch and increase versioning before placing to /L/E. You will then follow by repairing permissions to /L/E and rebuilding your cache. The patched kext with higher version will supersede the vanilla PlugIn kext. When I first installed osx on my machine Ethernet didn't work. I searched for a kext and the instructions were to put it into IOnetworking. I can't remember whether I replaced one that was already there or not. It worked! Ever since then I have got ethernet working on each new version by replacing the whole IONetworking kext. I'm not sure how to proceed now. Mike Link to comment https://www.insanelymac.com/forum/topic/335784-problem-with-ionetworkingfamilykext/#findComment-2638530 Share on other sites More sharing options...
Crabhunter Posted October 4, 2018 Author Share Posted October 4, 2018 20 hours ago, Hervé said: Simple: state the specs of car you use the kext for (model, PCI ids) post a zipped copy of the kext you used till now Thank you, this is what I get from system report in Sierra with Ethernet working using the kext attached. Broadcom 57765-B0: Name: ethernet Type: Ethernet Controller Bus: PCI Vendor ID: 0x14e4 Device ID: 0x16b5 Subsystem Vendor ID: 0x1025 Subsystem ID: 0x0743 Revision ID: 0x0010 Link Width: x1 BSD name: en1 Kext name: AppleBCM5701Ethernet.kext Location: /System/Library/Extensions/IONetworkingFamily.kext/Contents/PlugIns/AppleBCM5701Ethernet.kext mDNS offload capable: b8:88:e3:ac:da:a7 Version: 3.6.9b2 IONetworkingFamily.kext.zip Link to comment https://www.insanelymac.com/forum/topic/335784-problem-with-ionetworkingfamilykext/#findComment-2638683 Share on other sites More sharing options...
Crabhunter Posted October 11, 2018 Author Share Posted October 11, 2018 Here is a little more information on my IONetworkingFamily.kext problem. My Ethernet is a Broadcom BCM57785. In the past I have got it working by using an old IONetworking kext that has a patched AppleBCM5701Ethernet.kext in the plugin folder. If I use this complete IONetworking kext in Mojave the ethernet works but it knocks out WIFI If I replace the Mojave AppleBCM kext in the plugin folder with the one from my old kext then I can see an ethernet connection in the networking pref pane but it says a cable is disconnected even when one is present. Wifi is still working at this point. There must be some information needed in the old IONetworking kext apart from what's in the AppleBCM kext. Can someone give me some pointers as to what sort of information I should be looking for, what files it might be in and what programs I might need to open the sort of files if they're not text files. Mike Link to comment https://www.insanelymac.com/forum/topic/335784-problem-with-ionetworkingfamilykext/#findComment-2640129 Share on other sites More sharing options...
Crabhunter Posted October 11, 2018 Author Share Posted October 11, 2018 Thank you, that will give me something to work on. Mike Link to comment https://www.insanelymac.com/forum/topic/335784-problem-with-ionetworkingfamilykext/#findComment-2640145 Share on other sites More sharing options...
Crabhunter Posted October 12, 2018 Author Share Posted October 12, 2018 Well I've added the missing id to the vanilla AppleBCM kext inside the plugin folder of OINetworking. This at least brings up something in the networking prefpane but still the only way I can get it to work is by using the whole of my old IONetworkingfamily.kext which of course kills wifi. When I try rebuilding the cache I get a lot of errors about dependencies between IONetworking, AppleBCM and IO8xxx.kext which I have had to add Atherosairport or something to get my WiFi to work. I don't think this can be resolved by editing the config files, I think these dependencies have been compiled into the executables. Mike. Link to comment https://www.insanelymac.com/forum/topic/335784-problem-with-ionetworkingfamilykext/#findComment-2640382 Share on other sites More sharing options...
Recommended Posts