Cant boot up with OSXAPtipFix 1 OR 2

ekwipt said:

more details here: https://nickwoodhams...k-error-update/

Click to expand...

Thankyou ekwipt.

Question if I get past the whole initial allocation thing do I still need to mess with the Aptio or Test2 .efi combinations? Do they stop effecting the hackintosh after that? And they couldnt be responsible for a crash at PCI configuration began right?

Anyway today I dug up some old notes from last time I tried to hack this build. the flag that worked and got me to a REALLY buggy system was "IGPEnabler=N GraphicsEnabler=N -x -v dart=0 UseKernelCache=N -f npci=0x2000". The problem is I dont think that that one was a clover boot, but something else. Which of these commands should I still try using?

Todays tests were done with two flashdrives one with the boot flag "-v" and the other with "IGPEnabler=N GraphicsEnabler=N -x -v dart=0 UseKernelCache=N -f npci=0x2000"

I tried various .efi combinations (5 to be exact). All of them were able to get through the initial system allocation and all got stuck at PCI configuration began. (repeat question) Does this mean I dont need to mess with APtio or Test2 .efi combinations?

What exactly is the cause of the PCI configuarion began crash? is it the MOBO or one of the pieces in a PCIE slot, could this have to do with my wierd Haswell-e 6 core 5820k?

I am not really sure what else to try tomorrow. Any boot flag, kext, or efi suggestions are appreciated.

My build remains the same with the x99s mobo, 5820k cpu, 740 gpu, and compatible wireless card. The only thing I changed was I unplugged all usb's that werent needed. So in pci slots it is only a DVD drive and a Hard Drive. It is worth noting that sometimes on PCI configuration began it shows the following text before crashing "Bridges 1, 54 devices".

I'm not sure sorry mate, a lot of the stuff is over my head as well, I just follow guides and learn more along the way.

Happy hackintoshing

AndrewK230 said:

Thankyou ekwipt.

Question if I get past the whole initial allocation thing do I still need to mess with the Aptio or Test2 .efi combinations? Do they stop effecting the hackintosh after that? And they couldnt be responsible for a crash at PCI configuration began right?

Anyway today I dug up some old notes from last time I tried to hack this build. the flag that worked and got me to a REALLY buggy system was "IGPEnabler=N GraphicsEnabler=N -x -v dart=0 UseKernelCache=N -f npci=0x2000". The problem is I dont think that that one was a clover boot, but something else. Which of these commands should I still try using?

Todays tests were done with two flashdrives one with the boot flag "-v" and the other with "IGPEnabler=N GraphicsEnabler=N -x -v dart=0 UseKernelCache=N -f npci=0x2000"

I tried various .efi combinations (5 to be exact). All of them were able to get through the initial system allocation and all got stuck at PCI configuration began. (repeat question) Does this mean I dont need to mess with APtio or Test2 .efi combinations?

What exactly is the cause of the PCI configuarion began crash? is it the MOBO or one of the pieces in a PCIE slot, could this have to do with my wierd Haswell-e 6 core 5820k?

I am not really sure what else to try tomorrow. Any boot flag, kext, or efi suggestions are appreciated.

My build remains the same with the x99s mobo, 5820k cpu, 740 gpu, and compatible wireless card. The only thing I changed was I unplugged all usb's that werent needed. So in pci slots it is only a DVD drive and a Hard Drive. It is worth noting that sometimes on PCI configuration began it shows the following text before crashing "Bridges 1, 54 devices".

Click to expand...

The xxEnabler boot-args do nothing in Clover - they are Chimera/Chameleon only.
Reboot may be caused by not having VoodooTSCSynch.kext for 6 core CPU in your Clover kext folder.
There are links on several threads to OsxAptioFixDrv-Free2000 which works with X99 boards to cure the AptioFix errors and allow you to boot, dart=0 takes care of the need to disable VT-d, npci=0x2000 takes care of the PCI Configuration Begin hangup, -f is to boot without caches - does not do anything for installing, -x is boot without drivers - if using this boot-arg make sure you have any files you need post install on a USB because you will not be able to get to the network since the driver for your NIC did not load.

So try it with -v dart=0 npci=0x2000

You might also add maxmem=4096 if you continue to get memory errors.

Going Bald said:

The xxEnabler boot-args do nothing in Clover - they are Chimera/Chameleon only.
Reboot may be caused by not having VoodooTSCSynch.kext for 6 core CPU in your Clover kext folder.
There are links on several threads to OsxAptioFixDrv-Free2000 which works with X99 boards to cure the AptioFix errors and allow you to boot, dart=0 takes care of the need to disable VT-d, npci=0x2000 takes care of the PCI Configuration Begin hangup, -f is to boot without caches - does not do anything for installing, -x is boot without drivers - if using this boot-arg make sure you have any files you need post install on a USB because you will not be able to get to the network since the driver for your NIC did not load.

So try it with -v dart=0 npci=0x2000

You might also add maxmem=4096 if you continue to get memory errors.

Click to expand...

Ok so today I tried two boot flag combinations (on my two drives)
Red drive: -v dart=0 npci=0x2000
Blue drive: -v dart=0 npci=0x2000 cpus=1

