Comment 31 for bug 199883

On Tue, Nov 17, 2009 at 5:54 AM, Folkert <email address hidden> wrote:
> I think that the blacklist configuration has changed and that, although
> you have blacklisted saa7134_alsa, it gets loaded anyway somehow. That's
> why the workaround doesn't work anymore. Maybe an Ubuntu developer can
> confirm this/give some detailes?
>
> --
> noise at login, mixer setting problem?
> https://bugs.launchpad.net/bugs/199883
> You received this bug notification because you are a direct subscriber
> of the bug.
>

More config files:

/etc/modprobe.d/alsa-base.conf

Thes are 2 lines:

# Load saa7134-alsa instead of saa7134 (which gets dragged in by it anyway)
install saa7134 /sbin/modprobe --ignore-install saa7134 $CMDLINE_OPTS
&& { /sbin/modprobe --quiet --use-blacklist saa7134-alsa ; : ; }

And

options saa7134-alsa index=-2

So, any ideas?? Cause, I'm commenting all this lines (and also the
lines on options.conf) and I'm still getting this modules.

This is my
lsmod | grep saa

darkhole@darkhole-desktop:~$ sudo lsmod | grep saa
saa7134_alsa 12128 1
snd_pcm 75296 4
snd_via82xx,snd_ac97_codec,saa7134_alsa,snd_pcm_oss
snd 59204 18
snd_via82xx,snd_ac97_codec,snd_mpu401_uart,saa7134_alsa,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
saa7134 152616 1 saa7134_alsa
ir_common 48512 1 saa7134
v4l2_common 17500 1 saa7134
videodev 36736 2 saa7134,v4l2_common
videobuf_dma_sg 12544 2 saa7134_alsa,saa7134
videobuf_core 17952 2 saa7134,videobuf_dma_sg
tveeprom 11872 1 saa7134