From: Doug Alcorn <lathi@seapine.com>
To: linux-kernel@vger.kernel.org
Subject: Re: cs46xx on ThinkPad A22m and poor quality output
Date: 26 Feb 2002 21:21:11 -0500 [thread overview]
Message-ID: <87pu2r1x7s.fsf@localhost.localdomain> (raw)
In-Reply-To: <87vgcjvs1p.fsf@localhost.localdomain>
In-Reply-To: Doug Alcorn's message of "26 Feb 2002 16:42:26 -0500"
Doug Alcorn <lathi@seapine.com> writes:
> The other problem maybe hardware. Like I said, the sound was
> crystal clear. Recently, the output sounds like I blew out my
> speakers. At first I thought it was my crappy headphones. I
> unplugged the headphones and the internal speakers sound the same
> way. It's just at the higher-levels of output (when my xmms eq
> display has lines that peak) it sounds fuzzy. The other interesting
> thing is that streamed audio sounds much worse than my actual mp3
> files. Is it possible the card got smoked?
I hate to follow up to my own post; however, I managed to get the card
working well with the alsa cs46xx driver. This would imply to me that
it's a bug in the linux kernel driver for the cs46xx (is this referred
to as the oss driver?).
BTW, someone suggested I simply turn the volume down using the
hardware buttons on the keyboard. The poor sound quality is really
irrespective of the speaker volume. Maybe this wasn't clear when I
talked about the "higher-levels of output". I'm not sure about the
right vocabulary. I guess it's the power output on the individual
frequency bands.
--
(__) Doug Alcorn (mailto:doug@lathi.net http://www.lathi.net)
oo / PGP 02B3 1E26 BCF2 9AAF 93F1 61D7 450C B264 3E63 D543
|_/ If you're a capitalist and you have the best goods and they're
free, you don't have to proselytize, you just have to wait.
next prev parent reply other threads:[~2002-02-27 2:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 21:42 cs46xx on ThinkPad A22m and poor quality output Doug Alcorn
2002-02-27 2:21 ` Doug Alcorn [this message]
2002-02-27 18:17 ` Dave Hansen
2002-03-01 1:29 ` Theodore Tso
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=87pu2r1x7s.fsf@localhost.localdomain \
--to=lathi@seapine.com \
--cc=doug@lathi.net \
--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 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.