Acer Chromebook Spin 514

[ph1-xyz]

Hi!!

Following the docs, I managed installing Ubuntu on my laptop, but the screen backlight and sound, in spite of sof-setup-audio do not work.

These are the model information:

System:    Host: ubuntu Kernel: 5.10.88 x86_64 bits: 64 Desktop: KDE Plasma 5.21.4 
           Distro: Ubuntu 21.04 (Hirsute Hippo) 
Machine:   Type: Laptop System: Google product: Ezkinil v: rev4 serial: <superuser required> 
           Mobo: Google model: Ezkinil v: rev4 serial: <superuser required> BIOS: coreboot 
           v: Google_Ezkinil.13434.397.0 date: 07/20/2021 
Audio:     Device-1: Advanced Micro Devices [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio driver: snd_hda_intel 
           Device-2: Advanced Micro Devices [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor 
           driver: snd_pci_acp3x 
           Sound Server: ALSA v: k5.10.88 

[MilkyDeveloper]

What's the output of dmesg and the file created by sudo alsa-info?

[ph1-xyz]

dmesg dmesg-log.txt

alsa-info results http://alsa-project.org/db/?f=9514f2070a85a17b6d94c20f892deb397704ab4f

[MilkyDeveloper]

Looks like there's a bug in the kernel and this is not userspace. Could you run VERSION=ALT bash updatekernel.sh on the PC you built Breath with?

[ph1-xyz]

Sure, thanks.

Should I update the Breath installation support and the Breath installed on the Chromebook?

[MilkyDeveloper]

Yes.

[ph1-xyz]

Thanks, for the development. I reinstalled the OS with the updated instructions and the ALT kernel flag: still not working :-/

dmesg dmesg-log.txt alsa-info http://alsa-project.org/db/?f=b79d00be9d900fa5b84d1bdb2117be0b21e12235

PS: the brightness works!! 🎉 🎊

[MilkyDeveloper]

Could you run alsa info with sudo?

[ph1-xyz]

Here it is

http://alsa-project.org/db/?f=e40a043b457849331be79f08ee3eff1106e2520a

[ph1-xyz]

Hi @MilkyDeveloper

I installed Mr. Chromebox UEFI-BIOS and I'm now able to boot standard Linux distros.

I'm using Manjaro, but graphics (and touch screen) doesn't work; could you tell me where to find the correct AMD drivers so that I can try and update them myself?

Thanks!

[timmypidashev]

@ph1-xyz Most chromebooks don't have support for hadrware accelerated gpu's, but in your case, It might be best to go ahead and install the mesa graphics api

pamac build mesa-git lib32-mesa-git

Reboot and verify success by checking Mesa version:

glxinfo | grep Mesa

Hope this helps!

[ph1-xyz]

Here it is

http://alsa-project.org/db/?f=e40a043b457849331be79f08ee3eff1106e2520a

Hi @MilkyDeveloper, are there updates about this?

[MilkyDeveloper]

I don't have an AMD Chromebook, but following the build instructions again (including recloning the git repo) gives you a newer kernel and may fix it.

[ph1-xyz]

Thanks, I did it and things improved:

I'm able to stream audio via Bluetooth but still I can't hear no sound through speakers or headphones.

dmesg returns

[  318.127080] rt5682 i2c-10EC5682:00: Failed to register rt5682-dai-wclk: -17
[  318.127082] rt5682 i2c-10EC5682:00: ASoC: error at snd_soc_component_probe on i2c-10EC5682:00: -17
[  318.127117] acp3x-alc5682-max98357 AMDI5682:00: ASoC: failed to instantiate card -17
[  318.127155] acp3x-alc5682-max98357 AMDI5682:00: devm_snd_soc_register_card(acp3xalc5682m98357) failed: -17
[  318.127180] acp3x-alc5682-max98357: probe of AMDI5682:00 failed with error -17

[MilkyDeveloper]

This confuzzles me. acp3xalc5682m98 is the right sound card, but there are rt5682 logs, meaning that its (wrong) module was loaded.

Did you by chance run the RTK version of sof-setup-audio? If so, replace it by running only sof-setup-audio. A dmesg and lsmod from ChromeOS would be nice.

[MilkyDeveloper]

acp3x-alc5682-max98357 AMDI5682:00: ASoC: failed to instantiate card -17

Error -17 is that the file already exists. I think snd_hda_intel must be conflicting with acp3x-alc5682-max98357, but I've already blacklisted it.

[MilkyDeveloper]

What’s the output of lsmod? Sorry for the late reply :D

[ph1-xyz]

No problem :-D

Here it is

lsmodAcerChromebook.txt

[ph1-xyz]

Hi @MilkyDeveloper,

is there any news about this issue? Something I could try to make audio work?