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

TGIK Author

Level 1

23 points

Feb 4, 2020 3:06 PM in response to TGIK

00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])

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

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

Memory at a0000000 (64-bit, non-prefetchable) [size=4M]

Memory at 90000000 (64-bit, prefetchable) [size=256M]

I/O ports at 2000 [size=64]

[virtual] Expansion ROM at 000c0000 [disabled] [size=128K]

Capabilities: <access denied>

Kernel driver in use: i915

Kernel modules: i915

00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)

Subsystem: Intel Corporation Apple MacBookPro8,2 [Core i7, 15", 2011]

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

Memory at a0907100 (64-bit, non-prefetchable) [size=16]

Capabilities: <access denied>

Kernel driver in use: mei_me

Kernel modules: mei_me

00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Universal Host Controller #5 (rev 05) (prog-if 00 [UHCI])

Subsystem: Intel Corporation Apple MacBookPro8,2 [Core i7, 15", 2011]

Flags: bus master, medium devsel, latency 0, IRQ 21

I/O ports at 2120 [size=32]

Capabilities: <access denied>

Kernel driver in use: uhci_hcd

00:1a.7 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) (prog-if 20 [EHCI])

Subsystem: Intel Corporation Server Board S1200BTS / Apple MacBook Pro 8,1/8,2

Flags: bus master, medium devsel, latency 0, IRQ 23

Memory at a0906c00 (32-bit, non-prefetchable) [size=1K]

Capabilities: <access denied>

Kernel driver in use: ehci-pci

TGIK Author

Level 1

23 points

Feb 4, 2020 3:13 PM in response to TGIK

00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC Controller (rev 05)

Subsystem: Intel Corporation Apple MacBookPro8,2 [Core i7, 15", 2011]

Flags: bus master, medium devsel, latency 0

Capabilities: <access denied>

Kernel driver in use: lpc_ich

Kernel modules: lpc_ich

00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 05) (prog-if 01 [AHCI 1.0])

Subsystem: Intel Corporation Apple MacBookPro8,2 [Core i7, 15", 2011]

Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 43

I/O ports at 2148 [size=8]

I/O ports at 215c [size=4]

I/O ports at 2140 [size=8]

I/O ports at 2158 [size=4]

I/O ports at 2060 [size=32]

Memory at a0906000 (32-bit, non-prefetchable) [size=2K]

Capabilities: <access denied>

Kernel driver in use: ahci

Kernel modules: ahci

00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)

Subsystem: Intel Corporation Server Board S1200BTS / Apple MacBook Pro 8,1/8,2

Flags: medium devsel, IRQ 18

Memory at a0907000 (64-bit, non-prefetchable) [size=256]

I/O ports at efa0 [size=32]

Kernel driver in use: i801_smbus

Kernel modules: i2c_i801

02:00.0 Ethernet controller: Broadcom Limited NetXtreme BCM57765 Gigabit Ethernet PCIe (rev 10)

Subsystem: Broadcom Limited NetXtreme BCM57765 Gigabit Ethernet PCIe

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

Memory at a0400000 (64-bit, prefetchable) [size=64K]

Memory at a0410000 (64-bit, prefetchable) [size=64K]

Capabilities: <access denied>

Kernel driver in use: tg3

Kernel modules: tg3

TGIK Author

Level 1

23 points

Feb 4, 2020 3:18 PM in response to TGIK

02:00.1 SD Host controller: Broadcom Limited BCM57765/57785 SDXC/MMC Card Reader (rev 10) (prog-if 01)

Subsystem: Broadcom Limited BCM57765/57785 SDXC/MMC Card Reader

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

Memory at a0420000 (64-bit, prefetchable) [size=64K]

Capabilities: <access denied>

Kernel driver in use: sdhci-pci

Kernel modules: sdhci_pci

03:00.0 Network controller: Broadcom Limited BCM4331 802.11a/b/g/n (rev 02)

Subsystem: Apple Inc. AirPort Extreme

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

Memory at a0600000 (64-bit, non-prefetchable) [size=16K]

Capabilities: <access denied>

Kernel driver in use: wl

Kernel modules: bcma, wl

04:00.0 FireWire (IEEE 1394): LSI Corporation FW643 [TrueFire] PCIe 1394b Controller (rev 08) (prog-if 10 [OHCI])

Subsystem: LSI Corporation FW643 [TrueFire] PCIe 1394b Controller

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

Memory at a0500000 (64-bit, non-prefetchable) [size=4K]

Capabilities: <access denied>

Kernel driver in use: firewire_ohci

Kernel modules: firewire_ohci

TGIK Author

Level 1

23 points

Feb 4, 2020 3:22 PM in response to TGIK

05:00.0 PCI bridge: Intel Corporation CV82524 Thunderbolt Controller [Light Ridge 4C 2010] (prog-if 00 [Normal decode])

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

Bus: primary=05, secondary=06, subordinate=6b, sec-latency=0

Memory behind bridge: a0a00000-a0efffff

Prefetchable memory behind bridge: 00000000a4f00000-00000000a5afffff

Capabilities: <access denied>

Kernel driver in use: pcieport

Kernel modules: shpchp

06:00.0 PCI bridge: Intel Corporation CV82524 Thunderbolt Controller [Light Ridge 4C 2010] (prog-if 00 [Normal decode])

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

Bus: primary=06, secondary=07, subordinate=07, sec-latency=0

Memory behind bridge: a0c00000-a0cfffff

Capabilities: <access denied>

Kernel driver in use: pcieport

Kernel modules: shpchp

06:03.0 PCI bridge: Intel Corporation CV82524 Thunderbolt Controller [Light Ridge 4C 2010] (prog-if 00 [Normal decode])

Physical Slot: 2

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

Bus: primary=06, secondary=08, subordinate=08, sec-latency=0

Memory behind bridge: a0b00000-a0bfffff

Prefetchable memory behind bridge: 00000000a4f00000-00000000a50fffff

Capabilities: <access denied>

Kernel driver in use: pcieport

Kernel modules: shpchp

06:04.0 PCI bridge: Intel Corporation CV82524 Thunderbolt Controller [Light Ridge 4C 2010] (prog-if 00 [Normal decode])

Physical Slot: 3

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

Bus: primary=06, secondary=09, subordinate=39, sec-latency=0

Memory behind bridge: a0d00000-a0dfffff

Prefetchable memory behind bridge: 00000000a5100000-00000000a52fffff

Capabilities: <access denied>

Kernel driver in use: pcieport

Kernel modules: shpchp

TGIK Author

Level 1

23 points

Feb 4, 2020 7:03 PM in response to TGIK

06:05.0 PCI bridge: Intel Corporation CV82524 Thunderbolt Controller [Light Ridge 4C 2010] (prog-if 00 [Normal decode])

Physical Slot: 4

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

Bus: primary=06, secondary=3a, subordinate=6a, sec-latency=0

Memory behind bridge: a0e00000-a0efffff

Prefetchable memory behind bridge: 00000000a5300000-00000000a54fffff

Capabilities: <access denied>

Kernel driver in use: pcieport

Kernel modules: shpchp

06:06.0 PCI bridge: Intel Corporation CV82524 Thunderbolt Controller [Light Ridge 4C 2010] (prog-if 00 [Normal decode])

Physical Slot: 5

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

Bus: primary=06, secondary=6b, subordinate=6b, sec-latency=0

Memory behind bridge: a0a00000-a0afffff

Prefetchable memory behind bridge: 00000000a5500000-00000000a56fffff

Capabilities: <access denied>

Kernel driver in use: pcieport

Kernel modules: shpchp

07:00.0 System peripheral: Intel Corporation CV82524 Thunderbolt Controller [Light Ridge 4C 2010]

Subsystem: Device 2222:1111

Physical Slot: 1

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

Memory at a0c00000 (32-bit, non-prefetchable) [size=256K]

Memory at a0c40000 (32-bit, non-prefetchable) [size=4K]

Capabilities: <access denied>

Kernel driver in use: thunderbolt

Kernel modules: thunderbolt

TGIK Author

Level 1

23 points

Feb 4, 2020 7:09 PM in response to TGIK

So what I am pointing out is that linux shows you how they are mapping the devices into memory -- in the same way I used a BIOS install of Windows 10 to make a test DSDT that worked with sound without the same qwords (though there were other problems as stated earlier) I want to make a dsdt that reflects the values of how linux and I presume freebsd etc. allocate devices into memory --

PS. Everybody should have a linux install on their MAC -- it is the swiss army knife and has built-in gdisk to remove hybrid partition schemes which appear to be a big problem with people installing Windows on their Macs in pure EFI (Windows is stupid and requires a pure GPT disk)

Also - Andrew -- you can use the driver manager in Linux to install the Broadcom drivers (as you stated) -- but you can do it even without an ethernet connection -- if you make a linux live USB - those drivers exist on that USB -- and to everybody -- rEFIt -> rEFInd are great products - but I encourage people to learn how to use Macs built in bootloader -- I press alt when I turn on my computer and have custom booter partitions that boot all my OS's ---OSX, Windows 10, Linux, FreeBSD, Haiku, Android, I promise to make a video soon -- will make a short one of my bootloader first -- cause that's easy -- love to all-- goodnight

Loner T

Level 9

59,513 points

Feb 5, 2020 6:04 PM in response to TGIK

TGIK wrote:

PS. Everybody should have a linux install on their MAC -- it is the swiss army knife and has built-in gdisk to remove hybrid partition schemes which appear to be a big problem with people installing Windows on their Macs in pure EFI

Lots of 'Live' CD/USB are available, if necessary

(Windows is stupid and requires a pure GPT disk)

...and all these contortions to make a stupid OS produce Audio and support Thunderbolt. 👍

TGIK Author

Level 1

23 points

Feb 6, 2020 7:11 AM in response to Loner T

Of course you could run just live versions...why not have a faster resident version on an internal SSD?

Why not learn how linux works and see the parallels between it and OSX?

For me linux forced me to get my terminal skills better which in turn me more comfortable with the terminal in OSX - the place where you really can do 'power lifting'

Linux also illuminated to me the use of the var, usr, tmp folders which are made hidden in OSX but are still there---again, god forbid one wants to understand how something works and peek behind the 'appliance like' veil that Apple creates

And yes, Windows is stupid in the sense of how it takes that dsdt in firmware as god's word and doesn't allocated devices in the larger 64bit address space available (among other things) -- but that doesn't mean Windows doesn't have a lot of good and useful software ----15 years ago for the bootcamp beta released for OSX Tiger I needed Windows XP to run some VST's that were not available for Mac -- So I installed Windows.......I like a lot of the wifi scanning tools for Windows more then Mac -- so I use Windows --- For the theater company I do IT for I needed a TCP to RS232 forwarder --and there were amazing ones written for Windows so.......

Do I have standalone Windows machines? Of course

Is it it nice to be able to run any software for any OS on the same computer? Yes

could you use VMWare? Yes--- do you have to pay for VMWare? Yes ---Does bare-metal perform better then virtualized solutions? Generally yes

All of the 'contortions' are also an interesting dive into understanding how or why something does or doesn't work --

You, Apple and many others said there was no way to enable sound on pre 2013 Macs--- We found a way --

Is this why you seem particularly salty?

You seem to help many people as you are ubiquitous on these Apple forums --so you should be commended --

but why are you sweating this thread like that?

Feb 6, 2020 7:52 AM in response to TGIK

Hahaha tell'em! I hear the sizzlin burn! OMG I'm LMFAO. He is right Linux is needed, **** have you looked at their Disk Utility tool.... Another great tool - Gparted got it beat by a million. Most of the time the Disk Utility is breaking my partitions. So don't be hater 😉 when we Geeks unite. Apple can go burn itself. As long as they keep ripping people off, the more I will support causes such as this.

Loner T

Level 9

59,513 points

Feb 6, 2020 7:29 PM in response to xAndrewH1993x

TGIK wrote:

All of the 'contortions' are also an interesting dive into understanding how or why something does or doesn't work --

Reverse engineering is an art, not science.

You, Apple and many others said there was no way to enable sound on pre 2013 Macs--- We found a way --

The specific implementation of CSM-BIOS and EFI 'hides' devices', not that they are inaccessible. The same devices show using preUEFI in macOS.

Is this why you seem particularly salty?

I assume you understand the Security implications of such changes.

but why are you sweating this thread like that?

See the previous comment.

Loner T

Level 9

59,513 points

Feb 6, 2020 7:34 PM in response to xAndrewH1993x

xAndrewH1993x wrote:

have you looked at their Disk Utility tool.... Another great tool - Gparted got it beat by a million.

Let me know when GParted can understand APFS or CoreStorage.

Most of the time the Disk Utility is breaking my partitions.

A tool in can be used or abused. 😉

Apple can go burn itself. As long as they keep ripping people off, the more I will support causes such as this.

..and you are posting this on Apple-hosted forum. 🤣 I assume you have a Mac, correct?

Feb 8, 2020 6:14 AM in response to Loner T

https://www.bbc.com/news/technology-51413724 must I say anything else..... Have a great day. I have expressed myself more than enough, I'm here to help people see the truth and fix there MacBook Pros that Apple "decided" not to support. If that's offensive sorry buddy.

Feb 8, 2020 8:52 AM in response to Loner T

I think we are all big boys and know how to handle our security 😉 Thanks. I've been in the wireless industry for 8 years now, from experience I've seen the worst of iOS products and let me tell you it doesn't take 15-30 minutes to restore a phone accept an iPad in an iPhone (this is including downloading the ipsw). So again you can sit here and defend them until your blue in the face but I will never be converted after being screwed out of my money. I can use Samsung smart switch restore my phone back to where it was and be done with it. Includes restoring my backup and firmware within 30mins. If you are really smart you can use Odin to restore the devices and be done within 5 minutes. I can definitely say Apple needs to work on the consideration for people who has to troubleshoot their devices especially when you are working through one of the carriers and you got that stubborn customer that won't leave because they can't comprehend that they have to go through Apple. Hahaha when it's a simple factory reset that you have to do through iTunes just to remove the passcode lock. Haha.... Now let's move on... This forum is apparently not to your liking, I don't care if this is a iForum or a Apple Forum. We are "fixing" a unsupported product, it's the end user's responsibility to continue to use a end of life product and know the risks. Good day to you sir.

TGIK Author

Level 1

23 points

Feb 10, 2020 1:00 PM in response to xAndrewH1993x

Fun times I see people are having on this thread....It appears Loner T has the sort of 'myopic Apple fan boy' point of view because he (or she I suppose) never wants to point out any inadequacies on Apple's part, which is fundamentality an intellectually disingenuous position to have....Or maybe it's all in good fun and he has a strange sense of humor and finds the 'copy-what-you-wrote-and-editorialize' style responses charming......either way he has never been helpful in the thread. I commend his work helping other people, but again, he has provided very little substance in this discussion other then the occasional snarky missive...which I find mildly amusing ---so cheers to All

Loner T

Level 9

59,513 points

Feb 10, 2020 1:20 PM in response to TGIK

TGIK wrote:

It appears Loner T has the sort of 'myopic Apple fan boy' point of view because he (or she I suppose) never wants to point out any inadequacies on Apple's part, which is fundamentality an intellectually disingenuous position to have....

I point Apple's inadequacies to Apple, and not in a public Apple forum (see https://feedbackassistant.apple.com). Not supporting UEFI on a 2011 Mac (9 years old) is a product decision. 2012 Macs are preUEFI and still supported. Also, there is a very public set of articles documenting Apple's failures on Nvidia and AMD GPUs and batteries which does not need repeating.

Or maybe it's all in good fun and he has a strange sense of humor and finds the 'copy-what-you-wrote-and-editorialize' style responses charming......

It is indeed in good fun. 😉

I commend his work helping other people, but again, he has provided very little substance in this discussion other then the occasional snarky missive...which I find mildly amusing

There is a 'fully' supported method to run Windows on a 2011 (and older) Mac, which does not need any changes. You have an alternative 'method', borne out of intellectual/academic curiosity, which you admit does cause new issues, but is fine, if users do not care about such.

macOS has used EFI (1.x) for many years, which is not anything new. Most Linux distribution methods have also supported EFI 1.x.

Whether you (or anyone else) on this discussion dislikes Apple for their business practices, it is their problem, not necessarily Apple's.

MBP UEFI WINDOWS SOUND FIXED!!!!