Bug 88497
Summary: | (SOUND VIA_82CXXX)Distorted sound with new AC97 Audio Controller revision | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Vidar Langseid <vl> |
Component: | kernel | Assignee: | Jeff Garzik <jgarzik> |
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | CC: | ml, peterm |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-30 15:40:46 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
Vidar Langseid
2003-04-10 15:32:44 UTC
I have had a similar problem on my mainboard. Reason was that the actual codec the AC97 audio used was a Sigmatel which only supported one fixed 48kHz sample rate. That means the sound has to be upsampled by the driver. The linux support for that is not too good. Could you look into the output of dmesg after loading the modules; it should print which actual codec it finds. Then try to find a datasheet for that codec... I solved this by downloading the commercial OSS that Sigmatel offered free licenses for linux users; but later decided to get a new sound card anyway. dmesg shows the following: Via 686a audio driver 1.9.1 PCI: Found IRQ 5 for device 00:07.5 ac97_codec: AC97 Audio codec, id: 0x4943:0x4511 (ICE1232) via82cxxx: board #1 at 0xDC00, IRQ 5 Enabled Via MIDI I also have quite many instances of: via_audio: ignoring drain playback error -11 and via82cxxx: timeout while reading AC97 codec (0x9A0000) Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/ |