Razer Blade 2016 OS X 10.11.5

[hobyho]

1080P or 4K screen?

I have the 4K one, well QHD+

 

[uar]

I have the 4K one, well QHD+

You have to patch IOKit.

 

[freejack]

Hey @freejack or @uar new to this as I just got a Razer Blade, care to share your Clover files setup to get me started to experiment as well? Thanks!

I have the FHD model so I'm not sure what needs to be done to get the QHD display working. Maybe @uar can help if he's got one.

 

[freejack]

Works now, Thanks!

It is detected as a mouse rather then a trackpad. Have you got 2-finger scrolling working?

I'm speaking to one of the voodooI2C devs to get the synaptics interface working. We're using the generic one which is just a mouse emulator.

 

[uar]

I have the FHD model so I'm not sure what needs to be done to get the QHD display working. Maybe @uar can help if he's got one.

Have the FHD model too, but still I know how to get QHD display working. You have to set DVMT-prealloc and patch IOKit...
Read RehabMan´s FAQ:

Q. Are QHD+/UHD laptop displays supported?

Requirements for QHD+/UHD displays:
- patched IOKit framework (to remove pixel clock limitations)
- DVMT-prealloc set to 96MB or 128MB in BIOS
- Haswell: ig-platform-id 0xa2e0008
- Haswell: framebuffer configuration for 0xa2e0008 patched to match DVMT-prealloc value (Broadwell determines BIOS size dynamically)
- "normal" requirements for Haswell/Broadwell systems

Refer to this post as an example: http://www.tonymacx86.com/yosemite-...novo-yoga-2-pro-hd4400-qhd-qe-ci-working.html

For patching IOKit, clear instructions for using the-darkvoid's XPS9530.sh script are in the Y50 guide: http://www.tonymacx86.com/el-capita...-y50-uhd-1080p-using-clover-uefi-10-11-a.html

IMPORTANT!: Contrary to many of the guides you will read, Windows is NOT a valid way to determine what DVMT-prealloc is set to. There is no correlation, especially with Windows 10.

I'm speaking to one of the voodooI2C devs to get the synaptics interface working. We're using the generic one which is just a mouse emulator.

Great, let me know if something happens...

 

[hobyho]

Have the FHD model too, but still I know how to get QHD display working. You have to set DVMT-prealloc and patch IOKit...
Read RehabMan´s FAQ:

Great, let me know if something happens...

Cool thanks will look into that, can you or @freejack provide your current clover files as attachments as a starting point for me?

 

[RehabMan]

This will happen if you did not rename XDSM back to _DSM in the TPD0 section:

Method (_DSM, 4, Serialized) // _DSM: Device-Specific Method
{
If (LEqual (Arg0, HIDG))
{
Return (HIDD (Arg0, Arg1, Arg2, Arg3, HID2))
}

If (LEqual (Arg0, TP7G))
{
Return (TP7D (Arg0, Arg1, Arg2, Arg3, SBFB, SBFG))
}

Return (Buffer (One)
{
0x00
})
}

The kext should probably try to evaluate both _DSM and XDSM...

 

[freejack]

Cool thanks will look into that, can you or @freejack provide your current clover files as attachments as a starting point for me?

Relevant files attached. Good luck.

 

[uar]

The kext should probably try to evaluate both _DSM and XDSM...

Tried that, it didn't work. In my case I had change the device @freejack mentioned and remove your hotpatch in config.plist in ACPI section to boot VoodooI2C or KP...

 

[RehabMan]

Tried that, it didn't work. In my case I had change the device @freejack mentioned and remove your hotpatch in config.plist in ACPI section to boot VoodooI2C or KP...

You must have made the change incorrectly in the kext.

Note: The kext shouldn't crash in the case of a non-existent or incorrectly coded _DSM anyway...