opensuse 11.3 :Headphones wont mute speakers

English Multimedia
1

Hi,
I’m using opensuse 11.3 on lenovo y430.
Everything works perfect except “The problem with the headphones”.
Lenovo y430 has a sub woofer at the bottom which wont mute on plugging the headphones.

I tried with this
SDB:Intel-HDA sound problems - openSUSE

and possible outputs

ebenash@linux-seem:~> head -n 1 /proc/asound/card0/codec*
==> /proc/asound/card0/codec#1 <==
Codec: Nvidia MCP77/78 HDMI

==> /proc/asound/card0/codec#2 <==
Codec: Conexant CX20561 (Hermosa)

But could not find it, listed in
/usr/src/KERNEL_VERSION/Documentation/sound/alsa/ALSA-Configuration.txt

My KERNEL_VERSION =linux-2.6.34-12

Kindly help me out.
Thanks in advance.

2

Often the only way to solve these “speaker not mute” problems is by writing a bug report. But first can you provide some more information (in case the problem is not difficult) ? Please provide the information recommended to be provided in our multimedia stickie: Welcome to multimedia sub-area

3

First of all,Thank you very much for such quick response.

For code
/usr/sbin/alsa-info.sh

Output:
http://www.alsa-project.org/db/?f=1326389c715f0e38e5726ff32cb1b00223d24609

And for rest

linux-seem:/home/ebenash # rpm -qa ‘alsa’
alsa-plugins-samplerate-1.0.23-1.9.i586
alsa-tools-1.0.23-1.8.i586
alsa-plugins-1.0.23-1.9.i586
alsa-oss-1.0.17-29.2.i586
alsa-1.0.23-2.12.i586
pyalsa-1.0.22-1.8.i586
alsa-plugins-speex-1.0.23-1.9.i586
alsa-utils-1.0.23-1.8.i586
alsa-plugins-pulse-1.0.23-1.9.i586
alsamixergui-0.9.0rc1-746.1.i586
alsa-firmware-1.0.23-1.2.noarch
alsa-plugins-jack-1.0.23-1.9.i586
alsa-tools-gui-1.0.23-1.8.i586
linux-seem:/home/ebenash # rpm -qa ‘pulse’
pulseaudio-module-zeroconf-0.9.21-9.2.i586
pulseaudio-module-bluetooth-0.9.21-9.2.i586
libpulse-browse0-0.9.21-9.2.i586
pulseaudio-0.9.21-9.2.i586
pulseaudio-esound-compat-0.9.21-9.2.i586
pulseaudio-module-x11-0.9.21-9.2.i586
pulseaudio-utils-0.9.21-9.2.i586
pulseaudio-module-gconf-0.9.21-9.2.i586
libpulse-mainloop-glib0-0.9.21-9.2.i586
alsa-plugins-pulse-1.0.23-1.9.i586
libpulse0-0.9.21-9.2.i586
pulseaudio-module-lirc-0.9.21-9.2.i586
linux-seem:/home/ebenash # rpm -q libasound2
libasound2-1.0.23-2.12.i586
linux-seem:/home/ebenash # uname -a
Linux linux-seem.site 2.6.34-12-default #1 SMP 2010-06-29 02:39:08 +0200 i686 i686 i386 GNU/Linux
linux-seem:/home/ebenash # cat /etc/modprobe.d/50-sound.conf

options snd slots=snd-hda-intel

u1Nb.JhlWIrGTU2C:82801I (ICH9 Family) HD Audio Controller

alias snd-card-0 snd-hda-intel
linux-seem:/home/ebenash #

4

I note this in mixer:
Simple mixer control ‘Master’,0
Front Left: Playback 73 [99%] -1.00dB] [off]
Front Right: Playback 73 [99%] -1.00dB] [off]
Simple mixer control ‘PCM’,0
Front Left: Playback 252 [99%] [0.60dB]
Front Right: Playback 252 [99%] [0.60dB]

I assume Master volume is muted to try and stop sound from coming out of speakers.

I note a 32-bit 2.6.34-12-default kernel on a LENOVO 2781 with the ‘stock’ alsa 1.0.22.1 / 1.0.23. So we could try an update to a newer version of alsa, but before that, there is something else we could attempt first.

I also note your PC has a CX20561 (hermosa) which I think is the same as a Conexant 5051. I note these model options (only one at a time) from the HD-Audio-Models.txt file can be applied at boot to force an over ride of the automatic alsa configuration on a Conexant 5051 :

Conexant 5051
=============
  laptop	Basic Laptop config (default)
  hp		HP Spartan laptop
  hp-dv6736	HP dv6736
  lenovo-x200	Lenovo X200 laptop

We could work on the assumption that your audio is not being configured properly upon boot, and try to force a specific model option (configuration) when booting.

For example, lets say we want to try the option “laptop”. To do that, change the above file to:
options snd-hda-intel model=laptop
options snd slots=snd-hda-intel

u1Nb.JhlWIrGTU2C:82801I (ICH9 Family) HD Audio Controller

