I have been trying to get th linuxmce up and running for 4 days now and slowly thing work until I have to reload and try something different to get things work. Don't get me wrong, its fustrating but at the same time I am learning a lot.

Anyhow I have video on the AV wizard, not out of the DVI yet, but no audio from the Strawberry Blonde during the installation. If I start the UI diagnostics tool I can hear the audio from the video of the flame thrower. Are the any special setups to get the audio?

I too have the A8N-E and issues with the sound. Out-of-the-box the Realtek ALC850 chipset doesn't work (over S/PDIF anyways). I am attempting to compile enough useful information to post a fix for this board as it is rather irritating. For over a year I had a working KnoppMyth installation with this very board, _but_, I didn't document all the steps necessary to get it working. Live and learn I suppose. Hopefully I can post this information soon.

I will be reinstalling from the QuickStart DVD tonight, so perhaps in a few days I can have the fix compiled. Here's hoping.

I did get the sound partially working and will get the information posted as soon as I can. I have stereo output working through the optical out on the board, but have had no success with the AC3 pass-through. One step at a time. Just wanted to put in an update.

If you are using spdif make sure you unmute IEC958 in alasmixer settings.run alsamixer from a terminal and press m to toggle the mute setting on IEC958

good luck

Tim

That, unfortunately, didn't get me anywhere with the out-of-the-box installation.

I needed to take a few extra steps to get the chipset to output through the spdif optical. Granted I only got the stereo output and no AC3 pass-through. However, http://wiki.linuxmce.org/index.php/Changing_Xine_Player_Audio_Settings might have some more useful information on how to circumvent the built-in xine commands. I'll have to pull my old working xine config file from the Knoppmyth install where this was all working fine. Accoding to the wiki: "M = Manual, if the flag is present, the whole configuration string will be ignored and defaults from /etc/pluto/xine.conf won't be overridden." Perhaps I need to take this step, but at least for now the sound is working, albeit without AC3.

##### DEVICE NAMES ###### This configuration file defines four devices for use by the user. Those# devices are "analog", "mixed-analog", "digital", and "mixed-digital". The# user may also re-define "default" to be identical to one of the above-named# devices (i.e. to send all sound output to the digital output unless otherwise# specified). Use the device names as described below:# - "analog" outputs to the analog output directly and (at least on software# sound cards) blocks other audio output. After playback completes, "queued"# sounds are output in sequence.# - "mixed-analog" mixes audio output from multiple programs into the analog# output (so you can hear beeps, alerts, and other noises while playing back# an audio stream).# - "digital" outputs to the digital output directly. Since most (all?)# digital outputs expect 48kHz PCM audio, this may not work for some playback# (i.e. CD's--which are 44.1kHz PCM audio--or 32kHz audio streams from TV# recordings, etc.).# - "mixed-digital"

# All other devices created within this file are used only by the configuration# file itself and should /not/ be used directly. In other words, do not use# the devices "analog-hw", "dmix-analog", "digital-hw", or "dmix-digital".

##### IMPORTANT ###### To make this ALSA configuration file work with your sound card, you will need# to define the appropriate card and device information for the "analog-hw" and# "digital-hw" devices below. You can find the card and device information# using "aplay -l".

##### Configuration File #####

# Override the default output used by ALSA. If you do not override the# default, your default device is identical to the (unmixed) "analog" device# shown below. If you prefer mixed and/or digital output, uncomment the# appropriate four lines below (only one slave.pcm line).## Note, also, that as of ALSA 1.0.9, "software" sound cards have been modified# such that their default "default" device is identical to the "mixed-analog"# device. Whether using an ALSA version before or after 1.0.9, it does no harm# and has no affect on performance to redefine the device (even if the# redefinition does not change anything). Also, by using this ALSA# configuration file, you once again have access to unmixed analog output using# the "analog" device.pcm.!default { type plug ## Uncomment the following to use "mixed-analog" by default # slave.pcm "dmix-analog" ## Uncomment the following to use (unmixed) "digital" by default slave.pcm "digital-hw" ## Uncomment the following to use "mixed-digital" by default # slave.pcm "dmix-digital"}

# Alias for (converted) analog output on the card# - This is identical to the device named "default"--which always exists and# refers to hw:0,0 (unless overridden)# - Therefore, we can specify "hw:0,0", "default", or "analog" to access analog# output on the card# - Note that as of ALSA 1.0.9, "software" sound card definitions redefine# "default" to do mixing, meaning this device is different from "default" and# allows playback while blocking other sound sources (until playback# completes).pcm.analog { type plug slave.pcm "analog-hw"}

# The following devices are not useful by themselves. They require specific# rates, channels, and formats. Therefore, you probably do not want to use# them directly. Instead use of of the devices defined above.

# Alias for analog output on the card# Do not use this directly--it requires specific rate, channels, and formatpcm.analog-hw { type hw card 0 # The default value for device is 0, so no need to specify # - Uncomment one of the below or create a new "device N" line as appropriate # for your sound card or # device 1 # device 4}

# Alias for digital (S/PDIF) output on the card# Do not use this directly--it requires specific rate, channels, and formatpcm.digital-hw { type hw card 0 # device 1 # - Comment out "device 1" above and uncomment one of the below or create a # new "device N" line as appropriate for your sound card or device 2 # device 4}

We should probably get some information from others using the CK804 and ALC850 chipsets to see if their hardware addresses for the optical can be automatically applied. I've read of differences (hw0,2 hw 0,0 hw 0,4 etc) between the cards that could be problematic. Or does this need to be applied to a broader range of cards that use the snd-intel8x0 driver.

