5100 Seemingly Bricked
-
It really could be any number of things. You need to connect to the console to see what's actually happening there.
Steve
-
@cloudified When I connect a USB cable (through an Apple USB C to A dongle) to the 5100 and then run
ls -l /dev/cu.*
I only see
crw-rw-rw- 1 root wheel 0x9000001 Sep 10 13:21 /dev/cu.Bluetooth-Incoming-Port
As per the Netgate KB I'm expecting to see something of the form
/dev/cu.usbserial-<id>
-
Also, Netgate Global Support said this:
If this is an M1 Apple computer, then the drivers are not yet compatible with that CPU and you'll need to use another operating system to access the 5100's USB console. It could be an Intel-based Apple if available.
I am in fact running an M1 cpu.
-
@grounddave Hmm.
That's somewhat true. You should be able to do it with the latest release for the USB Serial chip -- I have 4 M1 Macs here and they can access the 5100.There are other programs out there you can use but they're not supported by Netgate as they're closed-source and not available to the public for free but they will work for you, too.
-
Are you referring to the latest Prolific drivers? I have installed them and nothing appears as /dev/cu.*
Regarding the commercial programs, can you name some for me known to work on modern macOS systems?
-
@grounddave If you're not getting a driver hook from the system I would verify you have a USB cable that passes data as well as power (4 wire USBs aren't used in battery chargers -- so if you have one that came with a power bank or a cell phone that won't work unless it was also designed to pass data).
As for the serial programs... just check the app store. There are many there -- a few work, I would check the reviews. I have one that I use but it is no longer available (they released a new non-upgrade version) and it could be construed as an endorsement by Netgate directly so I'd prefer to not go that route.
-
@grounddave aha. I’m still farting around on an Intel-based Mac so that might explain it. Good luck!
-
@grounddave said in 5100 Seemingly Bricked:
If you're not getting a driver hook from the system I would verify you have a USB cable that passes data as well as power (4 wire USBs aren't used in battery chargers -- so if you have one that came with a power bank or a cell phone that won't work unless it was also designed to pass data).
Derp! That was it. Found another cable and I now have a connection. This is all I see now:
boot: No /boot/kernel/kernel FreeBSD/x86 boot Default: 0:ad(0,a)/boot/kernel/kernel boot:
-
Hmm, well I would re-install from there if you have a config backup.
Do you have more than one boot device in that 5100, you added an SSD?
-
@stephenw10 Netgate support shot me a link to new firmware which installed seamlessly. I'm repurposing this box in a new home so I don't need to restore it's previous config.
I think I'm good for the moment. Thanks all!
-
@grounddave It's amazing how often, and please don't take this as a pot-shot at you, users go with the first mini-USB (or µ-USB) cable they find and assume that the hardware is dead or failed.
Glad you found a faster/better solution.
If you can DM me back with your original ticket # I'd appreciate it. -
This post is deleted! -
A follow-up:
This is a case of outdated information that has been addressed. If you find this forum and think the drivers aren't compatible please try another USB cable.If you really want to get in the weeds you can dig out a multi-meter to verify your Mini-USB cable has all 4 wires and connections made, as well as the shield (the metal on both ends of the cable should register continuity on your multi-meter as well).
Of course testing those ends is a royal pain so I would just plan on checking other cables. Having a half-dozen mini-USB and microUSB cables lying around is a great thing because you never know when you might need one for something, or two or three somethings at the same time.
-
This post is deleted! -
This post is deleted!