#21

@dolza 10.10 might be in that weird conflict zone where i’m not sure how the FTDI official vs AppleFTDI conflict. is there a possibility you could upgrade to 10.12? the alternative is to try installing the FTDI VCP driver and see if it works-- as it can always be removed later.

@laborcamp reboot your system. once booted, plug in grid and type in command line:

sudo dmesg | grep FTDI

it’ll ask for a root password. paste any output here.

@ngwese thanks for the excellent help here. thinking i need to put together a shell script to auto-diagnose as much of this as possible…

1 Like
#22

did the restart
then plugged the arc in
then ran the above script.

Screen Shot 2017-02-11 at 3.53.09 PM.png1570×380 60.3 KB

then opened max
and opened the arc test patch
arc is not showing up.

Screen Shot 2017-02-11 at 3.55.47 PM.png1680×522 78.2 KB

(this is the new arc
with current Max
on a new Mac laptop
running the current OS)

#23

just to be sure-- have you tested with a grid? i don’t want to doubt the arc, but worth cross-testing to rule it out.

that’s not good news that dmesg isn’t showing anything. it should be something like this:

0 [Level 5] [com.apple.message.domain com.apple.commssw.ftdi.device] [com.apple.message.signature AppleUSBFTDI] [com.apple.message.signature2 0x403] [com.apple.message.signature3 0x6001] [com.apple.message.summarize YES]

we’re not even dealing with anything monome-related at this point. the FTDI chip isn’t working, due to some apple-ftdi mishap, and we have to figure out their mess.

#24

smdh. y’all are warriors. best vibes in this battle.

#25

yup.
ran it all again, this time with the grid.
same results.

Screen Shot 2017-02-11 at 5.27.52 PM.png1776×1548 235 KB

#26

Out of curiosity - have you been using the same USB port on the laptop each time? I don’t expect it to change things in your case but what happens if you try a different one (possibly on the other side of the machine)?

–

If you are connecting it directly to the laptop one additional thing I would try is to stick a usb hub in the middle (if you have one) and see if you get any more love out of dmseg or kextstat (this is a long shot but I have seen this make a difference in the past with USB devices in general).

#27

i’m gonna chime in to say i’m having this problem too

troubleshooting rn and will report any solution i stumble across

#28

update: it works

reinstalled serialosc, rebooted, checked activity monitor…finally found it running…lastly, tested a max app and it’s detecting my device again

#29

Yes, I have been testing both USB inputs (opposite sides of the laptop).

Did not try a USB hub.
Will look for one and try to test that as well.

BUT

does this mean that we are “out of ideas” on how to have Max recognize the monome devices?

#30

@laborcamp, in your particular case I’m personally stumped. The only thing remaining that I can think of is to reinstall serialosc. The problem in your case doesn’t appear to be anything Max related - it is lower level, the OS level drivers don’t seem to be getting loaded even though the device is there in the system profiler.

#31

i’m at the edge of out-of-ideas. this is the most extensive FTDI debug i’ve ever done. and to be clear, again, this isn’t any software we control-- very different from being able to update some code and reflash a firmware. this is something specifically broken in apple and ftdi land. serialosc doesn’t even come into play until the device is enumerated by the ftdi/apple driver.

this seems stupid, but you could try installing the standard FTDI VCP driver, which allegedly works though we don’t believe them. but maybe it’ll work for you since your apple FTDI driver is totally asleep.

http://www.ftdichip.com/Drivers/VCP.htm

i’m not incredibly confident that FTDI support is helpful-- in the past they blame the end manufacturer.

here’s the mac install guide if you want to gut the apple-ftdi driver and use the FTDI provided one:

or maybe there is some new magic hidden in there.

#32

wow.

thank you @tehn and @ngwese for working with me through this!

I can’t believe this is happening, honestly, @tehn after the inexplicable and slightly nightmarish experience with TT and Trilogy (dis)communication, now this…

I am not too confident installing that FTDI driver myself. Unless you think this is a simple operation that will not cause ripples in the system.

Question:

Do you think that my problem here might be caused by the fact that the laptop has a custom build installed by my school? I think it’s just a software package of Adobe suite and all sorts of other software we teach, but maybe there is some deeper, low level shenanigans going on? I think I should perhaps bring this up with the IT folks at school and see what they say?

#33

I actually did re-install the serials a couple of times before even posting here, thinking that this was just a simple problem. Since it made no difference, I posted here hoping for the best. :slight_smile:

1 Like
#34

one additional thought. @laborcamp do you know if you are an admin on this laptop? Could you past the output from running the id command in the terminal?

#35

I believe I do have the admin privileges.

In the screenshots above you can see what happens after I typed the password. (Which was nothing, just sending me to the next line… unless something specific is supposed to happen? Should I do some test of that?)

here is what I see when I type “ID” in terminal:

Screen Shot 2017-02-12 at 3.10.48 PM.png1198×332 58 KB

1 Like
#36

…well that looks fine. There isn’t anything different between how your account is setup and how mine is (on my machine).

#37

I guess it was worth checking!
Thank you again for not abandoning me in this dark hour!
:fearful:

#38

here’s the FTDI install procedure. it’s very easy, and was previously required until apple decided to make their own driver a couple years ago.

download and run: http://www.ftdichip.com/Drivers/VCP/MacOSX/FTDIUSBSerialDriver_v2_2_18.dmg

in a terminal then:

cd /System/Library/Extensions/
sudo mv AppleUSBFTDI.kext AppleUSBFTDI.disabled
sudo touch /System/Library/Extensions

(wow, just checked the FTDI docs and they have this part wrong)

then reboot, and hope.

2 Likes
#39

OK.
Will do this in a sec.

(but first I should probably gather around a few small objects for a quick, informal voodoo ceremony… just reaching out to the outer layers of “support”)

1 Like
#40

just to be clear. there are two installers there.
should I run both?

Screen Shot 2017-02-12 at 3.25.08 PM.png710×218 21.2 KB