Jump to content

Attempting 10.10 on Supermicro G10DRG. Currently Hangs at [PCI Configuration Begin]


DonDonnelly
 Share

26 posts in this topic

Recommended Posts

For some reason with my limited experience I've decided to take on a high performance build. SuperMicro DRG10, dual e5v3 2697, 128GB DDR4 ECC, 1x GTX 960, 3x GTX980ti.

With both Clover and [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url], I'm stalling out at [PCI Configuration Begin] loading 10.10 installer. This flag shows up a few times in the boot process, the last one happens just after recognizing the LAN ports.

So far I've tried:
-Clover/Chimera
-Almost Every Boot Arg ("-v npci=0x2000 cpus=1 kext-dev-mode=1 PCIRootUID=1" has gotten me the farthest yet)
-Nvidia GTX960/GTX980Ti/Embedded

-Disabled onboard LAN

-Disabled unused PCIe slots

I'm reasonably sure I have the BIOS configured correctly (hyperthreading/virtualization/CSM off, AHCI on, etc.) however I haven't found a reference for BIOS settings for this board (honestly not too surprising though).

 

I knew going in this would be a challenging one, any assistance is greatly appreciated.
 

post-1597193-0-02010500-1443388588_thumb.jpg

Link to comment
Share on other sites

Ok here you GO !

IMPORTANT

For using options Installer OS X 

You need

Install OS X Yosemite.app

or

Install OS X El Capitan GM Candidate.app

on your Applications 

 

​The EFI Folder is specially for your config  Hopes it work!

0910.png

-12.png

015.png

219.png

 

Good Luck  :D  :thumbsup_anim:

  • Like 1
Link to comment
Share on other sites

Hey Chris,

 

I've successfully made the installer, and discovered that the black screen was from needing to physically disable the onboard GFX with a jumper to get to the clover bootloader. Currently getting a variety of kernel panics, which seem to be created/resolved by BIOS settings. The latest is "Invalid Queue Element Linkage". Screenshot attached.

 

 

*Update: I found another option that was enabled incorrectly in the BIOS. After disabling I no longer get Kernel panics, but I do get the dreaded [PCI Configuration Begin]. Screenshot added below.

post-1597193-0-72611400-1443540668_thumb.jpg

post-1597193-0-91936000-1443542318_thumb.jpg

Link to comment
Share on other sites

Hey Chris,

 

I've successfully made the installer, and discovered that the black screen was from needing to physically disable the onboard GFX with a jumper to get to the clover bootloader. Currently getting a variety of kernel panics, which seem to be created/resolved by BIOS settings. The latest is "Invalid Queue Element Linkage". Screenshot attached.

 

 

*Update: I found another option that was enabled incorrectly in the BIOS. After disabling I no longer get Kernel panics, but I do get the dreaded [PCI Configuration Begin]. Screenshot added below.

Secound pitture thats not the FakeSMC.kext  Inside Efi Installer

because I not put any plugin HWSensor

Link to comment
Share on other sites

Did you boot with bootflag: -v -f npci=0x3000 ....and remained your systems stuck on "PCI Configuration begin"? if not, then boot again

Link to comment
Share on other sites

there is a package "npci=0Xxxx" for Mavericks, this has patched us carlo_67 to perform a test with AppleHDA on Amd hackintosh. that has worked fine under Mavericks 10.9 to 10.9.5, I do not know if that solves your problem. I do not think that you can use the content of the package with Yosemite. But you can ask carlo_67 if he can patch a solution for Yosemite.

Link to comment
Share on other sites

With the help of a DSDT that Spakk made for me (documented on another thread in the DSDT sub) I've been able to get to a Kernel Panic if I keep more than one cpu per core active, and a system hang after the Bluetooth platform loader (supposedly a graphics loader issue from what I've been reading). I've definitely come across some references for your specific config, I'd try Rampage dev's x99 DMG to start.

Link to comment
Share on other sites

I'm pretty sure you need to use the same method as the 5960x and some of the other Haswell-E Xeons, which is to use the 10.9.5 version of IOPCIFamily.kext and AppleACPIPlatform.kext. Note that if you want to use Thunderbolt or FireWire you will have to roll those kexts back to the 10.9.5 versions as well.

  • Like 1
Link to comment
Share on other sites

Hi Jamie, I've rolled back those kexts to a 10.9.5 version I have from another machine and rebuilt caches, no change. 

 

UPDATE: 

 

After reinstalling the rollback kexts and clearing caches/fixing permissions a couple times I now get to FakeSMC: [Fatal] failed to initialize SMC Device. I've found a few articles from other forums on fixes, none of which help/seem to be legitimate solutions. Any ideas?

 

Eventually found a link to FakeSMC 6.18 which now loads correctly, still stuck on Bluetooth Controller Missing though. I've swapped out to the following GFX cards, with all possible boot flags.

 

Gtx960

Gtx980ti

Quadro 4000 Mac

 

I've also attempted setting up a vanilla install via another machine, installing clover, and nvidia web drivers. Same result. 

Link to comment
Share on other sites

  • 1 month later...
  • 2 weeks later...

For what it's worth, I was never able to get a USB installer for Yosemite to boot on my Supermicro X9DR3-F, always getting stuck at bluetooth controller or a black screen no matter what flags are used. I have to install the OS from my Macbook to an SSD in a USB dock, install Clover or Chameleon, and then put the SSD in my hack. At this point I can usually remote desktop in to install the nVidia web driver and then it's good to go. 

 

Welcome to the Supermicro server board world of hurt :) 

Link to comment
Share on other sites

  • 1 month later...

Have you tried 10.10.5 with the rollback 10.9.5 versions (or make me legacy version) of IOPCIFamily and AppleACPIPlatform plus patched the kernel? As Jaime said, you have the equivalent problems (and solutions) as an i7-5960X.

 

Your problem is most likely your CPU choice, not your motherboard. Using an E5-2697 V3 on any motherboard causes a hang at PCI Configuration Beings post 10.9.5, but remains fixable in 10.10.X, then a complete no go on 10.11.X.

 

I have this CPU, it works for me doing the above.

 

You a DIT?

Link to comment
Share on other sites

 Share

×
×
  • Create New...