No audio on intel baytrail minipc

andrius · December 16, 2018 at 11:25 AM

Hello,

I installed libreelec v8.90.008 on a cheap chinese minipc (it says Product model: I5).

The problems are the following:

I get is no audio on analog 3.5 mm output.
the video begins to play, but stops after a minute or so. (Video played well on 'stable' libreelec releases, I just hoped audio gets better on alpha)

Dmesg prints many lines "Baytrail Audio Port: ASoC: no backend DAIs enabled for Baytrail Audio Port".

- Full hardware specs (GPU is most important)

intel z3735f

- The LibreELEC version you are running ('latest' is not a version number)

LibreELEC (official): 8.90.009 (Generic.x86_64)

- In most cases a full debuglog

attached: kodilog20181216.zip

- Tell us the complete steps how to face the issue, so we can try to reproduce

I try to play any video, I get no sound from it.

- Name the specific hardware and maybe a link to the manufactor

pp_365007.html?wid=1527929

- Get us the output of 'dmesg' while the hardware is connected

plenty of:

[ 2358.053029] Baytrail Audio Port: ASoC: no backend DAIs enabled for Baytrail Audio Port

- Get us the output of 'lspci' if it's about PCI hardware

minipc:~ # lspci

00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register (rev 0f)

00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0f)

00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI (rev 0f)

00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine (rev 0f)

00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit (rev 0f)

- Get us the output of 'lsusb' if it's about some USB hardware

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Bus 001 Device 005: ID 413c:3016 Dell Computer Corp. Optical 5-Button Wheel Mouse

Bus 001 Device 004: ID 413c:2003 Dell Computer Corp. Keyboard

Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub

Bus 001 Device 002: ID 0bda:8152 Realtek Semiconductor Corp. RTL8152 Fast Ethernet Adapter

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Andrius

**HiassofT** · December 16, 2018 at 12:01 PM

Can you please post the full dmesg output?

Code

dmesg | paste

so long,

Hias

andrius · December 16, 2018 at 4:02 PM

Currently it is full of "no backend DAIs": http://ix.io/1w8z

After reboot: http://ix.io/1w90

**HiassofT** · December 16, 2018 at 7:34 PM

Thanks for the log!

It looks like we're missing a firmware file:

Quote

[ 2.824531] intel_sst_acpi 80860F28:00: Direct firmware load for intel/fw_sst_0f28.bin failed with error -2

Could you update to LibreELEC 8.90.009 and then run the following 2 commands

Code

mkdir -p /storage/.config/firmware/intel
wget -O /storage/.config/firmware/intel/fw_sst_0f28.bin https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/intel/fw_sst_0f28.bin

After that reboot so the kernel can pick up the firmware.

Please post dmesg again and drop us a line if it worked or not.

so long,

Hias

**HiassofT** · December 16, 2018 at 8:20 PM

Sorry, false alarm, the firmware is already included in the image, so it's something else.

It looks like the audio driver is built into the kernel and at driver probe time the firmwares from the system image aren't available yet. I'll have a look at it and report back - probably building the audio driver as a module should work fine.

so long,

Hias

andrius · December 17, 2018 at 7:47 AM

Thank you for looking into this issue. Waiting for the results and instructions

andrius · December 17, 2018 at 8:10 AM

I unzipped the windows driver package I got for this device. The directory /DriverPackage/Installer/PlatformInstaller/Drivers/audio/ contains the following files:

isstrtc.cat

isstrtc.inf

isstrtc.sys

realtek_fw_sst.bin

rtii2sac.cat

rtii2sac.inf

RTII2SAC.sys

Maybe this realtek_fw_sst.bin can useful?

**HiassofT** · December 17, 2018 at 12:18 PM

Could you test the latest Milhouse build #1216 from here? libreelec-generic.x86_64-9.0-milhouse-20181217113701-#1216-g850dc0f.tar

The intel_sst_acpi audio driver is now built as a module so firmware loading should hopefully work.

