Comment # 7 on bug 1037021 from
Okay, I'm now on my computer. AlsaMixer reports I'm using HDA Intel PCH /
Realtek ALC892.

I have both 64 and 32bit package installed and both have the same version:

Name        : libasound2
Version     : 1.1.3
Release     : 8.6.1

I have only a single alsa.conf on my harddisks. grep says there are three
places where direct_memory_access is used in the whole tree:

/usr/share/alsa/cards/HdmiLpeAudio.conf:HdmiLpeAudio.dmix.direct_memory_access
false
/usr/share/alsa/pcm/dmix.conf:    direct_memory_access {
/usr/share/alsa/pcm/dmix.conf:                ".dmix.direct_memory_access"

The second hit is inside a structure which starts with "pcm.!dmix {" right at
the start of dmix.conf.

> ALSA_CONFIG_PATH

I found an old copy in a snapper snapshot which I tried to copy out of the
snapshot and pass to steam using the ALSA_CONFIG_PATH.

Unfortunately, this gave me a new error and no sound:

ALSA lib pcm.c:2266:(snd_pcm_open_noupdate) Unknown PCM default
[0502/220815.365432:WARNING:alsa_util.cc(24)] PcmOpen: default,no such file or
directory

I found this file inside of steam

libasound2_1.1.0-0ubuntu1+steamos1+srt2_amd64

which suggests steam comes with libasound2 1.1.0. I also found a changelog.gz
and changelog.Debian.gz which says the same.

Regarding alsa config: How distribution specific is the config? Would it make
sense to keep a copy inside of steam to match the libasound2 in there? Or would
it make more sense to force steam to always use the installed libasound2?


You are receiving this mail because: