From: Ed Wright <edo.wright@gmail.com>
To: alsa-devel@lists.sourceforge.net
Subject: Re: intel-hda, 965 chipset, STAC9227 - problem - resolved
Date: Mon, 15 Jan 2007 19:46:33 +0900 [thread overview]
Message-ID: <45AB5B89.600@gmail.com> (raw)
In-Reply-To: <45A6488F.4010808@gmail.com>
Turns out the problem had nothing to do with my earlier guesses.
Running an strace on aplay showed that even though alsa-lib and
alsa-utils were compiled/installed with the default "prefix" (/usr), the
utilities were looking for alsa.conf, etc. under /usr/local for some reason.
Anyway, I symlinked the directory and all seems to be working.
Ed
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
prev parent reply other threads:[~2007-01-15 10:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 14:24 intel-hda, 965 chipset, STAC9227 - problem Ed Wright
2007-01-15 10:46 ` Ed Wright [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=45AB5B89.600@gmail.com \
--to=edo.wright@gmail.com \
--cc=alsa-devel@lists.sourceforge.net \
/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).