- #Dockmod el capitan mod
- #Dockmod el capitan drivers
- #Dockmod el capitan update
- #Dockmod el capitan driver
Note that Apple’s example rm -rf command is incorrect.
#Dockmod el capitan driver
This lets you delete the kernel extension blocklist so that you can use the Ethernet driver to access the network and software update. The reason that you have to reboot from the recovery partition, if you don’t have Wi-Fi, is to bypass System Integrity Protection. (And, in general, all apps purchased from the Mac App Store require the Ethernet interface at launch to perform receipt validation.)
#Dockmod el capitan update
The reason, I think, that you have to issue the software update command via Terminal to get the fix is that the Mac App Store app will not run if the Mac doesn’t have an Ethernet interface. If you can connect to WiFi, your Mac will update to version 3.28.2 automatically, or you can follow the steps below to restore it manually. If you have version 3.28.1, you need an update.
If the Ethernet connection on your Mac stopped working recently, check System Information to find out which version of “Incompatible Kernel Extension Configuration Data” is installed.
That could be a support-time problem in organisations that have ethernet-connected Mac labs, common in education.Īfter this error by Apple, IT organisations may need to consider testing Apple security updates before deploying them to their Mac fleets. Manual intervention is required, either connecting via external Ethernet adapter and running software updates, or transferring the fix manually with a Flash Drive. But if wi-fi is unavailable, it won’t be possible to use deployment methods such as Munki, ARD, Casper etc, or wait for automatic updates to fix the error.
#Dockmod el capitan drivers
If the Ethernet drivers are blocked, but the Mac has not yet rebooted, your Ethernet connection will remain working until the next time the Mac reboots.Īffected Mac computers that are connected via wi-fi will get the update and the Ethernet adapter will be once again detected and functional. This is a problem because blocking the Ethernet drivers means your Mac will not be able to connect to your network via an Ethernet connection. Unfortunately, this blacklist update appears to have inadvertently contained the kernel extension information for Apple’s own Ethernet drivers. Neither make me feel warm and fuzzy about the state of software coming from Apple. Given the catastrophic affect on systems, though, it’s possible this was just an intern with a faulty commit button that wasn’t caught. What remains to be seen is why they released this change now as opposed to after 10.11.4 shipped and had been in the field for some time. This is a concern for a number of reasons, but that’s a matter for another day.įortunately, Apple realized their error in a short period of time, and pushed another Incompatible Kernel Extension Configuration Data update which removed the entry for the Ethernet Kernel Extension. Also included in this update was the banishment of spyresoft’s Dockmod which somehow managed to get a kernel extension signed by Apple into production, in conflict with the security guidelines for OS X. This is a result of Apple’s security processes working to disable kernel extensions Apple deems harmful.
#Dockmod el capitan mod
The mod date on the bad AppleKextExcludeList.kext for me was Feb 24. The blacklist is dynamically pulled by OS X (it’s not part of a system update) and I’m not sure what the trigger is exactly. Specifically versions lower than 10.2.0 have been blacklisted and version 10.1.12 is the one included in OS X 10.11.3. So apparently the version of the kernel extension for the built-in ethernet driver (AppleBCM5701Ethernet.ext) in OS X 10.11.3 has been added to the blacklist by Apple (AppleKextExcludeList.kext). I rolled the exclusion list back to the last version in my Time Machine backup to fix it, but this required booting from a recovery partition and was a huge pain in the butt, not to mention the time wasted finding the problem.
Turns out that it added an exclusion for the stockĪppleBCM5701Ethernet driver! This breaks ethernet and you have to use WiFi to get online. This software update was pushed via the silent “security updates” to my iMac today:Ġ31-51913 | Incompatible Kernel Extension Configuration Data 3.28.1Īfter rebooting my ethernet didn’t work. Apple blacklisted their own enet driver in a silent security update, SIP prevents fixing.
0 kommentar(er)
