Headphone/Speaker problem

English Multimedia
#1

Just switched my laptop from that other operating system to openSUSE11.2. Everything works great except for one odd little bug. Both my speakers and headphones have output, are affected by the volume control and it even detects when I plug in headphones and stops output to the speakers. However the moment I adjust the volume, output to my headphones stops, and my speakers start.

Any suggestions on how to fix this? (or is it just something I’ll have to live with)

Regards,
MrChuckles14

Following is my multimedia information:
http://www.alsa-project.org/db/?f=1fcaecc135954cf7ee0ba238b64abd16c11b19cf

~> rpm -qa ‘alsa’
alsa-plugins-pulse-32bit-1.0.21-3.3.x86_64
alsa-plugins-pulse-1.0.21-3.3.x86_64
alsa-plugins-32bit-1.0.21-3.3.x86_64
alsa-1.0.21-3.2.x86_64
alsa-plugins-1.0.21-3.3.x86_64
alsa-utils-1.0.21-3.1.x86_64
alsa-oss-1.0.17-25.2.x86_64
alsa-oss-32bit-1.0.17-25.2.x86_64

~> rpm -qa ‘pulse’
alsa-plugins-pulse-32bit-1.0.21-3.3.x86_64
pulseaudio-lang-0.9.21-1.2.1.noarch
pulseaudio-0.9.21-1.2.1.x86_64
alsa-plugins-pulse-1.0.21-3.3.x86_64
pulseaudio-module-gconf-0.9.21-1.2.1.x86_64
libpulse0-0.9.21-1.2.1.x86_64
libpulse-mainloop-glib0-0.9.21-1.2.1.x86_64
pulseaudio-module-x11-0.9.21-1.2.1.x86_64
pulseaudio-module-bluetooth-0.9.21-1.2.1.x86_64
libxine1-pulse-1.1.16.1-7.6.x86_64
libpulse-browse0-0.9.21-1.2.1.x86_64
pulseaudio-utils-0.9.21-1.2.1.x86_64
libpulse0-32bit-0.9.21-1.2.1.x86_64
pulseaudio-module-zeroconf-0.9.21-1.2.1.x86_64
pulseaudio-module-lirc-0.9.21-1.2.1.x86_64

~> rpm -q libasound2
libasound2-1.0.21-3.2.x86_64

~> uname -a
Linux linux-0sj4 2.6.31.12-0.2-desktop #1 SMP PREEMPT 2010-03-16 21:25:39 +0100 x86_64 x86_64 x86_64 GNU/Linux

~> cat /etc/modprobe.d/50-sound.conf
options snd slots=snd-hda-intel

5Dex.ZTsnYRiTaCE:SBx00 Azalia (Intel HDA)

alias snd-card-0 snd-hda-intel

#2

Thanks for the script and rpm command output. It will (hopefully) help speed this up.

I note an ASUSTeK Computer INC “K50AF” (motherboard ? ) running a 64-bit openSUSE-11.2 with the 2.6.31.12-0.2-desktop kernel with 1.0.20/1.0.21 of the alsa sound driver. Also from the diagnostic script output, this ASUS appears to have an VT1708S hardware audio codec.

Now my experience is the problem you encountered is a problem with the driver.

I did a search on the alsa driver web site for the VT1708 and it appears there have been some updates to the alsa sound driver since openSUSE-11.2.

Hence you could try updating alsa per this guide: Alsa-update - openSUSE … please pay attention to your kernel version, and also AFTER you think you have updated the rpms, again do:

rpm -qa '*alsa*'
rpm -q libasound2

and if in addition to having alsa-driver-kmp-default, if you discover that those versions are the same as you already reported, then you failed in the update and you need to try again updating.

After a successful update, and after rebooting (to unload old drivers and reload new) if you still have the problem, then IMHO you are then into bug reporting territory in order to have this quickly fixed for you to use.

So, in that case, what you could do, if you have time, is write a bug report on openSUSE component “sound” on openSUSE-11.2.

Attach (don’t copy and paste, but attach) to the bug report the text file from running:

/usr/sbin/alsa-info.sh --no-upload

and that will create the file /tmp/alsa-info.txt which can be added as an attachment. That has bunch of technical info that may show the alsa dev what is wrong with the alsa driver, IF you also describe the audio symptoms.

Note the SuSE-GmbH packager for sound is also an alsa developer, and if he fixes this, the fix gets sent upstream and ALL Linux distributions will benefit from your efforts with him.

There is guidance here for raising bug reports: Submitting Bug Reports - openSUSE … The alsa developer/openSUSE packager, may ask that you try a few different alsa versions, and hence if your schedule is too busy for such support (and I definitely know what that can be like) then its probably best NOT to write such a bug report. (note - he won’t ask for too much)

Don’t reference this thread, as the SuSE-GmbH packager refuses to read forum threads. Its important the bug report has all the salient information.

