Jump to content

Unable to install/boot on X9DAi and dual Sandy Bridge Xeons.


Arkanis
 Share

13 posts in this topic

Recommended Posts

Howdy everyone,

 

Been suffering on this one, I've already read all the posts around in the forum regarding dropping MATS/BGRT, adding the fix under Clover, replacing previous AppleACPI kext... none of these haver worked so far, or maybe I am doing it wrong. I get a Kernel Panic every time.

 

So I'm calling you guys, maybe someone with the same/similar board has made it... or maybe someone with more knowledge than me can point me the safe path.

 

Current build:

 

Supermicro X9DAi

2 x Xeons 2650 Sandy Bridge

32 Gb Ram

MacPro 6,1 SMBIOS

 

10.12.6 is running smooth and flawless at the moment. I've attached my SSDT (I use SSDT + SSDT1 for PM) to the post and also my config.plist, maybe there is something to dig in there I ignore.

 

EDIT :

 

Made some progress, I installed from 10.12.6 using the manual method on another drive High Sierra, from there I replaced AppleACPI kext from 10.12.6 to avoid getting an immediate Kernel Panic. Now startup moves on but then hangs at a particular moment and then the screen becomes garbled.

 

image1.jpg

 

image2.jpg

 

Please not that this is booting from SATA and NOT USB... 

 

 

Thank you and any help will be greatly appreciated.

 

A.

SSDT.aml.zip

config.plist.zip

Link to comment
Share on other sites

Follow-up :

 

It's not very clear in the photo I took, but USB seems to be loading, after that the stop sign arrives and garbles the screen but you can read there:

 

"Waiting for root device"

 

I've already tried different boot flags but none makes me pass this.

Link to comment
Share on other sites

I DID IT! I managed to finally boot into High Sierra on this board.

 

The culprit ? Two things :

 

1) AppleACPI kext, giving me headaches and giving me KP's no matter what or fix. So I replaced it with the one from Sierra and got passed the KP's but was getting the stop sign and screen trash.

 

2) AppleAHCI in this High Sierra Beta is for some reason NOT LIKING the system, again, replaced It again with the one from Sierra and BOOM, passed through it... and finally booted into the system.

 

Still remain some problems:

 

- System is laggy and Geekbench sucks, so investigating the matter right now.

- No sound.

- No USB3.

 

Will keep posting advances in here.

 

EDIT 1 : 

 

Got USB3 working, played with various SSDT's but none works and digging a little bit more I noticed that only one CPU stays loaded most of the time and the rest barely move so there resides the problem with the lagginess... might be the ACPI replacement I did with previous kext, will try to roll back and see if I can get things booting some way or another. Haven't taken time to investigate audio yet, PM is more important.

  • Like 1
Link to comment
Share on other sites

Sure, the steps where pretty simple:

 

Booting the installer wasn't possible due to the ACPI Kernel Panics and modifying the installer USB drive was a drag SO:

 

1) From a working Sierra Installation download the latest public beta.

2) Go inside the package open and mount InstallESD.dmg, open Packages folder and launch OSInstall.mpkg (this will install the OS on the HD you prepared for High Sierra).

3) Mount BaseSystem.dmg and from /System/Library/CoreServices (in the DMG) copy the file boot.efi to the High Sierra partition to /System/Library/CoreServices (in the High Sierra HD).

4) Execute the following commands to bless the partition and make it bootable :

sudo bless --folder "/Volumes/Name Of The Volume You Installed macOS On/System/Library/CoreServices"
sudo bless --mount "/Volumes/Name Of High Sierra Partition" --setBoot

5) Check if the partition is bootable or not :

bless --info /Volumes/High Sierra Partition Name

6) Now normally you should be set BUT, due to the nature of our BIOS on our boards (and the beta state of High Sierra) we will get a kernel panic no matter what.

 

7) Copy from your Sierra install these two files : AppleACPIPlatform.kext and AppleAHCIPort.kext and copy them to your High Sierra installation to /System/Library/Extensions

 

8) Fix the permissions of those two kexts from the terminal.

 

9) Be sure to clear the cache folder if there is anything on your High Sierra installation (/System/Library/Caches).

 

10) Reboot and it should work.

 

This is the basics, after you managed to boot onto the system, you have to patch AppleIntelCPUManagement following Stinga's method (posted here at insanelymac) and then test if PM is working for you.

 

On my side, PM and Audio aren't working yet... most important thing to fix for me right now is PM, since the CPU distribution and load is behaving strangely, but that might be due to the fact that High Sierra is stil beta, maybe because I replaced the kexts, or Apple is just {censored} around with us. Still investigating this problem...

 

Please post your results in here so we can compare and build from here.

  • Like 1
Link to comment
Share on other sites

Just tested new beta, things are getting worst... lots of errors, lots of problems, and replacing kexts isn't enough anymore.

 

CPU problems unresolved and doesn't seem likely it will get better... it's not related neither with AICPUPM, IOPlatformPlugin, etc... Now half of the cores are detected, so that means either only one CPU is detected/accepted or half of the cores.

 

Single CPU people with X79 are getting moderate success, this might be the announced death of dual cpu capability under macOS...

Link to comment
Share on other sites

Just tested new beta, things are getting worst... lots of errors, lots of problems, and replacing kexts isn't enough anymore.

 

CPU problems unresolved and doesn't seem likely it will get better... it's not related neither with AICPUPM, IOPlatformPlugin, etc... Now half of the cores are detected, so that means either only one CPU is detected/accepted or half of the cores.

 

Single CPU people with X79 are getting moderate success, this might be the announced death of dual cpu capability under macOS...

Don't lose heart on X79's hackintosh buddy, things are getting better :)

Link to comment
Share on other sites

  • 3 weeks later...

I'm on the bus with you Arkanis (GA-X79-UP4)! I'm sure we don't have many options until we understand High Sierra a bit more but I'd steer clear from downgrading AHCI drivers to get it running. Are you running a modified DSDT btw? If not then you might find most of your issues fixed there with patches. 

The main difference between High Sierra and (Low?) Sierra is the APFS and I don't like to think of the consequences of the drivers missing certain steps when taking care of your data because they were rolled back to a pre-APFS using driver, but I'd no idea of the really awesome method you showed and will try an offline install to a blank SSD tonight. It's very convenient to be able to install the OS from terminal.

Link to comment
Share on other sites

 Share

×
×
  • Create New...