Bug 428107
Summary: | Audio broke with kernel 2.6.23.12-52.fc7 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dimitris <centos> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 7 | CC: | chris.brown |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-04-25 04:55:20 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
Dimitris
2008-01-09 09:30:34 UTC
Does booting back to the older kernel still work? A lot has changed since 2.6.23.1, so it is hard to tell what may have caused this... My mistake, 2.6.23.1 is also broken, due to ALSA 1.0.14 having a broken "hda-intel" module, which carried over to kernel 2.6.23.12, which also uses ALSA 1.0.14. It seems the solution is to upgrade to ALSA 1.0.15, as seen in: http://alsa-project.org/main/index.php/Changes_v1.0.14_v1.0.15 Fedora 8 kernel has ALSA 1.0.15 Is it possible to include ALSA 1.0.15 in a Fedora 7 kernel? Dimitris, Are you able to test first to confirm this works for you? I enabled the "development" repository and installed the latest kernel (2.6.24-0.150.rc7.git4.fc9), which is able to play audio without a problem. I would have kept this kernel, unfortunately this kernel only runs on runlevel 3, if i try to boot to runlevel 5 then the system freezes when X tries to load itself. Also, there are loads of weird error messages when the kernel boots, like: "Cannot access hardware clock via any known method". Okay, thanks for the update. I suggest you wait until a 2.6.24 Fedora 8 kernel arrives (which shouldn't be long) and test with that, then update this bug. (In reply to comment #7) > Okay, thanks for the update. I suggest you wait until a 2.6.24 Fedora 8 kernel Sorry, make that a 2.6.24 Fedora 7 kernel... No problem, thank you for taking the time to help me. My pleasure. I'll leave this at NEEDINFO for the moment so we know we're waiting on you to test... The Fedora 8 kernel should work fine on Fedora 7. Differences between the two are documented at: https://fedoraproject.org/wiki/KernelCommonProblems I'll wait for an official F7 kernel, due to several kernel-specific modules that i'm running, which are provided by 3rd party repositories (livna, freshrpms, etc). Okay, setting back to NEEDINFO so we know we're waiting on you to test then. Thanks for the update. The information we've requested above is required in order to review this problem report further and diagnose/fix the issue if it is still present. Since there have not been any updates to the report since thirty (30) days or more since we requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem. Setting status to "CLOSED INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report. Thank you in advance. Note that maintenance for Fedora 7 will end 30 days after the GA of Fedora 9. |