Hope I don’t add to the panic. Butttttt, I am also on 10.11.3 and have just plugged in my grid for the first time since updating and noticed a few interesting things once I fired up max and didn’t see any devices showing up. Here are my findings so far (tl;dr; at the end of the post):
Started with System Profiler, noticed that my grid was showing up in the device tree despite that it was unplugged at the time. OK, normally that means hardware weirdness, tested all the usb ports w/ other devices, they were being read just fine, but the monome was still showing up (the nested usb hub was my trying this with or without hubs, noticed the monome would actually cause erratic behaviour with both different hubs and none at all):
took a step down the BSD rabbit hole:
1692 ◯ sudo ioreg -p IOUSB -w0
Password:
+-o Root <class IORegistryEntry, id 0x100000100, retain 14>
+-o Root Hub Simulation Simulation@14000000 <class AppleUSBRootHubDevice, id 0x100000304, registered, matched, active, busy 0 (6 ms), retain 11>
+-o BRCM20702 Hub@14300000 <class AppleUSBDevice, id 0x100000305, registered, matched, active, busy 0 (9 ms), retain 15>
| +-o Bluetooth USB Host Controller@14330000 <class AppleUSBDevice, id 0x100000344, registered, matched, active, busy 0 (10 ms), retain 20>
+-o Apple Internal Keyboard / Trackpad@14400000 <class AppleUSBDevice, id 0x100000315, registered, matched, active, busy 0 (353 ms), retain 25>```
*prettier*:
```kanaloa ॐ ~:
1697 ◯ ioreg -p IOUSB -w0 | sed 's/[^o]*o //; s/@.*$//' | grep -v '^Root.*'
BRCM20702 Hub
Bluetooth USB Host Controller
Apple Internal Keyboard / Trackpad```
No device… ?!
okay. Let's move into Darwin and try the profiler in the command line this time:
``kanaloa ॐ ~:
1694 ◯ system_profiler SPUSBDataType
2016-03-05 12:47:03.827 system_profiler[4486:313162] SPUSBDevice: IOServiceGetMatchingService did not return anything for location 0x14211000
2016-03-05 12:47:03.827 system_profiler[4486:313162] SPUSBDevice: IOServiceGetMatchingService did not return anything for location 0x14210000
2016-03-05 12:47:03.828 system_profiler[4486:313162] SPUSBDevice: IOServiceGetMatchingService did not return anything for location 0x14200000
USB:``
USB 3.0 Bus:
Host Controller Driver: AppleUSBXHCILPTH
PCI Device ID: 0x8c31
PCI Revision ID: 0x0005
PCI Vendor ID: 0x8086
Apple Internal Keyboard / Trackpad:
Product ID: 0x0262
Vendor ID: 0x05ac (Apple Inc.)
Version: 2.25
Speed: Up to 12 Mb/sec
Manufacturer: Apple Inc.
Location ID: 0x14400000 / 3
Current Available (mA): 1000
Current Required (mA): 40
Extra Operating Current (mA): 0
Built-In: Yes
BRCM20702 Hub:
Product ID: 0x4500
Vendor ID: 0x0a5c (Broadcom Corp.)
Version: 1.00
Speed: Up to 12 Mb/sec
Manufacturer: Apple Inc.
Location ID: 0x14300000 / 2
Current Available (mA): 1000
Current Required (mA): 94
Extra Operating Current (mA): 0
Built-In: Yes
Bluetooth USB Host Controller:
Product ID: 0x8289
Vendor ID: 0x05ac (Apple Inc.)
Version: 1.12
Speed: Up to 12 Mb/sec
Manufacturer: Apple Inc.
Location ID: 0x14330000 / 6
Current Available (mA): 1000
Current Required (mA): 0
Extra Operating Current (mA): 0
Built-In: Yes
USB2.0 Hub:
Product ID: 0x0608
Vendor ID: 0x05e3 (Genesys Logic, Inc.)
Version: 32.98
Location ID: 0x14200000
USB2.0 Hub:
Product ID: 0x0608
Vendor ID: 0x05e3 (Genesys Logic, Inc.)
Version: 32.98
Location ID: 0x14210000
monome 64:
Product ID: 0x6001
Vendor ID: 0x0403 (Future Technology Devices International Limited)
Version: 6.00
Serial Number: m64-1017
Manufacturer: monome
Location ID: 0x14211000```
Error messages! Now we can google!
Found [this](https://discussions.apple.com/thread/7267570?start=0&tstart=0) link which had an interesting comment at the bottom:
> It seems like I could solve the issue on my OS X installation. I had the most recent FTDI VCP driver (2.3) installed and this driver was used for my FT232RL devices. I checked this with kextstat. Then I decided to remove the FTDI driver and use the default Apple FTDI driver. As soon as I removed the FTDI kexts and restarted my computer, the issue was gone.
:open_mouth:
Okay, we're getting somewhere! Did I install custom ftdi drivers at some point on this new box? I remember the olden days where there was no monome_sum/serialosc installer, and I do have fun with atmega chips & their serial opportunities, but thought this laptop was post-manual-ftdi-installation. Let's see…
<img src="/uploads/default/original/2X/c/c4af22259770cd09591b6d5079156cff658fd0eb.png" width="690" height="374">
:octopus: :octopus:
Okay, so let's uninstall the FTDI driver. Found [this](http://apple.stackexchange.com/questions/166906/how-can-i-uninstall-the-ftdiusbserialdriver) way of doing it, but it sounds a bit questionable.
##*tl;dr;*
Shit sucks on el cap 10.11.3. especially the 3d party ftdi drivers. Those come with OSX now, so get rid of them. I just don't know how to yet. Maybe it will fix the issue, maybe it wont. Help hive mind! Help!
