X299 Big Sur Support

[Ghostmac1969]

This is the KP that sometimes occurs...

Panic(CPU 0, time 3453995288839): NMIPI for spinlock acquisition timeout, spinlock: 0xffffff878c6d1220, spinlock owner: 0xffffff8788c0f9b0, current_thread: 0xffffff8788c0f9b0, spinlock_owner_cpu: 0x0
RAX: 0x0000000000000000, RBX: 0x0000000000000004, RCX: 0xffffff80066d3f53, RDX: 0xffffff80066d425c
RSP: 0xffffffa1fb154dd0, RBP: 0xffffffa1fb154e50, RSI: 0x0000000000000004, RDI: 0xffffffe282e8f024
R8: 0x0000000000000000, R9: 0x0000000000000024, R10: 0x0000000000000001, R11: 0x0000000000000000
R12: 0x0000000000000000, R13: 0x0000000000000000, R14: 0x0000000080000001, R15: 0xffffffe282e8f024
RFL: 0x0000000000000097, RIP: 0xffffff80066d3f56, CS: 0x0000000000000008, SS: 0x0000000000000010
Backtrace (CPU 0), Frame : Return Address
0xffffffa1fb154c80 : 0xffffff80067eee4b mach_kernel : _interrupt + 0x12b
0xffffffa1fb154cd0 : 0xffffff8006661d39 mach_kernel : _return_to_iret + 0x159
0xffffffa1fb154e50 : 0xffffff7fa4787832 com.apple.driver.AppleGFXHDA : __ZN21AppleGFXHDAController12pollRegisterEiijj + 0x2ca
0xffffffa1fb154e80 : 0xffffff7fa478c737 com.apple.driver.AppleGFXHDA : __ZN21AppleGFXHDAController15interruptFilterEP28IOFilterInterruptEventSource + 0x19f
0xffffffa1fb154ed0 : 0xffffff8006e1bfd1 mach_kernel : __ZN28IOFilterInterruptEventSource23normalInterruptOccurredEPvP9IOServicei + 0x81
0xffffffa1fb154f00 : 0xffffff8009038beb com.apple.iokit.IOPCIFamily : __ZN32IOPCIMessagedInterruptController15handleInterruptEPvP9IOServicei + 0x12b
0xffffffa1fb154f50 : 0xffffff8007695510 com.apple.driver.AppleACPIPlatform : __ZN23AppleACPIPlatformExpert23dispatchGlobalInterruptEi + 0x2e
0xffffffa1fb154f60 : 0xffffff800769e24f com.apple.driver.AppleACPIPlatform : __ZN31AppleACPICPUInterruptController15handleInterruptEPvP9IOServicei + 0x6b
0xffffffa1fb154f80 : 0xffffff80067eee9d mach_kernel : _interrupt + 0x17d
0xffffffa1fb154fd0 : 0xffffff8006661bdd mach_kernel : _hndl_allintrs + 0x11d
0xffffffe28c35baf0 : 0xffffff8006c2373a mach_kernel : _kevt_getstat + 0x16fa
0xffffffe28c35bb90 : 0xffffff8006c2274e mach_kernel : _kevt_getstat + 0x70e
0xffffffe28c35bbd0 : 0xffffff8006c27617 mach_kernel : _kevent_register + 0x997
0xffffffe28c35bcc0 : 0xffffff8006c2a70d mach_kernel : _kevent_id + 0x38d
0xffffffe28c35bdd0 : 0xffffff8006c2aaa8 mach_kernel : _kevent_workq_internal + 0xb8
0xffffffe28c35be00 : 0xffffff8009891a61 com.apple.kec.pthread : _workq_handle_stack_events + 0x9d
0xffffffe28c35be90 : 0xffffff8006bfb6e8 mach_kernel : _workq_kernreturn + 0x748
0xffffffe28c35bf40 : 0xffffff8006d69ceb mach_kernel : _unix_syscall64 + 0x27b
0xffffffe28c35bfa0 : 0xffffff80066621f6 mach_kernel : _hndl_unix_scall64 + 0x16
Kernel Extensions in backtrace:
com.apple.kec.pthread(1.0)[370B9FFE-4A14-3CA7-8908-FD392BC4613E]@0xffffff8009890000->0xffffff8009897fff
com.apple.iokit.IOPCIFamily(2.9)[A18ACD60-A811-3624-B50D-4F929836EE79]@0xffffff8009017000->0xffffff800903efff
com.apple.driver.AppleACPIPlatform(6.1)[D5E73559-87FF-3A4D-A884-3C734F0BB103]@0xffffff800768e000->0xffffff8007704fff
dependency: com.apple.driver.AppleSMC(3.1.9)[30ACBB00-67A3-36BD-AF95-1E6F0CB38447]@0xffffff8007c90000->0xffffff8007ca8fff
dependency: com.apple.iokit.IOACPIFamily(1.4)[65A1D60D-F9AF-37E7-B854-4127FBB3172A]@0xffffff8008ad2000->0xffffff8008ad3fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[A18ACD60-A811-3624-B50D-4F929836EE79]@0xffffff8009017000->0xffffff800903efff
com.apple.driver.AppleGFXHDA(100.1.431)[A45C4893-81FD-3D81-91B5-0C4DC912874F]@0xffffff7fa4784000->0xffffff7fa47e1fff
dependency: com.apple.iokit.IOAudioFamily(300.6.1)[8A293724-D2EF-3EF2-B6D0-245BB15A33DE]@0xffffff8008b35000->0xffffff8008b52fff
dependency: com.apple.iokit.IOGraphicsFamily(585)[BCCD5611-3116-3255-ADBF-C5521D3B39C6]@0xffffff7fa60b3000->0xffffff7fa60e1fff
dependency: com.apple.iokit.IONDRVSupport(585)[81DC638B-EE31-3C9B-98D1-9BC8414D97E9]@0xffffff7fa60f8000->0xffffff7fa6100fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[A18ACD60-A811-3624-B50D-4F929836EE79]@0xffffff8009017000->0xffffff800903efff

 

