Carlos E. R. wrote:
On 2022-06-26 10:08, Per Jessen wrote:
Carlos E. R. wrote:
On 2022-06-25 12:57, Per Jessen wrote:
Just clean as far as the sound config goes. Simply get rid of the pulseaudio stuff configured by yast.
No idea what files YaST writes, what services it starts.
Looking at the yast source code, it is all about pulseaudio. If you take a look at /etc/pulse/, I'm sure you will see recently changed files.
Nope. Elesar:~ # tree --si -D /etc/pulse/
Interesting, mine looks 99% similar.
Elesar:~ # tree --si -D /etc/modprobe.d/ /etc/modprobe.d/ ├── [3.6k Dec 7 2021] 00-system.conf ├── [1.3k Dec 6 2021] 10-unsupported-modules.conf ├── [ 308 Jun 17 9:33] 20-kernel-default-extra.conf ├── [5.3k Dec 6 2021] 50-blacklist.conf ├── [ 128 Nov 24 2021] 50-bluetooth.conf ├── [ 33 May 25 2018] 50-ipw2200.conf ├── [ 34 May 25 2018] 50-iwl3945.conf ├── [ 18 May 25 2018] 50-prism54.conf ├── [ 103 Jun 26 8:11] 50-sound.conf <=========== ├── [ 1 Jun 26 8:11] 50-sound.conf.YaST2save
Okay.
Bingo.
Elesar:~ # cat /etc/modprobe.d/50-sound.conf
options snd slots=snd-hda-intel # svHJ.YhraNp3EzIA:SB1040 PCI Express alias snd-card-0 snd-hda-intel
It's only giving the card an alias name, I can't imagine that screwing anything up.
Yep. It's a matter of attitude, that's all.
No, it is a machine in production, people depend on it. I'm sure you are aware of the constraints.
Do they all depend on the sound working, 24x7 ? :-) -- Per Jessen, Zürich (24.2°C)