That is strange. What I can suggest is that you check the output of dmesg, both after rebooting and after resetting alsa. Check if there is anything different when loading the snd-hda-intel module. Also, check if there is a duplicate module somewhere under /usr/lib/modules. It was simpler before the ubuntu developers removed slocate in hardy, all you needed to do was "locate snd-hda-intel", right now you need to do a find or something similar. Finally, check if there is another "option snd-hda-intel ..." entry either in /etc/modprobe.d/alsa-base or another file in /etc/modprobe.d - do "grep snd-hda-intel /etc/modprobe.d" and make sure the only output is the line you added to alsa-base.
-- alsamixer broken in hardy - intel hda https://bugs.launchpad.net/bugs/192382 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
