Actually I don't think this is a Trinity problem, because reverting to lightdm shows no change, but I post this in hope someone can give me a clue:
I have setup a machine based on an Intel based SBC (UP board with a "cherry trail" processor. It runs openSUSE Leap and Trinity. I initially had lots of screen corruption but this I solved by setting the graphics to "xua".
My problem is this: while I have the screen resolution setup to 1920x1080 (and trinity desktop looks OK for this resolution), the monitor (which is accessed from HDMI through an HDMI to VGA converter because I use a KVM that needs VGA connectors) was initially "seen" as 1024x768.
And the applications seem to retain that resolution. I could make things better in kmail (which is the main application for this machine) by reducing the font size. The other applications still look "too big".
So I get the feeling that the lower resolution was saved somewhere...
Is there a place where I can tell them to use 1920x768?
Have good day,
Thierry
Am Mittwoch, 8. Februar 2017 schrieb Thierry de Coulon:
Actually I don't think this is a Trinity problem, because reverting to lightdm shows no change, but I post this in hope someone can give me a clue:
I have setup a machine based on an Intel based SBC (UP board with a "cherry trail" processor. It runs openSUSE Leap and Trinity. I initially had lots of screen corruption but this I solved by setting the graphics to "xua".
My problem is this: while I have the screen resolution setup to 1920x1080 (and trinity desktop looks OK for this resolution), the monitor (which is accessed from HDMI through an HDMI to VGA converter because I use a KVM that needs VGA connectors) was initially "seen" as 1024x768.
And the applications seem to retain that resolution. I could make things better in kmail (which is the main application for this machine) by reducing the font size. The other applications still look "too big".
So I get the feeling that the lower resolution was saved somewhere...
Is there a place where I can tell them to use 1920x768?
This will most likely not solve your problem for GTK3 applications, but you can try to fix the screens DPI:
kcontrol / Apperreance / Fonts : Force DPI ... 96 DPI
For GNOME/GTK please look here: https://wiki.archlinux.org/index.php/HiDPI
Nik
On Wednesday 08 February 2017 12.43:43 Dr. Nikolaus Klepp wrote:
This will most likely not solve your problem for GTK3 applications, but you can try to fix the screens DPI:
kcontrol / Apperreance / Fonts : Force DPI ... 96 DPI
For GNOME/GTK please look here: https://wiki.archlinux.org/index.php/HiDPI
Nik
Thanks Nik, it did solve the problem, at least for the apps I use on that machine (kmail, Vivaldi, Yast). I had never noticed (nor needed) that setting, now I know where to look.
Thierry
Thierry de Coulon wrote:
My problem is this: while I have the screen resolution setup to 1920x1080 (and trinity desktop looks OK for this resolution), the monitor (which is accessed from HDMI through an HDMI to VGA converter because I use a KVM that needs VGA connectors) was initially "seen" as 1024x768.
It is interesting to know what is the output of xrandr
I have/had similar issues with my notebook(s) and external monitor. Natively eDP1 supports 1366x768, while monitor does 1920x1080.
So switching on and of the one and the other messed up from time to time the modesettings and I end up with unusable resolution. The external would refuse to accept 1920x1080. It improved recently with later 4.9 kernel and I did not test extensively. One option was to configure monitors in xorg.conf with their mod lines. I did this on the older notebook I however use now xrandr --scale as X tends to pick up the lowest common and it can not support different resolutions or whatever. So I put the bigger one to 1920x1080 and scale eDP1., which gives acceptable output.
I have read of similar issues with KVM.
regards
On Wednesday 08 February 2017 21.56:32 deloptes wrote:
Thierry de Coulon wrote:
My problem is this: while I have the screen resolution setup to 1920x1080 (and trinity desktop looks OK for this resolution), the monitor (which is accessed from HDMI through an HDMI to VGA converter because I use a KVM that needs VGA connectors) was initially "seen" as 1024x768.
It is interesting to know what is the output of xrandr
I have/had similar issues with my notebook(s) and external monitor. Natively eDP1 supports 1366x768, while monitor does 1920x1080.
So switching on and of the one and the other messed up from time to time the modesettings and I end up with unusable resolution. The external would refuse to accept 1920x1080. It improved recently with later 4.9 kernel and I did not test extensively. One option was to configure monitors in xorg.conf with their mod lines. I did this on the older notebook I however use now xrandr --scale as X tends to pick up the lowest common and it can not support different resolutions or whatever. So I put the bigger one to 1920x1080 and scale eDP1., which gives acceptable output.
I have read of similar issues with KVM.
regards
That's what I get:
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 DP1 disconnected (normal left inverted right x axis y axis) HDMI1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 256mm x 192mm 1024x768 60.00 + 1920x1080 60.00* 59.94 1280x1024 85.02 60.02 1440x900 74.98 59.90 1280x960 60.00 1360x768 60.02 1280x800 59.91 1280x720 119.99 60.00 59.94 720x480 60.00 59.94
To me it seems the chipset by itself can do a lot of resolutions. I am new to HDMI (I actually don't use it anwhere as I have no monitor with such a connector). So I can't test what would happen if I had a direct connection to the monitor.
I could imagine that the chain HDMI - HDMI to VGA (cheap chinese thing, by the way) - KVM switch - monitor is too much for a system that desperately tries to identify the monitor by itself. In the old time I would have been asked what my screen was...
Thierry
-
deloptes -
Dr. Nikolaus Klepp -
Thierry de Coulon -
Thierry de Coulon