Big Sur on X79-ZD3 Huananzhi, issues with FireWire Audio

Q: What is a Hackintosh?

A non-Apple computer configured to run macOS using compatible PC hardware combined with a custom bootloader and configuration files to emulate a real Mac environment.

Q: Is building a Hackintosh legal?

Installing macOS on non-Apple hardware violates Apple’s End User License Agreement (EULA). It is generally not illegal for personal experimentation but not permitted for commercial use.

Q: What hardware is best for a Hackintosh?

The best hardware closely matches real Apple systems, with Intel CPUs (6th Gen to Core Ultra), AMD Radeon GPUs, compatible chipsets, and Intel-based Wi-Fi cards offering higher success rates.

Q: Can I build a Hackintosh with an AMD CPU?

Yes, macOS can run on AMD Ryzen CPUs using kernel patches, but Intel CPUs provide better native compatibility.

Q: What is OpenCore?

OpenCore is a modern Hackintosh bootloader that provides near-native macOS behavior and is the recommended bootloader for new installations.

Q: Is Clover still supported?

Yes, Clover is still supported but less recommended compared to OpenCore for modern systems.

Q: Which macOS versions support Hackintosh?

Hackintosh systems support macOS versions from Leopard up to recent releases, depending on hardware compatibility.

Q: Do NVIDIA graphics cards work on Hackintosh?

Only older NVIDIA GPUs work on older macOS versions; modern NVIDIA GPUs are incompatible with current macOS releases due to lack of driver support.

Q: What is an EFI folder?

The EFI folder contains the bootloader, drivers, kexts, and configuration files required to boot macOS on a Hackintosh.

Q: What are kexts?

Kexts (kernel extensions) are drivers that enable hardware functionality such as audio, Ethernet, USB, and graphics.

JakubW · February 13, 2021

3 hours ago, MaLd0n said:

yes

What I have noticed, is that the USB 3.0 controller has issues, when a device, that runs below USB 2.0 speed is connected, but not in Windows, just Mac OS, at boot its still shows enumeration issues, but not with my Maschine Mikro MK2 controller, just iLok, AKAI LPD8, mouse and keyboard, all probably run below 480 Mbps

JakubW · February 14, 2021

17 hours ago, MaLd0n said:

yes

Not sure, if it does work, I uses USBPoerts.kext again and the modified mXHCD.kext, the USB controllers still seems to use the APPLEUSBXHCIPCI driver

https://drive.google.com/file/d/1KKYk610p2MeRouJSN4Ccx8m7j2N_mteO/view?usp=sharing

JakubW · February 14, 2021

6 hours ago, JakubW said:

Not sure, if it does work, I uses USBPoerts.kext again and the modified mXHCD.kext, the USB controllers still seems to use the APPLEUSBXHCIPCI driver

https://drive.google.com/file/d/1KKYk610p2MeRouJSN4Ccx8m7j2N_mteO/view?usp=sharing

Maybe changing the IOProviderClas to Frisco Logic od AsMedia on the port injector kext?

JakubW · February 14, 2021

1 hour ago, JakubW said:

Maybe changing the IOProviderClas to Frisco Logic od AsMedia on the port injector kext?

https://forums.macrumors.com/threads/usb-3-x-pcie-cards-for-classic-mac-pro.1501482/post-23009994

I don't think there is a need to mess with the driver, links above confirm, it works OTB, Maybe some current settings?

Edited February 14, 2021 by JakubW

JakubW · February 14, 2021

1 hour ago, JakubW said:

https://forums.macrumors.com/threads/usb-3-x-pcie-cards-for-classic-mac-pro.1501482/post-23009994

I don't think there is a need to mess with the driver, links above confirm, it works OTB, Maybe some current settings?

I checked that devices, that require more than 100 mA of current are stable and those at 100 or less have enumeration issues. SO there is an issue with low poerr device rather than the speed. It may be a power issue as this article suggests: https://www.cnet.com/news/tackling-a-usb-device-enumeration-error-in-os-x/

JakubW · February 16, 2021

On 2/14/2021 at 10:23 PM, JakubW said:

I checked that devices, that require more than 100 mA of current are stable and those at 100 or less have enumeration issues. SO there is an issue with low poerr device rather than the speed. It may be a power issue as this article suggests: https://www.cnet.com/news/tackling-a-usb-device-enumeration-error-in-os-x/

After looking in Windows via USBDevview, I got another conclusion, all the affected devices are USB 1.1, so maybe the legacy hub should be triggered somehow.

JakubW · March 10, 2021

On 1/25/2021 at 5:35 PM, MaLd0n said:

the power management start working now, but u need solve turbo. ur previous config x86platform is not load

It turns out the plugin type needed to be added to the SSDT, now X86 PlatformPlugin is loaded, had to generate custom aml with these args

./ssdtPRGen.sh -p 'E5-2670' -x 1 -target 0 -c 3 -cpus 1 -l 8 -mode custom -d 3

USB 1.1 enumeration issue still present

Edited March 10, 2021 by JakubW

JakubW · March 13, 2021

I checked that devices, that require more than 100 mA of current are stable and those at 100 or less have enumeration issues. SO there is an issue with low poerr device rather than the speed. It may be a power issue as this article suggests: https://www.cnet.com/news/tackling-a-usb-device-enumeration-error-in-os-x/

I have an impression, tie IO Probe score needs to be adjusted, but do't know how to approach it TBH

JakubW · September 25, 2021

On 3/10/2021 at 5:12 PM, JakubW said:

