I had the same reaction after my dist-upgrade of unstable as of today (April 24th). No sound. I use aumix to adjust the mixer (I don't know about alsamixer). All my settings are zeroed; but contrary to what the original submitter of this TR observes, using aumix to adjust the settings to something normal does not help - I *still* have no sound, and the settings do not survive reboot.
There is nothing wrong with the driver load and "udev" setup of devices - it works as always. But I fear that the problem may not be exclusively related to ALSA. I downgraded all the alsa packages alsa-base_1.0.11-1_all.deb libasound2-dev_1.0.11-2_i386.deb libasound2_1.0.11-2_i386.deb alsa-utils_1.0.11-1_i386.deb libasound2-doc_1.0.11-2_all.deb linux-sound-base_1.0.11-1_all.deb to the 1.0.10 versions. Now my mixer settings survive reboot - as before. But still I have no sound! I suspect that there may be problems with sound in the KDE upgrade that also arrived today: 3.5.2-1 to 3.5.2-2. I haven't yet tried to back out that upgrade (it is pretty big!). For the record, my sound is built-in on an AsRock K7S8X, version 3.0 motherboard; it uses (according to lspci) SiS sound controller. My kernel is the current unstable Debian 2.6.16 (2.6.16-9). Honestly, I consider upgrading the level of this TR to something release-critical. You know, an upgrade of the sound system, and now I have no sound.... best regard -- Peder Chr. Nørgaard e-mail: [EMAIL PROTECTED] Gefionsvej 19 spejder-e-mail: [EMAIL PROTECTED] DK-8230 Åbyhøj tel: +45 87 44 11 99 Denmark mob: +45 30 91 84 31
