Ubuntu
alsa-driver package

[Dell System XPS L502X, Realtek ALC665, Speaker, Internal] When running google chrome, speakers emit a repetitive 'pop'

Bug #1071481 reported by Saad Bin Javed
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
alsa-driver (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I've installed ubuntu-dev ppa and ran the sound troubleshooting steps mentioned in the wiki. There is no fix. The popping stops when chrome is closed. I tried disabling the PepperFlash plugin in chrome://plugins but to no avail.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
Uname: Linux 3.2.0-32-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu13
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: ALC665 Analog [ALC665 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: saad 1820 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xf1c00000 irq 54'
   Mixer name : 'Intel CougarPoint HDMI'
   Components : 'HDA:10ec0665,1028050e,00100003 HDA:80862805,80860101,00100000'
   Controls : 32
   Simple ctrls : 14
Date: Fri Oct 26 01:11:47 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_AlsaPlaybackTestStderr:
 W r i t e e r r o r : - 5 , I n p u t / o u t p u t e r r o r
  x r u n _ r e c o v e r y f a i l e d : - 5 , I n p u t / o u t p u t e r r o r
  T r a n s f e r f a i l e d : O p e r a t i o n n o t p e r m i t t e d
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [Dell System XPS L502X, Realtek ALC665, Speaker, Internal] Underruns, dropouts or crackling sound
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/29/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0NJT03
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnDellInc.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: Dell System XPS L502X
dmi.sys.vendor: Dell Inc.

Revision history for this message
Saad Bin Javed (sbjaved) wrote :
Revision history for this message
Raymond (superquad-vortex2) wrote :

do you mean the patch does not fix the problem ?

http://git.kernel.org/?p=linux/kernel/git/tiwai/sound.git;a=commit;h=f7f4b2322bf7b8c5929b7eb5a667091f32592580

Revision history for this message
Saad Bin Javed (sbjaved) wrote :

No. The popping noise is still here. I'm using chrome Version 22.0.1229.94

Revision history for this message
Saad Bin Javed (sbjaved) wrote :

is this patch present in the kernel i'm running?

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

pin-ctls of node 0x15 speaker should be OUT

Node 0x15 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out
  Control: name="Speaker Playback Switch", index=0, device=0
    ControlAmp: chs=3, dir=Out, idx=0, ofs=0
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals: [0x00 0x00]
  Pincap 0x0001003c: IN OUT HP EAPD Detect
  EAPD 0x0:
  Pin Default 0x99130110: [Fixed] Speaker at Int ATAPI
    Conn = ATAPI, Color = Unknown
    DefAssociation = 0x1, Sequence = 0x0
    Misc = NO_PRESENCE
  Pin-ctls: 0x20: IN
  Unsolicited: tag=00, enabled=0
  Power states: D0 D1 D2 D3 EPSS
  Power: setting=D0, actual=D0
  Connection: 2
     0x0c* 0x0d

Revision history for this message
Saad Bin Javed (sbjaved) wrote : Re: [Bug 1071481] [NEW] [Dell System XPS L502X, Realtek ALC665, Speaker, Internal] When running google chrome, speakers emit a repetitive 'pop'

Can you please explain which file is this and what bit should I change?

On Thursday, November 1, 2012, Raymond <email address hidden> wrote:

> pin-ctls of node 0x15 speaker should be OUT
>
>
> Node 0x15 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out
> Control: name="Speaker Playback Switch", index=0, device=0
> ControlAmp: chs=3, dir=Out, idx=0, ofs=0
> Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
> Amp-Out vals: [0x00 0x00]
> Pincap 0x0001003c: IN OUT HP EAPD Detect
> EAPD 0x0:
> Pin Default 0x99130110: [Fixed] Speaker at Int ATAPI
> Conn = ATAPI, Color = Unknown
> DefAssociation = 0x1, Sequence = 0x0
> Misc = NO_PRESENCE
> Pin-ctls: 0x20: IN
> Unsolicited: tag=00, enabled=0
> Power states: D0 D1 D2 D3 EPSS
> Power: setting=D0, actual=D0
> Connection: 2
> 0x0c* 0x0d
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1071481
>
> Title:
> [Dell System XPS L502X, Realtek ALC665, Speaker, Internal] When
> running google chrome, speakers emit a repetitive 'pop'
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1071481/+subscriptions
>

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

does l502x support surround5.1 by reconfiguring two hp jacks and mic jacks ?

since mic jack 0x1a can only be connected to 0x0d which can be connected to 0x03

this.mean headphone 0x1b should not connected to 0x03 , i.e. speaker 0x15 should be connected to 0x03 through 0x0d

Node 0x19 [Pin Complex] wcaps 0x40058f: Stereo Amp-In Amp-Out
  Control: name="Headphone Playback Switch", index=1, device=0
    ControlAmp: chs=3, dir=Out, idx=0, ofs=0
  Control: name="Headphone Jack", index=1, device=0
  Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
  Amp-In vals: [0x00 0x00]
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals: [0x00 0x00]
  Pincap 0x0000173c: IN OUT HP Detect
    Vref caps: HIZ 50 GRD 80
  Pin Default 0x03211020: [Jack] HP Out at Ext Left
    Conn = 1/8, Color = Black
    DefAssociation = 0x2, Sequence = 0x0
  Pin-ctls: 0x00: VREF_HIZ
  Unsolicited: tag=02, enabled=1
  Power states: D0 D1 D2 D3 EPSS
  Power: setting=D0, actual=D0
  Connection: 3
     0x0c 0x0d 0x0e*
Node 0x1a [Pin Complex] wcaps 0x40058f: Stereo Amp-In Amp-Out
  Control: name="Mic Boost Volume", index=0, device=0
    ControlAmp: chs=3, dir=In, idx=0, ofs=0
  Control: name="Mic Jack", index=0, device=0
  Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
  Amp-In vals: [0x00 0x00]
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals: [0x80 0x80]
  Pincap 0x00001734: IN OUT Detect
    Vref caps: HIZ 50 GRD 80
  Pin Default 0x03a11840: [Jack] Mic at Ext Left
    Conn = 1/8, Color = Black
    DefAssociation = 0x4, Sequence = 0x0
  Pin-ctls: 0x20: IN VREF_HIZ
  Unsolicited: tag=03, enabled=1
  Power states: D0 D1 D2 D3 EPSS
  Power: setting=D0, actual=D0
  Connection: 1
     0x0d
Node 0x1b [Pin Complex] wcaps 0x40058f: Stereo Amp-In Amp-Out
  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-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
  Amp-In vals: [0x00 0x00]
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals: [0x00 0x00]
  Pincap 0x0000173c: IN OUT HP Detect
    Vref caps: HIZ 50 GRD 80
  Pin Default 0x0321101f: [Jack] HP Out at Ext Left
    Conn = 1/8, Color = Black
    DefAssociation = 0x1, Sequence = 0xf
  Pin-ctls: 0x00: VREF_HIZ
  Unsolicited: tag=01, enabled=1
  Power states: D0 D1 D2 D3 EPSS
  Power: setting=D0, actual=D0
  Connection: 3
     0x0c 0x0d* 0x0e

Revision history for this message
Saad Bin Javed (sbjaved) wrote :
Download full text (3.1 KiB)

Raymond,

I swear that went over my head. If you know what to fix, please tell me in
simple english :)

On Thursday, November 1, 2012, Raymond <email address hidden> wrote:

> does l502x support surround5.1 by reconfiguring two hp jacks and mic jacks
> ?
>
> since mic jack 0x1a can only be connected to 0x0d which can be connected
> to 0x03
>
> this.mean headphone 0x1b should not connected to 0x03 , i.e. speaker
> 0x15 should be connected to 0x03 through 0x0d
>
>
> Node 0x19 [Pin Complex] wcaps 0x40058f: Stereo Amp-In Amp-Out
> Control: name="Headphone Playback Switch", index=1, device=0
> ControlAmp: chs=3, dir=Out, idx=0, ofs=0
> Control: name="Headphone Jack", index=1, device=0
> Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
> Amp-In vals: [0x00 0x00]
> Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
> Amp-Out vals: [0x00 0x00]
> Pincap 0x0000173c: IN OUT HP Detect
> Vref caps: HIZ 50 GRD 80
> Pin Default 0x03211020: [Jack] HP Out at Ext Left
> Conn = 1/8, Color = Black
> DefAssociation = 0x2, Sequence = 0x0
> Pin-ctls: 0x00: VREF_HIZ
> Unsolicited: tag=02, enabled=1
> Power states: D0 D1 D2 D3 EPSS
> Power: setting=D0, actual=D0
> Connection: 3
> 0x0c 0x0d 0x0e*
> Node 0x1a [Pin Complex] wcaps 0x40058f: Stereo Amp-In Amp-Out
> Control: name="Mic Boost Volume", index=0, device=0
> ControlAmp: chs=3, dir=In, idx=0, ofs=0
> Control: name="Mic Jack", index=0, device=0
> Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
> Amp-In vals: [0x00 0x00]
> Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
> Amp-Out vals: [0x80 0x80]
> Pincap 0x00001734: IN OUT Detect
> Vref caps: HIZ 50 GRD 80
> Pin Default 0x03a11840: [Jack] Mic at Ext Left
> Conn = 1/8, Color = Black
> DefAssociation = 0x4, Sequence = 0x0
> Pin-ctls: 0x20: IN VREF_HIZ
> Unsolicited: tag=03, enabled=1
> Power states: D0 D1 D2 D3 EPSS
> Power: setting=D0, actual=D0
> Connection: 1
> 0x0d
> Node 0x1b [Pin Complex] wcaps 0x40058f: Stereo Amp-In Amp-Out
> 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-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
> Amp-In vals: [0x00 0x00]
> Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
> Amp-Out vals: [0x00 0x00]
> Pincap 0x0000173c: IN OUT HP Detect
> Vref caps: HIZ 50 GRD 80
> Pin Default 0x0321101f: [Jack] HP Out at Ext Left
> Conn = 1/8, Color = Black
> DefAssociation = 0x1, Sequence = 0xf
> Pin-ctls: 0x00: VREF_HIZ
> Unsolicited: tag=01, enabled=1
> Power states: D0 D1 D2 D3 EPSS
> Power: setting=D0, actual=D0
> Connection: 3
> 0x0c 0x0d* 0x0e
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1071481
>
> Title:
> [Dell System XPS L502X, Realtek ALC665, Speaker, Internal] When
> running google chrome, speakers emit a repetitive 'pop'
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1...

Read more...

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

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

Changed in alsa-driver (Ubuntu):
status: New → Confirmed
Revision history for this message
moox (dagomox) wrote :

I have this problem too. It occurs only with chrome.
The sound appears to disappear when I plug the power in.

Revision history for this message
moox (dagomox) wrote :

Saad Bin Javed you can try this workaround

This is what I figured out actually works:
- Type about:plugins in your address bar
- Click Details on the upper right corner
- Locate the entry for libpepflashplayer.so
-- Click Disable
- Locate the entry for libflashplayer.so
-- The entry should already, if not enable it, or you'll lose flash support.

Restart Chrome and you'll be popping-free. But you will get the annoying "there is an flash update" dialogues. Better than the popping.

Source : http://ddurdle.blogspot.ca/2012/07/google-chrome-popping-sound.html

it worked for me

Revision history for this message
Saad Bin Javed (sbjaved) wrote : Re: [Bug 1071481] Re: [Dell System XPS L502X, Realtek ALC665, Speaker, Internal] When running google chrome, speakers emit a repetitive 'pop'

Disabling pepperflash plugin doesnt work for me.

On Fri, Nov 2, 2012 at 9:47 PM, moox <email address hidden> wrote:
Saad Bin Javed you can try this workaround

This is what I figured out actually works:
- Type about:plugins in your address bar
- Click Details on the upper right corner
- Locate the entry for libpepflashplayer.so
-- Click Disable
- Locate the entry for libflashplayer.so
-- The entry should already, if not enable it, or you'll lose flash support.

Restart Chrome and you'll be popping-free. But you will get the
annoying "there is an flash update" dialogues. Better than the popping.

Source : http://ddurdle.blogspot.ca/2012/07/google-chrome-popping-
sound.html

it worked for me

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1071481

Title:
[Dell System XPS L502X, Realtek ALC665, Speaker, Internal] When
running google chrome, speakers emit a repetitive 'pop'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1071481/+subscriptions

Revision history for this message
Saad Bin Javed (sbjaved) wrote :

Disabled power saving on the sound card by following this guide: http://www.foxswap.com/computers-and-technology/ubuntu-12-04-clicking-sound-from-speakers/
Works for me. Thank God! I was going nuts!

Revision history for this message
Saad Bin Javed (sbjaved) wrote :

It seems the new chrome stable version (23.0.1271.64) has fixed the issue. Still need to test it longer.

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
Launchpad Janitor (janitor) wrote :

[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.]

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

Other bug subscribers

Remote bug watches

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