alias snd-card-0 snd-hda-intelwhere you can see I added a line at the front of the file. Save that change and then restart your alsa with:

su -c 'rcalsasound restart'

and then restart your mixer (kmix in kde, and alsamixer ? gmixer ? in gnome). And then test your headset/speaker functionality.

That may make things completely worse. No worries if it does, simply replace ‘laptop’ in that line with another option, say ‘hp’, and save the change, restart alsa, restart your mixer, and test. Do that for EACH option to see if any help.

If none help, we can look at updating alsa, and I can point you to some rpms for that.

5

No luck Unfortunately.

Tried all the 4.

Completely No sound (Both headphones and speakers)for model=hp-dv6736

6

Ok, then the last step to try, before writing a bug report, is to update your version of the alsa sound driver to the latest version.

There is guidance here how to do that: SDB:Alsa-update - openSUSE

Note this means updating alsa-plugins-samplerate, alsa-tools, alsa-plugins, alsa-oss, alsa, alsa-plugins-speex, alsa-utils, alsa-plugins-pulse, alsamixergui, alsa-firmware, alsa-plugins-jack, alsa-tools-gui, and libasound2 from the repository:

 http://download.opensuse.org/repositories/multimedia:/libs/openSUSE_11.3/

and install alsa-driver-kmp-default from the repository:

 http://download.opensuse.org/repositories/multimedia:/audio:/KMP/openSUSE_11.3/

Note for the updates of the many alsa apps, check the version numbers after you have installed to ensure they were updated. If the version numbers did NOT update, then you failed to update. I would estimate 80% of those asking for help trying to update always make this mistake of not updating, when they think they did update. So be careful here!! I tried to make that clear in the wiki: SDB:Alsa-update - openSUSE with sketchs, markups, etc … but it does not matter as the mistakes are still made. I can only conclude is my suggestion for how to update is ignored, and everyone applies their own method which does not work. Anyway - nuff said. Just be as precise as possible.

After updating you MUST reboot.

Then test the sound.

If that fails, please advise, and I’ll provide guidance on writing a bug report, where for openSUSE, bug reports written on component sound often result in resaonably quick fixes (because a SuSE-GmbH employee is an alsa sound driver developer).

7

Thanks again for reply.
Updating Alsa solved the problem

Followed steps given on
SDB:Alsa-update - openSUSE

Thank you so much for all the replies.

No wonder why people say "LiNUX RoKZ"

Will try to help Puzzled Penguins [Like me] Everywhere I come across.

8

Thats excellent news ! Glad to read it.

As openSUSE users, we are lucky that we have an alsa developer employed by SuSE-GmbH, as they make those openSUSE update rpms available, which are in essence very cutting edge snapshots of the latest driver code (sometimes only a day or so old).

9

One warning that I forgot to give you < gulp > … there is a very strong possibility that when SuSE-GmbH put a kernel update on the repositories, it will break your sound when you install the kernel update. ie the cutting edge alsa updates won’t be in the kernel update.

Hence in a case like that, I recommend you decline to update your kernel, but instead wait a week, until you can observe that the SuSE-GmbH alsa packager/developer has also updated the alsa-driver-kmp-default rpm on the web site/respository you just used for your update. If you check the version number of the alsa-driver-kmp-default you will be able to tell if the new driver is available for the updated kernel. Once you confirm the driver is available (for the new kernel) then go ahead and apply the kernel update, and update the alsa-driver-kmp-default.

Best wishes and good luck.

10

Once again,Thank you very much.
Will be careful to an update.

11

Hi I am facing following problem after updating ALSA driver as explained in link given.

  1. If I hook up headphone during boot then sound will be routed to only to headphones. No sound on speakers.

  2. If I hook up headphone after boot up, sound won’t get muted from speakers(same as old problem).

Please find my alsa profile here:http://www.alsa-project.org/db/?f=3e93890be3df21c1aaa633d07174d61b61c4941b

12

Thankyou, but I am not familiar with your hardware, nor with what you have installed on your PC.

Presumeably you decided to post your problem on this thread for a reason, and if you did read this thread you will note the previous user provided additional information. The instruction as to what information to provide was in a link I provided. Here is the quote of mine asking for information:

Apologies, but I am not smart enough to even begin to suggest a solution without additional information as I noted above. Please, can you provide that?

Good luck and best wishes.

13

Sorry for the late reply…

