Jump to content
Pimentel

Gerenciamento de energia para Sandy Bridge/Ivy Bridge/Haswell CPU

272 posts in this topic

Recommended Posts

Segui o tutorial, patcheei o kernel, ativei a flag no clover, criei o ssdt, coloquei na pasta "acpi/patched" e reiniciei. O sistema dá o boot, mas chega em uma parte que fala que o gerenciamento de energia é desconhecido "algo do tipo", da timeout na ACPM e o sistema reinicia.

Estou usando smbios 15.1. Uma coisa que notei é que quando a kext disabler estava na pasta de kexts no efi, o sistema subia normalmente.

 

EDIT: eu havia esquecido de adicionar algumas coisas no clover. A kextdisabler não tem nada a ver com o problema que eu estava  tendo.

 

O sistema iniciou legal, mas estou com um probleminha aqui que me impossibilita de instalar qualquer coisa na pasta /System/Extensions, pois sempre dá erro.

 

Vou tentar ver se consigo corrigir, pra poder instalar algum app que monitore os states da cpu pra ver se está funcionando corretamente.

 

Problema corrigido.

 

EDIT2: nem a X86PlatformPlugin e nem a AppleLPC estão carregadas. Apenas a ACPI_SMC_PlatformPlugin carrega.

 

Olhem essa mensagem que aparece no boot: 

 

SeR84IY.jpg

 

O que eu faço? 

Share this post


Link to post
Share on other sites
Advertisement

Se o CPU for o da assinatura, está usando -xcpm e KernelPM?

 

Para carregar a LPC seria interessante aplicar um patch no DSDT.

Share this post


Link to post
Share on other sites

Se o CPU for o da assinatura, está usando -xcpm e KernelPM?

 

Para carregar a LPC seria interessante aplicar um patch no DSDT.

Opa, é sim o da assinatura. Estou usando apenas o KernelPM. Vou colocar o -xcpm no clover e vê no que dá. 

 

Brigadão pelo suporte!  :thumbsup_anim:

 

@Allan

 

Adicionei o -xcpm mas deu no mesmo. Outra coisa estranha, é o turbo que não está funcionando. No ssdt tá configurado a frequência do turbo, mas olhando pelo Intel Power Gadget a frequência só tá indo até 3.5GHz, que é a frequência máxima sem turbo.

Share this post


Link to post
Share on other sites

Voce não precisa usar SSDT modificado, apenas as opções que te falei.

Removi o SSDT e agora o turbo boost funciona. 

 

Com relação a LPC, não estou conseguindo achar o patch pra aplicar na dsdt. E sobre a X86PlatformPlugin, como fazer pra ela ser carregada? Só quando a LPC for carregada também?

Share this post


Link to post
Share on other sites

olá

into method label _DSM parent_label LPCB remove_entry;into device label LPCB insert begin
Method (_DSM, 4, NotSerialized)\n
{\n
Store (Package (0x02) {\n
"compatible", Buffer () {"pci8086,8c44"}\n
}, Local0)\n
DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))\n
Return (Local0)\n
}
end;

precisas também do DTGP

 

bom hack

Share this post


Link to post
Share on other sites

O Artur-pt te passou o patch para o LPC, caso tenha problemas, apenas mude o Ven/Dev ID para o seu.

 

Para termos certeza de como está seu gerenciamento de energia, verifique no IOReg. Entenda que a escolha certa de um SMBios influi nisso. Está usando qual modelo ai?

 

Tem que ter as informações como mostra abaixo no campo CPU0@0

WTc.png

Share this post


Link to post
Share on other sites

olá

into method label _DSM parent_label LPCB remove_entry;into device label LPCB insert begin

Method (_DSM, 4, NotSerialized)\n

{\n

Store (Package (0x02) {\n

"compatible", Buffer () {"pci8086,8c44"}\n

}, Local0)\n

DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))\n

Return (Local0)\n

}

end;

precisas também do DTGP

 

bom hack

 

 

Valeu artur! =D

 

O Artur-pt te passou o patch para o LPC, caso tenha problemas, apenas mude o Ven/Dev ID para o seu.

 

Para termos certeza de como está seu gerenciamento de energia, verifique no IOReg. Entenda que a escolha certa de um SMBios influi nisso. Está usando qual modelo ai?

 

Tem que ter as informações como mostra abaixo no campo CPU0@0

WTc.png

