Bug#220616: discover: actually, the problem is Discover doesn't know anything about ALSA
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.
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.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (101, 'testing'), (99, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.3
Locale: LANG=fi_FI@euro, LC_CTYPE=fi_FI@euro (ignored: LC_ALL set to fi_FI@euro)
Versions of packages discover depends on:
ii dash 0.4.21 The Debian Almquist Shell
ii debconf 1.4.11 Debian configuration management sy
ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an
ii libdiscover1 1.5-2 hardware identification library
-- debconf information:
* discover/manage_cdrom_devices: false
discover/cdrom_base_mountpoint: /
discover/cdrom_base_mountpoint_error:
Reply to: