From: Raymond Yau <superquad.vortex2@gmail.com>
To: alsa-devel@alsa-project.org
Subject: Re: alsactl restore: unknown hardware: ymf724f
Date: Fri, 26 Feb 2010 07:11:20 +0800 [thread overview]
Message-ID: <4f3252891002251511p4605f104jdac236e589d01149@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1002251502380.28127@eeebox2.perex-int.cz>
2010/2/25 Jaroslav Kysela <perex@perex.cz>
> On Thu, 25 Feb 2010, Angel Tsankov wrote:
>
> > Jaroslav Kysela wrote:
> >> On Thu, 25 Feb 2010, Angel Tsankov wrote:
> >>
> >>> Hello,
> >>>
> >>> I run 'alsactl restore' on a machine with 2 sound cards -- a built-in
> >>> Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev
> >>> 02) and a non-built-in Yamaha Corporation YMF-724F [DS-1 Audio
> >>> Controller] (rev 03) -- and get the following message:
> >>>
> >>> Unknown hardware: "YMF724F" "SigmaTel STAC9700,83,84" "AC97a:83847600"
> >>> "0x1073" "0x000d"
> >>> Hardware is initialized using a guess method
> >>>
> >>> As a consequence the volume levels of the Yamaha card do not get
> >>> restored to the levels stored in /etc/asound.state. The volume levels
> >>> of the built-in card however are properly restored. The asound.state
> >>> file has been created by executing 'alsactl store'.
> >>>
> >>> The kernel has been built with support for ALSA. I've built and
> >>> installed the kernel modules for both cards (not the ones in the
> >>> alsa-driver package but those that come with kernel version 2.6.30.2).
> >>> Any ideas why alsactl cannot find the hardware it has previously
> >>> identified as "YMF724F", "SigmaTel STAC9700,83,84", and so on?
> >>
> >> The logic of alsactl is to restore the state from /etc/asound.state if
> it
> >> is valid. It seems like the set_controls() function in alsactl/state.c
> >> returns an error code for a reason.
> >>
> >> Could you try to compile the latest alsa-utils snapshot
> >> (http://www.alsa-project.org/snapshot/) and run './alsactl -d restore'
> in
> >> alsa-utils/alsactl directory? A warning (fail reason) should be printed.
> >
> > I've attached a bash shell script that I used to download, configure,
> > compile, and run alsactl. I've also attached a .log file with stdout and
> > stderr that I got while executing the script.
>
> Thanks. I've added more debug print lines to state.c. Could you rerun your
> script and append also '/etc/asound.state' file and output from
> 'alsa-info.sh --no-upload' to your output tarballs? Send me this tarball
> privately or just an URL to this list.
>
> Thanks,
> Jaroslav
>
>
did alsactl restore those IFACE_PCM volume since they are supposed at 0dB by
default whenever the subdevice is open ?
store the values in asound.state seem to be for debugging only
control.61 {
comment.access 'read write inactive'
comment.type INTEGER
comment.count 2
comment.range '0 - 32768'
iface PCM
subdevice 1
name 'PCM Playback Volume'
value.0 26214
value.1 26214
}
next prev parent reply other threads:[~2010-02-25 23:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 7:54 alsactl restore: unknown hardware: ymf724f Angel Tsankov
2010-02-25 8:25 ` Jaroslav Kysela
2010-02-25 13:31 ` Angel Tsankov
2010-02-25 14:05 ` Jaroslav Kysela
2010-02-25 23:11 ` Raymond Yau [this message]
2010-02-26 11:57 ` Angel Tsankov
2010-02-26 14:05 ` Pacho Ramos
2010-02-26 16:36 ` Angel Tsankov
2010-02-27 7:14 ` Raymond Yau
2010-02-28 1:29 ` Raymond Yau
2010-03-26 8:28 ` Angel Tsankov
2010-03-28 12:52 ` Raymond Yau
2010-03-28 21:37 ` Angel Tsankov
2010-03-29 1:10 ` Raymond Yau
2010-03-29 8:09 ` Angel Tsankov
2010-04-01 14:05 ` Raymond Yau
2010-04-01 21:52 ` Angel Tsankov
2010-04-01 22:52 ` Raymond Yau
2010-02-27 2:06 ` Raymond Yau
2010-02-27 8:09 ` Angel Tsankov
2010-02-27 8:37 ` Raymond Yau
2010-02-27 9:53 ` Angel Tsankov
2010-02-27 10:03 ` Angel Tsankov
2010-02-27 15:19 ` Angel Tsankov
2010-02-27 11:21 ` Raymond Yau
2010-02-27 13:45 ` Raymond Yau
2010-02-27 14:46 ` Angel Tsankov
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=4f3252891002251511p4605f104jdac236e589d01149@mail.gmail.com \
--to=superquad.vortex2@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).