Jump to content

VoodooHDA 3.0.2


Slice
675 posts in this topic

Recommended Posts

I continue to support VoodooHDA. 

Now version 2.9.5 with some security check compiled under BigSur and now is working here.

Be sure your sound device is not HDEF. This is the way to exclude conflict between AppleHDA and VoodooHDA because AppleHDA will be loaded only if the device named HDEF and if HDMI device is called HDAU.

For VoodooHDA they can be any other names. For example

ALC device will be HDAS.

HDMI device on AMD graphics card will be named as HDMI.

See

Снимок экрана 2020-10-10 в 10.03.17.png

  • Like 2
Link to comment
Share on other sites

Hi,

 

i'm trying to get my soundblaster x-fi running, but changing "IOPCIClassMatch" to "IOPCIPrimaryMatch" and then "DeviceID + VendorID" shows no audiodevice at all. It's working with 2.8.7, 2.8.8 but all outputs only play (the same) when "Rear Green" is selected.

Any Tipps for this?

Thanks :)

Link to comment
Share on other sites

I am not sure but probably VoodooHDA requires less security for system.

The flag CSR_ALLOW_DEVICE_CONFIGURATION must be set in csr config.

I used mask 0x285 for success in BigSur.

Link to comment
Share on other sites

  • 1 month later...
  • 2 months later...
On 11/19/2020 at 10:39 PM, Slice said:

I made one more fix in VoodooHDA to be working under BigSur.

Now this is the version 2.9.6.

VoodooHDA.kext.zip 95.64 kB · 53 downloads

 

Tell me how to make it work? in Catalina, built-in sound worked for me (ALC662) and in Big Sur it does not work, only HDMI outputs are detected
 image.png.1d19721aabaeccce3e910284c0ae65ac.png

VoodooHDAGetdump.txt

Edited by NEOSoftWare
Link to comment
Share on other sites

On 1/19/2021 at 11:15 PM, NEOSoftWare said:

Tell me how to make it work? in Catalina, built-in sound worked for me (ALC662) and in Big Sur it does not work, only HDMI outputs are detected
 image.png.1d19721aabaeccce3e910284c0ae65ac.png

VoodooHDAGetdump.txt 13.71 kB · 0 downloads

VoodooHDA dump shows only HMDI sound. Check your BIOS settings.

Probing codec #0...
 HDA Codec #0: ATI R6xx HDMI

 

Link to comment
Share on other sites

  • 2 months later...

Hello @Slice thank you for continuing the VoodooHDA support, please, if I may: I have a couple of quick questions to clarify how latest v2.9.6. works and behaves.

 

On my NUC10 using Core i7-10710U I have (per lspci -nn) the Intel Corporation Comet Lake UHD 630 Graphics [8086:9bca] and Intel Corporation High Definition Audio Controller [8086:02c8] or in other terms  ALC256 (ALC3246). My audio device keeps the original name HDAS in IORegistry (since AppleALC is not used).

 

Using OpenCore 0.6.7 I have disabled AppleALC.kext and enabled VoodooHDA.kext and without any other parameter or setting, it seems to load OK: I get Headphones and HDMI Audio indications in Sound (and Microphone). The analog output works, tested it. But the digital audio doesn't seem to work...

  • Please, do recent VoodooHDA versions work with Intel iGPU digital audio? My online search found mixed results...
  • Do we still need to disable Apple's vanilla AppleHDA.kext via AppleHDADisabler.kext in Catalina and BigSur? It is mentioned in old posts, but I cannot confirm this lately. Is this disabler still needed?
  • Since the VoodooHDA.kext loads OK (via OpenCore) any idea why we need to still set CSR_ALLOW_DEVICE_CONFIGURATION? Following that Chrome update fiasco on macOS, I decided to make like vanilla Mac and secure everything...
  • Do we need to confirm this setting exists hda-gfx=onboard-1  on both IGPU and HDAS or is it totally ignored by VoodooHDA?

Many thanks, спасибо

NUC10-UHD630-ALC256-dump.txt

Link to comment
Share on other sites

1. I don't know what to do for Intel iGPU audio. It looks like working for me and I have no other information.

2. As the device is HDAS you don't need to disable AppleHDA.

3. Probably CSR_ALLOW_DEVICE_CONFIGURATION is not needed. Test?

4.  hda-gfx is ignored by VoodooHDA.

Link to comment
Share on other sites

  • 2 weeks later...
15 minutes ago, ellaosx said:

Hi @Slice

using 2.9.2 is ok

using 2.9.5-2.9.7 vodoohda loads but not working.


error:  codec #0 is not responding, probing aborted
error:  couldn't allocate memory for function groups
error:  no PCM channels found

 

 

There are no such differences between versions.

Link to comment
Share on other sites

Hi @Slice

Last working version is VoodooHDA.kext-2.9.0d10. Attached is a getdump result.

 

Version 291SSE panicked regarding IOAudioFamily.

 

Version 2.9.2 up to 2.9.7 loads but not working

error:  codec #0 is not responding, probing aborted
error:  couldn't allocate memory for function groups
error:  no PCM channels found

2.9.0d10 getdump: 2.9.0d10.txt

Link to comment
Share on other sites

4 hours ago, ellaosx said:

Hi @Slice

Last working version is VoodooHDA.kext-2.9.0d10. Attached is a getdump result.

 

Version 291SSE panicked regarding IOAudioFamily.

 

It looks like you use very old system while new VoodooHDA is compiled for 10.13 and up.

OK, use 2.9.0. There are no differences in final sound.

Link to comment
Share on other sites

2 hours ago, Slice said:

It looks like you use very old system while new VoodooHDA is compiled for 10.13 and up.

 

Im using this:

Desktop (UEFI): Gigabyte B250M-HD3, i3@3.9ghz, 16gb DDR4 Ram, Intel HD 630 - OS: High Sierra & Big Sur

Both HighSierra & Bigsur has those issues.

My primary audio driver is ApleALC. I just use your Voodoohda to test it.

Link to comment
Share on other sites

13 hours ago, ellaosx said:

Of course they work. It works on my other computers. Its just this computer that doesn't.

But how it is not working? Not loaded or no sound?

Link to comment
Share on other sites

Hello i'be VoodooHDA 2.97 since today. I'll hope this upgrade solve my problem : no sound I use OpenCore 0.68 and it said "Prelinked injection VoodooHDA.kext () - invalid parameter" I don't understand help:help:

Link to comment
Share on other sites

  • 2 weeks later...

I manage to make it working under Big Sur. As well as in Sonoma

1. Set restricted enabled SIP

            <key>CsrActiveConfig</key>
            <string>0x0A85</string>

2. Delete other old sound kext (VoodooHDA or AppleALC) from EFI folder.

3. Reboot

4. Copy the kext into LE. Open Terminal.app and enter here

sudo cp -R /path_to_kext/VoodooHDA.kext  /Library/Extensions

4a. Attention! If you copied the kext other way then you have to repair permissions

sudo chown -R root:wheel /Library/Extensions/VoodooHDA.kext

5. In the case of Ventura this is not enough. You should also load the kext

sudo kextutil -v /Library/Extensions/VoodooHDA.kext

 

6. The system ask you to look into System Preferences -> Security and enable here VoodooHDA

Screenshot 2023-06-07 at 19.36.00.png

 

Снимок экрана 2021-04-29 в 19.48.37.png 

 

Screenshot 2023-06-07 at 19.36.30.png

4. Reboot

5. Voila

Снимок экрана 2021-04-28 в 18.41.05.png

 

 

  • Like 5
  • Thanks 8
Link to comment
Share on other sites

×
×
  • Create New...