Console access with MacOS 26.1?

beerguzzle

Picture of complaints from MacOS system report.

Gertjan

Didn't saw a Mac for a decade or so, but this :

looks like : ask the admin to "validate" the install ?
The driver seems disabled.
Enable it ?

keyser

@beerguzzle Yeah, you need to install a driver package from the app-store or vendor website depending on the chipset. For FTDI and sillicon labs (the most common ones) its a simple unified driver package in app form (.DMG) from each vendor on their website

aivxtla

@beerguzzle I use console on MacOS 26. Also driver is here, https://www.silabs.com/software-and-tools/usb-to-uart-bridge-vcp-drivers?tab=downloads. I use the app "Serial2" by Decisive Tactics, works fine for console connection. I don't think I had to download the driver as far as I remember with the app, pretty sure it detects the usb bridge with a built in driver but my memory could be betraying me as it's been a while since I installed it. There are other free options that required some tweaking (you may have better luck) but this was the console app that worked immediately after install without any issues for me. I will say putty on windows was nicer as it would auto connect on rebooting the firewall.

elvisimprsntr

With previous macOS versions, the FTDI and Prolific drivers were built in and all one needed to do was download a serial console app like CoolTerm.

https://freeware.the-meiers.org

luckman212

@beerguzzle yes I've used 26.1 to connect to the console of my 6100 as well as assorted other Netgate devices in the field: an old 4860, a 2100, a 4200..... it can/does work

Have you checked your privacy settings to make sure the usb-serial chip is allowed to connect?

https://support.apple.com/en-us/102282

keyser

@beerguzzle The point is, the drivers are no longer native in MacOS 26, so you have to add them.
MacOS <= 15 installations that used the drivers before might have keept them installed when doing the upgrade to 26, but I doubt it.
So you have to install the drivers from the vendors download site.

beerguzzle

Short story for those who read this later: Do not attempt to use your MacOS 26 device to access the console! Go find a Win/Linux box instead, use Putty or standard Linux stuff like "screen" or "tip". Save yourself a lot of heartache.

Long story: I finally got the Prolific device driver installed on my MacBook Air (26.1), with /dev/cu.PL2303G-USBtoUART130 and got the console connection to work via "screen -U /dev/cu.PL230G-USBtoUART130 115200". To get the driver installed you have to:

Boot into "options" mode by holding down on the power button until you see "options" under the boot-up Apple logo. This method replaces the "Recovery boot" method in earlier OSes of holding the Apple key+R while starting up. Then go to "options", select an admin user, login, and open "Startup Security Utility" under the Utilities menu. Change the setting from "Full Security" to "Reduced Security" and select "Allow user management of kernel extensions from identified developers".
While still in options mode open a terminal window, do the following:
csrutil status
(it should say enabled)
csrutil disable

This will totally disable Apple's System Integrity Protection. At this point you have taken the safety off of the gun, and neutered Apple's system protections. Beware. Hence my advice to go find a Win box.

Reboot, and install the device driver from Prolifics. During the install, you will get a popup that says "System Extension Blocked" and another that says "PL2303Serial would like to use a new driver extension". Click the "Open System Settings" button. System Settings will open and you will get another popup saying "Driver Extensions" with a greyed-out slider bar for PL2303Serial. Click on the slider bar to change it. You will get another popup asking for
admin user/pw. The slider will change. Click done on the popup box. The Install box for PL2303Serial should say successful, telling you to restart your Mac.
Restart, and log back in. Fire up System Settings, search for Logins and Extensions. Scroll down until you see Extensions, click on By Category. Look for driver extensions. Click on the circled i. The PL2303Serial driver should be enabled.
Go to "About" in System Settings, scroll to the bottom and run System Report. Click on Software->Disabled Software. Your Prolific stuff may well appear there. Note the bundle number, something like 2MP849R8J5. It will probably say "no user consent".
do a "ls -l /dev/cu*". The cu.PL30... device may or may not be there. If it is there, great. Try it out with

screen -U /dev/cu.PL230G-USBtoUART130 115200

from a terminal window and see if you get to your Netgate console. If so, done.

If not, reboot back into options mode and open up a terminal window. Then do:

spctl kext-consent status
(it should be enabled)
spctl kext-consent list
spctl kext-consent add 2MP849R8J5
spctl kext-consent list
2MP849R8J5

This gives user consent for the disabled software bundle, even though the Mac will never show this in the Disabled Software section.

Reboot again. Go look for /dev/cu.PL230G-USBtoUART130. If it is there, great. If not then commit seppuku. Your work was in vain. You should have found a Win 10 box instead. I told you.

Note: With great pain, I got /dev/cu.PL... installed and working on my MacBook Air. I went through this again with my 2024 Mac Mini (26.1): failure. I don't know why.

luckman212

@beerguzzle Or just use Serial.app which has its own native driver that supports this UART without needing any extra software. One time purchase that I made years ago and do not regret!

aivxtla

@beerguzzle as I mentioned before and luckman mentioned above Serial2 just works without any tweaking.