v2.5 released

A new update of is available for download. Have a look at the commits to see what I changed. Here is one big improvement. Enter:


Gone with the error. Next up. Colorised output with contextual information. Something I previewed here.
Ok. This is actually a screenshot made with v2.2 and thus the output is slightly different. Thing is. Most people will find this improvement handy. Hey. Even I do.

What’s next

If you think that this is it… think again! I am going to change things even further. And big time. I tell you this. When I am done with the update to v3.0 then patching your frame buffer(s) will be much easier. Key point: Forget editors 🙂


You know the drill. All possible bugs (so called ‘issues’) should be filed at:

Please do not use my blog for this.

Thank you!

13 thoughts on “ v2.5 released

    • Thanks. The output, in plain English, should help you to understand the meaning of the data, and what to change, but you still need to know what to do with it. That is one of the problems with patching in general. Please wait for my next update. That is when things will be much easier. Trust me. We are about to enter a new erra in patching 😉

  1. I have had a chance to look yet as my decking just fell to pieces, but I’m wondering if the output if the new reg dumper is useful in being able to *automatically* determine what needs to be patched in framebuffer kext? Perhaps that’s where you are going with this…

  2. Nice pike, however it shows, port 5 till 7 as DP, while I only have one HDMI and one DVI(just as yours.

    0064d80: 0300 220d 0003 0303 0000 0002 0000 3001 (32 MB BIOS-allocated memory, 19 MB framebuffer)
    0064d90: 0000 0000 0000 0060 9914 0000 9914 0000 (0 MB cursor bytes, 1536 MB VRAM, backlight frequency 5273 Hz, 5273 Max backlight)
    0064da0: 0000 0000 0000 0000 0105 0900 0004 0000 (port 5, DisplayPort connector)
    0064db0: 8700 0000 0204 0a00 0004 0000 8700 0000 (port 6, DisplayPort connector)
    0064dc0: 0306 0800 0004 0000 1100 0000 ff00 0000 (port 7, DisplayPort connector / port 255 unused)
    0064dd0: 0100 0000 4000 0000 0200 0000 0101 0000 (VGA connector)
    0064de0: 0400 0000 0000 0000 0000 0000 0000 0000


    • Thanks, but a script can only show information from the selected frame buffer from the kext. Not that of what your hardware supports. That is (almost) impossible because Apple uses the same data to (re)configure the Intel GPU registers.

  3. Pingback: Preview of v3.0 | Pike's Universum

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s