Gigabyte X299X - Catalina Support

[mbi7]

Hi Feartech, I understand the intent of the rules, After re-reading the rules again, I'm not specifically asking for input on my system, I'm asking for feedback from another user to expand on their post who showed success with their build (To try and keep this thread on topic)... I'll update my info, but I don't believe I'm in violation of the rule "Profiles are mandatory so that others can assist you." I'm asking for another user to clarify their post on their build. If I update my stats to their build (the one I am seeking help on) it will just confuse the matter.

You need to have your hardware profile filled out as per rules (the ones you agreed to when signing up here)

https://www.tonymacx86.com/account/account-details

 

[Feartech]

Hi Feartech, what are we supposed to do if we maintain 4-5 different machines?

Terms and rules

You must agree to these terms and rules before using the site.

www.tonymacx86.com

read the signature part

 

[mbi7]

Thanks

Terms and rules

You must agree to these terms and rules before using the site.

www.tonymacx86.com

read the signature part

 

[WasMac]

Hi @WasMac - thanks for sharing your results. Could you confirm if you had to do anything custom other than download the EFI configs attached in post #1?

Nothing custom, everything from post 1. But I don't using any additional SSDTs, as my WS is very stable and I prefer to wait until "final" EFI.

 

[Il.F]

Hey guys,

I'm trying to configure a new Prime X299-A II for upcoming builds (as Prime X299-A is out of stock everywhere) and have a very weird problem (considering the current progress with the updated X299 M/Bs).

The Catalina installer is not booting - hangs on +++++++++++.

In BIOS (version 0504) 'MSR Lock Control' option is set to Disabled.
GRUB check (from here) confirms that CFG Lock (offset is 0x537) set to 0x00.
But preboot.log from Clover (v5103) says:

0:102  0:000  MSR 0xE2 before patch 00008402
0:102  0:000  MSR 0xE2 is locked, PM patches will be turned on

Then I've patched the BIOS with UEFIPatch (from here) with the next result:

parseImageFile: Aptio capsule signature may become invalid after image modifications
parseFile: non-empty pad-file contents will be destroyed after volume modifications
parseFile: non-empty pad-file contents will be destroyed after volume modifications
patch: replaced 8 bytes at offset 42D1h 81E10080000033C1 -> 9090909090909090
patch: replaced 8 bytes at offset 42D1h 81E10080000033C1 -> 9090909090909090
patch: replaced 8 bytes at offset 2413h BE0080000023CE0B -> BE0000000023CE0B
patch: replaced 8 bytes at offset 2413h BE0080000023CE0B -> BE0000000023CE0B
Image patched

Flashed BIOS (via USB BIOS Flashback).
Tried to boot from the USB installer and got the same result - +++++++++ on the screen and the same info in the preboot.log

Any tips?

Config (for tests) is:
M/B - ASUS PRIME X299-A II (BIOS 0504)
CPU - i9 9940X
RAM - 32Gb (2*16Gb Crucial 3000MHz)
SSD - 1Tb Samsung 970 EVO Plus
GPU - RX 5700

 

[dolgarrenan]

@dolgarrenan and @oli.mathieu
Success with the Asrock X299 Creator #63
Thanks for your help and sharing

That is great news for the community!! Thanks for sharing your findings, I'll possibly be moving to OC very soon. I already have my system running under OC and everything seems stable so far, so expect a new EFI soon.

 

[oli.mathieu]

Hello
I feel dumb
Again a lot of tests (.kext, .efi, SSDT, clover version) with always the same KP
I started with the clover folder and BIOS setting of post #1.
If someone is kind enough to test my Clover folder on his "X299X designare 10G" it would be much appreciated
Thanks in advance

 

[canyondust]

Hey guys,

I'm trying to configure a new Prime X299-A II for upcoming builds (as Prime X299-A is out of stock everywhere) and have a very weird problem (considering the current progress with the updated X299 M/Bs).

The Catalina installer is not booting - hangs on +++++++++++.

In BIOS (version 0504) 'MSR Lock Control' option is set to Disabled.
GRUB check (from here) confirms that CFG Lock (offset is 0x537) set to 0x00.
But preboot.log from Clover (v5103) says:

0:102  0:000  MSR 0xE2 before patch 00008402
0:102  0:000  MSR 0xE2 is locked, PM patches will be turned on

Then I've patched the BIOS with UEFIPatch (from here) with the next result:

parseImageFile: Aptio capsule signature may become invalid after image modifications
parseFile: non-empty pad-file contents will be destroyed after volume modifications
parseFile: non-empty pad-file contents will be destroyed after volume modifications
patch: replaced 8 bytes at offset 42D1h 81E10080000033C1 -> 9090909090909090
patch: replaced 8 bytes at offset 42D1h 81E10080000033C1 -> 9090909090909090
patch: replaced 8 bytes at offset 2413h BE0080000023CE0B -> BE0000000023CE0B
patch: replaced 8 bytes at offset 2413h BE0080000023CE0B -> BE0000000023CE0B
Image patched

Flashed BIOS (via USB BIOS Flashback).
Tried to boot from the USB installer and got the same result - +++++++++ on the screen and the same info in the preboot.log

Any tips?

Config (for tests) is:
M/B - ASUS PRIME X299-A II (BIOS 0504)
CPU - i9 9940X
RAM - 32Gb (2*16Gb Crucial 3000MHz)
SSD - 1Tb Samsung 970 EVO Plus
GPU - RX 5700

Why are you patching a bios image as opposed to setting the register on your motherboard with the grub shell?

 

[Il.F]

Why are you patching a bios image as opposed to setting the register on your motherboard with the grub shell?

Because, as I wrote, GRUB shell says that the register is 0x00 already.

But there might be a problem with the current M/B because it can't shut down from Windows and some times from BIOS (it stucks with 00 on POST coder and the fan on the card run at 100%).

 

[dolgarrenan]

Because, as I wrote, GRUB shell says that the register is 0x00 already.

But there might be a problem with the current M/B because it can't shut down from Windows and some times from BIOS (it stucks with 00 on POST coder and the fan on the card run at 100%).

If that's the case, I wouldn't mess around with the board any longer, just RMA and get a replacement. A faulty board will just drive you nuts down the road, besides, if the register comes back 0x00 then there little you can do. Alternative: Flash BIOS to first version and try to escalate one by one, see if you can load from backup BIOS instead of main.