macOS 11 Big Sur on Unsupported Macs Thread

[Macdctr]

I'm a bit puzzled: as far as I know our Retina 15-inch rMBP's @ 10,1 (mid-2012 and early-2013) are unsupported for Big Sur. So technically your device is not natively supported unless you mean you are able to have OTA system updates by virtue of OCLP????

I am still on 11.3.1 so I can't verify your noticing faster performance yet. It sounds tempting to upgrade, so thanks!

Curious: what aspects seem snappier? Startup ... opening certain apps ... download times ... etc.?

What I'm saying is from the operator's perspective, I can go to System Preference and then select Software Update to see if there's any OS updates available to select and update my computer.

Since using OCLP which I stated, I have been able to update the OS on my computer thru Software Update in System Preference just like I normally would if this computer was natively supported.

As for snappier performance, I have noticed Safari coming up faster than I usually have been seeing it come up with web pages refreshing faster. I'm seeing snappier performance with any app I'm running or when opening up a finder window everything seems to come up alittle faster than before the OS update.

This is just an observation of overall performance of my laptop running OS 11.5 beta software as compared to 11.4 beta I was running earlier today before this update.

 

[buckrock]

What I'm saying is from the operator's perspective, I can go to System Preference and then select Software Update to see if there's any OS updates available to select and update my computer.

Since using OCLP which I stated, I have been able to update the OS on my computer thru Software Update in System Preference just like I normally would if this computer was natively supported.

As for snappier performance, I have noticed Safari coming up faster than I usually have been seeing it come up with web pages refreshing faster. I'm seeing snappier performance with any app I'm running or when opening up a finder window everything seems to come up alittle faster than before the OS update.

This is just an observation of overall performance of my laptop running OS 11.5 beta software as compared to 11.4 beta I was running earlier today before this update.

Great -- thanks for clarifying -- I understand!

Again, I'm tempted to update to 11.5 beta 1. I use the InstallAssistant.pkg with BarryKN's 0.5.1 micropatcher method, so maybe I'll hold off on the update until they release 11.5 beta 2.

I wonder if folks are noticing speedier systems on the 11.4 RC installs? ... or are the performance improvements linked solely to the 11.5 builds? Anyone know?

 

[Jonathan50]

cMP3,1 running BigSur 11.2.3 (20D91) oclp 0.1.5, opencore 0.6.9, installed with mac-flashed GTX680 (GK104) works ok and I can see all screens.

When I swap the GTX680 for a GT710 (GK208, also Kepler, metal enabled) all I get is a black screen with a moving mouse pointer.

When I swap the GTX680 for a GT120 (non-Kepler, not metal enabled) I can see all screens and works a bit slower.

Is it possible that Kepler 2.0 cards (e.g. GK208) are no longer supported in Big Sur?
The GT710 (GK208) works fine in El Capitan with nvidia drivers and in Mojave natively, no boot screens of course.

Edit: after a 5,7gb "ota" update to 11.3.1 (20E241) the gt710 issue persists.

 

[Larsvonhier]

