From: Pacho Ramos <pacho@condmat1.ciencias.uniovi.es>
To: Jaroslav Kysela <perex@perex.cz>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: Since kernel-2.6.32, alsactl fails to restore defaults
Date: Fri, 19 Feb 2010 12:25:15 +0100 [thread overview]
Message-ID: <1266578715.5249.2.camel@localhost.localdomain> (raw)
In-Reply-To: <1266174876.23964.10.camel@localhost.localdomain>
[-- Attachment #1.1: Type: text/plain, Size: 793 bytes --]
El dom, 14-02-2010 a las 20:14 +0100, Pacho Ramos escribió:
> El dom, 14-02-2010 a las 20:10 +0100, Jaroslav Kysela escribió:
> >
> > The files look good. The question is why the initialization is called
> > when a default state already exists (it shouldn't).
> >
> > Does 'alsactl -f test.state restore' show some messages? Use test.state
> > file you sent me.
> >
> > Jaroslav
> >
> > -----
> > Jaroslav Kysela <perex@perex.cz>
> > Linux Kernel Sound Maintainer
> > ALSA Project, Red Hat, Inc.
>
> Yes, it shows:
> # alsactl -f test.state restore
> Unknown hardware: "VIA8237" "Realtek ALC658D" "AC97a:414c4781" "0x147b"
> "0x1415"
> Hardware is initialized using a guess method
>
Any news on this? Do you need any more information? Thanks a lot :-)
[-- Attachment #1.2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
prev parent reply other threads:[~2010-02-19 11:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-14 14:05 Since kernel-2.6.32, alsactl fails to restore defaults Pacho Ramos
2010-02-14 18:20 ` Jaroslav Kysela
2010-02-14 19:00 ` Pacho Ramos
2010-02-14 19:10 ` Jaroslav Kysela
2010-02-14 19:14 ` Pacho Ramos
2010-02-19 11:25 ` Pacho Ramos [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=1266578715.5249.2.camel@localhost.localdomain \
--to=pacho@condmat1.ciencias.uniovi.es \
--cc=alsa-devel@alsa-project.org \
--cc=perex@perex.cz \
/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).