Contribute
Register

X299 Big Sur Support

Status
Not open for further replies.
Thank you for support. Problem has been solved.

It was the bios version 3405 that caused the KP. Loaded version 3302 and finally installation without problems of 11.4 beta 1.

Mac pro 7.1, no WEG, no string agdpmod = in boot args. Some first tests:
Glad you got it sorted - thought it was the bios. Are you using the modded one I sent (@izo1) with the Apple logo?

If not it is a nice authentic GUI if that appeals!
 
Bravo!

If things ever get hairy in Big Sur check the ASMEDIA ports. I found on my board that Big Sur identified it wrong and it would cause a panic on restart which in turn caused the driver to fail to load on the start. Here's the fix.

I didn't come up with it but I think all users should know about it.

I believe it's not needed anymore in 11.3? I havent used the ASMedia kext in a while but maybe i'm wrong haha
 
I believe it's not needed anymore in 11.3? I havent used the ASMedia kext in a while but maybe i'm wrong haha

I'm not using it at the moment either but the potential problem @NorthAmTransAm described does kind of match what I was seeing - cold boot the ASmedia controllers were nearly always there, restart and one or both would have disappeared, same after a failed sleep or wake attempt.

I didn't spend ages debugging it though, just tried to fix sleep first and it happened to fix the strange USB behaviour too. As soon as I added the SSDT-GPRW and ACPI patch its all behaved perfectly. I'll keep an eye on it, at least its there if needed :)
 
I'm not using it at the moment either but the potential problem @NorthAmTransAm described does kind of match what I was seeing - cold boot the ASmedia controllers were nearly always there, restart and one or both would have disappeared, same after a failed sleep or wake attempt.

I didn't spend ages debugging it though, just tried to fix sleep first and it happened to fix the strange USB behaviour too. As soon as I added the SSDT-GPRW and ACPI patch its all behaved perfectly. I'll keep an eye on it, at least its there if needed :)

Sounds good :) Btw I think GPRW disables wake from usb devices. Not a deal breaker for some people but it's nice to just press a button on the bt keyboard to wake up :)

If you really wanted you could edit your GPU-DISABLE SSDT and device properties to have the name of the RTX card and fix the slot number. See my Rampage VI Extreme Encore EFI for an example

 
@NorthAmTransAm and @CaseySJ my Thunderbolt EX4 card is coming in today so I'll be doing some tests. Are the commands to read/flash the chip are different than the Titan Ridge cards?
 
I'm not using it at the moment either but the potential problem @NorthAmTransAm described does kind of match what I was seeing - cold boot the ASmedia controllers were nearly always there, restart and one or both would have disappeared, same after a failed sleep or wake attempt.

I didn't spend ages debugging it though, just tried to fix sleep first and it happened to fix the strange USB behaviour too. As soon as I added the SSDT-GPRW and ACPI patch its all behaved perfectly. I'll keep an eye on it, at least its there if needed :)

It was driving me nuts!

I see now however that my 3.1 bus has the standard AppleUSBXHCIPCI loaded. However, I've read that despite that being loaded, without the ASMEDIA.kext they still get the crash. I'm going to experiment with a min/max version for the kext and see if it can load.

Here's the original post I got it from.
#969

And here is a bit of the confusion.

#47
 
@djlild7hina, any idea what could be causing KP from my post? I am using 11.2.3.
I believe it is somehow connected to 10gbe or USB, but I don't really know how to read KP report.

Any good reason to upgrade to newer beta with X299 SAGE 10G and dual Radeon VII...? Also, is is possible to "upgrade" beta to final without doing clean install?
 
It was driving me nuts!

I see now however that my 3.1 bus has the standard AppleUSBXHCIPCI loaded. However, I've read that despite that being loaded, without the ASMEDIA.kext they still get the crash. I'm going to experiment with a min/max version for the kext and see if it can load.

Here's the original post I got it from.
#969

And here is a bit of the confusion.

#47

I see now. Not confusing at all.

We dont want 3142 to load. We want 2142 to load. Got it!
 
I don't have any patched firmwares just yet. Still experimenting. @CaseySJ might have an SSDT for you to try though!

Ah I figured there was no patched firmware yet but was just curious on extracting the firmware.
 
Status
Not open for further replies.
Back
Top