That is a great and well informed answer, @Larsvonhier ! But... "They most likely ignore feedback on betas from such machines" - apparently not correct, I submitted feedback on Big Sur beta from my unsupported Mac, and got a fix and even a reply to ask me to check it was working! (Amongst many others I sent with no reply at all! Which I am sure is completely normal and most people's experience - and mine too, apart from that one!)

…what I also confirmed under „my personal experience“. So totally agree!

 

[Dilli]

deleted

 

[Ausdauersportler]

cMP3,1 running BigSur 11.2.3 (20D91) oclp 0.1.5, opencore 0.6.9, installed with mac-flashed GTX680 (GK104) works ok and I can see all screens.

When I swap the GTX680 for a GT710 (GK208, also Kepler, metal enabled) all I get is a black screen with a moving mouse pointer.

When I swap the GTX680 for a GT120 (non-Kepler, not metal enabled) I can see all screens and works a bit slower.

Is it possible that Kepler 2.0 cards (e.g. GK208) are no longer supported in Big Sur?
The GT710 (GK208) works fine in El Capitan with nvidia drivers and in Mojave natively, no boot screens of course.

Edit: after a 5,7gb "ota" update to 11.3.1 (20E241) the gt710 issue persists.

The K610M based on the GK208 is still working fine within the modded iMac 2009-2011 and Big Sur - so it cannot be this particular chip itself. We would have seen posts here if this GPU fails like yours. Does not really help, I know.

 

[Jonathan50]

The K610M based on the GK208 is still working fine within the modded iMac 2009-2011 and Big Sur - so it cannot be this particular chip itself. We would have seen posts here if this GPU fails like yours. Does not really help, I know.

Appreciate your reply. The k610m is listed as a GK208 Kepler core and the gt710 as a GK208B, not sure if that minor (?) detail is of any significance. In any case I'll test some more with my limited means, see if I can figure out what's happening here and report back.

 

[BeatCrazy]

Raising this concern here, as I've been troubleshooting for over a week, and I feel the issue is related to OCLP.

I'm using OCLP 11.3.1 on my iMac 11,1 Late 2009 27". Bluetooth is my issue 🙂

My Bluetooth module (BCM943602CDP, which is an updated BT 4.2 module) was turning itself off and just flat out not working. Wi-Fi works fine. I would try all kinds of troubleshooting steps, including resetting PRAM, resetting the module, deleting .plist files, SMC reset, you name it, I tried them all, including Bluetooth Hardware IO Tools 7.3.

Occasionally, I could get BT working, but after 5-10 minutes, it would completely stop. Although the BT radio toggle was "on", it was if the module was off. After a reboot, it would still show as "off", and eventually the module wasn't even recognized by macOS, like I had no card in the system.

So, I bought a new BCM943602CDP and installed it today. Essentially the same situation. It worked for about 5 minutes, but now it's no longer recognized.

To be safe, I rebuilt OCLP 1.5, but that didn't have any impact. So now I have a "Bluetooth off" icon in my menu bar I can't even get rid of :-/ And no Bluetooth of course.

What can I help test to see if it's something that can be fixed via OCLP?

 

[Ausdauersportler]

Raising this concern here, as I've been troubleshooting for over a week, and I feel the issue is related to OCLP.

I'm using OCLP 11.3.1 on my iMac 11,1 Late 2009 27". Bluetooth is my issue 🙂

My Bluetooth module (BCM943602CDP, which is an updated BT 4.2 module) was turning itself off and just flat out not working. Wi-Fi works fine. I would try all kinds of troubleshooting steps, including resetting PRAM, resetting the module, deleting .plist files, SMC reset, you name it, I tried them all, including Bluetooth Hardware IO Tools 7.3.

Occasionally, I could get BT working, but after 5-10 minutes, it would completely stop. Although the BT radio toggle was "on", it was if the module was off. After a reboot, it would still show as "off", and eventually the module wasn't even recognized by macOS, like I had no card in the system.

So, I bought a new BCM943602CDP and installed it today. Essentially the same situation. It worked for about 5 minutes, but now it's no longer recognized.

To be safe, I rebuilt OCLP 1.5, but that didn't have any impact. So now I have a "Bluetooth off" icon in my menu bar I can't even get rid of :-/ And no Bluetooth of course.

What can I help test to see if it's something that can be fixed via OCLP?

Before leading us into a complete wrong direction could you please check your hardware with the latest supported macOS version on your iMac? Does to run with High Sierra?

I own the same iMac models using the same BT card model having no problems with OCLP at all.

My guess: Check and change the Mini PCIe carrier board and check the soldering of the D+/D- cabling.

 

[BeatCrazy]

Before leading us into a complete wrong direction could you please check your hardware with the latest supported macOS version on your iMac? Does to run with High Sierra?

I own the same iMac models using the same BT card model having no problems with OCLP at all.

My guess: Check and change the Mini PCIe carrier board and check the soldering of the D+/D- cabling.

Yes, it ran fine on High Sierra. Picture of my (own) PCIe carrier board is below. I also triple checked all BT antenna connections. The most obvious issue would be the card itself, but the behavior is the same with a completely different card.

Wi-Fi works perfect. Great speed, no dropouts. What else could explain Bluetooth working only occasionally, but mostly not at all? Forgot to mention, it's not USB 3.0 interference. I had the same "turn off" behavior while using in 3 different rooms.

Also, I've always connected the BT antenna to the connector below. I even tried connecting it to different connections, but that didn't work at all:

 

[buckrock]

Raising this concern here, as I've been troubleshooting for over a week, and I feel the issue is related to OCLP.

I'm using OCLP 11.3.1 on my iMac 11,1 Late 2009 27". Bluetooth is my issue 🙂

My Bluetooth module (BCM943602CDP, which is an updated BT 4.2 module) was turning itself off and just flat out not working. Wi-Fi works fine. I would try all kinds of troubleshooting steps, including resetting PRAM, resetting the module, deleting .plist files, SMC reset, you name it, I tried them all, including Bluetooth Hardware IO Tools 7.3.

Occasionally, I could get BT working, but after 5-10 minutes, it would completely stop. Although the BT radio toggle was "on", it was if the module was off. After a reboot, it would still show as "off", and eventually the module wasn't even recognized by macOS, like I had no card in the system.

So, I bought a new BCM943602CDP and installed it today. Essentially the same situation. It worked for about 5 minutes, but now it's no longer recognized.

To be safe, I rebuilt OCLP 1.5, but that didn't have any impact. So now I have a "Bluetooth off" icon in my menu bar I can't even get rid of :-/ And no Bluetooth of course.

What can I help test to see if it's something that can be fixed via OCLP?

You probably did it, but I have to ask: when you reset the bluetooth module (option-shift click the bluetooth menubar icon) did you first click "remove all devices"? Yeah, I thought so!

I suspect Ausdauersportler is on the right track especially if BT works for a few minutes when the boards are cold. Also, try booting a supported MacOS as he suggested. That could isolate the problem to Big Sur.

Do you have a pristine admin account you could try to see if a user-level conflict exists? Good luck!

Edit: I missed your response while I was typing. Interesting: it works without problems on High Sierra!

 

[BeatCrazy]

You probably did it, but I have to ask: when you reset the bluetooth module (option-shift click the bluetooth menubar icon) did you first click "remove all devices"? Yeah, I thought so!

I suspect Ausdauersportler is on the right track especially if BT works for a few minutes when the boards are cold. Also, try booting a supported MacOS as he suggested. That could isolate the problem to Big Sur.

Do you have a pristine admin account you could try to see if a user-level conflict exists? Good luck!

Edit: I missed your response while I was typing. Interesting: it works without problems on High Sierra!

I haven't run High Sierra in a while, but I'm willing to set up a new instances for additional troubleshooting. For testing purposes, can I dual boot from a USB (SSD) instance of High Sierra? Could you kindly point me in the right direction for how to do that, considering I'm using OCLP? I know how to do it if I was running a supported OS, but I don't want to break my OCLP Big Sur 🙂

 

[Ausdauersportler]

Yes, it ran fine on High Sierra. Picture of my (own) PCIe carrier board is below. I also triple checked all BT antenna connections. The most obvious issue would be the card itself, but the behavior is the same with a completely different card.

Wi-Fi works perfect. Great speed, no dropouts. What else could explain Bluetooth working only occasionally, but mostly not at all? Forgot to mention, it's not USB 3.0 interference. I had the same "turn off" behavior while using in 3 different rooms.



Also, I've always connected the BT antenna to the connector below. I even tried connecting it to different connections, but that didn't work at all:

Ran fine! So get an external USB connected hard drive, set up High Sierra (as we always recommend for exactly this reason) on this external disk and forget OCLP and Big Sur for the time being. It is about testing your hardware on a supported macOS version. This is slightly off topic here as long a you cannot proof it is an Big Sur or OCLP problem at all.

 

[Jack Neill]

I just used the latest OCLP to get a Mid 2009 iMac Big Sur. Works as good as Mojave did with some graphical glitches.

 

[buckrock]

I haven't run High Sierra in a while, but I'm willing to set up a new instances for additional troubleshooting. For testing purposes, can I dual boot from a USB (SSD) instance of High Sierra? Could you kindly point me in the right direction for how to do that, considering I'm using OCLP? I know how to do it if I was running a supported OS, but I don't want to break my OCLP Big Sur 🙂

It is super simple. If you can create an installer USB with High Sierra 10.13.6 on it, you simply use option key startup and select the installer. Have your USB SSD drive (I use a Crucial X8, 500GB) plugged in and format it MacOS Extended (Journaled), GUID partition using the Disk Utility on the Installer drive. Then just install High Sierra to the SSD drive. Hopefully you have a Time Machine backup FROM HIGH SIERRA so you can transfer your apps and settings to the new external drive. This is important since High Sierra will not recognize a Big Sur Time Machine backup!

I just ran GibMacOS and found this entry for the InstallAssistant.pkg for the latest High Sierra from this sucatalog.:

17. macOS High Sierra 10.13.6 (17G66) - 041-91758 - Added 2019-10-19 18:19:55.

If you need more help in getting the correct InstallAssistant or in using it to prepare your Installer USB, let us know.

 

[BeatCrazy]

Ran fine! So get an external USB connected hard drive, set up High Sierra (as we always recommend for exactly this reason) on this external disk and forget OCLP and Big Sur for the time being. It is about testing your hardware on a supported macOS version. This is slightly off topic here as long a you cannot proof it is an Big Sur or OCLP problem at all.

Indeed. I was able to make a test boot of HS, and also experienced the unexpected behavior.

After removing the HS boot SSD (external), I seem to have mangled my OCLP booter with this this message:

It is super simple. If you can create an installer USB with High Sierra 10.13.6 on it, you simply use option key startup and select the installer. Have your USB SSD drive (I use a Crucial X8, 500GB) plugged in and format it MacOS Extended (Journaled), GUID partition using the Disk Utility on the Installer drive. Then just install High Sierra to the SSD drive. Hopefully you have a Time Machine backup FROM HIGH SIERRA so you can transfer your apps and settings to the new external drive. This is important since High Sierra will not recognize a Big Sur Time Machine backup!

I just ran GibMacOS and found this entry for the InstallAssistant.pkg for the latest High Sierra from this sucatalog.:

17. macOS High Sierra 10.13.6 (17G66) - 041-91758 - Added 2019-10-19 18:19:55.

If you need more help in getting the correct InstallAssistant or in using it to prepare your Installer USB, let us know.

Appreciate it sir! I was able to do exactly as you described and created a bootable SSD for HS. My Bluetooth ended up being flaky there too, so I suppose I'm off to find an external dongle. I dunno what the hell caused my PCIe BT carrier board adapter to stop working. At least that's the only thing I can point to, since I've ruled out the OS and the BT card.

 

[Pri-est]

Always without PCI-E USB expansion boards to avoid the freeze?

I don't use any PCI-Express devices in that old granny =)

 

[Ausdauersportler]

I haven't run High Sierra in a while, but I'm willing to set up a new instances for additional troubleshooting. For testing purposes, can I dual boot from a USB (SSD) instance of High Sierra? Could you kindly point me in the right direction for how to do that, considering I'm using OCLP? I know how to do it if I was running a supported OS, but I don't want to break my OCLP Big Sur 🙂

Exchange the PCIe carrier board and redo the cabling. The odds you got to BT/WiFi cards with dead BT are low....although all these (used) cards might end up on the used parts market for a reason.

About the security violation: Disable SBM, again. Booting into High Sierra can mess the Big Sur Preboot I am told. How to fix this using the /etc/fstab has been published some posts ago...To fix the Preboot you can re-install Big Sur or wait for the next update (11.4). Meanwhile fix HS auto mount of Big Sur partitions. Do not mount a single one within HS.

 

[David dongfox]

after update to 11.4 RC from OCLP. sidecar with my ipad is not working. help !

 

[indiawallah]

Had a little strange situation when performing an OTA update to the latest 11.5 Beta. Once the update had installed the backlight was working and the F5/ F6 keys were working. The 1st time I have had such a situation. However after performing the Post install volume patch and rebuilding OP to my internal drive on reboot there was no more backlight or F5/F6 functionality. Anyone else had this?

 

[BeatCrazy]

Exchange the PCIe carrier board and redo the cabling. The odds you got to BT/WiFi cards with dead BT are low....although all these (used) cards might end up on the used parts market for a reason.

About the security violation: Disable SBM, again. Booting into High Sierra can mess the Big Sur Preboot I am told. How to fix this using the /etc/fstab has been published some posts ago...To fix the Preboot you can re-install Big Sur or wait for the next update (11.4). Meanwhile fix HS auto mount of Big Sur partitions. Do not mount a single one within HS.

I appreciate the tips. I was able to do a 100% wipe and re-install. Took some time, but I'm back to a fresh install of OCLP.

 

[macinfo]

Had a little strange situation when performing an OTA update to the latest 11.5 Beta. Once the update had installed the backlight was working and the F5/ F6 keys were working. The 1st time I have had such a situation. However after performing the Post install volume patch and rebuilding OP to my internal drive on reboot there was no more backlight or F5/F6 functionality. Anyone else had this?

Have the same on a MacBookPro4,1 (11.5Beta1 full install, OCLP 0.1.5). I think that’s a smaller, bearable disadvantage of having accelerated graphics on these older GPUs, at least for now.

## It’s kinda funny, before the post-install patch was applied:
keyboard backlight is working (also controllable via keyboard), but display brightness is stuck to its current setting (not controllable at all).

## After the post-install patch it’s the other way round:
keyboard backlight is disabled, but display brightness setting is fully working (also controllable via keyboard).

Other than that, it’s really great having such old machines running this well, so thanks again to all involved for that!

 

[Jonathan50]

Borrowed a second gt710 from a friend to test with. On both the cMP3,1 and cMP5,1 the issue persists. So nothing wrong with my gt710. At the end of the BigSur boot process I get a black screen with a mouse pointer that reacts to mouse movement, but no Finder/Desktop. Abrupt movement of the mouse makes the pointer larger, as expected.

The only difference is that on the cMP5,1 I can see the boot picker and "white over black" progress bar whereas on the cMP3,1 I can see none of those things.

Both gt710's work fine with Mojave on hdmi and dvi outputs, therefore:

For the time being I tend to believe that BigSur has ended support for GK208(B) Kepler 2.0 core gpus on cMP's.

 

[xanderon]

panic & crashes with BS 11.3.1 and OCLP 0.1.5

i experience random reboots (sometimes with apples notification that my machine crashed, in different languages on reboot) and still can't pin point it down to the main reason.

I also collected some reports and try to collect more. there are no crash logs on the EFI partition.
its totally random and I think its my SSD+HDD self-made FusionDrive, but not totally sure. maybe you guys can read something

thanks in advance.

panic(cpu 1 caller 0xffffff802ea9f6b6): [data.kalloc.256]: element modified after free (off:0, val:0x0000f80000000000, sz:256, ptr:0xffffff938e6f7100, prot:zero)
    0: 0x0000f80000000000
   32: 0x0000ff0000000000
  144: 0x0000ff0000000000
  176: 0x0000ff0000000000
  184: 0x0000ff0000000000
Backtrace (CPU 1), Frame : Return Address
0xffffffa0f2323230 : 0xffffff802e28e02d mach_kernel : _handle_debugger_trap + 0x3fd
0xffffffa0f2323280 : 0xffffff802e3d48e3 mach_kernel : _kdp_i386_trap + 0x143
0xffffffa0f23232c0 : 0xffffff802e3c4eda mach_kernel : _kernel_trap + 0x55a
0xffffffa0f2323310 : 0xffffff802e232a2f mach_kernel : _return_from_trap + 0xff
0xffffffa0f2323330 : 0xffffff802e28d84d mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffa0f2323450 : 0xffffff802e28db43 mach_kernel : _panic_trap_to_debugger + 0x273
0xffffffa0f23234c0 : 0xffffff802ea9d68a mach_kernel : _panic + 0x54
0xffffffa0f2323530 : 0xffffff802ea9f6b6 mach_kernel : _kheap_temp_leak_panic + 0x1b7c
0xffffffa0f23239b0 : 0xffffff802e2ec816 mach_kernel : _work_interval_port_type_render_server + 0x4446
0xffffffa0f2323a20 : 0xffffff802e29d60c mach_kernel : _ipc_thread_port_unpin + 0x1cc
0xffffffa0f2323a70 : 0xffffff802e26998e mach_kernel : _ipc_kmsg_get_from_kernel + 0xae
0xffffffa0f2323ad0 : 0xffffff802e294767 mach_kernel : _mach_msg_send_from_kernel_proper + 0x37
0xffffffa0f2323b00 : 0xffffff802ea24320 mach_kernel : __ZN12IOUserClient18_sendAsyncResult64EPyiS0_jj + 0x280
0xffffffa0f2323c40 : 0xffffff8030fb8a6f com.apple.iokit.IOTimeSyncFamily : __ZN20IOTimeSyncUserClient21sendAsyncNotificationEjyy + 0x7f
0xffffffa0f2323ca0 : 0xffffff8030fbd48b com.apple.iokit.IOTimeSyncFamily : __ZN17IOTimeSyncService16sendNotificationEjyy + 0xb3
0xffffffa0f2323cf0 : 0xffffff7fc796c229 com.apple.plugin.IOgPTPPlugin : __ZN16IOTimeSyncDomain18receivedSyncOnPortEP14IOTimeSyncPortP20IOTimeSyncDomainSync + 0xbe1
0xffffffa0f2323de0 : 0xffffff7fc7959713 com.apple.plugin.IOgPTPPlugin : __ZN26IOTimeSyncTimeSyncTimePort14synthesizeSyncEv + 0x167
0xffffffa0f2323e90 : 0xffffff7fc796eba5 com.apple.plugin.IOgPTPPlugin : __ZN24IOTimeSyncLocalClockPort13syncTimerFireEP18IOTimerEventSource + 0x13
0xffffffa0f2323eb0 : 0xffffff802e9f54f5 mach_kernel : __ZN18IOTimerEventSource15timeoutSignaledEPvS0_ + 0xa5
0xffffffa0f2323f20 : 0xffffff802e9f4c88 mach_kernel : __ZN18IOTimerEventSource12checkForWorkEv + 0x38
0xffffffa0f2323f30 : 0xffffff802e9eeaae mach_kernel : __ZN10IOWorkLoop15runEventSourcesEv + 0x11e
0xffffffa0f2323f70 : 0xffffff802e9ee096 mach_kernel : __ZN10IOWorkLoop10threadMainEv + 0x36
0xffffffa0f2323fa0 : 0xffffff802e23213e mach_kernel : _call_continuation + 0x2e
      Kernel Extensions in backtrace:
         com.apple.iokit.IOTimeSyncFamily(980.4)[A5FA159E-C468-37EB-92A2-A4B6E527C671]@0xffffff8030fac000->0xffffff8030fc7fff
            dependency: com.apple.iokit.IONetworkingFamily(3.4)[EFF68ECC-483B-3BAC-82B9-09C8F0600009]@0xffffff8030ad2000->0xffffff8030ae8fff
         com.apple.plugin.IOgPTPPlugin(980.4)[DA74055E-BAE8-30FB-86CD-0D4A6B5ABBD8]@0xffffff7fc7946000->0xffffff7fc79aafff
            dependency: com.apple.iokit.IOHIDFamily(2.0.0)[C365D2A4-769B-3399-9F8D-31DDAA238589]@0xffffff8030a0e000->0xffffff8030a6afff
            dependency: com.apple.iokit.IONetworkingFamily(3.4)[EFF68ECC-483B-3BAC-82B9-09C8F0600009]@0xffffff8030ad2000->0xffffff8030ae8fff
            dependency: com.apple.iokit.IOSkywalkFamily(1)[8E95C676-D763-3923-BE43-E8BE08DD3C23]@0xffffff8030e2a000->0xffffff8030e4bfff
            dependency: com.apple.iokit.IOTimeSyncFamily(980.4)[A5FA159E-C468-37EB-92A2-A4B6E527C671]@0xffffff8030fac000->0xffffff8030fc7fff
            dependency: com.apple.kec.Libm(1)[526EF6DE-89A2-334E-A748-F37E33579C6F]@0xffffff803130a000->0xffffff8031317fff

Process name corresponding to current thread: kernel_task
Boot args: keepsyms=1 debug=0x100 chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
20E241

Kernel version:
Darwin Kernel Version 20.4.0: Thu Apr 22 21:46:47 PDT 2021; root:xnu-7195.101.2~1/RELEASE_X86_64
Kernel UUID: 068F99A3-1DB3-31C0-87D5-09942F122BB6
KernelCache slide: 0x000000002e000000
KernelCache base:  0xffffff802e200000
Kernel slide:      0x000000002e010000
Kernel text base:  0xffffff802e210000
__HIB  text base: 0xffffff802e100000
System model name: iMac12,2 (Mac-7BA5B2D9E42DDD94)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 3268069509353
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x000002f8e81f51aa
  Sleep   : 0x0000000000000000 0x0000000000000000 0x0000000000000000
  Wake    : 0x0000000000000000 0x000000129872d1d4 0x0000000000000000

panic(cpu 6 caller 0xffffff80047c52a6): Kernel trap at 0xffffff80047a5b32, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000000000000000, CR3: 0x0000000372106247, CR4: 0x00000000000626e0
RAX: 0x0000000000000060, RBX: 0x0000000000000000, RCX: 0x0000000000000007, RDX: 0x0000000000000001
RSP: 0xffffffa0d0443b20, RBP: 0xffffffa0d0443b90, RSI: 0x0000600002520000, RDI: 0xffffff86a5fdb300
R8:  0xffffff8021400000, R9:  0x000ffffffffff000, R10: 0xffffff801238ac90, R11: 0xffffff8013a24490
R12: 0xffffff86a5fdb300, R13: 0x000000015fa12000, R14: 0x0000600002520000, R15: 0x0000000000000000
RFL: 0x0000000000010206, RIP: 0xffffff80047a5b32, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x0000000000000000, Error code: 0x0000000000000000, Fault CPU: 0x6, PL: 1, VF: 0

Backtrace (CPU 6), Frame : Return Address
0xffffffa0d0443540 : 0xffffff800468e02d mach_kernel : _handle_debugger_trap + 0x3fd
0xffffffa0d0443590 : 0xffffff80047d48e3 mach_kernel : _kdp_i386_trap + 0x143
0xffffffa0d04435d0 : 0xffffff80047c4eda mach_kernel : _kernel_trap + 0x55a
0xffffffa0d0443620 : 0xffffff8004632a2f mach_kernel : _return_from_trap + 0xff
0xffffffa0d0443640 : 0xffffff800468d84d mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffa0d0443760 : 0xffffff800468db43 mach_kernel : _panic_trap_to_debugger + 0x273
0xffffffa0d04437d0 : 0xffffff8004e9d68a mach_kernel : _panic + 0x54
0xffffffa0d0443840 : 0xffffff80047c52a6 mach_kernel : _sync_iss_to_iks + 0x2c6
0xffffffa0d04439c0 : 0xffffff80047c4f8d mach_kernel : _kernel_trap + 0x60d
0xffffffa0d0443a10 : 0xffffff8004632a2f mach_kernel : _return_from_trap + 0xff
0xffffffa0d0443a30 : 0xffffff80047a5b32 mach_kernel : _phys_attribute_clear + 0x1a2
0xffffffa0d0443b90 : 0xffffff80047523b7 mach_kernel : _vm_page_balance_inactive + 0x107
0xffffffa0d0443be0 : 0xffffff8004764874 mach_kernel : _vm_page_queues_remove + 0x574
0xffffffa0d0443c30 : 0xffffff8004765e17 mach_kernel : _vm_page_free_prepare_queues + 0x57
0xffffffa0d0443c70 : 0xffffff8004748c28 mach_kernel : _vm_io_reprioritize_init + 0x1998
0xffffffa0d0443ce0 : 0xffffff80047477ba mach_kernel : _vm_io_reprioritize_init + 0x52a
0xffffffa0d0443d10 : 0xffffff8004748ad5 mach_kernel : _vm_io_reprioritize_init + 0x1845
0xffffffa0d0443d40 : 0xffffff8004747ce2 mach_kernel : _vm_io_reprioritize_init + 0xa52
0xffffffa0d0443d80 : 0xffffff800473345b mach_kernel : _vm_map_remove + 0xa3b
0xffffffa0d0443ed0 : 0xffffff8004732a93 mach_kernel : _vm_map_remove + 0x73
0xffffffa0d0443f00 : 0xffffff8004c1da43 mach_kernel : _munmap + 0xb3
0xffffffa0d0443f40 : 0xffffff8004d40dae mach_kernel : _unix_syscall64 + 0x2ce
0xffffffa0d0443fa0 : 0xffffff80046331f6 mach_kernel : _hndl_unix_scall64 + 0x16

Process name corresponding to current thread: Microsoft Teams Helper (Renderer
Boot args: keepsyms=1 debug=0x100 chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
20E241

Kernel version:
Darwin Kernel Version 20.4.0: Thu Apr 22 21:46:47 PDT 2021; root:xnu-7195.101.2~1/RELEASE_X86_64
Kernel UUID: 068F99A3-1DB3-31C0-87D5-09942F122BB6
KernelCache slide: 0x0000000004400000
KernelCache base:  0xffffff8004600000
Kernel slide:      0x0000000004410000
Kernel text base:  0xffffff8004610000
__HIB  text base: 0xffffff8004500000
System model name: iMac12,2 (Mac-7BA5B2D9E42DDD94)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 24478866024470
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x000016436e1d30d3
  Sleep   : 0x000013ddcc5bbc53 0x000000004189e2be 0x00000a1cc06cabf9
  Wake    : 0x000013dddc41c68a 0x00000000411ed62e 0x000013dddb33a1e0

 

[Ausdauersportler]

Borrowed a second gt710 from a friend to test with. On both the cMP3,1 and cMP5,1 the issue persists. So nothing wrong with my gt710. At the end of the BigSur boot process I get a black screen with a mouse pointer that reacts to mouse movement, but no Finder/Desktop. Abrupt movement of the mouse makes the pointer larger, as expected.

The only difference is that on the cMP5,1 I can see the boot picker and "white over black" progress bar whereas on the cMP3,1 I can see none of those things.

Both gt710's work fine with Mojave, therefore:

For the time being I tend to believe that BigSur has ended support for GK208(B) Kepler 2.0 core gpus.

You should open an issue on the OCLP Github page. Anyway this is only a user forum, development and debugging is triggered after opening an issue, only.

I had such symptoms once in a while back with micropatcher and some OC settings (mostly amfi_get_out_of_my_way, which enabled NightShift but interfered with some other settings).