Thinkstation P700 - Dual Xeon E5-2620 v3

[iPwnJ00]

I've spent the last 5 hours and still no installation.

I got a bit further into the loading stage by replacing the AppleACPIPlatform.kext and IOPCIFamily.kext files from Mavericks as suggested by some posts, but then I will start getting some Invalid Argument errors on mount_hfs. Not much information about that.....

Soon afterwards, my machine will KP and then reboot and the cycle starts again.

 

[ammulder]

Do you have any additional hardware in your system that can be removed or disabled? The fix in the big list for stuck at PCI configuration begin is to disable USB3 if you have the option, but maybe remove any add-in PCI cards for now or things like that.

If you have a DSDT for your system, make sure you're booting with it.

If you have one handy, you might try with a more modern video card too -- I know some people have had trouble with older Nvidia cards. (Wouldn't have thought this was the way it manifested, but I'm running out of ideas now...)

 

[iPwnJ00]

Do you have any additional hardware in your system that can be removed or disabled? The fix in the big list for stuck at PCI configuration begin is to disable USB3 if you have the option, but maybe remove any add-in PCI cards for now or things like that.

If you have a DSDT for your system, make sure you're booting with it.

If you have one handy, you might try with a more modern video card too -- I know some people have had trouble with older Nvidia cards. (Wouldn't have thought this was the way it manifested, but I'm running out of ideas now...)

Well, I am in-fact using one of the LGA2011-3 CPUs and that seems to be the biggest culprit in this problem.

Also, I have two processors on the motherboard (ie. running dual Xeons) which I think may have a chance that it's causing the issue.

I've seen some people say that USB3 mileage will vary; some need it on and some have it off...

I continued to try installing starting with Yosemite, but after replacing the AppleACPIPlatform.kext file, I now KP upon boot with an ACPI unknown platform message. Have you seen that before?

 

[ammulder]

No, I've paid much less attention to the Yosemite problems people have... I'd try the Yosemite forum for that.

 

[iPwnJ00]

Wow after a whole day of trying, I finally got into the installation!

In fact, there was an amazingly easy fix.

1. Reset the CMOS on the motherboard (for some reason, Load Optimized Defaults) is different to clearing the CMOS.

2. In EFI/CLOVER/kexts, delete all the numbered folders and only leave "Other".

3. In "Other", you will only need 2 kexts, mainly VoodooTSCSync.kext and FakeSMC.kext

4. Boot with flags: npci=0x2000 dart=0 -v

... and you should get to the installation screen!

Now let's see if the post-installation will be successful.

 

[reitmr]

Any luck? Mind to send along your config.plist and the contents of CLOVER/drivers64UEFI.

On my m/b i needed to add EmuVariableUefi-64.efi and OsxAptioFix2Drv.efi to even get to the infamous [PCI begin ...]. But I'm stuck there.

 

[Amjsez]

Wow after a whole day of trying, I finally got into the installation!

In fact, there was an amazingly easy fix.

1. Reset the CMOS on the motherboard (for some reason, Load Optimized Defaults) is different to clearing the CMOS.

2. In EFI/CLOVER/kexts, delete all the numbered folders and only leave "Other".

3. In "Other", you will only need 2 kexts, mainly VoodooTSCSync.kext and FakeSMC.kext

4. Boot with flags: npci=0x2000 dart=0 -v

... and you should get to the installation screen!]


Now let's see if the post-installation will be successful.

Hi did you use AppleACPIPlatform.kext and IOPCIFamily.kext from Mavericks or the ones from El Capitan??
Thanks...

 

[Rikoshet]

Hi did you use AppleACPIPlatform.kext and IOPCIFamily.kext from Mavericks or the ones from El Capitan??
Thanks...

Would like to share my experience: AppleACPIPlatform.kext and IOPCIFamily.kext are not an issue, I'm using native kexts for Yosemite and El Capitan. Maybe you should look to your dsdt. A guy helped me with my PCI Config... issue by editing my dsdt. There is a lot of work to do since I have kernel panics, but at least I can boot to desktop.