Adding/Using HiDPI custom resolutions

[hectorox]

If you use download.sh and install_downloads.sh as per ProBook/EliteBook guide, you should have no issue with matching Lilu.kext+IntelGraphicsFixup.kext.



Seems like HiDPI is not enabled.
You should get some HiDPI resolutions enabled just by enabling the HiDPI options.
Focus on that first (without a display override).

Did you reboot after doing the 'sudo defaults write'/etc?

I am still using an old Lilu.kext version for getting my audio to work (thats probably why an error message appeared)

I tried that also (without display override). No HiDPI options at all :/

Yes, I did a reboot after executing the sudo defaults commands. Executing the second command gives me that:

2017-12-13 01:28:41.965 defaults[503:5422]
Domain (/Library/Preferences/com.apple.windowserver) not found.
Defaults have not been changed.

 

[RehabMan]

I am still using an old Lilu.kext version for getting my audio to work (thats probably why an error message appeared)

Lilu.kext has nothing to do with audio with the ProBook/EliteBook guide. It uses patched AppleHDA (via hotpatch), not AppleALC.kext.

I tried that also (without display override). No HiDPI options at all :/

Did you try with a fresh install?

Yes, I did a reboot after executing the sudo defaults commands. Executing the second command gives me that:

2017-12-13 01:28:41.965 defaults[503:5422]
Domain (/Library/Preferences/com.apple.windowserver) not found.
Defaults have not been changed.

I got the same thing, but with HiDPI options after reboot...

 

[hectorox]

Lilu.kext has nothing to do with audio with the ProBook/EliteBook guide. It uses patched AppleHDA (via hotpatch), not AppleALC.kext.



Did you try with a fresh install?



I got the same thing, but with HiDPI options after reboot...

@lilu.kext
I know but your hotpatch was always problematic on my side, thats why I switched to AppleALC. Never had any problem with AppleALC.

A fresh install would be really the last option, as I already have a lot of stuff installed on my machine

maybe it is something with the internal monitor? I will try to get EDID information and add them to display override. Maybe this will help?

 

[RehabMan]

@lilu.kext
I know but your hotpatch was always problematic on my side, thats why I switched to AppleALC. Never had any problem with AppleALC.

A fresh install would be really the last option, as I already have a lot of stuff installed on my machine

maybe it is something with the internal monitor? I will try to get EDID information and add them to display override. Maybe this will help?

Repeat: Did you try with a fresh install?
(note you can do so to a separate partition)

 

[hectorox]

Repeat: Did you try with a fresh install?
(note you can do so to a separate partition)

thats what I found on a different forum:

It stopped working for me too from the 10.8.3 through 10.9.* up to 10.10.2. They added new mechanisms to check the resolution overrides. They can't exceed, what the monitor reports as his maximum.

One can invest time and test following:
- Extract EDID
- edit EDID so the max. supported resolution is higher than what your monitor supports
- override the display resolution like so in this thread
- (optional) maybe it is necessary to use https://code.google....xel-clock-patch

Can you explain to me how to add custom EDID to your repository (I think it needs to be added in SSDT-IGPU.aml somehow?)?
As injecting it through clover or/and displayoverrides does not override the EDID :/

 

[hectorox]

You have a very basic problem to start with...
You should see some HiDPI resolutions just by enabling the HiDPI option.
So... you need to overcome that hurdle before you can expect any extra resolutions added in a display override.

I am considering to install my osx to the newest version now. Actually I am on 10.12.3 and as I see most users are on newer version. I have no idea when I will have time to do it, but I will come back and inform you guys.

If someone has any other ideas, please let me know.

 

[LordHung]

you need to install RDM app. Open it and HiDPI options should be there.

 

[RehabMan]

I am considering to install my osx to the newest version now. Actually I am on 10.12.3 and as I see most users are on newer version.

Yes.
No sense in dealing with old versions of macOS.

 

[ibizalove]

Thanks for this tutorial! I was using SwitchResX and deleted it in favor of this manual option. Unfortunately I'm not able to achieve my target resolution of 1600x900 HiDPI as my display begins to jump and distort at this resolution only. The same thing happened with SwitchResX. At any other resolution the display is stable but when using 3200x1800 or 1600x900 HiDPI the display jumps and distorts and is unusable. Do you have any idea why this happens? My display is AU Optronics B156HW01 V.5 Full HD 1080p Glossy LED LCD Screen. It works perfectly with no flaws at native 1920x1080 but I get headaches because of the tiny resolution. Normal 1600x900 works as well but it's too blurry to be usable. 1600x900 HiDPI is the perfect solution if I can get it stabilized.

 

[RehabMan]

Thanks for this tutorial! I was using SwitchResX and deleted it in favor of this manual option. Unfortunately I'm not able to achieve my target resolution of 1600x900 HiDPI as my display begins to jump and distort at this resolution only. The same thing happened with SwitchResX. At any other resolution the display is stable but when using 3200x1800 or 1600x900 HiDPI the display jumps and distorts and is unusable. Do you have any idea why this happens? My display is AU Optronics B156HW01 V.5 Full HD 1080p Glossy LED LCD Screen. It works perfectly with no flaws at native 1920x1080 but I get headaches because of the tiny resolution. Normal 1600x900 works as well but it's too blurry to be usable. 1600x900 HiDPI is the perfect solution if I can get it stabilized.

No "Problem Reporting" files attached.
Read FAQ, "Problem Reporting" again. Carefully. Attach all requested files/output.
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/
Use the tool mentioned in the FAQ, that way it is less likely you'll omit something.