You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

TGIK Author

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

Top-ranking reply

xAndrewH1993x

Level 1

4 points

Posted on Oct 28, 2019 1:02 PM

Get Ready Set and Go! Tonight at 10:00pm EST, Valor (Script) goes live! https://www.youtube.com/watch?v=gLiz8Soxiig&feature=youtu.be @ http://howeitworks.com/valor

Valor: A Frankin-Mac Project

DSDT Patch to Enable Audio Drivers in EFI Installed Version of Windows 10, Blue Screen Of Death Fix, and more.

ALL THANKS GOES TO TGIK AND itayemi's METHODS! TGIK IS DA MAN! TGIK APPLE FOURM: https://discussions.apple.com/thread/250137979 AND itayemi's Windows Method (This without the script or drivers) (How to do this manually):http://www.itayemi.com/blog/2019/09/12/dual-booting-mac-osx-and-windows-on-macbookpro/ -THANKS AGAIN itayemi!

TGIK provided the full Mac/Clover bootloader version of creating a executing the DSDT patch, and gave a solution to the issue, itayemi provided a Windows alternative of creating and executing the DSDT patch. I'm the guy who took the two and made a script for Windows and added other needed and useful tools that is needed to make Windows 10 ver 1903 and higher to be compatible. This is the safest way without mistakenly bricking your Macbook and ruining your firmware. This is only targeted to MacBook Pro Early 2011 "13" inch models aka MacBookPro8,1.

Welcome to Valor!

Thanks for being here and giving this a spin!

1.) This is a script that will install a DSDT file to make your audio drivers work for your MacBook Pro Early 2011 in EFI mode. This is means if you want to install multiple Windows Partitions you can in EFI and you are no longer dependent on the DVD Rom.

2.) BootCamp drivers downloaded and changed as of 10/23/2019. The modifications are MacHaldriver.sys has been completely removed and through this script installs a MacHaldriver.inf instead to avoid Blue Screen Of Death with Windows 10 ver. 1903 or higher because of incompatibility. Untested on Mid 2011 and Late 2011 Macbooks, please provide feedback if there are any issues. This will be automatically executed when using the script.

3.) Legacy Windows essentials programs will be installed to ease user experience transitioning for Windows 7. Ninite will be executed to insure all users are setup with modern day browsers and including the must have tools to maintain this machine. Anti-Virus will be provided and other useful Microsoft programs including Windows Media Center-Port Over from Windows 7.

Please look into the Script Directory and Resources\Installers Directory to look over what will be installed or offered to be installed as you go through the script! Thanks again I hope you enjoy!

View in context

305 replies

Jan 26, 2020 11:45 AM in response to Spirit_TY

One other piece of advice do not install the drivers from the boot camp assistant tool do not download the drivers from Apple use the drivers that are inside of Valor which has been manipulated to work with the current version of Windows 10 build 1909.... The reason why I say this is because a while back whenever I was developing Valor Microsoft had release 1903 prior and I finally had updated to that build and realize that my project was broken and it was because of Apple not updating their certificates on the drivers making them compatible with Windows 10. they're only doing it for the newer edition of MacBooks that support Windows 10. See my model was only supported to Windows 7. But try it out if it doesn't work restore and then install your drivers and if you notice a blue screen then you have a driver problem.

KyuR_pt

Level 1

4 points

Jan 31, 2020 12:00 AM in response to Spirit_TY

Hi there! Is, by any chance your Windows user name comprised of two words, separated by a space? ( Like: Jonh Doe)?

I had a similar issue, and was the username that's responsible. Just created a local account to install Valor, than deleted it. Hope it helps

Jan 31, 2020 6:25 AM in response to Spirit_TY

I would still try KyuR_pt's troubleshooting steps which I will include in the Google doc going forward, if it still acts up I don't mind remote in to helping you with your issue using TeamViewer. I might be able to manually run Valor without running the whole script. I feel though KyUR_pt is right I remember running into a issue with Valor and then I thought it was windows and I wiped it reinstalled it name my user just "Andrew" not "Andrew Howe" now I understand why the issue couldn't be duplicated until now. Great Job! I wouldn't have figured that out because when I connect my Hotmail to my local account it creates "Andre" instead "Andrew Howe". Hmm interesting but let me know when you want me to remote in and help!

Jan 31, 2020 6:26 AM in response to KyuR_pt

Thank you for your feedback I'm going to give you recognition for this within the project itself on the next update! I'm going to upload this to the troubleshooting guide I'm making! You are the Bomb dot com buddy!

TGIK Author

Level 1

23 points

Jan 31, 2020 7:00 AM in response to Spirit_TY

How far did you initially get ? Were you able to do an EFI install at all ? Was is just sound not working ? I have my email (or at least did) somewhere in this forum -- I can edit your dsdt and guide you through the next steps -- it really is simpler then you think -- reach out to me on my email and I can help you--- or, like another client did, ship me your laptop and I will do it (though that will cost money) -- I think we can do it over email or video chat etc

Jan 31, 2020 8:19 AM in response to TGIK

Thank you everyone.

@KyuR_pt: I don't think this is the problem. I have since re-formatted 3 times and tried using only a single username. It is still the same result.

@xAndrewH1993x: Thank you for your offer to help. Please let me know your window of availability. I am in a timezone of GMT+1 but will make myself available anytime convenient for you. How can I reach you please? You can reach me via engrty.uj@gmail.com

