Bugzilla – Bug 128678
CS46xx sound doesn't work after Update; doesn't work after YaSt configuration
Last modified: 2007-06-07 12:37:55 UTC
After updating from 9.3 to 10.0, sound was no longer working. Even after calling the sound module in YaST, sound doesn't work. maybe the YaST module aborts without message (looks to me like that). Some details: Hardware: SubVendor: pci 0x1013 "Cirrus Logic" SubDevice: pci 0x4280 "Crystal SoundFusion PCI Audio Accelerator" Revision: 0x01 Driver: "Sound Fusion CS46xx" YaST: 2005-10-17 11:55:58 <3> pc8032(20794) [agent-modules] ModulesConf.cc(getOptions):169 Bad options for module: snd-cs46xx 2005-10-17 11:55:59 <3> pc8032(20794) [YCP] Linuxrc.ycp:26 Reading install.inf, but file doesn't exist!!! rcalsa restart: # rcalsasound restart Starting sound driver: cs46xx done /usr/sbin/alsactl: set_control:890: warning: device mismatch (0/2) for control #35 /usr/sbin/alsactl: set_control:892: warning: subdevice mismatch (0/0) for control #35 /usr/sbin/alsactl: set_control:894: warning: name mismatch (IEC958 Playback Default/IEC958 Playback Default) for control #35 /usr/sbin/alsactl: set_control:896: warning: index mismatch (0/0) for control #35 ...
Note that alsasound init script doesn't load modules except for restart/reload. The modules are loaded by udev/hotplug at boot time. See README.SuSE in alsa package. Do you have a /etc/sysconfig/hardware/hwcfg-* file including snd-cs46xx module? If yes, what module options are set in /etc/modprobe.d/sound? The warning messages from alsactl are harmless. Ignore them.
There is no file "/etc/sysconfig/hardware/hwcfg-*" containing "cs46". Also, even ncurses yast terminates as soon as I select the displayed sound card for changing.
Created attachment 54323 [details] y2log for last YaST session (ncurses "yast sound")
Ladsialv, it looks like a yast2-sound problem...
Please, attach /etc/modprobe.d/sound file.
The two lines of text are hardly worth an attachment: # H0_h.bPM+sbjw7xD:Crystal SoundFusion PCI Audio Accelerator alias snd-card-0 snd-cs46xx
YaST's sound module also seems to abort for other hardware (ISA PnP Soundblaster AWE32).
Do you have any other additional setting in /etc/modprobe.conf or /etc/modprobe.conf.local? Or any other files containing snd-* configuration in /etc/modprobe.d directory?
Three times "No". Sound works now, but the way YaST terminates during sound configuration makes me worry. Anything else I should provide?
Status update: after a reboot the sound does not work again. Only after a manual "alsaconf" things worked again.
A reboot seems to loose the configuration alsaconf used to get things up and working: After reboot sound won't work again. When using YaST to configure the sound card, no CS46xx card is offered. On another attempt, the !quick and automatic setup" failed: kernel: ALSA sound/pci/cs46xx/cs46xx_lib.c:427: cs46xx: failure waiting for FIFO command to complete "normal setup" also failed "manual setup also failed" Once again, "alsaconf" could set up the sound with no problem. I'll attach YaST logs.
Created attachment 57232 [details] YaST logs for some attempts to configure sound
"modprobe snd_cs46xx" does what "rcalsosound start" fails to do: Enable sound playback.
Being disappointed with the solutions SuSE could provide so far, I had another look and found this: In /etc/modprobe.conf (why no longer modules.conf?) I found these lines: # remove this if sound is configured install char-major-116 /bin/true (BUT SOUND IS CONFIGURED!) In /etc/modprobe.d/sound there seem to be the correct settings however: alias snd-card-0 snd-cs46xx alias sound-slot-0 snd-cs46xx Now it's your turn: Why didn't yast do that correctly, and what is the suggested SuSE solution to fix the problem permanently?
Yast writes some additional data to /etc/modprobe.d/sound file as comments, if they are missing yast is confused and might not assign the configuration to the right card. The problem was reported on 10.0, updating of 10.0 or a newer version works without problems.