Update: This method in this post requires trial and error if you have lot of displays. Konstantin Gredeskoul has created an automated bash script and shared it on GitHub. Check his comment.
Or directly go to GitHub for instructions: Changing OSX Underscan
I recently purchased an Asus external monitor. The first thing I noticed on plugging it to my MacBook was that there was a blank space at each of the edges. This wasted quite a bit of screen estate and also made everything blurry. This can generally happen due to wrong underscan/overscan settings.
On testing monitor with other laptops, I found that it was working fine. So it was something with my Mac. macOS has a slider to adjust overscan in system preferences. However, it only appears for TVs. So it was not appearing for me.
It took me two hours but I finally fixed it with help of command line and Stack Overflow.
The Stack Overflow question: “How to reload .com.apple.iokit.graphics underscan without restarting?”. This was unrelated to my problem but helped me to find the file where configuration is stored.
In case you encounter same issue, here’s a step by step guide to save you a couple of hours:
Disclaimer: You may damage your system with a wrong command, so proceed with caution. I am just sharing what worked for me and am not responsible for any loss or harm caused by anything in this post. It worked for me on a MacBook Pro (Retina, 13-inch, Early 2015) running macOS High Sierra (10.13.2), it may or may not work for you.
Fixing Overscan/Underscan
- Open terminal.
- You want to open
/var/db/.com.apple.iokit.graphicsfile. To do that, enter following command in terminal:
open -a TextEdit /var/db/.com.apple.iokit.graphics - TextEdit will open with the file. You’ll notice that the file has following structure:
- Starting with line 5, every
keytag is a separate display and followingdictis list of preferences for it. - Note: You may need to do a bit of trial and error to find the correct display. In my case, I only use a limited number of displays, so I reset the settings for every display, restarted and it was fixed.
- Find the lines that say
<key>pscn</key>. This is the preference that controls underscan/overscan. - Next line after every
pscnkey will look like this:<integer>10000</integer>(line 34 above). - 10000 means that there is no underscan. Value less than 10000 means that display will be underscanned, larger value means it is overscanned.
- For values less than 10000, change them back to 10000.
- Save the file, you may need to enter your admin password.
- Restart.
The issue should be fixed. I hope it will save some time for you. In meantime, if you find any shortcuts, do let me know via comments.
Ishan, thank you so much for posting this! It was a lifesaver for me, as I am forced to work on a very crappy Samsung monitor for a week that does not have any buttons, besides the power button LOL!
I wanted to add one additional hint on how to determine which monitor is the the one that needs to be changed. Below commands are all run from the terminal:
? grep pscn /var/db/.com.apple.iokit.graphics | wc -l
58
This tells me that I had 58 monitor entries! How to tell which one is the crappy monitor I use?
Here is what I did to figure this out:
1) Make a backup of the current file:
? cp /var/db/.com.apple.iokit.graphics /tmp/.com.apple.iokit.graphics.backup
2) With the “troubled” monitor connected, open DIsplay Preferences, and change it’s settings: for example, I changed it’s resolution from 1080p to 1080i. It doesn’t matter what you change, as long as you change something and specifically for that monitor.
3) Run the “diff” command to see what had changed in that file after you made the changes:
? diff /var/db/.com.apple.iokit.graphics /tmp/.com.apple.iokit.graphics.backup
195c195
AAAAAAA….
(I shortened the lines for readability). The only part we care about is shown on the very first line: 195. This is the line number where the change happened after you modified your monitor settings. In my case, the value for `pscn` was three lines above 195, i.e. at line 192.
Now it’s time to follow your instructions, open the file in an editor, then scroll to line 192, then go up a few lines to find the `pscn` and edit it.
Don’t forget to exit display settings before changing it, and then restart.
Finally, I’ve tried to automate this process in a helpful script, documented here:
https://github.com/pioneerworks/lib-bash#changing-osx-underscan-for-old-monitors
Thanks again!
Wow. That script is amazing. Thank you for sharing this. I have added a note to top of the post about this.
You are welcome! I just extracted it so that it’s standalone and requires no dependencies:
https://gist.github.com/kigster/7ce9e879883cf4899fa0de94a57dfaf0
Thanks again!
Hi,
I had the same problem and was able to fix it with the help of this post, So thank you !
But I wish to put my 2 cents to this problem so I tried a few things and I maybe have a quicker solution…
If you just delete the .com.apple.iokit.graphics file then restart Mac OS will create a new default one and voilà problem solved !
Hi Pascal,
Thank you for sharing. In my case, I had tried deleting that file but that didn’t work for me.
i typed “open -a TextEdit .com.apple.iokit.graphics” into terminal and it said the file does not exist.
I tried searching for it on finder/spotlight trying several different keywords and phrases. I couldn’t find the file.
could someone help?
Hi,
The file is in /var/db, so either you need to use
open -a TextEdit /var/db/.com.apple.iokit.graphicsor usecd /var/db/and then run the command I mentioned in step 2.Thanks.
Thanks Ishan, I tried a lot of troubleshooting and nothing worked, this was a big relief!