Here is my system info…
linux-79xv:/home/nvadiga # rpm -qa ‘alsa’
alsa-1.0.23-2.12.i586
alsa-utils-debugsource-1.0.23-25.1.i586
alsa-plugins-samplerate-1.0.23-33.1.i586
alsa-oss-debuginfo-1.0.17-53.1.i586
alsa-tools-debugsource-1.0.23-9.1.i586
alsa-plugins-maemo-1.0.23-33.1.i586
alsa-debugsource-1.0.23-69.1.i586
alsa-oss-1.0.17-29.2.i586
alsa-utils-1.0.23-1.8.i586
pyalsa-1.0.22-4.1.i586
alsa-tools-gui-debuginfo-1.0.23-9.1.i586
alsa-plugins-speex-1.0.23-33.1.i586
alsa-plugins-maemo-debuginfo-1.0.23-33.1.i586
alsa-plugins-debuginfo-1.0.23-33.1.i586
alsa-docs-1.0.23-69.1.noarch
alsa-tools-gui-1.0.23-9.1.i586
alsa-devel-1.0.23-69.1.i586
alsa-plugins-1.0.23-1.9.i586
alsa-plugins-pulse-1.0.23-1.9.i586
alsa-utils-debuginfo-1.0.23-25.1.i586
alsa-plugins-speex-debuginfo-1.0.23-33.1.i586
alsa-plugins-pulse-debuginfo-1.0.23-33.1.i586
alsa-plugins-debugsource-1.0.23-33.1.i586
alsa-firmware-1.0.23-8.1.noarch
alsa-tools-devel-1.0.23-9.1.i586
alsa-driver-kmp-desktop-1.0.23.20101006_k2.6.34.7_0.3-3.1.i586
alsa-tools-debuginfo-1.0.23-9.1.i586
alsa-plugins-jack-debuginfo-1.0.23-33.1.i586
alsa-plugins-jack-1.0.23-33.1.i586
alsa-plugins-samplerate-debuginfo-1.0.23-33.1.i586
alsa-oss-debugsource-1.0.17-53.1.i586
alsa-tools-1.0.23-9.1.i586

linux-79xv:/home/nvadiga # rpm -qa ‘pulse’
libpulse-browse0-0.9.21-10.1.1.i586
pulseaudio-module-gconf-0.9.21-10.1.1.i586
pulseaudio-module-x11-0.9.21-10.1.1.i586
pulseaudio-module-bluetooth-0.9.21-10.1.1.i586
pulseaudio-esound-compat-0.9.21-10.1.1.i586
alsa-plugins-pulse-1.0.23-1.9.i586
pulseaudio-0.9.21-10.1.1.i586
pulseaudio-module-lirc-0.9.21-10.1.1.i586
alsa-plugins-pulse-debuginfo-1.0.23-33.1.i586
pulseaudio-utils-0.9.21-10.1.1.i586
libpulse0-0.9.21-10.1.1.i586
libpulse-mainloop-glib0-0.9.21-10.1.1.i586
pulseaudio-module-zeroconf-0.9.21-10.1.1.i586

linux-79xv:/home/nvadiga # rpm -q libasound2
libasound2-1.0.23-2.12.i586

linux-79xv:/home/nvadiga # cat /etc/modprobe.d/50-sound.conf

options snd slots=snd-hda-intel,snd-hda-intel

5Dex.eScF8+KE3b9:SBx00 Azalia (Intel HDA)

alias snd-card-0 snd-hda-intel

l4dC.+LiosE56dU6:RS780 Azalia controller

alias snd-card-1 snd-hda-intel

In the mean time I also found an workaround of restarting alsa sound using “/etc/init.d/alsasound restart” after connecting headphone. It will route the sound to headphones only.

14

Wow! Please, why so many alsa applications?? I’m confused! :open_mouth:

Installing more will most definitely NOT cure your headphone problem. It may cause other problems. In Linux, typically bloat is not good… Did someone tell you to install all those ‘debug’ and ‘debuginfo’ rpms? Do you know how to use them ? I don’t. I recommend you remove every alsa app with ‘debug’ in the file name.

Now, note I high lighted in red alsa-1.0.23-2.12.i586, alsa-oss-1.0.17-29.2.i586, alsa-plugins-1.0.23-1.9.i586, alsa-plugins-pulse-1.0.23-1.9.i586, libasound2-1.0.23-2.12.i586. To be consistent with the other alsa apps on your PC, those should be updated to alsa-1.0.23-69.1.i586, alsa-oss-1.0.17-53.1.i586, alsa-plugins-1.0.23-33.1.i586, alsa-plugins-pulse-1.0.23-33.1.i586, libasound2-1.0.23-69.1.i586

The repository for that is here:

http://download.opensuse.org/repositories/multimedia:/libs/openSUSE_11.3/

Then restart and test.

This was about 4x harder than normal to check the versions, because you have way more alsa apps installed than I think you need. I view that as bloat that clouds the issue and makes figuring out what is going on significantly more difficult.

Note, another way to restart your sound driver is:

su -c 'rcalsasound restart'

and enter root password when prompted, and then restart your mixer.

Good luck.

15

Thanks for the info… My problem solved after updating the packages. I installed those ‘debug’ packages before reading this thread just to make sure I have everything installed for sound to work properly :frowning: Sorry for the noise that I created.

16

Excellent !! Congratulations on your solving this, and thankyou for sharing your solution.

A caution/warning, … when there is a kernel update, it may break your sound, and you may be again forced to update the ‘alsa-driver-kmp-desktop’ rpm from the repository:

 http://download.opensuse.org/repositories/multimedia:/audio:/KMP/openSUSE_11.3_Update/

…
once again, congratulations on solving the PC’s problem.