From alsa-user-owner@alsa.jcu.cz  Wed Mar 10 18:44:40 1999
Received: from brunel.swec.com (brunel.swec.com [199.103.216.36])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id SAA06854
	for <alsa-user@alsa.jcu.cz>; Wed, 10 Mar 1999 18:41:04 +0100
Received: from usa.net (bsnt3035.swec.com [111.1.20.4])
	by brunel.swec.com (8.9.1/8.9.1) with ESMTP id MAA11343
	for <alsa-user@alsa.jcu.cz>; Wed, 10 Mar 1999 12:40:32 -0500
Message-ID: <36E6AEDE.D9814CE0@usa.net>
Date: Wed, 10 Mar 1999 12:41:50 -0500
From: Glenn <dodgepond@usa.net>
MIME-Version: 1.0
To: ALSA list <alsa-user@alsa.jcu.cz>
Subject: Re: [Fwd: ALSA and new kernel/modules]
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 Ryan,

Yes, I was aware of the change to to kernel modules. I have sound and
OSS only selected as modules and no specifics for my sound card. The
problem is that after I made a new kernel, 2.2.3 for example, and copied
in the ALSA addtions to the "misc" directory, that I would get
complaints about the version that the modules were made under versus the
later kernel version, when the modules were attempting to load during
startup.

Thanks,
Glenn

Ryan Gustafson <rgg@MetaphaseTech.com>
1999-03-10 11:09:34

 For 2.2.2 and later kernels ALSA now seems to require that OSS be
compiled
into your kernel, but you don't need specify any OSS drivers.

Look at the README and INSTALL for new instructions on how to build
ALSA. I suggest doing it "from scratch", forget everything you used
to do, and follow the new instructions.

Hopefully after you get ALSA working again, you should be able to go
back
to using ALSA with multiple kernel revisions.




