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: Fri, 02 Apr 2010 00:52:27 +0300	[thread overview]
Message-ID: <hp34j2$fn6$1@dough.gmane.org> (raw)
In-Reply-To: <z2i4f3252891004010705h8dfe2f71q20de60626a9b8941@mail.gmail.com>

Raymond Yau wrote:
> 2010/3/29 Angel Tsankov <fn42551@fmi.uni-sofia.bg>
> 
>> Raymond Yau wrote:
>>
>>> 2010/3/29 Angel Tsankov <fn42551@fmi.uni-sofia.bg>
>>>
>>>  Raymond Yau wrote:
>>>>> 2010/3/26 Angel Tsankov <fn42551@fmi.uni-sofia.bg>
>>>>>
>>>>>  Hello again!
>>>>>> I've recently had some time to investigate this problem further on and
>>>>>> here's what I've discovered:
>>>>>>
>>>>>> Raymond Yau wrote:
>>>>>>
>>>>>>> 2010/2/26 Pacho Ramos <pacho@condmat1.ciencias.uniovi.es>
>>>>>>>
>>>>>>>  El vie, 26-02-2010 a las 13:57 +0200, Angel Tsankov escribió:
>>>>>>>>> Raymond Yau wrote:
>>>>>>>>>
>>>>>>>>>> 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'.
>>>>>>>>>>>>>>  your problem is "alsactl restore" become "alsactl init" when
>>>>>>> the number
>>>>>>>
>>>>>> of
>>>>>>
>>>>>>> controls is more than those in state file.
>>>>>>>
>>>>>> I'm not quite sure that the case is this since 'alsactl restore' does
>>>>>> restore the values of the Yamaha sound card (and those of the other
>>>>>> card, too) and 'alsactl restore 1' seems to just initialize the Yamaha
>>>>>> card.  This is with alsa-utils version 1.0.22.
>>>>>>
>>>>>>  "Hardware is initialized using a guess method "  is the message used
>>>>> by
>>>>> alsactl init
>>>>>
>>>>>
>>>>>
>>>> http://git.alsa-project.org/?p=alsa-utils.git;a=commitdiff;h=9a748178d1c9e783242f0cc794ab3efb27092f34;hp=0c02a4e3d23c7b5d03215f1bfaba9f70ed11e9b7
>>>>
>>>> I don't get what you mean. Could you explain a little bit more?
>>>>
>>>>  post the output of alsa-info.sh after  "alsactl init"
>>> and immeditate after the system boot
>>>
>> I'm sending the requested output as an attachment.
> 
> As you can see the driver has 79 controls but only 48 controls saved in the
> asound.state
> 
> that is why "alsactl restore" become "alsactl init"
> 
> 
> !!Amixer output
> !!-------------
> 
> !!-------Mixer controls for card 0 [YMF724F]
> 
> Card hw:0 'YMF724F'/'Yamaha DS-1 (YMF724F) at 0xfb000000, irq 5'
>   Mixer name    : 'SigmaTel STAC9700,83,84'
>   Components    : 'AC97a:83847600'
>   Controls      : 79
>   Simple ctrls  : 31

My question was why 'alsactl restore' restores the sound card and 
'alsactl restore 1' just initializes the card.

Angel Tsankov

  reply	other threads:[~2010-04-01 21:52 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
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 [this message]
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='hp34j2$fn6$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.