Bug#220616: discover: actually, the problem is Discover doesn't know anything about ALSA

[Thomas Poindessous <thomas@poindessous.com>]

On Thu, Mar 11, 2004 at 11:18:28AM +0200, Martin-Éric Racine wrote:
> Package: discover
> Version: 1.5-2
> Severity: normal
> Followup-For: Bug #220616
> 
> In my case, I use a 2.6 kernel with ALSA modules.  Discover tries to load the OSS module called es1371, which of
> course fails, since what I have is the ALSA modules ens1371.  This means that Discover's database should be able to
> use ALSA equivalents to the old OSS modules, if they exist.  Boolean OR case: OSS or ALSA modules for card XXX. 

kernel 2.6.* have OSS drivers, and discover1 can't provide boolean
logic. Discover2 will do that. With discover1, we need to have a single
data list, so, with 2.2, 2.4 and 2.6, and alsa,oss, it always will be
wrong for something. I think current discover-data is focused on 2.4
support, with oss for sound.

> Then again, having Discover detect the sound driver is the wrong approach, since alsa-utils has its own configurator
> and its own sound module loader, which is executed in the second stage (S20alsa in rc2.d to rc5.d) of the boot process. 

If you don't want discover to try loading of es1371, just add "skip
es1371" in /etc/discover.conf. But the logic is right :

* if you want to use oss driver, discover will load it for you (2.4 and
  2.6 will work in this case)
* if you want to use alsa driver, just add a skip in discover.conf and
  use alsa module loader.



-- 
Thomas Poindessous