Please be more specific:

1- What System are you on? Leopard (which version)? Snow Leopard?

2- Your Mac specs: model? RAM? Processor?

3- What FF? 400 or 800? Driver version? Firmware?

The Fireface in OSX doesn't actually mount or un-mount. It just auto-launch its two applications when turned on: TotalMix and FireFace Settings.
To remove the unit, just quit the latter apps, turn down speakers volume and switch off FF.

As to Core Audio hanging forever forcing users to restart the computer:

I'm one of those iMac users who had to lean on workarounds to get their audio system working properly (2 years now), but STILL I believe that the one and only culprit for this sometimes unreliable FF/Mac relationship is : Apple FIREWIRE BUS along with its kernel extensions.

I don't want to spread mis-infos, this is just my experience and my point of view, consolidated after many different "geeky", "risky" system intrusions.

My story (briefly): been working flawlessly (Logic 8.0.2) on Tiger 10.4.11 and on Leopard (till version 10.5.4 !!!) using the FW 6pin/9pin cable workaround since first posted on this forum. Not a problem whatsoever.

Since Leopard 10.5.5 on, including Snow Leopard: FF400 and external FW drives no longer recognised and mounted after waking from sleep-mode; Core Audio freezing, System Profiler unable to detect its own firewire ports. Full immersion into reading and decoding logs, result: weird behaviour as to the system FW .kexts (5 files).

Analogic solution (don't try this at home if you don't know what you're doing!):

Installed FW.kext "package" from Tiger 10.4.11 Installer through Pacifist, in order not to come across permissions problems.
Everything went back to normality: FF400 and Ext. FW HD regularly seen and launched/mounted.

More details to come.
I'd like to read replies from RME guys first, as to this Frankenstein-like workaround.

Still I have to rely on the iMac/FF400 workaround, but hey, this has always worked fine actually.

Apple FW hardware-chipset caused and still causes problems to many RME users, now I'm pretty sure that the whole interaction between chipset and FW kernel extensions has to get involved to give a more in-deep analysis spectrum.

As already stated: just my experience, don't take it as a solid-solution or even semi-solid-solution.

EDIT - For the sake of information:

Here are the 5 .kext files I modified to get FIREWIRE Bus fully working in Snow Leopard:
Installed through Pacifist v.2.6.3 from Tiger 10.4.11 Installer package.

1- IOFireWireAVC.kext
2- IOFireWireIP.kext
3- IOFireWireSBP2.kext
4- IOFireWireSerialBusProtocolTransport.kext
5- IOFireWireFamily.kext

Still studying the IOKit framework (original SL version) and its behaviour to check whether it'd be better to install Tiger 10.4.11 version as well in order to "sync" it to the modified kexts.

Still planning to go and try to install FW kexts files from Leopard 10.5.4 (the last who seemed to handle my iMac FW Bus properly), just to prevent System Logs activities to warn me ('though causing NO problem at all) about some version/architecture discrepancy. ...guess why...

Regards.

Jesus!!!!!

If this turns out to be true...

Also regarding the just published information from matthias about the new windows drivers.
What the hell apple and microsoft are doing with firewire

Some info:

http://reviews.cnet.com/8301-13727_7-10 … g=mfiredir

http://discussions.apple.com/message.js … ID=9987731

You're welcome. journey

Hi there,

Everything's ok running FW kexts from Tiger 10.4.11 - See my previous posts.

Restored original kext FW files from Snow Leopard (10.6): each and every problem showed up again; basically everything you guys are complaining about at the moment.

A step forward: I'm currently working fine after installation of these kernel extensions from Leopard 10.5.0.pkg through Pacifist:

1- IOFireWireAVC.kext
2- IOFireWireIP.kext
3- IOFireWireSBP2.kext
4- IOFireWireSerialBusProtocolTransport.kext
5- IOFireWireFamily.kext

So far: NO "wake from sleep" issues, NO need to restart my iMac before turning on my FF400, NO Core Audio freezing (requiring forced Shut Down) when: [switching OFF FF400/ unprecised amount of time/ re-switching ON FF400].

a- Console app. no longer warns me about discrepancies as to the above files.
b- System Profiler no longer hangs searching for FW ports.

Will try 10.5.8 FW kexts later http://discussions.apple.com/thread.jsp … ;tstart=15 although I remember this OS version not working flawlessly as to these issues, at least in my case.

AGAIN: don't take it as a permanent solution, I'm just doing some experiments.

For those of you who feel like trying, post your comments and requests and I'll try to go more into details. Please be as exhausting as you can when describing your problems.

I believe a brand new topic would be required for such an issue: http://www.rme-audio.de/forum/viewtopic.php?id=6457

Regards.

Hi Urknall,

well, reading here and there, this micro-tutorial gave me some hints: http://reviews.cnet.com/8301-13727_7-10 … g=mfiredir

I just thought: it's doable and worth a try...it worked.
Never had a problem under Tiger, nor under Leopard (till v.10.5.4): again, my iMac's FW hardware-chipset was to blame for other reasons (i.e. not seeing FF400 through FW400 port, a well known problem), but, after relying on the 6pin/9pi9n workaround, it had surely nothing to do with the latest strange FF400/OS interaction since I upgraded to SL.
Given that it was a software issue, why not trying to start "manipulating" a bit...:-O

My Mac still boots up 32 bit Kernel Mode, not allowed to go 64, waiting for a firmware update.
In theory you shouldn't encounter issues as to 32 bit FW kexts dwelling in your 64 bit system...not sure 'though.

If you want to give it a try, feel free to ask me anything- better start from the other topic.:-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-)

let me know...