Description of problem: $title How reproducible: Every time Steps to Reproduce: 1. Start alsamixer 2. unmute master mono 3. Reboot 4. Start alsamixer Actual results: Master Mono item is muted again Expected results: Master Mono item is unmuted and audio level is same as set before Additional info: Advanced Linux Sound Architecture Driver Version k3.14.5-200.fc20.i686. Machine: Dell Latitude X1 [piret@pirrux1 ~]$ cat /proc/asound/card0/codec97#0/ac97#0-0 0-0/0: SigmaTel STAC9752,53 PCI Subsys Vendor: 0x1028 PCI Subsys Device: 0x01a3 Flags: 0 Revision : 0x02 Compat. Class : 0x12 Subsys. Vendor ID: 0xffff Subsys. ID : 0xffff Capabilities : -headphone out- DAC resolution : 20-bit ADC resolution : 20-bit 3D enhancement : SigmaTel 3D Enhancement Current setup Mic gain : +20dB [+20dB] POP path : post 3D Sim. stereo : off 3D enhancement : off Loudness : off Mono output : MIX Mic select : Mic1 ADC/DAC loopback : off Extended ID : codec=0 rev=2 AMAP DSA=0 VRA Extended status : VRA PCM front DAC : 44100Hz PCM ADC : 44100Hz Gain Inverted Buffer delay Location Master Out : 0.0 dBV - 0/fs Rear I/O Panel AUX Out : 0.0 dBV - 0/fs Rear I/O Panel Mic 1 : 0.0 dBV - 0/fs Rear I/O Panel Mic 2 : 0.0 dBV - 0/fs Rear I/O Panel Line In : 0.0 dBV - 0/fs Rear I/O Panel Mono Out : 0.0 dBV - 0/fs Rear I/O Panel
Similar issue is present with another machine - Dell Latitude D610 which has STAC9750,51 card. From Linux kernel: sound/pci/ac97/ac97_codec.c: [snip] { 0x83847650, 0xffffffff, "STAC9750,51", NULL, NULL }, // patch? { 0x83847652, 0xffffffff, "STAC9752,53", NULL, NULL }, // patch? [/snip]
Created attachment 909703 [details] pactl-list-d610.txt Output of `pactl list` on Dell Latitude D610
Created attachment 909716 [details] alsa-info-d610-after-reboot.txt Output from alsa-info.sh just after reboot (when channels are muted by default)
Similar issue from Ubuntu: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/792098
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.17.2-200.fc20. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21. If you experience different issues, please open a new bug report for those.
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.