c.craigen

Trimmed it down to just those 5, still doing the same thing. Also tweaked a verb since the digital out is optical.

Could be that the connector is shot. Never did try the onboard audio in Windows since the intention from the start was to send everything over HDMI (which is working fine on both platforms). Might be a short on the detection line, I had to pull the front panel out to reconnect one of the USB cords and I might have bumped something I shouldn't have. If it is that I swear I'm gonna shoot something, I've been plugging away at this for 2 days now.

Update
1. Audio was exhibiting the same behavior in Windows, so I was assuming a hardware fault.
2. Disconnected the front panel, no joy on the sound but the switching stopped.
3. Rebooted. Still no sound.
4. Cold-booted with HDMI unplugged, lo and behold the audio worked! Reconnected the front panel, no rapid switching, autodetection working fine, sound working.
5. Rebooted, still working.
6. Rebooted back on to the Mac side, no joy and hang upon trying to change audio stuff.
7. Rebooted to Windows, sound had stopped working again.
8. Cold-booted Windows, audio working again.
9. Rebooted Windows again, audio still working.

What the hell is going on here? Am I messing something up in the DSDT? Is AppleHDA doing some kind of device reconfiguration that is {censored} the hardware on reboot?

I'm trying this out on a P8H61-M, which also has the new card. It hangs the system completely for about 10 minutes on startup. Are you all using the older AppleHDA or a bin-patched version of the newer one?

update - it appears that this happens no matter what version of AppleHDA I use. When the system eventually kicks out of its loop, audio still isn't working and the whole system is much less responsive. Removal of the legacy kext restores functionality. I'm using the DSDT edit.

update 2 - taking a deeper look in IOreg, it looks like it is switching between headphones and internal speakers rapidly and won't stop. Even though nothing is plugged in. Trying to fix.

update 3 - deleted the MuteGPIO keys for IntSpeaker and Headphone. Boots normally now and shows up in System Preferences, but sound output still doesn't work and the system switches between IntSpeaker and Headphone about twice a second. Never had this much trouble with an HDA patch before.

update 4 - added the Headphone MuteGPIO key back in, system still loads alright but sound still doesn't work. Clicking in headphones indicates that the switching is still happening about twice a second. System Preferences locks up if I unplug the headphones and won't unlock at all. This is confusing me, it's even more frustrating than the ALC262 that thought it was an ALC892 and had a node graph that looked like someone nuked a yarn convention. Even VoodooHDA choked on that one; this one is worse in that it *almost* works.

There is unlikely to be one used in an official mac any time soon, Apple tends to stick with the higher end of Intel's offerings so the lowest common denominator is still probably going to be the HD3000.

The other thing I was worried about was sound over integrated HDMI. I know for a fact that I can get this to work with ATI cards (since I've used them in 2 of my 3 hackintosh builds so far) but it's still a blind shot with the Intel graphics.

K, good to know. They are the same controller design but the 3000 has twice as many rendering cores. My guess is that it's just being initialized as if it has 12 cores instead of 6 and this is why it craps out when it's handed certain instructions.

Screw it, I'll just buy a Radeon 5570. It's got more horsepower anyways.

Has anyone tested this with an HD 2000 yet? If I could skip out of buying a discrete card for my next build, that would be wonderful.