Public bug reported:
I've been having trouble for days with my audio not working. I couldn't
figure it out: I completely stopped GDM, and used aplay from a command
line to try to play directly to my alsa device. I knew from alsamixer
that all my volumes were up and nothing was muted. I knew because alsa
wasn't playing anything directly that it wasn't a pulseaudio issue.
Today I realized that when I opened my lid (the laptop, an HP 8530w,
normally lives in a dock) the audio mute button was red (which indicates
mute, as opposed to blue which means not-mute). I found bug 456769,
which has led me to the conclusion that this button is indicating the
audio controller's power state. To make this better, pressing the button
seems to power up the controller. Yay! I can hear sound! ... for about
10 seconds until the thing goes into power save again.
There is some interesting behavior here I'm observing:
- I can hear the expected "pop" sound when the sound controller powers down.
- I *sometimes* hear a "pop" when I manually power up the device again by
pressing the physical mute button.
- The physical mute button color doesn't always change immediately to reflect
the change in power state (I hear a pop, button remains blue for a while), but
if I try to play something while I know the sound to be powered down (because I
heard the "pop" with no subsequent "pop" to indicate powering back on) then the
color will immediately change to red. No sound plays.
- The button color is changing between red and blue at irregular intervals that
to not seem related to when I am playing sound.
- So far I have successfully played a sound after the initial power down of the
device until I manually unmute it by pressing the physical mute button.
I have already tried two of the common recommendations for resolving
this. I have set module parameters power_save=0 and model=laptop
(appropriate for my AD1984a, according to alsa's documentation).
Strangely power_save=0 does not prevent my card from powering down. I
can still hear it popping after a brief time. I have done 'sudo alsa
force-reload' and a full reboot to test these settings. I'm baffled why
power_save=0 didn't resolve things.
This problem started sometime in the last 2 weeks I think, after or
around the time Karmic entered RC. Possibly related to updating to alsa-
driver 1.0.20+dfsg-1ubuntu5 or 1.0.20+dfsg-1ubuntu4.
ProblemType: Bug
AplayDevices:
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: amd64
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
Subdevices: 2/2
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: meyerm 3631 F.... pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xdb320000 irq 17'
Mixer name : 'Analog Devices AD1984A'
Components : 'HDA:11d4194a,103c30e7,00100400
HDA:11c11040,103c1378,00100200'
Controls : 22
Simple ctrls : 14
Date: Tue Nov 3 11:39:39 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: alsa-base 1.0.20+dfsg-1ubuntu5
PackageArchitecture: all
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: alsa-driver
Uname: Linux 2.6.31-14-generic x86_64
XsessionErrors:
(gnome-settings-daemon:2486): GLib-CRITICAL **: g_propagate_error: assertion
`src != NULL' failed
(gnome-settings-daemon:2486): GLib-CRITICAL **: g_propagate_error: assertion
`src != NULL' failed
(polkit-gnome-authentication-agent-1:2588): GLib-CRITICAL **:
g_once_init_leave: assertion `initialization_value != 0' failed
(nautilus:2577): Eel-CRITICAL **: eel_preferences_get_boolean: assertion
`preferences_is_initialized ()' failed
(gnome-panel:2576): Gdk-WARNING **:
/build/buildd/gtk+2.0-2.18.3/gdk/x11/gdkdrawable-x11.c:952 drawable is not a
pixmap or window
** Affects: alsa-driver (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug
--
AD1984a enters power save and never wakes up
https://bugs.launchpad.net/bugs/473000
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
