1st/2nd SG-1100 console port OK (macOS), 3rd and 4th no serial port available
-
Hi all,
This issue has wasted two full days at least. I have an SG-1100 #1 (Serial: NTG1929000xxx) connect to MacBook using USB-A to micro-USB cable. No issues. I follow the Netgate instructions, open terminal session and type "ls -l /dev/cu.*" or just cd /dev and ls and browse. I tested 5 cables to be good, which I have in a special box now.I have another SG-1100 #2 (Serial NTG1933000xxx), no issues.
Then a month ago I returned a 3rd SG-1100 #3 because no /dev/cu.usbserial-<id> appeared, with any of the cables.
Serial NTG2150000xxx.I just took delivery of a 4th SG-1100, same issue.
Serial NTG2132000xxx.Then I read this topic and shaved a bit of plastic off one of my cables, just to be sure. No dice.
So #3 and #4 are newer devices. Has there been any change implemented by Netgate? I mean concerning macOS console logon?
This can't be a coincidence of two defective units. Also, #4 was tested by the seller and found to have a working console port, probably on a windows machine.
TL;DR
- console port access test
- 4 Netgate SG-1100 units
- MacBook Pro 2013 (Big Sur) + MacBook air 2017 (Monterey)
- Prolific PL2303 USB to UART Bridge driver, downloaded today May 22 2023
SG-1100 #1 (Serial NTG1929000xxx): OK
SG-1100 #2 (Serial NTG1933000xxx): OK
SG-1100 #3 (Serial NTG2150000xxx): no /dev/cu.usbserial-<id> appears
SG-1100 #4 (Serial NTG2132000xxx): no /dev/cu.usbserial-<id> appears
Any thoughts?
Pete
Home: SG-2100 + UniFi + Synology. SG-1100 retired
Parents: SG-1100 + UniFi + Synology
Testing: SG-1100 w/ 120GB SSD via ext USB (eMMC dead). Works great -
Do either show as a USB device in dmesg?
Is it an ARM based Mac Book?
-
@Cabledude said in 1st/2nd SG-1100 console port OK (macOS), 3rd and 4th no serial port available:
MacBook using USB-A to micro-USB cable.
- A real Data cable or loading cable "only"?
Some will only load devices and other are for
both made, loading and data transfer - MacBook with M1 or M2 CPU?
If it come to driver related stuff it could be
that you will be getting hands on a driver to
make it proper working together with the
Mx based versions of MacOS
In older versions you may be able to get hands
on another serial adapter or cable, install the
driver and all is fine here, but since those chips
are inside of the devices it could be more and
more complicated.My APU6B4 is like yours sorted with an internal
chip so I only need a cable, but at the contact
to my Windows 10 Laptop, a driver would be
automatically installed by windows itself.Please see the picture below:
If you know what chip is used at your pfSense
appliance you will be able to go to the website
of that vendor and load and install the drivers
onto your Mx MacBook. This should be better
than swapping over and over the next unit.The most well known are FTDI, Prolific and
Silicon Labs from what I know it, for sure
there are other in the wild I don´t know. - A real Data cable or loading cable "only"?
-
@Dobby_ said in 1st/2nd SG-1100 console port OK (macOS), 3rd and 4th no serial port available:
Thanks for willing to help out
@Cabledude said in 1st/2nd SG-1100 console port OK (macOS), 3rd and 4th no serial port available:
MacBook using USB-A to micro-USB cable.- A real Data cable or loading cable "only"?
It's a real data cable as it works with SG-1100 units #1 and #2
- MacBook with M1 or M2 CPU?
It's a 2013 macbook pro and a 2017 MacBook Air, so all Intel
*If it come to driver related stuff...
If you know what chip is used at your pfSense
appliance ...I simply followed Netgate instructions here and installed the driver on these two Intel MacBooks and out of four SG-1100's #1 and #2 do connect perfectly but with #3 and #4 no serial connection comes up at all.
I just thought :
same Netgate SG-1100 model > same 2303 chip > same macbook and cable > same driver > should connect to any SG-1100 unit, right? But that's not the case.The most well known are FTDI, Prolific
Yes prolific is where I downloaded the driver
-
@stephenw10 said in 1st/2nd SG-1100 console port OK (macOS), 3rd and 4th no serial port available:
Thank you Steve for your input.
Do either show as a USB device in dmesg?
Will look at this as soon as I get home
Is it an ARM based Mac Book?
They are two (2013 and 2017) Intel macbooks with prolific 2303 UART driver.
-
It seems likely the newer 1100s have a different chip revision on the USB com IC and the driver you have doesn't recognise it. That would be more likely on ARM but could still happen on x86. The dmesg output should show a difference if there is one.
-
@stephenw10 said in 1st/2nd SG-1100 console port OK (macOS), 3rd and 4th no serial port available:
It seems likely the newer 1100s have a different chip revision on the USB com IC and the driver you have doesn't recognise it. That would be more likely on ARM but could still happen on x86. The dmesg output should show a difference if there is one.
Hi Steve,
Thanks for this troubleshooting advice. Actually I have spent so much time already, that I am in the process of slowly giving up. I tried a macOS app called "serial.app" (suggestion by Netgate's Ryan) and although a license would set me back $40, it does successfully connect to the console and I have been able to flash new firmware.But I was curious and am currently staring at dmesg output. It's several pages full of stuff I don't really understand. What am I looking for? Can you suggest a search string?
Thanks!
Selwin
-
@stephenw10 said in 1st/2nd SG-1100 console port OK (macOS), 3rd and 4th no serial port available:
It seems likely the newer 1100s have a different chip revision on the USB com IC and the driver you have doesn't recognise it. That would be more likely on ARM but could still happen on x86. The dmesg output should show a difference if there is one.
Hi @stephenw10
Here is a screen shot of the serial app after connecting both SG-1100 units. Of particular interest is the line in small type.
#4 is the trusted older device that shows up as "/dev/cu.usbserial-1410"
#3 is the problematic unit of newer date, which doesn't have a "/dev/cu..." etc line under it, instead a SN (serial number?) + code.
Does this clarify things?
-
I would run dmesg then connect the 1100 console then run dmesg again and look at what was added. Or you can probably use System Profiler to get the USB device details but I have nothing to check that on right now.
