Bug 506547 (davenull)
| Summary: | ALSA does not properly detect all channels on card | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | David Fogle <dave> |
| Component: | kernel | Assignee: | Jaroslav Kysela <jkysela> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 11 | CC: | awilliam, dave, eric.moret, itamar, jkysela, kernel-maint |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-06-28 13:06:25 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
David Fogle
2009-06-17 17:34:13 UTC
I have run alsa-info on the computer, below is the emitted output. http://www.alsa-project.org/db/?f=4427b0a4948ef9e453b3df0a2c8fd7d3a84ee1a0 I just now removed pulseaudio packages from the system, no change, this is definately alsa as the cause, but interestingly enough, all of those extra channels that it could not see before are visible and modifiable, but they still do not output any sound to the channels. Could you please try the latest alsa-plugins package from rawhide and let me know if that fixes your issue. If it does, I'll push the new package to F11 Where would a guy find that package? I am rather new to Fedora, not linux, havent figured out all the places you guys have setup to find packages. Rawhide is the development repo for the next release of Fedora. You can get rawhide packages by looking up the development tree on the mirror list. Check the wiki page at: http://fedoraproject.org/wiki/Releases/Rawhide eric, I'm confused. there's no plain 'alsa-plugins' package, so it's not clear which one you're talking about. If you mean alsa-plugins-pulseaudio, David says the problem is still there without PA running, so how would it help anything? if you mean a different alsa-plugins package, which one exactly? alsa-plugins-upmix? just trying to understand this. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Well Eric, I have updated the alsa packages, no change, installed pulseaudio, no change... All I can think of if is the alsa drivers themselves. Indeed I was not paying attention and assumed it could help to upgrade to latest alsa-plugins because the bug is opened against this package. You might want to change the bug to package alsa-lib if you think this is the culprit. Also the best way to address this issue may be to follow up with the upstream alsa project. https://bugtrack.alsa-project.org/alsa-bug/login_page.php http://www.alsa-project.org/main/index.php/Help_To_Debug eric: Lennart and Jaroslav tell me that there's basically no-one handling upstream ALSA bug reports any more, so in practice it's better to report them here and assign them to Jaroslav, who might actually get around to them sometime this century. :\ moving to alsa-lib. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Well, updating alsa libs did absolutely nothing either, I had upgraded them with everything else. After updating alsa-driver to 1.0.20 from the alsa project, the issue is resolved. This is a kernel issue then. Thanks for the help guys, how should I proceed from here on out? Maybe reassigning this bug to kernel? Moving bug to kernel :) In order for this to work properly, the alsa packages from rawhide should me moved to 11, they are current stable from the alsa project though. no, it's not that simple. the alsa-driver bits live in the kernel, and are in the upstream kernel too; our kernels usually use whatever's latest in the upstream kernel, not whatever's latest at alsa-project.org, I believe. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers (In reply to comment #16) > no, it's not that simple. the alsa-driver bits live in the kernel, and are in > the upstream kernel too; our kernels usually use whatever's latest in the > upstream kernel, not whatever's latest at alsa-project.org, I believe. > > -- > Fedora Bugzappers volunteer triage team > https://fedoraproject.org/wiki/BugZappers That makes it a bit more of a hassle then. Compiling them from source works fine though, I can just keep updating if need be until the upstream is using what actually runs this beast of a lappy. At least I know what it is, I have also had a couple of people in the alsa channel on freenode try this, and it got 3-4 fedora users to a point where they had working sound for the first time. David: If you could clearly identify the files that made it work, maybe the RH kernel team could create a patch and include it in the kernel package while waiting for upstream to merge? yeah, it often works as a sledgehammer approach to the problem, as obviously they progressively fix bugs in newer upstream ALSA releases. I did email jaroslav to ask what his policy was on backporting fixes / just updating the in-kernel ALSA wholesale, but he hasn't replied yet. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers (In reply to comment #18) > David: If you could clearly identify the files that made it work, maybe the RH > kernel team could create a patch and include it in the kernel package while > waiting for upstream to merge? Well, that could be daunting as hell, I could diff all the files from 1.0.18 and 1.0.20 and see what is there. Also to be noted, the alsa-driver version is an alpha of 1.0.18, there are 2 RCs, 1.0.19, and then 1.0.20 is current, so there is at least a legit reason to move away from an alpha. (In reply to comment #19) > yeah, it often works as a sledgehammer approach to the problem, as obviously > they progressively fix bugs in newer upstream ALSA releases. I did email > jaroslav to ask what his policy was on backporting fixes / just updating the > in-kernel ALSA wholesale, but he hasn't replied yet. > > -- > Fedora Bugzappers volunteer triage team > https://fedoraproject.org/wiki/BugZappers Fantastic, thanks for the help everyone :) I have only seen the gentoo cats work faster than you guys. lol And as for the diff of all the files, a little under 3 MB of changes. There must be some confusion here, how did you find out that the fedora kernel includes 1.0.18a? For what I understand, fedora does NOT ship alsa-driver but relies on the kernel itself to provide these driver files. Therefore a diff would have to be done against what the kernel source provides and not against alsa-driver-1.0.18a It does, if you run alsa-info on a fedora 11 install, it outputs the dirver version. Fedora 11's 2.6.29 kernel has the 1.0.18a build in it. Well, let me take the beginning of that sentence, it has alsa drivers, where they come from is beyond me though. I have tried to find any alsa related files in the kernel sources, really only found one so far. Well, screw me, rebooted the thing, and now sound on the channels I just fixed is gone again... So, looks like there is a little config file somewhere that the driver makes after starting the hardware the first time.... what happens if you do "alsactl init"? as root. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Absolutely nothing, it still behaves in the same way, still claims to have the proper channels, nothing is muted, no sound other than front left/right. I do know for fact that ubuntu jaunty uses 1.0.17 alsa drivers, Fedora at 1.0.18a. I could not get the lower version to compile, so I could not confirm if this is a regression in alsa or what... 1.0.20 is the newest stable, and it does the exact same thing. This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. 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 '11'. 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 11'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 11 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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. |