Either way: please post dmesg and lsmod output shortly after bootup

so long,

Hias

andrius · December 17, 2018 at 2:00 PM

How do I install it? Usually I put the img file into /storage/.updates

The tar file you sent is not an img. I guess /target directory contains the image files, but how do I install them?

andrius · December 17, 2018 at 2:28 PM

Still no sound output.

Code

##############################################
#                 LibreELEC                  #
#            https://libreelec.tv            #
##############################################

LibreELEC (Milhouse): devel-20181217113701-#1216-g850dc0f (Generic.x86_64)
minipc:~ # dmesg | paste
http://ix.io/1wdI
minipc:~ # pactl info
Server String: /var/run/pulse/native
Library Protocol Version: 32
Server Protocol Version: 32
Is Local: yes
Client Index: 2
Tile Size: 65472
User Name: root
Host Name: minipc
Server Name: pulseaudio
Server Version: 12.2
Default Sample Specification: s16le 2ch 44100Hz
Default Channel Map: front-left,front-right
Default Sink: auto_null
Default Source: auto_null.monitor
Cookie: a6c6:c77a
minipc:~ # zip kodilog20181217.zip  .kodi/temp/kodi.log

Display More

dmesg: http://ix.io/1wdi

kodi.log: kodilog20181217.zip

Andrius

**HiassofT** · December 17, 2018 at 11:02 PM

Thanks a lot for the logs, the firmware error is gone which is a good sign!

I've checked the alsa-devel mailing list and it looks like baytrail needs some userspace configuration in place before the audio device can be used.

This stuff (alsaucm) is currently missing in LibreELEC, I'll prepare a new build and post an update when it's finished.

so long,

Hias

**HiassofT** · December 18, 2018 at 12:29 PM

Can you test this build: libreelec-generic.x86_64-9.0-devel-20181217224448-658cde5.tar

It includes the Alsa UCM configuration tool and files needed to manually setup baytrail audio.

After boot quickly ssh in and stop kodi so dmesg doesn't get spammed with "no backend DAI" messages:

Code

systemctl stop kodi

Then run alsaucm to configure the audio device

Code

alsaucm -c bytcr-rt5640 set _verb HiFi

Now use speaker-test to check if you can get audio from the analog output / Line out:

Code

speaker-test -c 2 -t sine

Abort speaker-test with control-c after a couple of seconds and then post dmesg - if you didn't get audio it could be because something else is still missing and/or you may need a different firmware file (maybe the one from the windows driver you mentioned).

If you got audio, start kodi again with systemctl start kodi and check if it works there, too. If it does. add the alsaucm command to autostart.sh to make the configuration permanent.

so long,

Hias

andrius · December 18, 2018 at 8:25 PM

Still no sound after speaker-test.

How do I try different firmware?

Andrius

minipc:~ # dmesg | paste

http://ix.io/1wka

minipc:~ # cat /storage/.kodi/temp/kodi.log | paste

http://ix.io/1wkb

Code

##############################################
#                 LibreELEC                  #
#            https://libreelec.tv            #
##############################################

LibreELEC (HiassofT): devel-20181217224448-658cde5 (Generic.x86_64)
minipc:~ # systemctl stop kodi
minipc:~ # 
minipc:~ # alsaucm -c bytcr-rt5640 set _verb HiFi
minipc:~ # speaker-test -c 2 -t sine

speaker-test 1.1.7

Playback device is default
Stream parameters are 48000Hz, S16_LE, 2 channels
Sine wave rate is 440.0000Hz
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 16 to 204800
Period size range from 8 to 102400
Using max buffer size 204800
Periods = 4
was set period_size = 51200
was set buffer_size = 204800
 0 - Front Left
 1 - Front Right
Time per period = 4.239388
 0 - Front Left
 1 - Front Right
Time per period = 4.246584
 0 - Front Left
 1 - Front Right
Time per period = 4.246258
 0 - Front Left
 1 - Front Right
Time per period = 4.252681
 0 - Front Left
 1 - Front Right
