Jump to content



Member Since 21 Mar 2008
Offline Last Active Jan 25 2016 07:10 PM

Posts I've Made

In Topic: VoodooHDA with fix for random KP

27 August 2013 - 09:21 PM

... aaand back from the dead, 8 months later.. I've been busy recording so i decided not to experiment with the drivers..

Thanks Zenith for your work - I now tried 2.7.6d2, 2.8.1 and 2.8.2d6, and they all seem to get rid of the KP, but unfortunately they also get rid of my onboard sound card...


I'm using an HDTV for my screen and it's connected via HDMI.. Using the updated kexts only allow me to select those digital out, but no HD audio with line in/outs - which is what i need. Mixing through an old LG 37LD450's speakers is far from optimal ;]


I rolled back to my random KP inducing kext, which i can live with since once started it's running fine. Thanks a lot anyway, and glad I could help a little!

In Topic: VoodooHDA with fix for random KP

05 January 2013 - 10:16 PM

thanks a lot zenith, I will try your updated version a bit later and post back the results.


In Topic: VoodooHDA with fix for random KP

31 December 2012 - 11:58 AM

It's best to boot with "-f" after freshly installing it, because sometimes there's a stale copy in kernelcache. Anyhow, I can't read the stack trace because of the "You need to restart your computer" window that's hiding the crash address in VoodooHDA (it's that line with 7f81dc...). If it's still giving you KPs after booting with "-f", look for a panic log in /Library/Logs/DiagonsticReports and upload it.

Sorry about the restart box, takes less than a second to appear and block the text. Will try right now.


Tried with -f, and it crashed right away. Didn't change anything after, and it doesn't seem to generate a panic log either, i made sure to delete all logs before rebooting, and i find nothing in /Library/Logs/... /Users/.../Library/Logs/...

There are files that were generated in /Private/var/log but nothing that seems to concern the KP.

I tried to snap a picture in the half a second where the message is visible, which resulted in the blurry image attached to this post. Tell me if you can make out the important bits, otherwise I can try to take a better one, but it's a pain in the a** to try that way.

Btw, it just occurred to me - does -v force the console output to be logged on file ?

In Topic: VoodooHDA with fix for random KP

29 December 2012 - 02:36 AM


4 KP's in a row, went through on the 5th.

At least it doesn't want to tear my speakers anymore when loading and it fixed the clipping sound issues..

Motherboard (old and cheap, i know, but works fine):
Asrock Wolfdale1333-D667 R2.0 W/Patched bios

HD Audio (Realtek ALC662 Audio Codec)

In Topic: GT610 on 10.7.2

29 December 2012 - 01:59 AM

Got It!

I did the combo update to 10.7.5, then booted with -s to remove S/L/E/NV* and S/L/E/Ge* (I played too much the kexts and probably had conflicting versions anyway) as i was unable to boot into the desktop otherwise.

I then downloaded the retail Nvidia drivers for 10.7.5 here:

I left the new NVDAGF100hal untouched, didn't seem to contain any device id's anyway.

Rebooted and got full resolution and QE/CI.

Thanks @rampage for your info, it actually pointed me in the right direction!

Hope this helps someone else!

Edit: This might also help people with newer versions such as Mountain Lion - I saw a few posts from people having similar issues (unable to get to the desktop after reboot), so my guess is that it might be worth it to try clean S/L/E from the non-working kexts and get the retail nvidia drivers for the specific version of OS X being used.
© 2017 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy