Help. Updated to 10.11.3 lost monome

I updated to the newest El Capitan. When I plug in the monome it does it’s lights pattern. The monome will not appear in max/m4l patches so far. I installed serialosc 1.4 over the previous serialosc 1.4 and restarted. Nothing. Not sure what route to take now.

Booted up from my 10.11.2 external and everything works normal. Guess I’ll restore to that version for now.

(lots of cursing)

will investigate this weekend.

@tehn,
Don’t worry about it. I went back to my 10.11.2 and then reinstalled 10.11.3 and everything is fine right now. Not sure what got screwed up but I’m sure it was on my end. I was installing quiet a few things yesterday and something weird must have happened. :smirk:

@tehn,
Shit. I spoke to soon. It’s not working again. I installed a driver for a Wacom intuos tablet and now it’s not working again so perhaps I found the culprit.

Edit:

Yep,
It’s the Wacom driver for the Intros pen and touch that screws everything up. This is quite unfortunate. I am really liking learning how to use illustrator with the tablet but I can’t have my monome not working!

First world problems.

After reading up on Wacom drivers it is apparent that their drivers often have terrible issues. For now I will have to install the Wacom driver when I want to use the tablet and uninstall it when I want to use the monome.

Hopefully the next Wacom update fixes the issue although it seems like an issue they wouldn’t even be aware of. I wouldn’t think they would have any knowledge of serialosc. I’m not sure how one would let them know about it either as there are no crash reports to send.

One last thing I may try tomorrow is going back to 10.11.2 and installing the Wacom driver. That is the only setup I haven’t tried at this point.

Update:
After installing the Wacom driver for Yosemite everything is working together. (for now) Whew!

Wish I knew somebody on Apple’s USB team. Seems like it would be a very useful person to know.

1 Like

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!

![pls halp](/uploads/default/original/2X/5/54fd37f555f192bb63d10b9331a44a387919f5f3.jpeg)

##RTFM
In the docs:

4.2 Uninstalling FTDI VCP Drivers on OS X 10.9 onwards
To remove the drivers from Mac OS X 10.9 onwards, the user must be logged on as root. Root is a reserved username that has the privileges required to access all files.
Start a Terminal session (Go > Applications > Utilities > Terminal) and enter the following commands at the command prompt:
cd /Library/Extensions
rm -r FTDIUSBSerialDriver.kext
then reboot

Note that rm -r FTDIUSBSerialDriver.kext command needs to be sudo rm -rf FTDIUSBSerialDriver.kext

… jerks.

##I tried

Well. Fuck guys.

What. The. Actual. Fuck.

I’m still getting the zombie grid in the usb device tree and seeing the command line error which you can see in the pink.

Oh this is interesting. With all all this grid plug-cycling (I just made phrase that up), my usb hub decided to nest inside itself and stays nested when plug-cycling! That hub nesting made me realize that the sun came out and I should really just be on my bicycle as I am in over my head.

Fuck this guys. I’m out.

fuck

3 Likes