hi,
when i plugin my headset @ the front jacks the sound works well, but my receiver doesn’t work over the optical output. When the SPDIF output is activated it lights in red (in windows)… mhh what can i do ? 
well my Hardware:
Shuttle SG31G2 (XPC) (onboard Sound HDA Intel Codec ALC 888)
Alsa Info
tsalsa.txt - nopaste.com (beta)
http://www.alsa-project.org/db/?f=05f8809328688f71ff311e726e1cf6f145860981
openSuse 11.0
KDE 3.5
kernel 2.6.25.18-0.2-pae
Your hardware is well beyond anything I have (the most powerful PC at our house is over 4 years old - coming 5 years next month). I did search on ALSA and noted updates to the alc888 which is in your PC:
Search results for ALC888 - AlsaProject
I’m curious to see you solve this, as I am contemplating a new PC purchase, and the GA-M57SLI-S4 motherboard I am thinking of purchasing has an ALC888 
Don’t forget to try different settings in your mixer. There are various digital and surround settings in the mixer to adjust.
The scripts suggest you have 1.0.16 of alsa installed. You could consider updating to 1.0.18 of alsa to get better support (possibly). Guidance for that is here: Alsa-update - openSUSE
Note you have to be very exact when following that page. You need to send 6 zypper commands … one group of 3 to install alsa, alsa-firmware, alsa-utils, alsa-tools, libasound2 (and any other alsa apps you have installed) per your openSUSE-11.0 version, and one group of 3 to install alsa-driver-kmp-pae per your 2.6.25.18-0.2 kernel.
ok it is updated
Advanced Linux Sound Architecture Driver Version 1.0.18.
Compiled on Nov 10 2008 for kernel 2.6.25.18-0.2-pae (SMP)
but nothing changed…
I need more information to assess your sound hardware/software configuration after the update.
Please, to provide the information, with your PC connected to the internet copy and paste the following into a gnome-terminal or konsole:
wget http://home.cfl.rr.com/infofiles/tsalsa && su -c 'bash ./tsalsa'
when prompted for a password please enter your root password. Please try to accurately answer the question on the number of plugs/jacks on your PC (for example my PC has 3 i/o plugs/jacks). When the script completes it will pass you a URL. Please post that URL here.
Also, please copy and paste the following into a gnome-terminal or konsole and post the output here.rpm -qa | grep alsa
rpm -qa | grep pulse
rpm -q libasound2
uname -a
cat /etc/modprobe.d/sound
Its possible a hand edit to your /etc/modprobe.d/sound file is needed. The model options for that file are listed here in this extract from the ALSA-Configuration.txt file:
ALC883/888
3stack-dig 3-jack with SPDIF I/O
6stack-dig 6-jack digital with SPDIF I/O
3stack-6ch 3-jack 6-channel
3stack-6ch-dig 3-jack 6-channel with SPDIF I/O
6stack-dig-demo 6-jack digital for Intel demo board
acer Acer laptops (Travelmate 3012WTMi, Aspire 5600, etc)
acer-aspire Acer Aspire 9810
medion Medion Laptops
medion-md2 Medion MD2
targa-dig Targa/MSI
targa-2ch-dig Targs/MSI with 2-channel
laptop-eapd 3-jack with SPDIF I/O and EAPD (Clevo M540JE, M550JE)
lenovo-101e Lenovo 101E
lenovo-nb0763 Lenovo NB0763
lenovo-ms7195-dig Lenovo MS7195
lenovo-sky Lenovo Sky
haier-w66 Haier W66
3stack-hp HP machines with 3stack (Lucknow, Samba boards)
6stack-dell Dell machines with 6stack (Inspiron 530)
mitac Mitac 8252D
clevo-m720 Clevo M720 laptop series
fujitsu-pi2515 Fujitsu AMILO Pi2515
3stack-6ch-intel Intel DG33* boards
auto auto-config reading BIOS (default)
But I need the above information that I asked for, so I can come up with a recommended edit to your /etc/modprobe.d/sound file.
tsalsa.txt - nopaste.com (beta)
linux-t8b8:/home # rpm -qa | grep alsa
alsa-utils-1.0.18.git20081031-2.1
alsa-driver-kmp-pae-1.0.18.20081110_2.6.25.18_0.2-4.1
alsa-plugins-1.0.16-57.1
alsa-firmware-1.0.17.git20080617-2.1
alsa-1.0.18.git20081030-1.1
alsa-tools-1.0.18.git20081030-1.1
alsa-oss-1.0.15-48.1
linux-t8b8:/home # rpm -qa | grep pulse
linux-t8b8:/home # rpm -q libasound2
libasound2-1.0.18.git20081030-1.1
linux-t8b8:/home # uname -a
Linux linux-t8b8 2.6.25.18-0.2-pae #1 SMP 2008-10-21 16:30:26 +0200 i686 i686 i386 GNU/Linux
linux-t8b8:/home # cat /etc/modprobe.d/sound
options snd slots=snd-hda-intel
# u1Nb.kZ1c+ntEU3C:82801G (ICH7 Family) High Definition Audio Controller
alias snd-card-0 snd-hda-intel
Interesting, …
when I look at this (from your first post):
and I compare it to this from your second post:
I am immediately struck by the fact with the second running of the script you have a second sound device ( ie a USB sound device) , that was not present with your first running of the script.
I don’t know what is going on? Was that USB device present when you ran the script the first time?
For me, it goes without saying, that one should try hard not to change the configuration in the middle of troubleshooting, as one can never know what affect that might be. My knowledge in this is not good enough that I can categorically state that a major configuration change (such as adding a new sound device) had no affect on the initial problem summary.
So my apologies, but I am a bit confused here. Where did the 2nd audio device come from?
You could try some edits to the /etc/modprobe.d/sound file, to see if it helps …
Recall my previous post where I noted the following is the content from the ALSA-Configuration.txt file for the ALC888:
ALC883/888
3stack-dig 3-jack with SPDIF I/O
6stack-dig 6-jack digital with SPDIF I/O
3stack-6ch 3-jack 6-channel
3stack-6ch-dig 3-jack 6-channel with SPDIF I/O
6stack-dig-demo 6-jack digital for Intel demo board
acer Acer laptops (Travelmate 3012WTMi, Aspire 5600, etc)
acer-aspire Acer Aspire 9810
medion Medion Laptops
medion-md2 Medion MD2
targa-dig Targa/MSI
targa-2ch-dig Targs/MSI with 2-channel
laptop-eapd 3-jack with SPDIF I/O and EAPD (Clevo M540JE, M550JE)
lenovo-101e Lenovo 101E
lenovo-nb0763 Lenovo NB0763
lenovo-ms7195-dig Lenovo MS7195
lenovo-sky Lenovo Sky
haier-w66 Haier W66
3stack-hp HP machines with 3stack (Lucknow, Samba boards)
6stack-dell Dell machines with 6stack (Inspiron 530)
mitac Mitac 8252D
clevo-m720 Clevo M720 laptop series
fujitsu-pi2515 Fujitsu AMILO Pi2515
3stack-6ch-intel Intel DG33* boards
auto auto-config reading BIOS (default)
Its possible the alsa autoprobe/configuration of your sound device did not work perfectly, and it may be possible by a hand edit to your /etc/modprobe.d/sound file to improve the configuration of your alsa sound driver. Try this edit to that file (where note all I did was add a 4th line):
options snd slots=snd-hda-intel
# u1Nb.kZ1c+ntEU3C:82801G (ICH7 Family) High Definition Audio Controller
alias snd-card-0 snd-hda-intel
options snd-hda-intel model=6stack-dig
save that, and then restart your alsa sound driver with **su -c ‘rcalsasound restart’**enter your root password when prompted for a password, and then test your sound. If the model option “6stack-dig” does not work, then replace “6stack-dig” with “6stack-dig-demo”, save the change, and restart your alsa sound driver, and retest the sound. You can do that with each option that I quoted from the ALSA-Configuration.txt file, until you find one that works.
Be certain to pay very careful attention to your mixer settings during each test. I don’t have the sort of system you are referring to, so my ability to provide a quality check on your mixer settings (as reported by tsalsa script) is very limited.
well, you’re the man 
it works rotfl!
with the mentioned configuration from you:
options snd slots=snd-hda-intel
# u1Nb.kZ1c+ntEU3C:82801G (ICH7 Family) High Definition Audio Controller
alias snd-card-0 snd-hda-intel
options snd-hda-intel model=6stack-dig
the optical out is lightning red and my receiver makes awesome sound ^^
thank you for your help
and yes the usb headset was plugged in before i started the openSuse installation
Fantastic!! Congratulations.
Thanks for this tidbit. I don’t have a USB headset myself, and sometimes trying to visualize what is taking place on another user’s PC pushes my ability to understand what is happening.
If I do go ahead and purchase the GA-M57SLI-S4 motherboard (for a new desktop, subject to my “Mrs” approval ) your testing/troubleshooting will benefit me also - in which case, an advance thank you!
Hy!
i have the same problem, but i can’t solve it. I have ga-ep43-ds3 mobo, i think 6stack-dig is what i need but if i write it the /etc/modprobe/sound, nothing happends. I can restart alsa with rcalsasound restart, but then pulse audio is quit then i can’t use it and will be no sound on the jacks at all. (when i try to start pulse audiocontrol: Connection failed: Connection refused)
i try to modify the etc/modprobe/sound file many times like this:
options snd-hda-intel model=6stack-dig enable=1 index=0
# u1Nb.d+x9W4UhE78:ICH10 HD Audio Controller
alias snd-card-0 snd-hda-intel
# NXNs.4ni5+t8Ozt3:RV635 Audio device [Radeon HD 3600 Series]
alias snd-card-1 snd-hda-intel
# u1Nb.d+x9W4UhE78:ICH10 HD Audio Controller
alias snd-card-0 snd-hda-intel
options snd-hda-intel model=6stack-dig
# NXNs.4ni5+t8Ozt3:RV635 Audio device [Radeon HD 3600 Series]
alias snd-card-1 snd-hda-intel
options snd slots=snd-hda-intel
# u1Nb.d+x9W4UhE78:ICH10 HD Audio Controller
alias snd-card-0 snd-hda-intel model=6stack-dig
# NXNs.4ni5+t8Ozt3:RV635 Audio device [Radeon HD 3600 Series]
alias snd-card-1 snd-hda-intel
This is my configuration right now, and i dont know where to go now. Yast sound configure is freeze when i try to reconfigure the ich10 card to default.
linux-pkgl:/etc/modprobe.d # linux-pkgl:/etc/modprobe.d # rpm -qa | grep alsa
alsa-plugins-pulse-1.0.18.git20081114-1.4
alsa-1.0.18.git20081120-1.1
alsa-oss-1.0.17.git20080715-2.23
alsa-tools-1.0.18.git20081114-1.3
alsa-plugins-1.0.18.git20081114-1.4
alsa-patch-bay-1.0.0-0.pm.2
alsa-firmware-1.0.17.git20080617-2.1
alsa-tools-gui-1.0.18.git20081114-1.3
alsa-utils-1.0.18.git20081114-1.3
linux-pkgl:/etc/modprobe.d # rpm -qa | grep pulse
alsa-plugins-pulse-1.0.18.git20081114-1.4
libpulse-browse0-0.9.11-2.25
libpulsecore4-0.9.11-2.25
libpulse0-0.9.11-2.25
gstreamer-0_10-pulse-0.9.7-42.pm.1
libpulse-mainloop-glib0-0.9.11-2.25
audacious-plugins-output-pulse-1.5.1-0.pm.9
linux-pkgl:/etc/modprobe.d # rpm -q libasound2
libasound2-1.0.18.git20081120-1.1
linux-pkgl:/etc/modprobe.d # uname -a
Linux linux-pkgl 2.6.25.18-0.2-pae #1 SMP 2008-10-21 16:30:26 +0200 i686 i686 i386 GNU/Linux
linux-pkgl:/etc/modprobe.d # cat /etc/modprobe.d/sound
options snd slots=snd-hda-intel
# u1Nb.d+x9W4UhE78:ICH10 HD Audio Controller
alias snd-card-0 snd-hda-intel
# NXNs.4ni5+t8Ozt3:RV635 Audio device [Radeon HD 3600 Series]
alias snd-card-1 snd-hda-intel
How can I confirm its the same problem? I need a script output like the previous poster provided.
Assuming 6stack-dig is the correct option, then IMHO this is the best configuration. Please change your /etc/modprobe.d/sound file to that.
Where is alsa-driver-kmp-pae ? You need to install that and reboot.
You may have other problems, but without a script output I can’t tell.
You may be able to run the script with /usr/sbin/alsa-info.sh
“How can I confirm its the same problem?”
Same because i have sound on the jacks, but dont have on the optical output.
So, i was installed alsa-driver-kmp-pae (Wich mirror have it? Because in my mirrors there is no file like this)
I changed the /etc/modprobe.d/sound file reboot then still no sound on spdif.
Here is the alsa-infofile:
http://www.alsa-project.org/db/?f=66897e74b9acd39fdcb20735f1983d0fee7c1509
Tanks!
here is a part of my /var/log/boot.msg Something wrong
Setting up the hardware clockdone
Activating device mapper...
WARNING: /etc/modprobe.d/tsalsa line 22: ignoring bad line starting with 'vers="2008-09-14"'
WARNING: /etc/modprobe.d/tsalsa line 23: ignoring bad line starting with 'dialg=$(which'
WARNING: /etc/modprobe.d/tsalsa line 24: ignoring bad line starting with ''
WARNING: /etc/modprobe.d/tsalsa line 25: ignoring bad line starting with 'dialog'
WARNING: /etc/modprobe.d/tsalsa line 26: ignoring bad line starting with 'faildialg=$?'
WARNING: /etc/modprobe.d/tsalsa line 27: ignoring bad line starting with ''
WARNING: /etc/modprobe.d/tsalsa line 28: ignoring bad line starting with ''
WARNING: /etc/modprobe.d/tsalsa line 29: ignoring bad line starting with 'dialog'
WARNING: /etc/modprobe.d/tsalsa line 30: ignoring bad line starting with 'dialog'
WARNING: /etc/modprobe.d/tsalsa line 31: ignoring bad line starting with 'spdifz="$(cat'
WARNING: /etc/modprobe.d/tsalsa line 32: ignoring bad line starting with 'dialog'
WARNING: /etc/modprobe.d/tsalsa line 33: ignoring bad line starting with 'model="$(cat'
WARNING: /etc/modprobe.d/tsalsa line 34: ignoring bad line starting with 'dialog'
WARNING: /etc/modprobe.d/tsalsa line 35: ignoring bad line starting with 'plugz="$(cat'
WARNING: /etc/modprobe.d/tsalsa line 36: ignoring bad line starting with 'dialog'
WARNING: /etc/modprobe.d/tsalsa line 37: ignoring bad line starting with 'num="$(cat'
WARNING: /etc/modprobe.d/tsalsa line 38: ignoring bad line starting with 'dialog'
WARNING: /etc/modprobe.d/tsalsa line 39: ignoring bad line starting with 'ext="$(cat'
WARNING: /etc/modprobe.d/tsalsa line 40: ignoring bad line starting with 'dialog'
WARNING: /etc/modprobe.d/tsalsa line 41: ignoring bad line starting with 'fresh="$(cat'
WARNING: /etc/modprobe.d/tsalsa line 61: ignoring bad line starting with 'echo'
WARNING: /etc/modprobe.d/tsalsa line 62: ignoring bad line starting with 'echo'
WARNING: /etc/modprobe.d/tsalsa line 63:
If you type in google, “openSUSE alsa update” the first “hit” you get is this a guide for updating alsa: Alsa-update - openSUSE
… and if you look carefully at it, you will see two repositories for updating you alsa … one for alsa, alsa-utils, alsa-oss, … etc :
http://download.opensuse.org/repositories/multimedia:/audio/openSUSE_11.0/
and one for alsa-driver-kmp-pae:
http://download.opensuse.org/repositories/multimedia:/audio:/KMP/openSUSE_11.0_Update/
Now if typing “opensuse alsa update” in google is too challenging, you can always check web pin. For example, if you type “alsa-driver-kmp-pae” in webpin, you get: Webpin
Now on that webpin page, pay very careful to the version numbers, because you MUST pick a alsa-driver-kmp-pae version that is consistent with your kernel.
And if you are going to update some of the alsa apps, IMHO you should update them all to be consistent. I think you definitely need alsa-driver-kmp-pae if you updated alsa (which from what I can see, you did)
From that I see you have an ALC888. As already posted in this thread, the current options for an ALC888 are as listed in the ALSA-Configuration.txt file, which has this for the ALC888:
ALC883/888
3stack-dig 3-jack with SPDIF I/O
6stack-dig 6-jack digital with SPDIF I/O
3stack-6ch 3-jack 6-channel
3stack-6ch-dig 3-jack 6-channel with SPDIF I/O
6stack-dig-demo 6-jack digital for Intel demo board
acer Acer laptops (Travelmate 3012WTMi, Aspire 5600, etc)
acer-aspire Acer Aspire 9810
medion Medion Laptops
medion-md2 Medion MD2
targa-dig Targa/MSI
targa-2ch-dig Targs/MSI with 2-channel
laptop-eapd 3-jack with SPDIF I/O and EAPD (Clevo M540JE, M550JE)
lenovo-101e Lenovo 101E
lenovo-nb0763 Lenovo NB0763
lenovo-ms7195-dig Lenovo MS7195
lenovo-sky Lenovo Sky
haier-w66 Haier W66
3stack-hp HP machines with 3stack (Lucknow, Samba boards)
6stack-dell Dell machines with 6stack (Inspiron 530)
mitac Mitac 8252D
clevo-m720 Clevo M720 laptop series
fujitsu-pi2515 Fujitsu AMILO Pi2515
3stack-6ch-intel Intel DG33* boards
auto auto-config reading BIOS (default)
So why is it you believe 6-stack-dig is the model for you? Did you try the other model options, and conclude 6-stack-dig was the best one for you?
I didn’t taught that 2 mirror is needed for 1 thing. I was put the multimedia mirror from that site, I didn’t know what is kmp, so now i updated from that mirror everything alsa too. I have 6jacks and 1 analog, 1 optical digital out. This is the same description as 6stack-dig. This is enough for me to think that this is the right option but sure i was try another otions like 3stack-dig, 6stack-dig, 3stack-6ch, 3stack-6ch-dig, 6stack-demo, auto. I will try now again whit the updated files.
I can’t restart rc alsasound.
linux-pkgl:/ # rcalsasound restart
Shutting down sound driver^C
And like its freeze, dont do nothing. Cant restart with yast too. Do the same, and can’t close the sound setup window.
This will happen with some model options, … It means that option did not work. … Just change the model option and keep trying.
But before yesterday i could restart with any option that i write in. So i think something is wrong with it right now. Anyway it have to shut down alsa no matter what, maybe cant start it with wrong option. If i go to ctrl+alt+f2 with no gui on it i can restart it.
I was try all the options now. set it in ctrl+alt+f2 then restart alsa, then go back to ctrl+alt+f7 test the sound and nothing heard on the amplifier >:(
Unless I can see exactly what you have installed now, I can’t help. Also, when you tried each model option, it is imperative that you checked your mixer.
Often, when restarting alsa, one’s mixer is shutdown, and one has to restart the mixer.
You should not have to go to <CTRL><ALT><F2> to restart alsa. You have something else wrong right now, and that could have skewered the results of your test, and made it not representative of proper behaviour. I recommend you fix that, and then try again, being careful to check your mixer.
I don’t know what to do now. alsaconf, alsamixer nothing show some reaction. I was reinstall all the installed alsa packages.