From alsa-user-owner@alsa.jcu.cz  Thu Dec  3 15:08:53 1998
Received: from entry.jcu.cz (IDENT:perex@entry.jcu.cz [160.217.1.111])
	by marvin.jcu.cz (8.9.1a/8.9.1) with SMTP id PAA10941;
	Thu, 3 Dec 1998 15:06:06 +0100
Date: Thu, 3 Dec 1998 15:06:06 +0100 (CET)
From: Jaroslav Kysela <perex@jcu.cz>
To: Giacomo Mulas <gmulas@ca.astro.it>
cc: alsa-user@alsa.jcu.cz
Subject: Re: was: help needed: Audio Devices: NOT ENABLED IN CONFIG
In-Reply-To: <Pine.LNX.3.96.981203133614.868A-100000@capitanata.ca.astro.it>
Message-ID: <Pine.LNX.3.96.981203150112.26107F-100000@entry.jcu.cz>
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, Giacomo Mulas wrote:

> On Tue, 1 Dec 1998, Anders Semb Hermansen wrote:
> 
> > To get oss emulation to work you'll have to load the snd-pcm1-oss module
> > 
> > modprobe snd-pcm1-oss
> 
> Ok, that's nice to know, I had the same problem lately, after upgrading to
> 0.2.0-pre10p1. I supposed it was not a real problem, since things appeare
> to work simply fine anyway. 
> On the other hand, another thing came up that may be a real problem:
> alsactl always complains with the message: 
> "alsactl: MIXER switch read error (Device not configured) - skipping" 
> This did not happen before, and does not seem to cause problems, but what
> does it mean? I can use the mixer perfectly via alsamixer, so it does seem
> to be actually working! 

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.

> 	Last question, most important one, this definitely is a REAL
> problem:  my computer is a laptop, an AcerNote Light 370PC with a Yamaha
> OPL-SA3 embedded. When it goes in hibernation mode, saving its complete
> status (memory, registers, whatever...) on disk, upon resuming it messes
> up the alsa system. For example, if I try to play a sample with aplay it
> gets played over and over until I break it. Stopping and restarting alsa
> cures it, but it implies shutting down whatever may use sound, before,
> e.g. the sound module of Afterstep, rplayd, etc. Would it be easy to
> implement some way to reset the sound system without having to unload and
> reload the modules?  This would do the trick.  

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).

If you want do some hack (documentation is available) I'll accept
changes.. I willn't work on this (really specific) problem - sorry.

							Jaroslav

-----
Jaroslav Kysela <perex@jcu.cz>
Academic Computer Centre, University of South Bohemia
Branisovska 31, C. Budejovice, CZ-370 05 Czech Republic


