From: "David E. Storey" <dave@tamos.net>
To: Mark Knecht <mknecht@controlnet.com>
Cc: alsa <alsa-devel@lists.sourceforge.net>
Subject: RE: aplay: pcm_write:1025: write error & SNDRV_PCM_IOCTL_PREPAREfailed:device or resource busy
Date: 02 Jun 2003 10:49:52 -0400 [thread overview]
Message-ID: <1054565392.602.177.camel@localhost> (raw)
In-Reply-To: <NDBBLGIKBJENLAMOLFHGEELNCFAB.mknecht@controlnet.com>
[-- Attachment #1: Type: text/plain, Size: 736 bytes --]
most likely,
aplay -D hw:1,0 sound.wav
d!
On Mon, 2003-06-02 at 10:35, 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???
>
>
>
>
> -------------------------------------------------------
> 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
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/alsa-devel
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-06-02 14:49 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
2003-06-02 14:59 ` Mark Knecht
2003-06-02 14:49 ` David E. Storey [this message]
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=1054565392.602.177.camel@localhost \
--to=dave@tamos.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox