MBP UEFI WINDOWS SOUND FIXED!!!!

Question

Level 1

23 points

MBP UEFI WINDOWS SOUND FIXED!!!!

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. I was given the answer from a tutorial only adjacently related -here:

https://egpu.io/forums/pc-setup/fix-dsdt-override-to-correct-error-12/

essentially what we knew was that windows didn't 'see' the correct audio devices when booted in pure efi-

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 -

So what was windows doing different?

I had messed around with mm commands in a UEFI shell (The shell provided in the rEFIt package) to no avail*

I had tried to pass SETPCI commands from grub into Windows 10- no luck*

A quote from the link above got my brain spinning

"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. A watermark TOLUD value is then set and locked in the system firmware. Windows OS honors the root bridge definition and will allocate PCIe devices within it. macOS ignores the root bridge constraints as too does Linux when booted with the 'pci=noCRS' parameter. Neither of those OS require a DSDT override and can allocate freely in the huge 64-bit PCIe address space"

So Windows 'honors' the root bridge and OSX and linux disregard it --hmmm interesting.

As 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.......

A 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)*

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-

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 [not sure if that one matters] & /EFI/Clover/ACPI/Windows

holding ALT/option during bootup I selected "EFI Boot" from the USB clover and booted into Clover

for the exact Clover configuration send me a message

After 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 also looked at device manager via 'by resources' and saw that a new entry 'Large memory with an address range appeared

And low and behold the address range for the 'large memory section' contained the range for the hd audio controller

I then wanted to see if the method described in the initial link posted above where you force that memory map into the registry and turn on 'test signing' worked --

it did, which allowed me to boot directly into windows without the help of clover --

*NOTE: when I tested the registry method I skipped the first few steps since I already had a modified DSDT- I did need to create the 'C:\dsdt folder and extract the windows binaries to that folder - but I did not use their acpi dump nor compiler (I check for errors and compiled my dsdt in Maciasl in OSX)

I would gladly go more in depth but I doubt there are many more who need this information- just glad to have figured it out without the BIOS emulation of bootcamp- going to test this method on other 'pre 2013' Macs with non complient UEFI bios'

MacBook Pro

Posted on Feb 3, 2019 11:57 AM

Reply

Answer 1

Feb 1, 2020 7:53 AM in response to Spirit_TY

Updates:

So, I managed to replace the DSDT.aml in xAndrewH1993x's script with my modified DSDT and ran the script. It worked fine also. My audio is good, using valor.

How I wish there could be a fix for the DisplayPort. Any luck TGIK?

Thanks again guys.

Reply

Answer 2

Apr 28, 2020 1:51 PM in response to TGIK

Dear whoever is still out there struggling! Easiest solution - bluetooth speaker/earphone. that's all. i dont think theres a necessary risk to redo the entire thing (installing in uefi is tough enough, plus after success and ended up with a bulk of unused blank dvd) . ive not tried but usb speaker might work too, since the issue is just the audio hardware within the imac not being recognized. cheers and good health everyone (Y)

Reply

Answer 3

Apr 28, 2020 3:24 PM in response to steve0108

Dude just use my script, click mount run its that easy. This is for those people who are not technically savvy. www.howeitworks.com/valor there are tutorials and free download links with no surveys. Thanks for stopping in.

Reply

Answer 4

Dec 3, 2020 7:21 PM in response to medham

Please check out TGIK's Link to create DSDT Patch: https://youtu.be/a8abK1HmKDM if you want to use Windows to install it, please check out instructions below. Please check out my personal project Valor (TGIK's DSDT Patch/Batched Itayemi's method into a Batch Script (For 2011 Macbook Pros)) https://youtu.be/rb-B9M7ro5A & https://youtu.be/c72B5Zajo2g

itayemi's instructions (copied from his website)

Reply

Answer 5

Khanj

Level 1

14 points

Nov 1, 2020 9:43 AM in response to TGIK

Just follow the link and sound is Fixed.

Intel Method Worked for me.

Macbookpro 2011 late 13"

UEFI installed Windows 10

Reply

Answer 6

Loner T

Level 9

59,606 points

Feb 3, 2019 2:18 PM in response to TGIK

Nice.

Instead of all this work, why not install using standard BIOS mode? Most Mac users who install UEFI on 2011 (or older model) are unaware of the proper (and supported) mechanism or want to clean-install W10, which Apple officially does not support.

Reply

Answer 7

itayemi

Level 1

4 points

Sep 12, 2019 5:38 PM in response to TGIK

@TGIK - I thought I might as well give it a try after I posted my last message. To make things interesting, I am doing this remotely on a MAC (belong to a cousin) on which I had installed RealVNC server :-)

Thanks, I got audio to work. I was going to post my procedure (approx 5,800 xters) here but it appears the limit for a single post is 5,000 characters, thus giving me the opportunity for some shameless self-advertisement. I have put it on my website instead:

http://www.itayemi.com/blog/2019/09/12/dual-booting-mac-osx-and-windows-on-macbookpro/

If necessary, I can break it up into 2 messages and post the whole thing here as well.

