Jump to content

DSM2

Members
  • Content Count

    80
  • Joined

  • Last visited


Reputation Activity

  1. Like
    DSM2 got a reaction from Gigamaxx in AMD Radeon Vii in macOS Mojave   
    Time to make things clear...
    As already mentioned by me in the German community @trueadm posted in the thread of @KGP-iMacPro that the VII only runs when the IGPU is on in the bios.
    The whole thing didn't leave me any peace today and I wanted to know it exactly, so I set up a small test setup.
    Since I was missing a CPU cooler, I had to improvise a little, as you can easily see.
    Don't worry all parts live and CPU was kept constant at 53/54 degrees
     
    What turned out now ?
     
    Yes, the card has acceleration when you edit the kext but ONLY!! :
     
    if...
     
    a) the IGPU is active or
     
    b) basically there is a helper card in it
     
    If both are not available then the behavior already determined by @KGP-iMacPro or myself mentioned from day one.
     



  2. Like
    DSM2 got a reaction from KGP-iMacPro in AMD Radeon Vii in macOS Mojave   
    You still forget that your CPU has an iGPU and just because you didnt configure it by yourself it doesnt mean its not initialized by WEG.
     
    How ever... Its 6 o' clock in the morning here in Germany. Bed time!
  3. Like
    DSM2 got a reaction from Gigamaxx in AMD Radeon Vii in macOS Mojave   
    Time to make things clear...
    As already mentioned by me in the German community @trueadm posted in the thread of @KGP-iMacPro that the VII only runs when the IGPU is on in the bios.
    The whole thing didn't leave me any peace today and I wanted to know it exactly, so I set up a small test setup.
    Since I was missing a CPU cooler, I had to improvise a little, as you can easily see.
    Don't worry all parts live and CPU was kept constant at 53/54 degrees
     
    What turned out now ?
     
    Yes, the card has acceleration when you edit the kext but ONLY!! :
     
    if...
     
    a) the IGPU is active or
     
    b) basically there is a helper card in it
     
    If both are not available then the behavior already determined by @KGP-iMacPro or myself mentioned from day one.
     



  4. Like
    DSM2 got a reaction from Gigamaxx in AMD Radeon Vii in macOS Mojave   
    Time to make things clear...
    As already mentioned by me in the German community @trueadm posted in the thread of @KGP-iMacPro that the VII only runs when the IGPU is on in the bios.
    The whole thing didn't leave me any peace today and I wanted to know it exactly, so I set up a small test setup.
    Since I was missing a CPU cooler, I had to improvise a little, as you can easily see.
    Don't worry all parts live and CPU was kept constant at 53/54 degrees
     
    What turned out now ?
     
    Yes, the card has acceleration when you edit the kext but ONLY!! :
     
    if...
     
    a) the IGPU is active or
     
    b) basically there is a helper card in it
     
    If both are not available then the behavior already determined by @KGP-iMacPro or myself mentioned from day one.
     



  5. Like
    DSM2 got a reaction from PMheart in LiluFriend - Fixing Lilu does not function correctly under system locations   
    Thanks! Will test it asap!
    The kext has to be in L/E but I will also try via Kext Injection.
     
    Unfortunatly doesn't fix my issue... hmm...
     
    This is my problem: 
     
    2019-02-03 00:33:29.252097+0100 0x38d0     Default     0x0                  0      0    kernel: (VRS8AudioDriver) AEsiAudioEngine[]::CreateAudioStream() failed to allocate IOBufferMemoryDescriptor
    2019-02-03 00:33:29.252099+0100 0x38d0     Default     0x0                  0      0    kernel: (VRS8AudioDriver) AEsiAudioEngineIn[]::initHardware(), failed to create all streams.
    2019-02-03 00:33:29.252100+0100 0x38d0     Default     0x0                  0      0    kernel: (VRS8AudioDriver) AEsiAudioEngineIn: failed to create analogInputStream!
    2019-02-03 00:33:29.252103+0100 0x38d0     Default     0x0                  0      0    kernel: (IOAudioFamily) - IOAudioEngine[<private>]::start(<private>, <private>)
    2019-02-03 00:33:29.252104+0100 0x38d0     Default     0x0                  0      0    kernel: (IOAudioFamily) - IOAudioEngine[<private>]::start(<private>) returns 0
    2019-02-03 00:33:29.252108+0100 0x38d0     Default     0x0                  0      0    kernel: (IOAudioFamily) - IOAudioDevice[<private>]::activateAudioEngine(<private>, 1) returns 0x<private>
    2019-02-03 00:33:29.252109+0100 0x38d0     Default     0x0                  0      0    kernel: (IOAudioFamily) + IOAudioEngine[<private>]::free()
    2019-02-03 00:33:29.252124+0100 0x38d0     Default     0x0                  0      0    kernel: (IOAudioFamily) - IOAudioEngine[<private>]::free()
    2019-02-03 00:33:29.252124+0100 0x38d0     Default     0x0                  0      0    kernel: (VRS8AudioDriver) AEsiAudioDevice[<private>]::initHardware: failed!
    2019-02-03 00:33:29.256646+0100 0x38d0     Default     0x0                  0      0    kernel: (IOAudioFamily) - IOAudioDevice[<private>]::start(<private>)
     
    Maybe you have an idea what I could try...
  6. Like
    DSM2 reacted to PMheart in LiluFriend - Fixing Lilu does not function correctly under system locations   
    Hi,
     
    Does it have to be installed in /L/E or /S/L/E instead of Clover/kexts/ ? If not, then I'd highly recommend you installing it to Clover and use kext injection for higher priority.
     
    Anyway, if you do need it, here you go:
    <key>OSBundleLibraries</key> <dict> <key>com.apple.kpi.bsd</key> <string>12.0.0</string> <key>com.apple.kpi.iokit</key> <string>12.0.0</string> <key>com.apple.kpi.libkern</key> <string>12.0.0</string> <key>com.apple.kpi.mach</key> <string>12.0.0</string> <key>com.apple.kpi.unsupported</key> <string>12.0.0</string> <key>net.egosys.driver.VRS8Audio</key> <string>1.03</string> </dict>  
  7. Like
    DSM2 got a reaction from PMheart in [pre-release] macOS Mojave 10.14.4   
    Thank you @PMheart 
  8. Like
    DSM2 reacted to PMheart in [pre-release] macOS Mojave 10.14.4   
    Hi!
     
    EDIT:
    I have optimized some algorithm, you may temporarily gather the new binary here (until @Slice uploads a new package on SourceForge).
    As for diff, please see https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/?do=findComment&amp;comment=2661179
     
    PMheart
     
  9. Like
    DSM2 got a reaction from Wackymac in Decompiled original Apple DSDTs   
    Anyone here around with an MacBookPro15,3 Vega 16 or 20 ?
     
    If so a full darwin dump would be awesome!
  10. Like
    DSM2 got a reaction from Wackymac in Decompiled original Apple DSDTs   
    Anyone here around with an MacBookPro15,3 Vega 16 or 20 ?
     
    If so a full darwin dump would be awesome!
  11. Like
    DSM2 got a reaction from Balamut in How to build your own iMac Pro [Successful Build/Extended Guide]   
    @KGP-iMacProThere are two entries and have to be patched both... otherwise it will not work! 
    Like I see he use aswell an WS X299 Sage/10G so it can't be different then on my build  
    Besides from the enp of course...
  12. Like
    DSM2 reacted to KGP-iMacPro in How to build your own iMac Pro [Successful Build/Extended Guide]   
    Sure.. that's what I was saying. Following your recent information, it seems that due to unknown reason the 2 10GB LAN connectors are distributed over two separate enp controllers.
     
    Thus the patch I provided in post 
     
     
    in fact needs to be applied twice for both enps as you did...
     
    If the former enp info provided by @Balamut was correct, his patches should properly read:
     
    sudo ethtool -E enp179s0f0 magic 0x15638086 offset 0x242 value 0x0a sudo ethtool -E enp179s0f0 magic 0x15638086 offset 0x243 value 0x00 sudo ethtool -E enp179s0f1 magic 0x15638086 offset 0x242 value 0x0a sudo ethtool -E enp179s0f1 magic 0x15638086 offset 0x243 value 0x00  
    no idea why the enps are different in his and your case under Linux. 
  13. Like
    DSM2 got a reaction from Balamut in How to build your own iMac Pro [Successful Build/Extended Guide]   
    @Balamut
     
    sudo ethtool -E enp225s0f0 magic 0x15638086 offset 0x242 value 0x0a
    sudo ethtool -E enp225s0f0 magic 0x15638086 offset 0x243 value 0x00
    sudo ethtool -E enp225s0f1 magic 0x15638086 offset 0x242 value 0x0a
    sudo ethtool -E enp225s0f1 magic 0x15638086 offset 0x243 value 0x00
     
    but check if your enp is correct.
    This example is from my WS X299 Sage/10G and this way it works on my build without any problems.
     
     

  14. Like
    DSM2 got a reaction from Balamut in How to build your own iMac Pro [Successful Build/Extended Guide]   
    @Balamut
     
    sudo ethtool -E enp225s0f0 magic 0x15638086 offset 0x242 value 0x0a
    sudo ethtool -E enp225s0f0 magic 0x15638086 offset 0x243 value 0x00
    sudo ethtool -E enp225s0f1 magic 0x15638086 offset 0x242 value 0x0a
    sudo ethtool -E enp225s0f1 magic 0x15638086 offset 0x243 value 0x00
     
    but check if your enp is correct.
    This example is from my WS X299 Sage/10G and this way it works on my build without any problems.
     
     

  15. Like
    DSM2 reacted to Brumbaer in The Beast   
    Overclocked to 5200.
    Board Z390 Phantom Gaming itx/ac
     

  16. Like
    DSM2 got a reaction from Fergarth in [pre-release] macOS Mojave 10.14.1   
    Copy the related kext for your gpu to to extension folder and repair the rights...
  17. Like
    DSM2 reacted to KGP-iMacPro in How to build your own iMac Pro [Successful Build/Extended Guide]   
    SSDT-9.aml, apparently the one and only key for a complete and successful TB Hackintosh implementation...

    In order to demonstrate that I am not yet totally insane with my guesses and ideas, let's demonstrate below that SSDT-9.aml seems to be one of possible cornerstone for reaching full Hackintosh functionality on a iMac Pro Hackintosh system.

    However, due to the missing method "_ini" implementation (port and device initialisation/configuration) in SSDT-9.aml and likely also due to other missing Apple iMac Pro SSDT/DSDT ACPI implementations, my modified SSDT-9.aml yet fails in implementing the basic system essentials for a complete TB Hackintosh configuration and results in plenty of ACPI errors, Name Space Lookup failures and variable or argument errors during boot..
     

     

     

     
    Nevertheless, few essential things are added when inspecting IOREG or Apple's system report..

    While from the TB-kexts used on a real iMacPro only com.apple.driver.AppleThunderboltNHI.kext is active on our Hackintosh systems, SSDT-9.aml so far also loads at least com.apple.iokit.IOThunderboltFamily.kext.
     

     

     
    However, com.apple.driver.AppleThunderboltDPAdapterFamily, com.apple.driver.AppleThunderboltIP.kext, com.apple.driver.AppleThunderboltDPInAdapter, com.apple.driver.AppleThunderboltPCIDownAdapter remain without function due to frequent ACPI errors (Namespace Lookup errors, argument and variable errors, etc.) during boot, which are supposedly due to the yet missing Method "_ini" (port/device implementation/configuration) in my most actual SSDT-9.aml distribution and lacking related ACPI implementations...
     

     
    Most essentially, with my current SSDT-9.aml, also the "RTPC true" entry adds under AppleThuderboltNHIType3..
     

     
    One might also find the one or other interesting IOREG add-ons under in all other TB PCI device implementations...

    Please find linked here my current AML TB implementations for experts only (!!!), i.e. SSDT9.aml, SSDT-DTPG.aml, SSDT-GNVS.aml, SSDT-GG/SG-Methods.aml, SSDT-OSDW.aml and SSDT-SBUS.aml,  I also link once more @TheOffcialGypsy 's most recent iMac Pro dump, where you find the original SSDT-9.aml (BTW.. SSDT-10.aml might be noteworthy in addition)  besides the iMac Pro DSDT and other iMacPro SSDT implementations... linked as well the IOREG save of the original iMac Pro...

    @TheOfficialGypsy, any more recent dump under 10.13.6 or 10.14 PB4 available?

    I guess, it rapidly might become evident that the complexity of the problem apparently exceeds the capacities and knowledge of one single person... What about active collaborators, here online or maybe also within some small local "insitu" and "hands-on" workgroup in the Berlin/Germany area?
     
    @apfelnico, @nmano, or who ever is interested and is able to join this endeavour?

    I really don't know if there is any valid chance for a successful SSDT-9.aml Hackintosh TB implementation.. However, we should give it a try.. 

    Enjoy and have fun,
     
    KGP
     
    P.S: SSDT-9.aml of the iMac Pro dump is broken and impossible to be compiled..

    One needs to start with the SSDT-9.dsl and add "\_SB.PC01.BR1A.UPSB.AMPE ()" under:
     
    Scope (\_GPE) { Method (_L32, 0, NotSerialized) // _Lxx: Level-Triggered GPE { If (LNot (OSDW ())) { If (LEqual (\_SB.PC01.BR1A.POC0, One)) { Return (Zero) } Sleep (0x0190) If (LEqual (\_SB.PC01.BR1A.WTLT (), One)) { \_SB.PC01.BR1A.ICMS () } Else { } If (\_SB.PC01.BR1A.UPMB) { Store (Zero, \_SB.PC01.BR1A.UPMB) Sleep (One) } Else { } \_SB.PC01.BR1A.CMPE () } ElseIf (LEqual (\_SB.GGII (0x01030012), One)) { \_SB.SGII (0x01030012, Zero) } Else { \_SB.SGII (0x01030012, One) } \_SB.PC01.BR1A.UPSB.AMPE () } } It took me weeks and months to discover and fix these stupid errors..
     
    For the sake of completeness and for simplicity, I also attach a minimal SSDT-9 hot plug injector AML, i.e. SSDT-9-minimal-hotplug-injector.aml, which pretty does everything for achieving a functional TB and TB XHC USB hot plug workaround on THB-C removed Hackintosh systems..
     
     
  18. Like
    DSM2 got a reaction from xtddd in [pre-release] macOS Mojave   
    Anyone else lost his Lan Ports? 
    With the newest beta I don't have any lan devices...
    Anyone any idea ? 
     
    imac.zip
  19. Like
    DSM2 reacted to "Sniki" in [pre-release] macOS Mojave   
    macOS Mojave "MinStolenSize" / DVMT-prealloc Patches
     
    @Sherlocks @PMheart i quoted you since im kinda new here and i noticed that you are one of the most active people on this forum (caught my attention).
     
    I noticed that during the Beta updates, the "MinStolenSize" patches are changing from what we previously had / on previous betas, after examining the binary files of the 3 respective platforms: KabyLake, SkyLake, Broadwell i noticed that the:
    on AppleIntelKBLGraphicsFramebuffer.kext
    Find: 764648FF 05
    Replace: EB4648FF 05
    values should be enough as it's only in one place in the binary file with a HexFiend search, same for Skylake & Broadwell:
    Find: 764048FF 05
    Replace: EB404FF 05
    on 2 of the binary files of the kexts if you try to search such result.
    so lets take KabyLake as example from my previous post:
     
    Kabylake: Name: com.apple.driver.AppleIntelKBLGraphicsFramebuffer Find: 764648FF 05225508 Replace: EB4648FF 05225508 from the code above on the binary file: 764648FF 05E25108 the code highlighted with red (which was present on previous betas of Mojave but kept changing during newer betas), is unnecessary as after verifying that the code: 764648FF 05 is present only once on KabyLake framebuffer binary file and we can replace it with: EB4648FF 05 this way the patch should be update proof "based on the fact that this part of code didn't change across betas.
     
    So in short words the code after "05" is/was unncessary and the supposedly Update Proof Patches for:
    macOS Mojave "MinStolenSize" / DVMT-prealloc Patches
     
     
    KabyLake:
    Comment: Disable minStolenSize less or equal fStolenMemorySize assertion, 10.14 Credits (Sniki)
    Name: com.apple.driver.AppleIntelKBLGraphicsFramebuffer
    Find: 764648FF 05
    Replace: EB4648FF 05
     
     
    SkyLake:
    Comment: Disable minStolenSize less or equal fStolenMemorySize assertion, 10.14 Credits (Sniki)
    Name: com.apple.driver.AppleIntelSKLGraphicsFramebuffer
    Find: 764048FF 05
    Replace: EB4048FF 05
     
     
    Broadwell:
    Comment: Disable minStolenSize less or equal fStolenMemorySize assertion, 10.14 Credits (Sniki)
    Name: com.apple.driver.AppleIntelBDWGraphicsFramebuffer
    Find: 764048FF 05
    Replace: EB4048FF 05
  20. Like
    DSM2 reacted to al6042 in WhatEverGreen Support Topic   
    I use a KextsToPatch entry to get HDMI/DP-Audio working on my Vega56:
    Name:  com.apple.driver.AppleHDAController Find:  021030AA Replace: 0210F8AA Comment: Vega56 HDMI-Audio Just find the Ven-/Dev-ID for your HDMI-Audio-Device and byte-flip the numbers
  21. Like
    DSM2 reacted to maleorderbride in ThunderBolt Drivers   
    This is a mini-guide to get Thunderbolt hotswap working. My SSDT is for an ASRock TB3 (JHL6540) card in my X299 motherboard, but I know this also works with the Gigabyte X99 Designare's built-in TB3 port.
    If you need a more basic overview of SSDTs then I suggest Shiloh's SSDT GPU Injection thread at the place that shall not be named.
     
    Based on the TheRacerMaster's work, and remote.syst3m's idea to change the value of "PCIHotplugCapable", I have TB3 hotswap working. Thunderbolt does not show as loaded in System Profiler, and this is undoubtedly a bit of a hack, but it seems to work and it is quite easy to implement.
     
    TheRacer Master's github work seems to be based on importing MacBookPro14,1 ACPI information. You can find some raw Darwin Dumps here from him that contain DSDTs, SSDTs, and IOreg.
     
    Below is the seemingly relevant bit, pulled from TheRacerMaster's github, with only the "PCIHotplugCapable" value changed to enabled and a few values modified to fit my computer.
    Device (DSB0) { Name (_ADR, Zero) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (LNot (Arg2)) { Return (Buffer (One) { 0x03 }) } Return (Package (0x02) { "PCIHotplugCapable", One }) } I implemented this as an SSDT, but perhaps one could simply inject the single property via Clover arbitrary, or just the DSB0 device with that one property.
     
    1. What you need:
    IOregistryExplorer (or IOJones)
    MaciASL (use Rehabman's patchmatic)
    Thunderbolt working (just without hotswap)
     
    2. Identify the TB device address
    2.1 Open IOreg and find your thunderbolt device(s) by typing in "thunderbolt" in the search bar. 
     
    2.2. Take note of the address (PCI0.RP05 for me).
     
    2.3. Now clear the thunderbolt search and switch to IOACPIPlane view on the top right of IOreg. Find that same address. You should see a few other entires under it, and make note of whatever does not begin with H (for X99), and any values for X299. In this case, mine are PXSX and SLT5. We are going to prevent these from loading by setting their STA value to Zero so that our devices load instead.
     
    3. Modify stock SSDT
    3.1 Download the attached base SSDT and replace any instances of PCI0.RP05 with your actual address. If you have multiple thunderbolt controllers then copy and modify accordingly.
     
    3.2. Replace PXSX and SLT5 with your value(s) from IOACPIPlane view. You might only have one value, in which case you can delete the extra line from the stock SSDT.
     
    That should be it! Reboot and open IOreg again. Look to see if you now have PCIHotplugCapable set to "True" on the right-hand side. If so, then it should be working.
     
    4. BIOS Settings
    4.1. If you have an ASUS X299 board then you should enabled ASPM and GPIO ForcePwr in addition to the normal BIOS settings (Legacy Security, Cache Line-in 128, any slot selection). If you don't do this then you will not see a USB 3.1 bus for the TB3 card unless you keep a USB 3.1 device plugged in to the TB3 port on startup.
     
    5. Inject USB ports (not required for hotswap but clears up errors in boot log)
    I also hardcoded the two USB 3.1 ports on my card to clear up some complaints during verbose startup. This was pulled from one of PikerAlpha's blog posts. I don't think it matters which device you inject this into (DSB2,3,4), but I chose DSB2 based upon the address on my particular card (0x0002000) locatable in IOreg. If I had had 0x0003000 then I would have done DSB3, etc. 
     
    5.1. If you already have an XHC2 device, then name it XHC3, 4, or whatever is appropriate. If you only have one TB3 port, then you only need HS01 and SSP1.
    Device (DSB2) { Name (_ADR, 0x00020000) // _ADR: Address Device (XHC2) { Name (_ADR, Zero) // _ADR: Address Device (RHUB) { Name (_ADR, Zero) // _ADR: Address Device (SSP1) { Name (_ADR, One) // _ADR: Address Name (_UPC, Package (0x04) // _UPC: USB Port Capabilities { 0xFF, 0x09, Zero, Zero }) Name (_PLD, Package (0x01) // _PLD: Physical Location of Device { Buffer (0x10) { /* 0000 */ 0x81, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0008 */ 0x31, 0x1C, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 } }) Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Return (Package (0x02) { "UsbCPortNumber", One }) } } Device (SSP2) { Name (_ADR, 0x02) // _ADR: Address Name (_UPC, Package (0x04) // _UPC: USB Port Capabilities { 0xFF, 0x09, Zero, Zero }) Name (_PLD, Package (0x01) // _PLD: Physical Location of Device { Buffer (0x10) { /* 0000 */ 0x81, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0008 */ 0x31, 0x1C, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 } }) Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Return (Package (0x02) { "UsbCPortNumber", 0x02 }) } } Device (HS01) { Name (_ADR, 0x03) // _ADR: Address Name (_UPC, Package (0x04) // _UPC: USB Port Capabilities { 0xFF, 0x09, Zero, Zero }) Name (_PLD, Package (0x01) // _PLD: Physical Location of Device { Buffer (0x10) { /* 0000 */ 0x81, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0008 */ 0x31, 0x1C, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 } }) } Device (HS02) { Name (_ADR, 0x04) // _ADR: Address Name (_UPC, Package (0x04) // _UPC: USB Port Capabilities { 0xFF, 0x09, Zero, Zero }) Name (_PLD, Package (0x01) // _PLD: Physical Location of Device { Buffer (0x10) { /* 0000 */ 0x81, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0008 */ 0x31, 0x1C, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 } }) } } } }  
    SSDT-TB3.aml.zip
  22. Like
  23. Like
    DSM2 reacted to MaLd0n in [Guide] Sierra / High Sierra / Mojave on mobos Serie 100 / 200 / 300 / SkyLake / KabyLake / CoffeeLake DSDT   
    the patch pegp to gfx0 is bad
    check if work
    CLOVER iMac.zip
    if have a problem just drop edited dsdt
  24. Like
    DSM2 reacted to al6042 in [pre-release] macOS Mojave   
    @DSM2 These are Clover KextsToPatch entries which should work on the Framebuffer kexts of the specific CPU Family. 
     
    AppleIntelBDWGraphicsFramebuffer = Broadwell
    AppleIntelSKLGraphicsFramebuffer = Skylake
    AppleIntelKBLGraphicsFramebuffer = Kabylake
     
    Since the DVMT-issue mostly occurs on Laptops, which can't change the DVMT-value in BIOS, these patches might not be used on desktops.
    An exception might be those fancy packaged machines from Lenovo, Asus or whatever, with minimised BIOS settings capabilities...
  25. Like
    DSM2 reacted to Ricky1994 in [pre-release] macOS Mojave   
    you can see this .
    AppleIntelBDWGraphicsFramebuffer (5th hd5500) Find: 764048FF 05122B06 Repl: EB4048FF 05122B06 AppleIntelSKLGraphicsFramebuffer (6th hd520 hd530) Find: 764048FF 0561E907 Repl: EB4048FF 0561E907 AppleIntelKBLGraphicsFramebuffer (7th 8th hd620 630 uhd620 uhd630) Find: 764648FF 05025208 Repl: EB4648FF 05025208  
    you can see my preview post
    AppleIntelBDWGraphicsFramebuffer (5th hd5500) Find: 764048FF 05122B06 Repl: EB4048FF 05122B06 AppleIntelSKLGraphicsFramebuffer (6th hd520 hd530) Find: 764048FF 0561E907 Repl: EB4048FF 0561E907 AppleIntelKBLGraphicsFramebuffer (7th 8th hd620 630 uhd620 uhd630) Find: 764648FF 05025208 Repl: EB4648FF 05025208  
×