Distribution: Debian GNU/Linux 'unstable/sid' Hardware Environment: (lspci -v) 0000:02:05.0 Multimedia audio controller: Creative Labs SB Audigy (rev 03) Subsystem: Creative Labs SB0090 Audigy Player/OEM (lspci -v -n) 0000:02:05.0 0401: 1102:0004 (rev 03) Subsystem: 1102:0053 Software Environment: After initial boot all goes fine, fire up xmms or whatever and behold no sound. Problem Description: Sound card was presented to userspace as 'Audigy' in 2.6.11 now presented as 'Unknown'. This means the mixer settings etc. were all for a 'different' sound card, hence, digital output was switched on by (the driver?) default meaning I got no sound at all in my (more common) setup of having only regular speakers connected. I get the impression that the emu10k1 driver needs to be taught fully what my Audigy card is and the default for an 'Unknown' card should be to call it 'Audigy' as in the previous kernels so people are not bitten by this bug. Be nice to see a small patch to correct this behaviour in the 2.6.12.x patch series as currently the new driver breaks sound for at least all people with my soundcard. I can do debugging/supply more information if you want. I presume most of the required information is at http://pciids.sourceforge.net/ though. Thanks for the work on the ALSA system, depsite this little regression, I do rather like it :-) Steps to reproduce: Upgrade to 2.6.12 from 2.6.11
This bug has been fixed in the alsa cvs (see http://alsa-project.org) It has been merged upstream, and is present in 2.6.13-rc3-mm1
Can you please confirm that 2.6.13-rc4 is now working OK?
With 2.6.13-rc4 it is now detected as an Audigy and displayed as such between the []. I'll check now that this makes sure the userspace restores the mixer settings correctly when I next reboot into it, and test rc5 instead for good measure.
yep works absolutely fine now. There was a bit of complaining from alsactl on initial mixer setting restore about various tuning nobs not found or Operation not permitted but a subsequent save / restore cycle has made those disappear. Plays an mp3 fine. So yes all working fine again and I am sure for people going straight from 2.6 <=2.6.11.11 to 2.6.13 things should work just fine.