[PLUG] Using xrandr to address overscan on TV

[tomas.kuchta.lists at gmail.com]

Disclaimer: I cannot remember how I solved this - long time ago - I
hope my comentary might give you some ideas.

I had similar problem in the past - caused by TV lying about its screen
resolution. It was one of the cheap but expensive + early Visio TVs.
There was sticker on the back advertising the "greatest and truest HD
TV ever". Needless to say the panel was not even HD but some obscure
1013-ish to 698-ish and of course it advertised itself as 1280x720 and
it was 6b panel with pretty bad dithering too.

I have a feeling that I was able to override the reported resolution in
X device configs somehow. I remember upgrading to newer distro about 2+
years ago - I could not get it working anymore. My wife solved it for
me by getting cheap, but this time not so expensive + late full HD +
not-Visio TV with real 1920x1080 resolution reported. That was the end
of that struggle for me.

Hope it helps you somehow,
Tomas

On Thu, 2019-03-28 at 16:38 -0700, Dick Steffens wrote:
> The system is a Lenovo M58P with an nVidia GeForce GT 610 using its
> HDMI 
> port. The OS is Xbuntu 18.04.
> 
> I'm trying to deal with the issue of the top and sides of the
> desktop 
> are outside of the TV frame. I tried the instructions at:
> 
> https://ubuntuforums.org/showthread.php?t=2380987
> 
> and have the same error as experienced by the poster.
> 
> -------------------------------------------------------------------
> ------------
> $ xrandr
> HDMI-0 connected (followed by  a bunch of stuff)
> 
> $sudo xrandr --output HDMI-0 --set underscan on --set "underscan 
> vborder" 30 --set "underscan hborder" 30
> X Error of failed request: BadName (named color or font does not
> exist)
> Major opcode of failed request: 140 (RANDR)
> Minor opcode of failed request: 11 (RRQueryOutputProperty)
> Serial number of failed request: 31
> Current serial number in output stream: 31
> -------------------------------------------------------------------
> ------------
> 
> Additional searches don't seem to address the problem.
> 
> Ideas?
> 
> Thanks.
>