Jake Lo

Need to change to this for MBP13,3

AAPL,ig-platform-id = 00001B19 

device-id=1B190000 

and disable these since you have dvmt set in BIOS

framebuffer-stolenmem

framebuffer-fbmem

The Nvidia in the 7510 will not be supported if you're going to be running MacOS. In that end, it has HD530 as the 5510, so no difference as I can tell.

Have you reset NVRam after the changes made to config file?

Then run modgrubshell.efi again to check if the change still updated, if not, change it again.

try switching SMBios to MBP14,3. Make sure to change the SMBIOS in the USBPorts-5510 info file as well.

Wonder if you could test it in Monterey and see if the result is the same. Of course you'll have to switch to the Monterey bootpack but also add the 4k patches.

setup_var 0x432 0x4 

 set it 0x4, not 0x3

No need to install Windows, I have the commands for this system. No worries about the brick warning, I have modded many times without issue. Safe to do it. It'll reset to default if you ever select ' Load Default" in the BIOS.

For Skylake Precision 7510/5510 
DVMT=0x432 //set to 0x4
CFG Lock=0x109 //set to 0x0

 

After booting with modgrubshell.efi

run 

setup_var 0x432 0x4  //this is for DVMT

setup_var ox109 0x0  //this is to unlock CFG Lock

 

The unknown card type is not BT, it's an emulated icon for the USB-C connection. It allows you to hot plug in any USB-C device.

As for Graphics, you might have to set DVMT to 0x4. Check out my guide for DVMT, but instead of using a modded bootx64.efi, use modgrubshell.efi

According to the config, AlpsHID.kext is disabled. Try enabling it. Seems to work for some with similar hardware.

I don't use OCC so I don't know what it does when you click scan/browse, I do all my edits manually with plistedit pro.

Looking at your error, I think it added 2 version of voodooInput.kext, one from Voodoops2controller and one VoodooI2C.kext to your config.plist.

Disable one and it should fix the problem.

Yes, you should disable the BRCM kexts from config and remove from kexts folder as well. No need if you have an Intel BT/Wifi combo

 

Give this a try

 

config-4k-Intel.plist.zip

Post IOReg file

try this, my ventura config file but edited for 4k display. 

config-4k.plist.zip

Basically you need to keep SIP partially disabled with csr-active-config at 03080000

no, you need to leave it in if you want to use MBP11,4 as smbios 

 

Note: Machines running macOS Ventura or systems with non-Metal GPUs cannot enable SIP outright, due to having a patched root volume. Enabling will brick the installation.

This is found in Dortania's guide for OCLP

I just did the same, change csr-active-config to 00000000 and reset NVRam, I'm able to boot but lost graphics acceleration.

I'm still able to boot though. Did you remove the bootarg -no_compat_check?

ok, had to re-run the patch which means having to switch back the setting again.

Looks like you'll have to repatch ever time you reset NVRam

No, don't know where you get that impression. You'll need the alpha version for Ventura Airportitlwm.kext and IntelBluetoothFirmware,kext + IntelBTPatcher + BlueToolFixup for Bluetooth.

As for the 4k display, you'll need to find the right patches for it. Read up on Whatevergreen

make sure ScanPolicy is set to 0 in your config file

Post your EFI folder

what's the display resolution?

try adding to boot arg

-igfxvesa

Post full system's specs including Harddisk brand and model

How are you making the installer?

Did you format it to GUID / Journal Extended?

Is your BIOS set to UEFI / AHCI?

From what I remember, you still need the kext, but leave out the compatibility value. 

Make sure to update all the kexts to the latest

If you're using my EFI files, Hervé suggested to remove the compatible string from the config file or delete this whole line under deviceproperties/Add

PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0) 

Give this a try, replace into USB to test 

HP650G2_OC87.zip

Please post IOReg file using IORegistryExplorer.app v2.1

Post your entire EFI folder + IOReg file using IOregistryExplorer.app

Not sure what previous voodoop2 you're using but as far as I know 4 fingers gesture doesn't work very well with any of the current kext that are available.