mczetah, you are the hero of my day. Thank you, your advised to-do-list solved my problem of my MOTU 828es not showing up as thunderbolt interface in MOTU Discovery on an iMac Pro with 10.14 (Mojave) with a thunderbolt 2 cable and the thunderbolt2/3-adapter by Apple being the only connection.
"Go to Library/Extensions/ and delete all MOTU drivers", new starts and then installation of latest MOTU drivers did the job.
828 ES Discovery App Problem
Moderator: James Steele
Forum rules
Discussion related to installation, configuration and use of MOTU hardware such as MIDI interfaces, audio interfaces, etc. for Mac OSX
Discussion related to installation, configuration and use of MOTU hardware such as MIDI interfaces, audio interfaces, etc. for Mac OSX
Re: 828 ES Discovery App Problem
having the same issue but do not have that folder when I go to my library. any thoughts? I am on mojave
-
the_wayfaerer
- Posts: 2
- Joined: Wed Aug 05, 2020 11:46 pm
- Primary DAW OS: MacOS
Re: 828 ES Discovery App Problem
I had a similar problem. Even after deleting the driver I had to reinstall them after every boot. This problem only occurred after I had to restore my Mac from a backup, but anyway…
What worked for me was to exempt Motu kernel extensions from the authorization.
To do this, you have to start your Mac in Recovery Mode (Command + R) and then issue the command:
/usr/sbin/spctl kext-consent add KRCLLMGZ2D
KRCLLMGZ2D is the Motu Team ID as can be seen in About this Mac -> System Report -> Software -> Extensions and there MOTUProAudio (in the Signed-By-Section at the bottom)
From my understanding what it does is that it uses every kernel extension from Motu without user consent which is acceptable for me because I would grant them anyway. But I’m sure there are some which consider this a security risk.
You can revoke it again in recovery mode with
/usr/sbin/spctl kext-consent remove KRCLLMGZ2D
What worked for me was to exempt Motu kernel extensions from the authorization.
To do this, you have to start your Mac in Recovery Mode (Command + R) and then issue the command:
/usr/sbin/spctl kext-consent add KRCLLMGZ2D
KRCLLMGZ2D is the Motu Team ID as can be seen in About this Mac -> System Report -> Software -> Extensions and there MOTUProAudio (in the Signed-By-Section at the bottom)
From my understanding what it does is that it uses every kernel extension from Motu without user consent which is acceptable for me because I would grant them anyway. But I’m sure there are some which consider this a security risk.
You can revoke it again in recovery mode with
/usr/sbin/spctl kext-consent remove KRCLLMGZ2D
-
HCMarkus
- Posts: 10404
- Joined: Tue Jan 10, 2006 9:01 am
- Primary DAW OS: MacOS
- Location: Rancho Bohemia, California
- Contact:
Re: 828 ES Discovery App Problem
This is very good information... thanks for sharing it.the_wayfaerer wrote:I had a similar problem. Even after deleting the driver I had to reinstall them after every boot. This problem only occurred after I had to restore my Mac from a backup, but anyway…
What worked for me was to exempt Motu kernel extensions from the authorization.
To do this, you have to start your Mac in Recovery Mode (Command + R) and then issue the command:
/usr/sbin/spctl kext-consent add KRCLLMGZ2D
KRCLLMGZ2D is the Motu Team ID as can be seen in About this Mac -> System Report -> Software -> Extensions and there MOTUProAudio (in the Signed-By-Section at the bottom)
From my understanding what it does is that it uses every kernel extension from Motu without user consent which is acceptable for me because I would grant them anyway. But I’m sure there are some which consider this a security risk.
You can revoke it again in recovery mode with
/usr/sbin/spctl kext-consent remove KRCLLMGZ2D
Unfortunately, comes a bit late for me; I spent more than a day rebuilding my boot drive from scratch after running into the issue you describe... having to reinstall the pro audio driver software to get my Mac to recognize my USB-connected 828es. MOTU was unable to provide me with a workaround. I had gotten lazy, and hadn't gotten around to cloning my DP10.11 boot drive.
The problem got serious for me on a day I booted back into my DP10.11 Mojave boot drive from my DP9.52 Mojave boot drive.
You can bet I now have a clone of my DP10.11 drive. But is is good to know of your workaround.
-
the_wayfaerer
- Posts: 2
- Joined: Wed Aug 05, 2020 11:46 pm
- Primary DAW OS: MacOS
Re: 828 ES Discovery App Problem
A small addition: Also with this kext exemption I described above, the detection of the interface only works when the 828ES is started before the mac or when the mac returns from sleep.
So far, I didn't find another way to detect it, but this works for me for now.
So far, I didn't find another way to detect it, but this works for me for now.