|
Home > Archive > Debian Developers > March 2004 > Bug#240125: The new broken world of 2.6, ALSA, and hotplug.
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Bug#240125: The new broken world of 2.6, ALSA, and hotplug.
|
|
| Marco d'Itri 2004-03-31, 5:33 am |
| On Mar 31, Scott Robinson <scott@tranzoa.com> wrote:
> Assuming hotplug doesn't load the OSS drivers first (#238694), it goes ahead
Yes, in a future release the default configuration will blacklist all OSS
drivers and frame buffer devices, just to be sure.
(Unless somebody can come up with a better solution...)
> and loads all the appropriate ALSA drivers... but misses OSS emulation.
This is the result of traditionally using a stupid init script instead
of the generic system mechanisms for loading modules.
I had to add to /usr/share/doc/udev/README.Debian:
ALSA OSS devices
~~~~~~~~~~~~~~~~
You need to add something like this in /etc/modprobe.d/ to make modprobe
automatically load the OSS compatibility module.
(snd-mixer-oss is loaded anyway, does anybody know why?)
install snd-pcm /sbin/modprobe --ignore-install snd-pcm && /sbin/modprobe snd-pcm-oss
> #2) ALSA's init script is executed after hotplug. The mixer settings are
> then "restored."
Same issue: a init script is the wrong place to restore the mixer
settings. Two correct places are /etc/modprobe.d/ or a script in
/etc/dev.d/.
> Sounds like a hotplug problem, right? Well, not according to the package's
> maintainer. udev is the solution!
udev is the solution if you have more than one sound card and do not
like the order in which they get assigned to the /dev/ nodes (which IIRC
is the order in which they appear on the PCI bus).
I welcome the opinion of the ALSA packages maintainers about these
issues...
--
ciao, |
Marco | [5456 raakoPsAphOEA]
|
|
|
|
|