Good luck !!

#3

Ok. Followed your instructions and updated alsa driver. It fixed the original problem but created another. Now when I plug my headphones in it mutes the volume (no sound from either speakers or headphones & mute symbol on volume control), but if I take mute off I have output from both speakers and headphones. I’m not really sure if this is progress or not.

Any additional suggestions (or is it time to submit a bug report?).
If you need any info outputs just ask.

Regards,
MrChuckles14

#4

When you plug the headphones in it is SUPPOSED to mute the speakers, but it is NOT supposed to mute the headphones (I know - I am stating the obvious). But this leads to my next question, which is did you check your mixer to ensure that the headphone volume control is not at a low setting or muted?

When you say “you take the mute off” I have no idea as to what control you are referring to

#5

Ignore my previous post, I really should know better than to troubleshoot while sleep deprived (one of the updates didn’t work).

Updated Alsa. Slightly different problem now. Sound works perfectly from both headphones and speakers, speakers mute when headphones plugged in but touching volume controls switchs speakers back on (headphones stay on as well now).

New info
http://www.alsa-project.org/db/?f=b74a3d072a6422f4e62650269791b8e3f5318687

~> rpm -qa ‘alsa’
alsa-plugins-pulse-32bit-1.0.23-28.1.x86_64
alsa-utils-1.0.23-20.1.x86_64
alsa-plugins-jack-1.0.23-28.1.x86_64
alsa-driver-kmp-desktop-1.0.23.20100717_2.6.31.5_0.1-1.1.x86_64
alsa-1.0.23-62.1.x86_64
alsa-oss-1.0.17-25.2.x86_64
alsa-oss-32bit-1.0.17-25.2.x86_64
alsa-plugins-pulse-1.0.23-28.1.x86_64
alsa-plugins-32bit-1.0.23-28.1.x86_64
alsa-firmware-1.0.23-8.1.noarch
alsa-plugins-1.0.23-28.1.x86_64
alsa-plugins-jack-32bit-1.0.23-28.1.x86_64

~> rpm -qa ‘pulse’
pulseaudio-lang-0.9.21-1.2.1.noarch
pulseaudio-module-gconf-0.9.21-1.2.1.x86_64
alsa-plugins-pulse-32bit-1.0.23-28.1.x86_64
libxine1-pulse-1.1.18.1-2.pm.41.1.x86_64
pulseaudio-module-x11-0.9.21-1.2.1.x86_64
libpulse-browse0-0.9.21-1.2.1.x86_64
pulseaudio-utils-0.9.21-1.2.1.x86_64
libpulse0-32bit-0.9.21-1.2.1.x86_64
pulseaudio-module-zeroconf-0.9.21-1.2.1.x86_64
alsa-plugins-pulse-1.0.23-28.1.x86_64
pulseaudio-module-lirc-0.9.21-1.2.1.x86_64
libpulse0-0.9.21-1.2.1.x86_64
libpulse-mainloop-glib0-0.9.21-1.2.1.x86_64
pulseaudio-module-bluetooth-0.9.21-1.2.1.x86_64
pulseaudio-0.9.21-1.2.1.x86_64

~> rpm -q libasound2
libasound2-1.0.23-62.1.x86_64

~> uname -a
Linux linux-0sj4 2.6.31.12-0.2-desktop #1 SMP PREEMPT 2010-03-16 21:25:39 +0100 x86_64 x86_64 x86_64 GNU/Linux

~> cat /etc/modprobe.d/50-sound.conf

options snd slots=snd-hda-intel

5Dex.ZTsnYRiTaCE:SBx00 Azalia (Intel HDA)

alias snd-card-0 snd-hda-intel

Does anything with the above seem out of place or am I into bug reporting territory now?
Oh and sorry for the delayed reply, I was busy with the start of semester organisation.

Thanks
MrChuckles14

#6

I recommend you write a bug report on this. Include as an attachment to the bug report the /tmp/alsa-info.txt file that is generated by running:

/usr/sbin/alsa-info.sh --no-upload

There is guidance here: openSUSE:Submitting bug reports - openSUSE … note the SusE-GmbH sound packager (also an alsa developer) won’t read a forum thread, so you need to include all salient details in the bug report.

#7

Hi! I recently installed 11.3 and almost every thing works quite well except my headphone’s microphone. I’m using KDE version of 11.3 on Asus G1 laptop. My ALSA diagnostic script information locates at http://www.alsa-project.org/db/?f=34a5cb0aea2cbb961460a0b2be8c31593a13180d.
Appreciate in advance for helping.

#8

I solved my headphone problem. It works fine now.

#9

What did you need to do to solve it ?

#10

I just needed to be a little more careful with writing characters!! I went to Yast then Hardware then Sound and edit chosen driver model to asus-v1s. The problem was my own mistake where I wrote vls instead of v1s. Now my headphone works correctly.