Então, ainda não apliquei patchs e tals. Olhei no ioreg e está assim:

post-637410-0-97055000-1431096102_thumb.jpg

Share this post


Link to post
Share on other sites

Está com o gerenciamento de energia errado!

 

Aconselho usar um SMBios de MacPro. E adiciona o patch para adiantar as coisa para você.  ;)

Share this post


Link to post
Share on other sites

Está com o gerenciamento de energia errado!

 

Aconselho usar um SMBios de MacPro. E adiciona o patch para adiantar as coisa para você.  ;)

Mas não existe nenhum MacPro com Haswell. O máximo que tem é MacPro 6,1, que é com Ivy Bridge EP.  

 

 

EDIT: ao compilar a DSDT, deu mais de 80 erros (vide anexo) e não consegui dar boot no sistema, pois dá kernel panic.

 

Fiz o boot usando o pendrive de instalação do sistema, e quando entrei no sistema vi que a x86sei lá o que havia carregado, mas não carregou ainda a LPC (vide anexo também).

post-637410-0-27611200-1431100090_thumb.jpg

post-637410-0-05985300-1431100106_thumb.jpg

Share this post


Link to post
Share on other sites

Não precisa se policiar com relação a isso.

 

Pois CPUs com IvyBridge também necessitam do plugin X86PlatformPlugin para ter o gerenciamento de energia correto.

Share this post


Link to post
Share on other sites

Não precisa se policiar com relação a isso.

 

Pois CPUs com IvyBridge também necessitam do plugin X86PlatformPlugin para ter o gerenciamento de energia correto.

Eu testei o smbios do macpro 6,1 mas deu na mesma.  :wallbash:

 

Sem conseguir compilar direito essa dsdt, fica complicado.  :rolleyes:

Share this post


Link to post
Share on other sites

Vamos fazer o seguinte, você tem entradas USB3 certo? Já instalou o kext responsável para o devido reconhecimento das USBs?

Share this post


Link to post
Share on other sites

Vamos fazer o seguinte, você tem entradas USB3 certo? Já instalou o kext responsável para o devido reconhecimento das USBs?

Aqui tinha aquela kext genérica, mas eu a removi pois não preciso usar mais ela. Quando ela tá no sistema, as portas USB ficam "malucas", já sem ela, funciona tudo normalmente.

Share this post


Link to post
Share on other sites

Você se refere a GenericUSBXHCI?

 

Utilizou ela com os boot arguments apropriados?

Sim. É ela mesmo.

 

Quais arguments você se refere? FixUSB, inject usb sei lá o que, clockid e ownership (acho que é isso)?

 

Se sim, usei todas elas mas continuavam malucas.

Share this post


Link to post
Share on other sites

Me refiro a esses:

-gux_defer_usb2 -gux_no_idle

Vamos fazer um teste? Instala essa versão, attachicon.gifGenericUSBXHCI.kext.zip e usa os boot arguments que te falei acima.

Cara, desculpa a pergunta, mas o que tem a ver o USB3 com o gerenciamento de energia processador? Tu não estás confundindo os tópicos não?  :P

Share this post


Link to post
Share on other sites

Bem, se você realmente leu este topico, verá o que eu expliquei na pag. 3: http://www.insanelymac.com/forum/topic/295577-gerenciamento-de-energia-para-sandy-bridgeivy-bridgehaswell-cpu/page-3

 

Não é preciso (ainda) usar SSDT modificada, apenas usar os boot arguments que te falei.

Se quiser é claro, talvez você tenha encontrado um método melhor para corrigir seu problema...

Share this post


Link to post
Share on other sites

Bem, se você realmente leu este topico, verá o que eu expliquei na pag. 3: http://www.insanelymac.com/forum/topic/295577-gerenciamento-de-energia-para-sandy-bridgeivy-bridgehaswell-cpu/page-3

 

Não é preciso (ainda) usar SSDT modificada, apenas usar os boot arguments que te falei.

Se quiser é claro, talvez você tenha encontrado um método melhor para corrigir seu problema...

Você está falando disto aqui:

 

http://www.insanelymac.com/forum/topic/295577-gerenciamento-de-energia-para-sandy-bridgeivy-bridgehaswell-cpu/page-3?do=findComment&comment=1996457

 

As imagens da página 3 estão todas quebradas, o que impossibilita eu ver o que havia nas imagens postadas pelos outros membros e por você.

 