My rationale for trying cpus=1 was that this article says it is necesary to make voodoTSCSync.kext work

That being said the red drive got the furthest today.

So as far as initial allocation I am now using test2-2016.efi and OsxAptioFix2Drv-free2000.efi as these have the best track record for getting things past initial allocation. Is there any reason why I should still try using some different combinations of those two efi's and their older versions?

Ok anyway when I say red got the furthest it is because blue (cpus=1) got to the whole IOBluetoothFamily, initting scan manager controller thing then screen went blank.

However red (not cpus=1) got through the IOBluetooth thing, and would print out "fInterfaceSnapshots is missing" acouple times before going dark.

I tried some of the nvidia boot flags nv_drv=1 didnt seem to change anything, but nv_disable=1 caused it to get stuck rather then crash at those finishing lines. This is how I am able to tell you them as they flashed two quickly before the screen went dark.

I am confused as to why the GPU is giving so much trouble it is a "EVGA GeForce GT 740".

Is it possible that I sucessfully got to the install screen but something with the graphics card stopped it from displaying that I got there? I am using a DVI-D cable if that matters. I would use HDMI but the GPU placement in the case make it so the cable is too wide to fit in its slot.

A note is perhaps I am having an issue because my CPU does not have integrated graphics? Perhaps my motherboard is simply too wierd?

I again do not know what to do next, it would appear the installation stopped because of the GPU yet I have tried every combination of the two nvidia boot flags. What should I do next?

Should I try out messing and disabling things related to USB?

Should I try maxmem=4096 even though this doesnt appear to be a memory issue?

I thought just to help I would list the kexts and efi's I am using

EmuVariableUefi-64.efi
FSInject-64.efi
HFSPlus.efi
OsxAptioFix2Drv-free2000.efi
OsxFatBinaryDrv-64.efi
Test2-2016.efi

AHCI_3rdParty_SATA.kext
AHCIPortInjector.kext
AppleIntelE1000e.kext
FakePCIID_XHCIMux.kext
FakePCIID.kext
FakeSMC.kext
NullCPUPowerManagement.kext
USB_Injector x99.kext
VoodooTSCSync.kext

Thanks for all the help so far!

AndrewK230 said:

So as far as initial allocation I am now using test2-2016.efi and OsxAptioFix2Drv-free2000.efi as these have the best track record for getting things past initial allocation. Is there any reason why I should still try using some different combinations of those two efi's and their older versions?

Click to expand...

Use only one OsxAptioFixDRV.efi - using two at once is counterproductive. I had the best luck with the free2000 version. It consistently allows me to boot, while the others would allow me to boot the installer once, but then give me an "unable to allocate..." error or memory errors. I am still using the free2000 version to boot from the SSD.

Going Bald said:

Use only one OsxAptioFixDRV.efi - using two at once is counterproductive. I had the best luck with the free2000 version. It consistently allows me to boot, while the others would allow me to boot the installer once, but then give me an "unable to allocate..." error or memory errors. I am still using the free2000 version to boot from the SSD.

Click to expand...

Wait so is test2 also an OsxAPtioFixDRV thing? I thought I was only using one.

Test2 and optio fix that I showed you are the essentially the same thing, he combines two fixes into one. So you only need free2000 version

Ok so I tried the boot flags with a drive with only free2000.edi (NO test2.efi)

1. -v dart=0 npci=0x2000
2. Blue: -v dart=0 npci=0x2000 maxmem=4096

They both got past DESMOS arrived, and some NVIDIA startup things, then it showed something about bluetoothIO real quick and then crashed.

At this point I get through the initial allocation basically every single time.

I also unplugged the power part from the DVD drive, technically it is still attached via a PCI connector, but according to board explorer it doesnt exist.

What should I try next?

Something worth mentioning is in the tutorial I have been following they have you put ssdt.aml in Clover/ACPHI/Patched, and have a custom config.plist that you drag in (They still have you edit it a bit in clover configurator (change boot flags, interface to auto select, and symbios for latest mac pro)).

I have attached the two incase they provide clues.

AndrewK230 said:

Ok so I tried the boot flags with a drive with only free2000.edi (NO test2.efi)

1. -v dart=0 npci=0x2000
2. Blue: -v dart=0 npci=0x2000 maxmem=4096

They both got past DESMOS arrived, and some NVIDIA startup things, then it showed something about bluetoothIO real quick and then crashed.

At this point I get through the initial allocation basically every single time.

I also unplugged the power part from the DVD drive, technically it is still attached via a PCI connector, but according to board explorer it doesnt exist.

What should I try next?

Something worth mentioning is in the tutorial I have been following they have you put ssdt.aml in Clover/ACPHI/Patched, and have a custom config.plist that you drag in (They still have you edit it a bit in clover configurator (change boot flags, interface to auto select, and symbios for latest mac pro)).

I have attached the two incase they provide clues.

Click to expand...

Do you have VoodooTscSynch.kext for 6 core CPU in your Clover/kexts/10.10, 10.11 folder?

Going Bald said:

Do you have VoodooTscSynch.kext for 6 core CPU in your Clover/kexts/10.10, 10.11 folder?

Click to expand...

Yup