Bug 406537

Summary: Yast sound module does not save kernel module options for snd-hda-intel
Product: [openSUSE] openSUSE 11.1 Reporter: Forgotten User 7pwnVrOCb1 <forgotten_7pwnVrOCb1>
Component: YaST2Assignee: Ladislav Slezák <lslezak>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Major    
Priority: P5 - None CC: bart
Version: Factory   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE 11.0   
Whiteboard:
Found By: Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: y2log file

Description Forgotten User 7pwnVrOCb1 2008-07-04 15:38:16 UTC
Tested on x86_64 and Lenovo 3000 N200, kernel 2.6.25.9(factory) and 2.6.25.5
and all yast factory updates

Hardware-Spec:
CPU T8100
Intel Corporation Mobile PM965/GM965/GL960
Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) 
VGA compatible controller: nVidia Corporation G72M [Quadro NVS 110M/GeForce Go 7300] (rev a1)
Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61)
Ethernet controller: Broadcom Corporation NetLink BCM5906M Fast Ethernet PCI Express (rev 02)

cat /proc/asound/cards 

0 [Intel          ]: HDA-Intel - HDA Intel
                      HDA Intel at 0xfc300000 irq 22

If I delete the default sound device in Yast, reconfigure it new with
option:

  model=lenovo
  position_fix=1

then the sound works, but this options are not written to /etc/modprobe.d/
or /etc/modprobe* or /etc/sysconfig
Comment 1 Bart geesink 2008-07-15 04:41:17 UTC
Same thing here with a Lenovo T60. Changing options in the YaST sound setup are not saved to /etc/modprobe.d/sound
Comment 2 Cyril Hrubis 2008-07-15 13:43:07 UTC
Please attach y2logs. If you are in doubt follow:

http://en.opensuse.org/Bugs/YaST

Thanks!
Comment 3 johan botha 2008-07-15 14:35:58 UTC
Created attachment 227884 [details]
y2log file

Attached is the y2log for the operation of trying to save the sound parameters

Thanks
Comment 4 Ladislav Slezák 2008-07-30 13:28:06 UTC
The bug is also in 11.0 Final.

*** This bug has been marked as a duplicate of bug 404900 ***