From alsa-user-owner@alsa.jcu.cz  Thu Jan 14 21:07:02 1999
Received: from friedrich.schiller.big.ac.at (friedrich.schiller.big.ac.at [193.170.224.66])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id VAA04909
	for <alsa-user@alsa.jcu.cz>; Thu, 14 Jan 1999 21:01:30 +0100
Received: from schiller.big.ac.at (Administratoren@localhost)
	by friedrich.schiller.big.ac.at (8.8.8/8.8.7) with ESMTP id VAA00339
	for <alsa-user@alsa.jcu.cz>; Thu, 14 Jan 1999 21:10:44 +0100 (Westeuropische Sommerzeit)
Message-ID: <369E4D2A.715E8DFF@schiller.big.ac.at>
Date: Thu, 14 Jan 1999 21:01:46 +0100
From: Michael Guntsche <fprefect@schiller.big.ac.at>
MIME-Version: 1.0
To: alsa-user@alsa.jcu.cz
Subject: Autoloading modules
References: <369DE52A.DAC9D026@adsl-145-99-70-68.snelnet.nl>
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

Hello LIST

Well, I noticed a strange behaviour in the module autoloading process.
Im using a devel kernel 132 to be exact and put all the necessary lines
in the conf.modules file.
Now the problem.
If I start a native alsa application, like amixer, aplay, or mpg123 with
alsa-support it doesnt load the modules. If i start an OSS application
like x11amp or a kmix, the modules get loaded.
If i start gqmpeg which is a GTK frontend for mpg123 the modules get
loaded too. I think it doest it, because it has a volumebar, and so
calls /dev/mixer on startup.
Anyone knows why this is happening???


Cheers,
Mike


-- 
---------------------------
Marked for deletion
Michael Guntsche
fprefect@schiller.big.ac.at
---------------------------

