You have no mentions about audio chip you’re trying to use.
IMHO YaST audio setup is broken.
Try to delete all cards, restart, add all available cards, configure them, save settings, restart, test with DE sound goodies.
Check in YaST which audio device you are configuring by seeing Volume settings - onboard audio ALC1220/870/etc. has multiple outputs, a contraria to HDMI/DP.
YaST’s sound test may not work.
Try to use alsamixer (in a console).
It’s an ALC887-VD, but I think that this is not the issue as the chip is correctly detected if I re-configure via YaST2. Also, the chip is directly connected to the CPU “standard” audio interface, the driver is “snd_hda_intel” (I indeed forgot to merntion that).
I deleted all audio devices, restarted, and added them again - no difference, after another restart I have no audio again. If I change the volume settings via YaST2, I see all levers, the name is “Family 17h (Models 00h-0fh) HD Audio Controller”, no reference to the ALC887.
What however does not work is the test sound via YaST2, even after reconfiguring.
No difference, after restart and before reconfiguring, alsamixer says that no sound cards are insatalled. After reconfiguring, everything is ok.
So YaST2 is somehow not totally wrong as it correctly idenifies and configures the audio HW, I “just” need to do it after every restart.
I note your kernel is Kernel release 5.3.18-59.19-preempt so one nominally expect that it is supported. I would not recommend you use the preempt kernel - possibly that is your problem.
The dmesg reports:
1.949550] hdaudio hdaudioC0D0: Unable to bind the codec
1.954551] hdaudio hdaudioC1D0: Unable to bind the codec
If the codec can’t be bound, I assume that means the alsa driver won’t properly load.
I recommend you go back to a default kernel.
Its puzzling that alsa is not loading. You could also try installing (if not already installed) alsa-firmware and kernel-firmware.
I needs to be taken into account that audio works if I recondigute it using YaST, without loading any additional SW or changing the kernel, as explained in the original post.
Meanwhile I also realized that if I only remove the 2nd (never used) audio device (“Baffin HDMI/DP Audio [Radeon RX…]”) within YaST, then the 1st audio device (“Family 17h (Models 00h-0fh) HD Audio Controller”) jumps to work - without reconfiguring it.
I did the alsa-info.sh again, the results are here.
**3400G:~ #** journalctl -b -q -o short-monotonic _KERNEL_SUBSYSTEM=usb -g 1-10
4.285598] 3400G kernel: usb 1-10: new full-speed USB device number 3 using xhci_hcd
4.619244] 3400G kernel: usb 1-10: New USB device found, idVendor=1130, idProduct=1620, bcdDevice= 1.40
4.619249] 3400G kernel: usb 1-10: New USB device strings: Mfr=0, Product=2, SerialNumber=0
4.619251] 3400G kernel: usb 1-10: Product: USB AUDIO
5.125610] 3400G kernel: **usb ****1-10****: Warning! Unlikely big volume range (=17152), cval->res is probably wrong.**
5.125614] 3400G kernel: **usb ****1-10****: [2] FU [PCM Playback Volume] ch = 2, val = 0/17152/1**
**3400G:~ #**
Presumably audio starts too early on your system for some reason. What are your device units?
**3400G:~ #** systemctl list-unit-files '*sound*'
UNIT FILE STATE VENDOR PRESET
alsasound.service **alias **-
sound-extra.service static -
sound.target static -
3 unit files listed.
**3400G:~ #** systemctl list-units '*sound*'
UNIT LOAD ACTIVE SUB DESCRIPTION
sys-devices-pci0000:00-0000:00:01.2-0000:01:00.0-usb1-1\x2d10-1\x2d10:1.0-sound-card0-controlC0.device loaded active plugged USB_AUDIO
sys-devices-pci0000:00-0000:00:08.1-0000:08:00.1-sound-card1-controlC1.device loaded active plugged /sys/devices/pci0000:00/0000:00:08.1/0000:08:00.1/sound/card1/controlC1
sys-devices-pci0000:00-0000:00:08.1-0000:08:00.6-sound-card2-controlC2.device loaded active plugged /sys/devices/pci0000:00/0000:00:08.1/0000:08:00.6/sound/card2/controlC2
sound.target loaded active active Sound Card
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
**4 loaded units listed.** Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
**3400G:~ #**
However, I just installed some updates - and now it works. It seems that no kernel or firmware files were updated, but a lot systemd- and udev-related stuff was.
Thank you for the assistance - plus reputation for everyone trying to help me !