From alsa-user-owner@alsa.jcu.cz  Mon Dec 21 23:40:52 1998
Received: from Newman.GSC.GTE.Com (SYSTEM@Newman.GSC.GTE.Com [207.175.88.67])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id XAA13359
	for <alsa-user@alsa.jcu.cz>; Mon, 21 Dec 1998 23:38:54 +0100
Received: from gscex01.gsc.gte.com
 ("port 1554"@gscex01.ndhm.gtegsc.com [155.95.162.170])
 by Newman.GSC.GTE.Com (PMDF V5.2-27 #29038)
 with ESMTP id <01J5LWANOLT0000G2W@Newman.GSC.GTE.Com> for
 alsa-user@alsa.jcu.cz; Mon, 21 Dec 1998 17:38:36 -0400 (EDT)
Received: by gscex01.ndhm.gtegsc.com with Internet Mail Service (5.5.2232.9)
	id <Y9HXJRAP>; Mon, 21 Dec 1998 17:35:14 -0500
Date: Mon, 21 Dec 1998 17:38:03 -0500
From: "Mullen, Patrick" <Patrick.Mullen@GSC.GTE.Com>
Subject: Determining driver version
To: "'alsa-user'" <alsa-user@alsa.jcu.cz>
Message-id: <2575327B6755D211A0E100805F9FF954742F90@ndhmex02.ndhm.gtegsc.com>
MIME-version: 1.0
Content-type: text/plain;	charset="iso-8859-1"
Reply-To: alsa-user@alsa.jcu.cz
Sender: alsa-user-owner@alsa.jcu.cz
Precedence: list

Is there any way to determine what version of the alsa-driver
package you are using?  I no longer have the source code, so
I cannot use the file name, but I am trying to see if the earlier
version of alsasound, which still works when I boot into linux
kernel 2.0.35, will work for 2.0.36.

I wonder if one of my problems is the fact I upgraded from
an earlier version of alsasound which used the /proc/sound
interface to the latest (0.2.0pre10p2), which uses /proc/asound.

I have gone through all documentation that I can find, but have
not found anything that looks out of the ordinary.  I made
sure my conf.modules looked like the one in the new INSTALL
file (which mostly consisted of changing "pcm" to "pcm1".

To help track down the problem, asound works.  What device
does asound use to output sound?  I've been trekking through
the source code, but I haven't been able to determine this
correctly.  I believe it's /dev/dsp, but no other programs have
been able to open and/or use /dev/dsp.  Has this device
somehow changed?

Thanks,


~Patrick


