Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 157850 - No sound from EMU10k1
Summary: No sound from EMU10k1
Alias: None
Product: Fedora
Classification: Fedora
Component: alsa-lib
Version: 4
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Martin Stransky
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2005-05-16 14:15 UTC by louisgtwo
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-05-16 21:21:10 UTC

Attachments (Terms of Use)

Description louisgtwo 2005-05-16 14:15:34 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050512 Fedora/1.0.4-2 Firefox/1.0.4

Description of problem:
Just installed FC4T3 on a Dell Dem 8200 and noticed I have no sound. The soundcard detection tool found the card but can't here the test sound. Don't know if this is the right package for this report. I am seeing hal not being properly shutdown.

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

How reproducible:

Steps to Reproduce:
1. run the sound detection tool
2. play the test sound

Additional info:

Comment 1 Martin Stransky 2005-05-16 17:15:23 UTC
Can you remove ~/.asoundrc and test it again? And check a mixer, if
you have all important chanels on.

Comment 2 louisgtwo 2005-05-16 19:00:42 UTC
Weird, I don't have a ~/.asoundrc file. But alsamixer and gnome volume
control show all chanels on.

Comment 3 Bill Nottingham 2005-05-16 19:30:20 UTC
What's the 'Wave' mixer set to?

Comment 4 louisgtwo 2005-05-16 21:15:56 UTC
Thw wave chanel was set to 0. I here sound now. This should be fixed in the

Comment 5 Bill Nottingham 2005-05-16 21:21:10 UTC
Should be fixed in alsa-utils-1.0.9rc2-2.

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