PCI Boot Issue, Audio Engineer Help?

[pulpfree]

I am able to get my system up and running with Unibeast/Multibeast setup. My current issue is boot hanging after installing Saffire Mix Control software that is supposed to install the drivers for my Saffire Pro 40s.
Clover is over my head at the moment and really need to get this machine up and running before the weekend. I've read in a few places that people with this issue were able to put Chimera 1.4.1 and get around this issue. It seems to be with the driver the Saffier Mixcontrol installs? I can boot fine with Uni/Multibeast setup but after I try to install the Saffier Mixcontrol it causes my system to just hang, no KPs just sit there and hang after initializing the firewire card? I'm going to try the same version of multibeast (7.1.1) I used back in December, but I can't imagine the newer version would have changed that much?

Wondering if anyone can help me with how to downgrade to Chimera 1.4.1 then? Or any suggestions on how to just install the Saffier driver without the mixcontrol software possibly? Or even some boot flags that might help get around this issue?

Starting to pull my hair out since it was a flawless install the first time around and I have a recording project coming up this weekend that I need this for. Any help is appreciated.

Here are the pictures I was able to take of the boot hang:
http://imgur.com/ykW4eXV

My Build:
GIGABYTE GA-Z97X-UD7 TH
Intel Core i7-4790K Haswell Quad-Core 4.0GHz LGA 1150
GeFroce GTX 760
Crucial Ballistix Tactical 16GB
SAMSUNG 840 EVO 120GB
Seagate Barracuda ST1000DM003 1TB
SYBA SD-PEX30009

 

[P1LGRIM]

I am able to get my system up and running with Unibeast/Multibeast setup. My current issue is boot hanging after installing Saffire Mix Control software that is supposed to install the drivers for my Saffire Pro 40s.
Clover is over my head at the moment and really need to get this machine up and running before the weekend. I've read in a few places that people with this issue were able to put Chimera 1.4.1 and get around this issue. It seems to be with the driver the Saffier Mixcontrol installs? I can boot fine with Uni/Multibeast setup but after I try to install the Saffier Mixcontrol it causes my system to just hang, no KPs just sit there and hang after initializing the firewire card? I'm going to try the same version of multibeast (7.1.1) I used back in December, but I can't imagine the newer version would have changed that much?

Wondering if anyone can help me with how to downgrade to Chimera 1.4.1 then? Or any suggestions on how to just install the Saffier driver without the mixcontrol software possibly? Or even some boot flags that might help get around this issue?

Starting to pull my hair out since it was a flawless install the first time around and I have a recording project coming up this weekend that I need this for. Any help is appreciated.

Here are the pictures I was able to take of the boot hang:
http://imgur.com/ykW4eXV

My Build:
GIGABYTE GA-Z97X-UD7 TH
Intel Core i7-4790K Haswell Quad-Core 4.0GHz LGA 1150
GeFroce GTX 760
Crucial Ballistix Tactical 16GB
SAMSUNG 840 EVO 120GB
Seagate Barracuda ST1000DM003 1TB
SYBA SD-PEX30009

Which version of the operating system are you running ?

Have you installed the latest Drivers ?

Previous versions of Chimera are Here.

You don't need to host your images on third party sites - You can just attach them to your posts.

 

[pulpfree]

Which version of the operating system are you running ?

Have you installed the latest Drivers ?

Previous versions of Chimera are Here.

You don't need to host your images on third party sites - You can just attach them to your posts.

I'm running clean OSX 10.10.0.

I've tried driver version 2.4, and 3.5 and whatever they have on their disk they ship with their devices (I'm assuming somewhere around 2.4 as well as I got my first one a few years ago with my Mac Mini and it worked out of box fine.)

For the previous version of Chimera, if I have run Multibeast and installed Chimera with that (I think the latest version is 4.0 or 4.0.1 or something?) can I just download an old version of Chimera and run it and it will replace the one I installed with Multibeast? Because I tried that last night and it wouldn't boot. I'm pretty new here, sorry.

And sorry about the image, I don't know why I copied that link, I knew I could upload images directly. Thank you though.

 

[P1LGRIM]

I'm running clean OSX 10.10.0.

I've tried driver version 2.4, and 3.5 and whatever they have on their disk they ship with their devices (I'm assuming somewhere around 2.4 as well as I got my first one a few years ago with my Mac Mini and it worked out of box fine.)

For the previous version of Chimera, if I have run Multibeast and installed Chimera with that (I think the latest version is 4.0 or 4.0.1 or something?) can I just download an old version of Chimera and run it and it will replace the one I installed with Multibeast? Because I tried that last night and it wouldn't boot. I'm pretty new here, sorry.

And sorry about the image, I don't know why I copied that link, I knew I could upload images directly. Thank you though.

As you are running Yosemite previous versions of Chimera probably will not work for you as the kernel and the way that it is 'unpacked' changed at that point.

Are you actually using Thunderbolt ? Could there be a conflict there somehow ?

 

[pulpfree]

