So my mac kernal_task keep using 600%++ of my CPU usage when my Mac is plugged in, and thus i decided to delete the IOPlatformPluginFamily.kext by doing these steps:
Enter Recovery Mode
Open Terminal
Disable SIP: csrutil disable
Enter Single User Mode
Delete the kext file
But will the kext file come back if i enable SIP again?
I'm currently using High Sierra but i have been doing this since Sierra
And i followed this guide https://www.davidschlachter.com/misc/kernel_task
Related
I have an application that we're developing that provides VPN System Extension for macOS. I have successfully built, signed and notarized the app.
When we install the package the user sees this popup:
The program tried to load new system extension(s). If you want to enable these extensions, open Security & Privacy System Preferences.
However when I download an existing VPN app from the macOS AppStore I see this popup when the extension is being installed:
Why am I getting the blocked popup when my app has been notarized? Is it because it's not coming from the AppStore?
As far as I'm aware, VPNs implemented via the NetworkExtension Framework don't necessarily need to be installed as System Extensions. This is probably the distinction you're running into. You can check the list of all system extensions in the system using the following Terminal command:
systemextensionsctl list
0 extension(s)
If the "Turbo VPN" extension is not listed there, it was not installed using the OSSystemExtensionManager API.
Only system extensions need to go through the System Preferences user approval process.
While I start mac-mini. I was unable to login into the login screen. It shows the wrong password.
but the password is right and I daily use it.
CPU: Mac mini
OS: Big Sur
I Research and find the solution from the Apple support team. and I saw many people face this problem.
Solution:
Step 1:
Start on your Mac and continue to long press and hold the power button until you see the startup options window. Click the gear/settings icon labeled Options, then click Continue.
Note: If you're asked to select a user you know the password for, select the user, click Next and enter their administrator password.
Step 2:
Then select reinstall macOS from the utility window in macOS recovery, then click Continue and follow the onscreen instructions.
Follow these guidelines during installation:
If the installer asks to unlock your disk, enter the password you use to log in to your Mac.
If the installer can't see your disk or notifies you that it can't install macOS on your computer or volume, you may need to erase your disk first.
If the installer offers you the choice between installing on Macintosh HD or Macintosh HD – Data, choose Macintosh HD.
Allow the installation to complete without putting your Mac to sleep or closing its lid. Your Mac may restart and show a progress bar several times, and the screen may be empty for minutes at a time.
When the installation is complete, your Mac may restart to a setup assistant.
For More information: https://support.apple.com/en-gb/HT204904
When I disabled SIP via recovery mode, the kext could be loaded by kextload, anyway, when system restart, kext will not be loaded by kext manager like it supposed to be in Mojave and lower.
If I enabled SIP and load the kext (the kext is full functional with 10.14 -), it will show following message
Kext rejected due to system policy: <OSKext 0x7ff02df0b450 [0x7fff89d4aba0]> { URL = "file:///Library/StagedExtensions/Library/Extensions/...
BTW, In Catalina, how user to allow a kext ? I know in 10.13, it will show on the General of Security & Privacy, in 10.14, I was using Kextdrop, anyway, kextdrop won't work with Catalina.
Found out I just need sign the kext and notarize the kext in order to get system to load it
I have downloaded Hardware IO Tools for Xcode 7.1 from the Apple Developer site and installed it by opening the DMG and then double clicking Network Link Conditioner.prefPane.
I then go to my System Preferences and can see the Network Link Conditioner is there. I can go into it but as soon as I click the switch to turn it on the whole System Preferences freezes up. Also, I noticed that my keyboard seems to stop working...somewhat. I can still do cmd + spacebar and then type in there to search my system but I can't type into the URL field on safari for example.
My Mac: OS X Yosemite v10.10.5
My Xcode: v7.2.1 (7C1002)
By the way, I downloaded the 7.1 version of the Hardware IO Tools as they only have a 7.1 or 7.3 version, there doesn't seem to be a version for 7.2. Maybe that is the issue? I can't currently upgrade to 7.3 as that requires me to upgrade OS X to 10.11 but our company policy does not currently allow for that.
Anybody know how I could fix this?
Could this be caused by the fact that I am not an admin on my machine?
My suspicion was correct, it wouldn't start as it needs to be run as an admin.
If you're not an admin, you need to run a command such as
sudo /Applications/System\ Preferences.app/Contents/MacOS/System\ Preferences
or in my case I had to get an admin in the office to do:
su - <admin_username> /Applications/System\ Preferences.app/Contents/MacOS/System\ Preferences
These commands will open the System Preferences as an admin user.
I have noticed that when he Network Link Condition is open in the System Preferences, my keyboard stops working in certain areas still. For example, I couldn't type in here whilst the panel was open (even with it turned off) but as soon as I closed the panel I could type again. I will possibly open another question at a later dare about this though.
I have tried to disable SIP from OS X El Capitan following the procedure
Enter Recovery Mode
Open terminal
csrutil disable
and it works fine, if I type csrutil status it is disabled.
Then I restart my computer, but in my terminal the csrutil status returns this
System Integrity Protection status: enabled (Custom Configuration).
Configuration:
Apple Internal: disabled
Kext Signing: disabled
Filesystem Protections: disabled
Debugging Restrictions: disabled
DTrace Restrictions: disabled
NVRAM Protections: disabled
This is an unsupported configuration, likely to break in the future and leave your machine in an unknown state.
Why is it still enabled? I need to disable it because otherwise the system won't recognize my Vodafone key in Vodafone Mobile Broadband.
Apparently this is a known bug. See https://openradar.appspot.com/22361698 ; that is listed as a duplicate of another bug but that other bug doesn't appear to be publicly accessible.