Page 4 of 11

Re: macOS High Sierra (10.13) FTDI Driver Bug Workaround

PostPosted: Sun May 13, 2018 1:20 pm
by bap
bedelman0731 wrote:
The place where I found the leftover/older version of FTDIUSBSerialDriver.kext was at /Library/StagedExtensions/Library/Extensions/FTDIUSBSerialDriver.kext -- I could tell because the date on the kext was from 2012 rather than showing the date of 5/9/17 as it should show for the newer driver.


Thank you for this pointer and the other details you provided. I ended up running into the exact same situation with the Mac Mini I run Indigo on, so after using your post as a guideline I deleted all the old FTDI drivers, installed the 2.4.2 driver, rebooted, and everything is working like a champ again.

Re: macOS High Sierra (10.13) FTDI Driver Bug Workaround

PostPosted: Wed Jun 06, 2018 8:10 am
by individualist
Updated MacMini server from 10.9 to 10.13 (whew!). Hit the FTDI driver bug. Performed the workaround - d/l the new FTDI driver and substituted it and USB connection to my interface was restored. Restarted a few times without a hitch. Tested the unplug/re-plug and was successful.

As a side note, I found the workaround to allow Timbuktu Pro 8.8.5 to run on High Sierra. Google: "Timbuktu DOES Work in High Sierra", and follow that with a search of Ric Ford's Macintouch site for the "easy" way to fix the ScreenSaver.framework and Gatekeeper issues. I'm sure I'm not the only one running my server headless.

Re: macOS High Sierra (10.13) FTDI Driver Bug Workaround

PostPosted: Wed Jun 06, 2018 4:52 pm
by FlyingDiver
lanbrown wrote:
I just use ARD to control a headless Mac. It is even used to control non-headless Mac's. The remote desktop portion of ARD is based on VNC.


I just use the built-in Screen Sharing, which is ARD-lite, I think. Works fine.

Re: macOS High Sierra (10.13) FTDI Driver Bug Workaround

PostPosted: Wed Jun 06, 2018 9:29 pm
by jltnol
Hey guys

FWIW, I was able to make this happen, thanks to the crystal clear, step by step instructions.

I did run into a few hiccups, mostly of my own making.

First, I made a clone of my Indigo OS to experiment with in case something went horribly wrong. But instead of downloading the latest 10.13 installer, I used one I already had. Once the upgrade was done, I was able to delete the offending files, install the right ones, gave them permission to run, and things were going smoothly, with the Insteon USB modem.

Then of course, came the update to the latest version of 10.13. During the update, as mentioned, Apple re-writes the AppleUSBFTDI.kext file, and puts it in original location, which needs to be moved. The problem I ran into when trying to do so was there was already a file in the location indicated by the Terminal, so I couldn't move it.

I then tried booting into the new OS, and moving the file in the GUI, but I wasn't able to do anything with it because of a permission issue. So I booted into the old OS, and was able to delete it from the new OS drive from there. After that, I booted into Recovery Mode, moved the newly written file to the now empty location, re-started, and everything seems fine. :)

While I pretty brave about the terminal, my skill level is very low. In retrospect, while in Recovery Mode and working in the Terminal, I could have deleted the first moved file, or I could have moved the 2nd file to a different location, but honestly didn't think of either option at the time, and even after, had to look up the commands to do so.

A host of untried options. but at least at the next OS update, I've got a few things to try to make this easier...

Anyway.... for now, everything seems to be working as it should. I'm going to give it several days... maybe a week before I clone the new os back to the internal drive of the Mini I'm using for Indigo.

As always, thanks to both Jay and Matt and everyone else who has contributed to this patch. Here's hoping Apple can see their way clear to fixing this, and soon.

macOS HS (10.13) FTDI Driver Bug Workaround...

PostPosted: Thu Jun 14, 2018 11:37 pm
by P15-D24
On a clean High Sierra install (Have not run Migration Assistant or modified anything) will the FTDI Driver mentioned in Step 1. exist?
I'm not seeing them in either /System/Library/Extensions/ or /Library/Extensions/ on my High Sierra drive.. I'm using Terminal, not Finder.

Re: macOS High Sierra (10.13) FTDI Driver Bug Workaround

PostPosted: Fri Jun 15, 2018 7:47 am
by jay (support)
No, none of the ones in step 1 should exist after a reformat/clean install of macOS - they would only exist if you were upgrading from a previous OS version where it was necessary to install the FTDI driver yourself. (or perhaps a Time Machine migration)

Re: macOS High Sierra (10.13) FTDI Driver Bug Workaround

PostPosted: Fri Jun 15, 2018 9:55 am
by P15-D24
Another success! First tried connecting using standard driver and wouldn't connect with any USB port. Unplugging/plugging back in didn't work either.
Installed the new driver, rebooted, connected immediately.

FYI, this is HS installed on a Mac Pro 3.1, which is not supported by Apple. Installation was done via the well documented "dosdude" hack for HS installs on older Macs.
YMMV, but if your waiting for Apple to release new hardware, this may buy you some time and be able to keep Indigo happily running. If my testing system develops any issues I will report them.

Re: macOS High Sierra (10.13) FTDI Driver Bug Workaround

PostPosted: Fri Jun 15, 2018 10:45 am
by Different Computers
@gflewis, you can determine your boot drive by opening System Preferences, then Startup Disk. All bootable volumes will show, but below the window with them it will say "You have selected [whatever] as your startup volume."

Odds are really really good that it is Macintosh HD as you think it is.

Re: macOS High Sierra (10.13) FTDI Driver Bug Workaround

