Weird issue with ALC892 Audio (Update: Solved)

[ikingblack]

Hey guys,

 

I've been using Yosemite DP since it came out and have gotten everything to work, even sleep, on my fairly old GA P55 USB3. I'm running an i7 860 and GTX 660, with onboard audio using the line-out green port at the back of the computer.

 

Recently, my audio has been acting up and I have no recollection of changing any kexts or audio-related stuff. The issue is that whenever the mouse is not moving, sound is distorted, crackles, skips, and sometimes even just becomes a scratchy mess. I'm using the Yosemite AppleHDA kexts found in this forum for the 892 chipset with no DSDT, so I have installed HDAEnabler for injection of ID 4. The same issue is present with Voodoo HDA, both version 2.8.4 and 2.8.5. I'm using Clover, if that helps.

 

Is anyone able to shed some light on this? I've come across my fair share of hackintosh issues but this particular one has me baffled.

 

Thanks!

 

Update: Check the later posts for the solution

[jamiethemorris]

Are you using UEFI or legacy?

 

If you're using UEFI, it sounds like your BusSpeedkHz setting is wrong. Clover detects the correct value automatically, which is usually pretty accurate during legacy boot but less accurate during UEFI boot. Every computer that I'm using UEFI Clover with has had similar problems with audio for this reason. 

 

The solution is:

-First, boot Clover in legacy mode. The easiest way is to just make a bios-bootable flash drive. You can use your exisiting config.plist (make sure you don't have BusSpeedkHz set manually, if you do then remove it).

-Boot into the Clover GUI, press F2, and then look in Clover's EFI/Clover/misc/preboot.log (note: to be sure you are booting in UEFI mode, check to make sure it says it's booting from "Clover EFI" and NOT "rEFIt") and at the top you should see "MemLog inited, TSC freq: " followed by some number.

-Get your stock CPU multiplier, which in your case is 28, and add three zeros, so you would have 28000. Now device the TSC frequency you just got from the preboot.log by that number. This is your BusSpeedkHz as set by legacy Clover.

-Add that value to your config.plist for UEFI, and reboot into UEFI mode. Your audio should now be working properly.

 

This has always worked for me without fail. If you are booting in legacy mode rather than UEFI, it's possible the bus speed could still be wrong. In that case I would suggest following the steps above to find out what it is. It should be somewhere around either 100000 or 133000. If it's close to 100000, try manually setting it to 100000 (this is what real Macs supposedly use). If it's close to 133000, try setting it to 133000 manually.

 

You can find more information on BusSpeedkHz in the wiki here: http://clover-wiki.zetam.org/Configuration/CPU#BusSpeedkHz

 

Let me know if you need help or if this makes absolutely no sense to you.

[ikingblack]

Thanks for the informative reply!

 

I actually realized that my processor is an i7 870 Lynnfield, and I've turned off OC for now so it's at the stock 22 multiplier, and I've used that for my calculations.

 

According to the preboot.log, my TSC freqency is 2931245404. 2931245404 divided by 22000 = 1,332,384.2745. I simply added this to the top of my config.plist, is this correct?

<key>CPU</key>
	<dict>
		<key>BusSpeedkHz</key>
		<string>133330</string>
	</dict>

But it doesn't seem to work. I redid the calculations using 28 as you said, and putting in 100000 still didn't fix anything. I'm at loss as what to do - perhaps I should try Chameleon, as this seems to be an error on Clover's part?

 

Thanks for your immense help again!

[jamiethemorris]

You got that from legacy boot right? Do you use uefi normally?

If your processor is 2.2 GHz then 22 is the correct value to use, don't use 28.

 

And yes try chameleon, at least that will give us a lead as to what the problem is.

[ikingblack]

You got that from legacy boot right? Do you use uefi normally?

If your processor is 2.2 GHz then 22 is the correct value to use, don't use 28.

 

And yes try chameleon, at least that will give us a lead as to what the problem is.

Yep, I tried Chameleon. Didn't fix anything, sadly.

 

