From: scott thomason <scott-kernel@thomasons.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, perex@suse.cz
Subject: alsa es1968 sound driver broken in 2.5.5x?
Date: Wed, 12 Feb 2003 08:06:36 -0600 [thread overview]
Message-ID: <200302120806.36310.scott-kernel@thomasons.org> (raw)
Greetings. I've been trying to make the ALSA PCI es1968 sound
driver work, for both playback and mic-in recording, with no
success. I've tried kernel versions 2.5.53, 2.5.59, and 2.5.60,
with no luck. I believe that it has to do with the driver
itself, as I can successfully use the ALSA cmipci driver for
both recording and playback. Fortunately, the cmipci chipset
sucks for recording, or I may never have had the motivation to
find and report this bug :)
Unfortunately, I don't know how to give good information for
debugging, only some half-assed descriptions of the symptoms:
1. KMixer won't show the card, just a big empty spot.
2. My favorite synthesizer program, AlsaModularSyth, crashes
immediately upon attempted load.
3. Zinf (formerly freeamp) tells me it can't open audio device
/dev/dsp.
I am using Gentoo 1.4rc1, which means I am using devfs, if that
helps any.
Please let me know if there is a way I can provide better
debugging info.
---scott
reply other threads:[~2003-02-12 13:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200302120806.36310.scott-kernel@thomasons.org \
--to=scott-kernel@thomasons.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
/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