From alsa-user-owner@alsa.jcu.cz  Fri Mar  5 17:05:37 1999
Received: from cerberus.ibmoto.com (cerberus.ibmoto.com [129.38.252.34])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id RAA17655;
	Fri, 5 Mar 1999 17:03:04 +0100
Received: from ibmoto.com (briscoe.ibmoto.com [129.38.251.65])
	by cerberus.ibmoto.com (8.9.0/8.9.0) with ESMTP id KAA23787;
	Fri, 5 Mar 1999 10:03:02 -0600 (CST)
Message-ID: <36E00036.C85A951C@ibmoto.com>
Date: Fri, 05 Mar 1999 10:03:02 -0600
From: Heikki Julkunen <heikki@ibmoto.com>
MIME-Version: 1.0
To: alsa-devel@alsa.jcu.cz, alsa-user@alsa.jcu.cz
Subject: Not possible to unload snd-mixer 
References: <Pine.LNX.3.96.990305192642.281B-100000@Trantor.Trnet.org>
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.

Has anyone experienced that it's not possible to
unload this module (or for that matter, the 'sound'
module included in the kernel) after stuff has gone
wrong ?

The scenario is this:
After heavy disc access, the /dev/dsp device (I'm using
a non ALSA mp3 player) goes away. 
All other modules except snd-mixer I can unload&reload
in an attempt to restart the driver (sometimes works),
but most often I get 'module in use' (or something like
that) when issuing rmmod snd-mixer.

Any ideas ?
This is my /etc/modules file:
# /etc/modules: kernel modules to load at boot time.
#
# This file should contain the names of kernel modules that are
# to be loaded at boot time, one per line.  Comments begin with
# a `#', and everything on the line after them are ignored.
# An entry named `auto' will cause the system to start kerneld immediately.
# Kerneld then loads modules on demand. `noauto' disables kerneld completely.

noauto
#slip

#Kernel sound
#sb io=0x220 irq=5 dma=1 dma16=5
#sound

#ALSA sound
snd-mixer
snd-pcm1-oss
snd-sb16
persist

Please email me if responding, I'm not frequently reading these lists.

Thanks
/ Heikki

-- 
Profanity is the one language all programmers know best.

