Arch Linux

JontomXire

Member

Registered: 2025-03-04

Posts: 38

nvidia-580xx-dkms packages not working properly.

So yesterday I was hit, as it appears many of us were, by the nVidia driver update. I eventually got the nvidia-580xx-dkms package, and friends, installed and the system is sort of working. But there are issues.

Sometimes a terminal window will go transparent. The window manager decorations, title bar, frame, etc, are all still there, but the main body of the window just displays whatever was behind it when it glitched. It recovers when the contents changes, e.g. when I press a key. Other windows flicker occasionally as if they went transparent and then immediately updated.

When I run "Ascension" (classless WoW) through Lutris, the processes are all running, but the screen never appears.

I just want my system working properly, and especially to be able to play Ascension. I tried to revert to nvidia-580.95.05-9-x86_64.pkg.tar.zst and friends from the pacman cache, but then the nVidia driver doesn't load at all. I suspect that the older nVidia drivers don't work with the newer kernel, and I need to keep moving forward or eventually Discord will refuse to work and then I won't be able to chat to friends over the internet.

Does anyone have any ideas how I can fix my system?

Last edited by JontomXire (2025-12-22 08:48:17)

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 14,565

Re: nvidia-580xx-dkms packages not working properly.

The nvidia drivers are out of tree kernel modules and need to be rebuild whenever the kernel changes.
When nvidia was in repos arch devs did this for linux & linux-lts.
Aur maintainers don't have the necessary resources for that, so you have to use dkms and perform local builds.

Try the nouveau driver which has improved a lot .

As for a permanent fix :
Get used to buying a new nvidia card every 3-4 years or switch to something that has the driver in the kernel.
(there are 20 year old amd / intel cards that still work fine and often better then when they were brand new).

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 71,486

Re: nvidia-580xx-dkms packages not working properly.

There's an open issue w/ the 580.119 driver, https://bbs.archlinux.org/viewtopic.php?id=311055
Downgrading to 580.95 might be a viable path, but as Lone_Wolf pointed out, you *have* the pick the nvidia-dkms package for that version (and downgrade nvidia-utils and in case you're using it, lib32-nivida-utils along)
https://wiki.archlinux.org/title/Arch_Linux_Archive

or switch to something that has the driver in the kernel

Let's all hope that eventually nvidia-open moves into the kernel and the constant stream of "helps! I brokes my nvidia driver" ends

---

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

JontomXire

Member

Registered: 2025-03-04

Posts: 38

Re: nvidia-580xx-dkms packages not working properly.

Thanks for that, Seth. I also just found this: https://github.com/basecamp/omarchy/issues/3646

So the package I want is nvidia-dkms-580.95.05-1-x86_64, right? Pacman does't like that name. I did  a bit of reading, and ArchLinux doesn't like pacman providing versioned packages, but I found the one I needed at https://archive.archlinux.org/packages/n/nvidia-dkms/.

One reboot later, I am on the old versions of the official repository packages. These get listed with "pacman -Qn":

lib32-nvidia-utils 580.95.05-1
linux-firmware-nvidia 20251125-2
nvidia-settings 580.95.05-1
nvidia-utils 580.95.05-1

And this is listed with "pacman -Qm":

nvidia-dkms 580.95.05-1

I have full resolution on both monitors, the driver clearly is loaded, it is the version I had before, but my Lutris game still is not working.

Anyone have any more ideas?

Last edited by JontomXire (2025-12-22 10:57:57)

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 71,486

Re: nvidia-580xx-dkms packages not working properly.

You can pass any file or url to "pacman -U", don't forget to also downgrade https://archive.archlinux.org/packages/n/nvidia-utils/ and you'll need the kernel-headers, https://wiki.archlinux.org/title/Dynami … le_Support

---

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

JontomXire

Member

Registered: 2025-03-04

Posts: 38

Re: nvidia-580xx-dkms packages not working properly.

Hi, Seth.

I think my edit to my earlier post overlapped your reply.

Also, "dkms status" reports:

nvidia/580.95.05, 6.18.2-arch2-1, x86_64: installed

So it looks like the rollback was completely successful except that the game still doesn't display a window.

Other packages that were updated at the same time as my nvidia drivers were found with "find . -mtime -3 | grep -v "^\./download" | grep -v ".sig$"" in the cache directory, which command outputs:

./python-soupsieve-2.8.1-1-any.pkg.tar.zst
./libopenmpt-0.8.4-1-x86_64.pkg.tar.zst
./gdb-common-17.1-1-x86_64.pkg.tar.zst
./cryptsetup-2.8.3-1-x86_64.pkg.tar.zst
./gdb-17.1-1-x86_64.pkg.tar.zst
./libwbclient-2:4.23.4-1-x86_64.pkg.tar.zst

Last edited by JontomXire (2025-12-22 11:03:10)

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 71,486

Re: nvidia-580xx-dkms packages not working properly.

glxinfo -B

What display server is this?
In case of X11, please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General
Otherwise: test the behavior w/ x11 or a different wayland compositor.

---

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

JontomXire

Member

Registered: 2025-03-04

Posts: 38

Re: nvidia-580xx-dkms packages not working properly.

$ glxinfo -B
name of display: :0.0
display: :0  screen: 0
direct rendering: Yes
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 8192 MB
    Total available memory: 8192 MB
    Currently available dedicated video memory: 7716 MB
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce GTX 1080/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 580.95.05
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6.0 NVIDIA 580.95.05
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)

OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 580.95.05
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

XOrg log:

[    86.282] 
X.Org X Server 1.21.1.21
X Protocol Version 11, Revision 0
[    86.282] Current Operating System: Linux shikamaru 6.18.2-arch2-1 #1 SMP PREEMPT_DYNAMIC Thu, 18 Dec 2025 18:00:18 +0000 x86_64
[    86.282] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=37875e0b-061b-4789-93fd-58d65a5d6088 rw loglevel=3 quiet
[    86.282]  
[    86.282] Current version of pixman: 0.46.4
[    86.282] 	Before reporting problems, check [url]http://wiki.x.org[/url]
	to make sure that you have the latest version.
[    86.282] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    86.282] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Dec 23 10:34:10 2025
[    86.289] (==) Using config directory: "/etc/X11/xorg.conf.d"
[    86.289] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    86.291] (==) No Layout section.  Using the first Screen section.
[    86.291] (==) No screen section available. Using defaults.
[    86.291] (**) |-->Screen "Default Screen Section" (0)
[    86.291] (**) |   |-->Monitor "<default monitor>"
[    86.292] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[    86.292] (**) Allowing byte-swapped clients
[    86.292] (==) Automatically adding devices
[    86.292] (==) Automatically enabling devices
[    86.292] (==) Automatically adding GPU devices
[    86.292] (==) Automatically binding GPU devices
[    86.293] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    86.295] (WW) The directory "/usr/share/fonts/misc" does not exist.
[    86.295] 	Entry deleted from font path.
[    86.295] (WW) The directory "/usr/share/fonts/TTF" does not exist.
[    86.295] 	Entry deleted from font path.
[    86.295] (WW) The directory "/usr/share/fonts/OTF" does not exist.
[    86.295] 	Entry deleted from font path.
[    86.295] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[    86.295] 	Entry deleted from font path.
[    86.295] (WW) The directory "/usr/share/fonts/100dpi" does not exist.
[    86.295] 	Entry deleted from font path.
[    86.295] (WW) The directory "/usr/share/fonts/75dpi" does not exist.
[    86.295] 	Entry deleted from font path.
[    86.295] (==) FontPath set to:
	
[    86.295] (==) ModulePath set to "/usr/lib/xorg/modules"
[    86.295] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[    86.295] (II) Module ABI versions:
[    86.295] 	X.Org ANSI C Emulation: 0.4
[    86.295] 	X.Org Video Driver: 25.2
[    86.295] 	X.Org XInput driver : 24.4
[    86.295] 	X.Org Server Extension : 10.0
[    86.296] (++) using VT number 7

[    86.296] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[    86.298] (II) xfree86: Adding drm device (/dev/dri/card1)
[    86.298] (II) Platform probe for /sys/devices/pci0000:00/0000:00:03.1/0000:09:00.0/drm/card1
[    86.305] (**) OutputClass "nvidia" ModulePath extended to "/usr/lib/nvidia/xorg,/usr/lib/xorg/modules,/usr/lib/xorg/modules"
[    86.308] (--) PCI:*(9@0:0:0) 10de:1b80:1458:3702 rev 161, Mem @ 0xfc000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/131072
[    86.308] (II) LoadModule: "glx"
[    86.311] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    86.322] (II) Module glx: vendor="X.Org Foundation"
[    86.322] 	compiled for 1.21.1.21, module version = 1.0.0
[    86.322] 	ABI class: X.Org Server Extension, version 10.0
[    86.322] (II) Applying OutputClass "nvidia" to /dev/dri/card1
[    86.322] 	loading driver: nvidia
[    86.322] (==) Matched nvidia as autoconfigured driver 0
[    86.322] (==) Matched nouveau as autoconfigured driver 1
[    86.322] (==) Matched nv as autoconfigured driver 2
[    86.322] (==) Matched modesetting as autoconfigured driver 3
[    86.322] (==) Matched fbdev as autoconfigured driver 4
[    86.322] (==) Matched vesa as autoconfigured driver 5
[    86.323] (==) Assigned the driver to the xf86ConfigLayout
[    86.323] (II) LoadModule: "nvidia"
[    86.324] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[    86.332] (II) Module nvidia: vendor="NVIDIA Corporation"
[    86.332] 	compiled for 1.6.99.901, module version = 1.0.0
[    86.332] 	Module class: X.Org Video Driver
[    86.333] (II) LoadModule: "nouveau"
[    86.333] (WW) Warning, couldn't open module nouveau
[    86.333] (EE) Failed to load module "nouveau" (module does not exist, 0)
[    86.333] (II) LoadModule: "nv"
[    86.333] (WW) Warning, couldn't open module nv
[    86.333] (EE) Failed to load module "nv" (module does not exist, 0)
[    86.333] (II) LoadModule: "modesetting"
[    86.333] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[    86.335] (II) Module modesetting: vendor="X.Org Foundation"
[    86.335] 	compiled for 1.21.1.21, module version = 1.21.1
[    86.335] 	Module class: X.Org Video Driver
[    86.335] 	ABI class: X.Org Video Driver, version 25.2
[    86.335] (II) LoadModule: "fbdev"
[    86.335] (WW) Warning, couldn't open module fbdev
[    86.335] (EE) Failed to load module "fbdev" (module does not exist, 0)
[    86.335] (II) LoadModule: "vesa"
[    86.335] (WW) Warning, couldn't open module vesa
[    86.335] (EE) Failed to load module "vesa" (module does not exist, 0)
[    86.335] (II) NVIDIA dlloader X Driver  580.95.05  Tue Sep 23 09:43:47 UTC 2025
[    86.335] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[    86.335] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    86.355] (II) Loading sub module "fb"
[    86.355] (II) LoadModule: "fb"
[    86.355] (II) Module "fb" already built-in
[    86.355] (II) Loading sub module "wfb"
[    86.355] (II) LoadModule: "wfb"
[    86.355] (II) Loading /usr/lib/xorg/modules/libwfb.so
[    86.357] (II) Module wfb: vendor="X.Org Foundation"
[    86.357] 	compiled for 1.21.1.21, module version = 1.0.0
[    86.357] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    86.359] (WW) Falling back to old probe method for modesetting
[    86.359] (EE) open /dev/dri/card0: No such file or directory
[    86.360] (II) NVIDIA(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[    86.360] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[    86.360] (==) NVIDIA(0): RGB weight 888
[    86.360] (==) NVIDIA(0): Default visual is TrueColor
[    86.360] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[    86.360] (II) Applying OutputClass "nvidia" options to /dev/dri/card1
[    86.361] (**) NVIDIA(0): Option "AllowEmptyInitialConfiguration"
[    86.361] (**) NVIDIA(0): Enabling 2D acceleration
[    86.361] (II) Loading sub module "glxserver_nvidia"
[    86.361] (II) LoadModule: "glxserver_nvidia"
[    86.361] (II) Loading /usr/lib/nvidia/xorg/libglxserver_nvidia.so
[    86.603] (II) Module glxserver_nvidia: vendor="NVIDIA Corporation"
[    86.603] 	compiled for 1.6.99.901, module version = 1.0.0
[    86.603] 	Module class: X.Org Server Extension
[    86.603] (II) NVIDIA GLX Module  580.95.05  Tue Sep 23 09:49:15 UTC 2025
[    86.604] (II) NVIDIA: The X server supports PRIME Render Offload.
[    86.606] (--) NVIDIA(0): Valid display device(s) on GPU-0 at PCI:9:0:0
[    86.606] (--) NVIDIA(0):     DFP-0 (boot)
[    86.606] (--) NVIDIA(0):     DFP-1
[    86.606] (--) NVIDIA(0):     DFP-2
[    86.606] (--) NVIDIA(0):     DFP-3
[    86.606] (--) NVIDIA(0):     DFP-4
[    86.606] (--) NVIDIA(0):     DFP-5
[    86.606] (--) NVIDIA(0):     DFP-6
[    86.606] (--) NVIDIA(0):     DFP-7
[    86.619] (II) NVIDIA(0): NVIDIA GPU NVIDIA GeForce GTX 1080 (GP104-A) at PCI:9:0:0
[    86.619] (II) NVIDIA(0):     (GPU-0)
[    86.619] (--) NVIDIA(0): Memory: 8388608 kBytes
[    86.619] (--) NVIDIA(0): VideoBIOS: 86.04.3b.40.61
[    86.619] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[    86.753] (--) NVIDIA(GPU-0): AOC 2470W (DFP-0): connected
[    86.753] (--) NVIDIA(GPU-0): AOC 2470W (DFP-0): Internal TMDS
[    86.753] (--) NVIDIA(GPU-0): AOC 2470W (DFP-0): 330.0 MHz maximum pixel clock
[    86.753] (--) NVIDIA(GPU-0): 
[    86.753] (--) NVIDIA(GPU-0): DFP-1: disconnected
[    86.753] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[    86.753] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[    86.753] (--) NVIDIA(GPU-0): 
[    86.753] (--) NVIDIA(GPU-0): DFP-2: disconnected
[    86.753] (--) NVIDIA(GPU-0): DFP-2: Internal DisplayPort
[    86.753] (--) NVIDIA(GPU-0): DFP-2: 1440.0 MHz maximum pixel clock
[    86.753] (--) NVIDIA(GPU-0): 
[    86.753] (--) NVIDIA(GPU-0): DFP-3: disconnected
[    86.753] (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
[    86.753] (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock
[    86.753] (--) NVIDIA(GPU-0): 
[    86.754] (--) NVIDIA(GPU-0): AOC 2460G5 (DFP-4): connected
[    86.754] (--) NVIDIA(GPU-0): AOC 2460G5 (DFP-4): Internal DisplayPort
[    86.754] (--) NVIDIA(GPU-0): AOC 2460G5 (DFP-4): 1440.0 MHz maximum pixel clock
[    86.754] (--) NVIDIA(GPU-0): 
[    86.756] (--) NVIDIA(GPU-0): DFP-5: disconnected
[    86.756] (--) NVIDIA(GPU-0): DFP-5: Internal TMDS
[    86.756] (--) NVIDIA(GPU-0): DFP-5: 165.0 MHz maximum pixel clock
[    86.756] (--) NVIDIA(GPU-0): 
[    86.756] (--) NVIDIA(GPU-0): DFP-6: disconnected
[    86.756] (--) NVIDIA(GPU-0): DFP-6: Internal DisplayPort
[    86.756] (--) NVIDIA(GPU-0): DFP-6: 1440.0 MHz maximum pixel clock
[    86.756] (--) NVIDIA(GPU-0): 
[    86.757] (--) NVIDIA(GPU-0): DFP-7: disconnected
[    86.757] (--) NVIDIA(GPU-0): DFP-7: Internal TMDS
[    86.757] (--) NVIDIA(GPU-0): DFP-7: 165.0 MHz maximum pixel clock
[    86.757] (--) NVIDIA(GPU-0): 
[    86.775] (==) NVIDIA(0): 
[    86.775] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[    86.775] (==) NVIDIA(0):     will be used as the requested mode.
[    86.775] (==) NVIDIA(0): 
[    86.776] (II) NVIDIA(0): Validated MetaModes:
[    86.776] (II) NVIDIA(0):     "DFP-0:nvidia-auto-select,DFP-4:nvidia-auto-select"
[    86.776] (II) NVIDIA(0): Virtual screen size determined to be 3840 x 1080
[    86.786] (--) NVIDIA(0): DPI set to (93, 94); computed from "UseEdidDpi" X config
[    86.786] (--) NVIDIA(0):     option
[    86.786] (II) UnloadModule: "modesetting"
[    86.786] (II) Unloading modesetting
[    86.787] (II) NVIDIA: Reserving 24576.00 MB of virtual memory for indirect memory
[    86.787] (II) NVIDIA:     access.
[    86.790] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[    86.790] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[    86.790] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[    86.790] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[    86.790] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[    86.790] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[    86.790] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[    86.790] (II) NVIDIA(0):     Config Options in the README.
[    86.814] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select,DFP-4:nvidia-auto-select"
[    86.948] (==) NVIDIA(0): Disabling shared memory pixmaps
[    86.948] (==) NVIDIA(0): Backing store enabled
[    86.948] (==) NVIDIA(0): Silken mouse enabled
[    86.949] (==) NVIDIA(0): DPMS enabled
[    86.950] (II) Loading sub module "dri2"
[    86.950] (II) LoadModule: "dri2"
[    86.950] (II) Module "dri2" already built-in
[    86.950] (II) NVIDIA(0): [DRI2] Setup complete
[    86.950] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[    86.951] (II) Initializing extension Generic Event Extension
[    86.951] (II) Initializing extension SHAPE
[    86.951] (II) Initializing extension MIT-SHM
[    86.951] (II) Initializing extension XInputExtension
[    86.951] (II) Initializing extension XTEST
[    86.952] (II) Initializing extension BIG-REQUESTS
[    86.952] (II) Initializing extension SYNC
[    86.952] (II) Initializing extension XKEYBOARD
[    86.952] (II) Initializing extension XC-MISC
[    86.952] (II) Initializing extension SECURITY
[    86.952] (II) Initializing extension XFIXES
[    86.952] (II) Initializing extension RENDER
[    86.952] (II) Initializing extension RANDR
[    86.953] (II) Initializing extension COMPOSITE
[    86.953] (II) Initializing extension DAMAGE
[    86.953] (II) Initializing extension MIT-SCREEN-SAVER
[    86.953] (II) Initializing extension DOUBLE-BUFFER
[    86.953] (II) Initializing extension RECORD
[    86.953] (II) Initializing extension DPMS
[    86.953] (II) Initializing extension Present
[    86.953] (II) Initializing extension DRI3
[    86.953] (II) Initializing extension X-Resource
[    86.953] (II) Initializing extension XVideo
[    86.953] (II) Initializing extension XVideo-MotionCompensation
[    86.953] (II) Initializing extension GLX
[    86.953] (II) Initializing extension GLX
[    86.953] (II) Indirect GLX disabled.
[    86.953] (II) GLX: Another vendor is already registered for screen 0
[    86.953] (II) Initializing extension XFree86-VidModeExtension
[    86.954] (II) Initializing extension XFree86-DGA
[    86.954] (II) Initializing extension XFree86-DRI
[    86.954] (II) Initializing extension DRI2
[    86.954] (II) Initializing extension NV-GLX
[    86.954] (II) Initializing extension NV-CONTROL
[    86.954] (II) Initializing extension XINERAMA
[    87.127] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[    87.127] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[    87.127] (**) Power Button: Applying InputClass "system-keyboard"
[    87.127] (II) LoadModule: "libinput"
[    87.127] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[    87.133] (II) Module libinput: vendor="X.Org Foundation"
[    87.133] 	compiled for 1.21.1.13, module version = 1.5.0
[    87.133] 	Module class: X.Org XInput Driver
[    87.133] 	ABI class: X.Org XInput driver, version 24.4
[    87.133] (II) Using input driver 'libinput' for 'Power Button'
[    87.133] (**) Power Button: always reports core events
[    87.133] (**) Option "Device" "/dev/input/event1"
[    87.141] (II) event1  - Power Button: is tagged by udev as: Keyboard
[    87.141] (II) event1  - Power Button: device is a keyboard
[    87.141] (II) event1  - Power Button: device removed
[    87.155] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1"
[    87.155] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[    87.155] (**) Option "xkb_model" "pc105"
[    87.155] (**) Option "xkb_layout" "gb"
[    87.172] (II) event1  - Power Button: is tagged by udev as: Keyboard
[    87.172] (II) event1  - Power Button: device is a keyboard
[    87.173] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[    87.173] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[    87.173] (**) Power Button: Applying InputClass "system-keyboard"
[    87.173] (II) Using input driver 'libinput' for 'Power Button'
[    87.173] (**) Power Button: always reports core events
[    87.173] (**) Option "Device" "/dev/input/event0"
[    87.174] (II) event0  - Power Button: is tagged by udev as: Keyboard
[    87.174] (II) event0  - Power Button: device is a keyboard
[    87.174] (II) event0  - Power Button: device removed
[    87.180] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0/event0"
[    87.180] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[    87.180] (**) Option "xkb_model" "pc105"
[    87.180] (**) Option "xkb_layout" "gb"
[    87.181] (II) event0  - Power Button: is tagged by udev as: Keyboard
[    87.181] (II) event0  - Power Button: device is a keyboard
[    87.182] (II) config/udev: Adding input device Logitech USB Keyboard (/dev/input/event3)
[    87.182] (**) Logitech USB Keyboard: Applying InputClass "libinput keyboard catchall"
[    87.182] (**) Logitech USB Keyboard: Applying InputClass "system-keyboard"
[    87.182] (II) Using input driver 'libinput' for 'Logitech USB Keyboard'
[    87.182] (**) Logitech USB Keyboard: always reports core events
[    87.182] (**) Option "Device" "/dev/input/event3"
[    87.184] (II) event3  - Logitech USB Keyboard: is tagged by udev as: Keyboard
[    87.184] (II) event3  - Logitech USB Keyboard: device is a keyboard
[    87.184] (II) event3  - Logitech USB Keyboard: device removed
[    87.197] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-5/1-5:1.0/0003:046D:C31C.0002/input/input3/event3"
[    87.197] (II) XINPUT: Adding extended input device "Logitech USB Keyboard" (type: KEYBOARD, id 8)
[    87.197] (**) Option "xkb_model" "pc105"
[    87.197] (**) Option "xkb_layout" "gb"
[    87.199] (II) event3  - Logitech USB Keyboard: is tagged by udev as: Keyboard
[    87.199] (II) event3  - Logitech USB Keyboard: device is a keyboard
[    87.200] (II) config/udev: Adding input device Logitech USB Keyboard Consumer Control (/dev/input/event4)
[    87.200] (**) Logitech USB Keyboard Consumer Control: Applying InputClass "libinput keyboard catchall"
[    87.200] (**) Logitech USB Keyboard Consumer Control: Applying InputClass "system-keyboard"
[    87.200] (II) Using input driver 'libinput' for 'Logitech USB Keyboard Consumer Control'
[    87.200] (**) Logitech USB Keyboard Consumer Control: always reports core events
[    87.200] (**) Option "Device" "/dev/input/event4"
[    87.202] (II) event4  - Logitech USB Keyboard Consumer Control: is tagged by udev as: Keyboard
[    87.202] (II) event4  - Logitech USB Keyboard Consumer Control: device is a keyboard
[    87.202] (II) event4  - Logitech USB Keyboard Consumer Control: device removed
[    87.222] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-5/1-5:1.1/0003:046D:C31C.0003/input/input4/event4"
[    87.222] (II) XINPUT: Adding extended input device "Logitech USB Keyboard Consumer Control" (type: KEYBOARD, id 9)
[    87.222] (**) Option "xkb_model" "pc105"
[    87.222] (**) Option "xkb_layout" "gb"
[    87.224] (II) event4  - Logitech USB Keyboard Consumer Control: is tagged by udev as: Keyboard
[    87.224] (II) event4  - Logitech USB Keyboard Consumer Control: device is a keyboard
[    87.225] (II) config/udev: Adding input device Logitech USB Keyboard System Control (/dev/input/event5)
[    87.225] (**) Logitech USB Keyboard System Control: Applying InputClass "libinput keyboard catchall"
[    87.225] (**) Logitech USB Keyboard System Control: Applying InputClass "system-keyboard"
[    87.225] (II) Using input driver 'libinput' for 'Logitech USB Keyboard System Control'
[    87.225] (**) Logitech USB Keyboard System Control: always reports core events
[    87.225] (**) Option "Device" "/dev/input/event5"
[    87.228] (II) event5  - Logitech USB Keyboard System Control: is tagged by udev as: Keyboard
[    87.228] (II) event5  - Logitech USB Keyboard System Control: device is a keyboard
[    87.228] (II) event5  - Logitech USB Keyboard System Control: device removed
[    87.239] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-5/1-5:1.1/0003:046D:C31C.0003/input/input5/event5"
[    87.239] (II) XINPUT: Adding extended input device "Logitech USB Keyboard System Control" (type: KEYBOARD, id 10)
[    87.239] (**) Option "xkb_model" "pc105"
[    87.239] (**) Option "xkb_layout" "gb"
[    87.241] (II) event5  - Logitech USB Keyboard System Control: is tagged by udev as: Keyboard
[    87.241] (II) event5  - Logitech USB Keyboard System Control: device is a keyboard
[    87.243] (II) config/udev: Adding input device Logitech Gaming Mouse G502 (/dev/input/event6)
[    87.243] (**) Logitech Gaming Mouse G502: Applying InputClass "libinput pointer catchall"
[    87.243] (II) Using input driver 'libinput' for 'Logitech Gaming Mouse G502'
[    87.243] (**) Logitech Gaming Mouse G502: always reports core events
[    87.243] (**) Option "Device" "/dev/input/event6"
[    87.296] (II) event6  - Logitech Gaming Mouse G502: is tagged by udev as: Mouse
[    87.296] (II) event6  - Logitech Gaming Mouse G502: device is a pointer
[    87.297] (II) event6  - Logitech Gaming Mouse G502: device removed
[    87.317] (II) libinput: Logitech Gaming Mouse G502: Step value 0 was provided, libinput Fallback acceleration function is used.
[    87.317] (II) libinput: Logitech Gaming Mouse G502: Step value 0 was provided, libinput Fallback acceleration function is used.
[    87.317] (II) libinput: Logitech Gaming Mouse G502: Step value 0 was provided, libinput Fallback acceleration function is used.
[    87.317] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-6/1-6:1.0/0003:046D:C07D.0004/input/input6/event6"
[    87.317] (II) XINPUT: Adding extended input device "Logitech Gaming Mouse G502" (type: MOUSE, id 11)
[    87.317] (**) Option "AccelerationScheme" "none"
[    87.317] (**) Logitech Gaming Mouse G502: (accel) selected scheme none/0
[    87.317] (**) Logitech Gaming Mouse G502: (accel) acceleration factor: 2.000
[    87.317] (**) Logitech Gaming Mouse G502: (accel) acceleration threshold: 4
[    87.373] (II) event6  - Logitech Gaming Mouse G502: is tagged by udev as: Mouse
[    87.374] (II) event6  - Logitech Gaming Mouse G502: device is a pointer
[    87.377] (II) config/udev: Adding input device Logitech Gaming Mouse G502 (/dev/input/mouse0)
[    87.377] (II) No input driver specified, ignoring this device.
[    87.377] (II) This device may have been added with another device file.
[    87.380] (II) config/udev: Adding input device Logitech Gaming Mouse G502 Keyboard (/dev/input/event7)
[    87.380] (**) Logitech Gaming Mouse G502 Keyboard: Applying InputClass "libinput keyboard catchall"
[    87.380] (**) Logitech Gaming Mouse G502 Keyboard: Applying InputClass "system-keyboard"
[    87.380] (II) Using input driver 'libinput' for 'Logitech Gaming Mouse G502 Keyboard'
[    87.380] (**) Logitech Gaming Mouse G502 Keyboard: always reports core events
[    87.380] (**) Option "Device" "/dev/input/event7"
[    87.384] (II) event7  - Logitech Gaming Mouse G502 Keyboard: is tagged by udev as: Keyboard
[    87.385] (II) event7  - Logitech Gaming Mouse G502 Keyboard: device is a keyboard
[    87.386] (II) event7  - Logitech Gaming Mouse G502 Keyboard: device removed
[    87.395] (II) libinput: Logitech Gaming Mouse G502 Keyboard: needs a virtual subdevice
[    87.395] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-6/1-6:1.1/0003:046D:C07D.0005/input/input7/event7"
[    87.395] (II) XINPUT: Adding extended input device "Logitech Gaming Mouse G502 Keyboard" (type: MOUSE, id 12)
[    87.395] (**) Option "AccelerationScheme" "none"
[    87.395] (**) Logitech Gaming Mouse G502 Keyboard: (accel) selected scheme none/0
[    87.395] (**) Logitech Gaming Mouse G502 Keyboard: (accel) acceleration factor: 2.000
[    87.395] (**) Logitech Gaming Mouse G502 Keyboard: (accel) acceleration threshold: 4
[    87.399] (II) event7  - Logitech Gaming Mouse G502 Keyboard: is tagged by udev as: Keyboard
[    87.400] (II) event7  - Logitech Gaming Mouse G502 Keyboard: device is a keyboard
[    87.403] (II) config/udev: Adding input device Mega World USB Game Controllers (/dev/input/event8)
[    87.404] (II) No input driver specified, ignoring this device.
[    87.404] (II) This device may have been added with another device file.
[    87.406] (II) config/udev: Adding input device Mega World USB Game Controllers (/dev/input/js0)
[    87.406] (II) No input driver specified, ignoring this device.
[    87.406] (II) This device may have been added with another device file.
[    87.410] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event10)
[    87.410] (II) No input driver specified, ignoring this device.
[    87.410] (II) This device may have been added with another device file.
[    87.411] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event11)
[    87.411] (II) No input driver specified, ignoring this device.
[    87.411] (II) This device may have been added with another device file.
[    87.413] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event12)
[    87.413] (II) No input driver specified, ignoring this device.
[    87.413] (II) This device may have been added with another device file.
[    87.415] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event13)
[    87.415] (II) No input driver specified, ignoring this device.
[    87.415] (II) This device may have been added with another device file.
[    87.418] (II) config/udev: Adding input device USB PnP Audio Device (/dev/input/event2)
[    87.418] (**) USB PnP Audio Device: Applying InputClass "libinput keyboard catchall"
[    87.418] (**) USB PnP Audio Device: Applying InputClass "system-keyboard"
[    87.418] (II) Using input driver 'libinput' for 'USB PnP Audio Device'
[    87.418] (**) USB PnP Audio Device: always reports core events
[    87.418] (**) Option "Device" "/dev/input/event2"
[    87.422] (II) event2  - USB PnP Audio Device: is tagged by udev as: Keyboard
[    87.422] (II) event2  - USB PnP Audio Device: device is a keyboard
[    87.422] (II) event2  - USB PnP Audio Device: device removed
[    87.445] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:07.1/0000:11:00.3/usb3/3-3/3-3:1.3/0003:0C76:161F.0001/input/input2/event2"
[    87.445] (II) XINPUT: Adding extended input device "USB PnP Audio Device" (type: KEYBOARD, id 13)
[    87.445] (**) Option "xkb_model" "pc105"
[    87.445] (**) Option "xkb_layout" "gb"
[    87.450] (II) event2  - USB PnP Audio Device: is tagged by udev as: Keyboard
[    87.450] (II) event2  - USB PnP Audio Device: device is a keyboard
[    87.453] (II) config/udev: Adding input device HD-Audio Generic Rear Mic (/dev/input/event14)
[    87.453] (II) No input driver specified, ignoring this device.
[    87.453] (II) This device may have been added with another device file.
[    87.455] (II) config/udev: Adding input device HD-Audio Generic Front Mic (/dev/input/event15)
[    87.455] (II) No input driver specified, ignoring this device.
[    87.455] (II) This device may have been added with another device file.
[    87.456] (II) config/udev: Adding input device HD-Audio Generic Line (/dev/input/event16)
[    87.456] (II) No input driver specified, ignoring this device.
[    87.456] (II) This device may have been added with another device file.
[    87.458] (II) config/udev: Adding input device HD-Audio Generic Line Out (/dev/input/event17)
[    87.458] (II) No input driver specified, ignoring this device.
[    87.458] (II) This device may have been added with another device file.
[    87.460] (II) config/udev: Adding input device HD-Audio Generic Front Headphone (/dev/input/event18)
[    87.460] (II) No input driver specified, ignoring this device.
[    87.460] (II) This device may have been added with another device file.
[    87.461] (II) config/udev: Adding input device PC Speaker (/dev/input/event9)
[    87.461] (II) No input driver specified, ignoring this device.
[    87.461] (II) This device may have been added with another device file.
[    87.479] (**) Logitech Gaming Mouse G502 Keyboard: Applying InputClass "libinput keyboard catchall"
[    87.479] (**) Logitech Gaming Mouse G502 Keyboard: Applying InputClass "system-keyboard"
[    87.479] (II) Using input driver 'libinput' for 'Logitech Gaming Mouse G502 Keyboard'
[    87.479] (**) Logitech Gaming Mouse G502 Keyboard: always reports core events
[    87.479] (**) Option "Device" "/dev/input/event7"
[    87.479] (II) libinput: Logitech Gaming Mouse G502 Keyboard: is a virtual subdevice
[    87.479] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-6/1-6:1.1/0003:046D:C07D.0005/input/input7/event7"
[    87.479] (II) XINPUT: Adding extended input device "Logitech Gaming Mouse G502 Keyboard" (type: KEYBOARD, id 14)
[    87.479] (**) Option "xkb_model" "pc105"
[    87.479] (**) Option "xkb_layout" "gb"
[    87.545] (II) config/udev: Adding input device Mega World USB Game Controllers (/dev/input/js0)
[    87.545] (II) No input driver specified, ignoring this device.
[    87.545] (II) This device may have been added with another device file.
[    87.629] (II) config/udev: Adding input device Mega World USB Game Controllers (/dev/input/event8)
[    87.629] (II) No input driver specified, ignoring this device.
[    87.629] (II) This device may have been added with another device file.
[   171.440] (II) config/udev: Adding input device Mega World USB Game Controllers (/dev/input/js0)
[   171.441] (II) No input driver specified, ignoring this device.
[   171.441] (II) This device may have been added with another device file.
[   171.448] (II) config/udev: Adding input device Mega World USB Game Controllers (/dev/input/js0)
[   171.448] (II) No input driver specified, ignoring this device.
[   171.448] (II) This device may have been added with another device file.
[   171.509] (II) config/udev: Adding input device Mega World USB Game Controllers (/dev/input/event8)
[   171.509] (II) No input driver specified, ignoring this device.
[   171.509] (II) This device may have been added with another device file.
[   171.593] (II) config/udev: Adding input device Mega World USB Game Controllers (/dev/input/event8)
[   171.593] (II) No input driver specified, ignoring this device.
[   171.593] (II) This device may have been added with another device file.
[   172.944] (--) NVIDIA(GPU-0): AOC 2470W (DFP-0): connected
[   172.944] (--) NVIDIA(GPU-0): AOC 2470W (DFP-0): Internal TMDS
[   172.944] (--) NVIDIA(GPU-0): AOC 2470W (DFP-0): 330.0 MHz maximum pixel clock
[   172.944] (--) NVIDIA(GPU-0): 
[   172.945] (--) NVIDIA(GPU-0): DFP-1: disconnected
[   172.945] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[   172.945] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[   172.945] (--) NVIDIA(GPU-0): 
[   172.945] (--) NVIDIA(GPU-0): DFP-2: disconnected
[   172.945] (--) NVIDIA(GPU-0): DFP-2: Internal DisplayPort
[   172.945] (--) NVIDIA(GPU-0): DFP-2: 1440.0 MHz maximum pixel clock
[   172.945] (--) NVIDIA(GPU-0): 
[   172.945] (--) NVIDIA(GPU-0): DFP-3: disconnected
[   172.945] (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
[   172.945] (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock
[   172.945] (--) NVIDIA(GPU-0): 
[   172.946] (--) NVIDIA(GPU-0): AOC 2460G5 (DFP-4): connected
[   172.946] (--) NVIDIA(GPU-0): AOC 2460G5 (DFP-4): Internal DisplayPort
[   172.946] (--) NVIDIA(GPU-0): AOC 2460G5 (DFP-4): 1440.0 MHz maximum pixel clock
[   172.946] (--) NVIDIA(GPU-0): 
[   172.948] (--) NVIDIA(GPU-0): DFP-5: disconnected
[   172.948] (--) NVIDIA(GPU-0): DFP-5: Internal TMDS
[   172.948] (--) NVIDIA(GPU-0): DFP-5: 165.0 MHz maximum pixel clock
[   172.948] (--) NVIDIA(GPU-0): 
[   172.948] (--) NVIDIA(GPU-0): DFP-6: disconnected
[   172.948] (--) NVIDIA(GPU-0): DFP-6: Internal DisplayPort
[   172.948] (--) NVIDIA(GPU-0): DFP-6: 1440.0 MHz maximum pixel clock
[   172.948] (--) NVIDIA(GPU-0): 
[   172.949] (--) NVIDIA(GPU-0): DFP-7: disconnected
[   172.949] (--) NVIDIA(GPU-0): DFP-7: Internal TMDS
[   172.949] (--) NVIDIA(GPU-0): DFP-7: 165.0 MHz maximum pixel clock
[   172.949] (--) NVIDIA(GPU-0): 

Running the game did not make any changes to the XOrg log.

I don't see any errors that couldn't be made to go away with a blacklist entry, but I'm not an expert.

Last edited by JontomXire (2025-12-23 13:50:41)

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 71,486

Re: nvidia-580xx-dkms packages not working properly.

Please use [code][/code] tags. Edit your post in this regard.
But xorg log and glxinfo look unsuspicious.

=> Some X11 compositor? picom? Ort what is your DE? XFCE? Cinnamon?

---

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

JontomXire

Member

Registered: 2025-03-04

Posts: 38

Re: nvidia-580xx-dkms packages not working properly.

I'm using XFCE. I'm not sure what you mean by compositor, but I did a search and found out how to disable it for XFCE. I did that and it made no difference.

libxfce4ui 4.20.2-1
libxfce4util 4.20.1-1
libxfce4windowing 4.20.4-2
xf86-input-libinput 1.5.0-1
xfce4-appfinder 4.20.0-2
xfce4-indicator-plugin 2.5.0-1
xfce4-notifyd 0.9.7-2
xfce4-panel 4.20.5-2
xfce4-power-manager 4.20.0-3
xfce4-pulseaudio-plugin 0.5.1-1
xfce4-screensaver 4.20.1-1
xfce4-screenshooter 1.11.3-3
xfce4-session 4.20.3-2
xfce4-settings 4.20.2-2
xfce4-terminal 1.1.5-2
xfce4-whiskermenu-plugin 2.10.0-2
xfconf 4.20.0-2
xfdesktop 4.20.1-3
xfwm4 4.20.0-2
xfwm4-themes 4.10.0-6

JontomXire

Member

Registered: 2025-03-04

Posts: 38

Re: nvidia-580xx-dkms packages not working properly.

Not sure if it helps, but the command being run is:

python3 /usr/share/lutris/bin/lutris-wrapper /home/me/.local/share/lutris/runners/wine/wine-ge-8-26-x86_64/bin/wine 0 0 /home/me/.local/share/lutris/runners/wine/wine-ge-8-26-x86_64/bin/wine "/home/me/Games/ascension-wow/drive_c/Ascension/Ascension Client/Ascension.exe"

Last edited by JontomXire (2025-12-23 14:02:28)

JontomXire

Member

Registered: 2025-03-04

Posts: 38

Re: nvidia-580xx-dkms packages not working properly.

Logs from when I actually run the game (I thought I had already uploaded these, sorry) are at https://github.com/user-attachments/fil … e-logs.txt.

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 71,486

Re: nvidia-580xx-dkms packages not working properly.

Is it only wine/proton?
Vulkan presentation problem?
Do you get this w/ https://wiki.archlinux.org/title/Steam/ … _emulation ?

Sometimes a terminal window will go transparent

Which terminal emulator specifically?

---

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

JontomXire

Member

Registered: 2025-03-04

Posts: 38

Re: nvidia-580xx-dkms packages not working properly.

I think the transparent terminal window was a different issue as you spotted previously:

There's an open issue w/ the 580.119 driver, https://bbs.archlinux.org/viewtopic.php?id=311055

On rolling back to 580.95.05 drivers from cache/archive the flickering windows and transparent terminal has stopped. I thought I had mentioned this, but clearly forgot. Apologies.

The problem is only with Lutris/wine. I am not sure if proton is involved, I have no idea what that is. Please note that the game ran fine before the driver shenanigans.

The launcher has built in DXVK support and yesterday I tried running without DXVK. No joy. I will try the PROTON_USE_WINED3D thing in a bit anyway.

I just ran another wine program in a different prefix and it started, albeit much much much slower than usual, but then I usually run it under my Ubuntu dual boot for work. Just in case it is just a delayed startup issue, I am going to run the game again and leave it for some time to see if it appears.

JontomXire

Member

Registered: 2025-03-04

Posts: 38

Re: nvidia-580xx-dkms packages not working properly.

After 15 minutes, the game still had not appeared, so not just delayed startup. So, something very specific to Lutris wine. I don't have any other Lutris games to test.

I tried the PROTON_USE_WINED3D thing and it didn't work. The full command was:

PROTON_USE_WINED3D=1 python3 /usr/share/lutris/bin/lutris-wrapper /home/me/.local/share/lutris/runners/wine/wine-ge-8-26-x86_64/bin/wine 0 0 /home/me/.local/share/lutris/runners/wine/wine-ge-8-26-x86_64/bin/wine "/home/me/Games/ascension-wow/drive_c/Ascension/Ascension Client/Ascension.exe"

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 71,486

Re: nvidia-580xx-dkms packages not working properly.

Do you have a log from that run?

---

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