[Shlonakzeen]

Many thanks guys. I finally managed to get to the installer but it’s very slow and every time it stuck at 15 minutes progress.

 

[kingkong89]

Asus X299 Prime Deluxe - i9-7980XE - XFX Radeon VII 16GB - Asus ThunderbolyEX 3 worked.

During the installation or update, There was twice it will hang will a cursor hanging on top left side of the screen, I had to switch off the computer manually and boot into the installer disk. I have tried a few time, every time same behaviour. but the third time will boot into Big Sur.

My EFI is base on what @Loloflatsix has shared. I update tp OC 6.3 and it worked. Asus Hyper M.2 X16 seems to have some issue though.

 

[lwndow]

In your case, I think there are just a few details to adjust : download different EFI files posted in posts above ( OC 0.6.3) and then you have to compare ACPI file, Kext file and config.plist by side with yours.

Have looked at many, mixed and matched, can't seem to find the right combo and would love some advice. EFI attached (with ROM/MLB/etc removed as well as Resources to keep size down). My MSI AC Carbon has MSR lock disabled in BIOS and NVRAM has always appeared to be working. Above 4G is on. Have a 7900x and Sapphire RX580.

Catalina runs great, so I feel like I'm missing something that's obvious. Can also upload my SysReport from OC if anyone is interested. Using 0.6.4 snapshots with editing in ProperTree. The USB reset SSDT is to disable USB controllers that I don't use in my rig.

FWIW, tried moving to MacPro7,1 (and removed WEG) and could no longer boot from the BigSur USB drive. Suppose it's just not compatible, or again, I'm missing something.

 

[djlild7hina]

EDIT: Moved to https://www.tonymacx86.com/threads/x299-big-sur-support.302143/post-2205842

 

[rustEswan]

So no takers yet for my issue - would it be best for me to start a separate thread for some support on working through the issues I've got with Big Sur install and then come back here with a full write up/EFI folder resource once I've worked everything though?

Just after advice on best way to go about it - thanks

 

[nch107]

So I seem to be having a similar issue as everyone else is here with Big Sur. I actually had Big Sur up and running smoothinly for days upon its offical release. Now i have upgraded my CPU to a i9-9940x with a X299 Prime Deluxe ii Mobo and im able to get to the apple logo with Opencore 0.6.3 and 0.6.4 but it hangs and stalls. I have attached my EFI, my GPu at the moment is a Radeon VI. Let me know what you guys think and what possible changes can be made.

 

[rsabluebulls]

Hi, if you are using the dortania opencore install guide for Intel HEDT everything is working like a charme - you only need 4 ssdt: PLUG, USBX, RTC0, AWAC for a first setup... took me about 30 minutes to make a efi. read, learn and install. you do not need efi from other guys, cause if you do it for yourselves it is easy for you to understand how it works and you will have no problems with further updates (opencore & system)

