Latest zen-kernel update broke the screen resolution?

Hi!

I updated the system today using garuda-update, so zen-kernel upgraded from 6.4.** to 6.5.3 and now my screen resolution on 1920x1200 looks like this: https://snipboard.io/GtMDcu.jpg (sorry for the link to screenshot - I really can’t explain this stuff, seems resolution scaling is totally corrupted).

If I’m changing resolution to 2560x1600 - it’s looks normal, but it is way too small and if I’m trying to scale it to 125% or more - symbol rendering looks awful, can’t read it without blood out my eyes. :slight_smile:

I’m running Lenovo laptop with full AMD hardware, and at first I thought that it is problem caused by AMD drivers. I reverted back to snaphot and added mesa drivers to ignorepkg, then performed a full update again. Still I have this problem with resolution.

Then I tested wayland session and the resolution problem was absolutely the same.

After that I decided to try the LTS kernel 6.1.53-1-lts and I was able to switch my resolution to 1920x1200 without any problems.

Here is my xrandr output (it is the same for both kernels - zen and LTS):

Screen 0: minimum 320 x 200, current 2560 x 1600, maximum 16384 x 16384
eDP connected primary 2560x1600+0+0 (normal left inverted right x axis y axis) 344mm x 215mm
2560x1600    165.00*+  60.00 + 120.03    96.03    72.00    60.00
1920x1200    165.00
1920x1080    165.00
1600x1200    165.00
1680x1050    165.00
1280x1024    165.00
1440x900     165.00
1280x800     165.00
1280x720     165.00
1024x768     165.00
800x600      165.00
640x480      165.00
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-1 disconnected (normal left inverted right x axis y axis)
HDMI-A-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-1-2 disconnected (normal left inverted right x axis y axis)
DisplayPort-1-3 disconnected (normal left inverted right x axis y axis)
DisplayPort-1-4 disconnected (normal left inverted right x axis y axis)
DisplayPort-1-5 disconnected (normal left inverted right x axis y axis)
DisplayPort-1-6 disconnected (normal left inverted right x axis y axis)
DisplayPort-1-7 disconnected (normal left inverted right x axis y axis)

Here is my garuda-inxi on LTS kernel:

