Contribute
Register

Gigabyte Z390 M Gaming build with working NVRAM

Hi,
Ever since I updated above Monterey Beta 6 Bluetooth malfunctions after wakeup from sleep. This does not happen on Big Sur. Using usb keyboard and mouse, if I just open Blutooth Preferences BT then functions and my magic mouse reconnects as well as the BT keyboard. It wakes up from the BT Keyboard or mouse but then goes dead. I am using the 0.74 efi from this tread. Otherwise everything works fine.. Any ideas?

I have no idea. I have not tried Monterey at all. I'm waiting for the final to be released.
 
Everything is working so far very good. I'm using the news OpenCore EFI image. More or less untouched.

But my bluetooth mouse and keyboard are not working in BIOS, OpenCore-bootscreen or in the FileVault password screen. Everything is working fine as soon as the OS has booted.

I'm using an original BRCM20702 bluetooth controller. Do I have to enable something in the BIOS?
 
Everything is working so far very good. I'm using the news OpenCore EFI image. More or less untouched.

But my bluetooth mouse and keyboard are not working in BIOS, OpenCore-bootscreen or in the FileVault password screen. Everything is working fine as soon as the OS has booted.

I'm using an original BRCM20702 bluetooth controller. Do I have to enable something in the BIOS?

Once they have been paired in macOS, there shouldn't be anything else you need to do.
 
Everything is working so far very good. I'm using the news OpenCore EFI image. More or less untouched.

But my bluetooth mouse and keyboard are not working in BIOS, OpenCore-bootscreen or in the FileVault password screen. Everything is working fine as soon as the OS has booted.

I'm using an original BRCM20702 bluetooth controller. Do I have to enable something in the BIOS?
ps2 port compatibility under USB in BIOS. Without it set to enabled, my keyboard will not work in BIOS.
 
Regarding TitanRidge and Thunderbolt-Displays
- Requires a second monitor or ghost plug to boot into Mac OS. One detail with the ghost plug is that it is not HDCP compliant, so once the machine boots up, if you want to watch content that has DRM(Disney+, Amazon, etc), you need to unplug it. Once the Apple Display turns on, it isn't needed until the next time you boot up from a shutdown. I have the monitors set to mirror, so there isn't an issue with the cursor going off the screen or anything like that.
I know, this topic is some older, but I got this problem some weeks ago while I played with the Monterey Beta, because it's not existent on Catalina. After many OpenCore configurations, SSDT experiments and some debug sessions, I read somewhere, that nearly the same problem can exist with Displayport monitors. The solution was to enable CSM in BIOS... and YES! this worked here too. My conclusion is, that Apple changed something between the macOS versions 11.2 and 11.6, because I remember that all worked without "enabled CSM" for me until BigSur freezes, because of the TitanRidge-Samsung-NVMe-Problem. So I hadn't used Big Sur and my working system is Catalina - also today.
Since I have enabled CSM in BIOS, the Apple Thunderbolt-Displays (I have 2 chained on a RX580) work from the second boot part, where macOS activating or switching something with the graphics mode.
 
Regarding TitanRidge and Thunderbolt-Displays

I know, this topic is some older, but I got this problem some weeks ago while I played with the Monterey Beta, because it's not existent on Catalina. After many OpenCore configurations, SSDT experiments and some debug sessions, I read somewhere, that nearly the same problem can exist with Displayport monitors. The solution was to enable CSM in BIOS... and YES! this worked here too. My conclusion is, that Apple changed something between the macOS versions 11.2 and 11.6, because I remember that all worked without "enabled CSM" for me until BigSur freezes, because of the TitanRidge-Samsung-NVMe-Problem. So I hadn't used Big Sur and my working system is Catalina - also today.
Since I have enabled CSM in BIOS, the Apple Thunderbolt-Displays (I have 2 chained on a RX580) work from the second boot part, where macOS activating or switching something with the graphics mode.

Interesting. So far I have been able to install all the Monterey Betas, needs open core 0.7.4 for the more recent ones. Big Sur seems to behave differently. Since Monterey is almost here, I am going to skip Big Sur. If I have the issue in the future though, I'll remember trying CSM.
 
Can't find this. I think you have a different motherboard?
You might have a different BIOS version. They sometimes change around the menu options between versions.

So enabling the PS/2 option will allow a Bluetooth keyboard to be recognized before the OS boots up? That's not very intuitive! :D

On my mobo/BIOS (Z390 Gaming X, f9g beta), I don't have that option either. My workaround is to keep a second USB keyboard/mouse plugged in whenever I have to muck around in the BIOS.
 
Any thoughts on how to debug OpenCanopy not working?

While on OC 0.6.9, I stupidly upgraded to Big Sur before prepping my EFI; I eventually got it working by updating directly to 0.7.4 but now the GUI isn't working on boot :(

I've re-downloaded the 0.7.4 release and diffed the related files (OpenCanopy.efi, Resources, OpenCanopy.efi) and I'm sure I have the right versions. Config attached =D
 

Attachments

  • config.plist
    27.8 KB · Views: 46
Any thoughts on how to debug OpenCanopy not working?

While on OC 0.6.9, I stupidly upgraded to Big Sur before prepping my EFI; I eventually got it working by updating directly to 0.7.4 but now the GUI isn't working on boot :(

I've re-downloaded the 0.7.4 release and diffed the related files (OpenCanopy.efi, Resources, OpenCanopy.efi) and I'm sure I have the right versions. Config attached =D

Do you see any text on the screen before the boot picker shows?
 
Back
Top