Manually Change in CLI: s-dpi, s-size & s-diag [Solved]

[CharlesV]

Your very welcome and please let us know how that worked - I think it will be just what you want.

[operadude]

Your very welcome and please let us know how that worked - I think it will be just what you want.

[operadude]

@CharlesV Looking over your script, I'm wondering if that will really fix it, since the resolution on the testing rig is, in fact, already set to 1920x1080:

Code: Select all

Screen-1: 0 s-res: 1920x1080 s-dpi: 305 s-size: 160x90mm (6.30x3.54") s-diag: 184mm (7.23")
  Monitor-1: HDMI-0 res: 1920x1080 hz: 60 dpi: 305 size: 160x90mm (6.3x3.54") diag: 184mm (7.23")
    modes: N/A

The problem, I think, is:
s-dpi: 305 (not 96, as it should be)
s-size: 160x90mm (not 509x286 mm, as it should be)
s-diag: 184mm (not 584mm, as it should be)

Will using the xrandr command in the script also correct the s-dpi/size/diag

EDIT/ADDENDUM:

While the above is accurate, I think I see where the confusion may lie. I am posting below the QSI for the display info on my main (Gigabyte) rig, which I am on now. The snippet below IS NOT for the testing rig:

Code: Select all

Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
  Monitor-1: HDMI-A-1 mapped: HDMI-0 model: Samsung built: 2007 res: 1920x1080 hz: 60 dpi: 305
    gamma: 1.2 size: 160x90mm (6.3x3.54") diag: 184mm (7.2") ratio: 16:9 modes: max: 1920x1080
    min: 640x480

Where it says "Monitor-1: HDMIA-A-1 mapped...", it DOES show:

dpi: 305
size: 160x90mm
diag: 184mm

which are the exact dimensions for my problematic testing rig!
So, what gives?

The difference is the line before that, which shows (again, for main, problem-free rig):

Code: Select all

Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")

Whereas, on the testing rig, for "Screen-1...", it shows, the problematic values:

Code: Select all

Screen-1: 0 s-res: 1920x1080 s-dpi: 305 s-size: 160x90mm (6.30x3.54") s-diag: 184mm (7.23")

And, as a reminder: for the testing rig, it shows 1920x1080, but again, "bad" s-dpi, s-size, and s-diag (taken from the first line, "Screen-1..."). So, it looks like the resolution doesn't need to be changed, but those s-dpi, s-size, and s-diag values do need to be changed.

[CharlesV]

Well.. the question is when lightdm is accessing your screen right? Not the res after login.

What I think we need to do is to force the lightdm to use the res you want.

I have never tried to force dpi with xrandr, but the docs say you can with

Code: Select all

xrandr --dpi 96

[operadude]

@CharlesV OK, thanks. I will try that, and see what happens.

I'm assuming that I will do the "force-dpi" command AFTER I am logged on, and that it will persist, right?

Also, what about "s-size" and "s-diag"?

Also, please look at my previous post-- I just added to it, which MIGHT clarify the issue...

[CharlesV]

Well, again the question is what your seeing at lightdm time - NOT when your logged in.

The script, set run at the lightdm.conf means that it runs when lightdm is active (before you log in). Then, upon login your regular settings should take over.

I think I would try res first in the script and then if that doesnt get you where you want to be.. try the dpi @ 96.

[operadude]

@CharlesV I sincerely apologize if I have muddled this whole thing!!!

I am on KDE, and apparently there IS NO "LightDM"

In expanding my repertoire of managing multiple distros, I think I forgot that small detail, and just assumed that there was an issue with "LightDM", especially given the fact that I recently posted on another thread about an issue with "LightDM" (on my MX-Minimal install).

I think I have conflated my Minimal install with my KDE install !!!

Anyway, it may just be semantics, since the issue on my testing rig (KDE) is at the login screen; however, on KDE, I cannot find anything called "LightDM"

So...not sure what exactly has to be modified. I looked in the /etc folder, and there is neither a /lightdm folder, nor a file called "lightdm.conf". Checking with "whereis" gives me nothing:

Code: Select all

$ whereis lightdm.conf
lightdm.conf:
opera-dude@GA-H270-HD3:/
$ 

Can you advise?

And, really, really sorry that I didn't catch this earlier


ADDENDUM:

Well, to console myself, I see that I did, indeed, put this post in the "MX KDE Official Release" Subforum; although, to be honest, I wasn't exactly sure where to put the post-- I thought maybe it should go in MX Help. Anyway...

Checking KDE:

Settings -> System Settings -> Startup & Shutdown -> Login Screen (SDDM)

So, I guess I would need to somehow modify SDDM (not LightDM)...


ADDENDUM:

OK, may have found it-- from the sddm "man" page:

Code: Select all

FILES
       /usr/lib/sddm/sddm.conf.d
              System configuration directory

       /etc/sddm.conf.d
              Local configuration directory

       /etc/sddm.conf
              Local configuration file for compatibility

       /usr/share/sddm/themes
              Where sddm looks for themes

SEE ALSO
       sddm.conf(5)

       The full documentation for sddm is available at https://github.com/sddm/sddm

xrandr seems to work in the terminal, so just add the line to sddm.conf (not lightdm.conf)?

[CharlesV]

Ayup.. I missed that too. yes, sddm is the beast.. I have not played with this, but a quick look around and it is still going to be xrandr .. just in a different file and slightly different method.

I believe it will be add
xrandr -s 1920x1080

to /usr/local/share/sddm/scripts/Xsetup.

I can test this a little later in a VM, headed into a conference call for an hour ish.

[operadude]

Ayup.. I missed that too. yes, sddm is the beast.. I have not played with this, but a quick look around and it is still going to be xrandr .. just in a different file and slightly different method.

I believe it will be add
xrandr -s 1920x1080

to /usr/local/share/sddm/scripts/Xsetup.

I can test this a little later in a VM, headed into a conference call for an hour ish.

Thanks Again

Will have to follow-up tomorrow, since:

"The system is going down for system halt NOW!"

[CharlesV]

ok, so in my VM I found:
- No such file as /usr/local/share/sddm/scripts/Xsetup

- I DID find /usr/share/sddm/scripts/Xsetup

and indeed adding the following did change my login window sizes:
I added to the file ( using Kate) :
xrandr -s 640x480

before the exit 0

So, my entire Xsetup file looks like this

Code: Select all

#!/bin/sh
# Xsetup - run as root before the login dialog appears

xrandr -s 640x480

exit 0

and then logged out and *little tiny login screen*. Played with various res's and it reacted across them, so that does work. and didnt play with anything else. (ie no dpi, or s- or anything. )

I am going to say set yours to something like this and you should be good:

Code: Select all

xrandr -s 1920x1080 

Remember I am in a VM, but here are my graphics setup from QSI which also show "strange" s-dpi settings. no clue what these are about, but I am sure someone can explain that.

Code: Select all

Graphics:
  Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.20.0.0 ports: active: Virtual-1
    empty: Virtual-2, Virtual-3, Virtual-4, Virtual-5, Virtual-6, Virtual-7, Virtual-8
    bus-ID: 00:02.0 chip-ID: 15ad:0405 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
    loaded: vmware unloaded: fbdev,modesetting,vesa dri: swrast gpu: vmwgfx display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1729x980 s-dpi: 47 s-size: 932x528mm (36.69x20.79") s-diag: 1071mm (42.17")
  Monitor-1: Virtual-1 mapped: Virtual1 res: 1729x980 hz: 60 size: N/A modes: max: 1729x980
    min: 640x480
  API: OpenGL v: 4.5 Mesa 24.2.8-1mx23ahs renderer: llvmpipe (LLVM 15.0.6 256 bits)
    direct-render: Yes