Bug 122787 - the i810_audio module quits working on an nforce board.
Summary: the i810_audio module quits working on an nforce board.
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel   
(Show other bugs)
Version: 1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2004-05-07 21:25 UTC by Glen
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-29 20:24:36 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Glen 2004-05-07 21:25:43 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6)
Gecko/20040207 Firefox/0.8

Description of problem:
I run Fedora Core 1 on an nvidia nforce board that has built in audio.
 When I boot up, the i810_audio module loads up, and sound works
great.  Somehow though, sound just stops working.  I play an mp3 or
something and nothing at all comes out of the speakers.  If I unload
and reload the i810_audio module, then my sound comes back.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Boot your machine.
2. Eventually the sound stops working.

Actual Results:  The sound stops working until I reload the module.

Expected Results:  I expected the sound to just work forever.

Additional info:

Comment 1 David Lawrence 2004-09-29 20:24:36 UTC
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

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/

Note You need to log in before you can comment on or make changes to this bug.