Hi @ol2003 - you are 100% correct. I reverted to the "base" version with the 4 ssdt and the booting of the installer is going much further.

I get the Apple logo and then the dark grey background with a mouse pointer. It is not going further than this. I don't see the menu bar at the top or the setup screen in the middle... any ideas? Could it be that my Nvme is interfering? I am not planning to install macOS on the nvme but rather a 256GB SSD.

Much appreciated!

 

[lwndow]

First off, this is my first post in years but been lurking and learning here since probably 2011 - although still feel like a massive novice. Second, I think the Build Signatures are broken because I don't seem to be able to make mine update at all.

I am having an issue installing Big Sur - I can boot the installer, complete the first graphical part of the install and reboot. On the reboot I select the Mac OS Installer on my SSD for Big Sur, this time it boots to the progress bar, then mouse pointer appears with the progress bar, screen goes black, shows a spinning logo for a second and reboots. Then this just keeps happening in a loop. When this happens even with the -V boot-arg Its already switched to graphical progress bar so I can't see where its failing.

Its an MSI X299 Pro, i9 10940x, Radeon RX 560, 2x Sabrent Rocket NVMe drives. Opencore 6.3.

I followed the Dortania guide to the letter for manual SSDT builds specific to my machine.

I have a perfectly functioning Catalina 10.15.7 build, sleep, wake, USB map, DRM everything seems to work perfectly except perhaps NVRAM. More on that in a second...

I initially suspected either EC or RCT0-RANGE as the problem because there is some weirdness with this motherboard:

• It has no EC device. In Windows device manager there is no entry for "ACPI Embedded Controller" or similar. And searching the dumped DSDT for PNP0C09 finds "0" results.
• It has both an AWAC and RTC device, with I think, a property that switched (STAS I'm barely even a beginner at ACPI!) to switch between the two, but it also seems to be missing the mapped section for the RTC device (0x70 range, 0x2 length)
• Opencore requires npci=0x2000 boot-arg to boot

I have manually created SSDT's and Im pretty sure they are now working correctly.

In IoregExplorer I can see an EC device the name "ACID0001" and a newly created RTC0 device with name "PNP0B00" (and no old RTC device) with the two ranges properly mapped - address 0x70, length 0x4 and address 0x74, length 0x4.

I have tried a number of things suggested in the Dortania guide including adding vsmcgen=1 to boot-args and replacing VirtualSMC with fake SMC, with and without NVMEfix.kext and WEG but the behaviour is always the same.

Regarding my NVRAM, I have noticed that my while my custom SSDT-PMC at least shows a PMCR device with name "APP9876" in IoregExplorer, it doesn't appear to be working as NVRAM should - Opencore doesn't save any changes to "startup disk" for example.

So I have a couple of questions and one favour to ask:

1. What is the best way for me to debug and collect or view log files to find out more about exactly what point its rebooting if -V is no longer showing the verbose output? It starts to show but once the screen shuts off and comes back with a progress bar and mouse pointer there is no verbose output to see anymore.
2. Is this potentially related to a non-functioning NVRAM implementation - If so some guidance in fixing that would be appreciated.
3. Could someone take a look at my custom SSDT's and give them a sanity check given my novice editing

(EFI folder attached with the SMBIOS cleaned and I removed resources and tools folders to reduce size, please let me know if you'd like to check the original DSDT dump, I'll add that too)




Thanks in advance for any help - and hopefully this can be worked through to another success so we can add another motherboard and config guide to the thread.

Do you see any MSR settings in your bios? On my MSI X299 Carbon I have to disable MSR lock, but seems to work after that. If you have something like that, maybe disable, then change your config list to set AppleXcpmCfgLock to False? if you don't have that, then also set AppleCpuPmCfgLock to True as well? Might affect the NVRAM questions one way or the other.

 

[Bagi1992]

Today I did a fresh install with Big Sur, opencore 0.6.3 after many months of using beta, what I upgraded from Catalina.

Everything went fine, my system is working perfectly, but I can not login into my apple ID. I did generate new serial, system ID etc... tried few different, but no luck. I get this message: "icloud unsupported device"

Interesting thing, I can login in appstore... but not in system preferences/icloud. Do you have guys any idea?