Re: Alsa problems with nforce2 (Solved)

Re: Alsa problems with nforce2 (Solved)

[Lee Revell]

On Wed, 2004-09-22 at 05:23, Maarten De Boer wrote:
> > I edit /etc/discover.conf and put disable the modules of OSS and
> > Voila!!!!
> 
> Remember those words... We will probably see this problem a lot in
> the future.
> 
> To resume: discover loads the OSS drivers when "discovering" the
> sound devices. Obviously, if a user installs alsa, the logical
> thing would be to blacklist the OSS drivers in the /etc/discover.conf
> automatically. But the problem is that, Debian policy, the alsa package
> is not allowed to change the configuration of another package. So the
> user has to add the blacklist to /etc/discover.conf himself.
> 
> As for as I understand, the solution would be to change discover
> configuration from a single file to a directory, where alsa can add
> it's blacklist during installation. A similar mechanism is already
> being used with hotplug)
> 

This is a good idea.  I am copying this to alsa-devel.

I suggested doing this in the ALSA drivers, having them printk() if
someone tries to load them with the OSS driver already loaded, but it's
much better to do it in userspace with a blacklist.

Lee