- Joined
- Jan 25, 2020
- Messages
- 29
- Motherboard
- Gigabyte Z390 Designare
- CPU
- i9-9900K
- Graphics
- RX 6900 XT
Almost everything is working beautifully for me with full system stability. Including native NVRAM! This is awesome!
I do experience a few issues:
1. I dual booth with Windows and use Clover. I use the Magic Mouse 2 and the Magic Keyboard, both Bluetooth based. Every time I switch to Windows, I have to go through a lot of configuration to get scrolling working with Apple's AppleWirelessMouse driver package extracted from the BootCamp support package for the iMac19,1. Sometimes it just won't work. Even Magic Utilities doesn't work. But then, usually after installing, uninstalling, and replacing drivers here and there for some time, it will eventually work and persist after reboot, but only until I boot into mac OS and then go back to Windows. This is really strange, as the two operating systems are completely separated. Could it be because Mac OS uses the PCI x1 Bluetooth card and Windows uses the on-board Intel chip and somehow the mouse doesn't like being paired to another Bluetooth chip? I've read something that felt related over at the Arch linux wiki:
However, since I'm using the on-board Bluetooth Intel chip on Windows and use a BCM94360CS2 chip on Windows, the overwriting stuff might not apply?
2. Universal Clipboard and Airdrop doesn't really work for large file transfers. Any ideas?
I do experience a few issues:
1. I dual booth with Windows and use Clover. I use the Magic Mouse 2 and the Magic Keyboard, both Bluetooth based. Every time I switch to Windows, I have to go through a lot of configuration to get scrolling working with Apple's AppleWirelessMouse driver package extracted from the BootCamp support package for the iMac19,1. Sometimes it just won't work. Even Magic Utilities doesn't work. But then, usually after installing, uninstalling, and replacing drivers here and there for some time, it will eventually work and persist after reboot, but only until I boot into mac OS and then go back to Windows. This is really strange, as the two operating systems are completely separated. Could it be because Mac OS uses the PCI x1 Bluetooth card and Windows uses the on-board Intel chip and somehow the mouse doesn't like being paired to another Bluetooth chip? I've read something that felt related over at the Arch linux wiki:
When dual booting Windows and Linux, you may find yourself having to repair your Bluetooth mouse again and again. This will happen every time you switch OS, because when you pair your device, your Bluetooth service generates a unique set of pairing keys.
First, your computer stores the Bluetooth device's mac address and pairing key. Second, your Bluetooth device stores your computer's mac address and the matching key. This usually works fine, but the mac address for your Bluetooth port will be the same on both Linux and Windows (it is set on the hardware level). However, when you re-pair the device in Windows or Linux, it generates a new key. That key overwrites the previously stored key on the Bluetooth device. Windows overwrites the Linux key and vice versa.
However, since I'm using the on-board Bluetooth Intel chip on Windows and use a BCM94360CS2 chip on Windows, the overwriting stuff might not apply?
2. Universal Clipboard and Airdrop doesn't really work for large file transfers. Any ideas?
Last edited: