Bug 373201

Summary: No audio out on MacBook Pro (SantaRosa ICH8)
Product: Red Hat Enterprise Linux 5 Reporter: Craig Chaney <cchaney>
Component: kernelAssignee: Jaroslav Kysela <jkysela>
Status: CLOSED CURRENTRELEASE QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: medium Docs Contact:
Priority: low    
Version: 5.1CC: cmeadors, dzickus, peterm, prarit, s.adam, syeghiay
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 483594 Environment:
Last Closed: 2010-05-14 08:40:40 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:
Bug Depends On: 525390    
Bug Blocks: 526948, 533192    
Attachments:
Description Flags
scsconfig.log the audio tool said to attach
none
scsrun.log file the error dialog said to attach. none

Description Craig Chaney 2007-11-09 17:27:53 UTC 
Description of problem:
I have no audio output when running the audio configuration (or any other time).
I have verified the audio device is not muted through alsamixer as well as the
volume is at a reasonable level.

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


How reproducible:
Every time.

Steps to Reproduce:
1.Run the audio configuration tool
2.Play the test audio button
3.Change PCM devices to test all
  
Actual results:


Expected results:


Additional info:
I am running an Apple MacBook Pro (SantaRosa ICH8) which seems to be properly
identified.
Comment 1 Craig Chaney 2007-11-09 17:28:54 UTC 
Created attachment 253071 [details]
scsconfig.log the audio tool said to attach
Comment 2 Craig Chaney 2007-11-09 17:29:33 UTC 
Created attachment 253081 [details]
scsrun.log file the error dialog said to attach.
Comment 3 Brian Maly 2007-12-14 01:21:11 UTC 
Does the raw device (rather than the audio tools) work? 
I.e, do you hear any noise if you run "find / > /dev/audio"?

Also could run "/sbin/lsmod|grep snd" and attach the output?
Comment 5 Stewart Adam 2008-05-07 20:57:48 UTC 
I can confirm this on a MacBook Pro 4,1. Fixed by adding the model=mpb3 to the
snd-hda-intel options.
Comment 6 Stewart Adam 2008-09-01 00:45:15 UTC 
Any updates on this issue?
Comment 8 RHEL Program Management 2009-04-23 17:49:13 UTC 
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.
Comment 11 Jaroslav Kysela 2009-10-07 12:40:32 UTC 
The latest ALSA HDA intel driver has this change. Backport bug#525390 .
Comment 12 RHEL Program Management 2009-10-07 13:00:10 UTC 
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.
Comment 13 Jaroslav Kysela 2009-11-05 10:43:06 UTC 
The latest ALSA HDA driver for RHEL 5.5 is available here:

http://people.redhat.com/~jkysela/RHEL5/

Please, report back test results.
Comment 16 RHEL Program Management 2009-12-16 06:11:33 UTC 
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.
Comment 20 Jaroslav Kysela 2010-05-14 08:40:40 UTC 
I believe that this issue is fixes in RHEL 5.5. If the problem persists, please, reopen this bug.