just like I did everyday before that, but for some reason this time I didn't get any sound output and the volume feedback was delayed when I tried to turn the volume up/down. It has *not* experienced any water damage or drops, but I'm pretty sure this problem started when I plugged in my external power speakers' amp to the headphone jack. 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.I am really stumped by this problem, and I'm really hoping you guys can help as I'm pretty sure it's a hardware issue.īasically, I get no audio from my MacBook Pro Retina 13" Late 2013 A1502 16Gb 2.6GHz - everything else works beautifully as ever with this machine (incl USB & power) apart from the sound. 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)
