Pro Audio Driver Fix for OS X 10.10 Yosemite for M-Audio, NI, and more

Posted on October 04, 2014

If you’re using OSX Yosemite and are using professional audio sound card, you’ve no undoubtely discovered that the device will not work and you can not listen to anything. I have a very simple fix to allow the drivers to load. I have tested this with the following devices: 

  • M-Audio Profire 610 (Firewire)
  • Native Instruments Komplete Audio 6 (USB)

The fix is very simple. From the command prompt, enter the following:

Also, if you’ve found this useful, please take a second and follow me. Just click on the button below.

Reboot. And you’re done!

Related Posts

  • James Mahon

    hi will this work for the maudio firewire 410

  • Matthew McDonald

    I have the same question as James Mahon. Firewire 410 work as well with this fix?

  • yes I have same problem with firewire 410 this work on it?

  • Guest

    I don’t have a 410 so I can’t answer that… there’s really only one way to find out. Please try it and let us all know.

    • Adam Onionman Kane

      i tried with my firewire 410, it didnt work.

  • I don’t have a 410 so I can’t answer that… there’s really only one way to find out. Please try it and let us all know.

    • Jonas Zaidys

      Hi all, not managing to make this work with 410 as well. Funny thing, I have a new mac (always had yosemite) and it was working fine, until I (regret) opened the pref. pane, now, even with sudo command vram and all, does not work :/

      • Pere Parramon

        I’m on the same page! When I opened the pref. pannel, it crashed out…. Did you solve it???

        Thanks in advance!!


  • Javier Iván García Garza

    Worked for me (PROFIRE 2626)

  • Dimitri

    NI Audio 10 here, did this and works! Thanks

    • what did u do

  • Marcus Kihn

    I want to do this but am nervous about the warning. I have a Profilre 2626 and it seems that it worked for Javier. Thoughts?

    • What warning? If you think there might be a problem, back your drive up.. If it worked for one person it will probably work for you…

      • disqus_zO5kUE1T9g

        I think he means the “sudo” warning. Terminal outputs that warning the first time you use it.

        @Marcus: Sudo is just a command that lets you act as the machine admin so to speak.

      • Guest

        Vine can you help me? i tried entering the code but when i restart with te firewire audiophile connected my macbook keeps re-starting one time after another is there any way to undo the command on the terminal ( if i restart without the sound card connected everything its ok)

      • Manuel Aburto

        Vinny! hi there can you help me? i tried entering the code but when i restart with te firewire audiophile connected my macbook keeps re-starting one time after another is there any way to undo the command on the terminal ( if i restart without the sound card connected everything its ok)

  • Chris

    I have a 2626 and it worked for me. Thanks to whoever did this you are a proper stand up geyser (i.e. nice bloke).

  • Audio 10 is working great thx again for the code

  • Ricardo Verdelho

    Hi guys. I am try to do that, however the “Terminal” won’t let me type my password to confirm. Am I doing something wrong? Thanks for the help.

    • Ricardo Verdelho

      Ok, i figure that out. We just type the password, even if the cursor is not moving. And by the way… it worked with M-Audio Firewire 2626. Thank you very much. 🙂

  • Chinchepos

    Thanks guys!!! My profire 2626 is really works.

  • Ricardo Verdelho

    Hello again,

    I have a studio and work with an M-Audio Firewire 2626 / Cubase 7.5.
    With all the worries about the drivers, I decided to buy a new Hard Drive to make the respective tests. Don’t want to mess with my work HD’s (never do that!).

    The fact is, the code REALLY works. I have all the input/output on Cubase, and it works perfectly on standalone and iTunes.

    I don’t have a 410, however if you guys have a Hard Drive to make some tests, try the code. I repeat: don’t mess with your work Hard Drive…

    By the way, my process of install was (made on a new HD):
    1. Install a fresh copy of Mavericks;
    2. Install 2626 and cubase drivers (on Mavericks);
    3. Install Yosemite.

    Best regards

  • Christophe Proust

    Don’t fully work with M-Audio FireWire Audiophile.
    Sound ok but no Pref Pane

    • skippingrock

      Not working with my Audiophile either. I’m very sad as I just got my turntable and preamp set up and was looking forward to being able to digitize some of my old childhood LPs for my kids to be able to listen to in the car…

      @Vinny Troia can you give us some background as to what is trying to be done with your terminal command? Perhaps the command needs to be modified depending on which M-Audio Firewire device is used.

      I can pump out audio out of my Audiophile through the headphone jack, but I can’t change any of the settings because the M-Audio Firewire app doesn’t load as we all know.

      Okay folks, I just had a wild idea, it is not ideal, but still better than nothing. Perhaps we can try having a system installed on another drive that we know works with the M-Audio Firewire devices.

      Then fire up the Settings application there.
      Change the settings to what we want them to be.
      Reboot into Yosemite and see if the set-up keeps for the device.

      Perhaps we might have to go a step further and go and grab the saved m-audio and Apple audio preferences files on the working system and copy them over to our Yosemite system;

      Reboot into Yosemite and perhaps run a repair of permissions on Yosemite (to ensure permissions are correct for the system)

      Reboot again and then try to see if your m-audio firewire device works with the set-up that you want.

      Of course this would only be useful if you only need to set-up and use the device and not make a bunch of changes while using the device. But you could use the presets in the settings app to change to different set-ups if you need to switch again (and repeat the above).

      It is just a thought that I’m going to try when I get a chance, but I encourage others that are still having problems to try this too and report back if this works for them.

      Not ideal, but better than nothing.

    • Adrian Cuenca

      same here

  • Matt

    Help! I’m working with Ozone on a Mac Pro and just downloaded Yosemite 10.10. My OZone no longer works. What do I do? There is no driver for 10.10

  • disqus_zO5kUE1T9g

    I just tried and reset but still not working (profire 610). Has anyone done this on a clean Yosemite install (not an upgrade from Mavericks)?

  • klanklab

    does this work with the S4MK2? My hardware gives a click when i load a song.

  • perish

    This has worked for me with an M-Audio Firewire Solo. I have tested this via my browser, Audition and Logic Pro. Can’t thank you enough

    • Marios Georgiades

      Hey Perish can you explain how you got your m-audio firewire solo to work on yosemite and logic pro? Which fix has worked for you? Is it sudo nvram boot-args=”kext-dev-mode=1″ ??
      This hasn’t worked for me.

      • dc_martins

        it worked for me, thank you so much!! been looking for a solution for months now.. tks tks tks
        Marios, I just opened up the terminal window and pasted the command line. after a few seconds I had to password confirm the action, and that was it.

        • Marios Georgiades

          Thanks for the reply! I switched back to Mavericks for now because somehow the command doesn’t work for me. The weird thing is that if I go to “Sound” in system preferences it is detected as a firewire 410 instead of a firewire solo. Does the preference panel work in system preferences?

          • dc_martins

            I see.. in my case, the preference panel was about the only thing working properly, and the m-audio graphic interface would always freeze before loading.

            (might have nothing to do with it, but before this solution I did tried installing several other firewire drivers).

            did you try deleting the driver and installing it again?

            good luck, hope it eventually works for you.

          • Marios Georgiades

            Thanks again!! I think I will give it another shot since I have cloned my main drive for easy recovery.

          • Marios Georgiades

            It works! But the preference panel doesn’t work. Can you check if your pref panel works after you fixed your driver? I don’t really mind though because the only case I would need to open that is to enable spdif. I can live without spdif 🙂 But anyway in the future I plan to get a UAD-2 once I can afford it

          • dc_martins

            oops same here.. no GUI for the m-audio firewire solo :-/

  • Edgar Bumpers

    Thanks for this workaround. I want to confirm that I did this using Yosemite 10.10.1 this morning and my M-Audio Ultra device now works on my Powerbook 13.

    • Carlos Duran

      Do you use any adapters between your profire and your powerbook?

      I have not been able to make it work. I got a new mac which only has
      lighting ports and usb 3.0. I had to connect two adapters to be able to
      connect my profire to my Mac. I think that is the reason why is not working for me.

      My adapters are: firewire 400 to 800 adapter, firewire 800 cable, firewire 800 to thunderbolt adapter…

      • Alex

        Hi i have exactly the same setup it was a bit of a nightmare to get working. Unplug your device and cables. Download and install this Driver then turn off your computer. plug it all back in and turn on the computer. worked for me

        • Guest

          such old driver? you proposing to use 1.10.3, and the newest is 2.4.2, have you tried newest one?

  • divine

    my ProFire 610 is NOT supported under Mac OS 10.10 Yosemite. can some one help me..?

  • kraVal

    hey: I’ve installed Yosemite and now my M-Audio Ozone is not working anymore. I updated Logic Express 9 (went fine) and entered the code above twice in my terminal. And I typed in my password. Still, my computer won’t find the sound divice.
    Any suggestions?
    Could you provide screenshots from each step entering the code, maybe? (I feel so dump).
    Thank’s a lot in advance!

  • Manuel Aburto

    Help!!! i tried entering the code but when i restart with te firewire audiophile connected my macbook keeps re-starting one time after another is there any way to undo the command on the terminal ( if i restart without the sound card connected everything its ok)

  • Marios Georgiades

    Has anyone gotten the m-audio firewire solo to work under yosemite using the sudo nvram boot-args=”kext-dev-mode=1″ ? I can see the firewire solo actually shows as a firewire 410 in system preferences, sound… but I get no sound output when I play something. Yosemite works much faster than mavericks and I really want to get this working!

    • josiahtam

      I just got it to work. Copied the command line into Terminal, hit enter, entered password. Uninstalled the driver and re-installed it (following the instructions to unplug, shut down, plug in, and then turn it on. Worked without having to do anything more once the computer was up and running again. Running 10.10.3 btw

  • Avtandil

    Just tested with Firewire Solo – no visible results.
    It was working before with driver from M-Audio, but Pref Panel was freezing – after entering code – is the same.

    Joining to other people – Vinny could you give ‘undo’ command ?

    • josiahtam

      I just got it to work with my Firewire Solo. Copied the command line into Terminal, hit enter, entered password. Uninstalled the driver and re-installed it (following the instructions to unplug, shut down, plug in, and then turn it on. Worked without having to do anything more once the computer was up and running again. Running 10.10.3 btw

      • Where can you find the latest drivers? I’m on 1.10.5 and I can’t open the M-Audio preferences. It freezes.

  • San-Borneo

    It works fine with logic, but still no pref panel. It’s sad, ’cause I need it very much.

  • Joe

    Unfortunately, this didn’t work for me. I have a ProFire 610 and am running 10.10.3.

  • Jonathan Vaughan

    I have Yosemite 10.10.3 and an M-Audio Ozone and this fixed it for me. Thank you!

    • milingo sutera

      are you still on yosemite or maybe on el capitan ? i’m afraid to upgrade and break the compatibility of my ozone on it

    • milingo sutera

      I just upgraded on El capitan , and my ozone works , weird but work well , only the panel of maudio on the OS X settings seems no firmware or device connected , instead the audio card and the keyboard works and works well with all my daws . Now it is recognized like a generic “ozone” and not “m-audio ozone” but i repeat, it works !

  • Thank you for this. I’ve got my M-Audio Firewire 410 working perfectly with OS X Yosemite 10.10.3.

    My process was as follows:

    – Install the drivers from
    – Restart
    – Execute sudo nvram boot-args=”kext-dev-mode=1″ in the terminal

    – Restart again and then it worked fine.

    • Suzie

      Newbie here, what is the terminal? I have a 2010 Mac desktop and an M-Audio 410 Firewire. OS X Yosemite.

      • Goto your “Applications” folder, then into “Utilities” and you’ll see the Terminal application. Good luck.

  • rramin

    -My FireWire 1814 was still working with El Capitan Beta 2 on my Mac Pro 2013 but
    It doesn’t work any more with El Capitan Beta 3: Apple has activated the rootless.

    -Only M-Audio signed extensions are accepted and the rootless doesn’t let any non signed extensions installation in the system folder and it’s not sure M-audio will ever update/recompile and sign old extensions…

    I think about 4 solutions when 10.11 will launch:
    1-Don’t update to 10.11 (too bad but it works)
    2-Replace your M-Audio hardware and choose another reliable manufacturer (cost money)
    3-Wait for M-Audio to update their drivers (Dream ?)
    4-Find a registered developer able to realize an universal alternative driver (don’t know one)
    5-Find a functional hack to force install the old working driver like the one in this blog (hope)

    Finally, if M-Audio doesn’t update their drivers for new system and old hardware, maybe it’s because they want people to buy their last products.
    If it’s true what will happen with 10.12, 10.13 etc : people will have to change their hardware again and again ?

    • Felipe Lacerda

      how you could switch between configuration tabs on the control panel?

      • rramin

        The control panel was not working for me in Yosemite (freeze): so to enter my setup I used to edit directly the values in the M-Audio .plist file…

        I think that anybody thinking to upgrade their OS to El Capitan should resign because there is no future with the old drivers.

        I am no more on Yosemite now, I am on El Capitan and old M-audio drivers will never(and don’t) work anymore as you can see in the WWDC keynote at 20:16

        “Extensions have to be signed with a developer ID for Kexts certificate install into Library/Extensions
        kext-dev-mode boot-args is now obsolete”

        Excerpt from :

        “In OS X 10.11 System Integrity Protection, also known as rootless, will prevent the modification or removal of certain system files even by administrative overrides. This means that no user, application, or process will be able to write files or modify files in the root System folder or the /bin, /sbin, and /usr directories, which are hidden by default in OS Xs Finder. The /usr/local folder will still be accessible though.

        By locking down the core system Apple will scupper the attempts of any malware to gain access to files, folders, running processes (software that manages tasks in the background) and system apps, such as the Finder and Dock. This might lead to some changes in third party apps you use regularly, for instance, prior to El Capitan Dropbox showed sync status in the Finder, luckily this wont be gone completely, Apple has added generic code to support it.

        Similarly Kernel extensions will still be allowed, but developers will need a valid certificate from Apple to get them cryptographically signed.”

        I know it doesn’t help, sorry.

        • Felipe Lacerda

          Ideally, a developer decided this, I believe it is not much to do for those who really know about development drivers.

          In the latter case, at least Windows 10 is running smoothly.

          • Felipe Lacerda

            Do you know what the latest version of firmware and bootloader?
            Here it is as follows:

            Bootloader: 2004/03/30 02:59:09
            Firmware: 2007/07/13 08:04:40
            Hardware: model: 83 version: 1

        • k8l

          Hi! Could you tell me more about editing plist to set routing ? Everything is working well with my Firewire 410 except control panel freezing. Which file do you actually edit ? Thank you very much.

          *EDIT** : found /Users/{username}/Library/Preferences/com.m-audio.device-settings.firewire.plist

          • rramin

            Yes you found it: /Volumes/Your HD/Users/Your user name/Library/Preferences/com.m-audio.device-settings.firewire.plist
            I was away and not able to reply before, sorry.

          • Troy Gardner

            what did you edit the file with, and what did you change? the file looks mostly like binary to me using Vim.

          • Troy Gardner

            oh nevermind,use textWrangler opens it as an xml file ok,

            It seems after you save them, you have restart the system to get the settings to stick, at least for me, before the sound card driver recognizes them.

            on OS 10.10 (yosemite) the card works with applications for me, just as mentioned control panel doesn’t. BUT the levels and mute can be controlled (but not the routing) via the Applications> Utilities >Audio Midi Setup and editing the plist file works with routing. CAVEATS. I mentioned that you have to sometimes restart for the settings to take effect, the firewire driver often is hung at this point making changes anyway.

            Second, when restarting, sometimes I have to unplug the M-audio box as it *sometimes* hangs with a white screen and won’t progress. Thankfully restarting isn’t something I have to do often.

            If you google the maudio control panel you can see screenshots which can help you figure out what the various sections of the plist file do. While the other keys are more self explanatory, You can apprarently mess with routing under this key:MASWreturnRoutingV2


            that’s top from bottom

            1 channel 1 and 2 IN
            2 channel 3 and 4 IN
            4 channel 5 and 6 IN
            8 channel 7 and 8 IN
            16channel – not sure? spdif?

            Where the values are this

            1 = output bus 1/2
            2 = output bus 3/4
            4 = output bus 5/6
            8 = output bus 7/8
            16 = output bus – not sure ?9/10?

            these values are bitflags for the routing and can be boolean logical AND together (e.g. 4 & 1 = 5)

            so for each input to be on it’s own output, (which works great for my 5.1 surround sound setup, playing dolby with VLC and MacBluyray)

            1 channel 1/2 in => output 1/2
            2 channel 3/4 in => output 3/4
            4 channel 5/6 in => output 5/6
            8 channel 7/8 in => output 7/8

            if I wanted to route the 5/6 channels to the 1/2 channels for 4 speaker.

            1 channel 1/2 in => output 1/2
            2 channel 3/4 in => output 3/4
            5 (4+1) channel 5/6 in => output 5/6 and 1/2
            8 channel 7/8 in => output 7/8

            that’s all I really figured out, but that’s good enough for me to use the card as it was prior to the upgrade. I will not be upgrading to El Capitan though cause I don’t believe the sudo nvram boot-args=”kext-dev-mode=1″ mentioned on this page works there.

          • DeLeon

            Hey, I have a M Audio Fast Track USB , 10.10.5, driver shows but “doesn’t have any outputs” will this help me?

          • rramin

            Troy, I’m afraid that you will have to find the right parameter by yourself
            in the .plist file, sorry I can’t help for this because I don’t know which one.

        • milingo sutera

          But in that video is showed how to disable the SIP to work with an unsigned kext

          • rramin

            No, sorry.

            SIP is blocking ALL installation in system folders, disabling it allow ONLY signed kext installation…
            The M-Audio driver we are talking about is NOT SIGNED !
            M-AUDIO is not registered as an authorized dev for APPLE ???

            The correct link is

          • milingo sutera

            Sure ? He says that because the sip require all the kext to be signed , it come in the way of developers that want to test with unsigned kext and the entire sip can be disabled ,(minute 21.19) this is what the ceo says , maybe i’m not in to this like an espert , but this he said . Ora maybe i want to believe 🙂

          • rramin

            Yes, you can install an unsigned kext after disabling SIP but after that if you re-enable SIP the kext will not load…

            Do you know that apart from what is said in the video I have tried all
            these solutions in the real life since the very first beta of El Capitan ?

            Today I think it’s not a good idea to always leave SIP disabled in El Capitan.
            The best solution is to have SIP enabled and a SIGNED kext or keep
            using Yosemite.

            I know it cost money for a developper but maybe M-Audio can afford it ?

            Anyway the M-Audio kext and control panel even with SIP disabled
            (or a signed kext) doesn’t work (freeze and/or crash), and it’s the real problem, the initial subject of this thread… 🙁

          • milingo sutera

            I know i know , but disable for ever the sip is not a drama . The security of your mac remain password related like was until now . More you can disable partially the sip only for the kext feature . This post’s argument is not only your audio device but all the device of m-audio that want work like mine for example , it is the ozone that work in yosemite with the upper hack and maybe , i repet maybe on el capitan with sip partually disabled

          • rramin

            So the 2 solutions to install and use the kext are:
            1-With Yosemite :
            sudo nvram boot-args=”kext-dev-mode=1″
            2-with El Capitan :
            Disable SIP partially or fully.

            The 2 solutions to install and use the Control Panel:
            1-For the settings:
            Disable SIP partially or fully to be able to modify each time the Pref file.
            2-For the freezing:
            Hope M-Audio will fix it.

            I think that this useful post could be useless if M-Audio:
            -Had signed kext,
            -Control panel not freezing and up to date.
            -Really took care of users.
            So it should not be necessary to tinker and hack, pros music users have no time and skill to do that: they want to produce music I think.

            Anyway I don’t want to partially or fully disable SIP.

          • milingo sutera

            almost totally agree this time , users or music producers must concentrate their strenght to make music , i’m gettin mad following apple’s news …not to partially disable the sip instead is a personal choice but disabling it is very similar to yosemite or maverick security settings when you wanted to install non signed softwares (the same mode macs work until now) , for all the rest i repeat i’m agree with you . at the end i will risk my music system upgrading to el capitan , i hope my m-audio ozone will work well like with yosemite ( and the last official driver for ozone came from leopard …)

          • milingo sutera
      • rramin
  • josep cullell ramis

    Hi I have Yosemite 10.10.4 and I can t seem to find the drivers for it in the M-Audio webpage. I have the firewire 410. Is there any way I can make it work? thanks

  • Ed Kellett

    Does anyone know if this works with a Firewire 410? And if so, is there any downside or risk?

  • nk

    “kext-dev-mode=1” is now obsolete in latest El Capitan, you should do this instead –

  • Frank Grohl

    MacBook Pro end 2007 with Yosemite and MAudio Firewire 410. Finally I was able to make it work! I deleted manually all the files of the old driver (you can find many howtos online), then I applied the sudo nvram boot-args=”kext-dev-mode=1″, finally restarted the PC and installed the latest version of the driver. The control panel doesn’t work, but you can handle all the controls of your soundcard through your favourite DAW (I used it with Logic10 and Ableton Live 9). You can enable the SPDIF in-out in the Midi settings of Yosemite too. I know this isn’t the best but now I can’t afford the expenses for a new soundcard so this works in the meantime. Thank you.

  • moshin

    Thanks! This allowed my driver to load for my Project Mix i/o in yosemite… BUT>>> The driver/control panel freezes anytime I try to change anything…. I keep reading thisis a door stop, but i hope not 🙁 Anyone??

  • Sebastian Podlesnik

    Have anyone tried Ozonic firewire keyboard-interface? SUDO command doesn’t work. Any luck?

    • Sebastian Podlesnik

      No, I also wasn’t able to make it work. I love Ozonic though. There is nothing like it anymore out there.

      • Sebastian Podlesnik

        Ozonic is Firewire and Ozone is USB. Could that be a problem?!

  • Alia Vox

    i bought a focusrite pro saffire 14. case closed.

  • Guy Audio

    I posted some clear instructions for how to get M-Audio’s firewire driver working on Yosemite and El Capitan. Tested with the ProjectMix I/O. I hope it saves someone a few hours of headache.

    • Sebastian Podlesnik

      I can’t make it work. That is just crazy.

      • Mark at Argent Cove

        Are you trying to get the ProjectMix working? I just did this last night and it’s working perfectly… audio, midi, surface control, everything. Did you follow the instructions exactly? Did you get stuck on anything?

        • Sebastian Podlesnik

          It’s about M-Audio Ozonic Firewire interface with keyboard. I did follow the instructions but Ozonic control panel just dont open up. Apart from that, Ozonic works. I just can’t control it from its Control panel.

          • Mark at Argent Cove

            Yah, the control panel doesn’t work for me either but I can do 99% of what I need from Reaper, Audition, and Live so I’m good.

        • moshin

          Does this allow the control panel to work too??

    • moshin

      I need the control panel to function as well. does this allow that?

  • Nick Ravenscroft

    Brilliant, thank you, that’s got my Lightbridge working. Total genius!

    Only probs is as the control panel doesn’t work, so there’s no way to get the device to slave to external clocks… When I changed that setting on an another, earlier mac, I found that it doesn’t stick on startup…

    It would be cool to be able to go into the driver and make the interface just start up as a slave. There must be a way to do this.. alas, a giant leap for my knowledge of code… It can’t be that difficult though is it?

  • jaz wav

    Got mine to work – I had just bought a mac mini with Yosemite preinstalled. Like everyone else plugged in M-Audio FW 610, no 610 in audio devices. DANG IT!!! I also noticed the blue light wasn’t on and I kept hearing low constant click. SOLUTION: Downloaded and installed “M-Audio_ProFire_Series_2.4.4.dmg” by clicking on the file. When the install panel appeared with the installer and uninstaller options I right clicked on the “installer” went to “open with” and selected “installer(default)”. Clicked “Continue” and installed as said; shut down computer just as it suggested at end of install; “The kicker” Connected and plugged in FW 610 external power supply( that I didn’t need with previous mac OS versions); turned it on until the blue light was up. Then turned on the mac mini and checked Audio devices…. and there it was!!!!! Like uz guyz I been fighting’ this for weeks….. Hope this works for uz out there!!!!

  • mdc

    I have managed to get a Firewire 410 working on El Capitan by installing a combination of..



  • Ryan Arno

    got it working on a m-audio 410 loaded 2 different drivers at the same time using this method. working on 10.10.5 2015 macbook pro 15 inch using thunderlboldt adapters. had it powered with powe adapter

  • Shai Yammanee

    I managed to get the Firewire 410 working on El Capitan (10.11.2)

    You have to disable the System Integrity Protection before it is recognised.

    You have to restart in Recovery mode ( Hold down “CMD+R” on restart), open up the terminal and then type in “csrutil disable”

    Then start up your computer normally.

    I was still unable to install the M-Audio drivers, but at least I am able to use the hardware again. Not sure why, but I’m not complaining.

    It is working in Logic Pro X for playback and recording.
    I have no issues with microphone inputs or midi input. All the outputs seem to be working as well.
    I couldn’t be happier. 😀

    I hope this works for you as well.

    Here is an article on how to disable the System Integrity Protection, and why you should and shouldn’t do it.

    All the best.

    • Vahan

      I did disable… Then find a driver and installed but didnt worked… Did you do anything alse from these?

  • Global Hiccup

    Thanks to everyone for all the useful information on this page. These days you have to be a detective to create digital music!

  • Manu Chaman

    Hi everyone, i have the solution, it works! If you are owner of M-Audio Firewire Solo sound card and you upgrade to OsX El Capitan, follow these instructions: for me, on my MacBook Pro and my iMac it works. Thanks a lot.

    • Rickson Medeiros

      Hey I use Yosemite 10.10.5 M -Audio 2626 resolves to me? Or have to migrate to El Capitan ?

    • James Cunningham

      This worked perfectly for my FW410! Running Logic X on El Capitan and my interface works a beauty 🙂 So pleased this trusty durable interface will live on! Virtually zero latency, tons of outputs, phantom power inputs with gain and pad – they don’t make them like they used to! Make sure you’re running El Capitan because the terminal script you need doesn’t register on Yosemite… I should also add that the control panel doesn’t work but it’s pretty useless so never mind

      • Tim Tapsell

        Hmmm…this didn’t work for my FW410, on Logic X, on El Capitan. 🙁

      • Vahan

        which driver u used for instal? Mecause my driver coundt install

  • Tom Richardson

    Hey guys, after much frustration and a little fidgeting, I got my Edirol FA-101 up and running on 10.11.2 el capitan. THANK YOU sooooooo much for this fix, updating just to have my stuff not work is such a pain. Here is what I did to get it working:
    – turned off System Integrity Protection (SIP)
    – used ur terminal command
    -verified my device works
    -turned SIP back ON.. and it still works!! so no need to leave SIP turned off.
    (this is an overview, not a step by step, just to clarify)

    • Vahan

      I did the same thing with same audio device, but which driver u used ?
      Mine didnt worked…

      • Tom Richardson

        For the red edirol FA-101, there is no osx driver. OSX has handled this device natively for as long as I have used osx. Since 10.5.8 or something, I just plugged it in and it appeared in AMS. I should also say that it did take a few tries to get this fix to work…

        • Vahan

          So yes i have red one… İ tried this steps but still i coudnt see my device at sound preferences… When i plug in device, its red button (firewire) flashing… It was full light at my windows comp…
          So which steps do you suggest to do for me?
          Thank you very much
          I am using 10.11.3

  • Danny Oliveira

    Yo guys! Did this setup on a recent Yosemite install – – don’t care for the panel, audio was working 100%. I’m on El Capitan now. Disabled SIP and etc, ran through all of the setups out there and i just can’t get the M-Audio FireWire Kernel Extension.pkg to install. And if i do it manually, i get this shit here. Annoying. I’ve checked SIP status using “csrutil status” on terminal and it is disabled. Any clues to what i should do? 🙂

  • Pippa Caole

    Hi – is this a fix for the problem of the firmware drivers never installing to the lightbridge during initial installation please? I would really appreciate feedback.

  • Fernando Luna

    Hello everyone! I have a presonus firepod that is no longer working with el capitan, any solutions? Thanks!

Contact Us

Have a question? Send us a message. We'll get back to you soon.