bon finalement ca ne marche plus chez moi non plus depuis hier, il doit bien s'agir d'un bug (pas de trace de cette modif dans le changelog)
mais j'ai trouvé ca dans NEWS.Debian.gz:
After Woody's release, and previous to Sarge's release, the Debian ALSA
packages (specifically alsa-base) took it upon themselves to help the user
choose which modules to load at boot-time, and then did so on their behalf
via an init script, /etc/init.d/alsa. With Sarge's release, viable generic
autoloading mechanisms such as hotplug and discover are available. In this
vein, alsa-base no longer handles module loading itself and instead
facilitates the use of discover and hotplug. Briefly, the changes are:
- Modules are no longer loaded in the /etc/init.d/alsa script. Modules
should be loaded via standard mechanisms such as /etc/modules,
/etc/modprobe.d/, /etc/modutils/, discover, or hotplug.
- /etc/hotplug/blacklist.d/alsa-base has been created, which causes
hotplug to ignore OSS modules upon alsa-base's installation. It will
load ALSA modules instead, when it starts and that file is in place.
- /usr/share/doc/alsa-base/alsa-base.discover has been provided for the
user. It's a config file snippet for use with discover, which provides
much the same functionality as /etc/hotplug/blacklist.d/alsa-base.
discover doesn't provide a method for changing its configuration file
in an automated manner, however, so the user must manage this change
manually.
comme je n'utilise pas discover, j'ai ajouté dans /etc/modules:
snd-emu10k1
snd_pcm_oss
je trouve ca pas terrible, d'autant plus que alsaconf ne marche plus.
[^] # Re: chezmoicamarche
Posté par botio2 . En réponse au message problème alsa dans debian. Évalué à 1.
mais j'ai trouvé ca dans NEWS.Debian.gz:
comme je n'utilise pas discover, j'ai ajouté dans /etc/modules:
snd-emu10k1
snd_pcm_oss
je trouve ca pas terrible, d'autant plus que alsaconf ne marche plus.