public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Sorensen <lsorense@opengraphics.com>
To: brain@artax.karlin.mff.cuni.cz
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problems with OSS driver and GUS PnP card
Date: Mon, 17 Dec 2001 14:05:50 -0500	[thread overview]
Message-ID: <20011217140550.H16621@opengraphics.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0112170152450.770-100000@ghost.ucw.cz>
In-Reply-To: <Pine.LNX.4.30.0112170152450.770-100000@ghost.ucw.cz>

On Mon, Dec 17, 2001 at 02:10:28AM +0100, brain@artax.karlin.mff.cuni.cz wrote:
> Since kernel 2.2 I've got permanent problems with my Gravis Ultrasound PnP card
> and the OSS driver. The problem is following: /dev/dsp0 isn't able to
> play/record sound because of "IRQ/DMA conflict" messages. /dev/dsp1 is playing
> without problems, but it isn't able to record :-(
> 
> I have tried all possible settings of IO, IRQ and DMA. The problem persits. Can
> anybody help me? Can anybody explain me what does parameters io, irq, dma,
> dma16, gus16 and sb16 EXACTLY mean? The documentation is very poor and I'm not
> sure if it is io/irq/dma of the GF1 chip or of the "SB digital audio" (as in
> isapnp.conf). Is there any documentation on the gus driver?
> 
> Don't tell me to use Alsa. It's a piece of crap - the sound is very noisy, like
> a waterfall in background.

Hmm, I always use alsa for my GUS PnP card, since it has much better
support than the crappy old GUS driver in the kernel (and from OSS).
I don't actually use the card anymore since I got an SB Live instead,
but it used to work well.  The static hiss on the card is due to an IC
defect, and may be masked by the use of the GUS emulation, but I find
that hard to believe.  Also using the correct speed ram helps a lot
(70ns or faster).

Len Sorensen

      reply	other threads:[~2001-12-17 19:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-17  1:10 Problems with OSS driver and GUS PnP card brain
2001-12-17 19:05 ` Len Sorensen [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=20011217140550.H16621@opengraphics.com \
    --to=lsorense@opengraphics.com \
    --cc=brain@artax.karlin.mff.cuni.cz \
    --cc=linux-kernel@vger.kernel.org \
    /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