All of lore.kernel.org
 help / color / mirror / Atom feed
From: Angel Tsankov <fn42551@fmi.uni-sofia.bg>
To: alsa-devel@alsa-project.org
Subject: Re: alsactl restore: unknown hardware: ymf724f
Date: Thu, 25 Feb 2010 15:31:13 +0200	[thread overview]
Message-ID: <hm5u2i$2h7$1@dough.gmane.org> (raw)
In-Reply-To: <alpine.LNX.2.00.1002250915480.28127@eeebox2.perex-int.cz>

[-- Attachment #1: Type: text/plain, Size: 1763 bytes --]

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.
> 
>  					Jaroslav

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.


Regards,
Angel Tsankov

[-- Attachment #2: test-alsa-utils.log.tar.bz2 --]
[-- Type: application/octet-stream, Size: 7348 bytes --]

[-- Attachment #3: test-alsa-utils.tar.bz2 --]
[-- Type: application/octet-stream, Size: 382 bytes --]

[-- Attachment #4: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2010-02-25 13:31 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 [this message]
2010-02-25 14:05     ` Jaroslav Kysela
2010-02-25 23:11       ` Raymond Yau
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='hm5u2i$2h7$1@dough.gmane.org' \
    --to=fn42551@fmi.uni-sofia.bg \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.