From: Robert Love <rml@tech9.net>
To: Udo Hoerhold <maillists@goodontoast.com>
Cc: Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: SoundBlaster Live! with kernel 2.5.x
Date: 15 Apr 2003 21:49:52 -0400 [thread overview]
Message-ID: <1050457791.3664.188.camel@localhost> (raw)
In-Reply-To: <200304152001.35975.maillists@goodontoast.com>
On Tue, 2003-04-15 at 20:01, Udo Hoerhold wrote:
> I've been running Debian woody with 2.4.20 kernel. I'm trying to switch to
> 2.5. I built 2.5.67 with emu10k driver in the kernel (same as I had with
> 2.4.20), but I get only a lot of popping sounds from the sound card. I also
> tried 2.5.50 and 2.5.67-mm3, with the same result. I googled for emu10k and
> soundblaster with 2.5, but I haven't seen anyone else with the same problem.
> Does anyone know what this problem is?
Not sure. It seems to work fine here.
Are you using ALSA or OSS? Best bet is ALSA. You want something like:
CONFIG_SND=y
CONFIG_SND_SEQUENCER=y
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=y
CONFIG_SND_PCM_OSS=y
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_EMU10K1=y
And then do not include any of the OSS stuff.
Then a normal audio playback on /dev/audio or whatever should work fine.
If not, do you see any errors during boot?
Robert Love
next prev parent reply other threads:[~2003-04-16 1:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-16 0:01 SoundBlaster Live! with kernel 2.5.x Udo Hoerhold
2003-04-16 1:49 ` Robert Love [this message]
[not found] ` <200304152228.11010.maillists@goodontoast.com>
2003-04-16 4:34 ` Udo Hoerhold
2003-04-16 4:58 ` Randy.Dunlap
2003-04-16 6:00 ` Udo Hoerhold
2003-04-16 15:18 ` Randy.Dunlap
-- strict thread matches above, loose matches on Subject: below --
2003-04-16 0:40 Alistair Strachan
2003-04-16 4:29 ` Udo Hoerhold
2003-04-16 14:07 ` Alistair Strachan
2003-04-16 15:33 Paolo Ciarrocchi
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=1050457791.3664.188.camel@localhost \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=maillists@goodontoast.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.