From: Wakko Warner <wakko@animx.eu.org>
To: Bob McElrath <rsmcelrath@students.wisc.edu>
Cc: Pierfrancesco Caci <p.caci@seabone.net>, linux-kernel@vger.kernel.org
Subject: Re: es1371 and recent kernels
Date: Tue, 12 Jun 2001 16:42:04 -0400 [thread overview]
Message-ID: <20010612164204.A21504@animx.eu.org> (raw)
In-Reply-To: <873d95lnqr.fsf@paperino.int-seabone.net> <20010612111503.A870@draal.physics.wisc.edu>
In-Reply-To: <20010612111503.A870@draal.physics.wisc.edu>; from Bob McElrath on Tue, Jun 12, 2001 at 11:15:03AM -0500
> > [please be kind and Cc when replying]
> >
> > Has someone been able to get es1371 to actually produce anything
> > audible with latest kernels? The last version I could use was 2.4.0.
> > Then I had some trouble but I attributed them to devfs. Now I've
> > removed devfs and still I'm not able to play anything.
>
> Works for me, but it produces all kinds of crackly noise garbage. I'm
> not sure if this is because the driver has a bug, or the sound card is
> a piece of flaming shit. But I'm inclined to believe the latter.
>
> Anybody have a suggestion for a card that isn't a flaming piece of shit,
> (and not made by Creative) less than $100 US, PCI, supported by linux,
> and available?
My ES1370 has done me good. You might want to try that card. Yes it's a
creative card. It only has a crackle running 22k 8-bit
--
Lab tests show that use of micro$oft causes cancer in lab animals
next prev parent reply other threads:[~2001-06-12 20:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-12 15:30 es1371 and recent kernels Pierfrancesco Caci
2001-06-12 15:53 ` Luigi Genoni
2001-06-12 16:15 ` Bob McElrath
2001-06-12 20:42 ` Wakko Warner [this message]
2001-06-12 20:55 ` Jeff Golds
2001-06-12 21:31 ` Bob McElrath
2001-06-12 21:43 ` Jeff Garzik
2001-06-12 21:55 ` Wakko Warner
2001-06-12 21:47 ` David S. Miller
2001-06-12 17:05 ` James Stevenson
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=20010612164204.A21504@animx.eu.org \
--to=wakko@animx.eu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.caci@seabone.net \
--cc=rsmcelrath@students.wisc.edu \
/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).