I have a perfectly running Mavericks system on a Supermicro X9DAi with 2 Xeons.
But after cloning the startup disk the boot hangs on
boot file path: System\Library\CoreServices\boot.efi
..
cloning process is as follows:
1) clone the perfectly working Clover Mavericks startup disk with carbon...
went through the install process again and now its working...
I probably messed something up with the terminal based copying...
although i thought i double checked the terminal commands...
always triple check! lol
ASUS X99-E WS
i7 5960X
ASUS TITAN X
managed to install Yosemite and could boot to the installed Yosemite partition with the unibeast USB and -x -x -f ...etc...
inserted Clover USB and could only boot with adding -x
then installed nvidia webdrivers
reboot
since then i'm hanging at PCI...
Im hanging at Section 8 Step 12 of the PDF guide:
[ PCI configuration begin ]
booting stops there
I have the exact same hardware specs at the original poster.
specifically bought for this build to make sure it works.
any pointers?
Tried to install El Capitan to my Supermicro X9Dai with to Xeon E5 2690 and while at first it only worked with hypethreading disabled. SOMEHOW now boots up with hyper threading enabled and it also sees both CPUs.
It only sees half of the RAM though.
Also I have lots of problems with my Titan...
I have a dual Xeon setup with an Supermicro X9Dai motherboard.
I have it running fine with a Quadro 4000.
I want to switch to octane render, and got a Titan-X. But it wont work.
Any pointers?
thanks!
well this is bad. i have 32 threads and I need every single on of them. 3D rendering uses a lot of resources.
would you mind guiding me through your Mavericks install. I just did not get it to boot to desktop I always gets stuck at "Missing Bluetooth Controller Transport"
I guess mavericks...
installed on Supermicro X9DAi with two Xeon E5 2690 and PNY NVIDIA Quadro 4000
Installation worked and I am able to get to the desktop when using the usb thumbdrive and the bootflags:
dart=0 -v PCIRootUID=1 npci=0x3000
but when booting directly from the disk where mavericks was installed...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.