Bug 121860

Try ac97_quirk=hp_only or ac97_quirk=none module option for snd-intel8x0.

If both don't help, attach the latest /etc/asound.state and
/proc/asound/card0/codec97#0/* files.

Created attachment 53752 [details]
/etc/asound.state

Created attachment 53753 [details]
ac97#0-0

Created attachment 53754 [details]
ac97#0-0+regs

BTW, yast only accept digital values for this parameter from -1 to 7

Idid edit /etc/modprobe.d/sount to add ac97_quirk=hp_only then alsasound reload,
but nothing better than without ...

attached what you have requested.

Best Regards

MaNU

Any change with ac97_quirk=none ?

Hi,

whatever value I give to ac97_quirk, it doesn't work the way it is intended to;
I tryed none, hp_only and all values from -1 to 7 : the green jack remains dumb.

with value 7, rcalsasound reload gives me : 

/usr/sbin/alsactl: set_control:873: failed to obtain info for control #48 (No
such file or directory)

with value 3 : 
/usr/sbin/alsactl: set_control:894: warning: name mismatch (Surround Playback
Switch/Master Playback Switch) for control #7
/usr/sbin/alsactl: set_control:896: warning: index mismatch (0/0) for control #7
/usr/sbin/alsactl: set_control:894: warning: name mismatch (Surround Playback
Volume/Master Playback Volume) for control #8
/usr/sbin/alsactl: set_control:896: warning: index mismatch (0/0) for control #8
/usr/sbin/alsactl: set_control:894: warning: name mismatch (Master Playback
Switch/Surround Playback Switch) for control #9
/usr/sbin/alsactl: set_control:896: warning: index mismatch (0/0) for control #9
/usr/sbin/alsactl: set_control:898: failed to obtain info for control #9
(Operation not permitted)


And I'm sure it's not a hardware problem as when I still had 9.3 and 10.0RC1
installed , it worked fine under 9.3 and bad like now with 10.0RC1.

I Guess a lot of things have changed for alsa between 9.3 and 10.0 ...

Best Regards

MaNU

The messages of alsactl are harmless.  You can ignore them.

I don't see problems in the files you attached, so currently no idea what's wrong.
It might be different from the driver, but the library or app.

Could you run just "aplay foo.wav" with a 2ch WAV file?  If it doesn't work, try "aplay -Dhw foo.wav" (assuming that no other programs are accessing the sound device).

Do I understand correctly that the onboard sound on the ASUS P4P800 does not work? If yes, it does for me. with the boxed 10.0. However after installing an (old) SB Audigy Yast cannot configure it (alsaconf can). See bug 96965 comment #13.

Hi,

sorry for the delay, was Really busy!

anyway, back to this problem, it turns out to be a quite stupid thing : I was expecting front and back channels to work with a 2 way ch configured in alsamixer! I've been fooled by its (really) bad gui ... but all is clear when launching it in a terminal. :-) 

Turning it to 4 ch "solved my problem".

Important thing I noticed : 

after log out/in,  I always get those weird settings from alsamixer (pcm muted, headphone jack sense, 2ch) even if I configure them properly and manually store them with :

# sudo alsactl /etc/asound.state store

trying add some "sudo alsactl -f /etc/asound.state restore" here and there doesn't work : I had to manually enter it in an xterm after gui is up.

Looking at /var/log/messages, I noticed a strange message about modprobe complaining about inserting sonypi module ... 

After commenting out the two lines about that module in /etc/modprobe.conf, my sound problems went away : the stored configuration is correctly restored at login.

Hope this will help someone!

Thanks a lot.

Closing as invalid as the "real bug isn't the one I opened the bug for!