Description of problem: With 2.6.24 kernel I get very ugly crackling sound from my T61 with recent kernel (2.6.23 is running just find - no sound problems. Even when I remove pcspkr (which is also now a good source of such cracklings) Oh - and btw - why CONFIG_ACPI_VIDEO is not set ? I do not get brightness control interface in /proc Version-Release number of selected component (if applicable): 2.6.24-0.55.rc3.git3.fc9 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: clean sound Additional info:
Hi Well I've moved myself to vanilla kernel - latest fedora kernel: vmlinuz-2.6.24-0.80.rc4.git6.fc9 doesn't play the sound at all - the volume move bar in gnome is basicaly enable/disabling sound at various points (at least from the cracling I could hear in the headphones) I guess some patch from the fedora patch set is heavily broken....
My update for this report: 2.6.24-0.136.rc6.git12.fc9 Sound with this kernel looks better (even thought the pcspkr module is better rmmod-ed) - at least with OSS and volume setting everything seems to be just fine. (yet with pulseaudio it is another horrible story...)
Hello another update on this issue - the problem appears to be with the power saving. with setting 0 here: /sys/module/snd_hda_intel/parameters/power_save the sound is clean&clear with setting 10 (which is default with fedora kernel) I do hear the crackling in the sound i.e. before the mp3 song gets played (with
Kernel default is 5 in rawhide and 0 in Fedora 8. Maybe we need to disable it by default and let users enable it at their own risk...
Bug could be probably closed - the problem is up to the user if he wants power saving or not. Could be selected by this options line in /etc/modprobe.conf options snd-hda-intel index=0 model=thinkpad power_save=0 I assume there is no way to make this power saving 'click-free' as even with muted sound the audio click when it's in power_save mode :(
Powersave is now off by default. Closing as dup of the newer bug since that's the one in the changelog. *** This bug has been marked as a duplicate of 433495 ***