16 Dec
2010
16 Dec
'10
2:16 a.m.
On 12/16/2010 02:08 AM, Paul Davis wrote:
On Wed, Dec 15, 2010 at 8:06 PM, Paul
Davis<paul(a)linuxaudiosystems.com> wrote:
Yes, I checked that. I was reading up on .asoundrc on the alsa
unofficial wiki.
Alsa, I noticed that aplay -L gave me an error after I had made a typo
in .asoundrc, so it's definitely doing something.
#ls -l .asoundrc
-rw-r--r-- 1 ailo ailo 69 2010-12-16 02:01 .asoundrc
--
ailo
On Wed, Dec 15, 2010 at 7:14 PM,
ailo<ailo.at(a)gmail.com> wrote:
also, check /etc/share/alsa/alsa.conf for this block of text, or
something very much like it:
@hooks [
{
func load
files [
"/etc/asound.conf"
"~/.asoundrc"
]
errors false
}
]
this is how ~/.asoundrc is loaded. On 12/16/2010 12:26 AM, ailo wrote:
that is what we were doing. what is the output of:
ls -l ~/.asoundrc
>> Apart from the aplay -L result at the end I got a lot of this:
>
> that's not what we're looking for. it should open ~/.asoundrc
> if it doesn't show with that command, use
>
> strace -e trace=file aplay -L
How can I make sure editing ~/.asoundrc has any effect?