System:
Kernel: 6.1.53-1-lts arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc available: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-lts
root=UUID=a39d3c31-81a4-4ae9-ab96-46dcc08fd8c8 rw rootflags=subvol=@
quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
ibt=off
Desktop: KDE Plasma v: 5.27.8 tk: Qt v: 5.15.10 wm: kwin_x11 vt: 2
dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Laptop System: LENOVO product: 82UH v: Legion 7 16ARHA7
serial: <superuser required> Chassis: type: 10 v: Legion 7 16ARHA7
serial: <superuser required>
Mobo: LENOVO model: LNVNB161216 v: NO DPK serial: <superuser required>
UEFI: LENOVO v: K9CN34WW date: 07/22/2022
Battery:
ID-1: BAT0 charge: 101.8 Wh (100.0%) condition: 101.8/99.9 Wh (101.9%)
volts: 17.3 min: 15.5 model: Celxpert L21C4PC2 type: Li-poly
serial: <filter> status: full cycles: 8
CPU:
Info: model: AMD Ryzen 9 6900HX with Radeon Graphics bits: 64 type: MT MCP
arch: Zen 3+ gen: 4 level: v3 note: check built: 2022 process: TSMC n6 (7nm)
family: 0x19 (25) model-id: 0x44 (68) stepping: 1 microcode: 0xA404102
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: 1619 high: 3300 min/max: 1600/4934 boost: enabled
scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 1719 2: 3300
3: 1357 4: 1455 5: 1600 6: 1600 7: 1337 8: 1600 9: 1594 10: 1600 11: 1362
12: 1503 13: 1358 14: 1600 15: 1463 16: 1462 bogomips: 105453
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT]
vendor: Lenovo driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x
process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s
lanes: 16 ports: active: eDP-1 empty: DP-1,DP-2,HDMI-A-1 bus-ID: 03:00.0
chip-ID: 1002:73df class-ID: 0300
Device-2: AMD Rembrandt [Radeon 680M] vendor: Lenovo driver: amdgpu
v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm) built: 2020-22
pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: none empty: DP-3,
DP-4, DP-5, DP-6, DP-7, DP-8 bus-ID: 37:00.0 chip-ID: 1002:1681
class-ID: 0300 temp: 39.0 C
Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.2.0
compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting,radeon
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1200 s-dpi: 96 s-size: 507x317mm (19.96x12.48")
s-diag: 598mm (23.54")
Monitor-1: eDP-1 mapped: eDP model: BOE Display 0x0a9b built: 2020
res: 1920x1200 hz: 165 dpi: 142 gamma: 1.2 size: 344x215mm (13.54x8.46")
diag: 406mm (16") ratio: 16:10 modes: max: 2560x1600 min: 640x480
API: OpenGL v: 4.6 Mesa 23.1.7-arch1.1 renderer: AMD Radeon RX 6800M
(navi22 LLVM 16.0.6 DRM 3.49 6.1.53-1-lts) direct-render: Yes
Audio:
Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 03:00.1 chip-ID: 1002:ab28
class-ID: 0403
Device-2: AMD Rembrandt Radeon High Definition Audio vendor: Lenovo
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 37:00.1 chip-ID: 1002:1640 class-ID: 0403
Device-3: AMD Family 17h/19h HD Audio vendor: Lenovo driver: snd_hda_intel
v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 37:00.6
chip-ID: 1022:15e3 class-ID: 0403
Device-4: JMTek LLC. USB PnP Audio Device
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 3-2.2:5 chip-ID: 0c76:161f class-ID: 0300
API: ALSA v: k6.1.53-1-lts status: kernel-api tools: N/A
Server-1: PipeWire v: 0.3.80 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 MT7922 802.11ax PCI Express Wireless Network Adapter
vendor: Lenovo driver: mt7921e v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1
bus-ID: 05:00.0 chip-ID: 14c3:0616 class-ID: 0280
IF: wlp5s0 state: up mac: <filter>
Device-2: Realtek RTL8125 2.5GbE vendor: Lenovo driver: r8169 v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: 4000 bus-ID: 06:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp6s0 state: down mac: <filter>
Bluetooth:
Device-1: Foxconn / Hon Hai Wireless_Device driver: btusb v: 0.8 type: USB
rev: 2.1 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-3:3 chip-ID: 0489:e0d8
class-ID: e001 serial: <filter>
Report: btmgmt ID: hci0 rfk-id: 2 state: down bt-service: enabled,running
rfk-block: hardware: no software: no address: <filter> bt-v: 5.2 lmp-v: 11
status: discoverable: no pairing: no
Drives:
Local Storage: total: 3.66 TiB used: 703.21 GiB (18.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:3 vendor: Samsung
model: SSD 970 EVO Plus 2TB size: 1.82 TiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 2B2QEXM7 temp: 41.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Samsung
model: MZVL21T0HCLR-00BL2 size: 953.87 GiB block-size: physical: 512 B
logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: CL1QGXA7 temp: 41.9 C scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: Toshiba model: MQ01ABD100
size: 931.51 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 3.0 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: HDD rpm: 5400
serial: <filter> fw-rev: 0404 scheme: GPT
Partition:
ID-1: / raw-size: 953.57 GiB size: 953.57 GiB (100.00%)
used: 703.16 GiB (73.7%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 57.9 MiB (19.3%) fs: vfat dev: /dev/nvme1n1p1 maj-min: 259:1
ID-3: /home raw-size: 953.57 GiB size: 953.57 GiB (100.00%)
used: 703.16 GiB (73.7%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 953.57 GiB size: 953.57 GiB (100.00%)
used: 703.16 GiB (73.7%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 953.57 GiB size: 953.57 GiB (100.00%)
used: 703.16 GiB (73.7%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 30.55 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 16 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 45.4 C mobo: N/A
Fan Speeds (rpm): N/A
GPU: device: amdgpu temp: 41.0 C mem: 40.0 C fan: 0 watts: 11.00
device: amdgpu temp: 41.0 C
Info:
Processes: 380 Uptime: 8m wakeups: 2 Memory: total: 32 GiB note: est.
available: 30.55 GiB used: 3.06 GiB (10.0%) Init: systemd v: 254
default: graphical tool: systemctl Compilers: gcc: 13.2.1 Packages: 1350
pm: pacman pkgs: 1331 libs: 353 tools: octopi,paru pm: flatpak pkgs: 19
Shell: fish v: 3.6.1 default: Bash v: 5.1.16 running-in: konsole
inxi: 3.3.29
Garuda (2.6.16-1):
System install date:     2023-09-03
Last full system update: 2023-09-20
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       Probably (Run as root to verify)
Failed units:

So I guess it is the zen-kernel problem, isn’t it? Should I write a bug-report or something?

If you want to submit a bug report, you should first test if the issue is reproducible on the “regular” (not Zen) kernel.

sudo pacman -S linux

If so, it’s probably a general kernel bug and not an issue related to the Zen kernel.

Test also if the issue remains on the mainline kernel.

sudo pacman -S linux-mainline

No problem on the mainline kernel would suggest the issue has already been fixed by the kernel devs, and when the kernel gets the update with the patch you’ll be all set.

Before submitting a kernel bug report, you should read through the relevant document here: Reporting bugs — The Linux Kernel documentation.

If after reading through that document you decide you would like to get involved, go ahead and get started here for a general kernel bug: https://bugzilla.kernel.org/ or here for issues related specifically to the Zen kernel: Issues · zen-kernel/zen-kernel · GitHub

5 Likes

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