chromebook-linux-audio icon indicating copy to clipboard operation
chromebook-linux-audio copied to clipboard

Speakers not working on Acer Chromebook 317

Open defitzwa opened this issue 2 years ago • 31 comments

I am using Fedora 38 (linux kernel 6.3.8-200.fc38.x86_64) with chromebook-linux-audio on an Acer Chromebook 317.

It is my understanding that this is a Jasperlake Chromebook with a Magpie board, so when searching for a solution, I came across the following thread from a familiar user: https://github.com/thesofproject/sof/issues/7162

If I read it correctly, it sounds like there was a resolution in the end. But maybe not yet rolled out? Are there any instructions for how I can get this working on my machine?

defitzwa avatar Jul 02 '23 01:07 defitzwa

My script will install the updated topologies for you, so it should just work.

WeirdTreeThing avatar Jul 02 '23 11:07 WeirdTreeThing

I ran the script before posting (apologies for not stating that clearly). The audio through the speakers is not working, but the audio through the headset is working after running the script. Before running the script, the headset audio was not working either.

It is my understanding that the script installed some or all of the files shown under /lib/firmware/intel/sof and /lib/firmware/intel/sof-tplg/

In case it is helpful, I have attached the outputs of ls -al /lib/firmware/intel/sof lib_firmware_intel_sof.txt

and ls -al /lib/firmware/intel/sof-tplg/ lib_firmware_intel_sof-tplg.txt

Is there anything else I can check that would help in troubleshooting the issue?

defitzwa avatar Jul 02 '23 17:07 defitzwa

Send the output of aplay -l.

WeirdTreeThing avatar Jul 02 '23 18:07 WeirdTreeThing

Please see attached: aplay -l.txt

defitzwa avatar Jul 02 '23 22:07 defitzwa

Run this and upload the file it creates audio-debug.sh.txt

WeirdTreeThing avatar Jul 02 '23 23:07 WeirdTreeThing

Here is the log file:

audio-debug.log

defitzwa avatar Jul 02 '23 23:07 defitzwa

So topology and ucm both look fine. Send your dmesg log with sudo dmesg > dmesg.log.

WeirdTreeThing avatar Jul 02 '23 23:07 WeirdTreeThing

There do appear to be some errors in this one:

dmesg.log

defitzwa avatar Jul 02 '23 23:07 defitzwa

Those errors are normal. Try running aplay -d plughw:0,0 /usr/share/sounds/alsa/Front_Center.wav

WeirdTreeThing avatar Jul 02 '23 23:07 WeirdTreeThing

Konsole didn't like the argument -d:

aplay -d plughw:0,0 /usr/share/sounds/alsa/Front_Center.wav aplay: main:659: invalid duration argument 'plughw:0,0'

It was happy with an uppercase D though: aplay -D plughw:0,0 /usr/share/sounds/alsa/Front_Center.wav Playing WAVE '/usr/share/sounds/alsa/Front_Center.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono

I'm guessing this is meant to play sound. Nothing came out of the onboard speakers though.

defitzwa avatar Jul 03 '23 00:07 defitzwa

Oh sorry I wrote the command wrong, but yeah the sound should be played out of the speakers. It looks like a kernel/firmware issue though. Anything new in dmesg after running that command?

WeirdTreeThing avatar Jul 03 '23 00:07 WeirdTreeThing

Nope, only addition is from where I tried and failed to run a diff command

defitzwa avatar Jul 03 '23 00:07 defitzwa

Apologies. I was not reading the output correctly. Yes, there are a couple new entries in dmesg that most likely do not have anything to do with me using the wrong argument in a diff.

[ 6990.115453] perf: interrupt took too long (2510 > 2500), lowering kernel.perf_event_max_sample_rate to 79000 [ 7439.327688] PDLOG 2023/07/03 00:11:35.722 P1 Disconnected

defitzwa avatar Jul 03 '23 00:07 defitzwa

Those aren't related to audio

WeirdTreeThing avatar Jul 03 '23 01:07 WeirdTreeThing

Yes, I came to that conclusion after googling them. Looks like it is just logging CPU scaling and then logging when I disconnect from wall power. Any other things I can try or look at? You mentioned the kernel/firmware. I would prefer to stick with Fedora but I suppose I could try a different distribution in the name of science.

EDIT: Also, regarding firmware specifically, what firmware interfaces did you use when testing Jasperlake/Magpie? I am currently using the UEFI full ROM from MrChromeBox, but I see that he also has a Legacy Boot option that could be used. Not sure if that would matter.

defitzwa avatar Jul 03 '23 02:07 defitzwa

Make sure your system is fully up-to-date. Run the audio script again and see if it still doesn't work.

WeirdTreeThing avatar Aug 16 '23 02:08 WeirdTreeThing

Sorry for the slow response. I was traveling last week and didn't want to run the update through my phone hotspot.

System has been updated. Re-pulled and re-ran the script. Does not appear to have changed behavior. Offboard audio works but onboard does not.

defitzwa avatar Aug 22 '23 02:08 defitzwa

Ok so most likely a UCM issue. JSL hasn't been the best supported for this for a while. Run cat /sys/class/dmi/id/product_sku and send the output.

WeirdTreeThing avatar Aug 22 '23 02:08 WeirdTreeThing

The output was:

sku720896

defitzwa avatar Aug 23 '23 00:08 defitzwa

I just updated the UCM, run the script and try again.

WeirdTreeThing avatar Aug 23 '23 02:08 WeirdTreeThing

I re-pulled https://github.com/WeirdTreeThing/chromebook-linux-audio and reran the setup-audio script, but did not see a change in audio behavior.

I reran cat /sys/class/dmi/id/product_sku. the ouput is still sku720896

I see there is another sizable Fedora update that became available today. I will try installing that and rerunning the script again.

defitzwa avatar Aug 24 '23 01:08 defitzwa

The SKU wont change. Run this script and send the output of it as an attachment.

WeirdTreeThing avatar Aug 24 '23 02:08 WeirdTreeThing

Output is attached audio-debug.log

defitzwa avatar Aug 24 '23 02:08 defitzwa

Can you kill your audio server (systemctl --user stop pipewire.socket && systemctl --user stop pipewire-pulse.socket) and try again?

WeirdTreeThing avatar Aug 24 '23 02:08 WeirdTreeThing

Here is the output of the audio-debug script after killing the audio server: audio-debug.log

defitzwa avatar Aug 24 '23 03:08 defitzwa

That all looks normal, not too sure why your speakers aren't working then. I'm gonna have someone else with the same device test their speakers, I know it worked for them before so a recent change might have broken it.

WeirdTreeThing avatar Aug 24 '23 03:08 WeirdTreeThing

Sounds like a good plan, thank you for the help.

defitzwa avatar Aug 24 '23 03:08 defitzwa

Forgot about this issue. I made some improvements to the magpie ucm a few weeks ago, try again.

WeirdTreeThing avatar Oct 02 '23 15:10 WeirdTreeThing

I re-cloned the repository and re-ran the script, then rebooted. The onboard audio is still stubbornly silent. Did the other person with the same hardware respond?

defitzwa avatar Oct 08 '23 23:10 defitzwa

Unfortunately, that person had some issues with their hardware.

WeirdTreeThing avatar Oct 09 '23 00:10 WeirdTreeThing