From: Takashi Iwai <tiwai@suse.de>
To: Aki Parviainen <aki.parviainen@iki.fi>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
perex@perex.cz
Subject: Re: PROBLEM: snd_intel_hda audio regression in 2.6.36-rc5
Date: Wed, 22 Sep 2010 17:36:11 +0200 [thread overview]
Message-ID: <s5hr5gl6b9w.wl%tiwai@suse.de> (raw)
In-Reply-To: <AANLkTi=Tctwyz=wLWSpf09Ex18wNgHqDv7PRSxXQ8LTw@mail.gmail.com>
At Wed, 22 Sep 2010 18:31:26 +0300,
Aki Parviainen wrote:
>
> >
> > So, you are testing only over SPDIF output, right?
>
> Yes, I'm only using SPDIF output!
>
> > Looks like the SPDIF status bits has been reset by some reason.
> > Try to restore via iecset program included in alsa-utils package,
> > e.g.
> > iecset original on
> > iecset category 0x02
>
> I tried this and didn't notice any difference.
Hm, then you might need to adjust other parameters, too.
> > If this doesn't help, try to unload sound driver once, remove (or
> > backup) /etc/asound.state (which might be in a different path
> > depending on the distro), then load sound modules again.
> > This will restore the default SPDIF status. Unmute / adjust mixer
> > setups appropriately after doing this.
>
> I also tried this but didn't notice a difference but however I noticed
> a workaround to this problem that might be related to deleting the
> asound.state (debian places it btw to /var/lib/alsa/asound.state): now
> the regular audio works via SPDIF once again if I first play a file
> with digital preencoded audio. Ie:
>
> -Boot with 2.6.36-rc5
> -Start kaffeine
> -Play mp3 file -> no sound at all via spdif
> -Play mkv file with 5.1 sound -> sound ok
> -Play mp3 file again -> sound ok!
> -Exit kaffeine & restart kaffeine or vlc
> -Play mp3 file again -> sound ok!
At this state, run "alsactl store", and keep the renewed asound.state
file. Once when this happens again, just run like
alsactl -f /your/saved/asound.state store
to restore the status.
> Unfortunately the fix isn't permanent because after reboot I cannot
> get regular sound via spdif until I have once played a file with 5.1
> audio track.
This is unlikely a kernel issue but the user-space issue.
I guess this was triggered because of changes of the id numbers in
mixer elements. Some user-space program (e.g. kmix) tend to restore
the mixer setup forcibly but often wrongly.
Takashi
prev parent reply other threads:[~2010-09-22 15:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 17:32 Aki Parviainen
2010-09-22 9:31 ` Takashi Iwai
[not found] ` <AANLkTikgOaBizi2z+AuAgD+anvmc+kG3z9KTqfzXs1zm@mail.gmail.com>
2010-09-22 14:30 ` Aki Parviainen
2010-09-22 14:40 ` Takashi Iwai
2010-09-22 15:31 ` Aki Parviainen
2010-09-22 15:36 ` Takashi Iwai [this message]
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=s5hr5gl6b9w.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=aki.parviainen@iki.fi \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
/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
all inboxes | Powered by JetHome®