Arch Linux

archsoft

Member

Registered: 2022-05-10

Posts: 3

Re: mesa problem

Solved and successfully running mesa 1:23.3.2-1 on Thinkpad T480 with i5-8250U CPU (CPU Gen 8, GPU Gen 9).

I switched Xorg driver from "intel" to "modesetting". However, the wrong AccelMethod gave me more segfaults.

Small howto switch to modesetting

My very old config was:

xf86-video-intel package for GPU, libva-intel-driver package for Hardware video acceleration.

/etc/X11/xorg.conf.d/20-intel.conf

Section "Device"
   Identifier "Intel Graphics"
   Driver "intel"
   Option "AccelMethod" "sna"
EndSection

New config:

Removed xf86-video-intel package, removed libva-intel-driver package, added intel-media-driver package for Hardware video acceleration.

For hardware video acceleration support it was also necessary to use the following module parameters in /etc/modprobe.d/i915.conf

options i915 enable_guc=2

/etc/X11/xorg.conf.d/20-intel.conf

Section "Device"
   Identifier "Intel Graphics"
   Driver "modesetting"
   Option "AccelMethod" "glamor"
   Option "DRI" "iris"
EndSection

In my case, AccelMethod "glamor" was important (and is default). With AccelMethod "sna" Xorg segfaults furthermore:

[    20.115] (EE) Backtrace:
[    20.115] (EE) 0: /usr/lib/Xorg (xorg_backtrace+0x2dd) [0x55f2a188cc5d]
[    20.115] (EE) 1: /usr/lib/libc.so.6 (__sigaction+0x50) [0x7f37ea1ec710]
[    20.115] (EE) 2: ? (?+0x0) [0x55f2a21c2a10]
[    20.115] (EE) 
[    20.116] (EE) Segmentation fault at address 0x55f2a21c2a10
[    20.116] (EE) 
Fatal server error:
[    20.116] (EE) Caught signal 11 (Segmentation fault). Server aborting

Sources

https://wiki.archlinux.org/title/intel_graphics
https://wiki.archlinux.org/title/Hardwa … celeration

Scimmia

Fellow

Registered: 2012-09-01

Posts: 11,654

Re: mesa problem

Or just delete 20-intel.conf and you would have been fine without all of that other stuff.

xyrgug

Member

Registered: 2023-12-15

Posts: 32

Re: mesa problem

I've read this.
https://wiki.archlinux.org/title/NVIDIA … de_setting

Could you please tell me if I did it right?

So in /etc/modprobe.d/ I created nvidia.conf
Put this two lines there:

nvidia_drm.modeset=1
nvidia_drm.fbdev=1

Then

mkinitcpio -p linux

Scimmia

Fellow

Registered: 2012-09-01

Posts: 11,654

Re: mesa problem

No. nvidia_drm.modeset=1 on the kernel command line.

samox86

Member

From: Slovakia

Registered: 2007-02-17

Posts: 5

Website

Re: mesa problem

Not sure if this can help, but I face the same problem on KVM VM.

- no specific parameter in kernel line, VM video type='vga'.
- PC is using i7-13700 igpu.
- mesa package version 1:23.3.2-1
- hypervisor is running archlinux too

Fixed by switching to mesa-amber.
I am guessing that this is just a temporary fix till mesa-amber will get the same update. Am I right?
Thanks

loqs

Member

Registered: 2014-03-06

Posts: 17,603

Re: mesa problem

Fixed by switching to mesa-amber.
I am guessing that this is just a temporary fix till mesa-amber will get the same update. Am I right?
Thanks

https://gitlab.archlinux.org/archlinux/ … 1108361f65
https://gitlab.archlinux.org/archlinux/ … -/issues/5
https://gitlab.freedesktop.org/mesa/mesa/-/issues/10371

xyrgug

Member

Registered: 2023-12-15

Posts: 32

Re: mesa problem

No. nvidia_drm.modeset=1 on the kernel command line.

You mean I need add nvidia_drm.modeset=1 to /etc/default/grub like this, right?

GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet nvidia_drm.modeset=1"

archlinux20130905

Member

Registered: 2013-09-05

Posts: 45

Re: mesa problem

mesa has now been updated to "mesa 1:23.3.2-2"

I just downgraded and blacklisted it after trying it out:

[2024-01-01T20:33:33+0100] [ALPM] transaction started
[2024-01-01T20:33:33+0100] [ALPM] downgraded mesa (1:23.3.2-2 -> 1:23.3.2-1)
[2024-01-01T20:33:33+0100] [ALPM] transaction completed

After the update I suddenly detected the following problems:

Jan 01 20:23:12 <hostname> kernel: nvidia: loading out-of-tree module taints kernel.
Jan 01 20:23:12 <hostname> kernel: nvidia: module license 'NVIDIA' taints kernel.
Jan 01 20:23:12 <hostname> kernel: Disabling lock debugging due to kernel taint
Jan 01 20:23:12 <hostname> kernel: nvidia: module license taints kernel.
Jan 01 20:23:13 <hostname> kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  545.29.06  Thu Nov 16 01:59:08 UTC 2023
Jan 01 20:23:13 <hostname> (udev-worker)[345]: nvidia: Process '/usr/bin/bash -c '/usr/bin/mknod -Z -m 666 /dev/nvidiactl c $(grep nvidia-frontend /proc/devices | cut -d \  -f 1) 255'' failed with exit code 1.
Jan 01 20:23:13 <hostname> kernel: nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint.
Jan 01 20:23:13 <hostname> (udev-worker)[351]: nvidia: Process '/usr/bin/bash -c '/usr/bin/mknod -Z -m 666 /dev/nvidiactl c $(grep nvidia-frontend /proc/devices | cut -d \  -f 1) 255'' failed with exit code 1.
Jan 01 20:23:13 <hostname> (udev-worker)[351]: nvidia: Process '/usr/bin/bash -c 'for i in $(cat /proc/driver/nvidia/gpus/*/information | grep Minor | cut -d \  -f 4); do /usr/bin/mknod -Z -m 666 /dev/nvidia${i} c $(grep nvidia-frontend /proc/devices | cut -d \  -f 1) ${i}; done'' failed with exit code 1.
Jan 01 20:23:13 <hostname> (udev-worker)[345]: nvidia: Process '/usr/bin/bash -c 'for i in $(cat /proc/driver/nvidia/gpus/*/information | grep Minor | cut -d \  -f 4); do /usr/bin/mknod -Z -m 666 /dev/nvidia${i} c $(grep nvidia-frontend /proc/devices | cut -d \  -f 1) ${i}; done'' failed with exit code 1.
Jan 01 20:23:13 <hostname> (udev-worker)[351]: nvidia_modeset: Process '/usr/bin/bash -c '/usr/bin/mknod -Z -m 666 /dev/nvidia-modeset c $(grep nvidia-frontend /proc/devices | cut -d \  -f 1) 254'' failed with exit code 1.
Jan 01 20:23:14 <hostname> kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset.  Error code: -22
Jan 01 20:23:14 <hostname> kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset.  Error code: -22
Jan 01 20:23:17 <hostname> kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
Jan 01 20:23:17 <hostname> kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset.  Error code: -22
Jan 01 20:23:17 <hostname> kernel: Xorg[597]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
Jan 01 20:23:18 <hostname> lightdm[590]: display_manager_add_seat: assertion '!priv->stopping' failed
Jan 01 20:23:18 <hostname> systemd[1]: lightdm.service: Failed with result 'exit-code'.
Jan 01 20:23:22 <hostname> kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
Jan 01 20:23:22 <hostname> kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset.  Error code: -22
Jan 01 20:23:25 <hostname> kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
Jan 01 20:23:25 <hostname> kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset.  Error code: -22
Jan 01 20:23:28 <hostname> kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
Jan 01 20:23:28 <hostname> kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset.  Error code: -22
Jan 01 20:23:31 <hostname> kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
Jan 01 20:23:31 <hostname> kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset.  Error code: -22

