From: Ray Lee <ray-lk@madrabbit.org>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: Christian Hartmann <cornogle@googlemail.com>,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: Q: Why I do have to restart alsa everytime after a resume from disk/ram ? Is this alsa- or kernel or config related??
Date: Sun, 13 Dec 2009 15:27:48 -0800 [thread overview]
Message-ID: <2c0942db0912131527x118f9689oe1dc128543f4fc27@mail.gmail.com> (raw)
In-Reply-To: <4B22DD11.7000905@gmail.com>
On Fri, Dec 11, 2009 at 4:00 PM, Robert Hancock <hancockrwd@gmail.com> wrote:
> On 12/11/2009 03:21 AM, Christian Hartmann wrote:
>>
>> hello list,
>>
>> everytime I suspended to disk or to ram, regardless of the used kernel
>> (git or stable from distri), I must restart alsa to hear sound again.
>> searched google and tried a lot but still the same awful behaviour.
>> Has anybode some suggestions for me? is this alsa related ? or is this
>> a kernel issue which could be dealt here?
>
> I'm not sure what you mean by restarting ALSA, do you mean reloading the
> audio device module or something?
>
> You didn't mention which kind of sound hardware you were using either..
Data point: Older versions of PulseAudio are very picky about the
timing data that comes back from ALSA, and throws a hissy-fit and goes
and sulks if it believes it's getting lied to. Perhaps you need to try
upgrading the PulseAudio packages, and try again.
next prev parent reply other threads:[~2009-12-13 23:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 9:21 Q: Why I do have to restart alsa everytime after a resume from disk/ram ? Is this alsa- or kernel or config related?? Christian Hartmann
2009-12-12 0:00 ` Robert Hancock
2009-12-12 21:51 ` Christian Hartmann
2009-12-13 20:30 ` Robert Hancock
2009-12-13 23:27 ` Ray Lee [this message]
2009-12-14 15:16 ` Christian Hartmann
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=2c0942db0912131527x118f9689oe1dc128543f4fc27@mail.gmail.com \
--to=ray-lk@madrabbit.org \
--cc=alsa-devel@alsa-project.org \
--cc=cornogle@googlemail.com \
--cc=hancockrwd@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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