From alsa-user-owner@alsa.jcu.cz  Fri Jan  1 21:31:35 1999
Received: from post1.fast.net (post1.fast.net [198.69.204.13])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id VAA22487
	for <alsa-user@alsa.jcu.cz>; Fri, 1 Jan 1999 21:28:33 +0100
Received: from fast.net (ras01-14-phl.fast.net [204.120.86.14])
	by post1.fast.net (8.9.1/8.9.1) with ESMTP id PAA26972
	for <alsa-user@alsa.jcu.cz>; Fri, 1 Jan 1999 15:28:21 -0500 (EST)
Message-ID: <368D3037.CFAED645@fast.net>
Date: Fri, 01 Jan 1999 15:29:43 -0500
From: Rod Smith <rodsmith@fast.net>
MIME-Version: 1.0
To: alsa-user@alsa.jcu.cz
Subject: Sound goes away & unresolved symbols
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

Hi,

I've been struggling with the ALSA drivers for my GUS PnP recently. 
I've previously used the ultra drivers, which work quite well for the
most part, but they refuse to compile with the 2.2.0-pre1 kernel I'm
trying out, so I've had a go with ALSA (driver version 0.3.0-pre2, with
lib version 0.1.3 [I also tried lib version 0.3.0-pre2, but the archive
didn't have a configure script, so I was dead in the water, not
understanding enough to do without it] and utils version 0.0.8).  This
stuff all compiles and works, but I'm having some problems:

First, the drivers start up with everything muted.  This is documented,
of course, and I used the alsamixer program to un-mute things, then used
alsactl to save the settings.  Sadly, sound refuses to stay un-muted for
more than a few seconds after a sound plays.  For instance, if I use
alsactl to un-mute the sound, then do a "vplay foo.wav", the sound
plays.  If I then wait two minutes and do "vplay foo.wav" again, the
sound is muted.  I suspect that Linux is unloading the ALSA sound
modules, and that when they load again they set up the sound muted.  Is
there any way around this, ideally by having the driver automatically
load up the parameters saved by alsactl when it's loaded up?  (I'd also
accept some way to keep the driver permanently in memory.)

Second, when I start my system, I normally have it play a sound by
having appropriate lines in my /etc/rc.d/rc.local file.  This doesn't
work, even when I have a call to alsactl just before the call to vplay. 
I've no clues on this.  When I run the same commands at a bash prompt
right after I log on, it works.

Third, when I manually insert the driver module (by "insmod
snd-interwave"), I get a bunch of "unresolved symbol" messages.  The
driver seems to work, though (aside from the above problems).  Here are
the messages:

[root@fast alsa-driver-0.3.0-pre2]# insmod snd-interwave
/lib/modules/2.2.0-pre1/misc/snd-interwave.o: unresolved symbol
isapnp_deactivate_Re5bc3040
/lib/modules/2.2.0-pre1/misc/snd-interwave.o: unresolved symbol
snd_cs4231_new_device_Rcc08aa3b
/lib/modules/2.2.0-pre1/misc/snd-interwave.o: unresolved symbol
isapnp_find_logdev_Rfadc6c15
/lib/modules/2.2.0-pre1/misc/snd-interwave.o: unresolved symbol
isapnp_cfg_end_R28b715a6
/lib/modules/2.2.0-pre1/misc/snd-interwave.o: unresolved symbol
isapnp_find_device_R6c0045af
/lib/modules/2.2.0-pre1/misc/snd-interwave.o: unresolved symbol
isapnp_config_init_R29d12a76
/lib/modules/2.2.0-pre1/misc/snd-interwave.o: unresolved symbol
snd_cs4231_interrupt_R30ecbc23
/lib/modules/2.2.0-pre1/misc/snd-interwave.o: unresolved symbol
snd_cs4231_new_mixer_Ree522b30
/lib/modules/2.2.0-pre1/misc/snd-interwave.o: unresolved symbol
isapnp_cfg_begin_R770a0036
/lib/modules/2.2.0-pre1/misc/snd-interwave.o: unresolved symbol
isapnp_configure_Re4f36da9
/lib/modules/2.2.0-pre1/misc/snd-interwave.o: unresolved symbol
isapnp_activate_R2ee66b41

As an alternative to ALL of the above, does anybody know of a way to get
the older ultra drivers to compile with kernel 2.2.0-pre1?  I've tried
both 2.72a and 2.99a-devel4 with no luck.  (I've an AMD K6, and the
configure script seems to get stuck on that, but when I modify the
script to tell it I've got a 686, it seems to work, but then the compile
chokes after compiling a few files.  For instance, when I tried
2.99a-devel4, I got:

gcc -Wall -Wstrict-prototypes -m486 -malign-loops=2 -malign-jumps=2
-malign-functions=2 -O2 -fomit-frame-pointer -pipe  -DLINUX 
-I/usr/src/linux/include  -c -o gf1_synth.o gf1_synth.c
gf1_synth.c: In function `gus_synth_flush':
gf1_synth.c:294: structure has no member named `timeout'
gf1_synth.c: In function `gus_write_gf1':
gf1_synth.c:578: structure has no member named `timeout'
gf1_synth.c: In function `gus_poll_gf1':

(It went on from there with more error messages.)

As one final aside, does anybody know if sound is supposed to work for
more than a few seconds in WINE, or is there a bug preventing this in
WINE?  Whenever I try to play a sound file of more than a couple of
seconds from a WINE program, WINE crashes, when using either a 2.0.x
kernel and ultra-2.72a or a 2.2.0-pre1 kernel and the ALSA drivers
described above.  Playing the same sound with native Linux tools works
fine.  If this is a WINE bug, then fine, but if it's related to ultra
and ALSA, is there any known workaround or a fix in progress?

Thanks in advance for any help on these matters.

-- 
Rod Smith
rodsmith@fast.net
http://www.users.fast.net/~rodsmith

