All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mark Knecht <mknecht@controlnet.com>
Cc: Alsa-Devel <alsa-devel@lists.sourceforge.net>
Subject: Re: aplay: pcm_write:1025: write error &	SNDRV_PCM_IOCTL_PREPAREfailed:device or resource busy
Date: Mon, 02 Jun 2003 16:48:14 +0200	[thread overview]
Message-ID: <s5hvfvoo7rl.wl@alsa2.suse.de> (raw)
In-Reply-To: <NDBBLGIKBJENLAMOLFHGEELNCFAB.mknecht@controlnet.com>

At Mon, 2 Jun 2003 07:35:49 -0700,
Mark Knecht wrote:
> 
> >
> > anyway, in general, BIOS on some ASUS boards have a bug, and the first
> > PCM device won't work on them.
> >
> 
> Can I tell aplay to use any other PCM device? The second device? How might I
> do this?
> 
> aplay hw:1 sound.wav???

please use -D option, for example,

	% aplay -D hw:0,1 sound.wav

for the second pcm device.  the first 0 means the first "card" and you
cannot ommit it to specify the pcm device number.


Takashi


-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5

  reply	other threads:[~2003-06-02 14:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-19  0:05 aplay: pcm_write:1025: write error & SNDRV_PCM_IOCTL_PREPAREfailed:device or resource busy Mark Knecht
2003-05-21 11:09 ` Takashi Iwai
2003-05-30  4:43   ` Mark Knecht
2003-06-02 11:11     ` Takashi Iwai
2003-06-02 13:41       ` Mark Knecht
2003-06-02 13:55         ` Takashi Iwai
2003-06-02 14:20           ` Mark Knecht
2003-06-02 14:25             ` Takashi Iwai
2003-06-02 14:33               ` Mark Knecht
2003-06-02 14:46                 ` Takashi Iwai
2003-06-03  4:14               ` Mark Knecht
2003-06-02 14:35           ` Mark Knecht
2003-06-02 14:48             ` Takashi Iwai [this message]
2003-06-02 14:59               ` Mark Knecht
2003-06-02 14:49             ` David E. Storey

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=s5hvfvoo7rl.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=mknecht@controlnet.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.