Headphone Detection

English Multimedia
1

ASUS K52JT. The sound works except for the headphone jack. I’ve tried changing the model setting, but can’t get it to work that way. I can get sound through the headphones with HDA-Analyzer by checking the output box on Node 0x19 and unchecking it for Node 0x1F to turn off the speakers. Unfortunately it doesn’t seem to stick through restarts and I have no idea where to go from there.
ALSA info: http://www.alsa-project.org/db/?f=58d9b23420391b156a6c7cd7c4329d1cd0bfd1ef

Packages:

-----@linux-pfur:~> rpm -qa '*alsa*'
alsa-firmware-1.0.24.1-3.1.noarch
alsa-plugins-pulse-32bit-1.0.24-6.1.x86_64
alsa-plugins-1.0.24-6.1.x86_64
alsa-oss-1.0.17-32.1.x86_64
alsa-utils-1.0.24.2-3.1.x86_64
alsa-1.0.24.1-3.1.x86_64
alsa-plugins-pulse-1.0.24-6.1.x86_64

-----@linux-pfur:~> rpm -qa '*pulse*'
pulseaudio-0.9.22-6.9.1.x86_64
alsa-plugins-pulse-32bit-1.0.24-6.1.x86_64
libpulse-mainloop-glib0-0.9.22-6.9.1.x86_64
pulseaudio-module-jack-0.9.22-6.9.1.x86_64
pulseaudio-module-zeroconf-0.9.22-6.9.1.x86_64
libpulse-browse0-0.9.22-6.9.1.x86_64
pulseaudio-module-bluetooth-0.9.22-6.9.1.x86_64
libxine1-pulse-1.1.19-4.4.x86_64
libpulse0-32bit-0.9.22-6.11.1.x86_64
libpulse0-0.9.22-6.9.1.x86_64
pulseaudio-esound-compat-0.9.22-6.9.1.x86_64
alsa-plugins-pulse-1.0.24-6.1.x86_64
pulseaudio-module-lirc-0.9.22-6.9.1.x86_64
pulseaudio-utils-0.9.22-6.9.1.x86_64
pulseaudio-module-x11-0.9.22-6.9.1.x86_64

-----@linux-pfur:~> rpm -qa libasound2
libasound2-1.0.24.1-3.1.x86_64

-----@linux-pfur:~> uname -a
Linux linux-pfur.site 2.6.37.1-1.2-desktop #1 SMP PREEMPT 2011-02-21 10:34:10 +0100 x86_64 x86_64 x86_64 GNU/Linux

Sound conf:

options snd-hda-intel model=asus
options snd slots=snd-hda-intel
# u1Nb.yUttYMZUFR7:5 Series/3400 Series Chipset High Definition Audio
alias snd-card-0 snd-hda-intel

Help would be appreciated.

2

I note a Conexant CX20585 which I believe uses the same model options as the Conexant 5066, which has these options from the HD-Audio-Models.txt file (from the alsa documentation):


Conexant 5066
=============
  laptop	Basic Laptop config (default)
  hp-laptop	HP laptops, e g G60
  asus		Asus K52JU, Lenovo G560
  dell-laptop	Dell laptops
  dell-vostro	Dell Vostro
  olpc-xo-1_5	OLPC XO 1.5
  ideapad       Lenovo IdeaPad U150
  thinkpad	Lenovo Thinkpad

However you gave me inconsistent information !! You state in the 50-sound.conf file that you have applied the ‘asus’ option. But the diagnostic script has you having applied an option called ‘auto’. There IS no auto option for the Conexant 5066, yet I can see it has been applied:


!!Modprobe options (Sound related)
!!--------------------------------
snd-hda-intel: model=auto

I know you say you have applied various options, but what was posted (inconsistent information) simply suggests to me mistakes were made. With mistakes, then sound may not work properly. I don’t know what to believe here.

How about applying the model option which you state you applied (asus) and then run that script again !

Anyway, if asus is subsequently CORRECTLY applied (where the script suggests it was NOT applied) does not solve the problem, then my recommendations are to either (and/or) :

(1) update alsa being careful to do it properly. 80% of the users seem to mess it up because they deviate from updating, they don’t know how to use YaST/zypper properly (although they think they do) and they consequently fail to update their various alsa apps. Guidance here: SDB:Alsa-update - openSUSE Again, be certain you update properly. If your alsa versions are the same after updating as they were before, then you FAILED to update.

(2) write a bug report. Guidance here: openSUSE:Submitting bug reports - openSUSE When writing the bug report, use your openSUSE forum username and password to log on to bugzilla. Write the bug report against openSUSE-11.4 component sound. Run the script:


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

and attach to the bug report the file /tmp/alsa-info.txt that the script produces. Ensure the bug report is complete. The openSUSE sound packager (who is also an alsa sound developer) will NOT read a forum thread. And ensure the script is consistent with the other information you provide, and don’t have it inconsistent as per above as that will just delay things as the packager examines the problem. Ensure you check the bug report every now and then, and when answering a question from the packager be certain to CLEAR the ‘need info’ flag.

3

I was trying anything and apparently forgot to change it back before running the ALSA script.

Anyways, updated ALSA and everything is working fine now. Thanks for the help.

4

Excellent ! Congratulations on getting this to work.

A caution about the updated alsa rpms … if you also installed alsa-driver-kmp-desktop per the web page I noted with instructions for updating alsa, … the alsa-driver-kmp-desktop tends to be kernel version specific. This means if you update alsa, part or all of your sound could be broken, until you update alsa again to the latest alsa-driver-kmp-desktop. The SuSE-GmbH sound packager (who is also a sound developer) maintains those rpms , and typically within a day t a week of a new kernel update he will produce new rpms consistent with the new kernel.

Also I recommend you only update alsa when absolutely necessary, …those rpms are very cutting edge and have fixes that may not yet have been accepted upstream … so exercise caution if further updates are needed.

Congratulations again on getting this to work with the latest alsa.