Surface pro 6 Catalina

[esalinas04]

I am currently using Mojave on my SP6 with Intel i5-8250u and Intel UHD 620 graphics. When trying to upgrade to Catalina using the installer from Apple I am able to run the install, reboot to Clover and run the install from there. When it reboots to finish the 2nd part of the install it hangs. The verbose indicates that the iGPU framebuffer has an error. I have already tried the id 0x12345678 to no gain. Using clover 5119, updated all kexts installed to latest version. Mojave boots fine using that. Also tried to create a bootable USB installer and running it from there but it stops at the same spot. Any suggestions? I have attached my EFI used for this. Thanks.

 

[littlegreen]

I'm by no means an expert, however, I notice you are declaring your UHD 620 incorrectly.

You are using both -disableigfxfirmware and are declaring a PciRoot device. I'm not on a mac at the moment so can't check if it matches mine (I've a same CPU and GPU config) - but one would not play well with the other.

Short term suggestion: Try to inject the intel graphics via a FakeID - if memory servers it is 0x59168086 - but do google it and remove this section:

<key>Properties</key>
        <dict>
            <key>PciRoot(0)/Pci(0x2,0)</key>
            <dict>
                <key>AAPL,ig-platform-id</key>
                <data>AAAWWQ==</data>
                <key>device-id</key>
                <data>FlkAAA==</data>
                <key>enable-hdmi20</key>
                <data>AQAAAA==</data>
                <key>framebuffer-con1-enable</key>
                <data>AQAAAA==</data>
                <key>framebuffer-con1-type</key>
                <data>AAgAAA==</data>
                <key>framebuffer-con2-enable</key>
                <data>AQAAAA==</data>
                <key>framebuffer-con2-index</key>
                <data>/////w==</data>
                <key>framebuffer-patch-enable</key>
                <data>AQAAAA==</data>
                <key>framebuffer-portcount</key>
                <data>AgAAAA==</data>
                <key>framebuffer-unifiedmem</key>
                <data>AAAAgA==</data>
        </dict>

 

[esalinas04]

I'm by no means an expert, however, I notice you are declaring your UHD 620 incorrectly.

You are using both -disableigfxfirmware and are declaring a PciRoot device. I'm not on a mac at the moment so can't check if it matches mine (I've a same CPU and GPU config) - but one would not play well with the other.

Short term suggestion: Try to inject the intel graphics via a FakeID - if memory servers it is 0x59168086 - but do google it and remove this section:

<key>Properties</key>
        <dict>
            <key>PciRoot(0)/Pci(0x2,0)</key>
            <dict>
                <key>AAPL,ig-platform-id</key>
                <data>AAAWWQ==</data>
                <key>device-id</key>
                <data>FlkAAA==</data>
                <key>enable-hdmi20</key>
                <data>AQAAAA==</data>
                <key>framebuffer-con1-enable</key>
                <data>AQAAAA==</data>
                <key>framebuffer-con1-type</key>
                <data>AAgAAA==</data>
                <key>framebuffer-con2-enable</key>
                <data>AQAAAA==</data>
                <key>framebuffer-con2-index</key>
                <data>/////w==</data>
                <key>framebuffer-patch-enable</key>
                <data>AQAAAA==</data>
                <key>framebuffer-portcount</key>
                <data>AgAAAA==</data>
                <key>framebuffer-unifiedmem</key>
                <data>AAAAgA==</data>
        </dict>

thanks. I actually did clean it up after studying the WEGkext faq. I got it to boot BUT there are no gfx acceleration. The About MAC screen says 19mb vs the 1536mb it said on Mojave. I was reading that WEG does not support gfx acceleration yet on Catalina with the Kaby lake GPU. I’m trying a clean install now with my updated .plist files that I cleaned up.

 

[littlegreen]

You have a weird thing in "KextsToPatch" - where you are patching AppleIntel KabyLake graphics buffer - and you should not need to, as it is natively supported and OK.

Also, MacBookPro15,2 is a better fit for the CPU, I believe.

Try the attached config.plist and see if it works?