I'm willing to help out in any way I can, but I'm not a good "proper" scripter. I can usually hack something out, but that doesn't mean that it's good.

I had this issue with different sound cards, i do not know if it helps with spdif but when this occurs i runsudo alsaconf from a shell then i get sound on the standard stereo output of the soundcard. Then i run again the AVWizard and it all wroks fine

pcm.asym_spdif { type asym playback.pcm "spdif_playback" capture.pcm "plughw:0"}While perusing the source code on svn.charonmedia.org I noticed http://svn.charonmedia.org/trac.cgi/browser/vendor/pluto-lmce-branch/config-pkgs/intel8x0/mkr_postinst.sh is supposed to handle the creation of the asound.conf file that pluto should use. I honestly don't ever remember seeing that file in that format. Makes me wonder if that file will work correctly. Guess I'll have to try it along with the Manual configuration settings I mentioned earlier. Perhaps I can get to that this weekend sometime.

##### DEVICE NAMES ###### This configuration file defines four devices for use by the user. Those# devices are "analog", "mixed-analog", "digital", and "mixed-digital". The# user may also re-define "default" to be identical to one of the above-named# devices (i.e. to send all sound output to the digital output unless otherwise# specified). Use the device names as described below:# - "analog" outputs to the analog output directly and (at least on software# sound cards) blocks other audio output. After playback completes, "queued"# sounds are output in sequence.# - "mixed-analog" mixes audio output from multiple programs into the analog# output (so you can hear beeps, alerts, and other noises while playing back# an audio stream).# - "digital" outputs to the digital output directly. Since most (all?)# digital outputs expect 48kHz PCM audio, this may not work for some playback# (i.e. CD's--which are 44.1kHz PCM audio--or 32kHz audio streams from TV# recordings, etc.).# - "mixed-digital"

# All other devices created within this file are used only by the configuration# file itself and should /not/ be used directly. In other words, do not use# the devices "analog-hw", "dmix-analog", "digital-hw", or "dmix-digital".

##### IMPORTANT ###### To make this ALSA configuration file work with your sound card, you will need# to define the appropriate card and device information for the "analog-hw" and# "digital-hw" devices below. You can find the card and device information# using "aplay -l".

##### Configuration File #####

# Override the default output used by ALSA. If you do not override the# default, your default device is identical to the (unmixed) "analog" device# shown below. If you prefer mixed and/or digital output, uncomment the# appropriate four lines below (only one slave.pcm line).## Note, also, that as of ALSA 1.0.9, "software" sound cards have been modified# such that their default "default" device is identical to the "mixed-analog"# device. Whether using an ALSA version before or after 1.0.9, it does no harm# and has no affect on performance to redefine the device (even if the# redefinition does not change anything). Also, by using this ALSA# configuration file, you once again have access to unmixed analog output using# the "analog" device.pcm.!default { type plug## Uncomment the following to use (unmixed) "analog" by default# slave.pcm "analog-hw"## Uncomment the following to use "mixed-analog" by default# slave.pcm "dmix-analog"## Uncomment the following to use (unmixed) "digital" by default# slave.pcm "digital-hw"## Uncomment the following to use "mixed-digital" by default# slave.pcm "dmix-digital"}

# Alias for (converted) analog output on the card# - This is identical to the device named "default"--which always exists and# refers to hw:0,0 (unless overridden)# - Therefore, we can specify "hw:0,0", "default", or "analog" to access analog# output on the card# - Note that as of ALSA 1.0.9, "software" sound card definitions redefine# "default" to do mixing, meaning this device is different from "default" and# allows playback while blocking other sound sources (until playback# completes).pcm.analog { type plug slave.pcm "analog-hw"}

# The following devices are not useful by themselves. They require specific# rates, channels, and formats. Therefore, you probably do not want to use# them directly. Instead use of of the devices defined above.

# Alias for analog output on the card# Do not use this directly--it requires specific rate, channels, and formatpcm.analog-hw { type hw card 0 # The default value for device is 0, so no need to specify# - Uncomment one of the below or create a new "device N" line as appropriate# for your sound card or # device 1# device 4}

# Alias for digital (S/PDIF) output on the card# Do not use this directly--it requires specific rate, channels, and formatpcm.digital-hw { type hw card 0 device 1# - Comment out "device 1" above and uncomment one of the below or create a# new "device N" line as appropriate for your sound card or # device 2# device 4}

amixer set IEC958 unmuteamixer set 'IEC958 Playback AC97-SPSA' 0amixer set 'IEC958 Playback Source' PCMPlease somebody verify these as I'd like to get this finalized on the wiki as well. Any input on the proper formatting on the wiki page would also be appreciated.

I too have an asound.state file located at /var/lib/alsa/, however, I have not modified that file and it also has a modification date of "2008-02-24 20:00" which happens to be the last time I restarted the machine. I believe that the /etc/asound.state is used at boot to configure the /var/lib/alsa file. I could be wrong so please, if I am, somebody correct me.

The avi files I have played seem to send the DD signal correctly. I'll do some more checking though.

I had to _create_ /etc/asound.state with the information stated previously. Sorry if I neglected to mention that. Did you modify the /var/lib/alsa/asound.state file? If you didn't have to create the /etc/asound.state file it might be possible that some of this problem has been fixed in the 0710 release. Mine didn't work correctly until I created the /etc/asound.state file under 0704.