From: GrandMasterLee <masterlee@digitalroadkill.net>
To: xizard@enib.fr
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: sound is stutter, sizzle with lasts kernel releases
Date: 02 Dec 2002 09:24:53 -0600 [thread overview]
Message-ID: <1038842693.2897.3.camel@localhost> (raw)
In-Reply-To: <3DEAA671.5090008@enib.fr>
On Sun, 2002-12-01 at 18:16, XI wrote:
>
> >
> >>I think the first thing I should do is to try different kernel version
> >>in order to find when this problem appeared first.
> >
> >
> > --The GrandMaster
> >
>
> Thanks for the reply,
>
> I don't think this is the problem, because nothing is plugged into mic
> or line in; and all settings are set to 0 in aumix except Vol, Pcm and
> OGain.
It's not so much about what is connected to the devices, as what is
actually going on in the asic on the board. If something were faulty, or
slightly more sensetive than it should be(too high a tolerance), then
you could get this affect. Changing your mixer parameters might show you
the light, er um...let you hear the difference and see if it gets worse
or not. Another thing you could also do, is move the sblive card to a
different slot, if not yet tried. If in too close proximity to the NIC,
it *could* cause this behaviour as well.
>
> Xavier
>
next prev parent reply other threads:[~2002-12-02 15:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-01 16:00 PROBLEM: sound is stutter, sizzle with lasts kernel releases XI
2002-12-01 17:53 ` Alan Cox
2002-12-02 0:16 ` XI
2002-12-02 16:09 ` Alan Cox
2002-12-02 18:48 ` XI
2002-12-04 11:11 ` Pavel Machek
2002-12-01 18:54 ` GrandMasterLee
2002-12-02 0:16 ` XI
2002-12-02 15:24 ` GrandMasterLee [this message]
2002-12-03 1:19 ` GrandMasterLee
2002-12-13 0:31 ` Herman Oosthuysen
-- strict thread matches above, loose matches on Subject: below --
2002-12-03 4:57 PlasmaJohn
2002-12-03 22:39 ` Thomas Molina
2003-01-05 0:59 ` XI
2003-01-05 10:04 ` John Bradford
2003-01-05 14:11 ` XI
2003-01-05 13:21 ` John Bradford
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=1038842693.2897.3.camel@localhost \
--to=masterlee@digitalroadkill.net \
--cc=linux-kernel@vger.kernel.org \
--cc=xizard@enib.fr \
/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).