This broke my tty-consoles. I couldn't switch from the GUI to tty using Ctrl+Alt+F<Number>. After the switch I only saw the usual one-line-report, which always indicates the state of my system's filesystem but no standard interactive text-only-login-prompt. I tried all tty-consoles. They all showed the same one-line-filesystem-report, nothing more. The tty-consoles didn't respond to any key-presses. After the downgrade all of these problems and the errors in the log disappeared. However this mesa-update did not seem to break Xorg:

[    16.189] 
X.Org X Server 1.21.1.10
X Protocol Version 11, Revision 0
[    16.189] Current Operating System: Linux <hostname> 6.6.8-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 21 Dec 2023 19:01:01 +0000 x86_64
[    16.189] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=<uuid> rw audit=1 lsm=landlock,lockdown,yama,apparmor,bpf loglevel=3 quiet libata.noacpi=1
[    16.189]  
[    16.189] Current version of pixman: 0.42.2
[    16.189] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[    16.189] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    16.189] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jan  1 20:23:25 2024
[    16.189] (==) Using config directory: "/etc/X11/xorg.conf.d"
[    16.189] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    16.189] (==) No Layout section.  Using the first Screen section.
[    16.189] (==) No screen section available. Using defaults.
[    16.189] (**) |-->Screen "Default Screen Section" (0)
[    16.189] (**) |   |-->Monitor "<default monitor>"
[    16.189] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[    16.189] (==) Automatically adding devices
[    16.189] (==) Automatically enabling devices
[    16.190] (==) Automatically adding GPU devices
[    16.190] (==) Automatically binding GPU devices
[    16.190] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    16.190] (==) FontPath set to:
	/usr/share/fonts/misc,
	/usr/share/fonts/TTF,
	/usr/share/fonts/OTF,
	/usr/share/fonts/Type1,
	/usr/share/fonts/100dpi,
	/usr/share/fonts/75dpi
[    16.190] (==) ModulePath set to "/usr/lib/xorg/modules"
[    16.190] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[    16.190] (II) Module ABI versions:
[    16.190] 	X.Org ANSI C Emulation: 0.4
[    16.190] 	X.Org Video Driver: 25.2
[    16.190] 	X.Org XInput driver : 24.4
[    16.190] 	X.Org Server Extension : 10.0
[    16.190] (++) using VT number 7

