Thanks, that worked, but a question:

What's the name of the v3.28 kernel extension so that I can delete it from my system rather just block it?

Hello MC. I did that. However, I'll have to re-enable the reduced security because of Rogue Amoeba's Loopback ACE component. How do I prevent the concurrent extension problem in this case?

I apologize up front for a newbie question, but I installed the 407 drivers over the 3.28a and am getting the same pop-up.  I've read through the Read Me for the 3.28, 3.28a, and 4.07 and after looking several times through System Settings and cannot find how to turn off the extensions.  I also did several Google searches.  I also just yesterday updated to the new Ventura 13.3.1 OS which might impact this. If I could kindly ask for some steps maybe more detailed than what I find in the Read Me, I would deeply appreciate some help to get rid of this pop up.  Thank you in advance for the help!

Kind of annoying that you guys don't put some sort of warning about this.

Im not really a Mac wiz by any stretch 

Is this not going to affect any other apps that have enabled kernel extensions with, such as Idrive?

Hi Matthias!

Similar scenario here - M1 Mac Studio (macOS 13.4) + Babyface Pro (203), I went to v4.08 drivers from v3.28.
I only get this message pointing to an existing RME USB kernel extension when starting "Fireface USB Settings".
Besides that message anything seems to be working properly.

So my question is:
Would there be any drawbacks or stability issues if I did not "uninstall" the RME kernel extension?
Since I also need some kernel extensions because of third-party software, I would like to avoid reinstalling the associated software after I have previously turned off the extensions and turned them back on again. 

Thanks for your support!

Thanks - to be on the safe side I have now gone through the procedure, got rid of the kernel extension and successfully reinstalled the other software!

The uninstaller is part of the driver installation and not working correctly due to some wrong behaviour of the latest macOS.

Hi I can't find this either, how did you get rid of the popup? I can't find anything in Security settings

thanks

Re. MADI channels, is the unit connected to USB 3?

Hi, it looks like for the latest upgrade of Ventura 13.4.1 this problem do not exist anymore.
My configuration is: Mac MINI M1 2020, Ventura 13.4.1 and Babyface Pro FS.
I installed today  DriverKit  v. 4.08 (2) over kernel extension Driver v.3.28B and the proces went smoothly. The only thing I had to do after reboot was to allow the Fireface USB Settings app in the Privacy&Security tab.
Reading previous posts I was worrying I will need to delete the kernel extension manually from Library/Extensions and clear the Staging cache using Terminal command, but not. Before running the Drivet kit installer I opened Library/Extension folder and Staging folder to observe the presence of RME kernel extension files. I saw, that after installation finished, the driver kernel extension vanished from both, Library/Etensions folder and  Staging extension Folder . So either Apple solved the problem with Ventura 13.4.1 or the latest installer is more effective at removing kernel extension...

So I didn't experienced "Concurrently running RME USB kernel extension detected" pop-up  after installation and reboot the OS after DriverKit installation over Kernel Extension Driver.  I hope that the installation will work in the same simple way for others

egor,

that means you switched from your old kext driver to the (newer) driverkit driver architecture.

As you didn't write more details, i can only guess:

You do not have to disable your 3rd party kexts in general.

I think, it's just your old (3.28) RME kext driver which is still loaded...? So you have to throw away/delete/uninstall just your "old" RME kext driver. 

Did you check that your /Library/Extensions/ and /Library/StagedExtensions/Library/Extensions/ folders do NOT contain any RME related files?

And yet the point is that after disabling and reboot you can enable it again...

I'm up to 14+ hours trying to figure this out now. One thing I don't understand is why, when I go into the Mac's System Report and look at all the extensions, I don't see a single RME extension? Or at least not one with the letters "RME" in the name? And yet EVERY SINGLE TIME I boot the Mac, I get the "concurrently running extension" dialog. Where is it 'running' from if it doesn't show up in the extensions list? How can I disable something that doesn't even seem to be there? Does the 'offending' kernel extension have a weird name that doesn't include the letters "RME?"? Or at least 'weird' to a non-programmer like me?

And I agree with bbjmm. In the absence of an installer that works properly by removing redundant or outdated code, it would be great to have step-by-step instructions of how to do so. Not instructions that just say "toggle the twizzler," but actually show step-by-step how to do this, and don't assume you're a Mac coder or love to spend your spare time researching the inner workings of the Mac OS. :-p

egor, bbjmm,

a lot of people are trying to help you.

Backup your 3rd party kexts to any location (and maybe also the launch scripts in /Library/LaunchAgents and/or /Library/LaunchDaemons

boot into recovery mode, disable 3rd party extensions (via full enable SIP)... yes, momentary also your other "necessary" kexts will probably not work. anyhow -> reboot -> reinstall the driverkit driver -> reboot again...

Works now?

Than you can boot into recovery mode again and disable your SIP. And your neccesary 3rd party kexts should work again.
Maybe you have to copy/reinstall the kexts to its old locations from your backup. And reboot again.

It would help more to get a detailed feedback what you exactly did and what was the result.
Instead of beeing frustrated, while it seems you have a customized environment/system.
To be clear: you are saying, you are not a tech guy - but you disabled SIP to run your 3rd party kexts...?!?
Maybe, you want to ask Apple if there is a genereal Step by Step guide/pocedure to switch from certain kext drivers to driverkit, while keeping other kexts? Would be nice if you could share it here then.

Yeah! Thank you very much. It fixed this issue too: https://forum.rme-audio.de/viewtopic.php?id=38456

Can't find theses settings...can you give the path?
Tank you

I'm also getting the KMErrorDomain error, but the installer says "success", and I'm not getting the "Concurrently running" error.

Seems like everything's fine for me despite the KMErrorDomain error.

m1 MBP 14.3.1 // SIP enabled // kext-consent 67AK2U2X7M added // RME MADIface Pro firmware v73, driver v4.10, TotalMix 1.93

That error message is not an issue. Neither is the Security Settings warning. Only if the RME driver itself warns about the Kernel Extension. As that did not happen everything seems to have worked. See post #35.

Same issue for me as well. I am on Sonoma 14.3.1, Fireface UFX III with driver 4.10 and TotalMix 1.93.
I can hear audio from all my softwares but not from Brave browser (I am on Brave version 1.65.114).
I tried 2 other audio interface:
Scarlet 2i2 -> no issue
Fractal FM9 -> no issue

yup... reverting to an older version of brave resolves this. Unfortunate timing i guess that the auto-update occurred at the same time as fixing the RME issue..

i will delete my initial post to keep this thread on topic.

edit - this is fixed the the latest nightly build of brave (Chromium 124.0.6367.82) - interfaces with over 32 outputs where not supported correctly , now fixed.

Edit: I just read above and as long as installer is successful then it's a false alarm. Could do without the message, but RME has always been so good about keeping gear alive a long time and updated so won't complain.

I just updated the Babyface driver to 412 on Mac Sonoma. During the install process Terminal opened and I entered the password and I'm getting the "Concurrently running" pop-up error.

Terminal showed:

dj@DJs-MacBook-Pro ~ % sudo /usr/bin/kmutil rebuild
Password:
Checking the auxiliary kernel collection...
Error Domain=KMErrorDomain Code=31 "Error occurred while building a collection: Cannot build collection without binaries as only 1 codeless kexts provided" UserInfo={NSLocalizedDescription=Error occurred while building a collection: Cannot build collection without binaries as only 1 codeless kexts provided}
djm@DJs-MacBook-Pro ~ %

Rebooted a couple times and still get the same "Concurrently running" error. Any ideas what to do next with the above info? Thanks!