http://qa.mandrakesoft.com/show_bug.cgi?id=4344
------- Additional Comments From [EMAIL PROTECTED] 2003-28-07 00:15 ------- The description of this bug is misleading; the bug is invalid. The volume level is separate from the "muted" property; that is, a channel may have a non-zero volume yet still be muted. Being "muted" does not equal having the volume set to zero. Some mixers assume that if the volume is zero and the channel is muted and the user then raises the volume they would "of course" also wish the channel to be unmuted and thus unmute it, but this is not necessarily the only "correct" behaviour. alsamixer does not make this assumption, and so if the channel is both set to zero and muted you must raise the volume and also press "m" to unset the "muted" property before you hear sound. This is intended behaviour, not a bug. -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: I am using the ALSA driver "snd-via82xx" and have these rpms: libalsa-data-0.9.5-1mdk libalsa2-0.9.5-1mdk alsa-utils-0.9.5-1mdk At boot, the driver's channels are all mutes (at zero). Now, if alsamixer is used to unmute them (set non-zero values), it has no effect since no sound can be heard even if alsamixer shows 100 for PCM and Master. However, if some other mixer (such as aumix) is used to unmute the sound channels to any non-zero values, alsamixer starts working fine. In brief, alsamixer cannot increase the volume (Master and PCM channels) if it starts from zero. This is a serious problem since after booting the ALSA drivers are muted and therefore it is impossible to get sound using alsamixer.
