Contribute
Register

[solved] Intel HD 4600 HDMI - screen fuzzy when plugged in or off

Status
Not open for further replies.
RehabMan said:
Must use a valid ig-platform-id.
You could patch 0x0a260006 for 64mb.
Click to expand...

Could you elaborate on how to do that?

RehabMan said:
You applied "USB _PRW 0x6d..." but your native files use 0x0d. It is a big mistake.
Suggestion: keep better notes on the patches you apply. And pay attention to the "Preview" window when applying patches to insure the changes the patches are making are sensible.
Click to expand...

I thought as long as when compiled did not give me an error, its still okay to use that patched DSDT haha. Because out of those warnings, almost all of them are 'method X may not return a value', so I just ignored it (?).
 
alv456 said:
Could you elaborate on how to do that?
Click to expand...

Refer to my guide plists for examples.

I thought as long as when compiled did not give me an error, its still okay to use that patched DSDT haha. Because out of those warnings, almost all of them are 'method X may not return a value', so I just ignored it (?).
Click to expand...

Just because code compiles does not make it correct.
 
RehabMan said:
Yes. Those are the plists linked from my guide.
Click to expand...

In your config.plist, there is only 96MB and 128MB patch, which data should I change to make it into 64MB?
 
alv456 said:
In your config.plist, there is only 96MB and 128MB patch, which data should I change to make it into 64MB?
Click to expand...

Look at the data in the patch carefully.

Hint: 64mb is half of 128mb.
 
RehabMan said:
Look at the data in the patch carefully.

Hint: 64mb is half of 128mb.
Click to expand...

How about the find value? still same?

What about the ig-platform-id?
 
alv456 said:
How about the find value? still same?
Click to expand...

Find is native data, therefore only dependent on data in the vanilla kext (so may change depending on version of macOS/OS X).
Look in a hex editor and you'll see.

What about the ig-platform-id?
Click to expand...

Well, it would remain the same... you're patching the data associated with a particular ig-platform-id.
To use the patched data that you're changing, you must stick with the same ig-platform-id.
Because switching to a different id would mean the kext is not using the data you changed.
 
RehabMan said:
Find is native data, therefore only dependent on data in the vanilla kext (so may change depending on version of macOS/OS X).
Look in a hex editor and you'll see.



Well, it would remain the same... you're patching the data associated with a particular ig-platform-id.
To use the patched data that you're changing, you must stick with the same ig-platform-id.
Because switching to a different id would mean the kext is not using the data you changed.
Click to expand...

So, that means I only need to change the last digit in Find to 2 and Replace to 4, since current DVMT is 32mb right?
 
alv456 said:
So, that means I only need to change the last digit in Find to 2 and Replace to 4, since current DVMT is 32mb right?
Click to expand...

You should not be changing Find. As I already wrote, Find operates on native data in the vanilla kext.

And you said your DVMT-prealloc was 64mb. Did you now change it to 32mb? If so, no patch needed as 0xa260006 assumes 32mb by default.

Keep in mind cursor bytes and framebuffer size must fit within the BIOS size (DVMT-prealloc).
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top