Pois bem, o argument que você citou no post anterior eu usei quando fui instalar o sistema, pois sem ele dava o famoso erro do "Missing Bluetooth Controller Transport". Irei adicionar a kext novamente e usar a flag que você fala. Já já posto aqui o que deu.

 

EDIT: fiz como você falou e as portas USB estão funcionando corretamente. E agora?

Share this post


Link to post
Share on other sites

EDIT: fiz como você falou e as portas USB estão funcionando corretamente. E agora?

 

Abra o IOReg e verifique.

Share this post


Link to post
Share on other sites

Abra o IOReg e verifique.

Continua a mesma coisa. Nada da x86 e nem da LPC.

Share this post


Link to post
Share on other sites

Já aplicou o patch LPC no seu DSDT?

Havia aplicado, mas como falei, dá aquele bocado de erros na compilação e kernel panic na hora do boot.

Share this post


Link to post
Share on other sites

Você sabe como achar o device LPC e aplicar o patch no local correto?

 

Usa esse aqui:

Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method                {
                    Store (Package (0x0C)
                        {
                            "device-id", 
                            Buffer (0x04)
                            {
                                 0x02, 0x3B, 0x00, 0x00
                            }, 
                            "compatible", 
                            Buffer (0x0D)
                            {
                                "pci8086,3b02"
                            }, 
                            "IOName", 
                            Buffer (0x0D)
                            {
                                "pci8086,3b02"
                            }, 
                            "name", 
                            Buffer (0x0D)
                            {
                                "pci8086,3b02"
                            }, 
                            "subsystem-id", 
                            Buffer (0x04)
                            {
                                 0x01, 0x50, 0x00, 0x00
                            }, 
                            "subsystem-vendor-id", 
                            Buffer (0x04)
                            {
                                 0x58, 0x14, 0x00, 0x00
                            }
                        }, Local0)
                    DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                    Return (Local0)
                }
            }

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

