Open cisoun opened 2 months ago
Some initial points:
libgnome-volume-control
is known to be broken and exposes the hardware device even though we don't want it tospeakersafetyd
manually requires certain switches to be passed to it. See its systemd unit file for an example.What distro are you using? Please post the output of asahi-diagnose
.
Hi,
Thanks for the clarification.
I'm currently using Fedora Linux Asahi Remix 40 (Forty). Here's the output of ̀asahi-diagnose
:
cyriaque@macbook-fedora:~$ asahi-diagnose
grep: /home/cyriaque/.local/state/wireplumber/restore-stream: No such file or directory
Collecting system diagnostic information...
Saved diagnostic information to /home/cyriaque/asahi-diagnose-20240512-161604.txt
Here's the diagnosis as well: asahi-diagnose-20240512-161604.txt
Thanks!
Speakersafetyd is launching at boot, so you shouldn't try to start it manually. Again, please do not try to change the device's profile. You need to keep it at default. Can you try to delete ~/.local/state/wireplumber/
, reboot your machine, then just select MacBook Pro J416 Speakers
in GNOME's volume mixer? This should at least get us into a known-good state.
Done. For now, I'll just use the headphones instead since the J416 is rather unstable on GNOME and the convolver doesn't work. Let me know if you need further tests/feedbacks.
Hello,
I'm running a Macbook M2 Pro from 2023 with J416 speakers, on GNOME. I've noticed some issues with this hardware:
I guess the J416 support isn't ready yet. Or did I miss something? Let me know how can I help otherwise.
Thanks a lot for your work!
EDIT: I've found
/usr/share/speakersafetyd/appl/j416.conf
but for an unknown reason, speakersafetyd looks for the profile from/usr/local
, I'll investigate why...