Update 15: OpenCore 0.8.4, macOS 12.6, Logitech BRIO Webcam, and Partial Fix for RGB
OpenCore 0.8.4
I followed the OpenCore Post-Install guide for
Updating OpenCore to update OpenCore from 0.8.3 to
0.8.4.
- I replaced these OpenCore files with the latest versions:
- BOOT/BOOTx64.efi
- OC/Drivers/OpenCanopy.efi
- OC/Drivers/OpenRuntime.efi
- OC/Drivers/ResetNvramEntry.efi
- OC/OpenCore.efi
- OC/Tools/OpenShell.efi
- I added a new property to config.plist that was identified in OCConfigCompare.
- Under
Misc -> Tools
, add LoadEarly
to each tool (in my case, OpenShell is the only tool) and set each to False
:
FullNvramAccess | Boolean | False
- I updated kexts to the latest versions:
- AppleALC.kext: 1.7.4 -> 1.7.5
My latest EFI folder is attached for reference.
macOS 12.6
I updated macOS from 12.5.1 to 12.6 using System Preferences without any issues.
Logitech BRIO Webcam for FaceTime and Windows Hello
I recently got a Logitech BRIO Webcam (
Amazon |
Newegg), which I primarily use for Zoom on my work computer. However, I've tested it, and it works with FaceTime and Windows Hello.
FaceTime
If you've enabled DRM, FaceTime won't work. The other person's video will be replaced with a black or gray screen. To fix this, you must disable DRM:
- Delete the shikigva patch from your config.plist:
- If you added the patch to your DeviceProperties:
- In config.plist, under
DeviceProperties -> Add -> [Your GPU DevicePath]
- Delete:
shikigva | Number | 80
- If you added the patch to your boot arguments:
- In config.plist, under
NVRAM -> Add -> 7C436110-AB2A-4BBB-A880-FE41995C9F82
- In
boot-args
, delete shikigva=80
- Reboot and run the following preference override command in Terminal to disable the AMD DRM decoder for streaming services:
Bash:
defaults write com.apple.AppleGVA gvaForceAMDKE -boolean false
If you're only using the webcam for other video call apps like Zoom, Google Meet, or Microsoft Teams, then you don't need to disable DRM. I don’t plan to use FaceTime on my computer, so I will keep the shikigva patch in my config.plist.
Windows Hello
The BRIO Webcam supports Windows Hello, which is
easy to set up.
Before setting up Windows Hello, it is recommended that you enable TPM in BIOS to secure your Windows Hello PIN:
- Boot up the computer.
- Press
Delete
or F2
to enter BIOS.
- Press
F7
or click Advanced in the bottom right corner to enter Advanced Mode.
- Go to Advanced > PCH-FW Configuration.
- Set PTT to Enabled.
- Save Changes and Reset.
- Go to the Exit menu.
- Select Save Changes & Reset and press
Enter
.
A quick note about the Windows Hello PIN: Having never used Windows Hello before, I assumed that if the facial recognition failed or my camera wasn't connected, the fallback would be my local user account password. However, this isn't the case. When you set up Windows Hello, your local user password is actually removed. Instead, you have two fallbacks: your Microsoft account password and a PIN you must create. I initially assumed the PIN would be restricted to numbers and only allow a few digits, which wouldn't be very secure. However, you can actually use letters and symbols for your PIN, and it doesn't have to be short. So I was actually able to use my old local account password as my PIN.
Partial Fix for RGB
I’ve never cared much about RGB lights, and I didn’t even realize my motherboard had RGB lights until after I got it. However, I have wanted to change the default rainbow colors to solid white. I briefly had this working using the Asus Armoury Crate app, but at some point, the RGB lights reverted back to rainbow colors and my motherboard stopped showing up as an RGB device in Armoury Crate. This is apparently a common problem with Armoury Crate. I tried several fixes I found online but never got the app working again.
I tried a few other RGB apps before finding one that partially worked. I tried iCUE, but it’s dependent on Armoury Crate, so it didn’t detect my motherboard either. I had high hopes for OpenRGB because it has a macOS app. However, it only detected my motherboard in Windows, not macOS. Also, when waking my computer from sleep, the RGB lights reverted to rainbow colors, and OpenRGB wouldn’t automatically change them back to white.
Finally, I tried
SignalRGB, which partially fixed this issue. It allowed me to set the RGB lights to white. When I wake the computer from sleep, the RGB does revert to rainbow colors, but after a few seconds, SignalRGB will switch it back to white, as long as it’s running in the background. The downside is that it’s only available for Windows, so when I wake my computer from sleep in macOS, the RGB reverts to rainbow colors until I boot Windows again.