From alsa-user-owner@alsa.jcu.cz  Tue Jan  5 04:17:47 1999
Received: from executioner.lis.net.au (mail@executioner.lis.net.au [203.35.83.3])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id EAA13327
	for <alsa-user@alsa.jcu.cz>; Tue, 5 Jan 1999 04:14:53 +0100
Received: from uucp by executioner.lis.net.au with local-rmail (Exim 2.05 #4)
	id 0zxMxF-0001wg-00 (Debian); Tue, 5 Jan 1999 14:14:49 +1100
Received: from kerry by gotss1.gotss.ml.org with local (Exim 1.92 #1)
	id 0zxMws-0002bK-00 (Debian); Tue, 5 Jan 1999 14:14:26 +1100
Message-ID: <19990105141426.A9981@gotss.ml.org>
Date: Tue, 5 Jan 1999 14:14:26 +1100
From: Kerry Hoath <kerry@gotss.ml.org>
To: alsa-user@alsa.jcu.cz
Subject: Re: ALSA and GUS MAX, on kernel 2.0.34 / Debian 2.0
References: <XFMail.990104174806.scode_ufp@usa.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <XFMail.990104174806.scode_ufp@usa.net>; from Peter Schuller on Mon, Jan 04, 1999 at 05:48:06PM +0100
Reply-To: alsa-user@alsa.jcu.cz
Sender: alsa-user-owner@alsa.jcu.cz
Precedence: list

This is an interesting situation, I am running Debian 2.0 and my 2 gusmax
cards operate flawlessly. Was the /proc/interrupts snapshot taken after you
had played sounds? It's a longshot but I noticed that the interrupt count
on IRQ5 was zero. Does this count increase when you play sound? My first
hunch is if the sound loops it is an interrupt conflict. I know I had to
go into the CMOS setup, PCI/Plug 'n' play, set resources assigned by manual
and set IRQ5 (the one that has the gusmax on it) to Legacy ISA.

If aplay isn't working, then you definitely have problems. For reference my
driversion is:
Advanced Linux Sound Architecture Driver Version 0.2.0-pre10p2.
Compiled in Dec 17 1998 for kernel 2.0.36.

I hope you get it working, it works just fine for me.
On Mon, Jan 04, 1999 at 05:48:06PM +0100, Peter Schuller wrote:
> Hi!
> 
> I've actually posted a question about this in the past, but I've got some more
> stuff to say now, and maybe more people are subscribed now, so the chances of
> someone knowing what's wrong is hopefully a bit higher :)
> 
> ALSA used to work fine on my old Linux install (kernel 2.0.30 + teardrop path.
> Dist. was RH 4.0). After I installed Debian 2.0, which uses kernel 2.0.34, I'm
> having problems. Basically, nothing works except Quake 2. Yes, that's right; a
> game is the only thing that works :)
> 
> When using apps like wine, xanim, mtvp, aplay, mpg123, splay, mikmod, I always
> have the same problem: the application can play the first second or so (how
> long varies a little), and then the sound "restarts", as if it was a broken
> record. 
> 
> AFAIK, there is no hardware conflict. I'm using the same interrupts and such as
> before, and I never had any problems then. Here's /proc/interrupts:
> 
> 0:   42134055   timer
>  1:     513544   keyboard
>  2:          0   cascade
>  4:    2323033 + serial
>  5:          0 + GUS MAX
> 11:    1026318   eepro
> 12:       7600   aic7xxx
> 13:          1   math error
> 14:    9024650 + ide0
> 15:     364928 + ide1        
> 
> 
> and here's /proc/dma:
> 
>  4: cascade
>  5: GF1/CS4231 record
>  6: CS4231 playback 
> 
> Currenly, the only way I can play a .wav file, is by using the "play" command
> in Quake 2, hehe :)
> 
> Does anyone have a clue as to what might be wrong? I'm using the latest
> version of alsa, but I've tried at least 3 I think, all of them "new" ones.
> 
> And what's Quake 2 doing different from all other apps? They're all using
> /dev/dsp AFAIK, with the possible exception of aplay.
> 
> And btw, Quake 2 doesn't work flawlessly either. Sometimes I get the same
> phenomenon in Q2 - every sound suddenly starts "echoing" or "jerking", and I
> have to restart it for it to go back to normal.
> 
> Thanks!
> 
> / Peter Schuller
> ----------------
> E-Mail: scode_ufp@usa.net
> Web: http://hem.passagen.se/petersch
> 
> ------
> 

-- 
--
Kerry Hoath:
kerry@gotss.ml.org or khoath@lis.net.au
ICQ UIN: 8226547


