From: "Robert L. Harris" <Robert.L.Harris@rdlg.net>
To: David Ford <david+hb@blue-labs.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6 sound drivers?
Date: Wed, 16 Jul 2003 20:08:04 -0400 [thread overview]
Message-ID: <20030717000804.GT2412@rdlg.net> (raw)
In-Reply-To: <3F15E3C9.4030401@blue-labs.org>
[-- Attachment #1: Type: text/plain, Size: 1489 bytes --]
No go, it looks like it's playing but nothing to the speakers.
Thus spake David Ford (david+hb@blue-labs.org):
> /dev/sound/* is from OSS. You'll have to enable OSS emulation if you
> want legacy apps to be able to use your sound.
>
> Alternatively, mpg123 --stdout | aplay, or similar. Use a script or
> alias to make it easy on yourself.
>
> David
>
> Robert L. Harris wrote:
>
> >I do but the problem is I don't have a /dev/dsp, /dev/sound/dsp or
> >anything else to point mpg123 at.
> >
> >Thus spake Mike Fedyk (mfedyk@matchmail.com):
> >
> >
> >
> >>On Wed, Jul 16, 2003 at 06:58:26PM -0400, Robert L. Harris wrote:
> >>
> >>
> >>>I have a soundblaster Live. I've historically used the OSS drivers as
> >>>they've worked well for me. I just tried to load the emu10k1 which
> >>>loads without error, but mpg123 says it can't open the default sound
> >>>device.
> >>>
> >>>Anyone able to do an lsmod or a listing of the drivers I need for an
> >>>SBLive?
> >>>
> >>>
> >>Did you install alsa-utils?
> >>
> >
:wq!
---------------------------------------------------------------------------
Robert L. Harris | GPG Key ID: E344DA3B
@ x-hkp://pgp.mit.edu
DISCLAIMER:
These are MY OPINIONS ALONE. I speak for no-one else.
Diagnosis: witzelsucht
IPv6 = robert@ipv6.rdlg.net http://ipv6.rdlg.net
IPv4 = robert@mail.rdlg.net http://www.rdlg.net
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-07-16 23:53 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 22:58 2.6 sound drivers? Robert L. Harris
2003-07-16 23:10 ` Rudo Thomas
2003-07-16 23:29 ` Robert L. Harris
2003-07-16 23:46 ` Rudo Thomas
2003-07-16 23:10 ` Mike Fedyk
2003-07-16 23:30 ` Robert L. Harris
2003-07-16 23:39 ` Mike Fedyk
2003-07-16 23:46 ` David Ford
2003-07-17 0:08 ` Robert L. Harris [this message]
2003-07-17 1:07 ` Wes Janzen
2003-07-17 1:42 ` James H. Cloos Jr.
2003-07-17 7:26 ` Martin Schlemmer
2003-07-17 8:57 ` Eugene Teo
2003-07-17 9:22 ` Takashi Iwai
2003-07-17 11:19 ` Ookhoi
2003-07-17 11:31 ` Ed Sweetman
2003-07-17 12:10 ` Alan Cox
2003-07-17 13:11 ` Ookhoi
2003-07-17 11:32 ` Takashi Iwai
2003-07-16 23:37 ` Jeff Garzik
2003-07-16 19:25 ` Max Valdez
2003-07-17 1:05 ` Jeff Garzik
2003-07-17 2:18 ` Norberto BENSA
2003-07-17 13:13 ` Ian Hastie
2003-07-17 13:25 ` Takashi Iwai
2003-07-17 13:19 ` Terje Kvernes
2003-07-17 16:08 ` Norberto BENSA
2003-07-17 11:22 ` Max Valdez
2003-07-17 16:54 ` Takashi Iwai
2003-07-17 18:43 ` Norberto BENSA
2003-07-17 19:44 ` Ian Hastie
2003-07-18 9:45 ` Takashi Iwai
2003-07-17 18:46 ` dacin
2003-07-17 19:12 ` MONOLITHIC sound (was Re: 2.6 sound drivers?) Douglas J Hunley
2003-07-17 20:09 ` dacin
2003-07-16 23:39 ` 2.6 sound drivers? Robert L. Harris
2003-07-16 23:57 ` Matt Reppert
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=20030717000804.GT2412@rdlg.net \
--to=robert.l.harris@rdlg.net \
--cc=david+hb@blue-labs.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).