speakers audio won't work - pavucontrol is switching continually between speakers and headphones

Bug #1316156 reported by Alessandro Ignis
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
ALSA driver
Unknown
Unknown
alsa-driver (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

The port is continually switching between Speakers and Heaphones and no audio is outputting from the speakers. I have tried various distributions and have found that this problems is NOT present in Ubuntu 11.04, 12.04, 13.04. I have not tried 11.10, or 12.10. But have found 13.10 and 14.04 to show this identical problem.
My main concern is for the 14.04 LTS version I am currently using.

- I tried regulating the audio from alsamixer -by disabling auto-mute in alsamixer i managed to stop it switching from one port to the other. Still, no audio from speakers (only a regular and low-volume BUMP comes out)
- I tried modifying the /etc/modprobe.d/alsa-base.conf file. Since i could not find my pc (Packard Bell EasyNote MX45) in the alsa-configuration list, i have tried using only the audio boards main info as referral (Intel HDA AD1986A NM10/ICH7). Thus i have added to the alsa-base.conf the following and rebooted after trying each and every new line (added only once per try, not all of them together).
                  -options snd-hda-intel model=laptop
                  -options snd-hda-intel model=laptop-eapd
                  -options snd-hda-intel model=3stack
                  -options snd-hda-intel model=generic

- Also tried the position_fix quirking suggested on the ubuntu documentation pages
                 -options snd-hda-intel position_fix= 1
                 -options snd-hda-intel position_fix= 2

The audio outputted from the speakers kept being a regular BUMP and nothing more, regardless of the input.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: pulseaudio 1:4.0-0ubuntu11
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic i686
ApportVersion: 2.14.1-0ubuntu3
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: xubuntu 3690 F.... pulseaudio
CasperVersion: 1.340
Date: Mon May 5 13:48:40 2014
LiveMediaBuild: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/11/2006
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: T12FvNC.203
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: EasyNote_MX45
dmi.board.vendor: Packard Bell BV
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: Packard Bell BV
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT12FvNC.203:bd10/11/2006:svnPackardBellBV:pnEasyNote_MX45:pvrPB64H00206:rvnPackardBellBV:rnEasyNote_MX45:rvr1.0:cvnPackardBellBV:ct10:cvr:
dmi.product.name: EasyNote_MX45
dmi.product.version: PB64H00206
dmi.sys.vendor: Packard Bell BV

Revision history for this message
Alessandro Ignis (artaeun) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in pulseaudio (Ubuntu):
status: New → Confirmed
Revision history for this message
Kristof S. (ksa1) wrote :

I am also affected by this bug, using 14.04 LTS.

Hardware:
Asus Pro52H Notebook
Sound-Chip is as described above: Intel HDA, AD1986A NM10/ICH7

The symptom is also as described above:
In the alsamixer the port is continually switching between Speakers and Headphones.
In result on the desktop you can see a constantly "blinking" volume display.

This happens just with the basic installation (auto detection), so the default installation already leads to the bug.

In can confirm that the bug is related to the auto mute feature, it only happens when auto mute is enabled. On the other hand having it disabled, I got no sound at all (though at least no blinking volume display on the screen).

Currently I am using this setting in alsa-base.conf:

options snd-hda-intel model=laptop-eapd position_fix=1

With this at least I got the headphones working and the blinking volume display does not appear any more.
As said, speaker not working, already the speaker port is said to be "not available" in the sound control.

Using that manual option last year I already had a fully working sound in an earlier release, I think it was 13.04, though I am not 100% sure.

Revision history for this message
Kristof S. (ksa1) wrote :

Is there any bugfix or workaround?
Can I install new alsa packages with included fix or something like that?
Thanks in advance!

Revision history for this message
Alessandro Ignis (artaeun) wrote :

i didn't manage to find any workaround till now. Only thing i could do is keep the 12.04 version. Cheers

Revision history for this message
Raymond (superquad-vortex2) wrote :
affects: pulseaudio (Ubuntu) → alsa-driver (Ubuntu)
Revision history for this message
Raymond (superquad-vortex2) wrote :

your system log have lots of

201.019841] iwl3945 0000:02:00.0: Radio disabled by HW RF Kill switch
[ 201.020002] iwl3945 0000:02:00.0: Radio disabled by HW RF Kill switch
[ 201.021485] iwl3945 0000:02:00.0: Radio disabled by HW RF Kill switch

Revision history for this message
Alessandro Ignis (artaeun) wrote :

I actually have a hardware switch for wifi connection, but i don't remember if at the time of the test i used LAN for connecting to the net or not. Though i am sure the bug manifested itself even when the wifi connection enabled.

Revision history for this message
Kristof S. (ksa1) wrote :

Should I post some debug output for the Asus Pro52H Notebook, too? In case that would help: Which logs do you want?

Revision history for this message
Raymond (superquad-vortex2) wrote :

https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda/patch_analog.c?id=0f7dbda0ec3bc4d778d7acf741b220fbf4318a2

you have to post output of alsa-info.sh

seem pro52h not in the above asus notebooks which use ad1986a

https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda/patch_analog.c?id=598e306184d26fa1d546334f2eb370b4d94a4ad3

post the pulseaudio verbose log and find out whether the hp jack is plugged and unplugged rapidly

try to find out the jack state is inverted or not by hda-jack-sense-test

https://bugzilla.kernel.org/show_bug.cgi?id=66621#c41

you can also try the modified version which can measure impedance since pincap supoort ImpSense

Node 0x1a [Pin Complex] wcaps 0x400185: Stereo Amp-Out
  Control: name="Headphone Playback Volume", index=0, device=0
    ControlAmp: chs=3, dir=Out, idx=0, ofs=0
  Control: name="Headphone Playback Switch", index=0, device=0
    ControlAmp: chs=3, dir=Out, idx=0, ofs=0
  Control: name="Headphone Jack", index=0, device=0
  Amp-Out caps: ofs=0x1f, nsteps=0x1f, stepsize=0x05, mute=1
  Amp-Out vals: [0x13 0x13]
  Pincap 0x0000001f: OUT HP Detect Trigger ImpSense
  Pin Default 0x0121401f: [Jack] HP Out at Ext Rear
    Conn = 1/8, Color = Green
    DefAssociation = 0x1, Sequence = 0xf
  Pin-ctls: 0xc0: OUT HP
  Unsolicited: tag=01, enabled=1
  Connection: 1
     0x0a

Revision history for this message
Kristof S. (ksa1) wrote :

All details in attached alsa-info.txt-file... (generated with alsa-info.sh)

Notebook ASUS Pro52H Series (X51H)
Kernel 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:31:42 UTC 2014 i686 i686 i686 GNU/Linux
Linux Mint 17 Qiana \n \l DISTRIB_ID=LinuxMint DISTRIB_DESCRIPTION="Linux Mint 17 Qiana" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 14.04 LTS" HOME_URL="http://www.ubuntu.com/" SUPPORT_URL="http://help.ubuntu.com/" BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"

snd_hda_intel
...
00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 02)
...
!!HDA-Intel Codec information
...
Codec: Analog Devices AD1986A
...

Revision history for this message
Kristof S. (ksa1) wrote :

...and pulse audio verbose log, too... (attached gz-file)

First automute was deactived, then I activated it - the volume bar started to freak out - and I deactivated it again. Well, it is a lot of log output and I hope the important information is easy enough to find there...

Many thanks in advance, it would be really great if that sound bug could be fixed!

Revision history for this message
Raymond (superquad-vortex2) wrote :

do pulseaudio log complain about the mic jack ?

 the model which you select set bit 8 of pin default of node 0x1f

0x1f 0x01a19020

0x1f 0x02a191f0

Sysfs Files
!!-----------

/sys/class/sound/hwC0D0/init_pin_configs:
0x1a 0x0121401f
0x1b 0x9117f110
0x1c 0x410110f0
0x1d 0x410110f0
0x1e 0x411711f0
0x1f 0x01a19020
0x20 0x418130f0
0x21 0x5993e1f0
0x22 0x5933112e
0x23 0x59b371f0
0x24 0x53f711f0
0x25 0x410110f0

/sys/class/sound/hwC0D0/driver_pin_configs:
0x1a 0x02214021
0x1b 0x90170110
0x1c 0x411111f0
0x1d 0x90a7013e
0x1e 0x411111f0
0x1f 0x02a191f0
0x20 0x411111f0

control.14 {
  iface CARD
  name 'Mic Phantom Jack'
  value true
  comment {
   access read
   type BOOLEAN
   count 1
  }
 }
 control.15 {
  iface CARD
  name 'Internal Mic Phantom Jack'
  value true
  comment {
   access read
   type BOOLEAN
   count 1
  }
 }

Revision history for this message
Raymond (superquad-vortex2) wrote :

try

hda-jack-sense-test -a

when you plugged and unplugged mic jack
to find whether your mic jack support jack detection

Revision history for this message
Kristof S. (ksa1) wrote :

Do you mean a physically connected microphone? I never used one with this Notebook...
I did not find a command/script 'hda-jack-sense-test'...

When I connect ear phones the connection is noticed by the desktop environment, so it seems there is some jack detection at least for the phones.

Revision history for this message
Raymond (superquad-vortex2) wrote :

your asus pro52 seem not set pin default of internal mic

can you post the output of alsa-info.sh when not specify any model ?

the headphone remain unplugged in your log

you have to file an upstream bug report since your case seem different from mx45

Revision history for this message
Kristof S. (ksa1) wrote :

Ok, here is alsa-info.sh >>without specified<< model, so it should be just "installation default"...

The auto mute feature is disabled, when enabled the blinking volume bar bug appears as in the already described case with specified settings (the settings that worked for me in an earlier ubuntu version).

Revision history for this message
Kristof S. (ksa1) wrote :

