Mac OS X on x86 Hardware 2008–2024 Technical Archive
InfiniteMac OSx86 › OSx86 Core & 10.X › Am I Missing Something
7,090 reads · 2009-11-24 – 2009-12-06
Report 10.X Core ALC889a / Audio Voodoo / XNU Kernel

Am I Missing Something

Ok well I just removed AppleHDA and any other enabler I had installed. but VoodooHDA still gives me this kernel panic. Am I missing like a kext or something? because I think thats why there are dependancy errors... If somebody could help…

Primary Author
@xXrkidXx Published 2009-11-24
Collection
OSx86 Core & 10.X
Archival Footprint
7,090 historical reads · 4 curated field notes (from 11 dispatches) · 2009-11-24 – 2009-12-06
Credited Voices (3)
@xXrkidXx (7)@Imkantus (3)@spalek83

Ok well I just removed AppleHDA and any other enabler I had installed. but VoodooHDA still gives me this kernel panic.

... modules in backtrace (with dependancies)
org.voodoo.driver.VoodooHDA(0.2.1)@0x16db7000->0x1bdd8fff
dependency: com.apple.iokit.IOPCIFamily(2.5)@0x122f6000
dependency: com.apple.iokit.IOAudioFamily(1.b.5fc3)@0x10b3e000

com.apple.iokit.IOAudioFamily(1.b.5fc3)@0x20b3e000
dependency: com.apple.kext.OSvKernDSPLib(1.1)@0x20b3b000

BSD Process name coressponding to current thread:kernel_task

Mac OS Version:
9G55

9.5.0 Voodoo Kernel

Am I missing like a kext or something? because I think thats why there are dependancy errors... If somebody could help me figure this out, it would make my year. I am Sound away from having a perfect hackint0sh.. and VoodooHDA gets the job done... Please Help

Author Updates & Technical Revisions

Follow-up dispatches by @xXrkidXx

Author Update #1 @xXrkidXx 2009-11-24

i removed AppleHDA because i thought they would conflict with each other.. I am placing it in S/L/E.. should i be placing it in E/E? and if so, how do i do it? in my extra folder there is no Extensions folder so I would have to create one but how do i make an Extensions.mkext? also what dependencies are needed to run it out of E/E?

Author Update #2 @xXrkidXx 2009-11-25

yes but then it still gave me mounting issues.. weird.. so i got the correct seatbelt and all better. could this be a problem with my kernel/version not supporting VoodooHDA?

Author Update #3 @xXrkidXx 2009-11-29

Well same KP with 9.6.0 AnV installer.. going to try something really quick..

Nope, still KP..

Tried 0.2.2 and KP again..

Author Update #4 @xXrkidXx 2009-12-01

Eh forget it.. Complete reinstall with iATKOS, and so far EVERYTHING is working.. Im pretty happy.

Thank you for all your help tho!

Author Update #5 @xXrkidXx 2009-12-03

Well, its back.. What happend.. I updated to 10.5.8. It went into a boot loop, so I reinstalled all my drivers from the iATKOS disc(I asked my friend for it again) and then VoodooHDA kp is BACK!which makes no sense.. So i reinstalled everything(clean, erased and repartitioned Disk) and Im STILL getting the voodooHDA kp.. Wtf? How is this possible? If I erased the disc completely and It was working on a clean install before how could this happen? Any ideas(its the same KP only with the 9.7.0 Qoopz Kernel).. Please help!

Synthesized Community Field Notes

4 technical responses curated from 11 original dispatches

Field Note #1 @spalek83 2009-11-24

you removed voodoohda but voodoohda is giving you errors? that dosn't really make sense, did you rebuild all extensions.mkext? (assuming the one in /extra?)

Field Note #2 @Imkantus 2009-11-24

Your Kernel Panic shows that you're using 9.5.0 Kernel - so I guess you reinstalled iPC again - did you select 10.5.5 seatbelt.kext at customization?

Field Note #3 @Imkantus 2009-11-30

Well it says something about depencies on IOPCIFamily.kext so you should try without VoodooHDA again and check, if has been loaded...
> "kextstat | grep IOPCIFamily" if it doesn't return anything, you should check if there are any error visible on /var/log/system.log

Field Note #4 @Imkantus 2009-12-06

I already wrote that into your second topic - having your codec dump migth help us to help you.

Well anyway - I attached an AppleAzaliaAudio.kext file - it should work on chips with the following device IDs 0x10ec , 0x14f1 , 0x11d4 , 0x434d & 0x8384
Give it a try if it matched with yours.

Sources & Contributor Provenance (3 credited usernames · Thread #4796)
UsernameDossier ContributionDispatchesActive Window
@xXrkidXxPrimary Author72009-11-24 → 2009-12-03
@ImkantusCore Contributor32009-11-24 → 2009-12-06
@spalek83Contributor12009-11-24