From: Anssi Hannula <anssi.hannula@iki.fi>
To: VDR User <user.vdr@gmail.com>
Cc: mailing@alsa-project.org, alsa-dev <alsa-devel@alsa-project.org>,
list@alsa-project.org
Subject: Re: Bug in setting channels, related to recent ELD/EDID changes?
Date: Thu, 23 Dec 2010 07:48:02 +0200 [thread overview]
Message-ID: <4D12E292.9050204@iki.fi> (raw)
In-Reply-To: <AANLkTikneYHc9NmrRW41=xRBW_PVgc0jqdcOaTgHcC-t@mail.gmail.com>
On 23.12.2010 04:22, VDR User wrote:
> Hi. After updating my stable kernel from 2.6.35.7 to 2.6.36.2, I get
> a problem when tuning HDTV channels that use surround sound. The
> error I get is as follows:
>
> audio_alsa_out: Cannot set number of channels to 6 (err=-22:Invalid argument)
> audio_out: open failed!
>
> With the following xine error:
> ---------------------- (ERROR) ----------------------
> The audio device is unavailable. Please verify if another program
> already uses it.
>
> ['Audio device unavailable' '']
> ------------------ (END OF ERROR) -------------------
What are the contents of /proc/asound/NVidia/eld* and
/proc/asound/NVidia/codec* ?
> This problem did not exist in 2.6.35.7 alsa drivers (using
> snd-hda-intel). I have noticed that there has been recent changes
> associated with ELD/EDID that sets limitations on channels. First of
> all I think this is a horrible idea since many devices don't even
> contain correct EDID. It's simply too unreliable to use.
Well, I haven't yet seen any EDID which contained incorrect audio
information. Also, in case we find no information in the ELD, all
channels and formats are allowed.
> Secondly,
> could the above problem be related to those changes?
It could.
> If anyone knows a fix for this or can point me in the right direction
> (aside of going back to 2.6.35.7), PLEASE fill me in.
>
> Here are some system specs:
> debian testing
> kernel snd-hda-intel driver used for hdmi audio on nvidia gt240 video card
> hdmi going to 7.1 surround sound receiver & setup
>
> Any help is greatly appreciated!
>
> Best regards,
> Derek
--
Anssi Hannula
next prev parent reply other threads:[~2010-12-23 5:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 2:22 Bug in setting channels, related to recent ELD/EDID changes? VDR User
2010-12-23 5:48 ` Anssi Hannula [this message]
2010-12-23 7:13 ` VDR User
2011-01-02 10:16 ` Anssi Hannula
2011-01-04 16:41 ` VDR User
2011-01-04 18:46 ` James Courtier-Dutton
2011-01-06 8:43 ` VDR User
2011-01-10 19:13 ` VDR User
2011-01-10 19:51 ` Takashi Iwai
[not found] ` <3a46493bd2a1ec3b74c89cb6970c9ab0.squirrel@mail.onse.fi>
[not found] ` <s5hk4icjy2t.wl%tiwai@suse.de>
2011-01-11 16:33 ` Anssi Hannula
2011-01-11 16:42 ` Takashi Iwai
2011-01-11 16:54 ` Anssi Hannula
[not found] ` <s5hbp3nkj1z.wl%tiwai@suse.de>
2011-01-11 16:58 ` Anssi Hannula
2011-01-11 17:34 ` Takashi Iwai
2011-01-11 20:37 ` VDR User
2011-01-11 20:47 ` Anssi Hannula
2011-01-12 6:37 ` VDR User
2011-01-12 6:47 ` Takashi Iwai
2011-01-22 2:53 ` VDR User
2011-01-24 13:32 ` Takashi Iwai
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=4D12E292.9050204@iki.fi \
--to=anssi.hannula@iki.fi \
--cc=alsa-devel@alsa-project.org \
--cc=list@alsa-project.org \
--cc=mailing@alsa-project.org \
--cc=user.vdr@gmail.com \
/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