I just flashed the TitanRidgeMacOSFirmware.bin (even though I didn't have kennel panics with NVM23-Elias64Fr.bin but hey what can I say, I love tinkering).** GC-Titan Ridge Owners **
Please read if you have flashed your Thunderbolt firmware chip (blue dot chip)
In Big Sur 11.3 onwards, the firmware GC-TITAN-RIDGE-NVM23-Elias64Fr.bin is not stable, and macOS Big Sur will crash. You are advised to flash the DSM firmware called TitanRidgeMacOSFirmware.bin. This firmware has been posted to the Repository. Although this has been tested on GC-Titan Ridge V1.0, it may well apply to V2.0 of the card as well.
Credit: @Matic
Credit for Firmware: DSM2 (MacRumors user name)
View attachment 517894
Please see this post:Hi everyone, has anyone had an issue with updating to 11.3.1 where the update just doesn't seem to 'take'? By that I mean the process seems to have worked, couple of reboots, usual Apple logo with '8 minutes remaining', reboot again... but OS seems to think I'm still on 11.2.4? I've been keeping pretty up to date with OC and Big Sur in recent months and never seen this. I've tried to reset NVRAM incase that's got anything to do with it. I don't have the picker displaying I just let it auto boot and it always seems to have worked in the past. Hoping there's something obvious I might have missed!? I'm on OC 0.6.9 by the way. Cheers!
Thanks for the speedy response Casey, forgive my ignorance, am I changing this 'AAAAAA==' entry to '67000000'?Please see this post:
They temporarily set csr-active-config to 67000000 to allow macOS to update.![]()
Gigabyte Z490 Vision D (Thunderbolt 3) + i5-10400 + AMD RX 580
Oh I think I found your HackinDROM App guide @CaseySJ , but I see this notice: Contraindication (Reason NOT to Use this App): If you have a multi-boot system (macOS, Windows, Linux, etc.) and the boot loaders for those other operating systems (Windows, Linux) are located in the same EFI folder...www.tonymacx86.com
Please try this and let us know if it helps.
This problem seems to affect a very limited number of users. You may want to just keep it atFigured it out, remembered to use ProperTree instead of TextEdit (sorry!). Changing to 67000000 DID work, system now updated.
Changed it back to '00000000'. Is this now likely to be required for each update? Weird that I've never had to do it before!
67000000
and see what happens...Also, now getting glitchy YouTube audio in Safari which is a bummer... any suggested fixes for that?
IPG prevent sleep while it is running. You need to quit it to allow sleep. UserEventAgent also sometimes gets stuck and prevents sleep. Running the terminal command purges running instances that are preventing sleep. I haven't determined what causes UAE to to stick but I believe its related to USB misconfiguration.Sweet! ok so just to clarify for myself...
Do I need to quit IPG every time I want to put it to sleep or will the code you posted be a full fix needing to only be run once and from there on I can keep IPG running every time in the background before sleep?
Also incase it has negative effects, what is the code to reverse what the line of code does that you posted?
Hi @CaseySJ : The "default"OC config you've been uploading (thank you) has a default setting of config<nvram<delete<csr-active-config. Should we start adjusting the value as needed and move csr-active-config from the nvram<delete to nvram<add ?Please see this post:
They temporarily set csr-active-config to 67000000 to allow macOS to update.![]()
Gigabyte Z490 Vision D (Thunderbolt 3) + i5-10400 + AMD RX 580
Oh I think I found your HackinDROM App guide @CaseySJ , but I see this notice: Contraindication (Reason NOT to Use this App): If you have a multi-boot system (macOS, Windows, Linux, etc.) and the boot loaders for those other operating systems (Windows, Linux) are located in the same EFI folder...www.tonymacx86.com
Please try this and let us know if it helps.