Unable to modify screen resolution after sytem update

N3M3SIS · 25 June 2023 09:54

Fully updated my system yesterday with garuda-update -a.

Before the update, my screen resolution was 1920x1200.
After reboot, my screen resolution was modified back to its original resolution 2880x1800.

The setting to modify it is not available anymore.
A message says :

I actually have Wayland installed on my system, but not currently using it (except if KDE plasma now does ?). I need to keep Wayland installed to run my Hyprland session (which is not active when this problem happens). My main session runs KDE.

garuda-inxi

System:
  Kernel: 6.3.9-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.1.1
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=394702fa-734d-4ffe-be2e-fc60fa05f197 rw rootflags=subvol=@
    quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
    systemd.unified_cgroup_hierarchy=1
    resume=UUID=6e50783f-d483-49d4-ae7f-6d21a4cb652d loglevel=3 ibt=off
  Desktop: KDE Plasma v: 5.27.6 tk: Qt v: 5.15.10 wm: kwin_x11 vt: 1
    dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Laptop System: ASUSTeK product: Vivobook_ASUSLaptop M3401QA_M3401QA
    v: 1.0 serial: <superuser required>
  Mobo: ASUSTeK model: M3401QA v: 1.0 serial: <superuser required>
    UEFI: American Megatrends LLC. v: M3401QA.303 date: 08/06/2021
Battery:
  ID-1: BAT0 charge: 54.6 Wh (100.0%) condition: 54.6/63.0 Wh (86.6%)
    volts: 12.0 min: 12.0 model: ASUSTeK ASUS Battery type: Li-ion serial: N/A
    status: not charging cycles: 71
  Device-1: hidpp_battery_0 model: Logitech MX Keys Wireless Keyboard
    serial: <filter> charge: 55% (should be ignored) rechargeable: yes
    status: discharging
  Device-2: hidpp_battery_1 model: Logitech Wireless Mouse MX Master 3
    serial: <filter> charge: 100% (should be ignored) rechargeable: yes
    status: discharging