[    16.190] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[    16.191] (II) xfree86: Adding drm device (/dev/dri/card1)
[    16.191] (II) Platform probe for /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card1
[    22.585] (**) OutputClass "nvidia" ModulePath extended to "/usr/lib/nvidia/xorg,/usr/lib/xorg/modules,/usr/lib/xorg/modules"
[    22.586] (--) PCI:*(1@0:0:0) 10de:17c8:1462:3233 rev 161, Mem @ 0xde000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/131072
[    22.586] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[    22.586] (II) LoadModule: "glx"
[    22.586] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    22.587] (II) Module glx: vendor="X.Org Foundation"
[    22.587] 	compiled for 1.21.1.10, module version = 1.0.0
[    22.587] 	ABI class: X.Org Server Extension, version 10.0
[    22.587] (II) Applying OutputClass "nvidia" to /dev/dri/card1
[    22.587] 	loading driver: nvidia
[    22.587] (==) Matched nvidia as autoconfigured driver 0
[    22.587] (==) Matched nouveau as autoconfigured driver 1
[    22.587] (==) Matched nv as autoconfigured driver 2
[    22.587] (==) Matched modesetting as autoconfigured driver 3
[    22.587] (==) Matched fbdev as autoconfigured driver 4
[    22.587] (==) Matched vesa as autoconfigured driver 5
[    22.587] (==) Assigned the driver to the xf86ConfigLayout
[    22.587] (II) LoadModule: "nvidia"
[    22.588] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[    22.588] (II) Module nvidia: vendor="NVIDIA Corporation"
[    22.588] 	compiled for 1.6.99.901, module version = 1.0.0
[    22.588] 	Module class: X.Org Video Driver
[    22.588] (II) LoadModule: "nouveau"
[    22.588] (WW) Warning, couldn't open module nouveau
[    22.588] (EE) Failed to load module "nouveau" (module does not exist, 0)
[    22.588] (II) LoadModule: "nv"
[    22.588] (WW) Warning, couldn't open module nv
[    22.588] (EE) Failed to load module "nv" (module does not exist, 0)
[    22.588] (II) LoadModule: "modesetting"
[    22.588] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[    22.589] (II) Module modesetting: vendor="X.Org Foundation"
[    22.589] 	compiled for 1.21.1.10, module version = 1.21.1
[    22.589] 	Module class: X.Org Video Driver
[    22.589] 	ABI class: X.Org Video Driver, version 25.2
[    22.589] (II) LoadModule: "fbdev"
[    22.589] (WW) Warning, couldn't open module fbdev
[    22.589] (EE) Failed to load module "fbdev" (module does not exist, 0)
[    22.589] (II) LoadModule: "vesa"
[    22.589] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[    22.589] (II) Module vesa: vendor="X.Org Foundation"
[    22.589] 	compiled for 1.21.1.4, module version = 2.6.0
[    22.589] 	Module class: X.Org Video Driver
[    22.589] 	ABI class: X.Org Video Driver, version 25.2
[    22.589] (II) NVIDIA dlloader X Driver  545.29.06  Thu Nov 16 01:52:34 UTC 2023
[    22.589] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[    22.589] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    22.589] (II) VESA: driver for VESA chipsets: vesa
[    22.589] (II) Loading sub module "fb"
[    22.589] (II) LoadModule: "fb"
[    22.589] (II) Module "fb" already built-in
[    22.589] (II) Loading sub module "wfb"
[    22.589] (II) LoadModule: "wfb"
[    22.589] (II) Loading /usr/lib/xorg/modules/libwfb.so
[    22.590] (II) Module wfb: vendor="X.Org Foundation"
[    22.590] 	compiled for 1.21.1.10, module version = 1.0.0
[    22.590] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    22.590] (WW) Falling back to old probe method for modesetting
[    22.590] (EE) open /dev/dri/card0: No such file or directory
[    22.590] (II) NVIDIA(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[    22.590] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[    22.590] (==) NVIDIA(0): RGB weight 888
[    22.590] (==) NVIDIA(0): Default visual is TrueColor
[    22.590] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[    22.590] (II) Applying OutputClass "nvidia" options to /dev/dri/card1
[    22.590] (**) NVIDIA(0): Option "AllowEmptyInitialConfiguration"
[    22.590] (**) NVIDIA(0): Enabling 2D acceleration
[    22.590] (II) Loading sub module "glxserver_nvidia"
[    22.590] (II) LoadModule: "glxserver_nvidia"
[    22.590] (II) Loading /usr/lib/nvidia/xorg/libglxserver_nvidia.so
[    22.600] (II) Module glxserver_nvidia: vendor="NVIDIA Corporation"
[    22.600] 	compiled for 1.6.99.901, module version = 1.0.0
[    22.600] 	Module class: X.Org Server Extension
[    22.600] (II) NVIDIA GLX Module  545.29.06  Thu Nov 16 01:55:23 UTC 2023
[    22.600] (II) NVIDIA: The X server supports PRIME Render Offload.
[    22.601] (--) NVIDIA(0): Valid display device(s) on GPU-0 at PCI:1:0:0
[    22.601] (--) NVIDIA(0):     CRT-0
[    22.601] (--) NVIDIA(0):     DFP-0
[    22.601] (--) NVIDIA(0):     DFP-1
[    22.601] (--) NVIDIA(0):     DFP-2
[    22.601] (--) NVIDIA(0):     DFP-3
[    22.601] (--) NVIDIA(0):     DFP-4 (boot)
[    22.601] (--) NVIDIA(0):     DFP-5
[    22.601] (--) NVIDIA(0):     DFP-6
[    22.601] (--) NVIDIA(0):     DFP-7
[    22.601] (II) NVIDIA(0): NVIDIA GPU NVIDIA GeForce GTX 980 Ti (GM200-A) at PCI:1:0:0
[    22.601] (II) NVIDIA(0):     (GPU-0)
[    22.601] (--) NVIDIA(0): Memory: 6291456 kBytes
[    22.601] (--) NVIDIA(0): VideoBIOS: 84.00.41.00.2d
[    22.601] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[    22.606] (--) NVIDIA(GPU-0): CRT-0: disconnected
[    22.606] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
[    22.606] (--) NVIDIA(GPU-0): 
[    22.610] (--) NVIDIA(GPU-0): DFP-0: disconnected
[    22.610] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[    22.610] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[    22.610] (--) NVIDIA(GPU-0): 
[    22.610] (--) NVIDIA(GPU-0): DFP-1: disconnected
[    22.610] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[    22.610] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[    22.610] (--) NVIDIA(GPU-0): 
[    22.610] (--) NVIDIA(GPU-0): DFP-2: disconnected
[    22.610] (--) NVIDIA(GPU-0): DFP-2: Internal DisplayPort
[    22.610] (--) NVIDIA(GPU-0): DFP-2: 960.0 MHz maximum pixel clock
[    22.610] (--) NVIDIA(GPU-0): 
[    22.610] (--) NVIDIA(GPU-0): DFP-3: disconnected
[    22.610] (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
[    22.610] (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock
[    22.610] (--) NVIDIA(GPU-0): 
[    22.610] (--) NVIDIA(GPU-0): Samsung U28D590 (DFP-4): connected
[    22.610] (--) NVIDIA(GPU-0): Samsung U28D590 (DFP-4): Internal DisplayPort
[    22.610] (--) NVIDIA(GPU-0): Samsung U28D590 (DFP-4): 960.0 MHz maximum pixel clock
[    22.610] (--) NVIDIA(GPU-0): 
[    22.613] (--) NVIDIA(GPU-0): DFP-5: disconnected
[    22.613] (--) NVIDIA(GPU-0): DFP-5: Internal TMDS
[    22.613] (--) NVIDIA(GPU-0): DFP-5: 165.0 MHz maximum pixel clock
[    22.613] (--) NVIDIA(GPU-0): 
[    22.613] (--) NVIDIA(GPU-0): DFP-6: disconnected
[    22.613] (--) NVIDIA(GPU-0): DFP-6: Internal DisplayPort
[    22.613] (--) NVIDIA(GPU-0): DFP-6: 960.0 MHz maximum pixel clock
[    22.613] (--) NVIDIA(GPU-0): 
[    22.613] (--) NVIDIA(GPU-0): DFP-7: disconnected
[    22.613] (--) NVIDIA(GPU-0): DFP-7: Internal TMDS
[    22.613] (--) NVIDIA(GPU-0): DFP-7: 165.0 MHz maximum pixel clock
[    22.613] (--) NVIDIA(GPU-0): 
[    22.617] (==) NVIDIA(0): 
[    22.617] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[    22.617] (==) NVIDIA(0):     will be used as the requested mode.
[    22.617] (==) NVIDIA(0): 
[    22.617] (II) NVIDIA(0): Validated MetaModes:
[    22.617] (II) NVIDIA(0):     "DFP-4:nvidia-auto-select"
[    22.617] (II) NVIDIA(0): Virtual screen size determined to be 3840 x 2160
[    22.624] (--) NVIDIA(0): DPI set to (159, 156); computed from "UseEdidDpi" X config
[    22.624] (--) NVIDIA(0):     option
[    22.624] (II) UnloadModule: "modesetting"
[    22.624] (II) Unloading modesetting
[    22.624] (II) UnloadModule: "vesa"
[    22.624] (II) Unloading vesa
[    22.625] (II) NVIDIA: Reserving 6144.00 MB of virtual memory for indirect memory
[    22.625] (II) NVIDIA:     access.
[    22.627] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[    22.627] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[    22.627] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[    22.627] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[    22.627] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[    22.627] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[    22.627] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[    22.627] (II) NVIDIA(0):     Config Options in the README.
[    22.642] (II) NVIDIA(0): Setting mode "DFP-4:nvidia-auto-select"
[    22.740] (==) NVIDIA(0): Disabling shared memory pixmaps
[    22.740] (==) NVIDIA(0): Backing store enabled
[    22.740] (==) NVIDIA(0): Silken mouse enabled
[    22.741] (==) NVIDIA(0): DPMS enabled
[    22.741] (II) Loading sub module "dri2"
[    22.741] (II) LoadModule: "dri2"
[    22.741] (II) Module "dri2" already built-in
[    22.741] (II) NVIDIA(0): [DRI2] Setup complete
[    22.741] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[    22.741] (II) Initializing extension Generic Event Extension
[    22.741] (II) Initializing extension SHAPE
[    22.741] (II) Initializing extension MIT-SHM
[    22.741] (II) Initializing extension XInputExtension
[    22.741] (II) Initializing extension XTEST
[    22.742] (II) Initializing extension BIG-REQUESTS
[    22.742] (II) Initializing extension SYNC
[    22.742] (II) Initializing extension XKEYBOARD
[    22.742] (II) Initializing extension XC-MISC
[    22.742] (II) Initializing extension SECURITY
[    22.742] (II) Initializing extension XFIXES
[    22.743] (II) Initializing extension RENDER
[    22.743] (II) Initializing extension RANDR
[    22.743] (II) Initializing extension COMPOSITE
[    22.743] (II) Initializing extension DAMAGE
[    22.743] (II) Initializing extension MIT-SCREEN-SAVER
[    22.743] (II) Initializing extension DOUBLE-BUFFER
[    22.744] (II) Initializing extension RECORD
[    22.744] (II) Initializing extension DPMS
[    22.744] (II) Initializing extension Present
[    22.744] (II) Initializing extension DRI3
[    22.744] (II) Initializing extension X-Resource
[    22.744] (II) Initializing extension XVideo
[    22.744] (II) Initializing extension XVideo-MotionCompensation
[    22.744] (II) Initializing extension GLX
[    22.745] (II) Initializing extension GLX
[    22.745] (II) Indirect GLX disabled.
[    22.745] (II) GLX: Another vendor is already registered for screen 0
[    22.745] (II) Initializing extension XFree86-VidModeExtension
[    22.745] (II) Initializing extension XFree86-DGA
[    22.745] (II) Initializing extension XFree86-DRI
[    22.745] (II) Initializing extension DRI2
[    22.745] (II) Initializing extension NV-GLX
[    22.745] (II) Initializing extension NV-CONTROL
[    22.745] (II) Initializing extension XINERAMA
[    22.830] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[    22.830] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[    22.830] (**) Power Button: Applying InputClass "system-keyboard"
[    22.830] (II) LoadModule: "libinput"
[    22.830] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[    22.831] (II) Module libinput: vendor="X.Org Foundation"
[    22.831] 	compiled for 1.21.1.8, module version = 1.4.0
[    22.831] 	Module class: X.Org XInput Driver
[    22.831] 	ABI class: X.Org XInput driver, version 24.4
[    22.831] (II) Using input driver 'libinput' for 'Power Button'
[    22.831] (**) Power Button: always reports core events
[    22.831] (**) Option "Device" "/dev/input/event2"
[    22.833] (II) event2  - Power Button: is tagged by udev as: Keyboard
[    22.833] (II) event2  - Power Button: device is a keyboard
[    22.833] (II) event2  - Power Button: device removed
[    22.873] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
[    22.873] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[    22.873] (**) Option "xkb_layout" "de"
[    22.889] (II) event2  - Power Button: is tagged by udev as: Keyboard
[    22.889] (II) event2  - Power Button: device is a keyboard
[    22.889] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[    22.889] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[    22.889] (**) Power Button: Applying InputClass "system-keyboard"
[    22.889] (II) Using input driver 'libinput' for 'Power Button'
[    22.889] (**) Power Button: always reports core events
[    22.889] (**) Option "Device" "/dev/input/event1"
[    22.890] (II) event1  - Power Button: is tagged by udev as: Keyboard
[    22.890] (II) event1  - Power Button: device is a keyboard
[    22.891] (II) event1  - Power Button: device removed
[    22.920] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1/event1"
[    22.920] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[    22.920] (**) Option "xkb_layout" "de"
[    22.922] (II) event1  - Power Button: is tagged by udev as: Keyboard
[    22.922] (II) event1  - Power Button: device is a keyboard
[    22.924] (II) config/udev: Adding input device Sleep Button (/dev/input/event0)
[    22.924] (**) Sleep Button: Applying InputClass "libinput keyboard catchall"
[    22.924] (**) Sleep Button: Applying InputClass "system-keyboard"
[    22.924] (II) Using input driver 'libinput' for 'Sleep Button'
[    22.924] (**) Sleep Button: always reports core events
[    22.924] (**) Option "Device" "/dev/input/event0"
[    22.927] (II) event0  - Sleep Button: is tagged by udev as: Keyboard
[    22.927] (II) event0  - Sleep Button: device is a keyboard
[    22.927] (II) event0  - Sleep Button: device removed
[    22.960] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0/event0"
[    22.960] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 8)
[    22.960] (**) Option "xkb_layout" "de"
[    22.964] (II) event0  - Sleep Button: is tagged by udev as: Keyboard
[    22.964] (II) event0  - Sleep Button: device is a keyboard
[    22.968] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event6)
[    22.968] (II) No input driver specified, ignoring this device.
[    22.969] (II) This device may have been added with another device file.
[    22.970] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event7)
[    22.970] (II) No input driver specified, ignoring this device.
[    22.970] (II) This device may have been added with another device file.
[    22.972] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event8)
[    22.972] (II) No input driver specified, ignoring this device.
[    22.972] (II) This device may have been added with another device file.
[    22.974] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event9)
[    22.974] (II) No input driver specified, ignoring this device.
[    22.974] (II) This device may have been added with another device file.
[    22.978] (II) config/udev: Adding input device Logitech USB Laser Mouse (/dev/input/event4)
[    22.978] (**) Logitech USB Laser Mouse: Applying InputClass "libinput pointer catchall"
[    22.978] (II) Using input driver 'libinput' for 'Logitech USB Laser Mouse'
[    22.978] (**) Logitech USB Laser Mouse: always reports core events
[    22.978] (**) Option "Device" "/dev/input/event4"
[    23.038] (II) event4  - Logitech USB Laser Mouse: is tagged by udev as: Mouse
[    23.038] (II) event4  - Logitech USB Laser Mouse: device set to 1200 DPI
[    23.039] (II) event4  - Logitech USB Laser Mouse: device is a pointer
[    23.039] (II) event4  - Logitech USB Laser Mouse: device removed
[    23.076] (II) libinput: Logitech USB Laser Mouse: Step value 0 was provided, libinput Fallback acceleration function is used.
[    23.076] (II) libinput: Logitech USB Laser Mouse: Step value 0 was provided, libinput Fallback acceleration function is used.
[    23.076] (II) libinput: Logitech USB Laser Mouse: Step value 0 was provided, libinput Fallback acceleration function is used.
[    23.076] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9:1.0/0003:046D:C062.0001/input/input4/event4"
[    23.076] (II) XINPUT: Adding extended input device "Logitech USB Laser Mouse" (type: MOUSE, id 9)
[    23.077] (**) Option "AccelerationScheme" "none"
[    23.077] (**) Logitech USB Laser Mouse: (accel) selected scheme none/0
[    23.077] (**) Logitech USB Laser Mouse: (accel) acceleration factor: 2.000
[    23.077] (**) Logitech USB Laser Mouse: (accel) acceleration threshold: 4
[    23.138] (II) event4  - Logitech USB Laser Mouse: is tagged by udev as: Mouse
[    23.138] (II) event4  - Logitech USB Laser Mouse: device set to 1200 DPI
[    23.139] (II) event4  - Logitech USB Laser Mouse: device is a pointer
[    23.142] (II) config/udev: Adding input device Logitech USB Laser Mouse (/dev/input/mouse0)
[    23.142] (II) No input driver specified, ignoring this device.
[    23.143] (II) This device may have been added with another device file.
[    23.144] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event10)
[    23.144] (II) No input driver specified, ignoring this device.
[    23.144] (II) This device may have been added with another device file.
[    23.146] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event11)
[    23.146] (II) No input driver specified, ignoring this device.
[    23.146] (II) This device may have been added with another device file.
[    23.148] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event12)
[    23.148] (II) No input driver specified, ignoring this device.
[    23.148] (II) This device may have been added with another device file.
[    23.150] (II) config/udev: Adding input device HDA Intel PCH Line Out Front (/dev/input/event13)
[    23.150] (II) No input driver specified, ignoring this device.
[    23.150] (II) This device may have been added with another device file.
[    23.151] (II) config/udev: Adding input device HDA Intel PCH Line Out Surround (/dev/input/event14)
[    23.151] (II) No input driver specified, ignoring this device.
[    23.151] (II) This device may have been added with another device file.
[    23.153] (II) config/udev: Adding input device HDA Intel PCH Line Out CLFE (/dev/input/event15)
[    23.153] (II) No input driver specified, ignoring this device.
[    23.153] (II) This device may have been added with another device file.
[    23.155] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event16)
[    23.155] (II) No input driver specified, ignoring this device.
[    23.155] (II) This device may have been added with another device file.
[    23.157] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event3)
[    23.157] (**) AT Translated Set 2 keyboard: Applying InputClass "libinput keyboard catchall"
[    23.157] (**) AT Translated Set 2 keyboard: Applying InputClass "system-keyboard"
[    23.157] (II) Using input driver 'libinput' for 'AT Translated Set 2 keyboard'
[    23.157] (**) AT Translated Set 2 keyboard: always reports core events
[    23.157] (**) Option "Device" "/dev/input/event3"
[    23.161] (II) event3  - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard
[    23.162] (II) event3  - AT Translated Set 2 keyboard: device is a keyboard
[    23.163] (II) event3  - AT Translated Set 2 keyboard: device removed
[    23.190] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input3/event3"
[    23.190] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 10)
[    23.190] (**) Option "xkb_layout" "de"
[    23.194] (II) event3  - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard
[    23.194] (II) event3  - AT Translated Set 2 keyboard: device is a keyboard
[    23.198] (II) config/udev: Adding input device PC Speaker (/dev/input/event5)
[    23.198] (II) No input driver specified, ignoring this device.
[    23.198] (II) This device may have been added with another device file.
[    31.032] (II) event2  - Power Button: device removed
[    31.046] (II) event1  - Power Button: device removed
[    31.063] (II) event0  - Sleep Button: device removed
[    31.080] (II) event4  - Logitech USB Laser Mouse: device removed
[    31.114] (II) event3  - AT Translated Set 2 keyboard: device removed
[    41.764] (--) NVIDIA(GPU-0): CRT-0: disconnected
[    41.764] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
[    41.764] (--) NVIDIA(GPU-0): 
[    41.769] (--) NVIDIA(GPU-0): DFP-0: disconnected
[    41.769] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[    41.769] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[    41.769] (--) NVIDIA(GPU-0): 
[    41.769] (--) NVIDIA(GPU-0): DFP-1: disconnected
[    41.769] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[    41.769] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[    41.769] (--) NVIDIA(GPU-0): 
[    41.770] (--) NVIDIA(GPU-0): DFP-2: disconnected
[    41.770] (--) NVIDIA(GPU-0): DFP-2: Internal DisplayPort
[    41.770] (--) NVIDIA(GPU-0): DFP-2: 960.0 MHz maximum pixel clock
[    41.770] (--) NVIDIA(GPU-0): 
[    41.770] (--) NVIDIA(GPU-0): DFP-3: disconnected
[    41.770] (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
[    41.770] (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock
[    41.770] (--) NVIDIA(GPU-0): 
[    41.771] (--) NVIDIA(GPU-0): Samsung U28D590 (DFP-4): connected
[    41.771] (--) NVIDIA(GPU-0): Samsung U28D590 (DFP-4): Internal DisplayPort
[    41.771] (--) NVIDIA(GPU-0): Samsung U28D590 (DFP-4): 960.0 MHz maximum pixel clock
[    41.771] (--) NVIDIA(GPU-0): 
[    41.774] (--) NVIDIA(GPU-0): DFP-5: disconnected
[    41.774] (--) NVIDIA(GPU-0): DFP-5: Internal TMDS
[    41.774] (--) NVIDIA(GPU-0): DFP-5: 165.0 MHz maximum pixel clock
[    41.774] (--) NVIDIA(GPU-0): 
[    41.774] (--) NVIDIA(GPU-0): DFP-6: disconnected
[    41.774] (--) NVIDIA(GPU-0): DFP-6: Internal DisplayPort
[    41.774] (--) NVIDIA(GPU-0): DFP-6: 960.0 MHz maximum pixel clock
[    41.774] (--) NVIDIA(GPU-0): 
[    41.774] (--) NVIDIA(GPU-0): DFP-7: disconnected
[    41.774] (--) NVIDIA(GPU-0): DFP-7: Internal TMDS
[    41.774] (--) NVIDIA(GPU-0): DFP-7: 165.0 MHz maximum pixel clock
[    41.774] (--) NVIDIA(GPU-0): 
[    41.812] (II) NVIDIA(0): Setting mode "DFP-4:nvidia-auto-select"
[    41.879] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[    41.879] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[    41.879] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[    41.879] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[    41.879] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[    41.879] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[    41.879] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[    41.879] (II) NVIDIA(0):     Config Options in the README.
[    41.913] (II) event2  - Power Button: is tagged by udev as: Keyboard
[    41.913] (II) event2  - Power Button: device is a keyboard
[    41.913] (II) event1  - Power Button: is tagged by udev as: Keyboard
[    41.913] (II) event1  - Power Button: device is a keyboard
[    41.914] (II) event0  - Sleep Button: is tagged by udev as: Keyboard
[    41.914] (II) event0  - Sleep Button: device is a keyboard
[    41.971] (II) event4  - Logitech USB Laser Mouse: is tagged by udev as: Mouse
[    41.971] (II) event4  - Logitech USB Laser Mouse: device set to 1200 DPI
[    41.971] (II) event4  - Logitech USB Laser Mouse: device is a pointer
[    41.972] (II) event3  - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard
[    41.973] (II) event3  - AT Translated Set 2 keyboard: device is a keyboard
[    49.233] (II) event2  - Power Button: device removed
[    49.250] (II) event1  - Power Button: device removed
[    49.266] (II) event0  - Sleep Button: device removed
[    49.283] (II) event4  - Logitech USB Laser Mouse: device removed
[    49.320] (II) event3  - AT Translated Set 2 keyboard: device removed
[    57.330] (--) NVIDIA(GPU-0): CRT-0: disconnected
[    57.330] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
[    57.330] (--) NVIDIA(GPU-0): 
[    57.334] (--) NVIDIA(GPU-0): DFP-0: disconnected
[    57.334] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[    57.334] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[    57.334] (--) NVIDIA(GPU-0): 
[    57.334] (--) NVIDIA(GPU-0): DFP-1: disconnected
[    57.334] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[    57.334] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[    57.334] (--) NVIDIA(GPU-0): 
[    57.334] (--) NVIDIA(GPU-0): DFP-2: disconnected
[    57.334] (--) NVIDIA(GPU-0): DFP-2: Internal DisplayPort
[    57.334] (--) NVIDIA(GPU-0): DFP-2: 960.0 MHz maximum pixel clock
[    57.334] (--) NVIDIA(GPU-0): 
[    57.334] (--) NVIDIA(GPU-0): DFP-3: disconnected
[    57.334] (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
[    57.334] (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock
[    57.334] (--) NVIDIA(GPU-0): 
[    57.334] (--) NVIDIA(GPU-0): Samsung U28D590 (DFP-4): connected
[    57.334] (--) NVIDIA(GPU-0): Samsung U28D590 (DFP-4): Internal DisplayPort
[    57.334] (--) NVIDIA(GPU-0): Samsung U28D590 (DFP-4): 960.0 MHz maximum pixel clock
[    57.334] (--) NVIDIA(GPU-0): 
[    57.336] (--) NVIDIA(GPU-0): DFP-5: disconnected
[    57.336] (--) NVIDIA(GPU-0): DFP-5: Internal TMDS
[    57.336] (--) NVIDIA(GPU-0): DFP-5: 165.0 MHz maximum pixel clock
[    57.336] (--) NVIDIA(GPU-0): 
[    57.336] (--) NVIDIA(GPU-0): DFP-6: disconnected
[    57.336] (--) NVIDIA(GPU-0): DFP-6: Internal DisplayPort
[    57.336] (--) NVIDIA(GPU-0): DFP-6: 960.0 MHz maximum pixel clock
[    57.336] (--) NVIDIA(GPU-0): 
[    57.336] (--) NVIDIA(GPU-0): DFP-7: disconnected
[    57.336] (--) NVIDIA(GPU-0): DFP-7: Internal TMDS
[    57.336] (--) NVIDIA(GPU-0): DFP-7: 165.0 MHz maximum pixel clock
[    57.336] (--) NVIDIA(GPU-0): 
[    57.348] (II) NVIDIA(0): Setting mode "DFP-4:nvidia-auto-select"
[    57.405] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[    57.405] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[    57.405] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[    57.405] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[    57.405] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[    57.405] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[    57.405] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[    57.405] (II) NVIDIA(0):     Config Options in the README.
[    57.439] (II) event2  - Power Button: is tagged by udev as: Keyboard
[    57.439] (II) event2  - Power Button: device is a keyboard
[    57.440] (II) event1  - Power Button: is tagged by udev as: Keyboard
[    57.440] (II) event1  - Power Button: device is a keyboard
[    57.440] (II) event0  - Sleep Button: is tagged by udev as: Keyboard
[    57.440] (II) event0  - Sleep Button: device is a keyboard
[    57.498] (II) event4  - Logitech USB Laser Mouse: is tagged by udev as: Mouse
[    57.498] (II) event4  - Logitech USB Laser Mouse: device set to 1200 DPI
[    57.498] (II) event4  - Logitech USB Laser Mouse: device is a pointer
[    57.499] (II) event3  - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard
[    57.499] (II) event3  - AT Translated Set 2 keyboard: device is a keyboard
[   123.910] (--) NVIDIA(GPU-0): CRT-0: disconnected
[   123.910] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
[   123.910] (--) NVIDIA(GPU-0): 
[   123.914] (--) NVIDIA(GPU-0): DFP-0: disconnected
[   123.914] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[   123.914] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[   123.914] (--) NVIDIA(GPU-0): 
[   123.914] (--) NVIDIA(GPU-0): DFP-1: disconnected
[   123.914] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[   123.914] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[   123.914] (--) NVIDIA(GPU-0): 
[   123.914] (--) NVIDIA(GPU-0): DFP-2: disconnected
[   123.914] (--) NVIDIA(GPU-0): DFP-2: Internal DisplayPort
[   123.914] (--) NVIDIA(GPU-0): DFP-2: 960.0 MHz maximum pixel clock
[   123.914] (--) NVIDIA(GPU-0): 
[   123.914] (--) NVIDIA(GPU-0): DFP-3: disconnected
[   123.914] (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
[   123.914] (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock
[   123.914] (--) NVIDIA(GPU-0): 
[   123.914] (--) NVIDIA(GPU-0): Samsung U28D590 (DFP-4): connected
[   123.914] (--) NVIDIA(GPU-0): Samsung U28D590 (DFP-4): Internal DisplayPort
[   123.914] (--) NVIDIA(GPU-0): Samsung U28D590 (DFP-4): 960.0 MHz maximum pixel clock
[   123.914] (--) NVIDIA(GPU-0): 
[   123.916] (--) NVIDIA(GPU-0): DFP-5: disconnected
[   123.916] (--) NVIDIA(GPU-0): DFP-5: Internal TMDS
[   123.916] (--) NVIDIA(GPU-0): DFP-5: 165.0 MHz maximum pixel clock
[   123.916] (--) NVIDIA(GPU-0): 
[   123.916] (--) NVIDIA(GPU-0): DFP-6: disconnected
[   123.916] (--) NVIDIA(GPU-0): DFP-6: Internal DisplayPort
[   123.916] (--) NVIDIA(GPU-0): DFP-6: 960.0 MHz maximum pixel clock
[   123.916] (--) NVIDIA(GPU-0): 
[   123.916] (--) NVIDIA(GPU-0): DFP-7: disconnected
[   123.916] (--) NVIDIA(GPU-0): DFP-7: Internal TMDS
[   123.916] (--) NVIDIA(GPU-0): DFP-7: 165.0 MHz maximum pixel clock
[   123.916] (--) NVIDIA(GPU-0): 

archlinux20130905

Member

Registered: 2013-09-05

Posts: 45

Re: mesa problem

There's one more weirdness, which I just noticed. If I don't login into an account using the GUI, I can switch between tty and the GUI as many times as I want. However this stops working if I login using the GUI. If I try to switch to a tty-console after logging into an account using the GUI, I'm unable to switch back using Ctrl+Alt+F<Number>. After switching back I only see a black screen and the mouse cursor. This problem occurs with mesa 1:23.3.2-1. I'm not sure, whether I had this problem before but probably not and I'm unwilling to downgrade mesa even more in order to find out.

seth

Member

Registered: 2012-09-03

Posts: 52,317

Re: mesa problem

@questionask, remove xf86-video-vesa, there's no sign of the swrast driver.
If keepassx segfaults you'll likely a https://wiki.archlinux.org/title/Core_d … _core_dump

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

seth

Member

Registered: 2012-09-03

Posts: 52,317

Re: mesa problem

@archlinux20130905
Remove every single xf86-video-* package, add "nvidia_drm.modeset=1 nvidia_drm.fbdev=1" to the kernel commandline (you still don't want to have the simpledrm device¹) and then please post the entire system journal - you can obfuscate your hostname, but random driver message that flips timed out are pretty much meaningless.
On a limb: you'r running GDM on wayland and some X11 session, but that's really just a completely wild guess about what might be going on.

¹

[    22.590] (EE) open /dev/dri/card0: No such file or directory

though looks like it got unloaded? Is this nvidia-open?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Ambos

Member

Registered: 2024-01-01

Posts: 5

Website

Re: mesa problem

No. nvidia_drm.modeset=1 on the kernel command line.

You mean I need add nvidia_drm.modeset=1 to /etc/default/grub like this, right?

GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet nvidia_drm.modeset=1"

Don't forget to regenerate the GRUB configuration file once you edited this one. That's what I did since I didn't have DRM enabled.
https://wiki.archlinux.org/title/Kernel_parameters#GRUB

Also, thank you seth and Scimmia for the explanations about the swrast driver.
https://gitlab.archlinux.org/archlinux/ … ote_152935

xyrgug

Member

Registered: 2023-12-15

Posts: 32

Re: mesa problem

It's not very clear on archwiki about setting the Kernel Parameter for nvidia driver.
This one makes sense to me:
https://github.com/korvahannu/arch-nvid … de-setting

Last edited by xyrgug (2024-01-02 04:57:51)

tethys

Member

Registered: 2019-08-13

Posts: 105

Re: mesa problem

It's not very clear on archwiki about setting the Kernel Parameter for nvidia driver.
This one makes sense to me:
https://github.com/korvahannu/arch-nvid … de-setting

Here I have a question (this applies to nvidia driver versions >= 545).
Archwiki says that in addition one should add:

FILES=(/etc/modprobe.d/nvidia.conf)

to /etc/mkinitcpio.conf. Is this necessary or not, as the above link does not mention it?

carrioncrow

Member

Registered: 2019-01-20

Posts: 2

Re: mesa problem

Hi,
Same problem for me ; I got a i7 6600u and using integrated Intel graphics. Downgrading mesa to 1:23-3.1-1 didn't work (weirdly, and I've ran `mkinitcpio -p linux`). I've removed `xf86-video-intel` and added `kms` to HOOKS in `/etc/mkinitcpio.conf`, ran `mkinitcpio -P linux` and it works now.

Last edited by carrioncrow (2024-01-02 08:39:23)

seth

Member

Registered: 2012-09-03

Posts: 52,317

Re: mesa problem

@tethys, the wiki says that *where*?
Generally that would, iff at all, only be required for early KMS, which isn't relevant to the situation at hand but even then, modprobe configs are picked up by the relevant mkinitcpio hook, and regenerating the initramfs is an inevitable step.

Wrt the paint-by-numbers rendition linked by xyrgug:
1. anyone who uses archlinux and copies some random config file from the internet unvetted into their system can line up for a public spanking
2. while enabling fbdev allows the driver to work w/ the simplydumb device, the wiki mentions severe caveats

· Note that when an nvidia-drm framebuffer console is enabled, unloading nvidia-drm will cause the screen to turn off.
· `fbdev=1` seems to cause my display to freeze (tty cursor not flickering, typed letters not appearing, etc., while Ctrl + Alt + Delete still works.)
· yet another issue where external screen wouldn't work due to https://forums.developer.nvidia.com/t/5 … /274788/15

what looks A LOT like archlinux20130905's problem.
The robust approach is to completely block the simpledrm device through the kernel parameter and wait until nvidia fixed their fbdev code, the 545xx drivers had a lot of issues anyway, driving many users to revert to 535 as mitigation.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

tethys

Member

Registered: 2019-08-13

Posts: 105

Re: mesa problem

@tethys, the wiki says that *where*?

In the link you posted earlier, please see the Note:

"If any of the affected modules is loaded from the initramfs, then you will need to add the appropriate .conf file to FILES in mkinitcpio.conf..."

Or did I missunderstand it?

Edit: in addition it says that "For nvidia driver version < 545, the nvidia_drm.modeset=1 option must be set through kernel parameters, in order to disable simpledrm".

Last edited by tethys (2024-01-02 10:06:35)

seth

Member

Registered: 2012-09-03

Posts: 52,317

Re: mesa problem

Ah, trapped by my textblock [fixing…]
The relevant section is https://wiki.archlinux.org/title/Kernel … mmand_line (the initcall blacklist isn't a module option)

Your note says "or use the modconf hook", so if you've the modconf hook enabled (which I believe is still default) you don't have to manually add anything

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

tethys

Member

Registered: 2019-08-13

Posts: 105

Re: mesa problem

Your note says "or use the modconf hook", so if you've the modconf hook enabled (which I believe is still default) you don't have to manually add anything

Ah, you are right, modconf hook is enabled also in my case. Thank you for the explanation.

archlinux20130905

Member

Registered: 2013-09-05

Posts: 45

Re: mesa problem

@archlinux20130905
Remove every single xf86-video-* package, add "nvidia_drm.modeset=1 nvidia_drm.fbdev=1" to the kernel commandline (you still don't want to have the simpledrm device¹) and then please post the entire system journal - you can obfuscate your hostname, but random driver message that flips timed out are pretty much meaningless.
On a limb: you'r running GDM on wayland and some X11 session, but that's really just a completely wild guess about what might be going on.

¹

[    22.590] (EE) open /dev/dri/card0: No such file or directory

though looks like it got unloaded? Is this nvidia-open?

Okay, so this is, what I did in order to fix my issues:

pacman -Rs xf86-video-vesa # I forgot that I had this installed.

Added the following parameters to the kernel:

nvidia_drm.modeset=1 nvidia_drm.fbdev=1 initcall_blacklist=simpledrm_platform_driver_init

Removed the configuration-file, I created yesterday:

rm -v /etc/modprobe.d/nvidia_drm.conf
mkinitcpio -p linux

This allowed me to install the newest mesa-package 1:23.3.2-2 without problems. The issue that I cannot switch back into a LightDM-session from a tty-console still persists. But I think that I can accept that. It's not that bad. As long as I log out of a LightDM-user-session I can switch between a tty-console and the LightDM-login-screen as many times as I want. The problem only occurs if I log into a LightDM-session,  switch to a tty-console using Ctl+Alt+F<Number> and then try to switch back using Ctl+Alt+F<Number> again. journalctl -b and /var/log/Xorg.0.log don't show any errors, when I do this. And they also don't show any errors during the boot process.

UPDATE: Okay, I finally found a thread, where people have a similar problem. It's probably an XFCE/proprietary Nvidia driver-incompatibility. Maybe this will get fixed at some point.

Last edited by archlinux20130905 (2024-01-02 13:57:20)

seth

Member

Registered: 2012-09-03

Posts: 52,317

Re: mesa problem

The issue that I cannot switch back into a LightDM-session from a tty-console still persists.

As pointed out, "nvidia_drm.fbdev=1" still has some issues (you seem to be hitting them) and is NOT required to avoid the simpledrm device (plus swrast is fixed in the latest archilnux package)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

gugah

Member

Registered: 2013-01-02

Posts: 60

Re: mesa problem

hi @seth how about those using bumblebee for hybrid graphics?

I've been using xf86-video-intel because it gives me the intel-virtual-output tool (followed: https://wiki.archlinux.org/title/Bumble … VIDIA_chip) and it works like charm when I plug in an external display. Having the same issue after updating mesa.

edit: checking other options for hybrid graphics (haven't checked in a while because how little I game nowadays) also require xf86-video-intel: https://wiki.archlinux.org/title/PRIME# … er_offload but not mesa which is required by bumblebee. time to do the switch...

edit 2: ok, for those still using bumblebee with this mesa issue: just switch to PRIME GPU offloading, works much better out of the box, even the external display. Sorry for going a bit off-topic.

Last edited by gugah (2024-01-02 20:38:01)

---

"The problem with quotes on the Internet is that it is hard to verify their authenticity." ~ Abraham Lincoln

Scimmia

Fellow

Registered: 2012-09-01

Posts: 11,654

Re: mesa problem

If you're using xf86-video-intel, you shouldn't be using the mesa package. As has been said over and over.

gugah

Member

Registered: 2013-01-02

Posts: 60

Re: mesa problem

If you're using xf86-video-intel, you shouldn't be using the mesa package. As has been said over and over.

mesa is a dependency of xf86-video-intel?

I was following https://wiki.archlinux.org/title/Bumblebee#Installation at the time which lists both (although xf86-video-intel optionally) . Guess it's time to use the supported method for hybrid graphics.

Last edited by gugah (2024-01-02 19:41:55)

---

"The problem with quotes on the Internet is that it is hard to verify their authenticity." ~ Abraham Lincoln

questionask

Member

Registered: 2021-01-09

Posts: 57

Re: mesa problem

With an AMD laptop CPU/GPU, I have both xf86-video-amdgpu and xf86-video-vesa installed. Should I uninstall xf86-video-vesa and will this fix the problem, or do I have to do also something else like editing some configuration files?