From alsa-user-owner@alsa.jcu.cz  Sat Oct 24 15:51:40 1998
Received: from krusty.eaglequest.com (krusty.eaglequest.com [209.57.56.20])
	by marvin.jcu.cz (8.9.1a/8.9.1) with SMTP id PAA31807
	for <alsa-user@jcu.cz>; Sat, 24 Oct 1998 15:50:21 +0200
Received: (qmail 26961 invoked from network); 24 Oct 1998 13:50:13 -0000
Received: from user-38.pm3-1.ppp.eaglequest.com (HELO eaglequest.com) (209.57.61.87)
  by krusty.eaglequest.com with SMTP; 24 Oct 1998 13:50:13 -0000
Message-ID: <3631DD3F.20C56D94@eaglequest.com>
Date: Sat, 24 Oct 1998 13:59:27 +0000
From: "Jay T. Millar" <jmillar@eaglequest.com>
MIME-Version: 1.0
To: alsa-user@jcu.cz
Subject: Re: ALSA's last chance ...
References: <7169fb0e.36312adc@aol.com> <36313ED8.E85A8AA8@isoc.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: alsa-user@alsa.jcu.cz
Sender: alsa-user-owner@alsa.jcu.cz
Precedence: list

"Richard J. Westcott, III" wrote:

> Hello, all:
>
> I've joined this list in a last ditch effort to get the ALSA working properly. I
> have a SB AWE64 and I have the ALSA loaded and I can make sound. The sound I get,
> though, is flat, over modulated and distorted.

I have a SB AWE64 as well.  I use a fairly recent version of ALSA (0.2.0-pre5), and
get great sound.

> Although I have an AWE64, when I do a modprobe snd-sbawe I get an error that the
> device is busy. I can, however, do a modprobe snd-sb16 and get sound with the
> above problems.

I couldn't get the AWE module of ALSA to load either (I get the message 'unresolved
symbol snd_emu8000_new_device' when I attempt to load it).  In any case, I have to
revert to the SB16 module to get sound too.

> I do have isapnp tools and I use them to detect & load the correct settings for
> my sound card and I followed all the instructions in the INSTALL file.

I use the isapnp tools as well to setup the PnP settings for my card.

> Here is some information about my setup:
>
> Pentium II 300
> Redhat Linux 5.1
> custom 2.0.35 kernel (compiled w/o sound)
> SB AWE64

My setup is:

AMD K6-2 300
RedHat Linux 5.0
custom 2.0.35 kernel (patched for UDMA support w/o sound)
SB AWE64

> I do own a copy of OSS with midi support which works great, but I'd much rather
> use ALSA because it integrates so much better with the Linux kernel then OSS
> (i.e.: /proc support).

I don't own a copy of OSS, and the Lite version of it included with the kernel just
plain stinks........so I went with ALSA.  Works beautifully.  The only things I can
think of that may be different between our setups are mixer settings, speaker
hardware, ALSA version, and possibly the version of our AWE64 cards.  I bought my
AWE64 fairly soon after it first hit the market.

My mixer settings are:

Master          100% (  0.00dB) : 100% (  0.00dB)
Bass            84 % ( 10.00dB) : 84 % ( 10.00dB)
Treble          84 % ( 10.00dB) : 84 % ( 10.00dB)
Synth           84 % (-10.00dB) : 84 % (-10.00dB)
PCM             82 % (-12.00dB) : 82 % (-12.00dB)
Line-In         0  % (-62.00dB) : 0  % (-62.00dB) Mute
MIC             0  % (-62.00dB) : 0  % (-62.00dB) Mute
CD              96 % ( -2.00dB) : 96 % ( -2.00dB)
In-Gain         0  % (-18.00dB) : 0  % (-18.00dB)
Out-Gain        0  % (-18.00dB) : 0  % (-18.00dB)
PC Speaker      0  % (-18.00dB) : 0  % (-18.00dB)

I pipe the output through the Line-In of a Sony boombox that I have.  I'm using ALSA
0.2.0-pre5.   Via isapnp, my SB AWE64 is reported as:

# Card 1: (serial identifier bf 01 0c c9 10 9d 00 8c 0e)
# Vendor Id CTL009d, Serial Number 17615120, checksum 0xBF.
# Version 1.0, Vendor version 2.0
# ANSI string -->Creative SB AWE64 PnP<--

Does anyone else have any suggestions or other points of concern to add here?

> Any help will be appreciated.
>
> rjwiii


