From: Steven Young <sdyoung@miranda.org>
To: alsa-devel@alsa-project.org
Subject: Re: Sound trouble with MCP61 chipset.
Date: Sat, 22 Sep 2007 14:15:09 -0400 [thread overview]
Message-ID: <20070922181509.GJ30453@miranda.org> (raw)
In-Reply-To: <1190428691.9924.20.camel@razman.gruemaster.com>
On Fri, Sep 21, 2007 at 07:38:11PM -0700, Tobin Davis wrote:
> On Fri, 2007-09-21 at 18:44 +0200, Takashi Iwai wrote:
>
> > It's way too old :) Try 1.0.15rc2, first.
>
> If you still have problems after installing 1.0.15rc2, please run
> http://bulletproof.servebeer.com/alsa/scripts/alsa-info.sh and send me
> the resulting link. It's probably too late to make 1.0.15, but I should
> be able to get you a patch that will make the next release.
Actually, 1.0.15rc2 fixed my problem. I should have thought of trying
the latest version before asking alsa-devel.
Thanks to everyone for their help! I am listening to Bust A Move in
stereo at this very instant.
Steve.
next prev parent reply other threads:[~2007-09-22 18:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 18:02 Sound trouble with MCP61 chipset Steven Young
2007-09-20 14:29 ` Takashi Iwai
2007-09-21 16:41 ` Steven Young
2007-09-21 16:44 ` Takashi Iwai
2007-09-22 2:38 ` Tobin Davis
2007-09-22 18:15 ` Steven Young [this message]
2007-09-23 2:05 ` Steven Young
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=20070922181509.GJ30453@miranda.org \
--to=sdyoung@miranda.org \
--cc=alsa-devel@alsa-project.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