Are you re-using the same /home for these tests / installations ?
Have you tried with a new user to see if sound works with the new user ?
I use a nis server so no local user accounts are there (except for a fresh 42.1 / tumbleweed install which doesn’t support nis at istall so a dummy user has to be configured).
Now I have a nearly working system with a great flaw:
Installed 13.1, configured everything (kdm, vnc, needed software,…), upgraded to tumbleweed:
sound works, x system works, remote login works,
BUT
when I start any yast module I get:
> /sbin/yast2 sw_single &
Error loading language plugin /usr/lib64/YaST2/plugin/libpy2lang_ruby.so: /usr/lib64/YaST2/plugin/libpy2lang_ruby.so: undefined symbol: _ZNK11SymbolEntry8toStringB5cxx11Eb
/usr/lib/YaST2/bin/y2base: symbol lookup error: /usr/lib64/YaST2/plugin/libpy2UI.so.2: undefined symbol: _Z16should_be_loggediRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE
Without Yast I fear I have to edit all the config files manually assuming I know which and where they are…
Any idea what went wrong?
After upgrading from 13.1 didn’t work I now made a fresh install of tumbleweed. As lightdm let the remote Xming crash I installed kdm and copied the config files from the previous install.
Now I have a working system with sound, x system, remote login and working yast. (took me a while)
Concluding I state that starting with 13.1 on these mainboards leads to multiple errors and dysfunctional sound and graphics.
Even a fresh install of 42.1 could not handle the graphics - maybe the chipset (intel B150 express) is not fully supported yet by this release.
I’ll stay with tumbleweed on this hardware for now waiting what 42.2 (probably 11/16) will do.
All the other machines stay with 13.1 - now evergreen (never change a running system - at least as long as security patches are available)
Thread can be closed.