Jump to content

x99-e WS DSDT help


critza
 Share

16 posts in this topic

Recommended Posts

Hello i am struggling with this system:

ASUS X99-E WS
ASUS GTX 970 Strix
Intel 5960X

I have made an install with Yosemite 10.10.1, but i cannot get it to boot without safe mode.

If i don't boot with -x i get stuck at PCI Configuration begin.

I don't know how to read a DSDT and i think that the amount of time i would need to understand this, will take too long.

So I'm hoping that someone could help me out with this.


/Christer

x99-e WS dsdt.zip

Link to comment
Share on other sites

Ok first of all, make sure you clear the kernel cache and set permissions/ownership after installing these kexts. My preferred method for this is just to run kext utility. So try that in safe mode before anything else.

 

Also have you tried npci=0x2000 or 3000?

 

If neither of those things work, you could try this DSDT...

 

The old fix for this problem before npci=0x#### was available was to remove Name (_ADR, Zero) from Device (PCI0) and put Name (_UID, Zero in its place). Your dsdt already had UID though, so I just removed _ADR. Not sure if that will work, but it's worth a shot.

 

I think there's a few other people using this board, maybe you should check with them and see what BIOS settings they are using. 

x99-e WS dsdt No _ADR.aml.zip

Link to comment
Share on other sites

What method of install did you use?

 

Do not edit the DSDT as it will cause issues. SSDT injection is the only method that will not create issues on x99 Systems.

 

Please post a IOREG so that I can create a SSDT for the x99 DMG.

 

Thank you.

Link to comment
Share on other sites

Ok first of all, make sure you clear the kernel cache and set permissions/ownership after installing these kexts. My preferred method for this is just to run kext utility. So try that in safe mode before anything else.

 

Also have you tried npci=0x2000 or 3000?

 

If neither of those things work, you could try this DSDT...

 

The old fix for this problem before npci=0x#### was available was to remove Name (_ADR, Zero) from Device (PCI0) and put Name (_UID, Zero in its place). Your dsdt already had UID though, so I just removed _ADR. Not sure if that will work, but it's worth a shot.

 

I think there's a few other people using this board, maybe you should check with them and see what BIOS settings they are using. 

 

npci=0x2000 got me past the first PCI Configuration begin error, but left me at another PCI Configuration begin which i havent been able to pass until now.

What method of install did you use?

 

Do not edit the DSDT as it will cause issues. SSDT injection is the only method that will not create issues on x99 Systems.

 

Please post a IOREG so that I can create a SSDT for the x99 DMG.

 

Thank you.

Hey Andrew, i know that you are working with this motherboard, and you suggested yo use myHack and 10.9.5 since clover is broken for 10.10 atm. But i was able to install 10.10 finally. (With the enemy weapon sorry to say Unibeazt and Multibeazt)

I did the rollback of IOPCIFamily and AppleACPIPlatform, patched the kernel and installed with kext-dev-mode=1, npci=0x2000 -v -f -x.

 

After installing i put kext-dev-mode=1 npci=0x2000, nvda_drv=1  in chameleon.boot.plist, copied the patched kexts and kernel, installed NVIDIA webdrivers, repaired permissions and to i was still stuck on PCI Configuration begin for 1 month.

 

Today someone posted somewhere that he used debug=0x14e to get past PCI Configuration begin on a x99-a and this worked for me as well.

So now my struggle with this board is finally over!!!

Link to comment
Share on other sites

What method of install did you use?

 

Do not edit the DSDT as it will cause issues. SSDT injection is the only method that will not create issues on x99 Systems.

 

Please post a IOREG so that I can create a SSDT for the x99 DMG.

 

Thank you.

Yeah the DSDT was just a test to see if it would work, that's not something I would normally recommend for a future-proof solution. 

 

@Balamut did you try the other things I posted? Seems like for almost everyone experiencing this even after installing the rollback kexts it turned out to be a kernel cache thing. That being said, I would think if that was the case it wouldn't boot in safe mode either.

 

@critza can you link to that original post? Never heard of using it for that purpose before - interesting that it solved that for you. EDIT: nevermind, I found it.

Link to comment
Share on other sites

  • 2 weeks later...

Anyone have any luck with this board/cpu/gpu?

 

No matter what I do/try ether reboot or lock on pci conf. It's funny thats the previous gen. works like a charm.

 

After a month of trying feels like I need to put 6 rounds of 12 gauge into this board (Sorry just had to went).

Link to comment
Share on other sites

 Share

×
×
  • Create New...