[Pkg-alsa-devel] Bug#481515: Bug#481515: alsa-utils: 'alsactl restore' fails on ICE1724 soundcards

[Martin Roll]

Elimar Riesebieter schrieb:
> On Sun, 01 Jun 2008 the mental interface of
> Martin Roll told:
>
>   
>> Elimar Riesebieter schrieb:
>>     
>>> On Thu, 29 May 2008 the mental interface of
>>> Martin Roll told:
>>>
>>>       
>>>   
>>>       
>>>> This is my asound.state
>>>>
>>>> Martin
>>>>     
>>>>         
>>> 	control.1 {
>>> 		comment.access read
>>> 		comment.type BYTES
>>> 		comment.count 52
>>> 		iface CARD
>>> 		name 'ICE1724 EEPROM'
>>> 		value '1153153b13020b80fcc3ffff5f0000000000000000000000000000000000000000000000000000000000000000000000ffff5f00'
>>>     }
>>>
>>>
>>> 	control.56 {
>>> 		comment.access read
>>> 		comment.type BYTES
>>> 		comment.count 10
>>> 		iface PCM
>>> 		device 1
>>> 		name 'IEC958 Q-subcode Capture Default'
>>> 		value '00000000000000000000'
>>> 	}
>>>
>>> These are both useless, aren't they? 
>>>       
>> I think so.
>>
>>     
>>> Do you have a customized
>>> asoundrc flowing around?
>>>       
>> No, I don't have an asoundrc.
>>
>>     
>>> You could try the following:
>>>
>>> # alsactl -P restore
>>>   
>>>       
>> alsactl doesn't accept the option -P as documented in the manpage but it
>> accepts --pedantic instead. Using the pedantic option has unfortunately
>> no effect. Same error messages.
>>
>>     
>>> or delete the above mentioned controls and do
>>>
>>> # alsactl restore
>>>   
>>>       
>> Removing the mentioned controls manually and invoking alsactl restore
>> seemed to have the desired effect at first. There were no more error
>> messages. But when I tried to store the settings (alsactl store) and
>> then to restore them, my "beloved" error messages reappeared. The
>>     
>
> Hmm, checking the source (driver|utils) I didn't found something
> similar to "IEC958 Q-subcode Capture Default" or "comment.type BYTES"
> or "name 'ICE1724 EEPROM'". Are you sure, there is no manipulation
> of an asound file neither in /etc nor in $HOME? 

I double checked my system again and yes, I'm sure, there is no asound
file in /etc nor in my user accounts' $HOME (including /root) and
nothing else has been manipulated.

> Did you made a test
> as root?
>
>   

Yes I did. The mentioned control entries (#1 and #56) are being restored
to /var/lib/alsa/asound.state every time you invoke "alsactl store" (and
thats exactly what the system does while shutting down). Unfortunately,
removing the entries from asound.state is futile.
(I hope that's what you meant with "test").

Seems pretty weird...

> Elimar
>
>   

Martin