6 replies to this topic

[denmarkdavis]

My new system is running great - until I use my RME Fireface 800 (through MB firewire 400 input). It's totally temperamental, often needing 4-5 restarts after kernal panics before it behaves. After these hiccups, it does run stable.

Is this a firewire problem? Any help would be really useful, it's driving me insane.


THANK YOU.

(Lion 10.7.2.)







p.s. Here are some [unrelated?] kernals from the log.

10/03/2012 09:22:54.000 kernel: NVClockX: NVClock Darwin port by alphamerik © 2010
10/03/2012 09:22:54.000 kernel: NVClockX: usr-sse2 © 2010
10/03/2012 09:22:54.000 kernel: NVClockX: [Warning] no nVidia graphics adapters found
10/03/2012 09:22:54.000 kernel: NVClockX: [Warning]
10/03/2012 09:22:54.000 kernel: NVClockX: NVClock Darwin port by alphamerik © 2010
10/03/2012 09:22:54.000 kernel: NVClockX: usr-sse2 © 2010
10/03/2012 09:22:54.000 kernel: NVClockX: [Warning] no nVidia graphics adapters found
10/03/2012 09:22:54.000 kernel: NVClockX: [Warning]

[Gringo Vermelho]

Delete the NVClockX fakesmc plugin if you don't have an nvidia card.

If you do, those messages are normal, sometimes NVClockX tries to access the video card before it's ready, so you'll see "no nVidia graphics adapters found" a few times until it finally can hook in.

Post more information about your Hackintosh, specs, installation method. Also run Terminal, type this

kextstat -k > ~/Desktop/kextstat.txt and attach the resulting kextstat.txt to your reply.

What firewire chip do you have?

I know from several real-life situations that the first thing to try if you're having Firewire problems is another cable.

Is the Fireface bus powered or does it use an external power supply?

Do you have any other Firewire devices you can hook up to and test it with?

Run Console.app and look for kernel.log. Try to track down messages from when you had your last crash caused by the firewire interface. If you find anything, post it here.

I have only used the Firewire on my Hackintosh twice, I believe it passed with flying colors - once I attached a PowerBook G4, booted it in target mode and installed 10.4.11 on it, another time I used it for copying a ton of files to a friend's MacBook Pro. No hiccups. I used an Apple Firewire cable. I've never tried any audio devices though. The Firewire chip is from LSI, no idea what model it is. Just to let you know that it is possible.

[denmarkdavis]

Amazing reply. Thank you very much. I will try all those things and report back. *tips cap*

[denmarkdavis]

Sorry this has taken me so long to reply - been very busy with work. Kextstat is attached.

-------------------

What firewire chip do you have?

It's the inbuilt firewire 400 on my Gigabyte SKT-1155 Z68XP-UD3 Motherboard.

I know from several real-life situations that the first thing to try if you're having Firewire problems is another cable

Tried new cable - no difference

Is the Fireface bus powered or does it use an external power supply?

External

Do you have any other Firewire devices you can hook up to and test it with?

All other firewire peripherals work fine.



It is when audio is passed through firewire, it either makes the mouse jitter which leads to a kernal panic, or the audio locks and repeats the last 10ms until a kernal panic or restarts. There are no firewire specific entries in the console.. :/

Would it be worth trying a firewire pci-e card - if so, which?

Setup:

Gigabyte SKT-1155 Z68XP-UD3
Gigabyte Radeon HD6870
i7 2600k
16gb 1600mhz ram (vengeance)



Thanks a million again.

Attached Files

•  kextstat.txt   11.05K   3 downloads

[GhaleonX]

I work with a RME Fireface 800, too
When we first got it we had some issues with it, but after updating the RME to the latest firmware, everything was good to go after reloading our configuration settings. If you have not already updated your RME's firmware, I'd suggest doing that FIRST.

That being said, if you already have the current firmware, and if all your other firewire devices work flawlessly, I'd suggest trying the RME on another computer and seeing if you run into problems. The problem you describe, however, suggests to me that you may have some DSDT fixing to do. FWIW, I've seen many audio problems (even with other external interfaces like mbox2) that will not go away until you have a proper enough DSDT to have proper IRQ routing (main problem area is HPET).

In fact, I've seen many people who end up getting a real Mac for audio production because of problems with their hackintosh. You should only use a hackintosh for professional work if it's very thorough, and of course, very vanilla.

[denmarkdavis]

Quote

will not go away until you have a proper enough DSDT to have proper IRQ routing (main problem area is HPET)

This shows my shortfalls, but I have no idea where to start with this.. Could you help me go through what you would do to get this to work?

Many thanks

[denmarkdavis]

Help! Still stuck with 4-5 kernal panics a day before it starts behaving..