X299 Big Sur Support

[Ghostmac1969]

Thank you! Can I plug the bluetooth cable?

 

[djlild7hina]

Thank you! Can I plug the bluetooth cable?

Sure you can try. have you tried running a memory test since your kit wasn't officially supported? Idk if that's whats causing your issues but i'd recommend checking out the debugging steps that izo mentioned. It's easier to debug when you have less.

 

[djlild7hina]

I am using an MSI X299 Tomahawk motherboard. Can I ask you to make the OC EFI?
I successfully installed Catalina, but had problems with Big Sur.

Are you running official release of 0.6.0? What problems are you running into?
You may need to manually define the RTC0 range like ASUS boards. Dump your DSDT using Hackintool and look for RTC for your range to see if it's missing anything.

acidanthera/OpenCorePkg

OpenCore bootloader. Contribute to acidanthera/OpenCorePkg development by creating an account on GitHub.

github.com

 

[Ghostmac1969]

Sure you can try. have you tried running a memory test since your kit wasn't officially supported? Idk if that's whats causing your issues but i'd recommend checking out the debugging steps that izo mentioned. It's easier to debug when you have less.

Can you suggest me which RAM should I buy to be sure about its compatibility? I need 128 GB ...

 

[djlild7hina]

Can you suggest me which RAM should I buy to be sure about its compatibility? I need 128 GB ...

Not sure I would just check the QVL list. I think @izo1 has 128gb of g skill trident z in his rig?

 

[djlild7hina]

Thank you!
SSDT-TB3-1.dsl - RP05, PCie_Slot-2, TB Bus-0, worked great with hotplug etc
SSDT-TB3-2.dsl - PCie_Slot-3, TB Bus-1
SSDT-TB3-3.dsl - PCie_Slot-4, TB Bus-2

update:

PXSX in SSDT-TB3-2 and in SSDT-TB3-3.dsl should be removed. Then UPSB and NHI are appear and TB-switch (IOthunderboltPort@7) is on. But I don't see the DSB0, DSB1, DSB2 and DSB4 - pci-bridge@x only.

New ioreg is attached.

I already described how to map it in my post and replied to your last comment about this...

Asus X299 - Catalina Support

Hello there! Yes it is flashed and DROM adjusted. I'm experimenting a bit and trying to expand my knowledge in case it ends up being possible to use 2 Titan Ridges together with one Sage/10G. I ended up jumping pins 3 and 5 as you mentioned in the other thread and it's working in Slot 2. Have...

www.tonymacx86.com

You need an additional scope with the pci-bridge@10 and then copy the thunderbolt ssdt code inside . the pci-bridge@10 is your slot. check the attached SSDT in the post.

 

[izo1]

Can you suggest me which RAM should I buy to be sure about its compatibility? I need 128 GB ...

I'm just running 3200Mhz Trident Z RGB (8x16GB) non B-Die for total of 128GB.

I saw some good RAM deals the other day, I believe you can do up to 256GB with the latest BIOS on the SAGE10G, but don't quote me on that. With 8x32GB, something like this.

But I think 3600MHz CL17 RAM (B-Die?) of 128GB (8x16GB) would be really good and fast.

Check sites for common sales. I think GSkill is good but so are other brands.

 

[osxfr33k]

Try completely unplugging the FENVI card for now. Including the onboard USB cable. It may be the hub I don't know. After all a lot of these products are cheaply made stuff in a niche market.

Can you also try removing FENVI card completely and see if the KP goes away? Use Ethernet for now.

Also if you truly have bent pins on your CPU, it might be pins that are connected to the IMC (Integrated Memory Controller) and that's why you're seeing KPs.

I went through 2 Prime Deluxe IIs (Rev1, when they came out) because the motherboard had issues hanging on with the 128GB of DDR4 RAM. I would get constant KPs. I switched to SAGE10/G and all the problems went away. You have the same board so it might be something related to the CPU itself or RAM?

Can you also remove all the RAM modules and start with a minimal amount and keep adding/rebooting to see if the problem arises from RAM itself? I am not sure how much RAM you have, but the higher amount (like 64GB+) means that it will hit the IMC harder and not all CPUs are created the same, so some will have issues pumping that much data through especially at higher clock speeds.

The thing about troubleshooting is you have to do one step at a time and diagnose where the issue is coming from, so you don't jump around until you exhaust one problem area to see if that's where the problem arises. I suggest starting from RAM and CPU first, but remove ALL PCIe cards first and just leave your Radeon VII in Slot 1 for now for testing purposes.

I had to return one board in the past because I had over-tightened the cooler pump. They should be hand tight and not use a philips head screw driver (most thumb screws have this on the top) to tighten at all it will distort the CPU pins on the motherboard.

 

[osxfr33k]

Can someone try to answer these questions please, couple of them are from a previous post?

1) Why are we setting num lock disable in Bios, does it cause keyboard issues if set to enabled?

2) My x299 Sage II won't boot properly (reboots after trying to get to desktop) when CPU Core ratio is set to Sync all cores have to set to Auto instead, I am using the proper TSCSync 18 core for my CPU Intel i9-10980XE.

3) I created my USB kext using HeadKaze's Macentool, I hate the word H...., rather use Clone etc. Anyways it creates additional files, one of which the SSDT-EC-USBX that is slightly different than the one from the Base OC, has external in the first few lines and maybe some slightly different code just in the beginning of the file. The SSDTs that come with the Base OC should be used as is correct including the SSDT-EC-USBX or should I use the one that is created from HeadKaze's tool?

4) Any other SSDTs I need to create that would be specific the the Sage II like the PCIe slots since there are some slight differences over the Sage 10G such as the ethernet, I probably cannot use any of those unless the number of PCIe slots are the same are we creating SSDTs for each slot?

Once I get all of this straight I can share my EFI, just not sure if anyone will be getting a Sage II or not?

Thanks!

 

[djlild7hina]

Can someone try to answer these questions please, couple of them are from a previous post?

1) Why are we setting num lock disable in Bios, does it cause keyboard issues if set to enabled?

2) My x299 Sage II won't boot properly (reboots after trying to get to desktop) when CPU Core ratio is set to Sync all cores have to set to Auto instead, I am using the proper TSCSync 18 core for my CPU Intel i9-10980XE.

3) I created my USB kext using HeadKaze's Macentool, I hate the word H...., rather use Clone etc. Anyways it creates additional files, one of which the SSDT-EC-USBX that is slightly different than the one from the Base OC, has external in the first few lines and maybe some slightly different code just in the beginning of the file. The SSDTs that come with the Base OC should be used as is correct including the SSDT-EC-USBX or should I use the one that is created from HeadKaze's tool?

4) Any other SSDTs I need to create that would be specific the the Sage II like the PCIe slots since there are some slight differences over the Sage 10G such as the ethernet, I probably cannot use any of those unless the number of PCIe slots are the same are we creating SSDTs for each slot?

Once I get all of this straight I can share my EFI, just not sure if anyone will be getting a Sage II or not?

Thanks!

1. That may have been a preference of @kgp. I think it's fine to leave as is
2. Not sure but something may be not configured right.
3. Just use the ones already in the EFI. Make sure to disable USBInjectAll.kext and replace with the new USBKext. Also disable XhciPortLimit.
4. SSDTs were mostly cosmetic and can be done via DeviceProperties. If you want to do renames then you can use SSDTs.