Contribute
Register

ALC889 Sound Assertion Errors

Status
Not open for further replies.
hi toleda

i've been having the same problem with my audio also::

Aug 1 13:17:40 snoqualmie kernel[0]: Sound assertion - Command/Response TIMED OUT and ( kRequestStateMatch == fCodecRequest->state = 2 ), fCodecRequest->command->codec: -549397426432, fCodecRequest->command->verb: 0xFFF, fPoweredDown: 0
Aug 1 13:17:40 snoqualmie kernel[0]: Sound assertion in AppleHDAController at line 4909
Aug 1 13:17:40 snoqualmie kernel[0]: Sound assertion in AppleHDAController at line 4910
Aug 1 13:17:40 snoqualmie kernel[0]: Sound assertion in AppleHDAController at line 8088

i've attached a copy of my IOReg as you suggested.

i have the customacmini 2011 build with the Gigabyte H67N F9 aml
 

Attachments

  • balaclava9.zip
    367.9 KB · Views: 65
Are these messages showing when using a MacPro3,1 smbios? I believe it may have something to do with the energy management system. In my hack it even "pops" when the audio is turned on/off, which I solved by using the antipop daemon (the sound assertions are still there though).
 
hi toleda

i've been having the same problem with my audio also::

Aug 1 13:17:40 snoqualmie kernel[0]: Sound assertion - Command/Response TIMED OUT and ( kRequestStateMatch == fCodecRequest->state = 2 ), fCodecRequest->command->codec: -549397426432, fCodecRequest->command->verb: 0xFFF, fPoweredDown: 0
Aug 1 13:17:40 snoqualmie kernel[0]: Sound assertion in AppleHDAController at line 4909
Aug 1 13:17:40 snoqualmie kernel[0]: Sound assertion in AppleHDAController at line 4910
Aug 1 13:17:40 snoqualmie kernel[0]: Sound assertion in AppleHDAController at line 8088

i've attached a copy of my IOReg as you suggested.

i have the customacmini 2011 build with the Gigabyte H67N F9 aml
Delete S/L/E/HDAEnabler889.kext. When you have a dsdt, do not install the enabler. You are lucky you had any sound; the enabler using interferes.
 
hi toleda thanks for the quick reply!
i'm glad my sound wasn't totally broken!


i deleted the s/l/e/HDAEnabler889.kext
i attached my new ioreg.

i still see the same assertion as before. it happens when sound has been inactive for a while ... them it triggers the following: the speakers pop and these errors appear in the log:

Aug 2 00:45:00 snoqualmie kernel[0]: Sound assertion - Command/Response TIMED OUT and ( kRequestStateMatch == fCodecRequest->state = 2 ), fCodecRequest->command->codec: -549422663936, fCodecRequest->command->verb: 0xFFF, fPoweredDown: 0
Aug 2 00:45:00 snoqualmie kernel[0]: Sound assertion in AppleHDAController at line 4909
Aug 2 00:45:00 snoqualmie kernel[0]: Sound assertion in AppleHDAController at line 4910
Aug 2 00:45:00 snoqualmie kernel[0]: Sound assertion in AppleHDAController at line 8088
Aug 2 00:45:01 snoqualmie kernel[0]: Sound assertion - Command/Response TIMED OUT and ( kRequestStateMatch == fCodecRequest->state = 2 ), fCodecRequest->command->codec: -549428512512, fCodecRequest->command->verb: 0xFFF, fPoweredDown: 0
Aug 2 00:45:01 snoqualmie kernel[0]: Sound assertion in AppleHDAController at line 4909
Aug 2 00:45:01 snoqualmie kernel[0]: Sound assertion in AppleHDAController at line 4910
Aug 2 00:45:01 snoqualmie kernel[0]: Sound assertion in AppleHDAController at line 8088
Aug 2 00:46:12 snoqualmie kernel[0]: Sound assertion - Command/Response TIMED OUT and ( kRequestStateMatch == fCodecRequest->state = 2 ), fCodecRequest->command->codec: -549422663936, fCodecRequest->command->verb: 0xFFF, fPoweredDown: 0
Aug 2 00:46:12 snoqualmie kernel[0]: Sound assertion in AppleHDAController at line 4909
Aug 2 00:46:12 snoqualmie kernel[0]: Sound assertion in AppleHDAController at line 4910
Aug 2 00:46:12 snoqualmie kernel[0]: Sound assertion in AppleHDAController at line 8088
Aug 2 00:46:13 snoqualmie kernel[0]: Sound assertion - Command/Response TIMED OUT and ( kRequestStateMatch == fCodecRequest->state = 2 ), fCodecRequest->command->codec: -549428512512, fCodecRequest->command->verb: 0xFFF, fPoweredDown: 0
Aug 2 00:46:13 snoqualmie kernel[0]: Sound assertion in AppleHDAController at line 4909
Aug 2 00:46:13 snoqualmie kernel[0]: Sound assertion in AppleHDAController at line 4910
Aug 2 00:46:13 snoqualmie kernel[0]: Sound assertion in AppleHDAController at line 8088


thanks so much!
 

Attachments

  • balaclava9-2nd.zip
    349.8 KB · Views: 61
ematos: i'm on macmini5,1

this antipop thing looks cool ...
http://www.tomsick.net/projects/antipop.html
simple trick

apparently the power down noise is a problem on older macs too ...

(ps i wonder if tomsick is running a hackintosh now :p)
 
i still see the same assertion as before. it happens when sound has been inactive for a while ... them it triggers the following: the speakers pop and these errors appear in the log:
At your convenience, try a clean 10.7.4 install. Use the normal MultiBeast selections except audio, chose only the Patched AppleHDA/ALC 889.
 
Toleda, couldn't those messages be related to energy management because he's using a macmini plist? I also use one and get almost identical errors on Mountain Lion with the patched kext + DSDT edit.
 
Toleda, couldn't those messages be related to energy management because he's using a macmini plist? I also use one and get almost identical errors on Mountain Lion with the patched kext + DSDT edit.
The popping is not caused by energy management. It is much simpler; if the codec doesn't have an audio signal for ~60 seconds, it quiets (reduces power to) the amp. This eliminates the static you hear, especially when an input is connected to a output in one of these systems. You hear this when you use an iPod as the input, headphones for the output, mute the iPod and 60m seconds later, the static is stops; that is quieting. The only system definition which doesn't enable quieting is macpro3,1. In the experiment, the static does not stop and there is not pop when an audio signal restarts. The pops are one problem and (I believe) the sound assertions, in particular the timeout, is a different problem.
 
So I agree, all the SMBIO settings (iMac 12,2 and MacMini) for my mobo give the popping.

I end up using the MacPro 3,1 just because the popping is annoying :)

I wonder why the mac pro is different and can we incorporate that somehow into the system (my knowledge isnt enough)
 
Status
Not open for further replies.
Back
Top