|
Bugzilla – Full Text Bug Listing |
| Summary: | No Sound after upgrade to 10.0; CMI8738/C3DX PCI sound card | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | John Bailo <jabailo> |
| Component: | Sound | Assignee: | Ladislav Slezák <lslezak> |
| Status: | RESOLVED WONTFIX | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | diprob, jabailo, jsrain, matz, tiwai, wstephenson |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
John Bailo
2005-10-11 23:40:02 UTC
Same here .. the sound comes again if i delete the sound card in YaST and run the configure procedure again ... It's likely an update problem. Once remove the card via yast2 and reconfigure it again as described in #1. See README.SuSE in alsa package. Confirmed. I did just that and it works great. But after rebooting the sound is missing again. And after that i couldn't reproduce that effect described in #1. I didn't see the Starting audio device message while booting since SuSE 10.0 ... too bad. (In reply to comment #4) > But after rebooting the sound is missing again. And after that i couldn't > reproduce that effect described in #1. I didn't see the Starting audio device > message while booting since SuSE 10.0 ... too bad. > What I notice with Suse is that if you reboot without a full shutdown (that is, turn off the power) then it won't retain any of the configuration settings. I don't know how to "force" a configuration change save, but anytime I make a signification change, I do a full shutdown and reboot to "lock in" the changes. To comment #4: alsasound init script never shows such a message any more at boot, because it is not alsasound init script who loads the driver. Please make clear what you mean "sound is missing". If /proc/asound/cards is missing or its entry is empty, it's a problem at loading sound modules. OTOH, if /proc/asound/cards shows the right entry, it's just a mixer setting problem. In the former case, check /etc/sysconfig/hardware/hwcfg-* files whether any of them contains your module (snd-cmipci). If not, run yast sound dialog, delete the current one, and quit once. (Note that this quit step is important.) Then, restart yast and reconfigure the sound device again. In the latter case, you have to adjust mixer setting once, and do either a clean shutdown, or save the mixer status manually via "/usr/sbin/alsactl store" as root. To comment #5: Of course, if you don't do a clean shutdown, the system will be instable. At a clean shutdown, alsasound init script saves the current mixer status to /etc/asound.state. If this is skipped, the last-saved /etc/asound.state is used to restore the mixer state. That's the only difference. To answer your questions ... /proc/asound/cards --> didn't exists .. even /proc/asound is not here. /etc/sysconfig/hardware/hwcfg- * didn't shows the soundcard anymore .. but yast shows 2 cards (but i think that was my fault beause i used alsconf to add a soundcard instead of yast. But now yast soundconfig didn't do anything .. it shows 2 cards. Two columns: |blank|sound card| |not configures|cm8738| But if i want to delete or edit one of the entrys it does nothing. if i press 'configure' it exits the yast sound module without any message. The only thing that works now is running alsconf and starting the sound device manually after each start .. I have removed the card from the computer and rebooted but nothing helped here. Yast shows this 2 entries .. and i could remove them anymore .. i think this is a yast problem or ?? Hello, i found a solution for this mess. First delete the sound* files in /etc/modeprobe.d/ (i think it t worth to delete the *.yast_safe file too). Now reboot SuSE 10 and reconfigure the sound card via yast and ... it work. I tested it and it worked. It seems that yast has problems with the old sound installation files ... I hope this help you. That can be the reason. Possibly, an old configuration file was read and override... Ladislav, does yast save the module config file with a strange extension? Yast uses .YaST2save suffix which is ignored by modprobe - so no problem here. Please, don't mix alsaconf with the yast module, yast doesn't support alsaconf configured cards properly (see bug #117066). Could anybody attach /etc/modeprobe.d/sound, 'hwinfo --sound' output, hwcfg-* file and y2log when this problem occurs? Btw, the attached info regards a SBLive not a CMI8738. *** Bug 207903 has been marked as a duplicate of this bug. *** *** Bug 116427 has been marked as a duplicate of this bug. *** This is update problem from 9.3 and older. Since the problem doesn't occurre if upgrading from 10.0 or newer, will not solve this issue any more. |