Haswell-E + X99 Motherboard Temporary Guide - OS X 10.10

[XxQ8LioNxX]

I keep getting the same error over and over again no matter what flags I use when booting. http://i.imgur.com/nZ8GTEJ.jpg

I did everything as laid out in the original post, I tried with no flags, using cpus=1, npci=0x2000, and nothing. Any ideas as to what might be wrong?

I have a 5820k, Gigabyte UD4, GTX 970 and 16gb of crucial ram.

Thanks.

Try -v -f nv_disable=1 npci=0x2000

 

[VIRDARI]

Guys could anyone help me with this error
My rig:
x99 asus deluxe Bios 1004
I7 5820k 6 core
G1 Gaming 970gtx x 2
250gb SSD to install yosemite,
I patched the kernel and also added voodoo kext and I always get stuck along that line.
The last 5 lines are:
DSMOS has arrived
IOBluetoothHCIController start completed
//2 more lines
Then the last line is bpfAttach len 64 dlt 12
That's where I get stuck always.

I'm a noob never tried to install hackintosh before that's why I'm lost, thanks for your help.

EDIT used - v -f nv_disable=1 npci=0x2000 worked
Thanks to the guy above me

I installed the os on a hard drive and booted and did the multi beast settings, I patched the kernel by copying it from USB to the hard drive, I changed the chameleon plist and added npci=0x2000. and rebooted now (did it exactly like it's described in the tutorial) I'm stuck at the Apple logo the bar is not loading up. I'm trying to boot into the hard disk now. (i suspect because of a kernel panic?)
could someone help me please ? tried to boot with -v -f nv_disable=1 npci=0x2000,]
Kernel panic comes up and says something about the processor, do you think setting my bios settings to default ( my cpu is overclocked at the moment) could solve the issue ?

 

[XxQ8LioNxX]

Guys could anyone help me with this error View attachment 115009
My rig:
x99 asus deluxe Bios 1004
I7 5820k 6 core
G1 Gaming 970gtx x 2
250gb SSD to install yosemite,
I patched the kernel and also added voodoo kext and I always get stuck along that line.
The last 5 lines are:
DSMOS has arrived
IOBluetoothHCIController start completed
//2 more lines
Then the last line is bpfAttach len 64 dlt 12
That's where I get stuck always.

I'm a noob never tried to install hackintosh before that's why I'm lost, thanks for your help.

EDIT used - v -f nv_disable=1 npci=0x2000 worked
Thanks to the guy above me

I installed the os on a hard drive and booted and did the multi beast settings, I patched the kernel by copying it from USB to the hard drive, I changed the chameleon plist and added npci=0x2000. and rebooted now (did it exactly like it's described in the tutorial) I'm stuck at the Apple logo the bar is not loading up. I'm trying to boot into the hard disk now. (i suspect because of a kernel panic?)
could someone help me please ? tried to boot with -v -f nv_disable=1 npci=0x2000,]
Kernel panic comes up and says something about the processor, do you think setting my bios settings to default ( my cpu is overclocked at the moment) could solve the issue ?

Have you done this after the MultiBeast part
http://www.tonymacx86.com/graphics/...ate-graphics-drivers-10-10-1-343-01-02-a.html
if not then start up using -v -x nv_disable=1 and do it
if that isn't your problem then i have no clue what r u talking about .. post a pic.

 

[VIRDARI]

Have you done this after the multi beast part
http://www.tonymacx86.com/graphics/...ate-graphics-drivers-10-10-1-343-01-02-a.html
if not then start up using -v -x nv_disable=1 and do it
if that isn't your problem then i have no clue what r u talking about .. post a pic.

I will try install those graphic drivers if I can get in. I tried to use - v - x nv_disable = 1 and here is the screen I get, i have no idea what i did wrong, because it did boot into the SSD before installing MultiBeast, after installing MultiBeast stuff i rebooted and now this thing comes up every time

 

[Octavean]

I will try install those graphic drivers if I can get in. I tried to use - v - x nv_disable = 1 and here is the screen I get, i have no idea what i did wrong, because it did boot into the SSD before installing MultiBeast, after installing MultiBeast stuff i rebooted and now this thing comes up every time
View attachment 115016

Thanks to BoomR and Janzwo I got my Core i7 5820K / ASUS X99-A build running Yosemite relatively well.

I suggest you delete all (should be only two) IOBluetooth related Kext files under S/L/E.

Also what does your Boot.plist file look like,...?

Are you trying to boot from the UniBeast USB stick or the internal drive you installed Yosemite to?

 

[VIRDARI]

uhm i pick the USB stick and then try to boot into the hdd from there, excuse me but i'm quite a noob so could you tell me how to fix my issue, thank you, i haven't really changed anything but just added ncpi=0x2000 to kernel flags part, other than that i didn't touch it. for the MultiBeast part, i picked the default option (quick installer or something ) then i just changed the system edition from mac pro 3.1 to mac pro 6.1 then i added voodoSYNCkext, and then i installed all those drivers and rebooted.

i just don't know how to fix it

 

[VIRDARI]

i tried to re - install Yosemite and now i can't even boot into the Yosemite hard disk to install MultiBeast stuff. i try with -v -f nv_disable=1 npci=0x2000 , and what happens is after it reads a bunch of stuff, the screen goes away and system reboots automatically, i have no idea what caused this now

 

[Soundsgreat78]

i tried to re - install Yosemite and now i can't even boot into the Yosemite hard disk to install MultiBeast stuff. i try with -v -f nv_disable=1 npci=0x2000 , and what happens is after it reads a bunch of stuff, the screen goes away and system reboots automatically, i have no idea what caused this now

I ran into this this weekend, try loading optimized defaults in the BIOS again before rebooting, that fixed things for me. Hope it helps.

 

[bdegazio]

QUOTE - "It gets about 3 minutes into the render and freezes completely."

Sounds like the CPU is overheating. Try backing down the over clocking, or use a better cooler.

 

[Manic Harmon1c]

QUOTE - "It gets about 3 minutes into the render and freezes completely."

Sounds like the CPU is overheating. Try backing down the over clocking, or use a better cooler.

If it's overheating it would probably just shut down, afaik that's what is supposed to happen at least... Sounds like the CPU might just be unstable, might need a little more voltage on something, or like you said backing down on the clock speeds.