Asus X299 - Catalina Support

[pieropontra]

Edit


Can I confirm or deny? Sounds like a very legalistic posit to me....Are you an Attorney? Should I raise my right hand and swear an oath........????

I'm going to guess that maybe, just maybe, English is not your first language? If not, then what is it with the legalistic question, actually?

I do not have any issues with slowdowns, period. But I run bios 2002 with no overclocking (just XMP, nothing else). And, please do not ask for my EFI. I won't post it, not on this thread or any of the other X299 thread....

I don't wanna upset anyone here, it's just as you supposed, I'm Italian so English is not my first language. I was simply asking if u got similar issues with VII and now I know you are ok. I say sorry if my words sounded legalistic, they were obviously not supposed to be.

Agree a bios upgrade is not a must as long as things work. However with my 10980XE on Windows I can see a cine bench boost from 6000pts with b2002 to 8600pts under 3101 so I think the cascade lake can benefit from the latest bios.

@pieropontra in my case it seemed that an EFI config was causing that. If your MB is the same try using my EFI posted before and see if that solves the trick.

YEah newer BIOS are actually designed to support 10th gen microcode so it's correct that your point go higher with that. I got a different board, but I checked your EFI and it's 99% similar to mine (a part from the stuff related to board like USB mapping etc.).

 

[InsomnIaHackintosh]

I don't wanna upset anyone here, it's just as you supposed, I'm Italian so English is not my first language. I was simply asking if u got similar issues with VII and now I know you are ok. I say sorry if my words sounded legalistic, they were obviously not supposed to be.



YEah newer BIOS are actually designed to support 10th gen microcode so it's correct that your point go higher with that. I got a different board, but I checked your EFI and it's 99% similar to mine (a part from the stuff related to board like USB mapping etc.).

Try copying your smbios into the EFi from me and adopt your usb and see if that changes anything. I spent so many hours trying to figure this lags out and the EFI didn’t seemed to have faults. However when I copied the EFI from my system 1 it worked straight away better. Now after the password it takes 6s to fully load everything and no other lags.

 

[mm2margaret]

I don't wanna upset anyone here, .....

Ok, no worries....I just don't have all answers sometimes.....hope you get your issues worked out. Unfortunately, I don't know what they might be. A bad or no USB map can cause a real mess, but I'd be hard pressed to call that as your issue.....I just don't know, sorry.

 

[pieropontra]

Try copying your smbios into the EFi from me and adopt your usb and see if that changes anything. I spent so many hours trying to figure this lags out and the EFI didn’t seemed to have faults. However when I copied the EFI from my system 1 it worked straight away better. Now after the password it takes 6s to fully load everything and no other lags.

my big lags also take a few seconds to go away, I just have micro lags here and there and they are, trust me, really short lived like 1/3 of a second. The way I notice it? if u connect a bluetooth headphone u can hear these micro lags affecting even audio. It's hard to explain I know. Think this way: let's say u got music playin via Bluetooth and meanwhile u open a safari tab or simply switch from music app to Safari, u can see a super fast hiccup on screen synced with hiccup on audio. Strangely thin not happens with wired audio. Believe me, this is driving me mad. I'm still incline to believe this is a GPU driver related stuff. The fact that everything wrong goes away putting system to sleep and waking it up is the final shot at my psych integrity Many report of various problem are present even on Apple Support website and other forums. People are incline to think on unoptimized Navi / Vega 20 drivers fault 'cause all kind of problems similar and even more badass are reported for 16" MBP (Navi) and MacPro's Pro VegaII (Vega 20) and WX 5700XT (Navi). I think there's nothing more to try, I just have to wait and see if driver maturing will solve these. Thanks for your support and patience.

EDIT: It's worth noting that prior to 10.15.3 everything worked smooth and I use the same EFI. It's also worth noting that the FaceTime/Zoom/Meet etc. macOS problem which affected a lot of people and found place even on big tech website, was later described as an issue with recent drivers and videochat apps need for video encoding (so GPU usage here). Cannot be a coincidence that I got problems since 15.3 then, and right now again my FaceTime was unusable then and now it is, but it's still slow to open and camera fps is rubbish.

 

[dithaack]

Here try this. I just copied the SSDT you posted earlier and adapted to the slot.

If you look at the SSDT, the scope begins at SB.PC01.BR1A. We need to null SL01 and rename it to PEGP. I inserted a condition to only null if it's booted into macOS. Since the SAGE boards have PLX chips, there is an extra step and each slot is separated by pci-bridges. In this case, Slot-5 is pci-bridge @ address 10. Note: If you add extra cards/devices into the pci slots, the numbers may switch so you have to keep an eye on that.

