Latest working kernel version: 2.6.17 / 2.6.22.1 Earliest failing kernel version: Distribution:Mandriva Hardware Environment:AMD64 Software Environment: Problem Description: Digital Output is broken with SB Live 5.1: "SB Live Analog/Digital Output Jack" I read some thread about it: http://readlist.com/lists/vger.kernel.org/linux-kernel/85/429383.html And wasn't able to get SPDIF out working again through controls. (My speakers 5.1 decoder monitors the line status, and so I was able to see that no valid digital signal was coming from the cable). I finally made it... by plugging the digital out 3.5 plug half the way ! So there's something changed in the SPDIF digital output jack control. The working configuration with 2.6.17 (2.6.22 too ?) kernels is : amixer set 'IEC958 Optical Raw Playback Switch' 0 amixer set 'IEC958 Optical Raw' off amixer set 'SB Live Analog/Digital Output Jack' on But the control 'IEC958 Optical Raw Playback Switch' have now changed and is now bound to 2 values instead of just being a switch. I think the problem comes from this control wich now emits 2 signals (digital+digital, digital+analog?) instead of just one and the decoders gets confused. That's why plugging the 3.5" jack half way (mono) fixes cable signal.
Marked as a regression.
It's a problem of the user-space stuff. It has to be called properly with a command line option.
Not. Parameters are changed and restored through asound.state
Then get "alsactl -f somefile store" on both working and non-working kernels and upload to compare.
Created attachment 15118 [details] asound.state 2.6.22.1 Working
Created attachment 15119 [details] asound.state 2.6.24.2 non working
On the 2.6.24.2 version, the card also outputs mixed/analog signal on 3.5 Jack. (checked with headphones)
Thanks. I don't understand why you see the "IEC958 Optical Raw" has been changed. As you see in these files, its type is same...
I guessed it from my 2.6.17 amixer commands. So the problem might not come from this control so. So I have no more clues on what made the 3.5' Jack's behaviour to change.
I still think it's somehow alsactl screwed up the setting. Could you check the following? - Reboot once to single runlevel (i.e. the system without the sound modules loaded) - Remove /etc/asound.state or whatever the system-wide alsactl file. The file localtion depends on the distro - Go to your usual runlevel. At this stage, the sound should be "normal" (i.e. muted). - Adjust mixer setting again manually and try apps.
Created attachment 15121 [details] Clean working asound.state with 2.6.24.2, working That works now. I join the working asound states. I can see is that there's some PCM Routing access changes. Should we move this bug in the Alsa tools bugtracking or distro bugtracking ?
The recent ALSA utils (1.0.16 or later) should work better for such changes. So, (hopefully) it won't happen so often in future...