From alsa-user-owner@alsa.jcu.cz  Sat Oct 24 09:15:39 1998
Received: from lbscissors.kek.jp (root@lbscissors.kek.jp [130.87.218.173])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id JAA03981
	for <alsa-user@jcu.cz>; Sat, 24 Oct 1998 09:15:33 +0200
Received: from lbscissors.kek.jp (really [127.0.0.1]) by lbscissors.kek.jp
	via in.smtpd with esmtp (ident sharkey using rfc1413)
	id <m0zWy7R-0016jXC@lbscissors.kek.jp> (Debian Smail3.2.0.101)
	for <alsa-user@jcu.cz>; Sat, 24 Oct 1998 16:28:13 +0900 (JST) 
Message-Id: <m0zWy7R-0016jXC@lbscissors.kek.jp>
To: alsa-user@jcu.cz
cc: rob@Netcentral.net
From: sharkey@ale.physics.sunysb.edu
Subject: Re: ALSA and Audiopci problems 
In-reply-to: Your message of "Fri, 23 Oct 1998 21:44:14 EST."
             <Pine.LNX.3.96.981023214215.22052C-100000@ns1.netcentral.net> 
Date: Sat, 24 Oct 1998 16:28:03 +0900
Reply-To: alsa-user@alsa.jcu.cz
Sender: alsa-user-owner@alsa.jcu.cz
Precedence: list

> I now have ALSA starting up in rc.local (dual-boot, so I'm rebooting at
> least every couple of days), but when it starts up everything is muted and
> I have to run alsamixer before I can use anything.  Is there a way to
> specify volumes and unmutedness for devices when I first load ALSA?

Read the FAQ:

Q: How can I store and restore mixer settings?
A: Use some native mixer program (for example amixer) or you can do simply
   'cat /proc/sound/#/mixer0 > file' where # is soundcard number. To restore
   use opposite way 'cat file > /proc/sound/#/mixer0'.

Eric