@TGIK, thank you. I think my issue may be the DSDT since I use MBP Mid 2012. I'll also reach out to know how to edit my DSDT.

Jan 31, 2020 9:12 AM in response to TGIK

Hey TGIK do you mind helping Spirit with his DSDT file? I'm not as comfortable to creating other people's DSDT files, I will create a Valor patch specifically for him! I just need the DSDT file specifically for him.

Jan 31, 2020 9:24 AM in response to TGIK

Cool you always and will be great at that process, I wish y'all the best at it! If you can let him know to send me the DSDT or if you can my man and then I'll send him a Google drive Link once I make Valor patch for him. TTYL

TGIK Author

Level 1

23 points

Jan 31, 2020 6:39 PM in response to xAndrewH1993x

I walked him through it -- he will send you the modified dsdt -- I do really appreciate your spearheading this forum as I have been swamped the last year --- I know I have said it a million times but I need to/will make a video because there are some extra things I can show that might interest people (hfs partitions for booting exotic OS's, custom booter icons etc) -- I also have the rare windows 7 uefi install on the same machine (though it has disappeared many times, but cool nonetheless)

Jan 31, 2020 6:59 PM in response to TGIK

That is awesome bro, I would love to see what you have to share! I will support your future projects as long as I'm allowed too. I will continue to show support here about Valor and continue to aid your cause! Believe me though when I say this, I will not step on your toes. I also hope that Valor is not going to be swept under the rug as it took me a lot of unpaid volunteered time to help individuals. I would honestly like to work with you on your personal projects if you are down! Windows 7 UEFI is pretty cool since Microsoft never officially made a ISO of it, super impressed. I would like to learn about the HFS partitions for booting exotic OSs. Current setup of mine is reFind with Prime OS (Android x86 Project), Windows 10 build 1909, Linux Mint, and MacOS Catalina patched by dosdude1. Duel SSDs and no SuperDrive..... So I'm definitely down to learning more from ya! I hope that we can build off of each other's success here from helping people genuinely. What I would love to learn is how to integrate a network card into my machine without sacrificing my SATA ports and still keep Duel SSDs. I've been trying to find a SATA to USB or SATA to ePCI Adapters so I can stick a wireless carrier network card in. I found a way to get Unlimited Hotspot internet from Sprint... now just got to integrate it. Thank you for helping him as well and for the thought of shooting over the DSDT file!

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. (~_*)

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.

TGIK Author

Level 1

23 points

Feb 2, 2020 9:31 AM in response to Spirit_TY

I have been working on that problem for quite a while with varied results (though none actually getting the thunderbolt bridge to be recognized) -- the strangest attempt was doing a BIOS install of windows and looking at how it mapped the memory (since thunderbolt works with CSM layer of bootcamp) and creating a DSDT based on those memory ranges; strangely, even without a qword entry, the sound worked but now there were different devices that windows could not allocate into memory -> The HD3000 graphics, a couple of system devices etc.....what I am attempting now is to study the lspci output from linux to see how it maps the devices into memory and perhaps create a dsdt to reflect that ---I am hoping someone in the linux community can teach me how to create a dsdt extrapolated from the ouptut of lspci --- in the hackintosh world we often create a SSDT (secondary system description table) to get thunderbolt working -- but I don't believe Windows can use a modified SSDT -- so maybe we can crack the nut - hoping to do so

Cheers,

Glad we got it all working for ya

Feb 4, 2020 6:03 AM in response to TGIK

Hey buddy some of this is going over my head again, you are clearly incredibly intelligent! Does this help at all? https://www.insanelymac.com/forum/topic/240435-dsdt-using-gfxutil-to-find-pci-locations/ I honestly don't know what I'm looking for to assist you. I hope some of this information from the forum can be some help like how you came across the other forum that gave you the idea of the sound fix.

TGIK Author

Level 1

23 points

Feb 4, 2020 3:01 PM in response to xAndrewH1993x

Humbly flattered sir --- I cannot code in the same way you can in terms of software -- so we all have our strengths --

I will have to post the output in multiple messages due to Apples stupid 5000 character limit;

mbp@mbp-MacBookPro:~$ lspci -v

00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)

Subsystem: Apple Inc. 2nd Generation Core Processor Family DRAM Controller

Flags: bus master, fast devsel, latency 0

Capabilities: <access denied>

00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) (prog-if 00 [Normal decode])

Flags: bus master, fast devsel, latency 0, IRQ 16

Bus: primary=00, secondary=01, subordinate=01, sec-latency=0

Memory behind bridge: a0800000-a08fffff

Capabilities: <access denied>

Kernel driver in use: pcieport

Kernel modules: shpchp

00:01.1 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) (prog-if 00 [Normal decode])

Flags: bus master, fast devsel, latency 0, IRQ 16

Bus: primary=00, secondary=05, subordinate=9b, sec-latency=0

I/O behind bridge: 00003000-00003fff

Memory behind bridge: a0a00000-a4efffff.

Prefetchable memory behind bridge: 00000000a4f00000-00000000a8efffff

Capabilities: <access denied>

Kernel driver in use: pcieport

Kernel modules: shpchp

MBP UEFI WINDOWS SOUND FIXED!!!!