Hello everyone. I have a multimonitor system, with two Medion and one Lenovo. The Medion are not native DP, but use an adapter to achieve connectivity. The Lenovo is native DP. One Medion stands on the right of the Lenovo, the other on the left. Now, when starting in Plasma there the order is fine and defined in settings: Medion on the left, Lenovo, Medion on the right. But when having the three login screens I encounter the problem that this order is not respected. Medion is on the left, then the cursor jumps to the uttermost right to the second Medion and turns then to the Lenovo. So for SDDM the order is Medion, Medion, Lenovo. Now my question: is there a way I can enforce the very order of monitors defined in plasma KDE onto SDDM? In some situation (seems stupid, but the cursor is small) it is difficult to understand how to reach the input window and you may think the cursor vanished while it is just on a "monitor odyssey" so to say. Thank you for the input if anybody by chance knows how to do this, were to set it.
On Mittwoch, 21. Juni 2023 21:29:15 CEST Stakanov wrote:
Hello everyone. I have a multimonitor system, with two Medion and one Lenovo. The Medion are not native DP, but use an adapter to achieve connectivity. The Lenovo is native DP. One Medion stands on the right of the Lenovo, the other on the left. Now, when starting in Plasma there the order is fine and defined in settings:
Medion on the left, Lenovo, Medion on the right.
But when having the three login screens I encounter the problem that this order is not respected. Medion is on the left, then the cursor jumps to the uttermost right to the second Medion and turns then to the Lenovo. So for SDDM the order is Medion, Medion, Lenovo.
Now my question: is there a way I can enforce the very order of monitors defined in plasma KDE onto SDDM?
In some situation (seems stupid, but the cursor is small) it is difficult to understand how to reach the input window and you may think the cursor vanished while it is just on a "monitor odyssey" so to say.
Thank you for the input if anybody by chance knows how to do this, were to set it.
Perhaps this could help: Create a file /etc/sddm.conf.d/99-my-sddm.conf with the following contents: [X11] DisplayCommand=/usr/local/sbin/displaymanager-Xsetup This script could contain something like xrandr --output "<connector lenovo>" --primary xrandr --output "<connector medion1>" --leftof "<connector lenovo>" xrandr --output "<connector medion2>" --rightof "<connector lenovo>" You can find the names of the connectors with xrandr | grep " connected" | awk '{ print $1 }' Bye Michael.
In data mercoledì 21 giugno 2023 22:12:28 CEST, mh@mike.franken.de ha scritto:
On Mittwoch, 21. Juni 2023 21:29:15 CEST Stakanov wrote:
Hello everyone. I have a multimonitor system, with two Medion and one Lenovo. The Medion are not native DP, but use an adapter to achieve connectivity. The Lenovo is native DP. One Medion stands on the right of the Lenovo, the other on the left. Now, when starting in Plasma there the order is fine and defined in settings:
Medion on the left, Lenovo, Medion on the right.
But when having the three login screens I encounter the problem that this order is not respected. Medion is on the left, then the cursor jumps to the uttermost right to the second Medion and turns then to the Lenovo. So for SDDM the order is Medion, Medion, Lenovo.
Now my question: is there a way I can enforce the very order of monitors defined in plasma KDE onto SDDM?
In some situation (seems stupid, but the cursor is small) it is difficult to understand how to reach the input window and you may think the cursor vanished while it is just on a "monitor odyssey" so to say.
Thank you for the input if anybody by chance knows how to do this, were to set it.
Perhaps this could help:
Create a file /etc/sddm.conf.d/99-my-sddm.conf with the following contents:
[X11] DisplayCommand=/usr/local/sbin/displaymanager-Xsetup
This script could contain something like
xrandr --output "<connector lenovo>" --primary xrandr --output "<connector medion1>" --leftof "<connector lenovo>" xrandr --output "<connector medion2>" --rightof "<connector lenovo>"
You can find the names of the connectors with
xrandr | grep " connected" | awk '{ print $1 }'
Bye Michael.
Brilliant, only that the identification of who is who is somewhat odd: entropy@localhost:~> xrandr | grep " connected" | awk '{ print $1 }' DP-1 DP-2 DP-3 Which does not tell me who is who so to say. I would need to find out what SDDM thinks is attached to DP-1, DP-2 and DP-3. If not that is brilliant, just have to find out how to do the aforementioned. This because I am by no means sure that what KDE thinks is on DP-x is also for SDDM alike.
On 2023-06-21 22:27, Stakanov wrote:
In data mercoledì 21 giugno 2023 22:12:28 CEST, mh@mike.franken.de ha scritto:
On Mittwoch, 21. Juni 2023 21:29:15 CEST Stakanov wrote:
You can find the names of the connectors with
xrandr | grep " connected" | awk '{ print $1 }'
Brilliant, only that the identification of who is who is somewhat odd:
entropy@localhost:~> xrandr | grep " connected" | awk '{ print $1 }' DP-1 DP-2 DP-3
Which does not tell me who is who so to say. I would need to find out what SDDM thinks is attached to DP-1, DP-2 and DP-3.
Try printing the entire line. xrandr | grep " connected" -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 2023-06-21 22:27, Stakanov wrote:
In data mercoledì 21 giugno 2023 22:12:28 CEST, mh@mike.franken.de ha scritto:
On Mittwoch, 21. Juni 2023 21:29:15 CEST Stakanov wrote:
You can find the names of the connectors with
xrandr | grep " connected" | awk '{ print $1 }'
Brilliant, only that the identification of who is who is somewhat odd:
entropy@localhost:~> xrandr | grep " connected" | awk '{ print $1 }' DP-1 DP-2 DP-3
Which does not tell me who is who so to say. I would need to find out what SDDM
In data mercoledì 21 giugno 2023 22:37:56 CEST, Carlos E. R. ha scritto: thinks is attached to DP-1, DP-2 and DP-3.
Try printing the entire line.
xrandr | grep " connected"
-- Cheers / Saludos,
Carlos E. R. (from 15.4 x86_64 at Telcontar)
Brilliant Carlos too, so: entropy@localhost:~> xrandr | grep " connected" DP-1 connected primary 2560x1440+1920+0 (normal left inverted right x axis y axis) 698mm x 393mm which is the Lenovo DP-2 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 509mm x 286mm which should be the Medion 20999 on the left DP-3 connected 1920x1080+4480+0 (normal left inverted right x axis y axis) 509mm x 286mm which is Medion 20666 on the left. Ok, I will try to do that thing with the config file. I am hopeful now.
On Wed, 21 Jun 2023 22:27:17 +0200 Stakanov <stakanov@disroot.org> wrote:
In data mercoledì 21 giugno 2023 22:12:28 CEST, mh@mike.franken.de ha scritto:
On Mittwoch, 21. Juni 2023 21:29:15 CEST Stakanov wrote:
Hello everyone. I have a multimonitor system, with two Medion and one Lenovo. The Medion are not native DP, but use an adapter to achieve connectivity. The Lenovo is native DP. One Medion stands on the right of the Lenovo, the other on the left. Now, when starting in Plasma there the order is fine and defined in settings:
Medion on the left, Lenovo, Medion on the right.
But when having the three login screens I encounter the problem that this order is not respected. Medion is on the left, then the cursor jumps to the uttermost right to the second Medion and turns then to the Lenovo. So for SDDM the order is Medion, Medion, Lenovo.
Now my question: is there a way I can enforce the very order of monitors defined in plasma KDE onto SDDM?
In some situation (seems stupid, but the cursor is small) it is difficult to understand how to reach the input window and you may think the cursor vanished while it is just on a "monitor odyssey" so to say.
Thank you for the input if anybody by chance knows how to do this, were to set it.
Perhaps this could help:
Create a file /etc/sddm.conf.d/99-my-sddm.conf with the following contents:
[X11] DisplayCommand=/usr/local/sbin/displaymanager-Xsetup
This script could contain something like
xrandr --output "<connector lenovo>" --primary xrandr --output "<connector medion1>" --leftof "<connector lenovo>" xrandr --output "<connector medion2>" --rightof "<connector lenovo>"
You can find the names of the connectors with
xrandr | grep " connected" | awk '{ print $1 }'
Bye Michael.
Brilliant, only that the identification of who is who is somewhat odd:
entropy@localhost:~> xrandr | grep " connected" | awk '{ print $1 }' DP-1 DP-2 DP-3
Which does not tell me who is who so to say. I would need to find out what SDDM thinks is attached to DP-1, DP-2 and DP-3.
Just try it with some order of labels. It may happen to be right. If not, change the order of the labels and try again. Repeat until solved.
If not that is brilliant, just have to find out how to do the aforementioned. This because I am by no means sure that what KDE thinks is on DP-x is also for SDDM alike.
In data mercoledì 21 giugno 2023 22:42:11 CEST, Dave Howorth ha scritto:
On Wed, 21 Jun 2023 22:27:17 +0200
Stakanov <stakanov@disroot.org> wrote:
In data mercoledì 21 giugno 2023 22:12:28 CEST, mh@mike.franken.de ha
scritto:
On Mittwoch, 21. Juni 2023 21:29:15 CEST Stakanov wrote:
Hello everyone. I have a multimonitor system, with two Medion and one Lenovo. The Medion are not native DP, but use an adapter to achieve connectivity. The Lenovo is native DP. One Medion stands on the right of the Lenovo, the other on the left. Now, when starting in Plasma there the order is fine and defined in settings:
Medion on the left, Lenovo, Medion on the right.
But when having the three login screens I encounter the problem that this order is not respected. Medion is on the left, then the cursor jumps to the uttermost right to the second Medion and turns then to the Lenovo. So for SDDM the order is Medion, Medion, Lenovo.
Now my question: is there a way I can enforce the very order of monitors defined in plasma KDE onto SDDM?
In some situation (seems stupid, but the cursor is small) it is difficult to understand how to reach the input window and you may think the cursor vanished while it is just on a "monitor odyssey" so to say.
Thank you for the input if anybody by chance knows how to do this, were to set it.
Perhaps this could help:
Create a file /etc/sddm.conf.d/99-my-sddm.conf with the following contents:
[X11] DisplayCommand=/usr/local/sbin/displaymanager-Xsetup
This script could contain something like
xrandr --output "<connector lenovo>" --primary xrandr --output "<connector medion1>" --leftof "<connector lenovo>" xrandr --output "<connector medion2>" --rightof "<connector lenovo>"
You can find the names of the connectors with
xrandr | grep " connected" | awk '{ print $1 }'
Bye Michael.
Brilliant, only that the identification of who is who is somewhat odd:
entropy@localhost:~> xrandr | grep " connected" | awk '{ print $1 }' DP-1 DP-2 DP-3
Which does not tell me who is who so to say. I would need to find out what SDDM thinks is attached to DP-1, DP-2 and DP-3.
Just try it with some order of labels. It may happen to be right. If not, change the order of the labels and try again. Repeat until solved.
If not that is brilliant, just have to find out how to do the aforementioned. This because I am by no means sure that what KDE thinks is on DP-x is also for SDDM alike.
I like the style, I am somewhat somebody who may go by trial and error. But I admit I am attracted by the beauty of the solution offered by Carlos. However I shirked a bit so to say. I labeled one by giving it another resolution, in the context of the output of the trick Carlos gave me, this allowed me to "lable by resolution". So in a certain sense I followed your idea as well. Thanks a lot, very helpful all three of you.
Stakanov composed on 2023-06-21 22:27 (UTC+0200):
2023 22:12:28 CEST, mh@mike... composed:
On Mittwoch, 21. Juni 2023 21:29:15 CEST Stakanov wrote:
Hello everyone. I have a multimonitor system, with two Medion and one Lenovo. The Medion are not native DP, but use an adapter to achieve connectivity. The Lenovo is native DP. One Medion stands on the right of the Lenovo, the other on the left. Now, when starting in Plasma there the order is fine and defined in settings:
Medion on the left, Lenovo, Medion on the right.
But when having the three login screens I encounter the problem that this order is not respected. Medion is on the left, then the cursor jumps to the uttermost right to the second Medion and turns then to the Lenovo. So for SDDM the order is Medion, Medion, Lenovo.
Now my question: is there a way I can enforce the very order of monitors defined in plasma KDE onto SDDM?
In some situation (seems stupid, but the cursor is small) it is difficult to understand how to reach the input window and you may think the cursor vanished while it is just on a "monitor odyssey" so to say.
Thank you for the input if anybody by chance knows how to do this, were to set it.
Perhaps this could help:
Create a file /etc/sddm.conf.d/99-my-sddm.conf with the following contents:
[X11] DisplayCommand=/usr/local/sbin/displaymanager-Xsetup
This script could contain something like
xrandr --output "<connector lenovo>" --primary xrandr --output "<connector medion1>" --leftof "<connector lenovo>" xrandr --output "<connector medion2>" --rightof "<connector lenovo>"
You can find the names of the connectors with
xrandr | grep " connected" | awk '{ print $1 }'
Brilliant, only that the identification of who is who is somewhat odd:
entropy@localhost:~> xrandr | grep " connected" | awk '{ print $1 }' DP-1 DP-2 DP-3
Which does not tell me who is who so to say. I would need to find out what SDDM thinks is attached to DP-1, DP-2 and DP-3.
If not that is brilliant, just have to find out how to do the aforementioned. This because I am by no means sure that what KDE thinks is on DP-x is also for SDDM alike.
You just had to wait until I left for my MD appt. to ask, didn't you. :p Display name mapping is something display drivers do to X/xrandr instead of using the names determined by the kernel driver. Inxi output shows the mapping. One system using Intel graphics and modesetting DIX display driver. First, the kernel names: # ls -1 /sys/class/drm card1 card1-DP-1 card1-DP-2 card1-DP-3 card1-HDMI-A-1 card1-HDMI-A-2 card1-HDMI-A-3 renderD128 version # Inxi also includes names experienced in X/xrandr: # inxi -Gaz inxi 3.3.27-00 (2023-05-07) Graphics: Device-1: Intel RocketLake-S GT1 [UHD Graphics 730] vendor: ASUSTeK driver: i915 v: kernel arch: Gen-12.1 process: Intel 10nm built: 2020-21 ports: active: DP-2,DP-3,HDMI-A-1 empty: DP-1,HDMI-A-2,HDMI-A-3 bus-ID: 00:02.0 chip-ID: 8086:4c8b class-ID: 0300 Display: x11 server: X.Org v: 21.1.8 driver: X: loaded: modesetting unloaded: fbdev,vesa alternate: intel dri: iris gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 5920x1440 s-dpi: 120 s-size: 1253x304mm (49.33x11.97") s-diag: 1289mm (50.76") Monitor-1: DP-2 mapped: DP-1-1 pos: left model: Dell P2213 serial: <filter> built: 2012 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2 size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400 Monitor-2: DP-3 mapped: DP-1-2 pos: right model: Dell P2213 serial: <filter> built: 2013 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2 size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400 Monitor-3: HDMI-A-1 mapped: HDMI-1 pos: primary,center model: Acer K272HUL serial: <filter> built: 2018 res: 2560x1440 hz: 60 dpi: 109 gamma: 1.2 size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes: max: 2560x1440 min: 720x400 API: OpenGL v: 4.6 Mesa 23.0.3 renderer: Mesa Intel Graphics (RKL GT1) direct-render: Yes # 2nd PC, AMDGPU DDX driver instead of Modesetting DIX: First, the kernel names: # ls -1 /sys/class/drm card1 card1-DP-1 card1-DVI-D-1 card1-HDMI-A-1 card1-VGA-1 renderD128 # Inxi also includes names experienced in X/xrandr: # inxi -Gaz inxi 3.3.27-00 (2023-05-07) Graphics: Device-1: AMD Kaveri [Radeon R7 Graphics] vendor: ASRock driver: amdgpu v: kernel alternate: radeon arch: GCN-2 code: Sea Islands process: GF/TSMC 16-28nm built: 2013-17 ports: active: DP-1, DVI-D-1, HDMI-A-1, VGA-1 empty: none bus-ID: 00:01.0 chip-ID: 1002:130f class-ID: 0300 Display: x11 server: X.Org v: 21.1.8 driver: X: loaded: amdgpu unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1 Screen-1: 0 s-res: 3600x2640 s-dpi: 120 s-size: 760x557mm (29.92x21.93") s-diag: 942mm (37.1") Monitor-1: DVI-D-1 mapped: DVI-D-0 pos: top-right model: Dell P2213 serial: <filter> built: 2012 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2 size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400 Monitor-2: DP-1 mapped: DisplayPort-0 pos: primary,bottom-l model: Acer K272HUL serial: <filter> built: 2018 res: 2560x1440 hz: 60 dpi: 109 gamma: 1.2 size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes: max: 2560x1440 min: 720x400 Monitor-3: HDMI-A-1 mapped: HDMI-A-0 pos: top-left model: NEC EA243WM serial: <filter> built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2 size: 519x324mm (20.43x12.76") diag: 612mm (24.1") ratio: 16:10 modes: max: 1920x1200 min: 640x480 Monitor-4: VGA-1 mapped: VGA-0 pos: middle-r model: Lenovo L2251x Wide serial: <filter> built: 2011 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2 size: 474x296mm (18.66x11.65") diag: 559mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400 # Names to expect to see from xrandr, as may have been noticed in inxi output above, and thus needed in individual xrandr scripts, may differ according to the DDX or DIX display driver in use. E.g. (FOSS drivers only): 1: using modesetting DIX, regardless of GPU, and on nouveau DDX: DP-1 HDMI-1 HDMI-2 2- using intel DDX: DP1 HDMI1 HDMI2 3- using amdgpu DDX or radeon DDX: DisplayPort-0 HDMI-0 HDMI-1 -- 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
On Donnerstag, 22. Juni 2023 02:13:42 CEST Felix Miata wrote: [...]
Inxi also includes names experienced in X/xrandr: # inxi -Gaz inxi 3.3.27-00 (2023-05-07) Graphics: Device-1: Intel RocketLake-S GT1 [UHD Graphics 730] vendor: ASUSTeK driver: i915 v: kernel arch: Gen-12.1 process: Intel 10nm built: 2020-21 ports: active: DP-2,DP-3,HDMI-A-1 empty: DP-1,HDMI-A-2,HDMI-A-3 bus-ID: 00:02.0 chip-ID: 8086:4c8b class-ID: 0300 Display: x11 server: X.Org v: 21.1.8 driver: X: loaded: modesetting unloaded: fbdev,vesa alternate: intel dri: iris gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 5920x1440 s-dpi: 120 s-size: 1253x304mm (49.33x11.97") s-diag: 1289mm (50.76") Monitor-1: DP-2 mapped: DP-1-1 pos: left model: Dell P2213 serial: <filter> built: 2012 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2 size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400 Monitor-2: DP-3 mapped: DP-1-2 pos: right model: Dell P2213 serial: <filter> built: 2013 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2 size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400 Monitor-3: HDMI-A-1 mapped: HDMI-1 pos: primary,center model: Acer K272HUL serial: <filter> built: 2018 res: 2560x1440 hz: 60 dpi: 109 gamma: 1.2 size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes: max: 2560x1440 min: 720x400 API: OpenGL v: 4.6 Mesa 23.0.3 renderer: Mesa Intel Graphics (RKL GT1) direct-render: Yes #
2nd PC, AMDGPU DDX driver instead of Modesetting DIX: First, the kernel names: # ls -1 /sys/class/drm card1 card1-DP-1 card1-DVI-D-1 card1-HDMI-A-1 card1-VGA-1 renderD128 # Inxi also includes names experienced in X/xrandr: # inxi -Gaz inxi 3.3.27-00 (2023-05-07) Graphics: Device-1: AMD Kaveri [Radeon R7 Graphics] vendor: ASRock driver: amdgpu v: kernel alternate: radeon arch: GCN-2 code: Sea Islands process: GF/TSMC 16-28nm built: 2013-17 ports: active: DP-1, DVI-D-1, HDMI-A-1, VGA-1 empty: none bus-ID: 00:01.0 chip-ID: 1002:130f class-ID: 0300 Display: x11 server: X.Org v: 21.1.8 driver: X: loaded: amdgpu unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1 Screen-1: 0 s-res: 3600x2640 s-dpi: 120 s-size: 760x557mm (29.92x21.93") s-diag: 942mm (37.1") Monitor-1: DVI-D-1 mapped: DVI-D-0 pos: top-right model: Dell P2213 serial: <filter> built: 2012 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2 size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400 Monitor-2: DP-1 mapped: DisplayPort-0 pos: primary,bottom-l model: Acer K272HUL serial: <filter> built: 2018 res: 2560x1440 hz: 60 dpi: 109 gamma: 1.2 size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes: max: 2560x1440 min: 720x400 Monitor-3: HDMI-A-1 mapped: HDMI-A-0 pos: top-left model: NEC EA243WM serial: <filter> built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2 size: 519x324mm (20.43x12.76") diag: 612mm (24.1") ratio: 16:10 modes: max: 1920x1200 min: 640x480 Monitor-4: VGA-1 mapped: VGA-0 pos: middle-r model: Lenovo L2251x Wide serial: <filter> built: 2011 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2 size: 474x296mm (18.66x11.65") diag: 559mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400 #
Names to expect to see from xrandr, as may have been noticed in inxi output above, and thus needed in individual xrandr scripts, may differ according to the DDX or DIX display driver in use. E.g. (FOSS drivers only): 1: using modesetting DIX, regardless of GPU, and on nouveau DDX: DP-1 HDMI-1 HDMI-2 2- using intel DDX: DP1 HDMI1 HDMI2 3- using amdgpu DDX or radeon DDX: DisplayPort-0 HDMI-0 HDMI-1
Great! I have to memorize that. I am an old school Linux guy, so inxi is "new" to me and I tend to forget its capabilites 8-| Bye. Michael.
In data giovedì 22 giugno 2023 02:13:42 CEST, Felix Miata ha scritto:
Stakanov composed on 2023-06-21 22:27 (UTC+0200):
2023 22:12:28 CEST, mh@mike... composed:
On Mittwoch, 21. Juni 2023 21:29:15 CEST Stakanov wrote:
Hello everyone. I have a multimonitor system, with two Medion and one Lenovo. The Medion are not native DP, but use an adapter to achieve connectivity. The Lenovo is native DP. One Medion stands on the right of the Lenovo, the other on the left. Now, when starting in Plasma there the order is fine and defined in settings:
Medion on the left, Lenovo, Medion on the right.
But when having the three login screens I encounter the problem that this order is not respected. Medion is on the left, then the cursor jumps to the uttermost right to the second Medion and turns then to the Lenovo. So for SDDM the order is Medion, Medion, Lenovo.
Now my question: is there a way I can enforce the very order of monitors defined in plasma KDE onto SDDM?
In some situation (seems stupid, but the cursor is small) it is difficult to understand how to reach the input window and you may think the cursor vanished while it is just on a "monitor odyssey" so to say.
Thank you for the input if anybody by chance knows how to do this, were to set it.
Perhaps this could help:
Create a file /etc/sddm.conf.d/99-my-sddm.conf with the following contents:
[X11] DisplayCommand=/usr/local/sbin/displaymanager-Xsetup
This script could contain something like
xrandr --output "<connector lenovo>" --primary xrandr --output "<connector medion1>" --leftof "<connector lenovo>" xrandr --output "<connector medion2>" --rightof "<connector lenovo>"
You can find the names of the connectors with
xrandr | grep " connected" | awk '{ print $1 }'
Brilliant, only that the identification of who is who is somewhat odd:
entropy@localhost:~> xrandr | grep " connected" | awk '{ print $1 }' DP-1 DP-2 DP-3
Which does not tell me who is who so to say. I would need to find out what SDDM thinks is attached to DP-1, DP-2 and DP-3.
If not that is brilliant, just have to find out how to do the aforementioned. This because I am by no means sure that what KDE thinks is on DP-x is also for SDDM alike.
You just had to wait until I left for my MD appt. to ask, didn't you. :p
Display name mapping is something display drivers do to X/xrandr instead of using the names determined by the kernel driver. Inxi output shows the mapping.
One system using Intel graphics and modesetting DIX display driver. First, the kernel names: # ls -1 /sys/class/drm card1 card1-DP-1 card1-DP-2 card1-DP-3 card1-HDMI-A-1 card1-HDMI-A-2 card1-HDMI-A-3 renderD128 version # Inxi also includes names experienced in X/xrandr: # inxi -Gaz inxi 3.3.27-00 (2023-05-07) Graphics: Device-1: Intel RocketLake-S GT1 [UHD Graphics 730] vendor: ASUSTeK driver: i915 v: kernel arch: Gen-12.1 process: Intel 10nm built: 2020-21 ports: active: DP-2,DP-3,HDMI-A-1 empty: DP-1,HDMI-A-2,HDMI-A-3 bus-ID: 00:02.0 chip-ID: 8086:4c8b class-ID: 0300 Display: x11 server: X.Org v: 21.1.8 driver: X: loaded: modesetting unloaded: fbdev,vesa alternate: intel dri: iris gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 5920x1440 s-dpi: 120 s-size: 1253x304mm (49.33x11.97") s-diag: 1289mm (50.76") Monitor-1: DP-2 mapped: DP-1-1 pos: left model: Dell P2213 serial: <filter> built: 2012 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2 size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400 Monitor-2: DP-3 mapped: DP-1-2 pos: right model: Dell P2213 serial: <filter> built: 2013 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2 size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400 Monitor-3: HDMI-A-1 mapped: HDMI-1 pos: primary,center model: Acer K272HUL serial: <filter> built: 2018 res: 2560x1440 hz: 60 dpi: 109 gamma: 1.2 size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes: max: 2560x1440 min: 720x400 API: OpenGL v: 4.6 Mesa 23.0.3 renderer: Mesa Intel Graphics (RKL GT1) direct-render: Yes #
2nd PC, AMDGPU DDX driver instead of Modesetting DIX: First, the kernel names: # ls -1 /sys/class/drm card1 card1-DP-1 card1-DVI-D-1 card1-HDMI-A-1 card1-VGA-1 renderD128 # Inxi also includes names experienced in X/xrandr: # inxi -Gaz inxi 3.3.27-00 (2023-05-07) Graphics: Device-1: AMD Kaveri [Radeon R7 Graphics] vendor: ASRock driver: amdgpu v: kernel alternate: radeon arch: GCN-2 code: Sea Islands process: GF/TSMC 16-28nm built: 2013-17 ports: active: DP-1, DVI-D-1, HDMI-A-1, VGA-1 empty: none bus-ID: 00:01.0 chip-ID: 1002:130f class-ID: 0300 Display: x11 server: X.Org v: 21.1.8 driver: X: loaded: amdgpu unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1 Screen-1: 0 s-res: 3600x2640 s-dpi: 120 s-size: 760x557mm (29.92x21.93") s-diag: 942mm (37.1") Monitor-1: DVI-D-1 mapped: DVI-D-0 pos: top-right model: Dell P2213 serial: <filter> built: 2012 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2 size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400 Monitor-2: DP-1 mapped: DisplayPort-0 pos: primary,bottom-l model: Acer K272HUL serial: <filter> built: 2018 res: 2560x1440 hz: 60 dpi: 109 gamma: 1.2 size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes: max: 2560x1440 min: 720x400 Monitor-3: HDMI-A-1 mapped: HDMI-A-0 pos: top-left model: NEC EA243WM serial: <filter> built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2 size: 519x324mm (20.43x12.76") diag: 612mm (24.1") ratio: 16:10 modes: max: 1920x1200 min: 640x480 Monitor-4: VGA-1 mapped: VGA-0 pos: middle-r model: Lenovo L2251x Wide serial: <filter> built: 2011 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2 size: 474x296mm (18.66x11.65") diag: 559mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400 #
Names to expect to see from xrandr, as may have been noticed in inxi output above, and thus needed in individual xrandr scripts, may differ according to the DDX or DIX display driver in use. E.g. (FOSS drivers only): 1: using modesetting DIX, regardless of GPU, and on nouveau DDX: DP-1 HDMI-1 HDMI-2 2- using intel DDX: DP1 HDMI1 HDMI2 3- using amdgpu DDX or radeon DDX: DisplayPort-0 HDMI-0 HDMI-1
Thank you, this finishes in my personal files
participants (5)
-
Carlos E. R. -
Dave Howorth -
Felix Miata -
mh＠mike.franken.de -
Stakanov