X299 Big Sur Support

[oli.mathieu]

@TheBloke
FYI : https://dortania.github.io/OpenCore-Post-Install/universal/memory.html#mapping-our-memory

 

[oli.mathieu]

To anyone who succeed to install BS on Mobo without NVRAM support (Via Real Mac) : can you Update BS afterward (Without real Mac) ?
Thanks

 

[S1lla]

@apfelnico found the solution for the boot issues on big sur and the error code 97.

"It seems Apple's new USB-ASMedia connection is broken. We use "ASMedia2142" on our boards, but Apple's driver is for "ASMedia3142". This driver runs first, then it doesn't run anymore on further reboots. Then the higher-level driver takes over, and it doesn't work with our chip. But the old working "AppleUSBXHCIPCI" is still in the system, which is included with Catalina. We can fix this by loading this Kext for the ASMedia controllers."

 

[Loloflatsix]

@apfelnico found the solution for the boot issues on big sur and the error code 97.

"It seems Apple's new USB-ASMedia connection is broken. We use "ASMedia2142" on our boards, but Apple's driver is for "ASMedia3142". This driver runs first, then it doesn't run anymore on further reboots. Then the higher-level driver takes over, and it doesn't work with our chip. But the old working "AppleUSBXHCIPCI" is still in the system, which is included with Catalina. We can fix this by loading this Kext for the ASMedia controllers."

Great !

 

[TheBloke]

@TheBloke
FYI : https://dortania.github.io/OpenCore-Post-Install/universal/memory.html#mapping-our-memory

Oh awesome! Thanks for the link. I will try this today. So I was on the right lines with using CustomMemory, but it seems that the most important thing is that you have to specify all 12 slots as filled, and empty slots you mark as EmptyDIMM rather than leaving them blank.

 

[TheBloke]

To anyone who succeed to install BS on Mobo without NVRAM support (Via Real Mac) : can you Update BS afterward (Without real Mac) ?

We don't know yet, we'll have to wait for a someone with non-working NVRAM to try it.

PS. It's not a requirement to use a real mac as the updating machine. A hack is fine too, as long as it has working NVRAM.

Last night I did a fresh Big Sur install on a test 128GB SSD, on my X299 machine. Then I moved the SSD to my old H77 hack and ran it there, and it worked fine. There's definitely no per-system sealing of the drives.

So if you have any other machine which has working NVRAM and is capable of upgrading/installing Big Sur, you can use it as a surrogate for your broken-NVRAM X299.

But yeah, we don't yet know if future updates will require working NVRAM, or if they might succeed. Either is possible at this stage. We'll have to wait until someone tests it, eg by updating from 11.0.1 to 11.1 on their no-NVRAM X299, and reports back.

Worst case you will always have to use another machine to do any update on Big Sur, until a proper fix for the non-working NVRAM has been discovered.

 

[Junologue]

@TheBloke
FYI : https://dortania.github.io/OpenCore-Post-Install/universal/memory.html#mapping-our-memory

@apfelnico found the solution for the boot issues on big sur and the error code 97.

"It seems Apple's new USB-ASMedia connection is broken. We use "ASMedia2142" on our boards, but Apple's driver is for "ASMedia3142". This driver runs first, then it doesn't run anymore on further reboots. Then the higher-level driver takes over, and it doesn't work with our chip. But the old working "AppleUSBXHCIPCI" is still in the system, which is included with Catalina. We can fix this by loading this Kext for the ASMedia controllers."

Thanks for both those tips.
Now i got a MacPro7,1 without memory notifications + no reboot issues. Lovely!

 

[TheBloke]

Yup MacPro7,1 memory notification gone for me too! Thanks again for pointing out the guide, @oli.mathieu

 

[Junologue]

Yup MacPro7,1 memory notification gone for me too! Thanks again for pointing out the guide, @oli.mathieu

When was this even added to the guide? Have been waiting so long for a fix regarding this disturbing popup, and i’ve completely missed this

 

[TheBloke]

When was this even added to the guide? Have been waiting so long for a fix regarding this disturbing popup, and i’ve completely missed this

Me too! I theorised that CustomMemory could be used to fix this, and tried it myself a few days ago. I got as far as realising we probably needed to add the 12 sockets that the Mac Pro has, but didn't get as far as thinking to test having them all full, even when they're not.

I just checked the commits and the new guide was first released 15 hours ago.