Skip to content

Fix formatting in undoing-early-speaker-hacks #186

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix formatting in undoing-early-speaker-hacks #186

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 8 additions & 6 deletions docs/sw/undoing-early-speaker-hacks.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
title: Undoing Early Speaker Hacks
---

### Introduction
# Introduction
You are probably here because you tried to enable your speakers early, and a change in config
between when you did this and the public release of speaker support broke something. You were
warned.
Expand All @@ -11,8 +11,9 @@ Below are some fixes for common early adopter hacks. Please try _all_ of them be
Your bug will be ignored if we find that you have failed to rectify any of the issues
below.

### The Pro Audio profile is/was enabled for the internal speakers / headphones
# The Pro Audio profile is/was enabled for the internal speakers / headphones
This one can happen in one of three ways:

* You have changed the profile while headphones were plugged in
* You have been using a very, very, _very_ old version of `asahi-audio`
* You have circumvented Wireplumber node permissions to experiment with device profiles
Expand All @@ -24,11 +25,12 @@ In doubt delete WirePlumber's sstate directory (`rm -rf ~/.local/state/wireplumb
and reboot.

The fix in the two other cases is the the same:

1. `rm -rf ~/.local/state/wireplumber/`
2. Reinstall `asahi-audio`, Pipewire _and_ Wireplumber
3. Reboot your machine

### You have files in /etc/ from a prerelease version of asahi-audio
# You have files in /etc/ from a prerelease version of asahi-audio
Very old versions of `asahi-audio` stored their configuration inside `/etc/pipewire/` and
`/etc/wireplumber/`. There should be nothing Asahi related in _either_ of these directories
or any of their subdirectories. To fix this:
Expand All @@ -41,7 +43,7 @@ rm -rf /etc/pipewire/pipewire.conf.d/*asahi*
Once you have done this, reinstall `asahi-audio`, Pipewire _and_ Wireplumber then reboot
your system.

### You have files in /usr/share/ from a prerelease version of asahi-audio
# You have files in /usr/share/ from a prerelease version of asahi-audio
Prerelease versions of `asahi-audio` had files in `/usr/share/` that do not match the ones
that shipped with 1.0. These files can conflict with the release versions, causing issues.
You must manually remove all `asahi-audio` files:
Expand All @@ -55,11 +57,11 @@ rm -rf /usr/share/pipewire/pipewire.conf.d/*asahi*
Once you have done this, reinstall `asahi-audio`, Pipewire _and_ Wireplumber then reboot
your system.

### You have tried to manually circumvent our kernel-level safety controls
# You have tried to manually circumvent our kernel-level safety controls
Remove `snd_soc_macaudio.please_blow_up_my_speakers` from wherever you added it. This could be
the default kernel command line, `modprobe.d`, or somewhere else. Reboot when this is done.

### Required speaker codec settings are not being applied
# Required speaker codec settings are not being applied
This can happen if you are on an old kernel, or you have manually set `snd_soc_tas2764.apple_quirks`
to some nonstandard value. As above, remove any reference to this module parameter, update your kernel,
then reboot.