Oh, to answer your question to the head phone: I did not connect it during the time generating the log, sorry for that misunderstanding. I just mentioned that the head phones work and there is a reaction when plugging in, that is not included in the log though - my main problem is that the internal speakers are not working.
(head phones do work with the above manual settings, though sometimes problems occur when you plug them in or out... Did not analyze that behaviour in detail)

Revision history for this message
Raymond (superquad-vortex2) wrote :

since both easynote mx45 and easynote mx65 have same pci ssid Subsystem: 1631:c022

https://bugzilla.kernel.org/attachment.cgi?id=159851&action=diff

the patch in kernel bugzilla affect both notebook

Revision history for this message
Kristof S. (ksa1) wrote :

How could I test if the patch is working? Are there already new package builds with the fix included that I can install...?
I already tried to use the alsa-setup.sh script (http://www.stchman.com/alsa_update.html) but it did not help unfortunately...

Still with enabled automute feature the volume bar is blinking and no sound from the speakers :-/

Tested with a few different settings in alsa-base.conf, just default without any settings , the earlier working "model=laptop-eapd position_fix=1" and with model=3stack but nothing changes...

Revision history for this message
Kristof S. (ksa1) wrote :

FYI: I tested again with a current Ubuntu Installation, Lubuntu 15.04, Kernel 3.19.0-21-generic #21-Ubuntu SMP (same Asus Notebook as noted above). The good news is the "switching bug" disappeared. The bad thing is that there is still no (speaker) sound yet, not with the installation default and not with manually trying the entry working for me in an earlier ubuntu version - options snd-hda-intel model=laptop-eapd position_fix=1).

Here is a recent alsa-info: ALSA information is located at http://www.alsa-project.org/db/?f=dd668e30fbdc329986902f48d7aa9229a17281e6

Revision history for this message
Alessandro Ignis (artaeun) wrote : Re: [Bug 1316156] Re: speakers audio won't work - pavucontrol is switching continually between speakers and headphones
Download full text (4.2 KiB)

Thanks for keeping me updated

Il giorno ven 3 lug 2015 23:05 Kristof S. <email address hidden> ha scritto:

> FYI: I tested again with a current Ubuntu Installation, Lubuntu 15.04,
> Kernel 3.19.0-21-generic #21-Ubuntu SMP (same Asus Notebook as noted
> above). The good news is the "switching bug" disappeared. The bad thing
> is that there is still no (speaker) sound yet, not with the installation
> default and not with manually trying the entry working for me in an
> earlier ubuntu version - options snd-hda-intel model=laptop-eapd
> position_fix=1).
>
> Here is a recent alsa-info: ALSA information is located at http://www
> .alsa-project.org/db/?f=dd668e30fbdc329986902f48d7aa9229a17281e6
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1316156
>
> Title:
> speakers audio won't work - pavucontrol is switching continually
> between speakers and headphones
>
> Status in ALSA driver:
> Unknown
> Status in alsa-driver package in Ubuntu:
> Confirmed
>
> Bug description:
> The port is continually switching between Speakers and Heaphones and no
> audio is outputting from the speakers. I have tried various distributions
> and have found that this problems is NOT present in Ubuntu 11.04, 12.04,
> 13.04. I have not tried 11.10, or 12.10. But have found 13.10 and 14.04 to
> show this identical problem.
> My main concern is for the 14.04 LTS version I am currently using.
>
> - I tried regulating the audio from alsamixer -by disabling auto-mute in
> alsamixer i managed to stop it switching from one port to the other. Still,
> no audio from speakers (only a regular and low-volume BUMP comes out)
> - I tried modifying the /etc/modprobe.d/alsa-base.conf file. Since i
> could not find my pc (Packard Bell EasyNote MX45) in the alsa-configuration
> list, i have tried using only the audio boards main info as referral (Intel
> HDA AD1986A NM10/ICH7). Thus i have added to the alsa-base.conf the
> following and rebooted after trying each and every new line (added only
> once per try, not all of them together).
> -options snd-hda-intel model=laptop
> -options snd-hda-intel model=laptop-eapd
> -options snd-hda-intel model=3stack
> -options snd-hda-intel model=generic
>
> - Also tried the position_fix quirking suggested on the ubuntu
> documentation pages
> -options snd-hda-intel position_fix= 1
> -options snd-hda-intel position_fix= 2
>
> The audio outputted from the speakers kept being a regular BUMP and
> nothing more, regardless of the input.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 14.04
> Package: pulseaudio 1:4.0-0ubuntu11
> ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
> Uname: Linux 3.13.0-24-generic i686
> ApportVersion: 2.14.1-0ubuntu3
> Architecture: i386
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: xubuntu 3690 F.... pulseaudio
> CasperVersion: 1.340
> Date: Mon May 5 13:48:40 2014
> LiveMediaBuild: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386
> (20140416.2)
> ProcEnv...

Read more...

Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

Changed in alsa-driver (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you.

Changed in alsa-driver (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.