From: Roger Gammans <roger@computer-surgery.co.uk>
To: Jurgen Kramer <gtm.kramer@inter.nl.net>
Cc: Muli Ben-Yehuda <mulix@actcom.co.il>, linux-kernel@vger.kernel.org
Subject: Re: sound choking with trident driver (SiS 7018)
Date: Fri, 16 Aug 2002 12:25:47 +0100 [thread overview]
Message-ID: <20020816122547.A5843@computer-surgery.co.uk> (raw)
In-Reply-To: <1029495244.1294.2.camel@paragon.slim>; from gtm.kramer@inter.nl.net on Fri, Aug 16, 2002 at 12:54:03PM +0200
[-- Attachment #1: Type: text/plain, Size: 1040 bytes --]
On Fri, Aug 16, 2002 at 12:54:03PM +0200, Jurgen Kramer wrote:
> I have just tried the driver from 2.4.20pre2. No change in behavior. The
> sound still chokes every few seconds. Any ideas what might cause this
> problem? It doesn't have to be the sound driver.
>
> I will give 2.5 another go.
Hmm.
I've seen this behavour on windwows as well. (I don't have any
linux desktops with the chipset atm. Servers yes - but we don't
normally install sound drivers on severs ;-)).
The machines I see this on are Athlon 1600XP with SIS5513 chipset
and an AMI bios.
Over in 'dozeland the problem was fixed by turning IDE DMA off, I
had characterised the problem as being due to I/o bandwidth
starvation, possibly due to a poorly set up DMAC. But given it
was doze I couldn't really investigate.
Phaps 2.5 IDE changes are more relavant.
Does information this help? ;-).
--
Roger.
Master of Peng Shui. (Ancient oriental art of Penguin Arranging)
GPG Key FPR: CFF1 F383 F854 4E6A 918D 5CFF A90D E73B 88DE 0B3E
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2002-08-16 11:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-15 11:11 sound choking with trident driver (SiS 7018) Jurgen Kramer
2002-08-15 12:16 ` Muli Ben-Yehuda
2002-08-16 10:54 ` Jurgen Kramer
2002-08-16 11:25 ` Roger Gammans [this message]
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=20020816122547.A5843@computer-surgery.co.uk \
--to=roger@computer-surgery.co.uk \
--cc=gtm.kramer@inter.nl.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mulix@actcom.co.il \
/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.