Microphone and Headphone Jack support!

[MilkyDeveloper]

Hello! If you've been linked here, you're one of the candidates selected for Headphone Jack and Microphone validation.

Only proceed if your speakers (internal audio) are working in the first place.

Thanks to u/nsx2brz's post here, I now know the correct AlsaMixer settings to enable a headphone jack.

I was previously unable to test this because I don't have a SOF device of my own, and my personal device's speakers were blown.

I've just added a script called sof-setup-aux that uses nsx2brz's method intended to be ran after running sof-setup-audio and rebooting, but it uses amixer rather than the preferred method of using a UCM. Below, I'll be debugging the correct method, using a UCM.

Instructions:

1. Tell me what Chromebook board you have (you can find this out on the developer mode boot screen or by looking here)
2. I'll give you a .zip archive that you should extract to /usr/share/alsa/ucm2/
   • The directory structure should look like: /usr/share/alsa/ucm2/A_FILE_OR_FOLDER_IN_THE_ZIP
   • Make sure to install unzip by running sudo apt install unzip -y
   • The command: unzip file.zip -d /usr/share/alsa/ucm2

[jthompson05]

@MilkyDeveloper Hi. I just came back to stock firmware from Mr. Chromeboxes UEFI firmware. Having a working mic and headphone jack under Linux sounds really exciting, so I wanted to try this out. As you may already know, I have a BLOOGLET Chromebook (HP Chromebook 14a). On the documentation, it says audio is supported for my device, but when I ran setup-audio then sof-setup-audio and rebooted, my sound icon disappeared. I created an Ubuntu 22.04 Breath USB with the KDE Plasma desktop. I wonder if that is the problem?

[jthompson05]

I got /lib/firmware/intel/sof: symbolic link to sof-v2.1.1. Also really awesome that Breath will work with UEFI too!

[MilkyDeveloper]

@dominicsherry1 has the same device and reported audio to work. Maybe rebuild the USB and don't run setup-audio?

[Denisuu]

I'm also back on Breath (Ubuntu XFCE sadly because the Arch ISO won't build) and I can confirm sound works here too. I'd be happy to test the aux .zip

[MilkyDeveloper]

Try running sof-setup-aux and test your headphone jack and mic. If that works, I'll build a UCM :D.

[Denisuu]

The script isn't found when I run sof-setup-aux so I copied it from Github. sof-setup-aux

AUX isn't working though, also speakers are not playing anymore. There's no sound at all now.

How do I change output device? On Manjaro (UEFI) I would do it through Pulseaudio but it isn't working on Breath. The terminal command amixer also doesn't work.

On Manjaro I mapped the vol up / vol down buttons to amixer -D pulse sset Master 3%-. I tried amixer set Master 3%- but that didn't work (even before running sof-setup-audio and speakers were working)

[dominicsherry1]

Hey @MilkyDeveloper, I'm happy to test out the audio jack support on a HP Chromebook 14a (BLOOGLET).
FYI, the microphone appears to be already working straight away after running sof-setup-audio and rebooting.

[MilkyDeveloper]

Attach the file created by sudo alsa-info. We might not even need a .zip file that contains the UCM :D.

The UCM used seems very simple. On my chromebook that uses a legacy audio system called Intel SST, the UCM is 500+ LoC, whereas this one is only 80 LoC.

You might have some dice by running:

amixer cset name='Headphone Jack Switch' on
amixer cset name='Headset Mic Switch' on

If this fails, you might not have alsa-utils (or alsa-* in more recent Debian versions) installed.

[jthompson05]

@MilkyDeveloper Do you think your UCM solution would work with linux on Mr. Chromebox UEFI? I am on UEFI firmware now and I tried the solution from reddit. The mic and headphone jack work, but the volume scaling issue is still present. I can fix the scaling issue by enabling Pro Audio in pavucontrol. In order for pro audio to work, pipewire is required. However, when Pro Audio is enabled, the headphone jack isn't recognized anymore. Any help?

[dominicsherry1]

Hey. Here's the alsa-info. I'm afraid I don't know what any of that stuff about UCM means :-)
I don't have a microphone pin on my headphones, but running amixer cset name='Headphone Jack Switch' on definitely did something. I do have alsa-utils and bluez-alsa-utils installed.
After a reboot though, there isn't an option to switch over to headphones in the control center or in alsamixer, and audio does not automatically switch over to the headphones.

[MilkyDeveloper]

Don’t reboot after running the amixer command. So, does sound come out of the headphone jack? Test this by running:

speaker-test -Dsofglkda7219max:Headset

[dominicsherry1]

There's no sound coming from the headphone jack. Before doing the speaker test I get white noise from the speakers. After running the amixer command:

$ amixer cset name='Headphone Jack Switch' on

numid=66,iface=MIXER,name='Headphone Jack Switch' ; type=BOOLEAN,access=rw------,values=1 : values=on

and then running the speaker test:

$ speaker-test -Dsofglkda7219max:Headset

speaker-test 1.2.6 Playback device is sofglkda7219max:Headset Stream parameters are 48000Hz, S16_LE, 1 channels Using 16 octaves of pink noise ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM sofglkda7219max:Headset Playback open error: -2,No such file or directory

No sound comes out and there's the above error message.

[RodBarnes]

I assume this is not available for Apollo Lake since we have to use the firmware change via apl-sof-setup-audio and rely on PulseAudio?

[MilkyDeveloper]

Maybe try running sof-setup-aux, this should change the alsamixer settings to something we can use.

[RodBarnes]

I built a fresh image and did the following:
apl-sof-setup-audio
reboot
sudo sof-setup-aux
reboot
I still have audio but no input device appears under settings. I was expecting that the internal microphone would appear there by default.

[RodBarnes]

Also, I had to clear the carriage returns from sof-setup-aux; it was saved in Windows EOL rather than Unix EOL. I didn't simply PR this since you may have to make other changes to the script.

[MilkyDeveloper]

The most important issue atm is the headphone jack. Tell me the output of the file created by sudo alsa-info; this should pin down the devices listed and help me tell you which command to get audio running through your headphones.

[RodBarnes]

Output of sudo alsa-info is here.