[solved] Cursor lags at startup

[demimontalto]

You can use either. But you have to enter the data correctly. You entered the wrong data (you should have used copy/paste).
The < > characters are used by Xcode when entering binary/hex data. You would not see/use them in CC.

I probably messed it up trying to edit after cc converted the "<>"
Now it works, thank you!

 

[RehabMan]

I probably messed it up trying to edit after cc converted the "<>"
Now it works, thank you!

Marked solved.

 

[demimontalto]

Marked solved.

Sorry to re-up this, but I noticed that my HDMI doesn't work anymore after this, what to do?
I just plug it in and nothing happens.. no freeze no reboot, no display recognized, nothing..

 

[RehabMan]

Sorry to re-up this, but I noticed that my HDMI doesn't work anymore after this, what to do?

No "Problem Reporting" files attached.

 

[demimontalto]

No "Problem Reporting" files attached.

I did two ioreg, one with hdmi plugged in and one not.
Clover folder is the same as prevoius posts, but with framebuffer patched correctly

 

[RehabMan]

I did two ioreg, one with hdmi plugged in and one not.
Clover folder is the same as prevoius posts, but with framebuffer patched correctly

Need all "Problem Reporting" files... I cannot guess regarding EFI/Clover content.

 

[demimontalto]

Need all "Problem Reporting" files... I cannot guess regarding EFI/Clover content.

Here they are

 

[RehabMan]

Here they are

Change the patch marked "0x0a260006 9MB cursor bytes (vbo), 2 ports only", to this:

Comment: 0x0a260006 9MB cursor bytes (vbo)
Find: <0600260a 01030303 00000002 00003001 00006000>
Replace: <0600260a 01030303 00000002 00003001 00009000>

 

[demimontalto]

Change the patch marked "0x0a260006 9MB cursor bytes (vbo), 2 ports only", to this:

Comment: 0x0a260006 9MB cursor bytes (vbo)
Find: <0600260a 01030303 00000002 00003001 00006000>
Replace: <0600260a 01030303 00000002 00003001 00009000>

Looks like it works, what was the issue?
Isn't it the same patch as before?

 

[RehabMan]

Looks like it works, what was the issue?
Isn't it the same patch as before?

It is not the same patch. Look carefully at what you had before.