[Bug 624896] New: Speakers popping when using battery power due to power_save parameter of snd_hda_intel driver not being set to zero. using option snd-hda-intel power_save=0 in /etc/modprobe.d/50-sound.conf not setting power_save to zero as expected.

newer
[Bug 604924] New: M-Audio Delta...

older
[Bug 709942] New: Microphone input...

bugzilla_noreply＠novell.com

22 Jul 2010 22 Jul '10

22:22

http://bugzilla.novell.com/show_bug.cgi?id=624896 http://bugzilla.novell.com/show_bug.cgi?id=624896#c0 Summary: Speakers popping when using battery power due to power_save parameter of snd_hda_intel driver not being set to zero. using option snd-hda-intel power_save=0 in /etc/modprobe.d/50-sound.conf not setting power_save to zero as expected. Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: i686 OS/Version: openSUSE 11.2 Status: NEW Severity: Minor Priority: P5 - None Component: Sound AssignedTo: tiwai@novell.com ReportedBy: super.attractive.monkey@gmail.com QAContact: qa@suse.de Found By: --- Blocker: --- Created an attachment (id=377894) --> (http://bugzilla.novell.com/attachment.cgi?id=377894) Output from /usr/sbin/alsa-info.sh --no-upload User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.10) Gecko/20100506 SUSE/3.5.10-0.1.1 Firefox/3.5.10 The issue is power_save=0 should be set to zero and the standard way to set it is not working. The speakers consistently pop when running my laptop from battery power. This is due to them constantly powering down and having to power back up to play any sound (popping occurs when speakers power back up). The cause of the speakers powering down is the power_save parameter in the intel sound driver (/sys/module/snd_hda_intel/parameters/power_save) which is set to 10 seconds by default. According to http://wiki.archlinux.org/index.php/Advanced_Linux_Sound_Architecture (search for power_save) setting power_save to 0 eliminates the popping issue since the speakers will not power down. However, using the option snd-hda-intel power_save=0 line in /etc/modprobe.d/50-sound.conf does not initially work as expected. options snd slots=snd-hda-intel options snd-hda-intel power_save=0 # u1Nb.Xr0+ey1p7G5:82801G (ICH7 Family) High Definition Audio Controller alias snd-card-0 snd-hda-intel By initially, I mean that when the system boots the power_save option is still set to 10. But if I restart the alsasound service (/etc/init.d/alsasound restart) the power_save=0 option does kick in. So my workaround was to add a startup script after the alsasound service starts that just runs /etc/init.d/alsasound restart. This does set power_save to zero and does eliminate the popping (except for an initial pop on startup when the speakers turn on). I don't think restarting the sound service is a good solution. You can also use modprobe snd-hda-intel power_save=0 as the site I mentioned suggests but I don't know where or when to use it in this case. Attached is the output from /usr/sbin/alsa-info.sh --no-upload Thanks, Sam Reproducible: Always Steps to Reproduce: 1. Run my laptop on battery power with snd-hda-intel power_save parameter set to anything other than 0 and any playback will have an initial pop as speakers power up 2. Using options snd-hda-intel power_save=0 in /etc/modprobe.d/50-sound.conf not setting power_save to zero as expected 3. Restarting alsasound service does set power_save to zero and does resolve popping issue but is an ugly workaround -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Show replies by date

bugzilla_noreply＠novell.com

23 Jul 23 Jul

09:46

New subject: [Bug 624896] Speakers popping when using battery power due to power_save parameter of snd_hda_intel driver not being set to zero. using option snd-hda-intel power_save=0 in /etc/modprobe.d/50-sound.conf not setting power_save to zero as expected.

http://bugzilla.novell.com/show_bug.cgi?id=624896 http://bugzilla.novell.com/show_bug.cgi?id=624896#c1 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |super.attractive.monkey@gma | |il.com --- Comment #1 from Takashi Iwai 2010-07-23 09:46:04 UTC --- Wow, this is the longest bugzilla subject I've seen over 10 years :) Try alsa-driver-kmp package on OBS multimedia:audio:KMP repo. This provides the very latest alsa-driver, and most of click issues should have been fixed. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

22:00

http://bugzilla.novell.com/show_bug.cgi?id=624896 http://bugzilla.novell.com/show_bug.cgi?id=624896#c2 --- Comment #2 from Sam Simmons 2010-07-23 22:00:51 UTC --- (In reply to comment #1)

...

Wow, this is the longest bugzilla subject I've seen over 10 years :)

Try alsa-driver-kmp package on OBS multimedia:audio:KMP repo. This provides the very latest alsa-driver, and most of click issues should have been fixed.

Ok, I'll use smaller subjects in the future. I upgraded to alsa-driver-kmp-default-1.0.23.20100723_2.6.31.5_0.1-1.1.i586.rpm The popping is still there after reboot and alsa-info.sh still says I'm using 1.0.21. The description (https://build.opensuse.org/package/show?package=alsa-driver-kmp&project=multimedia%3Aaudio%3AKMP) says these updates are installed in different directories from the standard. Is there anything I need to do point to the new drivers? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

24 Jul 24 Jul