So the bug is not specifically with asahi-btsync, but rather generically with reading that variable from NVRAM. We could even reassign it to librust-apple-nvram-dev since that's where the reading happens, but let's not rush things (also, the variable specifically is a bluetooth variable). Does `sudo asahi-nvram read | grep -i bluetooth` return anything? Do you have any paired bluetooth device on macOS (wondering if the variable is empty simply because there are no paired devices)?
For the record, I could not reproduce on a 14" M1 Pro MacBookPro (with a caveat, namely I booted Debian from USB there, using Fedora's m1n1+u-boot initial boot chain since my MacBookPro runs Fedora). Both on the Mini and on the MacBookPro I had previously paired bluetooth devices. Still, there's not much we can do other than report the bug upstream. Do you mind sharing the "Firmware versions" section of the output of `asahi-diagnose` so we know what to say? P.S.: I remembered your machine from previous conversations :-) And sorry for the many questions, I'm trying to get a better picture of the issue before bothering upstream.
