Extensions in Big Sur, Monterey and Ventura
Summary: Don't install Big Sur or
Monterey until you make sure your USB/Serial connection
the UART manufacturers have released new drivers that are
compatible with Big Sur and Monterey (see below).
Posted: March 21, 2020, Updated:September
Background: Warnings for
Legacy System Extensions started to appear on reboot after
installing macOS 10.15.4
These extensions are provided by the manufacturers (FTDI,
Silicon Labs etc.) of internal and external USB/Serial adapters
(UARTS) and are needed for CAT control of many serial port
(non-LAN) based radios, rotor controllers, etc.
intends to eventually prohibit kernel extensions for security
reasons and replace the functionality with DriverKit extensions
running in user space.
UART manufacturers have announced their intention to support
Apple's migration from Kernel Extensions to DriverKit Extensions.
Many UARTs are already supported automatically by Apple supplied
Driver Kit extensions in Big Sur.
As Apple System Extensions and DriverKit adds functionality, 3rd
party kernel extensions with matching functionality will not be
needed and will not load.
DXP is a Standard USB Class device and does not require
a 3rd party driver on Intel or Apple M1 Silicon Macs.
released Big Sur and Monterey with built-in support for many
(but not all) serial devices.
Big Sur/Monterey DriverKit (Intel and M1) currently
supports the following devices without any 3rd party driver:
Most devices tested so far with standard VID/PID including...
- KX3, K4
- K9JM CI-V Router
- Generic UART cables
- Silicon Labs:
- CP2102 (Icom IC-7610, IC-7300,
IC-9700, TS-590 etc.)
Most devices tested so far.
Big Sur/Monterey DriverKit does not
currently support the following devices without a
3rd party driver:
- Silicon Labs
- CP2105 (Yaesu
FT-991, FTdx101, etc.)
- Silicon Labs has released a new
released October 26, 2021
- Installs and loads on Apple M1 Silicon macOS Big Sur, Monterey
- Installs and loads on Intel macOS Big
- Terminal command to display
installed 3rd party DriverKit extensions:
$ systemextensionsctl list
active teamID bundleID (version) name