#43

You’ll almost certainly have to rename the file such that it doesn’t end in .kext (that is what the kernel is looking for). Try renaming it FTDIUSBSerialDriver.kext-disabled instead, then it should get skipped.

#44

I actually named it to “.disabled” but the OSX seemed to have added the .kext suffix again on its own so I figured you just had to have that suffix. I can try again…

EDIT: Yep, just tried it again. I can change the file type suffix and have to enter my administrator password, but then it just adds the .kext again on its own. This is OSX 10.11.5

#45

…that behavior is a preference which can be turned off (don’t remember where) - I’m surprised that Finder didn’t pop up a dialog box asking you if you wanted to use .disabled or keep the existing extension. I’d recommend just using the Terminal in this case to bypass that behavior. Try this in the Terminal:

  • cd /System/Library/Extensions
  • sudo mv -v FTDIUSBSerial* FTDIUSBSerial.kext-disabled (and type your password)

…then reboot. Given what you’ve said I think both the laptop and the mac pro have the same third party FTDI driver installed so this should be done on both machines.

#46

Okay I will try that but wanted to ask a little bit about it first because it says I could delete important system files and I just want to make sure I know what I am doing.
What does command line do? I know the first one just gets the terminal in the correct path, and I think the second one is renaming any file with the word “FTDIUSBSerial” to “FTDIUSBSerial.kext-disabled”?
And if this is true do I need to name the file back to “FTDIUSBSerial.kext” first? Because currently it is “FTDIUSBSerial.disabled.kext2.kext” from all my experiements in renaming it.

Thats for the laptop, but for the desktop computer I dont even had any files that start with “FTDI” in the extension folder and the only file with that acronym in it is the Apple file; the FTDIUSBSerial.kext does not exist on this computer. If the command is to force-rename the file, would it still work if that file doesnt exist?

Sorry for the extra questions, I just want to make sure I know what I am doing and do it correctly so I dont mess anything up!

#47

you won’t mess anything up here-- you can always simply reinstall the driver with the ftdi installer-- but it’s the ftdi driver causing the problem.

it’s more of an issue to accidentally delete drivers that ship with the os x install.

#48

The first command is cd which “changes directory” to put you in the right place.

The second command is mv which “moves (or renames)” files. The “sudo” part on the front tells the OS to increase your permissions level before running the mv command (likely needed because of the permissions on the file in question). The first argument to the mv command ends with the ‘*’ symbol to have it match any file name which starts with that name (I was trying to account for whatever might be left over from previous rename attempts).

#49

Just reintalled the FTDI VCP Driver 2.3 for OSX and rebooted my desktop computer. The problem still persists; once unplugged the device doesnt show up in activity monitor when replugged in.

EDIT: Also tried installing this on my laptop and no change there either. The funky “FTDIUSBSerial.kext-disabled.kext” file is still in that folder and a new one wasnt created (in case that was supposed to change during the install)

#50

I followed tehns advice on the reinstall, and after that didnt solve it I tried your terminal command on the laptop which did successfully rename that FTDIUSBSerial file to end with “disabled” (and now it is actually interpretted as an empty folder). However the issue of not being able replug-in the monome still persists…

any more ideas?

#51

did you reboot after renaming the file? if not the driver is still loaded and likely causing issue.

#52

just to eliminate another potential issue, is it possible to upgrade 10.12, which is proven (sortof) to work?

#53

yeah I reboot after each new attempt

#54

well it has been proven to work on this laptop’s OSX I know for sure because I was using the monome a bunch just last week! I havent had any issues in a long time. and havent upgraded the OS since then. Havent installed anything or changed anything either.

I dont upgrade the OS until the last minute when they release a new one, because I use a ton of plugins and if I fix this problem with an upgrade I’ll likely be on a couple other forums for things that I broke in other plugins ha.

EDIT: But I guess if there is nothing else to try I can just leave the monome plugged in at all times and it should work if I dont unplug it. I just wanted to get everything working like normal if I could, but maybe thats not possible for some reason

#55

ok, i’d try simply removing the FTDI driver entirely, then reboot. this is the command:

sudo rm -v /System/Library/FTDIUSBSerial*
#56

it says that there isnt such a directory…
its okay though, I can always just leave the monome plugged in. I’m not doing live shows right now so this should be fine. Thanks for your help though!

#57

I Wrote in terminal ls -lrt /dev and I read two:
cu.usbserial-m40h0205
And
tty.usbserial-m40h0205
Is it normal?

#58

I have updating my mac to Sierra but monome is been detected on max7 test grid but the light and the controlling not working, all is dark.

#59

here I have this results but the light and the enabling to controlling has failed.
the little pads are on the dark.

ioreg -c IOSerialBSDClient | grep usb
| | “IOTTYBaseName” = “usbserial-m40h0205”
| | “IOCalloutDevice” = “/dev/cu.usbserial-m40h0205”
| | “IODialinDevice” = “/dev/tty.usbserial-m40h0205”
| | “IOTTYDevice” = “usbserial-m40h0205”

monome 40h, macbook pro with Sierra without FTDI driver

#60

This is the latest update of the situation:
So, after some works with Terminal, finally if I plug and unplug the USB cable from monome 40h and with the patch in max7 “grid how to” loaded, the mac book with SIERRA successfully connect the device, without having to reboot the machine as before .
But the monome does not work well, because:
do not turn on the lights of the pads when I press on, which corresponds to incorrect operation because it does not receive messages from MAX and does not send messages to MAX.
What do you recommend, what can I try?
Excuse me for the situational crowds
Please, Someone can help me?

#62

please don’t repeat or cross-post-- it doesn’t make responses happen faster and it clutters up the view for everyone else.

you mentioned you were able to get it fully working with another computer, correct? so we can eliminate the possibility of a hardware issue?

at this point you’re seeing your device in the dropdown of the grid-howto maxpat? have you clicked on the dropdown to select the device?

#63

Excuse me tehn,
Now I am testing monome on IMac of my friend as yesterday and the lights-pads don’t working again, all are in the dark.
The grid-howto see monome but it doesn’t work.
Why?