CPU:
  Info: model: AMD Ryzen 7 5800H with Radeon Graphics bits: 64 type: MT MCP
    arch: Zen 3 gen: 4 level: v3 note: check built: 2021-22
    process: TSMC n7 (7nm) family: 0x19 (25) model-id: 0x50 (80) stepping: 0
    microcode: 0xA50000C
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
    L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
    L3: 16 MiB desc: 1x16 MiB
  Speed (MHz): avg: 1200 high: 1240 min/max: 1200/4462 boost: enabled
    scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 1198 2: 1198
    3: 1197 4: 1198 5: 1200 6: 1198 7: 1197 8: 1200 9: 1198 10: 1198 11: 1200
    12: 1240 13: 1197 14: 1198 15: 1197 16: 1200 bogomips: 102212
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series]
    vendor: ASUSTeK driver: amdgpu v: kernel arch: GCN-5 code: Vega
    process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s ports: active: HDMI-A-1,eDP-1 empty: none
    bus-ID: 03:00.0 chip-ID: 1002:1638 class-ID: 0300 temp: 48.0 C
  Device-2: IMC Networks USB2.0 HD UVC WebCam driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-3:3 chip-ID: 13d3:5458
    class-ID: fe01 serial: <filter>
  Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.2
    compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting
    alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 4800x1800 s-dpi: 96 s-size: 1269x475mm (49.96x18.70")
    s-diag: 1355mm (53.35")
  Monitor-1: HDMI-A-1 mapped: HDMI-A-0 pos: primary,right model: AOC 27B2
    serial: <filter> built: 2020 res: 1920x1080 dpi: 82 gamma: 1.2
    size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  Monitor-2: eDP-1 mapped: eDP pos: left model: Samsung 0x4154 built: 2020
    res: 2880x1800 hz: 90 dpi: 242 gamma: 1.2 size: 302x189mm (11.89x7.44")
    diag: 356mm (14") ratio: 16:10 modes: 2880x1800
  API: OpenGL v: 4.6 Mesa 23.1.2 renderer: AMD Radeon Graphics (renoir LLVM
    15.0.7 DRM 3.52 6.3.9-zen1-1-zen) direct-render: Yes
Audio:
  Device-1: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel
    v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4
    speed: 16 GT/s bus-ID: 03:00.1 chip-ID: 1002:1637 class-ID: 0403
  Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: ASUSTeK
    driver: N/A alternate: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x,
    snd_pci_acp6x, snd_acp_pci, snd_rpl_pci_acp6x, snd_pci_ps,
    snd_sof_amd_renoir, snd_sof_amd_rembrandt pcie: gen: 3 speed: 8 GT/s
    lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 03:00.5
    chip-ID: 1022:15e2 class-ID: 0480
  Device-3: AMD Family 17h/19h HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s bus-ID: 03:00.6 chip-ID: 1022:15e3
    class-ID: 0403
  Device-4: C-Media CM106 Like Sound Device
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 1-2:2 chip-ID: 0d8c:0102 class-ID: 0300
  API: ALSA v: k6.3.9-zen1-1-zen status: kernel-api tools: N/A
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: PipeWire v: 0.3.71 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: MEDIATEK MT7921 802.11ax PCI Express Wireless Network Adapter
    vendor: AzureWave driver: mt7921e v: kernel pcie: gen: 2 speed: 5 GT/s
    lanes: 1 bus-ID: 01:00.0 chip-ID: 14c3:7961 class-ID: 0280
  IF: wlp1s0 state: up mac: <filter>
Bluetooth:
  Device-1: IMC Networks Wireless_Device driver: btusb v: 0.8 type: USB
    rev: 2.1 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-2:2 chip-ID: 13d3:3563
    class-ID: e001 serial: <filter>
  Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
  Local Storage: total: 953.87 GiB used: 123.45 GiB (12.9%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Intel model: SSDPEKNU010TZ
    size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 002C temp: 34.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 936.96 GiB size: 936.96 GiB (100.00%)
    used: 123.45 GiB (13.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 576 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 936.96 GiB size: 936.96 GiB (100.00%)
    used: 123.45 GiB (13.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-4: /var/log raw-size: 936.96 GiB size: 936.96 GiB (100.00%)
    used: 123.45 GiB (13.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-5: /var/tmp raw-size: 936.96 GiB size: 936.96 GiB (100.00%)
    used: 123.45 GiB (13.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 16.61 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/nvme0n1p3 maj-min: 259:3
  ID-2: swap-2 type: zram size: 15.03 GiB used: 5.48 GiB (36.5%)
    priority: 100 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 58.5 C mobo: N/A gpu: amdgpu temp: 48.0 C
  Fan Speeds (RPM): cpu: 3100
Info:
  Processes: 443 Uptime: 18h 32m wakeups: 72 Memory: available: 15.03 GiB
  used: 9.79 GiB (65.1%) Init: systemd v: 253 default: graphical
  tool: systemctl Compilers: gcc: 13.1.1 clang: 15.0.7 Packages: pm: pacman
  pkgs: 2199 libs: 434 tools: octopi,pamac,paru,yay Shell: Zsh v: 5.9
  running-in: xfce4-terminal inxi: 3.3.27
Garuda (2.6.16-1):
  System install date:     2022-01-04
  Last full system update: 2023-06-24
  Is partially upgraded:   No
  Relevant software:       snapper(custom) NetworkManager mkinitcpio
  Windows dual boot:       No/Undetected
  Failed units:

BluishHumility · 25 June 2023 15:05

Check the output of:

echo $XDG_SESSION_TYPE

Check the rest of your environment variables as well, by running env. If anything is set to Wayland, you may have overwritten a needed environment variable by installing Hyprland on top of KDE. It is very easy to break stuff by layering DEs on top of each other like this.

N3M3SIS · 25 June 2023 16:38

KDE_SESSION_UID=1000
DESKTOP_SESSION=plasma
XDG_SESSION_DESKTOP=KDE
XDG_CURRENT_DESKTOP=KDE
$XDG_SESSION_TYPE=x11
KDE_SESSION_VERSION=5
KDE_FULL_SESSION=true

Here are the DE variables I could find in my environment.
Doesn't seem to be related to Wayland ?

BluishHumility · 25 June 2023 16:56

Hmm, you should have way more environment variables than that. Did you run env? Or is that just a random selection?

If you run env and you don’t have any variables set to “Wayland”, the issue is probably something else.

I would first reboot, to confirm the issue persists afterward. If it does, try booting into the snapshot from before yesterday’s update and see if the setting is back to normal inside the snapshot.

N3M3SIS · 27 June 2023 14:07

I tried to reboot on the pre update snapshot, but it did not fix it.
Also here is my full env :

environment

LC_TELEPHONE=fr_FR.UTF-8
KDE_SESSION_UID=1000
DESKTOP_SESSION=plasma
PWD=/home/****
WINDOWID=140509187
HG=/usr/bin/hg
GTK3_MODULES=xapp-gtk3-module
LOGNAME=****
MAIL=/var/spool/mail/****
LC_MEASUREMENT=fr_FR.UTF-8
XDG_SESSION_TYPE=x11
SYSTEMD_EXEC_PID=1746
PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/lib/emscripten:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/home/****/.spicetify:/home/****/Downloads/getbrains/ideaIU-2022.3.2/idea-IU-223.8617.56/bin
HOME=/home/****
SDL_IM_MODULE=fcitx
QT_IM_MODULE=fcitx
XCURSOR_THEME=Nordic-cursors
USER=****
DISPLAY=:0
INVOCATION_ID=3c9b183d06dc4d3ab52379a73ebc7a60
QT_AUTO_SCREEN_SCALE_FACTOR=0
MOTD_SHOWN=pam
JOURNAL_STREAM=8:26143
LANG=en_US.UTF-8
LC_NAME=fr_FR.UTF-8
XAUTHORITY=/tmp/xauth_ZxbsVV
LC_PAPER=fr_FR.UTF-8
SESSION_MANAGER=local/****:@/tmp/.ICE-unix/1693,unix/****:/tmp/.ICE-unix/1693
XCURSOR_SIZE=24
GTK_RC_FILES=/etc/gtk/gtkrc:/home/****/.gtkrc:/home/****/.config/gtkrc
XDG_RUNTIME_DIR=/run/user/1000
XDG_SESSION_ID=2
XDG_SESSION_DESKTOP=KDE
INPUT_METHOD=fcitx
VTE_VERSION=7202
XDG_CURRENT_DESKTOP=KDE
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session1
XDG_CONFIG_DIRS=/home/****/.config/kdedefaults:/etc/xdg
LC_ADDRESS=fr_FR.UTF-8
SHELL=/bin/zsh
GTK_IM_MODULE=fcitx
KDE_SESSION_VERSION=5
GRADLE_HOME=/usr/share/java/gradle
UBUNTU_MENUPROXY=1
PAM_KWALLET5_LOGIN=/run/user/1000/kwallet5.socket
XDG_SESSION_CLASS=user
LC_IDENTIFICATION=fr_FR.UTF-8
MANAGERPID=1249
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
GTK_MODULES=canberra-gtk-module:appmenu-gtk-module
KDE_FULL_SESSION=true
XMODIFIERS=@im=fcitx
OLDPWD=/home/****
XDG_VTNR=2
QT_SCREEN_SCALE_FACTORS=eDP=1;HDMI-A-0=1;
DEBUGINFOD_URLS=https://debuginfod.archlinux.org
LC_NUMERIC=fr_FR.UTF-8
KDE_APPLICATIONS_AS_SCOPE=1
D_DISABLE_RT_SCREEN_SCALE=1
TERM=xterm-256color
COLORTERM=truecolor
LC_TIME=fr_FR.UTF-8
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/****/.gtkrc-2.0:/home/****/.config/gtkrc-2.0
LC_MONETARY=fr_FR.UTF-8
XDG_SEAT=seat0
SHLVL=1
P9K_TTY=old
_P9K_TTY=/dev/pts/1
ZSH=/home/****/.oh-my-zsh
PAGER=less
LESS=-R
LSCOLORS=Gxfxcxdxbxegedabagacad
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=00:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.avif=01;35:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.webp=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:*~=00;90:*#=00;90:*.bak=00;90:*.old=00;90:*.orig=00;90:*.part=00;90:*.rej=00;90:*.swp=00;90:*.tmp=00;90:*.dpkg-dist=00;90:*.dpkg-old=00;90:*.ucf-dist=00;90:*.ucf-new=00;90:*.ucf-old=00;90:*.rpmnew=00;90:*.rpmorig=00;90:*.rpmsave=00;90:
P9K_SSH=0
_P9K_SSH_TTY=/dev/pts/1
SSH_AUTH_SOCK=/tmp/ssh-XXXXXXtsbFtW/agent.18795
SSH_AGENT_PID=18796
_=/usr/bin/env

BluishHumility · 27 June 2023 16:53

Try manually adding the 1920x1200 resolution with xrandr, as described here: xrandr - ArchWiki

First get the modeline with cvt:

cvt 1920 1200

Add a new mode in xrandr:

xrandr --newmode [enter Modeline value from cvt command above]

Add the mode to your output:

xrandr --addmode eDP-1 1920x1200_60.00

That's just an example, obviously use the values you get from the Modeline.

Switch the output to use the new mode:

xrandr --output eDP-1 1920x1200_60.00

N3M3SIS · 28 June 2023 09:00

Here is my original xrandr output. The resolution problem hapens on my laptop screen (eDP)

Screen 0: minimum 320 x 200, current 4800 x 1800, maximum 16384 x 16384

eDP connected 2880x1800+0+0 (normal left inverted right x axis y axis) 302mm x 189mm
   2880x1800     90.00*+  60.00
   (used to be way more options than only this one)

HDMI-A-0 connected primary 1920x1080+2880+0 (normal left inverted right x axis y axis) 598mm x 336mm
   1920x1080     60.00 +  74.97*   50.00    59.94
   ...
   (pointless to show other options for this screen - no problem with this one)

Here are the commands I executed :

cvt 1920 1200 90  # I also tried every commands with 60Hz

# 1920x1200 89.91 Hz(CVT) hsync: 113.83 kHz; pclk: 300.50 MHz
Modeline "1920x1200_90.00"  300.50  1920 2072 2280 2640  1200 1203 1209 1266 -hsync +vsync

xrandr --newmode "1920x1200_90.00"  300.50  1920 2072 2280 2640  1200 1203 1209 1266 -hsync +vsync

xrandr --addmode eDP 1920x1200_90.00

After this command, the 1920x1200 option appeared in xrandr and in settings menu :

Screen 0: minimum 320 x 200, current 4800 x 1800, maximum 16384 x 16384
eDP connected 2880x1800+0+0 (normal left inverted right x axis y axis) 302mm x 189mm
   2880x1800     90.00*+  60.00  
   1920x1200_90.00  89.91  # new mode
HDMI-A-0 connected primary 1920x1080+2880+0 (normal left inverted right x axis y axis) 598mm x 336mm
   1920x1080     60.00 +  74.97*   50.00    59.94
   ...

Then I switched mode by running this
xrandr --output eDP --mode 1920x1200_90.00
or by choosing this new mode in the settings options, my screen turns black every time.

Screen 0: minimum 320 x 200, current 4800 x 1200, maximum 16384 x 16384
eDP connected 1920x1200+0+0 (normal left inverted right x axis y axis) 302mm x 189mm
   2880x1800     90.00 +  60.00  
   1920x1200_90.00  89.91*  # the mode is selected
HDMI-A-0 connected primary 1920x1080+2880+0 (normal left inverted right x axis y axis) 598mm x 336mm
   1920x1080     60.00 +  74.97*   50.00    59.94  
   ...

I tried to reboot, but after each attempt the new mode is just gone after reboot.
Switching back to 2880x1800 60/90Hz makes the screen work again.
I noticed that after switching to the new mode, the screen settings looked a bit weird, they are spaced I'm not sure to understand why :

BluishHumility · 28 June 2023 12:24

That is perfectly normal. A persistent configuration requires additional configuration, see the next section in the article:

Permanently adding undetected resolutions

Once a suitable resolution is found using xrandr, the mode can be permanently added by creating an entry in /etc/X11/xorg.conf.d/:
/etc/X11/xorg.conf.d/10-monitor.conf`

Section "Monitor" 
     Identifier "VGA1" 
     Modeline "1280x1024_60.00" 109.00 1280 1368 1496 1712 1024 1027 1034 1063 -hsync +vsync 
     Option "PreferredMode" "1280x1024_60.00" 
EndSection 

Section "Screen" 
     Identifier "Screen0" 
     Monitor "VGA1" 
     DefaultDepth 24 
     SubSection "Display" 
          Modes "1280x1024_60.00" 
     EndSubSection 
EndSection 

Section "Device" 
     Identifier "Device0" 
     Driver "intel" 
EndSection
Replace intel with the right driver, e.g. nvidia. When the X server is restarted, you should be able to set the new resolution.

If this does not work for you, try removing the Screen and Device sections and just leaving the Monitor section. [3]

This is because the resolution of the leftmost display has changed, but the position of the rightmost display has not–it is still configured to be positioned at pixel 2880. When you change the leftmost display to only occupy 1920 pixels, that leaves a gap of 960 pixels between the two displays.

Probably configuring the persistent resolution will be all that is needed to fix that behavior with the gap, but if the position needs to be specified I believe you can do so with another Option line in the /etc/X11/xorg.conf.d/ config, for example:

Section "Monitor"
    Identifier "VGA1"
    Modeline "1280x1024_60.00"  109.00  1280 1368 1496 1712  1024 1027 1034 1063 -hsync +vsync
    Option "PreferredMode" "1280x1024_60.00"
    Option "Position" "1920 0"  # Specify the monitor position here
EndSection

I just copied the example from the ArchWiki, but added a line to specify that this display should be positioned at pixel 1920.

N3M3SIS · 28 June 2023 12:37

Okay thanks for the tips using xorg.conf.d

But for now my main concern is finding why my screen turns black when I switch to another resolution.

I tried creating modes of different resolutions / refresh rates. But every time I apply them, my screen just turns full black. I tried with : 1920x1200 60/90Hz & 1600x900 60/90Hz

Also tried to disconnect external screen before applying new mode (1920x1200) to my eDP screen.
And some obscure GPT approach :

xrandr --fb 1920x1200
xrandr --output eDP --mode 1920x1200 --rate 90

xrandr --query | grep "connected primary" | awk '{print $3}'
xrandr --output eDP --mode 2880x1800 --rate 90 --scale 0.6667x0.6667

N3M3SIS · 8 July 2023 11:02

Still can't figure how to get my 1920x1200 resolution back.
Here is a chat I had with GPT trying to solve this issue :

SGS · 8 July 2023 11:32

"a while ago I tried to install Wayland to configure Hyprland."

In hyprland you must set the scale value in hyprland.conf

# See https://wiki.hyprland.org/Configuring/Monitors/
monitor=,preferred,auto,1

to

monitor=,preferred,auto,1.5 # or 2

and sorry, IDK which DE do you use just now

N3M3SIS · 8 July 2023 13:04

I'm running KDE Plasma with X11 compositor.
I'm not trying to run Wayland / configure Hyprland, this is a side project.
I'm trying to get my screen resolution to be 1920x1200 but since I updated my system a few days ago, my system 'thinks' I'm running a Wayland session, thus making me unable to modify my laptop screen resolution.
yes when I boot up my laptop I select Plasma (X11) in session selector.

Bro · 8 July 2023 13:18

Have you tried different kernels?

N3M3SIS · 8 July 2023 13:27

Yeh same problem with zen, lts and mainline.

filo · 8 July 2023 14:11

Have you tried creating a different user?

N3M3SIS · 8 July 2023 15:02

yep: the problem also occurs for other users.
Tried using kernel Zen, LTS, Mainline.

system · 3 August 2023 09:52

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.