MACBOOK PRO WINDOWS 10 AUDIO DRIVERS INSTALL
Holding ALT/option during bootup I selected "EFI Boot" from the USB clover and booted into Cloverįor the exact Clover configuration send me a messageĪfter booting into windows the sound card was immediately working (this was because I had installed the cirrus logic drivers from bootcamp 4) - the display audio driver in device manager had an exclamation point but I was able to install the display audio driver from intel's driver support for the i7 2470m CPU in this machine. I used Maciasl to extract and edit my DSDT to add a 'Qword' section - I placed the DSDT in two locations /EFI/Clover/ACPI/Patched & /EFI/Clover/ACPI/Windows If you follow the guide and make a modified DSDT (one that add 'qwords' to the dwords section) you can test it in two ways.
MACBOOK PRO WINDOWS 10 AUDIO DRIVERS PC
So Windows 'honors' the root bridge and OSX and linux disregard it -hmmm interesting.Īs someone who also deals in hackintoshes I am very aware of DSDT's and how editing them can help get OSX running on home brew PC hardware- I had played around with installing Clover (the UEFI bootloader almost synonymous with Hackintoshes) on USB thumb drives and putting the DSDT from my MBP 2011 in the /Clover/ACPI/Windows folder - still nothing- I thought that pointing windows to a DSDT would be enough.Ī side note is that there are people who have 'bricked' their real Macs when using clover, I have never had that issue personally (a sub-link in the link above describes such a situation)* Neither of those OS require a DSDT override and can allocate freely in the huge 64-bit PCIe address space" macOS ignores the root bridge constraints as too does Linux when booted with the 'pci=noCRS' parameter. Windows OS honors the root bridge definition and will allocate PCIe devices within it. A watermark TOLUD value is then set and locked in the system firmware. "A Windows system's DSDT table root bridge definition (ACPI PNP0A08 or PNP0A03) is usually confined to a reserved 32-bit space (under 4GB) budgeted to be large enough to host the notebook's PCIe devices. I had tried to pass SETPCI commands from grub into Windows 10- no luck*Ī quote from the link above got my brain spinning
I had messed around with mm commands in a UEFI shell (The shell provided in the rEFIt package) to no avail* The part that was frustrating to me was that many users like myself have lots of UEFI installs on their 2011 MBP and those OS's have no problem 'seeing' the HD audio controller. I was given the answer from a tutorial only adjacently related -here:Įssentially what we knew was that windows didn't 'see' the correct audio devices when booted in pure efi. If anyone is still interested I have found the solution for audio on MBP 2011 Windows 10 UEFI installs - it has taken me 4 years to figure out.
0 kommentar(er)
