|
Bugzilla – Full Text Bug Listing |
| Summary: | YaST2 sound configurator wrongly creates /etc/modules-load.d/yast.conf | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Jesper Goll <jesper> |
| Component: | YaST2 | Assignee: | E-mail List <yast2-maintainers> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | 64bit | ||
| OS: | openSUSE Tumbleweed | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Jesper Goll
2021-02-01 19:52:39 UTC
Thanks for the report! The file /etc/modules-load.d/yast.conf is created by the Kernel.rb library: https://github.com/yast/yast-yast2/blob/06c67e0398a3f81ae1cbcfdab4baebd9eb633460/library/system/src/modules/Kernel.rb The modules-load.d directory is used by systemd: https://www.man7.org/linux/man-pages/man5/modules-load.d.5.html and the man page does say: > Note that it is usually a better idea to rely on the automatic > module loading by PCI IDs, USB IDs, DMI IDs or similar > triggers encoded in the kernel modules themselves instead > of static configuration like this. In fact, most modern > kernel modules are prepared for automatic loading already. In fact this problem has been reported before, we should raise its priority. *** This bug has been marked as a duplicate of bug 1116849 *** |