Created attachment 930130 [details] aplay -l Description of problem: When playing audio on my Dell PowerEdge T20 using the integrated sound (apparently a Realtek ALC3220 chip), the sound has very low quality (hard to describe, but it sounds like a cheap mono speaker). The problem exists both when using PulseAudio and when using ALSA directly. However, it is possible to get normal sound using two methods: 1) Using pavucontrol, switch the output from "Speakers" to "Headphones (unplugged)". 2) Using alsamixer, increase the "Headphone" volume and disable "Speaker". What makes the problem even more annoying is that the output is reset to the default on every reboot. There is a thread at http://forums.whirlpool.net.au/archive/2172061 about the same problem, so this is probably not a regression. I already updated ALSA and the kernel to the Fedora 21 versions but the problem persists. I am using BIOS version A04 with UEFI and disabled Legacy Option ROMs if that makes any difference. Version-Release number of selected component (if applicable): alsa-firmware.noarch 1.0.28-1.fc20 alsa-lib.x86_64 1.0.28-2.fc20 alsa-plugins-pulseaudio.x86_64 1.0.28-3.fc20 alsa-tools-firmware.x86_64 1.0.28-2.fc20 alsa-utils.x86_64 1.0.28-2.fc20 kernel.x86_64 3.16.1-300.fc20 kernel-core.x86_64 3.16.1-300.fc20 kernel-headers.x86_64 3.16.1-300.fc20 kernel-modules.x86_64 3.16.1-300.fc20 kernel-modules-extra.x86_64 3.16.1-300.fc20 pulseaudio.x86_64 5.0-7.fc20 pulseaudio-gdm-hooks.x86_64 5.0-7.fc20 pulseaudio-libs.x86_64 5.0-7.fc20 pulseaudio-libs-glib2.x86_64 5.0-7.fc20 pulseaudio-module-bluetooth.x86_64 5.0-7.fc20 pulseaudio-module-x11.x86_64 5.0-7.fc20 pulseaudio-utils.x86_64 5.0-7.fc20 Steps to Reproduce: 1. Play any sound file. 2. Switch the output from "Speakers" to "Headphones" and notice the difference.
Created attachment 930131 [details] aplay -L
Created attachment 932916 [details] /proc/asound/card0/codec#0 Attaching another file with probably important information.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.17.2-200.fc20. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21. If you experience different issues, please open a new bug report for those.
This is still happening with Fedora 21.
I am having the same problems. They are particularly acute when trying to get youtube videos to play. The volume drops to about 10% of what it should be based on a Windows 7 computer nearby. Everything sounds tinny, and some sounds are not played (or perhaps drop to 10% and I cannot hear them). When internet audio, it occurs on all my browsers, seamonkey, chrome, firefox.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 21 kernel bugs. Fedora 21 has now been rebased to 3.18.3-201.fc21. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
In the past few days I have noticed marked improvement in the sound on my computer. I don't know if all the problems are gone, but many of the specific sound problems have disappeared. Thanks, john
Thanks. We'll close this out.
For me, the problems still persist. By default, the sound still sounds tinny and I have to manually change it to "Headphones".
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 21 kernel bugs. Fedora 21 has now been rebased to 3.19.5-200.fc21. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 22, and are still experiencing this issue, please change the version to Fedora 22. If you experience different issues, please open a new bug report for those.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 EOL if it remains open with a Fedora 'version' of '21'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.