Contribute
Register

Gigabyte X299X - Catalina Support

Status
Not open for further replies.
I agree completely. When I saw who the developers of OC were it was no hard choice to start with OC. My CPU broke and I was kind in a hurry to setup the new machine. You EFI and AiBeast saved my day and gotta find a gap to change completely to OC. Right now what worries me is the just macOS boot and you need to compile the patched version for multi boot (even thou I am thinking getting rid of windows and use it in the old and fixed built). I won't write more about this because I am messing with the thread, better to keep things clean and right to point.
 
@beltzak & @dolgarrenan thanks for your help, but nothing worked, I tried everything, only the OC bootloader, in USB, SSD, NVME, tried OC 0.5.6, 0.5.8, 0.5.9 and the unreleased 0.6.0. I did not try Clover :( but anyway the main Issue is in the BIOS, even without any disk or usb drive, just the board, it has issues, It's a nightmare just to enter the BIOS, It resets all the time. Time to quit on this, I need this Hackintosh for work,

I decided to try the X299X, which was even worse. :( I wasn't even able to to boot the installer. In the end I've invested around $5K, almost the price of the base mac pro. I'm gonna try to return the X299X MB and CPU and buy the Mac Pro and upgrade it later.

Again, thanks for the help, and good luck to all, I really hope Gigabyte fixes the BIOS soon, but I can't wait until then.
 
Just curious why you need X299 for your work? Z390 Designare + 9900k +5700 XT is pretty powerful and cost about 1/3 of a base Mac Pro. If you jump to 16 cores in Mac Pro, you are looking at 8k, 10k depending on your config but you won't get double the performance in real world tasks, you will get double the benchmark scores.

@beltzak & @dolgarrenan thanks for your help, but nothing worked, I tried everything, only the OC bootloader, in USB, SSD, NVME, tried OC 0.5.6, 0.5.8, 0.5.9 and the unreleased 0.6.0. I did not try Clover :( but anyway the main Issue is in the BIOS, even without any disk or usb drive, just the board, it has issues, It's a nightmare just to enter the BIOS, It resets all the time. Time to quit on this, I need this Hackintosh for work,

I decided to try the X299X, which was even worse. :( I wasn't even able to to boot the installer. In the end I've invested around $5K, almost the price of the base mac pro. I'm gonna try to return the X299X MB and CPU and buy the Mac Pro and upgrade it later.

Again, thanks for the help, and good luck to all, I really hope Gigabyte fixes the BIOS soon, but I can't wait until then.
 
I've checked your EFI and is mostly ok, what have you connected to your computer? Do you have an EFI inside the main drive and another one on a USB attached? Or a second OS drive by SATA or NVME?? Might be bad BIOS config.

Have you been switching back and forth clover/OC, what other hardware you have, GFX,RAM...???
I am having this same issue. I have the EFI on a USB stick. I have Windows 10 on an NVMe drive. 5700 XT for graphics and 256 gig of Corsair ram, only other thing attached is a blank NVMe where I plan to install MacOS and my monitor Via HDMI, Mouse and Keyboard Via USB. I have tried OC 0.5.6 up to 0.5.9. Everytime I boot to the USB stick I get the OC menu, then in about 5 seconds it reboots. I've tried Default BIOS setup, as well as changing all the stuff people recommend, but it's always the same 5 seconds and reboot. I did have some luck with the NDK version of 0.5.9, where it would not just restart itself, but it would freeze on the Apple logo when installing. I'm really at a loss for what to try next.
 
@beltzak & @dolgarrenan thanks for your help, but nothing worked, I tried everything, only the OC bootloader, in USB, SSD, NVME, tried OC 0.5.6, 0.5.8, 0.5.9 and the unreleased 0.6.0. I did not try Clover :( but anyway the main Issue is in the BIOS, even without any disk or usb drive, just the board, it has issues, It's a nightmare just to enter the BIOS, It resets all the time. Time to quit on this, I need this Hackintosh for work,

I decided to try the X299X, which was even worse. :( I wasn't even able to to boot the installer. In the end I've invested around $5K, almost the price of the base mac pro. I'm gonna try to return the X299X MB and CPU and buy the Mac Pro and upgrade it later.

Again, thanks for the help, and good luck to all, I really hope Gigabyte fixes the BIOS soon, but I can't wait until then.

I had the same problem Urbankuest. I dissembled everything put in the box, call the online shop and ask them I wanted to return. I could not afford to waste time and so much money. Then I saw AiBeast post in the laptop. Ok if the same thing happens to another one maybe is not my mobo or cpu I tought. Unpacked everything again, call the shop, ask them no to call the transporter lol. Build the all the components again, installed just one old drive. Installed windows 10, for a couple of days everything worked really fine. No Bios Failure nothing. Now I was sure it wasn't the mobo or the cpu or the build. Started I thing with AiBeast EFI (clover) bang, I could install it. From there my machine is very stable but I hate that Bios Failure. I am going to take pictures of my Bios right now. Just in case you want to check everything just one more time. Also will upload my current EFI so you can test it too. I will clean the serial number of course.
 
Sorry for the focus and the bad pictures.

The Bios Failure came back again. This is what I did in pictures.
1) Enter BIOS.
2) Select the Clover Hard Drive from Boot Override.
If I do this it does not reset. If I load, save, change anything in the bios it does reset.
Bios Failure 1.jpg
Bios Failure 2.jpg
 

Attachments

  • Clean EFI.zip
    6.2 MB · Views: 67
  • Bios Designare 10G Small.pdf
    3.6 MB · Views: 127
Sorry for the focus and the bad pictures.

The Bios Failure came back again. This is what I did in pictures.
1) Enter BIOS.
2) Select the Clover Hard Drive from Boot Override.
If I do this it does not reset. If I load, save, change anything in the bios it does reset.
View attachment 476696View attachment 476697
I don't know if you have two separate 970 EVO or it's just a replica of the same device, but that itself is a problem. Having Windows (unless you are on 0.5.8 n-d-k fork), you won't be able to boot any drive and you will get the error that you are being presented with.

Remove the Windows 10 drive, do a clean BIOS setup (CMOS) and try to boot from the 970 (if there is an EFI inside, or if you have a USB drive with the EFI then it might be just a little tricky if there is any trace of a boot in the main drive), if everything boots fine, then you will have make a OC 0.5.8 n-d-k fork EFI for your system for dual boot.

Reason is because the n-d-k fork has a special quirk to prevent ACPI tables or configuration overall to be loaded onto Windows boot (you don't want to load an SSDT changing IDs and stuff to Windows), that's why you couldn't boot Windows from OC in the first place.

That is the only solution I have found for dual booting on a GB X299X Designare 10G, or for booting anything else. Hope this helps.
 
I don't know if you have two separate 970 EVO

I have two separate 970 EVO. I am thinking getting rid of windows in this build. ;P
I really don't mind the Bios Failure while this trick works (I am getting use to it). Sometimes It does not boot the first time but I can always boot for sure the second time after a Bios Failure.
 
Resorting to trickery to get your system going is just sad. Unfortunately nothing we can do till GB doesn't sort their problems, meanwhile OC is your best chance of not wanting to bin your build every time fails at boot.

Just my honest opinion.
 
i try your OC did not work
My OC EFI is a basis for anyone who wants to use to have somewhere to start, obviously it will not work for everyone given the difference in some hardware. BIOS configuration has the upper hand with this mobo, I would trace to the basics of BIOS config prior to going mad with EFI changes.

If you had one that was working, just try to complete that one, any info given or files by anyone may just work as a "things to consider and try" but ultimately it will be your config that will work for you.

Post your BIOS config by pics if you can, I know its tedious but there might be something wrong with it, and since we know these boards are very sensitive to firmware config then it would be no strange that its not working right..
 
Status
Not open for further replies.
Back
Top