Hide Forgot
Description of problem: cannot play sound after upgrading packages (via Applications -> System tools -> Software updater) Version-Release number of selected component (if applicable): [root@erazim ~]# rpm -q kernel kernel-2.6.15-1.2054_FC5 kernel-2.6.16-1.2069_FC5 How reproducible: play any sound: [techie@erazim uderka]$ ogg123 Vytvarna\ uderka11.ogg === Could not load default driver and no driver specified in config file. Exiting. Steps to Reproduce: 1. upgrade packages 2. play sound Actual results: does not play any sound Expected results: should play any sound Additional info: see attached scsound.log
Created attachment 127011 [details] System Config Soundcard log
curiously, it has somehow be connected to the fact that I have enabled/disabled one of the NICs in the system by setting onboot value in /etc/sysconfig/networking/devices/ifcfg-eth[01] because after enabling it again, both modules are in place: [techie@erazim ~]$ cat /proc/asound/modules 0 snd_emu10k1 1 cx88_alsa and sounds plays fine
This is really funny - I have rebooted the system and it seems that each time kernel initializes/probes devices in different order which causes disfunctionalities. In attached file erazim-dmesg-diff.txt are differences between reboot after which sound did not work and reboot after which sound did work (no I have not changed any HW config between reboots)
Created attachment 127154 [details] differences between dmesg of non-working and working kernel (on the same HW)
this seems to be pretty common problem - try searching google for 'EMU10K1_Audigy: probe failed with error'
Created attachment 127158 [details] /proc/pci contents seems that there is IRQ clash
A new kernel update has been released (Version: 2.6.18-1.2200.fc5) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. In the last few updates, some users upgrading from FC4->FC5 have reported that installing a kernel update has left their systems unbootable. If you have been affected by this problem please check you only have one version of device-mapper & lvm2 installed. See bug 207474 for further details. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. If this bug has been fixed, but you are now experiencing a different problem, please file a separate bug for the new problem. Thank you.
This bug has been mass-closed along with all other bugs that have been in NEEDINFO state for several months. Due to the large volume of inactive bugs in bugzilla, this is the only method we have of cleaning out stale bug reports where the reporter has disappeared. If you can reproduce this bug after installing all the current updates, please reopen this bug. If you are not the reporter, you can add a comment requesting it be reopened, and someone will get to it asap. Thank you.
Sound playing and recording (see bug 191076) works now so this bug can be closed.