Takashi Iwai composed on 2015-12-07 21:35 (UTC+0100):
Felix Miata wrote:
Usually you don't need to configure via YaST nowadays. Rather better to avoid it as much as possible.
IME, this is often the case, but hardly universal. Unfortunately when sound doesn't "just work", getting it to work is commonly an unduly frustrating ordeal.
2-No comprehensive sound configuration utility. Takashi responded "YaST setup is only for the kernel module." Why is that?
Because it's the only thing you can set up commonly in the system level. All the rest depends on your DE and your choice of sound backend setup, including the choice of packages and the choice of plugins.
Why is it in cases where sound does not "just work", is YaST2 (often) incapable of producing a test sound except in the process of initially configuring it? This happens to me time and again, in different releases dating back years, and on different hardware, though nearly always Intel chipset motherboards with onboard Intel sound device (typically using snd-intel8x0 driver on a business Dell PC Optiplex line model). In the current TW, 13.2 and 13.1 cases (not that preciptating thread's OP), again as observed many times past, going through "Advanced setup with possibility to change options", on reaching "Settings for sound card", volume's initial level is 0. Why would 0 ever be the initial value on a previously "unconfigured" sound device?
In your case, excluding PA, fiddling the system-level sound setup via YaST, then shuffling the sound layer setups...; no surprise that it doesn't always work flawlessly.
I never "excluded PA". I simply did not choose to install it, and nothing requiring it required it be installed. Only later I took the trouble to add it myself, unfortunately without changing results.
Look at the graphics setup. Few people fiddle with xorg.conf today. Most of graphics setups are done in a more dynamic way instead.
The similar trend is found for sound setup, too. You *shouldn't* change the system setup unless you know what you're doing. This is the way many DEs want / try to go. Instead, the sound setup is done in an upper level, typically in PulseAudio, then covered by more APIs on it like gstreamer, phonon, etc.
I don't see how "upper layers" can be expected to be successful regardless of choice of "upper layers" if YaST2 can't produce sound more than during initial configuration of the only sound device. FWIW, a possibly related problem I frequently encounter is some failure or another requires a forced reboot. CAD commonly fails to force the reboot, with flooding/repeated messages whild holding down "failed to store sound card state". -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org