Yes, I got the frequency from checking preboot.log after booting the system from my USB Clover drive. Is there a way to completely ensure I'm using a legacy boot?

 

My processor is currently running at 2.93, should I use 29? I thought bus ratios were similar to multipliers meaning each system has a different set (x24 on my i7 is different than x24 on a Sandy Bridge).

 

I'll try 29 now (gave me a calculation of 100000) and see how it works, I just tinkered with the BIOS settings and turned off any sort of turbo boost - the CPU should be running at 2.93 GHz right no.

 

Thanks!

 

Edit: 100000 doesn't work. 

[jamiethemorris]

Yep, I tried Chameleon. Didn't fix anything, sadly.

 

Yes, I got the frequency from checking preboot.log after booting the system from my USB Clover drive. Is there a way to completely ensure I'm using a legacy boot?

 

My processor is currently running at 2.93, should I use 29? I thought bus ratios were similar to multipliers meaning each system has a different set (x24 on my i7 is different than x24 on a Sandy Bridge).

 

I'll try 29 now (gave me a calculation of 100000) and see how it works, I just tinkered with the BIOS settings and turned off any sort of turbo boost - the CPU should be running at 2.93 GHz right no.

 

Thanks!

you don't need to use the oc frequency. What you found sounds right. You know if it's in legacy boot because the preboot log will say "booting clover efi" or sporting like that, whereas in uefi it will say it's booting refit.

 

Assuming that boot was in fact in legacy mode, try setting your bus speed to 133238.

 

However, if it's happening in chameleon as well, I don't think it's actually a problem with the bus speed...

 

You mentioned that moving your mouse seems to affect this, have you installed any mouse drivers (or anything for that matter) recently? Post the output of

kextstat | grep -v apple

Also check in the console under "all messages" to see if there's anything spamming the console log constantly that could be bogging down the system or something.

[ikingblack]

Okay, I just checked the log - it's EFI.

 

To clarify, when I said Chameleon didn't fix anything I meant it just botched it more - I could use the OS for a few seconds after login before receiving a KP, and during those few seconds I found sound wasn't working at all so I went back to Clover.

 

Thanks for the updated bus speed, I'll give that a try right now.

 

I've searched the problem online and I don't think it's the mouse specifically - just the CPU being active (it works better when I'm using Chrome too) will affect the sound, but here are my 3rd party kexts (I'm guessing if one of them is screwing up the sound it'd probably be FakeSMC):

Index Refs Address            Size       Wired      Name (Version) <Linked Against>
   18    1 0xffffff7f81c8e000 0x11000    0x11000    org.hwsensors.driver.FakeSMCKeyStore (1018) <7 5 4 3 1>
   29    0 0xffffff7f81ca2000 0x5000     0x5000     org.netkas.driver.FakeSMC (1018) <18 11 7 5 4 3 1>
   44    0 0xffffff7f80ee5000 0x34000    0x34000    com.lnx2mac.driver.RealtekRTL81xx (0.0.90) <43 12 5 4 3 1>

(The other Realtek one is Ethernet)

 

Nothing seems to be spamming the console log.

 

Thanks!

 

Edit: The new value didn't change anything, sound is still screwed up.

Edited July 5, 2014 by ikingblack

[ikingblack]

Update:

 

I seem to have fixed it! I don't know what exact combination of things actually fixed it, but here's the stuff I've done:

 

-Turned off Intel Turboboost (I'll turn it on later as this seems to not affect the sound, but perhaps a good troubleshooting tip)

 

-Using AppleHDA and HDAEnabler, no DSDT + Clover with a config.plist 

      -Config.plist included FIX_HDA and Injection of audio

 

-Using Bus Speed of 13328 (find yours using above posts)

 

One thing I noticed is that my bluetooth stopped working - I'm using a Magic Mouse and given the symptoms of the error, this seems kinda suspicious. Other USB devices work however, so I'll look into it and post an update.

 

I cannot stress how grateful I am to jamiethemorris. Thanks!!