That makes sense, again bare with me I'm still new to all this and trying to get it all figured out.
Not using thunderbolt at all no, haven't even tried it as I don't have any thunderbolt devices yet. The other interesting thing is when I have my USB 3.0 Hub plugged in after the mixcontrol / driver install it looks a little different than with nothing else plugged in, so I'm attaching that image as well.

The only difference I can think is the unibeast / multibeast version I used. Could that really be the cause?

 

[P1LGRIM]

That makes sense, again bare with me I'm still new to all this and trying to get it all figured out.
Not using thunderbolt at all no, haven't even tried it as I don't have any thunderbolt devices yet. The other interesting thing is when I have my USB 3.0 Hub plugged in after the mixcontrol / driver install it looks a little different than with nothing else plugged in, so I'm attaching that image as well.

The only difference I can think is the unibeast / multibeast version I used. Could that really be the cause?

If you're not using Thunderbolt is there an option to disable it in your BIOS ?

Are you able to boot in Safe Mode ?

Try -v -x -f

 

[pulpfree]

If you're not using Thunderbolt is there an option to disable it in your BIOS ?

Are you able to boot in Safe Mode ?

Try -v -x -f

I'll have to check on that in the BIOS tonight. And no I'm not able to boot into safe mode after the driver install, it gives me KP but I don't have an image of that yet because my phone died mid testing last night.

I have yet to try -f, what exactly does that do? I'll give that a try for sure.
I was battling the yosemite time machine issue last night so I should be able to get results much faster now that I have the terminal command to run that after going into the installer.

 

[pulpfree]

If you're not using Thunderbolt is there an option to disable it in your BIOS ?

Are you able to boot in Safe Mode ?

Try -v -x -f

There's one thing that was pointed out to me over in a ****** thread. I had forgotten to mention that after the first clean install of OSX, a firewire device is seen in the system report, though it's only 1 800 port (i have a card with 2 800 and 1 400). Then after running multibeast, there is nothing under the firewire in system report. Could this be the culprit?

A lot of people are suggesting to ditch multibeast and either manually handle kexts or use clover, but I have no idea where to ever start with finding the right kexts for my system.

 

[pulpfree]

Made some progress last night!

Was able to do a restore to a clean install of OSX 10.10.0 and decided to try installing the Saffire Mix Control before running multibeast. I only had 2.4 on my flash drive, so I ran that and after rebooting it froze at the same spot. Then I tried your suggestion of -v -f and that got me in with both devices connected!

I then tried to update by removing the old kexts / mixcontrol software and then running version 3.5 of mixcontrol, but system didn't like that. I could get to the login screen with -v -f -x but then it would KP right after.

so I'm wondering if the mixcontrol software is doing something with the kernel cache possibly that the system doesn't like? Am I supposed to do something after installing a driver? Going to do a few more tests tonight.

 

[pulpfree]

Had this issue for almost a a week straight. Don't know how it got fixed exactly but here are the things I tried today that got me up and running.



1.I reset everything in my BIOS, changed my wireless KB / Mouse back to wired ones. Redid my BIOs according to this thread ([Progress] GA-Z97X-UD7 TH / i7 4790K / 32GB / GTX 770 / 10.9.4). In addition to this I turned off thunderbolt. This sped up load times for installing and OSX hugely. I hadn't done this before because my BIOs would freeze anytime I tried to go into classic view (I think part of it was due to my wireless KB).

2. Referring back to the thread in step one, I did almost all the same multibeast settings except I skipped over USB 3.0 for now, though I might go back in and add it back in despite my 3.0 externals being recognized.

3. After installing MixControl 3.5 from Focusrite but before restarting, I rebuilt the kernel / kext cache with:
sudo chown -R root:wheel /System/Library/Extensions
sudo touch /System/Library/Extensions
This seemed to be the big step I was missing, but it didn't solve all my issues.

4. Still more to do....After my system froze restarting, I powered off the system, connected my pro 40's back up and turned one of them on. Booted up and everything connected fine. Connected both my external WD 1TBs and went in to do a time machine backup and got a KP. Kept getting KPs on boot. Disconnected all drives and booted into safe mode, first time KP. Second time got in fine.

5. Rebuilt the kernel cache again, figured that after the mandatory restart from the mixcontrol software it might have added something that wasn't there after the first time. Finally was able to boot up without any hangs or KPs after that one.

6. At this point both Pro 40's were still turned off. Someone had suggested to try and turn them on after the system had booted up, so I tried that after logging in and both were recognized and connected just fine. (DON'T TRY THIS UNLESS YOUR CARD AND DEVICE SUPPORTS HOT SWAP FIREWIRE, YOU CAN DAMAGE YOUR DEVICES / MOBO / FIREWIRE CARD DOING THIS IF IT'S NOT SUPPORTED)


Very, very, very confusing. But I really think the major change that helped was turning off thunderbolt and rebuilding the kernel cache TWICE. Once right after installing MixControl and a second time in safe mode after a successful boot. I'm hoping this stays stable as I try to install my CUDA drivers for my GTX 760 CARD and get Logic Pro up and running again. Though I'm wondering if maybe either my USB 3.0 Hub or one of my external HDDs could be causing issues now.

Needless to say, I feel slightly a bit more crazy then I did a week ago.