From: Lee Revell <rlrevell@joe-job.com>
To: Pavel Machek <pavel@suse.cz>
Cc: Nishanth Aravamudan <nacc@us.ibm.com>,
Nick Warne <nick@linicks.net>,
Jesper Juhl <jesper.juhl@gmail.com>,
tiwai@suse.de, ghrt@dial.kappa.ro, perex@suse.cz,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: No sound from SB live!
Date: Sun, 19 Feb 2006 16:54:34 -0500 [thread overview]
Message-ID: <1140386075.2733.399.camel@mindpipe> (raw)
In-Reply-To: <20060219214934.GO15311@elf.ucw.cz>
On Sun, 2006-02-19 at 22:49 +0100, Pavel Machek wrote:
> Hi!
>
> > > I run Ubuntu Breezy, which has:
> > >
> > > alsa-utils = 1.0.9a-4ubuntu5
> >
> > The alsa-utils version should not matter, it's alsa-lib that must be
> > kept in sync with the ALSA version in the kernel.
>
> I tried to play with mpg123 using OSS emulation, so that it does not
> have anything to do with ALSA. No luck. Trying aplay:
>
> root@hobit:/dev/snd# aplay
> /usr/share/xemacs21/xemacs-packages/etc/sounds/hammer.wav
> aplay: main:533: audio open error: No such file or directory
>
> while stracing:
>
> open("/dev/snd/pcmC0D0p", O_RDWR) = -1 ENOENT (No such file or
> directory)
> close(3) = 0
> write(2, "aplay: main:533: ", 17aplay: main:533: ) = 17
> write(2, "audio open error: No such file o"..., 43audio open error: No
> such file or directory) = 43
> write(2, "\n", 1
>
> ... but pcmC0D0p is not described in devices.txt...?
Hmm, that's a udev problem or something. If you have a static dev the
snddevices script that comes with ALSA will create the device files.
Lee
next prev parent reply other threads:[~2006-02-19 21:54 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-18 23:14 Pavel Machek
2006-02-18 23:27 ` ghrt
2006-02-18 23:48 ` Pavel Machek
2006-02-19 0:33 ` Richard Mittendorfer
2006-02-19 21:42 ` Pavel Machek
2006-02-19 22:07 ` Richard Mittendorfer
2006-02-19 0:58 ` Lee Revell
2006-02-19 21:44 ` Pavel Machek
2006-02-20 0:33 ` Lee Revell
2006-02-20 0:39 ` Pavel Machek
2006-02-20 1:33 ` Alistair John Strachan
2006-02-20 23:55 ` Pavel Machek
2006-02-19 11:04 ` Jesper Juhl
2006-02-19 11:18 ` Nick Warne
2006-02-19 19:29 ` Lee Revell
2006-02-19 20:20 ` Nick Warne
2006-02-19 20:31 ` Lee Revell
2006-02-20 19:18 ` Nick Warne
2006-02-20 19:31 ` D. Hazelton
2006-02-19 20:33 ` Lee Revell
2006-02-19 20:51 ` Nishanth Aravamudan
2006-02-19 21:30 ` Lee Revell
2006-02-19 21:47 ` Pavel Machek
2006-02-19 21:50 ` Lee Revell
2006-02-19 23:23 ` Alistair John Strachan
2006-02-19 23:32 ` Lee Revell
2006-02-19 23:46 ` Pavel Machek
2006-02-19 23:53 ` Lee Revell
2006-02-20 0:04 ` Nishanth Aravamudan
2006-02-20 0:11 ` Lee Revell
2006-02-20 0:57 ` Nishanth Aravamudan
2006-02-20 0:26 ` Pavel Machek
2006-02-20 0:30 ` Lee Revell
2006-02-20 0:42 ` Pavel Machek
2006-02-20 0:52 ` Lee Revell
2006-02-19 23:56 ` Alistair John Strachan
2006-02-20 0:05 ` Lee Revell
2006-02-20 0:12 ` David Lang
2006-02-20 0:16 ` Alistair John Strachan
2006-02-20 0:17 ` Lee Revell
2006-02-19 21:49 ` Pavel Machek
2006-02-19 21:54 ` Lee Revell [this message]
2006-02-19 22:25 ` Pavel Machek
2006-02-19 22:28 ` Lee Revell
2006-02-19 23:04 ` Lee Revell
2006-02-20 11:15 ` Takashi Iwai
2006-02-20 11:41 ` Pavel Machek
2006-02-20 19:50 ` Vojtech Pavlik
2006-02-20 19:52 ` Pavel Machek
2006-02-19 19:19 ` Pavel Machek
2006-02-22 14:05 ` Takashi Iwai
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=1140386075.2733.399.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=ghrt@dial.kappa.ro \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nacc@us.ibm.com \
--cc=nick@linicks.net \
--cc=pavel@suse.cz \
--cc=perex@suse.cz \
--cc=tiwai@suse.de \
/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
all inboxes | Powered by JetHome®