Bug 644684

Summary: YaST makes a broken sound configuration in /etc/modprobe.d/50-sound.conf
Product: [openSUSE] openSUSE 11.3 Reporter: Rob Fortune <rob.fortune>
Component: YaST2Assignee: Ladislav Slezák <lslezak>
Status: RESOLVED NORESPONSE QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P4 - Low    
Version: Final   
Target Milestone: ---   
Hardware: PC   
OS: openSUSE 11.3   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Rob Fortune 2010-10-07 17:09:50 UTC
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/534.8 SUSE/7.0.528.0 (KHTML, like Gecko) Chrome/7.0.528.0 Safari/534.8

Here is an example of file made by YaST:

cat 50-sound.conf~
options saa7134_alsa enable=1 index=0
alias snd-card-0 saa7134_alsa

But I don't have that soundcard? The file should look like this:

options snd_hda_intel enable=1 index=0
alias snd-card-0 snd_hda_intel

I have to chattr +i the file to stop YaST breaking the sound configuration.

Here is the information from hwinfo --sound


10: PCI 1b.0: 0403 Audio device                                                                                                                
  [Created at pci.318]                                                                                                                         
  Unique ID: u1Nb.QvGZV1Wy+TF                                                                                                                  
  SysFS ID: /devices/pci0000:00/0000:00:1b.0                                                                                                   
  SysFS BusID: 0000:00:1b.0                                                                                                                    
  Hardware Class: sound                                                                                                                        
  Model: "Intel 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller"                                                          
  Vendor: pci 0x8086 "Intel Corporation"                                                                                                       
  Device: pci 0x2668 "82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller"                                                    
  SubVendor: pci 0x1631 "Packard Bell B.V."                                                                                                    
  SubDevice: pci 0xe011                                                                                                                        
  Revision: 0x03
  Driver: "HDA Intel"
  Driver Modules: "snd_hda_intel"
  Memory Range: 0xf0100000-0xf0103fff (rw,non-prefetchable)
  IRQ: 25 (442 events)
  Module Alias: "pci:v00008086d00002668sv00001631sd0000E011bc04sc03i00"
  Driver Info #0:
    Driver Status: snd_hda_intel is active
    Driver Activation Cmd: "modprobe snd_hda_intel"
  Config Status: cfg=new, avail=yes, need=no, active=unknown


Reproducible: Always

Steps to Reproduce:
1. Configure something with YaST
Actual Results:  
It modifies my sound configuration, even when I never asked it to.

Expected Results:  
Not to change the sound configuration since I didn't ask it to, and if it has to then to choose the right module.

Vendor "Packard Bell" is a little irrelevant, the system has been heavily modified from it's original configuration, I included it in-case it has something to do with why YaST makes this odd choice.
Comment 1 Rob Fortune 2010-10-07 17:19:36 UTC
Actually, I do have a TV card in the machine (which I don't use and have not configured), that could be why it is doing this. But it's not my soundcard, YaST shouldn't detect it as such.
Comment 2 Michal Zugec 2010-10-18 08:54:10 UTC
Please attach YaST logs
Comment 3 Ladislav Slezák 2010-10-18 15:34:51 UTC
"automatic" modification of the sound config sounds strange. AFAIK that file is written only by the sound card module.

Or do you use yast SVN feature? (configured in /etc/sysconfig/yast2 config file)

The subvendor is irrelevnat, yast checks only vendor and device IDs.

The yast logs should tell us more...
Comment 4 Ladislav Slezák 2010-11-08 16:46:47 UTC
The requested information was not provided.

If you can still provide it then attach it and reopen the bug.