From: John Bradford <john@grabjohn.com>
To: xizard@enib.fr (XI)
Cc: tmolina@copper.net, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: sound is stutter, sizzle with lasts kernel releases
Date: Sun, 5 Jan 2003 10:04:37 +0000 (GMT) [thread overview]
Message-ID: <200301051004.h05A4bxs000499@darkstar.example.net> (raw)
In-Reply-To: <3E17836F.2000303@enib.fr> from "XI" at Jan 05, 2003 01:59:27 AM
> > SBline doesn't share interrupts well. Usually, changing PCI slots in
> > order to affect what interrupt is used can help a lot. The problem is,
> > depending on the motherboard, figuring out what a particular PCI slot
> > shares an interrupt with can be difficult.
>
> After some time, I have tested ALL possibilities with my PCI graphic
> card and my sound blaster live. (4 PCI slots => 12 possibilities).
>
> The problem is always the same, sound still stutter.
>
>
> Sum-up of my problem:
> The sound of my computer stutter when I move a window, watch a movie,
> ... with a kernel 2.4.19 and 2.4.20 ; whereas with a kernel 2.4.8, it
> works fine.
> I use a sound blaster live! with a Matrox G200 PCI, and an AMD 760MPX
> chipset.
Try adding this line to the "Device" section of your XF86Config file:
Option "PciRetry" "true"
and let us know if it stops the stuttering or not.
John.
next prev parent reply other threads:[~2003-01-05 9:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2003-01-05 14:11 ` XI
2003-01-05 13:21 ` John Bradford
-- strict thread matches above, loose matches on Subject: below --
2002-12-01 16:00 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
2002-12-03 1:19 ` GrandMasterLee
2002-12-13 0:31 ` Herman Oosthuysen
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=200301051004.h05A4bxs000499@darkstar.example.net \
--to=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tmolina@copper.net \
--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
Powered by JetHome