PostPosted: Tue Jul 10, 2018 5:46 pm
by sgtwicki
I can verify that this workaround works with 10.14 Beta (18A326h).
2412U works steadily in both the motherboard USB and also a PCIe USB3 card.
Oddly, when I first installed Mojave, the 2414U was working on the motherboard USB until Mojave did a software update. After that, the 2414U and W800RF32 wouldn't show up at all, no matter how many times I unplugged/replugged or restarted. Doing the steps in the workaround fixed it.

Re: macOS High Sierra (10.13) FTDI Driver Bug Workaround

PostPosted: Tue Jul 10, 2018 10:10 pm
by matt (support)
Unfortunately, Apple still shows this bug as open.

Re: macOS High Sierra (10.13) FTDI Driver Bug Workaround

PostPosted: Wed Jul 11, 2018 9:22 am
by jay (support)
lanbrown wrote:
Matt and Jay are you going to test the beta and provide feedback to Apple? There is a better chance of getting it fixed during the beta phase. From it working and then stopped after a software update, Apple may have tried to fix it and then a further fix broke it again.


Yes, we'll install the beta at some point and test. However, the only Mac I was able to confirm the bugs on is not supported by Mojave. So, bottom line is that we may no longer have the ability to duplicate the bugs even if they persists in Mojave. Anyone who's testing Mojave would give us valuable insight into these bugs.

Re: macOS High Sierra (10.13) FTDI Driver Bug Workaround

PostPosted: Wed Jul 11, 2018 9:23 am
by jay (support)
sgtwicki wrote:
I can verify that this workaround works with 10.14 Beta (18A326h).
2412U works steadily in both the motherboard USB and also a PCIe USB3 card.
Oddly, when I first installed Mojave, the 2414U was working on the motherboard USB until Mojave did a software update. After that, the 2414U and W800RF32 wouldn't show up at all, no matter how many times I unplugged/replugged or restarted. Doing the steps in the workaround fixed it.


Can you confirm which PowerLinc you're using? You mention a 2412U and a 2414U. The latter doesn't use the FTDI driver so if it doesn't work that would be a different issue.

Re: macOS High Sierra (10.13) FTDI Driver Bug Workaround

PostPosted: Thu Jul 12, 2018 3:22 pm
by kw123
here my conversion:

bought an old 2012 mac pro (2x6 cpu 3.46GHz, 32GB) , added a MACSales internal PCIe bus 1 TB disk , installed HS ( all together 2-5 times as fast as 2008 mac pro)

installed a USB3 board <<<==== this elimiates the USB driver issues !!!

move data
copy files over to new box:
- ~/users/indigo (my plugins )
/Library/Application Support/Perceptive Automation/Indigo 7

move big internal storage Disks (4 x 2 TB in raid config )
connect external backup disk (4x 2 TB )

installed new postgres app
created a dump on old machine pg_dumpall > dump
imported dump file on new machone: psql < dump

install new INDIGO
onto copied directory (will set rights etc properly)

installed virtual box (for my UniFi camera system)
copy .. virtual box files
create new unifi box system and import vdi file
change VBOX-unifi ip number to old ipnumber


general
change MACPRO ip number to old ip number in system parameters / network
setup time machine to point to the right destination disk


reboot ...., everything works
- insteon
-zwave
-rfxcom -- needed to restart plugin
- caddx security plugin usb connection
- sqllogger,
- pibeacon,
- unifi,
- indigoplots,
- fingscan (installed its files automatically .. seems to work fine
- utilities
- and many others


all together about 1 hour

Longest time was
- finding a HDMI dongle that fits the video out on the mac pro (the connector is different on the 2012 as compared to the 2008
- the holders for the internal disks are different, had to unscrew the old holders and attach the new ones, otherwise it is just take out and put into new


very positively surprised

Karl

ps the macpro is bored, > 400 indigo devices, postgres 34GB db, ubuntu linux vbox for UniFi NVR 12 cameras. +...

Screen Shot 2018-07-12 at 16.04.35.png
Screen Shot 2018-07-12 at 16.04.35.png (34.44 KiB) Viewed 4361 times

Re: macOS High Sierra (10.13) FTDI Driver Bug Workaround

PostPosted: Thu Jul 12, 2018 3:31 pm
by FlyingDiver
I just upgraded my '10 Mac Pro to 12 core 2.93 GHz and 40GB ram (4x8GB new, plus 4x2GB old). Added an PCI riser card for an SSD boot drive, and also a PCI USB-3 card (both Sonnet, I think). It's got a 512GB SSD for boot (way overkill), 4TB for boot backup and clone, 4TB for Security Spy, and 8TB for Plex storage. Have one bay free. Plus I could add another SSD to the Sonnet PCI card.

That was in anticipation of moving all my HA stuff onto it. Everything is there now (SecuritySpy, Plex, SurLaTablo (OTA DVR extractor) except Indigo. I was waiting until we get back from the summer road trip for that, but I think the trip is going to be delayed so I might do it next week.

Re: macOS High Sierra (10.13) FTDI Driver Bug Workaround

PostPosted: Fri Jul 13, 2018 12:09 pm
by Different Computers
Just installed 10.13.5 on top of 10.11.6 on a 2013 2.4Ghz i5 Retina MBP Model 11,1 and it seems like everything is working. Insteon, Z-wave, everything.

Update: And now updated to 10.13.6, and though HomeKit Bridge didn't start when the server did, reloading it fixed that. Insteon and Z-wave still working, and in fact Insteon is through a hub. I have a PowerLinc 2412U.

Here's one unexpected bonus I haven't seen mentioned anywhere else: If both Macs are running 10.13.6, either may now act as an AirPlay receiver for the other, and iTunes doesn't even have to be running on the receiver.

Seems like the AirPlay 2 implementation is troublesome when there are AirPlay 1 devices around at the same time, even if you're picking one or the other. I'm getting a lot of flakiness in the display and choosing of AP devices.