Time per period = 4.240290
 0 - Front Left
 1 - Front Right
Time per period = 4.241668
 0 - Front Left
 1 - Front Right
^CTime per period = 2.149490
minipc:~ # 
minipc:~ # 
minipc:~ # dmesg | paste
http://ix.io/1wka
minipc:~ # cat /storage/.kodi/temp/kodi.log | paste
http://ix.io/1wkb
minipc:~ #

Display More

**HiassofT** · December 19, 2018 at 12:31 PM

Thanks for the logs! dmesg spam seems to be gone, but there are lots of Alsa errors in the kodi log. I think it's best to focus on getting speaker-test working.

I looked through the alsaucm docs and noticed I missed an important step: after setting the _verb we also need to enable the (output) device. The output devices "Headphones" and "Speaker" look like good candidates.

Please try these commands:

Code

alsaucm -c bytcr-rt5640 set _verb HiFi
alsaucm -c bytcr-rt5640 set _enadev Headphones

Then run speaker-test -c 2 -t sine again and upload dmesg.

If it didn't work try with the Speakers device - but before we need to disable the Headphones device

Code

alsaucm -c bytcr-rt5640 set _disdev Headphones
alsaucm -c bytcr-rt5640 set _enadev Speaker

According to the manual using the "reset" command should also work, this should allow us to start from scratch:

Code

alsaucm -c bytcr-rt5640 reset
alsaucm -c bytcr-rt5640 set _verb HiFi
alsaucm -c bytcr-rt5640 set _enadev Speaker

Try speaker-test again and grab dmesg.

If you get any errors on the terminal these would be interesting, too.

so long,

Hias

andrius · December 19, 2018 at 7:43 PM

_enadev and _disdev give me some errors.

I'll try to read some docs about them.

Code

LibreELEC (HiassofT): devel-20181217224448-658cde5 (Generic.x86_64)
minipc:~ # systemctl stop kodi
minipc:~ # 
minipc:~ # alsaucm -c bytcr-rt5640 set _verb HiFi
minipc:~ # alsaucm -c bytcr-rt5640 set _enadev Headphones
alsaucm: error failed to set _enadev=Headphones: No such file or directory
minipc:~ # alsaucm -c bytcr-rt5640 set _disdev Headphones
alsaucm: error failed to set _disdev=Headphones: No such file or directory
minipc:~ # alsaucm -c bytcr-rt5640 set _enadev Speaker
alsaucm: error failed to set _enadev=Speaker: No such file or directory
minipc:~ # alsaucm -c bytcr-rt5640 reset
minipc:~ # 
minipc:~ # alsaucm -c bytcr-rt5640 set _verb HiFi
minipc:~ # alsaucm -c bytcr-rt5640 set _enadev Speaker
alsaucm: error failed to set _enadev=Speaker: No such file or directory
minipc:~ #

Display More

**HiassofT** · December 19, 2018 at 7:54 PM

Ah, sorry, I should have read the manpage more carefully - using 2 separate alsaucm calls doesn't work.

The end of the manpage gives an example how the Speaker device on baytrail can be selected - better use that as a template Ubuntu Manpage: alsaucm - ALSA Use Case Manager

Code

alsaucm -n -b - <<EOM
open bytcr-rt5640
reset
set _verb HiFi
set _enadev Speaker
EOM

andrius · December 19, 2018 at 8:01 PM

Yes, this seemingly works somehow with Headphones value. speaker-test is just producing beeps in both ears. Shouldn't it make some sines?

I'll test Speaker and some movie with kodi.

andrius · December 19, 2018 at 8:12 PM

"Speaker" does not produce any sound on my headphones.

"Headphones" always makes beeps in both ears at the same time, even though the speaker-test says "0 - Front Left" or "1 - Front Right".

Movie playing in Kodi just makes some strange noise.

But the beeps are definitely a big progress when comparing with the complete silence

Any ideas - what can I try now?

Vielen Dank Matthias!

Andrius