public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jurgen Kramer <gtm.kramer@inter.nl.net>
To: Muli Ben-Yehuda <mulix@actcom.co.il>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sound choking with trident driver (SiS 7018)
Date: 16 Aug 2002 12:54:03 +0200	[thread overview]
Message-ID: <1029495244.1294.2.camel@paragon.slim> (raw)
In-Reply-To: <20020815121602.GI6772@alhambra.actcom.co.il>

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. 


On Thu, 2002-08-15 at 14:16, Muli Ben-Yehuda wrote:
    On Thu, Aug 15, 2002 at 01:11:49PM +0200, Jurgen Kramer wrote:
    > Hi,
    > 
    > I have a laptop with a SiS 7018 soundchip. While playing music
    > the sound chokes every few seconds (2.4.19 kernel). I am not sure where
    > the problem lies. With the ALSA drivers under kernel 2.5 the problem is
    > not there.
    > 
    > Is there a newer driver for the SiS 7018 (trident.c). The current driver
    > in 2.4 is dated October 2001.
    
    the -ac tree and 2.4.20-pre1 and onwards (as well as 2.5) contain an
    updated trident.c driver. I don't see anything there that is obviously
    related to your problems, but you might wish to give the updated
    driver a try anyway.  
    
    Thanks and please let us know how it goes, 
    -- 
    "Hmm.. Cache shrink failed - time to kill something?
     Mhwahahhaha! This is the part I really like. Giggle."
    					 -- linux/mm/vmscan.c
    http://vipe.technion.ac.il/~mulix/	http://syscalltrack.sf.net
    
    


  reply	other threads:[~2002-08-16 10:45 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 [this message]
2002-08-16 11:25     ` Roger Gammans

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=1029495244.1294.2.camel@paragon.slim \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox