Hi all,
ok this is the actual state for me (as NoisyCoil already found out:
macbook pro m1pro 14'')
asahi btsync:
thread 'main' panicked at src/main.rs:53:17:
called `Result::unwrap()` on an `Err` value: VariableNotFound
note: run with `RUST_BACKTRACE=1` environment variable to display a
backtrace
asahi-nvram read system:BluetoothUHEDevices
VariableNotFound
but asahi-nvram has a bunch of variables
I am still running my own u-boot-asahi - actual 2024.07-1+cy8aer1
https://git.g3la.de/repos/-/packages/debian/u-boot-asahi/2024.07-1+cy8aer1
actual builder:
https://git.g3la.de/repos/m1-debian/src/branch/baer/m1n1_uboot_kernel.sh
Am 01.09.24 um 20:21 schrieb NoisyCoil:
Package: asahi-btsync
Followup-For: Bug #1071216
X-Debbugs-Cc: noisyc...@tutanota.com, cybae...@web.de
Hi all,
The reported bug seems to point to a missing variable in NVRAM, which is a bit
weird. I cannot reproduce it on my machine (M1 Mac Mini).
cy8aer, do you confirm the bug is still there and, if yes, what machine (was it
a 14" M1 Pro MacBook Pro?) and version of u-boot-asahi (origin, i.e. debian or
self-built, if self-built from what sources, and what version) you are using?
Also, using asahi-nvram from the asahi-nvram package, what does
`sudo asahi-nvram read system:BluetoothUHEDevices` return on stdout? Does
`sudo asahi-nvram read` return anything at all?
I feel the answers to these questions might be relevant to better understand
the issue before involving upstream.
