Troubleshooting a Kernel Extension might not be straight forward, here are some tactics:
# Hardware Configuration
# BIOS Configuration
Fast Boot: Disabled
CNVi Support: Auto
Regarding Fast Boot and Dual Boot with Windows, read this explanation (opens new window) from Linux for more info.
# Kernel Extension Loading Status
Run the following command in terminal:
kextstat | grep -i "KEXT'S_NAME"
$ kextstat | grep -i "itlwm" 70 0 0xffffff7f84126000 0xf86000 0xf86000 com.zxystd.itlwm (1) 10EA7641-BDCB-3820-9AF7-4C773FD9953E <33 13 6 5 3 1>
- If a new line with the kext's name appears, it means the kext has successfully loaded.
- If you get nothing, please recheck your bootloader's configuration.
# Resetting System Preferences - Network
If you've tried other network-related Kernel Extensions before, some system configurations may be corrupted.
WARNING: The following procedures will completely reset your network preferences, including proxies, DNS, etc. The deleted files will be automatically created. But make sure you have made a proper backup.
Open System Preferences → Network, delete all ports, click on apply at the bottom right corner.
Open Terminal, run:
- And all files containing
Xas an integer)
If you've changed your SMBIOS before, you must also delete files with names that contain your current and previous models.
# Runtime Logs
Choose one of the following methods to collect logs.
# Via HeliPort
Use HeliPort to create a diagnostic report (works for AirportItlwm as well)
# Manually Collecting Logs
For AirportItlwm users, run the following commands before the next step:
# Enable airportd logs sudo /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Resources/airport debug +AllUserland +AllDriver +AllVendor1
Run the following commands in terminal to gather logs:
sudo dmesg | grep -E "itlwm|Airport|IO80211|EAPOL" > ~/Desktop/Log_"$(date '+%Y-%m-%d_%H-%M-%S')".log1
A log file will then be created on your Desktop.
# Debugging 802.1X
If you are using a network with 802.1X, please follow the guide below provided by Apple.
# Enabling Logging
Enable 802.1X verbose logs by running the below command in the terminal:
sudo wdutil log +wifi +eapol1
Reproduce the problem. (Important: Note the date and time issue occurred add this information to your report).
Then gather wireless diagnostics by running the below command in the terminal:
sudo wdutil diagnose1
Attach the wireless diagnostic file that appears in
/private/var/tmp/after several minutes.
Note: The wireless diagnostic process can take 10 minutes to complete. Once finished, the folder “/private/var/tmp/“ should appear automatically in the Finder and the wireless diagnostic file there will look similar to this:
# Disabling Logging To disable EAPOL logging
To disable both Wi-Fi and EAPOL logging use:
sudo wdutil log -wifi -eapol