Under the new scope PEGP, we give the device (pci-bridge@10) a name and specify the address. In this case, I named it EGP1 (name can be anything as long as it's not used already).

Here is some pseudo code on how it looks.

Scope (\_SB.PC01.BR1A)
{
    Scope (Sl01)
    {
        Null if macOS
    }

    // create new scope PEGP
    Scope (PEGP)
    {
        // create new device and specify address 10
        Device (EGP1)
        {
            Name (_ADR, 0x00100000)
            // copy rest of thunderbolt code here
            {
            }
        }
    }
}

Hope this helps! When I first started hacking X299, I was probably the first one here with a Sage and got very frustrated when I couldn't figure out how to adapt my SSDTs. Those pci-bridges can be annoying to understand and adapt in your SSDT at first!

Thank you for sharing that! I appreciate the groundwork you've already put in. Hope I can keep learning this stuff to be able to wrap my head around everything.

So far no success in slot 5. I do see the Thunderbolt devices in system report, and IOReg reflects your changes, but the devices won't mount. And if I try to boot with any plugged in I only get black screen and Qcode 62. I tried with Thunderbolt settings in BIOS on and off with same result. Otherwise I simply replaced the SSDT with your new one and reset NVRAM--was there anything else I should've done?
Also, are you aware of any reason why jumping the Titan Ridge pins would make the system run hotter? Weird increase in heat started yesterday and I can't figure out...

 

[djlild7hina]

Thank you for sharing that! I appreciate the groundwork you've already put in. Hope I can keep learning this stuff to be able to wrap my head around everything.

So far no success in slot 5. I do see the Thunderbolt devices in system report, and IOReg reflects your changes, but the devices won't mount. And if I try to boot with any plugged in I only get black screen and Qcode 62. I tried with Thunderbolt settings in BIOS on and off with same result. Otherwise I simply replaced the SSDT with your new one and reset NVRAM--was there anything else I should've done?
Also, are you aware of any reason why jumping the Titan Ridge pins would make the system run hotter? Weird increase in heat started yesterday and I can't figure out...

hmmm can you try updating the thunderbolt firmware with Flashed 50 and/or another slot? I know I had a issues with reboots on firmware 23 in other slots but I don’t have a flasher anymore to update the firmware. My thunderbolt stuff is coming in next week.
As for jumping the pins and heat not sure...

 

[dithaack]

hmmm can you try updating the thunderbolt firmware with Flashed 50 and/or another slot? I know I had a issues with reboots on firmware 23 in other slots but I don’t have a flasher anymore to update the firmware. My thunderbolt stuff is coming in next week.
As for jumping the pins and heat not sure...

Ok, so I just flashed to firmware 50 (the one called "Gigabyte-Vision-D-NVM-50-Elias64Fr-CaseySJ.bin" right?). No difference in slot 5. I can move it around a bit and try. Is it as simple as modifying your code:
Name (_ADR, 0x00100000) // _ADR: Address
to become "0x00080000)" for slot 3? That's the only other Bridge number I've found so far, in case you have the others. Thanks!
EDIT: There was one difference actually in slot 5 with the NVM50--I was actually able to boot. But still no TB3 devices.

 

[djlild7hina]

Ok, so I just flashed to firmware 50 (the one called "Gigabyte-Vision-D-NVM-50-Elias64Fr-CaseySJ.bin" right?). No difference in slot 5. I can move it around a bit and try. Is it as simple as modifying your code:
Name (_ADR, 0x00100000) // _ADR: Address
to become "0x00080000)" for slot 3? That's the only other Bridge number I've found so far, in case you have the others. Thanks!

Yes, just make sure it's still under PC01, otherwise you need to adapt to PC02-> BR2A. It's weird that it recognizes it plugs in but shows no drivers installed.

 

[mm2margaret]

hmmm can you try updating the thunderbolt firmware with Flashed 50 and/or another slot? I know I had a issues with reboots on firmware 23 in other slots but I don’t have a flasher anymore to update the firmware. My thunderbolt stuff is coming in next week.
As for jumping the pins and heat not sure...

So, I also wonder about jumper pins. I have full power connection(s) for the Thunderbolt card and I don't know it would be needed unless jumper these pins are necessary, and how that would add more functionality. According to CaseySJ, and some others I've read, jumpering these pins are necessary to make sure the TB tree shows up even when nothing is connected. Not sure what value that adds, because as long as when something is connected, if the tree is there, that would seem sufficient.

Btw, have you or do you intent to try the 14B version of NVM50? I note that there appears to be two versions of the NVM50, the one you listed above and then there's the 14B version (from Elias, I believe). Curious if the 14B version adds something more to solution.

 

[djlild7hina]

So, I also wonder about jumper pins. I have full power connection(s) for the Thunderbolt card and I don't know it would be needed unless jumper these pins are necessary, and how that would add more functionality. According to CaseySJ, and some others I've read, jumpering these pins are necessary to make sure the TB tree shows up even when nothing is connected. Not sure what value that adds, because as long as when something is connected, if the tree is there, that would seem sufficient.

Btw, have you or do you intent to try the 14B version of NVM50? I note that there appears to be two versions of the NVM50, the one you listed above and then there's the 14B version (from Elias, I believe). Curious if the 14B version adds something more to solution.

I imagine if something is plugged in prior to boot jumping isn't necessary, but that means you would always have to keep something plugged in. I haven't tested this though.

Nope, I'm still on NVM23 since I dont have my raspberry pi anymore. I'm not sure what the difference between the two but I'm going to try the non 14B version since it didn't cause reboot issues for gandem.