Announcements

  • Similar Content

    • By MaLd0n
      -Donations with PayPal
      https://tinyurl.com/r2bvzm7
       
      -Donations with Bitcoin
      33HeGCuCSh4tUBqdYkQqKpSDa1E7WeAJQ3
       
      -Donations with PicPay 
      @danielnmaldonado
        Nehalem, SandyBridge, IvyBridge, Haswell, Broadwell   https://www.olarila.com/topic/5794-guide-install-macos-with-olarila-image-step-by-step-install-and-post-install-windows-or-mac/   Skylake, Kabylake and Coffeelake is here https://www.olarila.com/topic/5794-guide-install-macos-with-olarila-image-step-by-step-install-and-post-install-windows-or-mac/   Install MacOS with Olarila Image, Step by Step, Install and Post Install
       
      https://www.olarila.com/topic/5794-guide-install-macos-with-olarila-image-step-by-step-install-and-post-install-windows-or-mac/
          First...   ***Update bios to last available version!***   If you need a full patched DSDT...  -Extract tables with F4 key in Clover boot screen! -Run it and send me files! RunMe.app   Installation   --Create a bootable copy of macOS Sierra / High Sierra / Mojave   https://github.com/chris1111/Create-Install-Media/releases   --Install Clover in USB stick   https://github.com/CloverHackyColor/CloverBootloader/releases   --Replace with my Clover folder https://www.olarila.com/topic/5676-clover-folder-for-all-chipsets/   --Install Sierra/High Sierra and boot into system!   Post Installation --Install Clover and replace with my folder   https://www.olarila.com/topic/5676-clover-folder-for-all-chipsets/   --Reboot and activate video!   Bingo!   Now you need a fine tune! DSDT time!   --DSDT   Patches -FIX ERRORS AND WARNINGS -HPET -SATA -DMAC -SLPB -DARWIN -LPC -XHCI -PLUGIN TYPE -XXXX to HDEF -HDEF -RTC -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -LAN -USBX -PMCR -EC -PNLF -HDMI
       
      --Power Management
      - 1 Generation Intel Processors, use Generate P and C States in config.plist
      - 2 and 3 Generations Intel Processors, Generate SSDT with Piker script and drop CpuPm and Cpu0Ist SSDTs
      ssdtPRGen.command.zip
      Credits-https://github.com/Piker-Alpha/ssdtPRGen.sh
      - 4 Generation+ Intel Processors, use PluginType=1 in DSDT, SSDT or Clover config.plist
       
      for check Power, Frequency, Temperature and Utilization, use it
       
      Install Intel Power Gadget.pkg.zip
       
      --Brightness
      Install .app, select the required permission and reboot. Work in F1 / F2 keys!
      NativeDisplayBrightness.app.zip


      https://github.com/Bensge/NativeDisplayBrightness/releases
      *in some cases .app don't work, check patches in config.plist inside Clover folder Post Install
       
      --Clover
       
      https://sourceforge.net/projects/cloverefiboot/files/Installer/
       
      --AUDIO
       
      Use DSDT + AppleAlc
       
      --install Lan driver by Mieze
        -Atheros   http://www.insanelymac.com/forum/files/file/313-atherose2200ethernet/   -Intel   http://www.insanelymac.com/forum/files/file/396-intelmausiethernet/   -Realtek   http://www.insanelymac.com/forum/files/file/88-realtekrtl8111-binary/   --Links   -FakeSMC   https://bitbucket.org/RehabMan/os-x-fakesmc-kozlek   -Audio   https://github.com/vit9696/AppleALC http://www.insanelymac.com/forum/topic/314406-voodoohda-289/   -USB   https://bitbucket.org/RehabMan/os-x-usb-inject-all/downloads   It's time to Rock   -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!   Apple, Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad and many, many, many others!   We're all here to have fun and learn from each other!  
    • By Kailash
      I successfully managed to install Hackintosh on my Lenovo Ideapad 520 but now I don't have audio, brightness control feature or battery indicator. My audio driver is an ALC230. I am new to all this. What do I do to solve this? I have attached my EFI files below.
      EFI.zip
    • By chatelp
      Hi all !
       
      I'm migrating from Clover to OpenCore and stuck on an ACPI error at boot:
      ACPI Error [_STA] Namespace lookup failure, AE_ALREADY_EXISTS This comes from trying to load my custom SSDT-EC tables.
       
      From what I gather, the preferred method of dealing with EC0 for Desktops with OC is to add an _STA method to EC0 to change return code to 0, and then to add a new fake EC device. Both done via SSDT-EC.
       
      Problem is, my EC0 defined in the system DSDT already has an _STA method. And it looks like it can't be overridden through SSDT redefinition at boot. Is this excepted ACPI behavior? Is it not possible to override/redefine methods like _STA? If so, what other option do I have?
       
      Here is the original EC0 device in DSDT
      Device (EC0) { Name (_HID, EisaId ("PNP0C09")) // _HID: Hardware ID Name (_UID, One) // _UID: Unique ID Name (_GPE, 0x6E) // _GPE: General Purpose Events Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0F) } ....  
      Here is my very standard SSTD-EC for Skylake:
       
      /* * AppleUsbPower compatibility table for Skylake+. * * Be warned that power supply values can be different * for different systems. Depending on the configuration * these values must match injected IOKitPersonalities * for com.apple.driver.AppleUSBMergeNub. iPad remains * being the most reliable device for testing USB port * charging support. * * Try NOT to rename EC0, H_EC, etc. to EC. * These devices are incompatible with macOS and may break * at any time. AppleACPIEC kext must NOT load. * See the disable code below. * * Reference USB: https://applelife.ru/posts/550233 * Reference EC: https://applelife.ru/posts/807985 */ DefinitionBlock ("", "SSDT", 2, "ACDT", "SsdtEC", 0x00001000) { External (_SB_.PCI0.LPCB, DeviceObj) /* * Uncomment replacing EC0 with your own value in case your * motherboard has an existing embedded controller of PNP0C09 type. * * While renaming EC0 to EC might potentially work initially, * it connects an incompatible driver (AppleACPIEC) to your hardware. * This can make your system unbootable at any time or hide bugs that * could trigger randomly. */ External (_SB_.PCI0.LPCB.EC0, DeviceObj) Scope (\_SB.PCI0.LPCB.EC0) { Method (_STA, 0, NotSerialized) // _STA: Status { If (_OSI ("Darwin")) { Return (0) } Else { Return (0x0F) } } } Scope (\_SB) { Device (USBX) { Name (_ADR, Zero) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If ((Arg2 == Zero)) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x08) { "kUSBSleepPowerSupply", 0x13EC, "kUSBSleepPortCurrentLimit", 0x0834, "kUSBWakePowerSupply", 0x13EC, "kUSBWakePortCurrentLimit", 0x0834 }) } } Scope (\_SB.PCI0.LPCB) { Device (EC) { Name (_HID, "ACID0001") // _HID: Hardware ID Method (_STA, 0, NotSerialized) // _STA: Status { If (_OSI ("Darwin")) { Return (0x0F) } Else { Return (Zero) } } } } } }  
      I saw this other similar post but can't find a working solution in it: https://www.insanelymac.com/forum/topic/341585-hpet/?_fromLogin=1
       
       
    • By MacKonsti
      Hello everyone, I hope you are well and safe. Long time Hackintosh user, didn't post new topics really as most solutions are here, just need some good digging around.
       
      However, there has been no talk about renaming "bare" PCI devices shown in IORegistryExplorer such as e.g. pci8086,1911@8 or pci8086,9def@14,2 to something more meaningful such as ACPI Devices like (SPI1) or (PGMM) or (SHRM) etc. etc.
       
      I have been experimenting a lot with different SSDT ways of making code and injecting the compiled AML via Clover, in preparation for OpenCore, but I cannot succeed for this one.
       
      Why is this needed? For starters, I have two good reasons.
       
      a) My device pci8086,3ed0@0 is MCHC per lspci and despite Clover being able to inject the parameter AddMCHC, I cannot achieve the same result via SSDT injection instead, meaning OpenCore would not do it either (well, for now).
       
      b) Moreover, I discovered by accident from another config.plist in some Github repository, that my device pci8086,9df9@12 that is listed in lspci as Coffee Lake Thermal Controller [8086:9df9] can be set to being compatible with Apple's accepted and combatible device-id of pci8086,9d21 via Clover injection in Devices -> Properties section or via SSDT, but I cannot make it get a human-friendly ACPI name at all so it get to work and load kext com.apple.driver.AppleIntelPCHPMC.
       
      Believe me, I have a few structures of code... Here is my code (compiles 100%) as an example and below, a blocking issue as well.
       
      /* * Intel ACPI Name Space Architecture for NUC8i7BEH2 device * * NOTES: * Assigned PCI device generic (PGMM) and working (PMCR) to undefined devices in IODeviceTree. * Added new (SBUS) sub-system (BUS0) and (DVL0) devices for improved vanilla detection. * Added new (LPCB) sub-system (EC) device for improved Catalina detection. */ DefinitionBlock ("SSDT-OTHER.aml", "SSDT", 2, "Clover", "OTHER", 0x00000000) { External (_SB_.PCI0, DeviceObj) External (_SB_.PCI0.LPCB, DeviceObj) External (_SB_.PCI0.LPCB.H_EC, DeviceObj) External (_SB_.PCI0.SBUS, DeviceObj) Scope (\_SB.PCI0) { // Device (MCHC) // Intel Corporation Host Bridge/DRAM Registers [8086:3ed0] // { // Name (_ADR, 0x00000000) // } // Device (PGMM) // Intel Corporation Core Processor Gaussian Mixture Model [8086:1911] // { // Name (_ADR, 0x00080000) // } Device (PMCR) // Intel Corporation Coffee Lake Thermal Controller [8086:9df9] { Name (_ADR, 0x00120000) } // Device (SRAM) // Intel Corporation Coffee Lake Shared SRAM [8086:9def] // { // Name (_ADR, 0x00142000) // } // Device (SPI1) // Intel Corporation Coffee Lake Serial Bus SPI Controller [8086:9da4] // { // Name (_ADR, 0x001F5000) // } } Scope (\_SB.PCI0.LPCB) // Intel Corporation Coffee Lake LPC Controller [8086:9d84] { Device (EC) { Name (_HID, "ACID0001") Method (_STA, 0, NotSerialized) { If (_OSI ("Darwin")) { Return (0x0F) } Else { Return (Zero) } } } } // Do not rename EC0, H_EC, etc. to EC as these devices are incompatible with macOS // and may break at any time; AppleACPIEC kext must NOT load. If your motherboard // has an existing Embedded Controller of PNP0C09 type, use the code below to disable. Scope (\_SB.PCI0.LPCB.H_EC) { Method (_STA, 0, NotSerialized) { If (_OSI ("Darwin")) { Return (Zero) } Else { Return (0x0F) } } } Scope (\_SB.PCI0.SBUS) // Intel Corporation Coffee Lake SMBus Controller [8086:9da3] { Device (BUS0) { Name (_ADR, Zero) Name (_CID, "smbus") Device (DVL0) { Name (_ADR, 0x57) Name (_CID, "diagsvault") Method (_DSM, 4, NotSerialized) { If (LEqual (Arg2, Zero)) { Return (Buffer (One) {0x57}) } Return (Package (0x02) {"address", 0x57}) } } } } } So if I use External (_SB_.PCI0, DeviceObj) reference on top, then a Scope (\_SB.PCI0) under it, I found out after many tests and reboots that device with 0x00120000 address is somehow allowed to be assigned a "name" in IODeviceTree but not any others! If I enable the other ones, nothing gets injected in this SSDT as a result !
       
      00:00.0 Host bridge [0600]: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers [8086:3ed0] (rev 08) 00:08.0 System peripheral [0880]: Intel Corporation Core Processor Gaussian Mixture Model [8086:1911] 00:12.0 Signal processing controller [1180]: Intel Corporation Coffee Lake Thermal Controller [8086:9df9] (rev 30) 00:14.2 RAM memory [0500]: Intel Corporation Coffee Lake Shared SRAM [8086:9def] (rev 30) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Coffee Lake SPI Controller [8086:9da4] (rev 30) I guess this is likely due to the way my Intel NUC8i7BEH's BIOS and ACPI code is written ?
       
      What's amazing is that if we use Clover's AddMCHC option, in MacIASL I see inside the main DSDT a new code portion added in the _SB.PCI0 very very end at the bottom:
       

       
      But if I uncomment the code for adding Device (MCHC) in my SSDT code above, the device will not get injected ! This is nuts.
       
      @MaLd0n I have been following most of your work for many years and know that you have better knowledge of ACPI code than me, can you possibly advise how we can rename these "naked" PCI devices in IORegistry Explorer to something meaningful like Device (XYZ) ? Is this possible via SSDT code injection?
       
      Anyone else you have in mind, that could help? @Hervé peut-être, maybe you?
       
      The idea is that, except device at 0x00120000 address being accepted (by chance!) and renamed as Device (PMCR) that helps enable the native power-management by injecting later in Clover's configuration a <key>compatible</key> ID, all others including MCHC cannot be assigned a name.
       
      Your help is appreciated... I tried ways to define Devices with root " \ " reference as in External (\_SB_.PCI0, DeviceObj) and Scope (\_SB.PCI0) and without this, for the love of me I cannot understand how to do it.
       
      Moreover, having disassembled all AML files obtained at Clover Boot time, there is no reference to a device with addresses Name (_ADR, 0x00000000), Name (_ADR, 0x00080000), Name (_ADR, 0x00120000) or Name (_ADR, 0x001F5000) anywhere...
       
      Could it be that they do not belong to Scope (\_SB.PCI0) at all ? But Hackintool does report them as being under PciRoot(0x0) ! Could it be differently under some other device instead? ACPIPlane in IORegistryExplorer doesn't show anything
       
      IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/MCHC@0 --> PciRoot(0x0)/Pci(0x0,0x0) IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PMCR@12 --> PciRoot(0x0)/Pci(0x12,0x0) IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/pci8086,9def@14,2 --> PciRoot(0x0)/Pci(0x14,0x2) IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/pci8086,9da4@1F,5 --> PciRoot(0x0)/Pci(0x1F,0x5)  
      Thanks... hope I can resolve this before spending time migrating to OpenCore...!
       
      Here's a screenshot of the "bare" pci8086,xxxx devices without injection of my code at all, except Clover's AddMCHC option.

    • By Cimmerian_Iter
      Hello everyone i have a sony vaio svd1321Z9E intel i7-4500U/4400HD and 8G of ram and using opencore 5.6
      I made a battery patch following rehabman tutorials and i think the patch looks good, but when i try to load it with the kext my pc won't boot to the home menu.

      Like i it does the verbose boot then show me a grey glitchy screen with scattered apple logo.

      Normally it should give this screen then immediately turn into a black apple loading screen (still glitchy) and then return back to normal once it boot into the desktop menu of mac os. (my gpu problem that i never managed to fix but doesn't bother me)

      I would like to know how i could debug and solve this problem. Any help is appreciated.
      Here are my DSDT, config and my battery patch

       
      config.plist
      DSDT.dsl
      SSDT-BATT-3.aml
×