[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#658728: linux-image-3.2.0-1-amd64: No more sound



At Mon, 6 Feb 2012 22:53:59 -0500,
A. Costa wrote:
> 
> On Mon, 06 Feb 2012 10:21:40 +0100
> Takashi Iwai <tiwai@suse.de> wrote:
> 
> > No sound from which output exactly?
> 
> Which?  None.

"None" means almost nothing :)  Tell which outputs you have tried.
I don't know exactly whether you checked only the speaker, or only the
headphone, or any jacks what ever.  (Judging from the text, I can
guess you tested the headphone jack and the line-out jack.  But you
didn't test the surround/CLFE outputs from line-in/mic-in jacks, no?)

>  No outputs are audible, so far as I can tell.  The
> 'pavucontrol' streams still work, the meter goes up and down to the
> silent music.
> 
> On the good kernel (3.1.0-1) sound plays through the (separately
> powered) speakers plugged into the back of the PC case; when I plug the
> headphones in a different jack on the front of the case, the speakers
> turn off, and the headphone sound goes on.

Hm, so maybe the auto-mute feature is implemented in the hardware
itself?  Interesting.  The 3.1 driver doesn't provide the auto-mute in
software for your device.

> On the silent kernel (3.2.0-1), there's no sound from headphones or
> speaker, and the headphones being plugged and unplugged has no audible
> effect on either speakers or headphones.
> 
> > What happens if you turn off "Auto-Mute Mode" mixer enum?
> > 	% amixer -c0 set "Auto-Mute Mode" Disabled
> 
> On the good kernel (3.1.0-1), this happens:
> 
> 	% amixer -c0 set "Auto-Mute Mode" Disabled ; echo $?
> 	amixer: Unable to find simple control 'Auto-Mute Mode',0
> 
> 	1
> 
> Haven't tried that 'amixer' command on the silent kernel (3.2.0-1).

The question above was only for 3.2 kernel.  It wasn't enabled for 3.1
kernel for your device unless you passed model=auto explicitly.

If the above doesn't change anything, try to set the pin-control of
each pin as same as 3.1 kernel:

	hda-verb /dev/snd/hwC0D0 0x0e SET_PIN_WID 0x00
	hda-verb /dev/snd/hwC0D0 0x0d SET_PIN_WID 0x24
	hda-verb /dev/snd/hwC0D0 0x0c SET_PIN_WID 0x20
	hda-verb /dev/snd/hwC0D0 0x0b SET_PIN_WID 0x40
	hda-verb /dev/snd/hwC0D0 0x0f SET_PIN_WID 0xc0
	hda-verb /dev/snd/hwC0D0 0x10 SET_PIN_WID 0x24
	hda-verb /dev/snd/hwC0D0 0x1f SET_PIN_WID 0x00
	hda-verb /dev/snd/hwC0D0 0x20 SET_PIN_WID 0x00
	hda-verb /dev/snd/hwC0D0 0x11 SET_PIN_WID 0x20

One of the command may trigger something.  Don't change the plug while
you test this.  Also, keep "Auto-Mute" mode turned off.  Otherwise the
driver might reset the pin-control values again.

Last but not least, for testing the output, don't use PulseAudio but
use aplay or speaker-test with the raw ALSA access.
Run like
	% aplay -Dplughw -vv somefile.wav

If PA complains, use pasuspender
	% pasuspender -- aplay -Dplughw -vv somefile.wav


thanks,

Takashi



Reply to: