You are not logged in.

Pages: 1

#1 2023-03-15 16:40:31

nerdnils
Member
Registered: 2017-03-04
Posts: 32

[solved] XServer crashes

Hi there,

since a Syu a few days ago I can not start games in openbox using https://aur.archlinux.org/packages/attract it worked fine before the updates. Whole X-Server crashes.
Updated among other stuff was the kernel:
linux (6.2.2.arch1-1 -> 6.2.5.arch1-1) and after that to 6.2.6 (same issue on both)
but not the graphics driver(nvidia). dmesg shows nothing when X crashes but it shows that all usb-HDDs are disconnected and reconnected when it happens.
I can not find any logfile for openbox which is started using agetty autologin. Attract output was logged but looks fine, it shows what to start
and output just ends when the X-Server crashes.
Xorg-log shows this when it crashes:

[   394.696] (II) event1  - Power Button: device removed
[   394.722] (II) event0  - Power Button: device removed
[   394.749] (II) event3  - Logitech USB Keyboard: device removed
[   394.776] (II) event5  - Logitech USB Keyboard Consumer Control: device removed
[   394.802] (II) event6  - Logitech USB Keyboard System Control: device removed
[   394.829] (II) event7  - HID 1241:1122: device removed
[   394.856] (II) event8  - Razer Razer Basilisk V2: device removed
[   394.882] (II) event11 - Razer Razer Basilisk V2: device removed
[   394.922] (II) event2  - Ultimarc I-PAC Ultimarc I-PAC: device removed
[   394.949] (II) event4  - Ultimarc I-PAC 2 Ultimarc I-PAC 2: device removed
[   394.962] (II) event9  - Razer Razer Basilisk V2 Keyboard: device removed
[   406.500] (--) NVIDIA(GPU-0): DFP-0: disconnected
[   406.500] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[   406.500] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[   406.500] (--) NVIDIA(GPU-0): 
[   406.500] (--) NVIDIA(GPU-0): DFP-1: disconnected
[   406.500] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[   406.500] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[   406.500] (--) NVIDIA(GPU-0): 
[   406.544] (--) NVIDIA(GPU-0): Samsung S27B350 (DFP-2): connected
[   406.544] (--) NVIDIA(GPU-0): Samsung S27B350 (DFP-2): Internal TMDS
[   406.544] (--) NVIDIA(GPU-0): Samsung S27B350 (DFP-2): 600.0 MHz maximum pixel clock
[   406.544] (--) NVIDIA(GPU-0): 
[   406.544] (--) NVIDIA(GPU-0): DFP-3: disconnected
[   406.544] (--) NVIDIA(GPU-0): DFP-3: Internal DisplayPort
[   406.544] (--) NVIDIA(GPU-0): DFP-3: 1440.0 MHz maximum pixel clock
[   406.544] (--) NVIDIA(GPU-0): 
[   406.544] (--) NVIDIA(GPU-0): DFP-4: disconnected
[   406.544] (--) NVIDIA(GPU-0): DFP-4: Internal TMDS
[   406.544] (--) NVIDIA(GPU-0): DFP-4: 165.0 MHz maximum pixel clock
[   406.544] (--) NVIDIA(GPU-0): 
[   406.544] (--) NVIDIA(GPU-0): DFP-5: disconnected
[   406.544] (--) NVIDIA(GPU-0): DFP-5: Internal DisplayPort
[   406.544] (--) NVIDIA(GPU-0): DFP-5: 1440.0 MHz maximum pixel clock
[   406.544] (--) NVIDIA(GPU-0): 
[   406.544] (--) NVIDIA(GPU-0): DFP-6: disconnected
[   406.544] (--) NVIDIA(GPU-0): DFP-6: Internal TMDS
[   406.544] (--) NVIDIA(GPU-0): DFP-6: 165.0 MHz maximum pixel clock
[   406.544] (--) NVIDIA(GPU-0): 
[   406.562] (II) NVIDIA(0): Setting mode "DFP-2:nvidia-auto-select"
[   406.594] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[   406.594] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[   406.594] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[   406.594] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[   406.594] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[   406.594] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[   406.594] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[   406.594] (II) NVIDIA(0):     Config Options in the README.
[   406.628] (II) event1  - Power Button: is tagged by udev as: Keyboard
[   406.628] (II) event1  - Power Button: device is a keyboard
[   406.629] (II) event0  - Power Button: is tagged by udev as: Keyboard
[   406.629] (II) event0  - Power Button: device is a keyboard
[   406.630] (II) event3  - Logitech USB Keyboard: is tagged by udev as: Keyboard
[   406.630] (II) event3  - Logitech USB Keyboard: device is a keyboard
[   406.631] (II) event5  - Logitech USB Keyboard Consumer Control: is tagged by udev as: Keyboard
[   406.631] (II) event5  - Logitech USB Keyboard Consumer Control: device is a keyboard
[   406.632] (II) event6  - Logitech USB Keyboard System Control: is tagged by udev as: Keyboard
[   406.632] (II) event6  - Logitech USB Keyboard System Control: device is a keyboard
[   406.633] (II) event7  - HID 1241:1122: is tagged by udev as: Mouse
[   406.633] (II) event7  - HID 1241:1122: device is a pointer
[   406.634] (II) event8  - Razer Razer Basilisk V2: is tagged by udev as: Mouse
[   406.634] (II) event8  - Razer Razer Basilisk V2: device is a pointer
[   406.636] (II) event9  - Razer Razer Basilisk V2 Keyboard: is tagged by udev as: Keyboard
[   406.636] (II) event9  - Razer Razer Basilisk V2 Keyboard: device is a keyboard
[   406.637] (II) event11 - Razer Razer Basilisk V2: is tagged by udev as: Keyboard
[   406.637] (II) event11 - Razer Razer Basilisk V2: device is a keyboard
[   406.638] (II) event2  - Ultimarc I-PAC Ultimarc I-PAC: is tagged by udev as: Keyboard
[   406.638] (II) event2  - Ultimarc I-PAC Ultimarc I-PAC: device is a keyboard
[   406.639] (II) event4  - Ultimarc I-PAC 2 Ultimarc I-PAC 2: is tagged by udev as: Keyboard
[   406.639] (II) event4  - Ultimarc I-PAC 2 Ultimarc I-PAC 2: device is a keyboard

Whole Xorg-Logfile can be found here: http://ix.io/4qUz

Everything is fine when run over another X-Server changing to the user(I have this agetty with autologin on tty1 and an sddm on tty2) but I need to fix this one.

Any ideas are appreciated, please tell me if further information is need

Last edited by nerdnils (2023-03-16 18:58:53)

Offline

#2 2023-03-16 00:16:07

jonno2002
Member
Registered: 2016-11-21
Posts: 684

Re: [solved] XServer crashes

have you re-compiled the attract aur package after the system update ?
does the problem go away if you downgrade the kernel 6.2.2 ?

Offline

#3 2023-03-16 05:07:07

nerdnils
Member
Registered: 2017-03-04
Posts: 32

Re: [solved] XServer crashes

jonno2002 wrote:

have you re-compiled the attract aur package after the system update ?
does the problem go away if you downgrade the kernel 6.2.2 ?

Yes, attract was recompiled. And attract still works fine in the other session. I don't understand what the problem in the openbox-session is.

I downgraded linux and linux-headers to 6.2.2-arch2. Reinstalled nvidia to get the right modules but no X starts anymore at all.
dmesg http://ix.io/4qWw
Xorg.0.log: http://ix.io/4qWx

Offline

#4 2023-03-16 07:09:30

jonno2002
Member
Registered: 2016-11-21
Posts: 684

Re: [solved] XServer crashes

you will need nvidia-dkms with the older kernel

Offline

#5 2023-03-16 07:57:08

seth
Member
Registered: 2012-09-03
Posts: 51,186

Re: [solved] XServer crashes

I doubt this is an Xorg problem, 1 log doesn't indicate problems (looks like a running X11 server) and the 2nd one is because you trashed the nvidia driver
More likely https://bbs.archlinux.org/post.php?tid=284299

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

Online

#6 2023-03-16 18:57:05

nerdnils
Member
Registered: 2017-03-04
Posts: 32

Re: [solved] XServer crashes

seth wrote:

I doubt this is an Xorg problem, 1 log doesn't indicate problems (looks like a running X11 server) and the 2nd one is because you trashed the nvidia driver
More likely https://bbs.archlinux.org/post.php?tid=284299

And the oscar goes to… thank you @seth

Offline

Pages: 1

Board footer

Powered by FluxBB