- Joined
- Oct 25, 2013
- Messages
- 124
- Motherboard
- MSI X299 SLI Plus
- CPU
- i7-7820X
- Graphics
- RX580 + GTX1070 + GT710
- Mac
- Mobile Phone
Has anyone success with Broadwell-E CPUs to have Video Decoder Acceleration ?
How do you test this?
Has anyone success with Broadwell-E CPUs to have Video Decoder Acceleration ?
Well it does look like renaming to xhc1 removes 3 usb3 ports, so that would make sense.
But your usb 3.1 ports does not look like mine under 10.13.2, so something has changed in the beta.
Okay one last question: are the errors you posted last time WITH XHCI? Because it complains about not creating ss05, and ss05 is not there with xhc1, but it is there with xhci
My system is very sensitive to OsxAptio. I have been able to boot by only using the combination of Test2.efi + OsxAptioDrv.
My conclusion with Clover 4369 is that:
OsxAptioFixDrv: works both restarting and from a cold boot.
OsxAptioFix2Drv: works only from cold boot. If I restart, I get the "Does printf work??" error.
So Clover 4369 is a great improvement for me, no need for Test2.efi anymore. I will stay with OsxAptioFixDrv for now.
One easy way to test it is-How do you test this?
From what I understood from kgp's remarks, I believe Test2.efi is also meant to fix random reboots. Please let us know if you notice any.
Edit: Actually from my own notes (this is what I wrote about it)
Install Test2-2016.efi in /Volumes/ESP/EFI/CLOVER/drivers64UEFI/. This is supposed to add stability to "OsxAptioFixDrv-64"
# Otherwise the "OsxAptioFixDrv-64" trick won't work, you'll stay stuck on a non-loaded "using reloc block"
There are no random reboots on Skylake-X/X299 if everything is set properly. Test2-2016.efi has been solely used to avoid memory allocation errors at early boot.
Thank you KGP for the clarification!
Would you have a copy of RAMALAMA_ASUS_R6E_USB.kext to share please?
Sweet! So there is hope. Which kext do you use for Ethernet? Did you have to do anything special for it or just use the one provided in kgp's EFI?
Also, OSX 10.13.2?
You don’t need any XHC kext. All XHC USB boards should be natively implemented.
yes, 10.13.2, nothing change