Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Panella <stefano.panella@citrix.com>
To: alsa-devel@alsa-project.org
Subject: Problem opening default device in haswell system using aplay
Date: Wed, 22 May 2013 16:48:58 +0100	[thread overview]
Message-ID: <519CE8EA.3010303@citrix.com> (raw)

Hi everyone,

sorry if this email has been sent twice... ( I sent it once before subscribing)

I am working on some haswell systems running Ubuntu 12.04 and I have a problem if I run aplay -D sysdefault.

when I do:

cat /proc/asound/pcm

I get:

00-03: HDMI 0 : HDMI 0 : playback 1
00-07: HDMI 1 : HDMI 1 : playback 1
00-08: HDMI 2 : HDMI 2 : playback 1
01-00: ALC662 rev3 Analog : ALC662 rev3 Analog : playback 1 : capture 1
01-02: ALC662 rev3 Analog : ALC662 rev3 Analog : capture 1

If I do:

aplay -L | grep sysdefault

I get:

sysdefault:CARD=PCH

where PCH is card number 1 (id = 1)

on most of my systems (non haswell laptops) the default card is number 0

If I run

aplay -D sysdefault

I get:

ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
aplay: main:682: audio open error: No such file or directory

if I strace it I get:

open("/dev/snd/pcmC0D0p", O_RDWR|O_NONBLOCK|O_CLOEXEC) = -1 ENOENT (No
such file or directory)

If I run:

aplay -D hw:PCH,0

all works fine...

Any idea why hw:PCH,0 works and sysdefault does not?

I guess there could be a problem in the mapping of devices in hw systems?

Has anybody else observed a similar issue? Or has this been a problem in
the past already fixed upstream?
If so, where was it fixed (kernel, lib, tools, utils, etc.) ?

Thanks for all your help on this.

In case this is a real problem I am willing to help debugging it and
submit patches.

Stefano

             reply	other threads:[~2013-05-22 15:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-22 15:48 Stefano Panella [this message]
2013-05-24  2:18 ` Problem opening default device in haswell system using aplay Raymond Yau
2013-05-24 22:50   ` Stefano Panella
2013-05-27  7:07 ` Takashi Iwai
2013-05-28  9:26   ` Stefano Panella

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=519CE8EA.3010303@citrix.com \
    --to=stefano.panella@citrix.com \
    --cc=alsa-devel@alsa-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox