|
Bugzilla – Full Text Bug Listing |
| Summary: | Yast sound card can't be configured, the alternative driver is not used | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Walddys Emmanuel Dorrejo Céspedes <dev.dorrejo> |
| Component: | YaST2 | Assignee: | YaST Team <yast-internal> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Major | ||
| Priority: | P4 - Low | CC: | dev.dorrejo, jslaby, tiwai |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| URL: | https://trello.com/c/IV9tunV0 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | descriptive picture | ||
|
Description
Walddys Emmanuel Dorrejo Céspedes
2019-09-26 18:15:20 UTC
Created attachment 819660 [details]
descriptive picture
(In reply to Walddys Emmanuel Dorrejo Céspedes from comment #0) > And can't found snd_soc_skl on /lib/modules It's snd-soc-skl.ko in /lib/modules/<version>/kernel/sound/soc/intel/skylake/. Could you attach dmesg output after it fails in yast? (In reply to Jiri Slaby from comment #2) > (In reply to Walddys Emmanuel Dorrejo Céspedes from comment #0) > > And can't found snd_soc_skl on /lib/modules > > It's snd-soc-skl.ko in > /lib/modules/<version>/kernel/sound/soc/intel/skylake/. > > Could you attach dmesg output after it fails in yast? Hello, after i run the config on yast, on dmesg appear this new line: [ 6800.031529] snd_soc_skl 0000:00:1f.3: The DSP is not enabled on this platform, aborting probe (In reply to Walddys Emmanuel Dorrejo Céspedes from comment #3) > Hello, after i run the config on yast, on dmesg appear this new line: > > [ 6800.031529] snd_soc_skl 0000:00:1f.3: The DSP is not enabled on this > platform, aborting probe That hardware should be handled by the legacy driver. This is likely a yast bug if it insists on loading snd_soc_skl for this card. (In reply to Jiri Slaby from comment #4) > That hardware should be handled by the legacy driver. Um, YaST uses the "modinfo" tool to get the driver for the configured card. Unfortunately the PCI IDs reported by the snd_soc_skl driver are also covered by the snd_hda_intel driver. So the snd_soc_skl driver is used just because it's first found. How can YaST know if the card requires the snd_soc_skl or the snd_hda_intel driver? Or should YaST just try the other one if the first used fails? this is a more clean detail lspci -nnk 00:1f.3 Audio device [0403]: Intel Corporation Cannon Lake PCH cAVS [8086:a348] (rev 10) DeviceName: Onboard - Sound Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1219] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_soc_skl, sof_pci_dev alsa-info.sh : https://pastebin.com/54yQccCj There is an implicit rule that the driver gets loaded in alphabetical order, and that's how the things working on such systems. So, if you have multiple entries, try to pick up the first alphabetic one, unless it's blacklisted in the module configuration. (In reply to Takashi Iwai from comment #9) > There is an implicit rule that the driver gets loaded in alphabetical order Ah, that's the missing detail! Thanks! Is fixed, after some updates, yast can configure my sound card, but when the volume on some frequency crack, on windows this not happend. Fixed |