From alsa-user-owner@alsa.jcu.cz  Thu Dec  3 17:05:07 1998
Received: from capitanata (root@capitanata.ca.astro.it [192.167.8.254])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id QAA19119
	for <alsa-user@alsa.jcu.cz>; Thu, 3 Dec 1998 16:59:32 +0100
Received: from localhost by capitanata.ca.astro.it
	via sendmail with smtp
	id <m0zlb4D-000FjhC@capitanata> (Debian Smail3.2.0.102)
	for <alsa-user@alsa.jcu.cz>; Thu, 3 Dec 1998 16:53:21 +0100 (CET) 
Date: Thu, 3 Dec 1998 16:53:21 +0100 (CET)
From: Giacomo Mulas <gmulas@ca.astro.it>
To: Jaroslav Kysela <perex@jcu.cz>
cc: alsa-user@alsa.jcu.cz
Subject: Re: was: help needed: Audio Devices: NOT ENABLED IN CONFIG
In-Reply-To: <Pine.LNX.3.96.981203150112.26107F-100000@entry.jcu.cz>
Message-ID: <Pine.LNX.3.96.981203163114.3551B-100000@capitanata.ca.astro.it>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: alsa-user@alsa.jcu.cz
Sender: alsa-user-owner@alsa.jcu.cz
Precedence: list

On Thu, 3 Dec 1998, Jaroslav Kysela wrote:

> You probably don't have actual alsa-lib binaries in your system compiled
> with latest alsa-driver header. I don't know why, but people doesn't do
> make install for alsa-driver, alsa-lib and alsa-utils in right order.

I trusted the (binary) debian package I installed. Taking the alsa sources
from your "official" site, compiling them and installing them fixed this.
Thank you. I will send an email to the debian package maintainer
so that this can be fixed for good.

> The questions what must be reset after system wakeup? I think that your
> trouble are caused by wrong wakeup code or hardware (driver doesn't have
> after wakeup hardware in same state before hibernation).

This is likely. Anyway, the pnp settings are correct, after wakeup, or it
would not be possible to simply restart alsa without resetting these
settings first, so it must be something else. What is it? What should I do
to discover that? How can I dump the state of the OPL-SA3, so that I can
test it before hibernation and after wakeup and check any differences?

However, the apmd daemon that handles apm features in Linux can execute
some "pre-suspend" and "post-resume" scripts. They are mostly used to
manage pcmcia peripherals that don't work well with suspend-resume. Such
cards can therefore be "soft-ejected" before hibernation and then
"soft-inserted" again upon wakeup. A similar trick would perhaps also get
alsa working. I will try and have a look at the docs, and if I can get it
to work I will send you patches and/or workarounds.

Bye
Giacomo

______________________________________________________________________

Giacomo Mulas <gmulas@ca.astro.it, gmulas@flashnet.it, gmulas@eso.org>
______________________________________________________________________

OSSERVATORIO  ASTRONOMICO                                                
Str. 54, Loc. Poggio dei Pini * 09012 Capoterra (CA)

Tel.: +39 070 71180 216     Fax : +39 070 71180 222
______________________________________________________________________

"Outside of a dog, a book is a man's best friend
 Inside of a dog, it's too dark to read..."
              (Groucho Marx)
______________________________________________________________________


