From alsa-user-owner@alsa.jcu.cz  Tue Sep 15 21:51:55 1998
Received: from smtp3.erols.com (smtp3.erols.com [207.172.3.236])
	by marvin.jcu.cz (8.8.8/8.8.8) with ESMTP id VAA10235
	for <alsa-user@alsa.jcu.cz>; Tue, 15 Sep 1998 21:50:02 +0200
Received: from oemcomputer (207-172-126-72.s9.as9.nyb.erols.com [207.172.126.72])
	by smtp3.erols.com (8.8.8/8.8.5) with SMTP id PAA20059
	for <alsa-user@alsa.jcu.cz>; Tue, 15 Sep 1998 15:50:00 -0400 (EDT)
Message-ID: <35FEC481.74CC@erols.com>
Date: Tue, 15 Sep 1998 15:48:17 -0400
From: Paul Winkler <zarmzarm@erols.com>
MIME-Version: 1.0
To: alsa-user@alsa.jcu.cz
Subject: ALSA & OSS-Linux on the same machine?
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

While I'm fussing around trying to get ALSA to work, I'd like to still
be able to use OSS-Linux, which I already have working reasonably well.
(Besides, ALSA doesn't have much midi support yet anyway!)  

But since I installed ALSA, even if ALSA isn't loaded, I can't start
OSS. The usual routine is to run a shell script called 'soundon' as
root. But now doing that gives this message:

[root@localhost utils]# soundon
snd                7            0 (autoclean)
vfat               4            1 (autoclean)
fat                6    [vfat]  1 (autoclean)
nls                1    [vfat fat]      0 (autoclean)
Error: Sound driver appears to be already loaded or
compiled in the kernel. Please unload the old driver
or install a kernel without the built in sound driver.

What's peculiar is that the snd module IS NOT loaded prior to running
soundon. If I do 'rmmod snd', 'lsmod' (just to check), and then
'soundon' again, the same thing happens.

And no, there is NOT sound compiled in to the kernel... 
Somehow, the OSS soundon script must be causing the ALSA snd.o module
to load, and then soundon complains that it's loaded !?!?! I've had a
look at the soundon script, and I don't know why it would do
that. (But then I don't read shell scripts very well.)

Has anyone had any luck with OSS/Linux and ALSA co-existing on the
same system? Did  you have to do anything in particular to get it to
work?

If this is not just a problem with my setup, I'd like to see it
addressed. I doubt 4front will help out their competition, so we may
have to find a workaround ourselves.  After all, isn't the whole point
that users should be able to use whatever driver they want, whenever
they want?

One possible fix that would probably be a pain in the ass:
Is there any reason the snd.o module needs to be
named snd.o? Why not e.g. alsasnd.o or sound.o or anything else?

Thanks,

PW

