[SOLVED] Drive information shown after login instead of desktop

arthu · 2024-04-17 15:14:03

Hello, I've been having this issue where when I boot my PC, this information about my /dev/sda2 drive shows up, which by itself isn't unusual. However, when I eventually get to the KDE login screen and log in, the screen returns and doesn't go away until I long-press the power button to shut off the machine. The issue goes away on reboot but returns after shutting the PC down and leaving it turned off for a while, then booting it back up.

Image

Mod note: Replaced oversized image with link.

Last edited by arthu (2024-04-17 17:02:35)

seth · 2024-04-17 15:50:23

Please remove the oversized image

However, when I eventually get to the KDE login screen and log in, the screen returns and doesn't go away until I long-press the power button to shut off the machine.

1. Have you tried to just switch the VT forth and back (ctrl+alt+F1,F2,F3,…)
2. Are you trying to log into KDE/wayland (now the default) or X11 - does it matter?
3. Under no circumstances push the power button, you drop every journal that could provide further hints if the above doesn't help - https://wiki.archlinux.org/title/Keyboa … el_(SysRq)

arthu · 2024-04-17 16:03:19

1. I have, same screen on every tty
2. I was trying to log in to Wayland, the issue doesn't seem to happen on X11
3. I guess I could try enabling ssh and getting the journal through that before powering it off.

arthu · 2024-04-17 16:15:10

Here's the journal: https://0x0.st/XoHH.txt

seth · 2024-04-17 16:26:13

Apr 17 18:10:22 archlinux kernel: [drm] Initialized simpledrm 1.0.0 20200625 for simple-framebuffer.0 on minor 0
Apr 17 18:10:22 archlinux kernel: simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device

Apr 17 18:10:25 archlinux kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000700] Failed to apply atomic modeset.  Error code: -22
Apr 17 18:10:25 archlinux kernel: nvidia 0000:07:00.0: [drm] fb0: nvidia-drmdrmfb frame buffer device
Apr 17 18:10:25 archlinux kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000700] Failed to apply atomic modeset.  Error code: -22
Apr 17 18:10:28 archlinux kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000700] Flip event timeout on head 0
Apr 17 18:10:31 archlinux kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000700] Flip event timeout on head 1
Apr 17 18:10:34 archlinux kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000700] Flip event timeout on head 2
Apr 17 18:10:34 archlinux kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000700] Failed to apply atomic modeset.  Error code: -22
Apr 17 18:10:38 archlinux kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000700] Flip event timeout on head 0
Apr 17 18:10:41 archlinux kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000700] Flip event timeout on head 1
Apr 17 18:10:44 archlinux kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000700] Flip event timeout on head 2
Apr 17 18:10:44 archlinux kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000700] Failed to apply atomic modeset.  Error code: -22
Apr 17 18:10:47 archlinux kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000700] Flip event timeout on head 0
Apr 17 18:10:50 archlinux kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000700] Flip event timeout on head 1
Apr 17 18:10:53 archlinux kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000700] Flip event timeout on head 2
Apr 17 18:10:53 archlinux kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000700] Failed to apply atomic modeset.  Error code: -22

Enable https://wiki.archlinux.org/title/NVIDIA … de_setting - use the "nvidia_drm.modeset=1" kernel parameter (modprobe.conf won't do!), the reports on nvidia_drm.fbdev=1 are currently inconclusive, it might or not benefit you.

arthu · 2024-04-17 16:36:28

As far as I know, it is already enabled. I have a file called /etc/modprobe.d/nvidia.conf with this content:

options nvidia_drm modeset=1 fbdev=1

cat /sys/module/nvidia_drm/parameters/modeset also returns Y.

seth · 2024-04-17 16:48:00

Remove "fbdev=1" and add the kernel parameter.
1. "reports on nvidia_drm.fbdev=1 are currently inconclusive"
2. We want to make the simpledrm device go away (and w/o fbdev=1 nvidia_drm will not even be able to replace the device but just run next to it) - the kernel parameter (NOT the module option!) acts as a hack-indicator to please not use that thing itfp because it causes trouble w/ the nvidia driver)

Fwwi, w/o modeset=1 wayland wouldn't start at all.

arthu · 2024-04-17 17:02:21

Thank you, that seems to have done the trick!
I've added nvidia_drm.modeset=1 to the GRUB_CMDLINE_LINUX_DEFAULT line in my grub config and now it seems to consistently boot ordinarily.

Arch Linux

#1 2024-04-17 15:14:03

[SOLVED] Drive information shown after login instead of desktop

#2 2024-04-17 15:50:23

Re: [SOLVED] Drive information shown after login instead of desktop

#3 2024-04-17 16:03:19

Re: [SOLVED] Drive information shown after login instead of desktop

#4 2024-04-17 16:15:10

Re: [SOLVED] Drive information shown after login instead of desktop

#5 2024-04-17 16:26:13

Re: [SOLVED] Drive information shown after login instead of desktop

#6 2024-04-17 16:36:28

Re: [SOLVED] Drive information shown after login instead of desktop

#7 2024-04-17 16:48:00

Re: [SOLVED] Drive information shown after login instead of desktop

#8 2024-04-17 17:02:21

Re: [SOLVED] Drive information shown after login instead of desktop

Board footer