Red Hat Bugzilla – Bug 224310
es1373 sound stops working with kernels >= 2.6.19-1.2895.fc6
Last modified: 2009-01-09 02:03:38 EST
Description of problem:
I have ES1373 sound controller on the motherboard. After upgrading to the latest
kernel I have no sound anymore. According to lsmod all sound drivers are loaded,
but in alsamixer there is no volume controls for master, PCM and CD. In dmesg
log I can see "AC'97 0 analog subsections not ready" message.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot kernel-2.6.19-1.2895.fc6 on computer with ES1373 sound controller
2. Run any audio application
Sound should work
This can be seen also in es18xx.
I'm forced to run the stock kernel 2.6.18-1.2798.fc6 which is the only one ALSA
works on. I have tried 2.6.19.x and 2.6.20.x multiple versions without touching
anything else but there is no sound from any of these versions.
Gnome has problems logging in when I switch to the newer kernels and on reboot
the mixer settings can't be saved. When I boot to the 2789 I need to unmute the
sound but othervise it is OK.
and it seems that this problem (atleast for the es18xx chip) can be solved.
See bug #223950 for reference.
Basically I removed all references to the sound system from /etc/modprobe.conf
and rebooted to the new kernel (2.6.20-1.2933.fc6) and autodetect fixed the
Rebuilding of modprobe.conf and hwconf make no difference at all. But
experimenting with different setups I've found that sound actually works
immediately after kernel boot and cease to work if sound driver modules are
unloaded and reloaded again. So, it seems, that beginning from kernel 2.6.19
this sound driver failed to unload properly.
Is this bug still present in F8?
Yes, it is. That's why I've changed version to 8 ;-)
I'm reviewing this bug as part of the kernel bug triage project, an attempt to
isolate current bugs in the Fedora kernel.
I am CC'ing myself to this bug and will try and assist you in resolving it if I can.
There hasn't been much activity on this bug for a while. Could you tell me if
you are still having problems with the latest kernel?
If the problem no longer exists then please close this bug or I'll do so in a
few days if there is no additional information lodged.
If you are then please attach the following as separate attachments of type
text/plain to this bug:
# lspci -vvxxx > lscpi.out
dmesg > dmesg.out
Please also run system-config-soundcard and generate a scsconfig.log (under the
Previous fix has permanently fixed this for me.
Created attachment 293971 [details]
The output of lspci -vvxxx
Created attachment 293972 [details]
The output of dmesg
Created attachment 293973 [details]
The output of system-config-soundcard
Created attachment 293975 [details]
The contents of /proc/asound/card0/.../ac97#0-0+regs
Created attachment 293976 [details]
The output of dmesg after removing and reloading snd-card-0 kernel module
Created attachment 293977 [details]
The contents of /proc/asound/card0/.../ac97#0-0+regs after removing and reloading snd-card-0 kernel module
This bug is still present in kernel-18.104.22.168-107.fc8.i686. It happens when
snd-card-0 kernel module is removed by modprobe -r snd-card-0 and reloaded again
with modprobe snd-card-0.
Have you tried removing the references in modrpobe.conf and rebooting into a new
kernel as Marko mentioned? These are the three to remove.
alias snd-card-0 snd-ens1371
options snd-card-0 index=0
options snd-ens1371 index=0
Yes I have. I does not make any difference. Obviously something bad happens with
hardware state when this kernel module is removed.
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '8'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 8's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 8 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.