Laptop speakers won't mute when using headphones

Bug #92992 reported by Josh Ancill
16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Won't Fix
Low
Ubuntu Audio Team
linux-source-2.6.22 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I am having a problem with laptop sound under feisty fawn.

When plugging in headphones into the headphone jack on my Compaq V3000Z (AMD Turion X2) the speakers do not mute and the sound mixer controls both the headphone and speaker volumes.

According to lspci this is the sound device my laptop uses:
00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2)

I hope this helps fix this issue.

Revision history for this message
Luke Yelavich (themuso) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please add the output requested at https://help.ubuntu.com/community/DebuggingSoundProblems as separate attachments? Thanks in advance.

Changed in alsa-driver:
status: Unconfirmed → Needs Info
Revision history for this message
Josh Ancill (mempf) wrote :
Revision history for this message
Josh Ancill (mempf) wrote :
Revision history for this message
Josh Ancill (mempf) wrote :
Revision history for this message
Josh Ancill (mempf) wrote :
Revision history for this message
Josh Ancill (mempf) wrote :
Revision history for this message
Josh Ancill (mempf) wrote :
Revision history for this message
Josh Ancill (mempf) wrote :

Ok I have posted the attachments you requested.

Changed in linux-source-2.6.20:
assignee: nobody → ubuntu-audio
importance: Undecided → Medium
status: Needs Info → Confirmed
Revision history for this message
Bastanteroma (bastanteroma) wrote :

I can confirm this on an HP with the same sound chip.

Revision history for this message
paulimk (paulimk) wrote :

I can also confirm this on a HP dv2140eu with the same sound chip. The problem is fixed in alsa-driver-1.0.14rc2.

Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom still visible in 7.04 (final)?

Changed in linux-source-2.6.20:
importance: Medium → Low
status: Confirmed → Needs Info
Revision history for this message
Josh Ancill (mempf) wrote :

Yes I still have this issue running feisty final.

Revision history for this message
Josh Ancill (mempf) wrote :

I would like to note that this is fixed in Gutsy using kernel 2.6.22-1.

Revision history for this message
Andrew Ash (ash211) wrote :

Bastanteroma, paulimk: can either of you confirm this fix in gutsy with kernel 2.6.22-1 if possible?

Daniel T Chen (crimsun)
Changed in linux-source-2.6.20:
status: Needs Info → Fix Committed
Revision history for this message
Mike Basinger (mike.basinger) wrote :

I'm still having this problem after with Gutsy Tribe 5 (kernel: 2.6.22-10).

Revision history for this message
Haakon Nilsen (haakonn) wrote :

This problem has plagued me as long as I've owned this Lenovo 3000 N100 laptop, and still does in gutsy, kernel 2.6.22-14-generic. lspci says soundcard is "00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)".

The only way I've found to turn off the laptop speakers is to mute the "External Amplifier" in alsamixer, but that makes the sound very muffled and is not a solution.

# cat /proc/asound/cards
 0 [Intel ]: HDA-Intel - HDA Intel
                      HDA Intel at 0xb0000000 irq 21

# aplay --list-devices
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 6: Si3054 Modem [Si3054 Modem]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

From 'lspci -vvnn':

00:1b.0 Audio device [0403]: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller [8086:27d8] (rev 02)
        Subsystem: Lenovo Unknown device [17aa:2066]
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 21
        Region 0: Memory at b0000000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: [50] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
                Address: 0000000000000000 Data: 0000
        Capabilities: [70] Express Unknown type IRQ 0
                Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
                Device: Latency L0s <64ns, L1 <1us
                Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
                Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
                Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
                Link: Supported Speed unknown, Width x0, ASPM unknown, Port 0
                Link: Latency L0s <64ns, L1 <1us
                Link: ASPM Disabled CommClk- ExtSynch-
                Link: Speed unknown, Width x0

Revision history for this message
Neil Grover (ngrover) wrote :

I am experiencing this same problem on an ASUS V1F laptop under Gutsy with 2.6.22-14-generic.

lspci says: 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)

Revision history for this message
Neil Grover (ngrover) wrote :

sorry Asus V1S not V1F

Revision history for this message
Nikhil (mushroomcloudwarrior-01) wrote :

Same problem on Dell vostro 1500, using Gutsy 7.10 AFTER installing Linux-backports-modules

Revision history for this message
thisjackis (thisjackis) wrote :

I've got the same problem with SONY VAIO SZ series

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi All,

Since the original bug reporter has commented that issue is resolved in Gutsy, I'm going to close this report. Please note that the symptom of this particular bug is specific to the hardware used. So while many of you may have the same symptom they really should be different bugs because you have different hardware. For those of you with different sound cards than the original bug reporter it would be helpful if everyone were to test with the latest Hardy Alpha release, http://cdimage.ubuntu.com/releases/hardy/ , and open a separate bug report for their hardware using "linux" as the package. You should be able to test via the LiveCD. The new bug report you open should contain the information requested at http://wiki.ubuntu.com/KernelTeamBugPolicies . Additionally, it would be great if you made the titles of a new bug report contain information about your system. I apologize for any inconvenience this might cause but appreciate your cooperation. Thanks.

Changed in linux-source-2.6.22:
status: New → Fix Released
Changed in linux-source-2.6.20:
status: Fix Committed → Won't Fix
Revision history for this message
sjs889 (sjarrettsprague) wrote :

This bug is still present in Hardy Heron. Putting headphones in socket doesn't mute the speakers on the laptop (Toshiba Satellite Pro a120).

Revision history for this message
sjs889 (sjarrettsprague) wrote :
Revision history for this message
sjs889 (sjarrettsprague) wrote :
Revision history for this message
sjs889 (sjarrettsprague) wrote :
Revision history for this message
Neil Grover (ngrover) wrote :

This problem persists for me also on my Asus V1S.

WORKAROUND !!

I followed this workaround and now my headphones work as expected: http://ubuntuforums.org/showthread.php?t=582089&page=2

Basically

* Add/change the following line in /etc/modprobe.d/alsa-base:
"options snd-hda-intel model=lenovo"
* Go to System > Settings > Audio > choose Device: HDA Intel (...) and Channel: PCM
* If you use the applet in the gnome-Panel to control the volume: Go to [right click] -> Settings -> Device: HDA Intel (...); Channel: PCM
* You may want to turn up the volume of the Front channel to almost 100%
* Reboot

This is not fix but it does make it work.

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.