Monitor resolution stuck

JvpL · 2025-07-07 19:36:42

I've updated my system and now the screen is stuck at the wrong resolution and refresh rate. Here's the log file:

[2025-07-07T20:21:27+0330] [ALPM] upgraded btop (1.4.3-3 -> 1.4.4-1)
[2025-07-07T20:21:27+0330] [ALPM] upgraded hyprutils (0.8.0-1 -> 0.8.1-1)
[2025-07-07T20:21:29+0330] [ALPM] upgraded linux (6.15.4.arch2-1 -> 6.15.5.arch1-1)
[2025-07-07T20:21:29+0330] [ALPM] transaction completed

I was using hyprland and so I tried kde but that had the same issue and I already tried to edit the dot files without any success.

I'm guessing it's a kurnal issue because it seems the system isn't recognizing my monitor the way it should.

seth · 2025-07-07 19:44:32

kurnal

https://en.wikipedia.org/wiki/Kernel - were do people get these crazy spellings?

Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

but most likely you're somehow left w/ the simpledrm device.

JvpL · 2025-07-07 20:06:18

Silly me. I'm sorry.
here you are:
Jul 07 23:30:58 ArchMachine kwin_wayland[631]: kwin_wayland_drm: Failed to create framebuffer: Invalid argument
...
Jul 07 23:30:58 ArchMachine kwin_wayland[631]: kwin_wayland_drm: Failed to create framebuffer: Invalid argument
Jul 07 23:30:59 ArchMachine kwin_wayland[631]: kwin_wayland_drm: Failed to create framebuffer: Invalid argument
Jul 07 23:31:03 ArchMachine systemd[1]: tmp-grub\x2dbtrfs.FaOONOtLqC.mount: Deactivated successfully.
Jul 07 23:31:03 ArchMachine grub-btrfsd[2507]: Grub menu recreated
Jul 07 23:31:13 ArchMachine sudo[2511]: jvpl : TTY=pts/1 ; PWD=/home/jvpl ; USER=root ; COMMAND=/usr/bin/journalctl -b
Jul 07 23:31:13 ArchMachine sudo[2511]: pam_unix(sudo:session): session opened for user root(uid=0) by jvpl(uid=1000)

It's the same error over and over.

seth · 2025-07-07 20:12:05

Which indicates a problem but nothing else.

seth wrote:

Please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st

JvpL · 2025-07-07 20:23:46

My internet is really bad. I think it's not working.

curl: (56) Recv failure: Connection reset by peer

seth · 2025-07-07 20:25:07

sudo journalctl -b | wc -l

JvpL · 2025-07-07 20:26:23

116158

seth · 2025-07-07 20:31:33

That's quite a bit, reboot, check again (should be much less)
If you still struggle w/ the upload

sudo journalctl -b > /tmp/journal.txt
sudo cmod ugo+r /tmp/journal.txt
zstd /tmp/journal.txt
du -hs /tmp/journal.txt.zst
cat /tmp/journal.txt.zst | curl -F 'file=@-' 0x0.st

JvpL · 2025-07-07 20:43:45

http://0x0.st/8GV-.bin

seth · 2025-07-07 20:53:41

Jul 08 00:11:07 ArchMachine kernel: simple-framebuffer simple-framebuffer.0: [drm] Registered 1 planes with drm panic
Jul 08 00:11:07 ArchMachine kernel: [drm] Initialized simpledrm 1.0.0 for simple-framebuffer.0 on minor 0
Jul 08 00:11:07 ArchMachine kernel: simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device
Jul 08 00:11:07 ArchMachine systemd[1]: Starting Load Kernel Module drm...
Jul 08 00:11:07 ArchMachine systemd[1]: modprobe@drm.service: Deactivated successfully.
Jul 08 00:11:07 ArchMachine systemd[1]: Finished Load Kernel Module drm.
Jul 08 00:11:21 ArchMachine kwin_wayland[635]: No backend specified, automatically choosing drm
Jul 08 00:11:22 ArchMachine kwin_wayland[635]: kwin_wayland_drm: Could not find edid for connector DrmConnector(id=36, gpu="/dev/dri/card0", name="Unknown-1", connection="Connected", countMode=1)
Jul 08 00:11:22 ArchMachine kwin_wayland[635]: kwin_core: Failed to open drm node: ""
Jul 08 00:11:22 ArchMachine kwin_wayland[635]: kwin_scene_opengl: couldn't find dev node for drm device
Jul 08 00:11:22 ArchMachine kwin_wayland[635]: kwin_wayland_drm: Failed to create framebuffer: Invalid argument

Yup, you're on the simplydumb device.

Jul 08 00:11:07 ArchMachine kernel: pci 0000:01:00.0: [10de:1080] type 00 class 0x030000 PCIe Endpoint

There's an nvidia GPU but neither nvidia nor nouveau are loaded.
nvidia-utils will likely blacklist nouveau, the pascal chip should™ be supported by the nvidia package.

pacman -Qs nvidia

JvpL · 2025-07-08 09:33:43

local/libvdpau 1.5-3
Nvidia VDPAU library
local/linux-firmware-nvidia 20250627-1
Firmware files for Linux - Firmware for NVIDIA GPUs and SoCs
local/nvtop 3.2.0-1
GPUs process monitoring for AMD, Intel and NVIDIA
local/vulkan-nouveau 1:25.1.5-1
Open-source Vulkan driver for Nvidia GPUs
local/xf86-video-nouveau 1.0.18-1 (xorg-drivers)
Open Source 3D acceleration driver for nVidia cards

My gpu is a gtx 580 and nvidia drivers don't work. Before the update mesa was working fine. I've also realized the GL_RENDERER has changed from NVC8 into llvmpipe (LLVM 20.1.7, 256 bits).

Last edited by JvpL (2025-07-08 10:44:55)

seth · 2025-07-08 14:51:30

My gpu is a gtx 580 and nvidia drivers don't work.

Sure?

Jul 08 00:11:07 ArchMachine kernel: pci 0000:01:00.0: [10de:1080] type 00 class 0x030000 PCIe Endpoint

https://linux-hardware.org/?id=pci:10de-1b80-3842-6286

Either way, nouveau isn't loaded (and it's not because nvidia-utils is installed)

modprobe -c | grep -v alias | grep nouveau

Arch Linux

#1 2025-07-07 19:36:42

Monitor resolution stuck

#2 2025-07-07 19:44:32

Re: Monitor resolution stuck

#3 2025-07-07 20:06:18

Re: Monitor resolution stuck

#4 2025-07-07 20:12:05

Re: Monitor resolution stuck

#5 2025-07-07 20:23:46

Re: Monitor resolution stuck

#6 2025-07-07 20:25:07

Re: Monitor resolution stuck

#7 2025-07-07 20:26:23

Re: Monitor resolution stuck

#8 2025-07-07 20:31:33

Re: Monitor resolution stuck

#9 2025-07-07 20:43:45

Re: Monitor resolution stuck

#10 2025-07-07 20:53:41

Re: Monitor resolution stuck

#11 2025-07-08 09:33:43

Re: Monitor resolution stuck

#12 2025-07-08 14:51:30

Re: Monitor resolution stuck

Board footer