• l_m
  • New member
  • Offline
  • Registered: 2024-10-25
  • Posts: 5

Topic: [Solved] Fireface 800 not working on Mac Studio M2 - macOS Sonoma 14.4

hello everyone,

I start by saying that I've read all the info on this forum about the topic, which would basically recap into this fix:
https://forum.rme-audio.de/viewtopic.php?id=33277

I've upgraded to a new Mac Studio M2 with MacOs 14.4, and there's no way this computer would recognize my Fireface800.
I am using a "Firewire 800 cable -> Thunderbolt 2 adapter -> Thunderbolt 3 adapter" setup to connect the Fireface, which seems to be working for most people here on this forum.

I have reinstalled the drivers and used the 'kernel extension panic medic boot command' to make sure I could Allow the RME driver again in the Security Settings + also run the 'kextutil' command to check the 'FirefaceAudio' extension...
but nothing...the Fireface is nowhere to be seen by the computer

I also went into the System Report to check if the hardware was at least recognized, but absolutely nothing...nowhere to be found in the USB 3 nor Thunderbolt sections...
which I guess it's normal if the driver doesn't work correctly???

Anything else I should try / check?

Please help!

THank you so much

L

  • l_m
  • New member
  • Offline
  • Registered: 2024-10-25
  • Posts: 5

Re: [Solved] Fireface 800 not working on Mac Studio M2 - macOS Sonoma 14.4

ps: all the adapters are original Apple adapters...
the Thunderbolt 2 -> 3 was crazy expensive too...

  • l_m
  • New member
  • Offline
  • Registered: 2024-10-25
  • Posts: 5

Re: [Solved] Fireface 800 not working on Mac Studio M2 - macOS Sonoma 14.4

pps: the driver I tried to install is "driver_fw_mac_341"

  • From: Haimhausen
  • Registered: 2012-04-02
  • Posts: 239

Re: [Solved] Fireface 800 not working on Mac Studio M2 - macOS Sonoma 14.4

The adaters and the interface must be shown in the system report as a hardware connection. Otherwise the adapter is defective.
How to locate your Interface in macOS System Report
https://rme-audio.de/macos-system-report.html

To install the kernel driver on M1, M2, .... you must change the security settings in recovery mode first.
Installation guide
https://rme-audio.de/rme-macos.html

https://rme-audio.de/files/uploads/Cont … -macOS.png

Regards,
Audio AG Support

Audio AG Support's Website

  • l_m
  • New member
  • Offline
  • Registered: 2024-10-25
  • Posts: 5

Re: [Solved] Fireface 800 not working on Mac Studio M2 - macOS Sonoma 14.4

yes sure I have changed the security settings in recovery mode...

so you reckon the adapter is defective? is there any other way I can double check this?

6 Reply by maggie33 (edited by maggie33 2024-10-27 15:06:17)

  • From: Germany, Tuvalu, Poland, Chile
  • Registered: 2021-07-27
  • Posts: 473

Re: [Solved] Fireface 800 not working on Mac Studio M2 - macOS Sonoma 14.4

As Audio AG already posted:

Do you see the TB to FW Adapter or not?

https://rme-audio.de/files/uploads/Support/TB-SystemInfo.png


is there any other way I can double check this?

Try another Mac.

“Do It For Her”
My Gear: Bontempi Magic light Keyboard

7 Reply by l_m (edited by l_m 2024-10-29 13:40:21)

  • l_m
  • New member
  • Offline
  • Registered: 2024-10-25
  • Posts: 5

Re: [Solved] Fireface 800 not working on Mac Studio M2 - macOS Sonoma 14.4

ok I seem to have solved this.

the problem seems to be this new Samsung external SSD + Thunderbolt 4 case that I use for data storage.
If the SSD is connected, there's no way the Firewire->Thunderbolt adapter will be recognized: it just won't appear in the System Info at all...
If I disconnect the SSD, everything works fine and I can finally use my Fireface800 + Settings + Total Mix on this new Mac Studio...

I honestly didn't expect such a problem on a new computer and with a new technology such as Thunderbolt 4,
but lookin around the internet it seems to be not so uncommon actually.
It's mostly due to the way the bus allocates power and resources, especially for old legacy stuff...

It is pretty annoying not being able to use both at the same time, but not much I can do I guess...
It'd be nice to know If anyone else experiences a similar issue, maybe also on a Mac Mini or Mac Pro...

Anyway, hope other people will find this helpful!

thank you!

L