Thanks again!

Reply

Answer 8

Oct 25, 2019 7:15 AM in response to xAndrewH1993x

Hiya

I've successfully done this mod to get audio on my mid 2011 iMac. I would be interested in a automated process script or a video if one is available though. Didnt mind going through the process to do the mod, but i've created a backup of my windows installation so I don't have to in future. But would still be handy to have a script for all or part of the process. Many thanks.

Reply

Answer 9

TGIK Author

Level 1

23 points

Dec 3, 2019 2:07 PM in response to AMcomputers

I think Andrew will be able to help you -- he is making the process a lot easier - though the steps outlined throughout this forum post are not that difficult -- it really is just cutting/copying and pasting....I also put my email on here in case people wanted me to edit their DSDT for them (though I am literally just copying and pasting 1 section) --

If you already have Windows installed in UEFI mode you a literally seven minutes from getting it to work with sound -- (though don't count on thunderbolt functionality as of right now)

let us know how to help

Reply

Answer 10

Feb 1, 2020 5:44 AM in response to TGIK

You guys are super and awesome!

Apologies. Got this sorted about 12 hours ago but it was 3:00am in my location then (I'm in Africa) so I had to hit the bed. I planned to come back here to report later. Just got the chance.

TGIK was patient enough to walk me through the entire process, taking me through step by step. Now I have sound on my Windows OS. Better still, I know the steps to take now so I can replicate the solution time and again. I'm grateful man. You're the best.

xAndrewH1993x reached out to me to check in and I'm so glad he did. I have the modified DSDT file now. I'll mail to you in a few seconds so you can mod for MBP 2012 users. I'll be willing to test for you while you develop and test the modified script.

Thanks guys. I'm grateful for all your help. I've got sound now on my MBP Mid 2012.

I'll format now and try to do it myself. (~_*)

Reply

Answer 11

Mar 12, 2020 8:32 AM in response to GustavoPi

Sounds like the bootcamp drivers that you have is just out dated. If you install Windows as EFI (Not through bootcamp assist tool from MacOS) (Formatted GPT partition table flash drive with a EFI installer of Windows 10) and run Valor (includes updated bootcamp drivers for some 2011 models) you might be good. What Macbook do you have? The reason why I said install it as EFI is because Valor was developed for EFI installed of Bios (Legacy).

Reply

Answer 12

TGIK Author

Level 1

23 points

Apr 16, 2020 9:03 AM in response to tic-tac-crumpet

email me at tacogenius@gmail.com and we can walk you through some steps -- I can even edit your DSDT table for you -- FYI you can do a BIOS install if you have another spare PC and you clone that BIOS install but not everyone has access to spare computers nor the patience and insanity to deal with such 'work arounds' --- in terms of the different methods I would do the registry method as most people are afraid of using Clover--

cheers

Reply

Answer 13

TGIK Author

Level 1

23 points

May 9, 2020 6:39 PM in response to Nrmanaaas

You installed in UEFI mode correct? Are you using a thunderbolt or USB interface with Pro Tools?

The first thing is to create a patched DSDT

go to https://bitbucket.org/RehabMan/os-x-maciasl-patchmatic/downloads/

download MaciASL

run the program , it will load your dsdt - click the 'compile' button at the top -- then save as and send me a copy of your DSDT to patch -- my email is tacogenius@gmail.com

Reply

Answer 14

TGIK Author

Level 1

23 points

May 11, 2020 2:54 PM in response to Nrmanaaas

Start by re-installing Windows 10 in UEFI mode-- you need to have empty space on the drive for a Windows partition - I wouldn't use Bootcamp assistant I would just use disk utility to re-size your Mac partition(s) - once you have Windows 10 installed again I can help you from there-- my email is all over this thread - email me when you have Windows installed - then we can get your sound working --

Reply

Answer 15

TGIK Author

Level 1

23 points

May 14, 2020 11:57 AM in response to GustavoPi

So you made a patched dsdt (or one was made for you)?

You created a c:\dsdt folder?

you downloaded

Windows Binary Tools (WBT - Dec 2016) extracted to c:\dsdt directory. [ newer WBT has parsing errors]
Windows Driver Kit (WDK), which contains the Windows ASL Compiler (asl.exe)

extracted the first (WBT) to this newly created c:\dsdt folder?

ran the second installer?

ran this command

c: & cd \dsdt
set 64bit_OS_asl="C:\Program Files (x86)\Windows Kits\10\Tools\x64\ACPIVerify\asl.exe"
set 32bit_OS_asl="C:\Program Files (x86)\Windows Kits\10\Tools\x86\ACPIVerify\asl.exe"
copy /y %32bit_OS_asl% c:\dsdt > nul & copy /y %64bit_OS_asl% c:\dsdt > nul
if not exist c:\dsdt\asl.exe echo ERROR: Failed to copy asl.exe to c:\dsdt

and this command

c: & cd \dsdt
asl /loadtable dsdt-modified.aml

and this command

bcdedit -set TESTSIGNING ON

and it still is not booting in 'test mode' ?

-let me know

Cheers

Reply