Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
TV hdmi overscan issues
140 views
Skip to first unread message
Henning Follmann
Aug 30, 2021, 6:20:05 PM8/30/21
to
Hello,
I recently upgraded a NUC (which is my kodi media server) to bullseye.
I always had an issue with the overscan of my TV monitor.
The overscan cannot be disabled on the monitor (it is an 16 year old
sharp). And I tried to compensate via xrandr --transform, which I never
was able to figure out. But you can set in kodi the display to compensate for
this. You still can do this, however kodi(bullseye) forgets these settings,
which means you have to configure this after every new start of kodi.
I think this might be a bug. But now I want o try again to solve the overscan
issue on system level (most likely again with xrandr)
Now this sytem runs with wayland and for any combination of the --transform
matrix I currently get an error:
X Error of failed request: BadValue (Integer parameter out of range for operation)
the initail try was just
xrandr --output XWAYLAND3 --mode 1280x720 --transform 1.05,0,-10,0,1,0,0,0,1
to shift the x axis.
Is this a wayland issue?
-H
--
Henning Follmann | hfol...@itcfollmann.com
I recently upgraded a NUC (which is my kodi media server) to bullseye.
I always had an issue with the overscan of my TV monitor.
The overscan cannot be disabled on the monitor (it is an 16 year old
sharp). And I tried to compensate via xrandr --transform, which I never
was able to figure out. But you can set in kodi the display to compensate for
this. You still can do this, however kodi(bullseye) forgets these settings,
which means you have to configure this after every new start of kodi.
I think this might be a bug. But now I want o try again to solve the overscan
issue on system level (most likely again with xrandr)
Now this sytem runs with wayland and for any combination of the --transform
matrix I currently get an error:
X Error of failed request: BadValue (Integer parameter out of range for operation)
the initail try was just
xrandr --output XWAYLAND3 --mode 1280x720 --transform 1.05,0,-10,0,1,0,0,0,1
to shift the x axis.
Is this a wayland issue?
-H
--
Henning Follmann | hfol...@itcfollmann.com
Felix Miata
Aug 30, 2021, 7:20:04 PM8/30/21
to
Henning Follmann composed on 2021-08-30 18:09 (UTC-0400):...
On a 39" Proscan I needed this to eliminate overscan:
xrandr --output HDMI-1 --set underscan on --set "underscan vborder" 20 --set "underscan hborder" 35
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
> xrandr --output XWAYLAND3 --mode 1280x720 --transform 1.05,0,-10,0,1,0,0,0,1
> to shift the x axis.
...
> to shift the x axis.
On a 39" Proscan I needed this to eliminate overscan:
xrandr --output HDMI-1 --set underscan on --set "underscan vborder" 20 --set "underscan hborder" 35
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
Henning Follmann
Aug 31, 2021, 9:00:04 AM8/31/21
to
On Mon, Aug 30, 2021 at 07:00:02PM -0400, Felix Miata wrote:
> Henning Follmann composed on 2021-08-30 18:09 (UTC-0400):...
> > xrandr --output XWAYLAND3 --mode 1280x720 --transform 1.05,0,-10,0,1,0,0,0,1
> > to shift the x axis.
> ...
> On a 39" Proscan I needed this to eliminate overscan:
> xrandr --output HDMI-1 --set underscan on --set "underscan vborder" 20 --set "underscan hborder" 35
> --
Hello,
> Henning Follmann composed on 2021-08-30 18:09 (UTC-0400):...
> > xrandr --output XWAYLAND3 --mode 1280x720 --transform 1.05,0,-10,0,1,0,0,0,1
> > to shift the x axis.
> ...
> On a 39" Proscan I needed this to eliminate overscan:
> xrandr --output HDMI-1 --set underscan on --set "underscan vborder" 20 --set "underscan hborder" 35
> --
thanks for the help.
However that does not work either. It fails with "font or color unknown", which I think ia
misleading. I suspect that wayland does not allow me to set any properties with xrandr.
David Wright
Aug 31, 2021, 10:10:04 AM8/31/21
to
On Tue 31 Aug 2021 at 08:56:37 (-0400), Henning Follmann wrote:
> On Mon, Aug 30, 2021 at 07:00:02PM -0400, Felix Miata wrote:
> > Henning Follmann composed on 2021-08-30 18:09 (UTC-0400):...
> > > xrandr --output XWAYLAND3 --mode 1280x720 --transform 1.05,0,-10,0,1,0,0,0,1
> > > to shift the x axis.
> On Mon, Aug 30, 2021 at 07:00:02PM -0400, Felix Miata wrote:
> > Henning Follmann composed on 2021-08-30 18:09 (UTC-0400):...
> > > xrandr --output XWAYLAND3 --mode 1280x720 --transform 1.05,0,-10,0,1,0,0,0,1
> > > to shift the x axis.
> > > Is this a wayland issue?
Not so much an issue as Wayland's raison d'être, to push out X.
> > ...
> > On a 39" Proscan I needed this to eliminate overscan:
> > xrandr --output HDMI-1 --set underscan on --set "underscan vborder" 20 --set "underscan hborder" 35
> However that does not work either. It fails with "font or color unknown", which I think ia
> misleading. I suspect that wayland does not allow me to set any properties with xrandr.
wayland-… or gnome-…, rather than x…, to distinguish the two worlds.
Cheers,
David.
0 new messages