breath icon indicating copy to clipboard operation
breath copied to clipboard

Acer Spin 713-2W Audio disappearing on restart

Open 1Guardian opened this issue 3 years ago • 11 comments

Hello, I installed Ubuntu 22.04 with breath on an Acer spin 713-2W, and other than the fans not working right, the only other issue is that the internal audio is not working. I ran sof-audio-setup and it appears to successfully run, but the only audio device that appears after rebooting is "dummy output". I uploaded alsa-info and dmesg outputs. alsa.txt dmesg.txt

1Guardian avatar Apr 23 '22 17:04 1Guardian

What about running this from Breath:

git clone https://github.com/thesofproject/sof-bin —depth 1
cd sof-bin
sudo ./install.sh v2.1.x

MilkyDeveloper avatar Apr 24 '22 13:04 MilkyDeveloper

It fails due to not being able to find files/folders that appear to be expected to come with it. Full error included below.

+ ln -sT sof-v2.1.x /lib/firmware/intel/sof
+ ln -sT sof-tplg-v2.1.x /lib/firmware/intel/sof-tplg
+ rsync -a ./sof*v2.1.x /lib/firmware/intel/
rsync: [sender] link_stat "/home/administrator/makecrap/sof-bin/sof*v2.1.x" failed: No such file or directory (2)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1333) [sender=3.2.3]

1Guardian avatar Apr 24 '22 18:04 1Guardian

cd v2.1.x
rsync -a sof*v2.1.1   /lib/firmware/intel/
ln -s sof-v2.1.1      /lib/firmware/intel/sof
ln -s sof-tplg-v2.1.1 /lib/firmware/intel/sof-tplg
rsync tools-v2.1.1/*  /usr/local/bin

MilkyDeveloper avatar Apr 24 '22 18:04 MilkyDeveloper

Yep, that worked!

Thanks!

1Guardian avatar Apr 24 '22 19:04 1Guardian

I'll be opening this issue if you don't mind so I can close it when I make this run OOTB.

MilkyDeveloper avatar Apr 24 '22 19:04 MilkyDeveloper

No problem at all, and thanks again for the help!

1Guardian avatar Apr 24 '22 19:04 1Guardian

One point of note @MilkyDeveloper, the module doesn't seem to load for the audio device if the os is restarted. When it restarts, it switches back to only having a dummy output. When the device is completely powered off and then back on, it loads back up and the audio works again. Not really an issue for my use case, but just thought I'd mention it.

Update: It happens randomly on cold boot too. Doesn't seem to have any pattern as to when the module loads correctly or not, and always requires a shutdown and turn back on to get it working again.

1Guardian avatar Apr 26 '22 04:04 1Guardian

By module I assume you mean a kernel module (like one that is in /lib/modules and determined using lsmod).

Do you know what module this is? I think an alsa-info before and after audio works would be useful if you can’t figure this out.

MilkyDeveloper avatar Apr 27 '22 19:04 MilkyDeveloper

I'm not sure which one it would be, and the only reason I thought it might be was from seeing a line that said something like "loaded/loading alsa driver modules" in the boot log (journalctl logs) and it's corresponding field was empty. I did however get the alsa-info outputs for both when it's working and when it's not, so maybe you can make something out of it.

Alsa-Output-Not-Working.txt Alsa-Output-Working.txt

1Guardian avatar Apr 28 '22 00:04 1Guardian

I think the audio card is sometimes getting initialized by Depthcharge. This might still be a SOF error, so I've posted an issue for them here. You might want to follow that instead.

MilkyDeveloper avatar Apr 28 '22 01:04 MilkyDeveloper

Will do, thanks!

1Guardian avatar Apr 28 '22 01:04 1Guardian