All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kumlien <pomac@vapor.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: ALSA user list <alsa-user@lists.sourceforge.net>,
	alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: [noise] The noise problem wrt Audigy 2 ZS
Date: Mon, 24 Oct 2005 11:00:51 +0200	[thread overview]
Message-ID: <1130144451.10270.22.camel@localhost> (raw)
In-Reply-To: <1130127531.16563.5.camel@mindpipe>

[-- Attachment #1: Type: text/plain, Size: 2242 bytes --]

On Mon, 2005-10-24 at 00:18 -0400, Lee Revell wrote:
> Please make sure to cc: the ALSA lists.

Yeah, i only hit reply last time, =P

> On Mon, 2005-10-24 at 02:14 +0200, Ian Kumlien wrote:
> > On Sun, 2005-10-23 at 12:27 -0400, Lee Revell wrote:
> > > On Sun, 2005-10-23 at 17:17 +0200, Ian Kumlien wrote:
> > > > Hi, 
> > > > 
> > > > I have found a bunch of topics on this now:
> > > > Squealing / Buzzing / Static noise with EMU10k1 and Audigy 2 ZS
> > > > https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1276
> > > 
> > > How are you able to access this site at all?  bugtrack.alsa-project.org
> > > has been giving me "Connection refused" for days.
> > 
> > It worked before, both from here and from a friends place... 
> > 
> > > Can you repost the text of the bug report?
> > 
> > Someone else did.
> > 
> > The interesting part of this is that it almost works for a while, if you
> > really work at it, you *can* get it to work sometimes. It feels like it
> > depends on where in the memory "things" are located, and by things i
> > mean either the kernel module or the app itself, i dunno which.
> > 
> > You can also hear more or less of the actual sound with the noise,
> > sometimes you don't hear any of it and sometimes you hear some of it.
> > 
> 
> Hmm.  You mentioned this bug only occurs on 64 bit machines or with more
> than 1GB of memory.  Maybe it can only DMA into the first 1GB of memory
> or something.  Try this patch.

Yes, that seems to work, and the comment above should apply to both
cards i think =)

(i compiled a new version of rc2 with this patch and it just started
playing fine, now contact the others =)

> --- include/sound/emu10k1.h~	2005-10-11 12:31:42.000000000 -0400
> +++ include/sound/emu10k1.h	2005-10-24 00:14:40.000000000 -0400
> @@ -48,7 +48,7 @@
>  
>  /* FIXME? - according to the OSS driver the EMU10K1 needs a 29 bit DMA mask */
>  #define EMU10K1_DMA_MASK	0x7fffffffUL	/* 31bit */
> -#define AUDIGY_DMA_MASK		0xffffffffUL	/* 32bit */
> +#define AUDIGY_DMA_MASK		0x7fffffffUL	/* 32bit */
>  
>  #define TMEMSIZE        256*1024
>  #define TMEMSIZEREG     4

-- 
Ian Kumlien <pomac () vapor ! com> -- http://pomac.netswarm.net

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2005-10-24  9:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1130080668.10270.3.camel@localhost>
     [not found] ` <1130084827.11980.12.camel@mindpipe>
     [not found]   ` <1130112868.10270.11.camel@localhost>
2005-10-24  4:18     ` [noise] The noise problem wrt Audigy 2 ZS Lee Revell
2005-10-24  9:00       ` Ian Kumlien [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=1130144451.10270.22.camel@localhost \
    --to=pomac@vapor.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=alsa-user@lists.sourceforge.net \
    --cc=rlrevell@joe-job.com \
    /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.