It turns out the plugin type needed to be added to the SSDT, now X86 PlatformPlugin is loaded, had to generate custom aml with these args

./ssdtPRGen.sh -p 'E5-2670' -x 1 -target 0 -c 3 -cpus 1 -l 8 -mode custom -d 3

USB 1.1 enumeration issue still present

Allright, another update on mz CPU. I removed Plugin Type from the CPU SSDT and generated SSDT Plug. Works better with Big Sur. I also had issues with updating to newer build. The fix with older FireWire kexts caused kernel panics and /I had to sort out the Unicore Bridge, use a DSDT patch in OC, but I still can't get FireWire Audio working on Big Sur. I'am afraid I will have to delete the kexts form the OS and load older ones from OC, but it doesn't seem to be a good solution in the long run. Saw this in Verbose Boot and Boot Log:

2021-09-24 02:01:38.037853+0200 0x897 Default 0x0 0 0 kernel: (AppleFWOHCI) AppleFWOHCI_DescriptorPool::create - link = <private>
2021-09-24 02:01:38.049394+0200 0x897 Default 0x0 0 0 kernel: (AppleFWAudio) AM824NuDCLRead::Start() failed: 0xe00002d4
2021-09-24 02:01:38.057864+0200 0x897 Default 0x0 0 0 kernel: (AppleFWAudio) AppleFWAudioDevice::initHardware error StartAllStreams
2021-09-24 02:01:38.065788+0200 0x897 Default 0x0 0 0 kernel: (AppleFWAudio) AppleFWAudioDevice[<private>]::initHardware() Error!!! something wrong in initHardware calling cleanUpResources() status=<private>
2021-09-24 02:01:38.076060+0200 0x897 Default 0x0 0 0 kernel: (AppleFWAudio) AppleRemoteAudioDevice[<private>]::initHardware(<private>) failed

Will compare with Catalina.

MaLd0n · September 25, 2021

https://www.olarila.com/topic/10301-olarila-runme-dumper/
https://olarila.com/files/Utils/RunMe.app.zip
https://olarila.com/files/Utils/IORegistryExplorer.app.zip

JakubW · September 27, 2021

On 9/25/2021 at 7:53 PM, MaLd0n said:

https://www.olarila.com/topic/10301-olarila-runme-dumper/
https://olarila.com/files/Utils/RunMe.app.zip
https://olarila.com/files/Utils/IORegistryExplorer.app.zip

After updating to 11.6 it got better. the device loads the driver, but is stutter, after a reboot it doesn't"t load. Note on ACPI I now use SSDTX79ZD3.aml instead of the DSDT (as You also did in the EFI folders)

Send me Jakubs-Mac-Pro.zip

And here the IOReg

https://drive.google.com/file/d/1CGJmob-vdVf8Q4yOeI6qbOAH76yU7E5K/view?usp=sharing

JakubW · September 27, 2021

And here the IOReg

https://drive.google.com/file/d/1CGJmob-vdVf8Q4yOeI6qbOAH76yU7E5K/view?usp=sharing

I have an impression there is an IRQ conflict between HDAU and FRWR

IRQ.zip

Edited September 27, 2021 by JakubW

JakubW · October 1, 2021

his SendMe is from the boot, were the Firewire auto interface got enabled, the boot log shows the same error, so there must be something else pointing to issues with launchingg the audio interface. Anyway the interface rather won't load. There were also issues with the SSDT, so I switched back to the DSDT

https://drive.google.com/file/d/15a55IGV9fk93S_Mmn5MqKLNnHVD8jnWj/view?usp=sharing

Send me Jakubs-Mac-Pro.zip

JakubW · October 4, 2021

More and more I suspect, that the interrupt specifies, starting with 03 cause the issue, it may be related to the HPET as well

IRQ 2.zip

MaLd0n · October 4, 2021

need work with default irqs patch

JakubW · October 4, 2021

Yep, on Mojave it picks 04 in the HDAU segment of the GPU. I also saw, you moved the HPET to SBRG in the DSDT, did the same with an SSDT, now the boot is stable again.

When I leave the OEM HPET and add patches to it, the system hangs, total freeze

MaLd0n · October 5, 2021

ye

hpet inside low pin count device. in this case name is different

JakubW · October 5, 2021

I found multiple values in UAR1, that have Benn blocked, including 3 and 4. Anything we could do, e.g. disable it and inject it again via SSDT with no IRQNOFlags?

urrent Legacy IRQs:

- SIO1: []

- PS2K: [1, 1]

- PS2M: [12, 12, 12]

- UAR1: [4, 3, 4, 5, 6, 7, 10, 11, 12, 3, 4, 5, 6, 7, 10, 11, 12, 3, 4, 5, 6, 7, 10, 11, 12, 3, 4, 5, 6, 7, 10, 11, 12]

- PIC: [2]

- TMR: [0]

- RTC0: [8]

- COPR: [13]

MaLd0n · October 6, 2021

kill UAR1 device

JakubW · October 6, 2021

19 minutes ago, MaLd0n said:

kill UAR1 device

STA method in SSDT for example?

Sign In

Big Sur on X79-ZD3 Huananzhi, issues with FireWire Audio

Recommended Posts

JakubW

JakubW

JakubW

JakubW

JakubW

JakubW

JakubW

JakubW

JakubW

MaLd0n

JakubW

JakubW

JakubW

JakubW

MaLd0n

JakubW

MaLd0n

JakubW

MaLd0n

JakubW

Create an account or sign in to comment

Create an account

Sign in

Browse

Activity