Long story short: I was deepcleaning my Microsoft Natural Keyboard Pro (a board I've been typing on since 1999!) but some water must've remained in a key and (momentarily) made the board freakout. Sadly this happened on the OpenCore selection menu, where it cleaned NVRAM. No harm no foul I thought, but my Bluetooth has been dead ever since. It's a CRS8510 A10 dongle that worked fine, up an including Ventura.
I came across an old (2013!) thread that suggested to install particular Windows software and make sure that the dongle is booting in the right setting. (Initial Bootmode set to 0000) Did that in Windows. Didn't have any effect sadly. Kexts I load (and order) unaltered are BrcmBluetoothInjector.kext and BlueToolFixup.kext.
I can live without Bluetooth (use a Trackpad every now and then) but I find it annoying that a simple NVRAM trigger could have this effect. Does anyone have a clue what I could try? I read something about adding NVRAM entries in config.plist to reanimate Bluetooth but that seems to be for Intel dongles (?)
If there's few simple steps I could try lemme know!
I came across an old (2013!) thread that suggested to install particular Windows software and make sure that the dongle is booting in the right setting. (Initial Bootmode set to 0000) Did that in Windows. Didn't have any effect sadly. Kexts I load (and order) unaltered are BrcmBluetoothInjector.kext and BlueToolFixup.kext.
I can live without Bluetooth (use a Trackpad every now and then) but I find it annoying that a simple NVRAM trigger could have this effect. Does anyone have a clue what I could try? I read something about adding NVRAM entries in config.plist to reanimate Bluetooth but that seems to be for Intel dongles (?)
If there's few simple steps I could try lemme know!
