[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: discover or alsa?

On Wed, 13 Oct 2004 13:43:01 +0200, Wouter Verhelst wrote:

> On Wed, Oct 13, 2004 at 10:51:46AM +0200, Marco d'Itri wrote:
>> On Oct 13, Thomas Hood <jdthood@yahoo.co.uk> wrote:
>> > Lots of users are reporting that ALSA sound doesn't "just" work when
>> > they install it.  The cause of the problem is the fact that discover
>> > loads OSS modules even when ALSA modules are available.  This bug cannot
>> > be worked around consistently with policy because discover offers no
>> > mechanism for blacklisting modules other than editing a conffile.  The
>> > bug report against discover1 (#220616) has been tagged "wontfix" so I am
>> > not expecting the discover maintainers to solve the problem.
>> Discover should not try to load drivers for PCI devices AT ALL, we have
>> hotplug for this.
> The reverse could be (and has been, on multiple occasions) said about
> hotplug.

> The issue is that there are multiple auto-detection schemes in the
> This multitude of packages doing stuff with modules is bound to break
> eachother. Perhaps it's time to create a scheme which will allow
> packages to load modules without stepping on eachother's toes? Such a
> scheme would
> * Require init scripts to ask the central module handling system
>   permission to load a module, with a description of what purpose the
>   module serves.
> * Not do anything if the central handling system forbids it.
> * Optionally keep track of what modules are loaded by what package, for
>   debugging purposes.
> * Allow packages to register themselves as the 'preferred' handler of
>   the module at postinst time (similar to the alternatives system; this
>   would solve the current issue ALSA has).
> * Give the local admin the ability to override such decisions, or to
>   disable the loading of certain modules.
> Comments?

I think this is a situation where should push a particular implementation
to standard. Just as we promote 'sysvinit' and have interoperability
scripts for things like file-rc; if people want to use it.

Once we've picked a standard one, I'm partial to hotplug myself since it
seems to work well on both 2.4 and 2.6 kernels and I've found discover
doesn't. The optional detection mechanism(s) can then come up with a
programmatic interface similar to sysv-rc.


linux.conf.au 2005   -  http://lca2005.linux.org.au/  -  Birthplace of Tux
April 18th to 23rd   -  http://lca2005.linux.org.au/  -       LINUX
Canberra, Australia  -  http://lca2005.linux.org.au/  -    Get bitten!

Reply to: