The simplest definition of the bug is that after bootup, the actual state of the emu20k2 hardware is not accurately reflected in the software (alsamixer, alsactl store). The easiest observable effect (in my case) is the PCM Capture switch - it shows off even though it's functioning as if it were on. Other differences between hardware and software may be exist, but I've not detected them (nor have I searched).
Toggling the switch on, then off, fixes the issue and syncs between hardware and software. However, using alsactl restore has no effect even if the configuration being restored contains the instructions to set the switch to off, and even if the "force" parameter is used (which is the default anyway). I wonder if alsactl compares the hardware state to the new state intended and avoids setting the switch value as an "optimization"... I'm testing your latest now, will report its effects. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1133065 Title: Default mixer settings for EMU20K2 enable PCM Input on boot while showing it as disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1133065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
