Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dave <inssomniak@mountaincable.net>
To: alsa-devel@lists.sourceforge.net
Subject: iec958 controls dissapeared from alsamixer/amixer and spdif no longer works
Date: Mon, 06 Feb 2006 23:07:07 -0500	[thread overview]
Message-ID: <43E81CEB.40707@mountaincable.net> (raw)

I tried this on the -user mailing list with no luck, maybe someone here 
can help me troubleshoot my problem

Recently without changing any thing regarding sound configuration on 
this one machine, the iec958 mixer controls dissapeared, and can no 
longer use the iec958/spdif port of my SI7012/alc655 chipset using the 
snd-intel8x0 driver in kernel 2.6.15 using alsa-lib/tools/headers 
1.0.11-rc2 and rc3 versions of alsa.

Analog controls are all there, and work, I try to use the spdif port and 
get:

alsa-init: 1 soundcard found, using: spdif
ALSA lib setup.c:549:(add_elem) Cannot obtain info for CTL elem 
(MIXER,'IEC958 Playback Default',0,0,0): No such file or directory


using mplayer as an example

and:

Using PCM device 'plug:iec958:{AES0 0x2 AES1 0x82 AES2 0x0 AES3 0x2}'
ALSA lib setup.c:549:(add_elem) Cannot obtain info for CTL elem 
(MIXER,'IEC958 Playback Default',0,0,0): No such file or directory
snd_pcm_open: No such file or directory
Output open failed

trying with ac3dec.


I changed nothing originally, but updated to -rc3 to try to fix it.
It all worked perfectly before some unknown force caused it to cease.

 



Thanks!




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642

                 reply	other threads:[~2006-02-07  4:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43E81CEB.40707@mountaincable.net \
    --to=inssomniak@mountaincable.net \
    --cc=alsa-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox