Page 1 of 1
Manually Change in CLI: s-dpi, s-size & s-diag
Posted: Tue Jul 01, 2025 9:14 am
by operadude
Coming to you from my new testing rig (dedicated, stand-alone machine for testing stuff)
All is good, except for screwy s-dpi, s-size & s-diag for this machine. Need to change them!
This monitor (1920x1080, 60Hz) has 3 HDMI-in ports. I use one of them for this testing rig, another one for my daily driver (Gigabyte machine-- running now), and a streamer.
Everything was perfectly fine before installing Nvidia drivers, which I tried once before, but rolled-back. Tried again today, and got the same results, but I managed to correct some problems. Still, I see that the s-dpi, s-size & s-diag are set INCORRECTLY for this testing rig.
Question:
How can I manually and permanently change them?
Here's what they should be (currently on my Gigabyte machine):
s-dpi: 96
s-size: 509x286 mm
s-diag: 584mm
Here's what they are on this testing rig:
s-dpi: 305
s-size: 160x90 mm
s-diag: 184mm
Last, but not least, here's the QSI from the testing rig:
Code: Select all
Snapshot created on: 20250617_1407
System:
Kernel: 6.1.0-37-amd64 [6.1.140-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-37-amd64 root=UUID=<filter> ro quiet splash
Desktop: KDE Plasma v: 5.27.5 info: plank wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23.6_x64
Libretto October 13 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Desktop System: ASUS product: All Series v: N/A serial: <superuser required>
Mobo: ASUSTeK model: H81M-K v: Rev X.0x serial: <superuser required> UEFI: American Megatrends
v: 1101 date: 03/09/2015
CPU:
Info: model: Intel Core i5-4690 bits: 64 type: MCP arch: Haswell gen: core 4 level: v3
note: check built: 2013-15 process: Intel 22nm family: 6 model-id: 0x3C (60) stepping: 3
microcode: 0x28
Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB
L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB desc: 1x6 MiB
Speed (MHz): avg: 825 high: 900 min/max: 800/3900 scaling: driver: intel_cpufreq
governor: ondemand cores: 1: 800 2: 900 3: 800 4: 800 bogomips: 27935
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: indirect_target_selection status: Not affected
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled
Type: mds mitigation: Clear CPU buffers; SMT disabled
Type: meltdown mitigation: PTI
Type: mmio_stale_data status: Unknown: No mitigations
Type: reg_file_data_sampling status: Not affected
Type: retbleed status: Not affected
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW; STIBP: disabled; RSB
filling; PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA GK107 [GeForce GT 740] vendor: ASUSTeK driver: nvidia v: 470.256.02 non-free:
series: 470.xx+ status: legacy-active (EOL~2023/24) arch: Kepler code: GKxxx process: TSMC 28nm
built: 2012-18 pcie: gen: 2 speed: 5 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:0fc8
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: nvidia unloaded: fbdev,modesetting,nouveau,vesa alternate: nv gpu: nvidia display-ID: :0
screens: 1
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
API: OpenGL v: 4.6.0 NVIDIA 470.256.02 renderer: NVIDIA GeForce GT 740/PCIe/SSE2
direct-render: Yes
Audio:
Device-1: Intel 8 Series/C220 Series High Definition Audio vendor: ASUSTeK 8
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8c20 class-ID: 0403
Device-2: NVIDIA GK107 HDMI Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 2
speed: 5 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:0e1b class-ID: 0403
API: ALSA v: k6.1.0-37-amd64 status: kernel-api tools: alsamixer,amixer
Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK H81M-C
driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 03:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: docker0 state: down mac: <filter>
Drives:
Local Storage: total: 1.02 TiB used: 74.09 GiB (7.1%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 model: SATA SSD size: 111.79 GiB block-size: physical: 512 B
logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 61.3 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST1000DM003-1ER162 size: 931.51 GiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
rev: CC45 scheme: GPT
Partition:
ID-1: / raw-size: 111.54 GiB size: 109.23 GiB (97.93%) used: 29.23 GiB (26.8%) fs: ext4
dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
dev: /dev/sda1 maj-min: 8:1
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 3 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
System Temperatures: cpu: 37.0 C mobo: N/A gpu: nvidia temp: 40 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 20%
Repos:
Packages: pm: dpkg pkgs: 3124 libs: 1595 tools: apt,apt-get,aptitude,nala pm: rpm pkgs: 0
pm: flatpak pkgs: 0
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb https://mxrepo.com/mx/repo/ bookworm main non-free
2: deb https://mxrepo.com/mx/repo/ bookworm ahs
No active apt repos in: /etc/apt/sources.list.d/skype-stable.list
Info:
Processes: 199 Uptime: 15m wakeups: 1 Memory: 7.69 GiB used: 1.5 GiB (19.5%) Init: SysVinit
v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
Just to give you an idea of what's going on, here's a pic:
And, one more:
EDIT/ADDENDUM:
This might be the best pic: when I select the "Whisker Menu" (not sure if that's what it's called in KDE), it takes come a HUGE portion of the screen. Other windows are also way-too-big!!! Anyway, a picture is worth a thousand words, so, here you go:
Re: Manually Change in CLI: s-dpi, s-size & s-diag
Posted: Tue Jul 01, 2025 10:01 am
by operadude
Well, that was weird
So, I had turned-off "compositing", which seemed to solve some of the window-sizes problem; although, some of the windows remained huge, especially icons on the desktop, items in the taskbar, some menu windows, etc.
Then, I thought, for proper diagnosis, I should really re-enable the "compositing" feature, so as not to contaminate the diagnosis process. After Reboot, here are what the pics look like:
So, looks like everything is OK. BUT....
Strangely, the QSI still shows the wrong dimensions for s-dpi, s-size & s-diag
Code: Select all
Graphics:
Device-1: NVIDIA GK107 [GeForce GT 740] vendor: ASUSTeK driver: nvidia v: 470.256.02 non-free:
series: 470.xx+ status: legacy-active (EOL~2023/24) arch: Kepler code: GKxxx process: TSMC 28nm
built: 2012-18 pcie: gen: 2 speed: 5 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:0fc8
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: nvidia unloaded: fbdev,modesetting,nouveau,vesa alternate: nv gpu: nvidia display-ID: :0
screens: 1
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
API: OpenGL v: 4.6.0 NVIDIA 470.256.02 renderer: NVIDIA GeForce GT 740/PCIe/SSE2
direct-render: Yes
At this point, I will leave it alone, unless someone with a higher pay-grade than me says I should change it
Please let me know your thoughts
EDIT/ADDENDUM:
I'm wondering if the post in the link below, and code I snipped from there, might have something to do with what happened to my system:
viewtopic.php?p=793301#p793301
I did not use the code below, but I did turn-off compositing (xrandr?) and re-start:
Code: Select all
xrandr --output HDMI-0 --off ; sleep 1 ; xrandr --output HDMI-0 --primary --mode 1920x1080 --rate 60
So, maybe my disabling and then re-enabling Compositing had the same effect as the post in the link above describes?
Also, let me know if you think I should try to manually change the s-dpi, s-size, & s-diag, which still seem to have the WRONG dimensions, as shown in the QSI
Re: Manually Change in CLI: s-dpi, s-size & s-diag
Posted: Tue Jul 01, 2025 12:13 pm
by operadude
Follow-Up:
Upon "cold" boot, the LightDM login screen is HUGE-- cannot see the complete fields for Username and Password. Not a problem, since I know my password by heart!
BUT, after logon, everything looks OK.
Maybe I SHOULD try to change those parameters?
Or, "If it aint (mostly) broke, don't fix it" ?
Re: Manually Change in CLI: s-dpi, s-size & s-diag
Posted: Tue Jul 01, 2025 2:01 pm
by CharlesV
Were your settings manually set this way or did it install with the nvidia drivers this way?
Re: Manually Change in CLI: s-dpi, s-size & s-diag
Posted: Tue Jul 01, 2025 2:29 pm
by operadude
CharlesV wrote: Tue Jul 01, 2025 2:01 pm
Were your settings manually set this way or did it install with the nvidia drivers this way?
I did nothing, except install the Nvidia drivers.
I'm not sure what the settings were before installing the Nvidia drivers.
Reminds me of something I think you recommended on another post:
During Backup, get a copy of your QSI
Obviously, I didn't do that!
ADDENDUM:
Thanks CharlesV for the reply.
I will check back tomorrow..."Shutting down for system halt NOW"
Re: Manually Change in CLI: s-dpi, s-size & s-diag
Posted: Tue Jul 01, 2025 3:05 pm
by CharlesV
This sounds like maybe rolling back to the opensource driver and seeing what that does might give the needed clue?
That xrandr command looks like it is defining basically a turn off and turn on - waking up the monitor and telling the video to wake up essentially. I dont believe that is an issue.
Re: Manually Change in CLI: s-dpi, s-size & s-diag
Posted: Wed Jul 02, 2025 2:40 am
by operadude
CharlesV wrote: Tue Jul 01, 2025 3:05 pm
This sounds like maybe rolling back to the opensource driver and seeing what that does might give the needed clue?
That xrandr command looks like it is defining basically a turn off and turn on - waking up the monitor and telling the video to wake up essentially. I dont believe that is an issue.
Yeah, I wasn't sure about the xrandr command, so I DID NOT run it!
Got some rest, and realized that I DO HAVE the old QSI-- via MX-Snapshot
, which I took after configuring the sytem; I also made a Live USB, via MX-LUM
I will 'Boot from my LUE' (
), i.e., boot from the Live USB Environment, and check the QSI from the original state, i.e., before the Nvidia drivers were installed. Will report back with that info.
As it stands, I really do want to keep the Nvidia drivers, as I will be using this testing rig for running AI models (e.g. Ollama) locally; and so, I want the Nvidia/Cuda drivers for that. Also, as of now, the only glitch in the system is the LightDM login screen, which is a bit annoying (HUGE size), but a minor inconvenience.
What is irking me is the fact that the system seems to still think that my monitor has these dimensions: 160x90mm (s-size) & 184mm (s-diag), with 305 dpi. However, it now seems that those dimensions are being used ONLY with LightDM. After logging-on, everything reverts to normal dimensions, and is visually identical to my main rig (on the other HDMI port). Again, I can live with the weird LightDM settings...
Anyway, is there a safe way (without breaking dependencies or the system as a whole), via CLI, to manually change those dimensions: s-dpi, s-size, & s-diag ???
Even if I don't end-up changing them, I would like to know how to do that, via CLI
Thanks again for the reply
Exclamatorily, Yours (I use way too many exclamation points, right?)
,
Re: Manually Change in CLI: s-dpi, s-size & s-diag
Posted: Wed Jul 02, 2025 3:47 am
by operadude
operadude wrote: Tue Jul 01, 2025 2:29 pm
CharlesV wrote: Tue Jul 01, 2025 2:01 pm
Were your settings manually set this way or did it install with the nvidia drivers this way?
I did nothing, except install the Nvidia drivers.
I'm not sure what the settings were before installing the Nvidia drivers.
Reminds me of something I think you recommended on another post:
During Backup, get a copy of your QSI
Obviously, I didn't do that!
ADDENDUM:
Thanks CharlesV for the reply.
I will check back tomorrow..."Shutting down for system halt NOW"
CORRECTION :
Sorry about the misquote above ("Shutting down for system halt NOW")
The correct quote is:
"The system is going down for system halt NOW!"
Re: Manually Change in CLI: s-dpi, s-size & s-diag
Posted: Wed Jul 02, 2025 10:55 am
by CharlesV
Glad you got some sleep - you look all fired up :-)
So, xrandr can tell you what your hardware is (or .. what it thinks it is), and then you can set params to set the system using it.
The way I have seen it used in this case before is to have lightdm fire off a script that sets the screen res the way you want it.
Here is an example of setting a res for a DVI output in a script.
SetVideoRes.sh
Code: Select all
#!/bin/sh
xrandr --output DVI-0 --primary --mode 1920x1080
You would have to change to your correct video output, and then save this to your script folder (or desktop etc). Then make it executable.
Run it and make sure that all is good. ( maybe change the res some if your regular mode is 1920x1080, just to verify all good.)
If all good, then put the script in your /usr/share folder (so it doesnt get blown out).
Then in the /etclightdm folder edit the lightdm.conf file and add the following line at the end of the file
Code: Select all
display-setup-script=/usr/share/SetVideoRes.sh
Next logout or reboot you should have the video res size that your after / specified, at login.
Caveat - I am only about have way through my first cup of coffee ... so double check everything ;-p
Re: Manually Change in CLI: s-dpi, s-size & s-diag
Posted: Wed Jul 02, 2025 12:09 pm
by operadude
@CharlesV 
That looks AWESOME
It looks like it will have to wait until tomorrow to test that all out...
I will let you know how it goes.
I really appreciate the feedback and the detailed/thorough response!
Re: Manually Change in CLI: s-dpi, s-size & s-diag
Posted: Wed Jul 02, 2025 12:13 pm
by CharlesV
Your very welcome and please let us know how that worked - I think it will be just what you want.
Re: Manually Change in CLI: s-dpi, s-size & s-diag
Posted: Wed Jul 02, 2025 12:43 pm
by operadude
CharlesV wrote: Wed Jul 02, 2025 12:13 pm
Your very welcome and please let us know how that worked - I think it will be just what you want.
Re: Manually Change in CLI: s-dpi, s-size & s-diag
Posted: Wed Jul 02, 2025 1:00 pm
by 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.
Re: Manually Change in CLI: s-dpi, s-size & s-diag
Posted: Wed Jul 02, 2025 1:34 pm
by 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
Re: Manually Change in CLI: s-dpi, s-size & s-diag
Posted: Wed Jul 02, 2025 1:37 pm
by 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...
Re: Manually Change in CLI: s-dpi, s-size & s-diag
Posted: Wed Jul 02, 2025 1:43 pm
by 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.
Re: Manually Change in CLI: s-dpi, s-size & s-diag
Posted: Wed Jul 02, 2025 2:08 pm
by 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)?
Re: Manually Change in CLI: s-dpi, s-size & s-diag
Posted: Wed Jul 02, 2025 2:28 pm
by 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.
Re: Manually Change in CLI: s-dpi, s-size & s-diag
Posted: Wed Jul 02, 2025 2:32 pm
by operadude
CharlesV wrote: Wed Jul 02, 2025 2:28 pm
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!"
Re: Manually Change in CLI: s-dpi, s-size & s-diag
Posted: Wed Jul 02, 2025 6:09 pm
by 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:
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
Re: Manually Change in CLI: s-dpi, s-size & s-diag
Posted: Thu Jul 03, 2025 2:59 am
by operadude
CharlesV wrote: Wed Jul 02, 2025 6:09 pm
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:
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
Well, that looks like a quick and easy fix
Will try later, and get back to you...
Re: Manually Change in CLI: s-dpi, s-size & s-diag
Posted: Thu Jul 03, 2025 7:40 am
by operadude
@CharlesV Unfortunately, this did nothing:
Add this line (before "exit 0"):
Unfortunately, upon reboot, same huge login screen...
CORRECTION:
I had written earlier that the Login screen on the testing rig is HUGE, and that I can't see the whole field for the password.
Now, I do see the whole field (not sure what changed somewhere along the way), AND, I have enough room to put my whole password.
EDIT: [Emendations in Text boxes, like this one]:
The only inconvenience is that the other options that appear below the password box are
too [very] large, and [almost, but not quite] overlap one another. I can still choose "X11"/"Wayland",
but some of the other options are overlapping, and looks like I wont be able to choose them, or maybe very carefully! I think the last option ("Other") is also occluded., and the other options are very large, but they ARE accessible. The only one that is a bit tricky, but still doable, is the "X-Session V. Wayland" option, which is kinda sandwiched between the other options.
Whatever...
At this point, changing the login screen (SDDM) is NOT a deal-breaker, and I am willing to live with the current state.
Having said that, I would, for the Geek-Factor (Upping My Linux Skills), like to successfully tweak this sucker, so that I can have the Computer Bend To My Will (Too Cringe?
)
EDIT/ADDENDUM:
Just tried various combinations of editing the "Xsetup" file, with:
Code: Select all
xrandr --primary --fb 1920x1080 --dpi 96
None of those worked; neither singly, nor all together.
So,
@CharlesV , let me know, "Before Midnight Tonight
"
, if you have any further thoughts or recommendations.
Re: Manually Change in CLI: s-dpi, s-size & s-diag
Posted: Thu Jul 03, 2025 10:20 am
by CharlesV
hmmm... please verify that you do NOT have this file - And if you DO, lets see what the contents of that are.
Code: Select all
/usr/local/share/sddm/scripts/Xsetup
Re: Manually Change in CLI: s-dpi, s-size & s-diag
Posted: Thu Jul 03, 2025 10:42 am
by operadude
CharlesV wrote: Thu Jul 03, 2025 10:20 am
hmmm... please verify that you do NOT have this file - And if you DO, lets see what the contents of that are.
Code: Select all
/usr/local/share/sddm/scripts/Xsetup
Nope!
I have this folder:
But NO "sddm" folder !
I also tried adding the same file, but renamed as ".xsession", in my home folder, since the "man" page for "xsession.options" says this:
Code: Select all
allow-user-xsession
If users have an executable file called .xsession in their home directories, it
can be used as the startup program for the X session (see Xsession(5)). If the
file is present but not executable, it may still be used, but is assumed to be a
Bourne shell script, and executed with sh(1).
I tried with permissions set to both "root" and "opera-dude" (separately), but this also had NO EFFECT.
Grasping at straws...
The only other thing I have noticed, is that when the machine boots (before login screen), there are a few ACPI errors flashed to the screen (something about "BIOS bug"), and then very quickly, those same errors appear MUCH LARGER. So, yeah, not sure what is causing that...
Re: Manually Change in CLI: s-dpi, s-size & s-diag
Posted: Thu Jul 03, 2025 10:58 am
by CharlesV
Perfect. (I was thinking maybe that local was overriding the other location.)
This is starting to sound like your wayland scaling is broken - and I bet this is that wayland / nvidia issue I read about.
That Xsetup is to manipulate X11 around and since it has no effect ... Let me see if I can find a wayland equivalent. ( or since that machine has nvidia, maybe we can push back to X11 ? Let me see what I can find. )
Re: Manually Change in CLI: s-dpi, s-size & s-diag
Posted: Thu Jul 03, 2025 11:01 am
by operadude
CharlesV wrote: Thu Jul 03, 2025 10:58 am
Perfect. (I was thinking maybe that local was overriding the other location.)
This is starting to sound like your wayland scaling is broken - and I bet this is that wayland / nvidia issue I read about.
That Xsetup is to manipulate X11 around and since it has no effect ... Let me see if I can find a wayland equivalent. ( or since that machine has nvidia, maybe we can push back to X11 ? Let me see what I can find. )
Fantastic
But, are you sure I am using Wayland?
I thought I was using the X11 Session ?
FYI, I have BOTH my rigs going now, and both signed into the Forum !
ADDITION:
Is this info from my QSI (testing rig, "problematic" system) relevant?:
Code: Select all
Snapshot created on: 20250617_1407
System:
Kernel: 6.1.0-37-amd64 [6.1.140-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-37-amd64 root=UUID=<filter> ro quiet splash
Desktop: KDE Plasma v: 5.27.5 info: plank wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23.6_x64
Libretto October 13 2023 base: Debian GNU/Linux 12 (bookworm)
That shows the "wm" as kwin_x11
So, NOT Wayland ?
ADDITION:
Ahh..., but I also see this from the QSI:
Code: Select all
Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
loaded: nvidia unloaded: fbdev,modesetting,nouveau,vesa alternate: nv gpu: nvidia display-ID: :0
screens: 1
So, how does this work? X11 server WITH Xwayland?
Re: Manually Change in CLI: s-dpi, s-size & s-diag
Posted: Thu Jul 03, 2025 11:10 am
by CharlesV
Xactly ! ( Sorry, had to do it !) .. That was why I headed for the XSetup file.
Lets try this...
in your /etc/addm.conf file , under the General section add the following and reboot.
and if that STILL has no change, then add this line (also under the General Section )
I dont believe thsi second line will make any difference as I think you are already ON the X11 server.. but ... worth a try.
Re: Manually Change in CLI: s-dpi, s-size & s-diag
Posted: Thu Jul 03, 2025 11:13 am
by operadude
CharlesV wrote: Thu Jul 03, 2025 11:10 am
Xactly ! ( Sorry, had to do it !) .. That was why I headed for the XSetup file.
Lets try this...
in your /etc/addm.conf file , under the General section add the following and reboot.
and if that STILL has no change, then add this line (also under the General Section )
I dont believe thsi second line will make any difference as I think you are already ON the X11 server.. but ... worth a try.
No "/etc/addm.conf file"
EDIT:
Ahh...looks like a typo...must be "sddm.conf"
Will try now...
Re: Manually Change in CLI: s-dpi, s-size & s-diag [Solved]
Posted: Thu Jul 03, 2025 11:16 am
by CharlesV
sorry.. typo.
sddm.conf
Also.. I just saw there are system-settings for sddm.
Start system-settings from the MX menu, then type in sddm
click on Login Screen, and at the bottom there is a button that says "Apply Plasma Settings"
If you click that button shows a number of things that are about to be changed, ONE of which IS DPI to match your desktop!!
Please try that.
Re: Manually Change in CLI: s-dpi, s-size & s-diag
Posted: Thu Jul 03, 2025 11:19 am
by operadude
@CharlesV No "General" section !
Here are the complete contents of /etc/sddm.conf
Code: Select all
[Theme]
CursorTheme=breeze_cursors
Re: Manually Change in CLI: s-dpi, s-size & s-diag
Posted: Thu Jul 03, 2025 11:22 am
by operadude
CharlesV wrote: Thu Jul 03, 2025 11:16 am
sorry.. typo.
sddm.conf
Also.. I just saw there are system-settings for sddm.
Start system-settings from the MX menu, then type in sddm
click on Login Screen, and at the bottom there is a button that says "Apply Plasma Settings"
If you click that button shows a number of things that are about to be changed, ONE of which IS DPI to match your desktop!!
Please try that.
On It
Re: Manually Change in CLI: s-dpi, s-size & s-diag
Posted: Thu Jul 03, 2025 11:26 am
by CharlesV
Very odd.. both my machines the sddm.conf files have this:
Code: Select all
[Autologin]
Relogin=false
Session=plasma.desktop
User=
[General]
HaltCommand=
RebootCommand=
DisplayServer=x11
EnableHiDPI=true
[Theme]
Current=monochrome
[Users]
MaximumUid=60000
MinimumUid=1000
and I added the
DisplayServer=x11
EnableHiDPI=true
on this VM.
Re: Manually Change in CLI: s-dpi, s-size & s-diag
Posted: Thu Jul 03, 2025 11:30 am
by operadude
operadude wrote: Thu Jul 03, 2025 11:22 am
CharlesV wrote: Thu Jul 03, 2025 11:16 am
sorry.. typo.
sddm.conf
Also.. I just saw there are system-settings for sddm.
Start system-settings from the MX menu, then type in sddm
click on Login Screen, and at the bottom there is a button that says "Apply Plasma Settings"
If you click that button shows a number of things that are about to be changed, ONE of which IS DPI to match your desktop!!
Please try that.
On It
AND THE WINNER IS...
@CharlesV
That did it
Now, give yourself a raise, and I hereby decree that:
Thou Shall Take a Vacation Day Tomorrow
Thank You CharlesV, My Yankee Doodle Dandy
Now, Go Celebrate
What, no Fireworks Emoji ???
Anyway...
Re: Manually Change in CLI: s-dpi, s-size & s-diag
Posted: Thu Jul 03, 2025 11:32 am
by CharlesV
Excellent! Your very welcome and glad we got that. (I should remember to check 'settings' FIRST ;-p .. ) But Yessir.. I need a nap now ! ( or more coffee !!)
Re: Manually Change in CLI: s-dpi, s-size & s-diag
Posted: Thu Jul 03, 2025 11:34 am
by operadude
CharlesV wrote: Thu Jul 03, 2025 11:32 am
Excellent! Your very welcome and glad we got that. (I should remember to check 'settings' FIRST ;-p .. ) But Yessir.. I need a nap now ! ( or more coffee !!)
Whatever floats your boat...
Whatever it is...YOU EARNED IT
Re: Manually Change in CLI: s-dpi, s-size & s-diag
Posted: Thu Jul 03, 2025 11:35 am
by CharlesV
thanks!
