Re: Re: 2.6.12-rc1-mm3, sound card lost id

[James Courtier-Dutton <James@superbug.co.uk>]

Lee Revell wrote:
> On Tue, 2005-03-29 at 23:13 +0200, Jean Delvare wrote:
> 
>>>+	{.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80271102,
>>>+	 .driver = "EMU10K1", .name = "SBLive! Value [CT4832]", 
>>>+	 .emu10k1_chip = 1,
>>>+	 .ac97_chip = 1} ,
>>
>>Unsurprisingly, my card is now named CT4832. I had to edit
>>/etc/asound.state manually to get my mixer settings back (with some
>>warnings, but I get some sound).
>>
>>Not sure I quite see the idea of renaming from "Live", which the user
>>will understand, to (I suppose) the exact chip name on the card, while
>>the user has certainly no idea what it is. But heh I'm not an ALSA
>>developer, there must be a good reason.
> 
> 
> Blame Creative.  They have released so many different cards under the
> Live! name that it's become meaningless.  There are now two separate
> classes of cards marketed as Live! (or Audigy) that don't even use the
> same driver (ca0106 and emu10k1x), the hardware isn't even similar.
> Unsurprisingly, the user confusion is massive.
> 
> The model number is the simplest unique identifier.  This is also what
> the "good" Windows drivers for these devices, http://www.kxproject.com,
> use.
> 
> Lee
> 

It looks to me that alsactl is to blame here.
If a user has 2 sound cards of exactly the same model, the state will
not be saved, as the state.xxxx will be the same for both cards.
I think we need to change alsactl to make the saved state unique.
Maybe a combination of driver name and card number, and not use short
name at all.
Any comments?


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click