- Joined
- Jun 3, 2020
- Messages
- 14
Hey everyone,
After updating to Monterey I am having some strange USB issues. I first noticed it with Bluetooth where the system report would recognise a Bluetooth controller (In both USB and Bluetooth) but would give a null address meaning Bluetooth isn't working at all. When this happens, the rest of the system works fine but after a while USB will entirely stop working and the computer needs a force restart. Following the restart Bluetooth suddenly works and USB has no issues. This seems to last a few restarts the eventually back to Bluetooth not being recognised and USB crashing after a while.
This has only started happening after the upgrade to Monterey. My USB map seems to be correct and the only way I can get Bluetooth to occasionally work (even though the card was native in Big Sur) is to use the bluetoolfixup kext.
Anyone got any ideas on what is causing this?
Cheers
After updating to Monterey I am having some strange USB issues. I first noticed it with Bluetooth where the system report would recognise a Bluetooth controller (In both USB and Bluetooth) but would give a null address meaning Bluetooth isn't working at all. When this happens, the rest of the system works fine but after a while USB will entirely stop working and the computer needs a force restart. Following the restart Bluetooth suddenly works and USB has no issues. This seems to last a few restarts the eventually back to Bluetooth not being recognised and USB crashing after a while.
This has only started happening after the upgrade to Monterey. My USB map seems to be correct and the only way I can get Bluetooth to occasionally work (even though the card was native in Big Sur) is to use the bluetoolfixup kext.
Anyone got any ideas on what is causing this?
Cheers