From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: No sound for several minutes after reboot
Date: Tue, 30 Aug 2016 10:32:01 +0200 [thread overview]
Message-ID: <20160830083201.GA5031@x4> (raw)
In-Reply-To: <s5hbn0a3cow.wl-tiwai@suse.de>
On 2016.08.30 at 10:04 +0200, Takashi Iwai wrote:
> On Mon, 29 Aug 2016 16:02:33 +0200,
> Markus Trippelsdorf wrote:
> >
> > On 2016.08.29 at 14:06 +0200, Markus Trippelsdorf wrote:
> > > On 2016.08.29 at 11:32 +0200, Takashi Iwai wrote:
> > > > On Mon, 29 Aug 2016 11:20:47 +0200,
> > > > Markus Trippelsdorf wrote:
> > > output:ALSA def-222 [003] .... 422.035002: hda_send_cmd: [0000:00:14.2:0] val=0x01570d01
> > > output:ALSA def-222 [003] .... 422.035061: hda_get_response: [0000:00:14.2:0] val=0x00000000
> >
> > Actually it right here that sound starts again:
> >
> > markus@x4 hda-emu % ./a.out 0x01570d01
> > raw value = 0x01570d01
> > cid = 0, nid = 0x15, verb = 0x70d, parm = 0x01
> > raw value: verb = 0x70d, parm = 0x1
> > verbname = set_digi_cvt_1
>
> So, the program itself sets the value. Which sound backend are you
> using? PulseAudio, whatever?
No backend at all. I use mpd directly on type hw:
pcm.!default {
type hw
card 0
device 3
}
> Basically you need to track the verb 0x01570dXX that changes the
> digital converter parameter.
>
> When the driver was loaded and initialized, what value does the node
> have? Also check the raw ctl elements, too. The value is controlled
> via "IEC958 Status" controls. If the value at the init time is wrong,
> you may set the initial value via "iecset" program included in
> alsa-utils.
The driver is build directly into my monolithic kernel (I don't have
modules enabled at all).
At boot time I run "alsactl restore" in an init script.
alsamixer shows that S/PDIF is unmuted, but as I wrote it doesn't work
for several minutes. If I toggle the S/PDIF setting in alsamixer from
unmuted to muted to unmuted then sounds starts working.
Anyway:
/usr/bin/hda-verb /dev/snd/hwC0D0 0x15 SET_DIGI_CONVERT_1 0x01 &> /dev/null
works fine in my init script, so the issue is solved for me.
Thanks.
--
Markus
next prev parent reply other threads:[~2016-08-30 8:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160827095018.GA309@x4>
[not found] ` <20160827113908.GA312@x4>
2016-08-29 8:15 ` No sound for several minutes after reboot Takashi Iwai
2016-08-29 8:33 ` Markus Trippelsdorf
2016-08-29 8:39 ` Takashi Iwai
2016-08-29 8:56 ` Markus Trippelsdorf
2016-08-29 9:05 ` Markus Trippelsdorf
2016-08-29 9:16 ` Takashi Iwai
2016-08-29 9:20 ` Markus Trippelsdorf
2016-08-29 9:32 ` Takashi Iwai
2016-08-29 9:40 ` Markus Trippelsdorf
2016-08-29 12:06 ` Markus Trippelsdorf
2016-08-29 14:02 ` Markus Trippelsdorf
2016-08-30 8:04 ` Takashi Iwai
2016-08-30 8:32 ` Markus Trippelsdorf [this message]
2016-08-30 9:03 ` Takashi Iwai
2016-08-30 9:20 ` Markus Trippelsdorf
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=20160830083201.GA5031@x4 \
--to=markus@trippelsdorf.de \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).