X servers fail to start after nvidia 361.18 & other upgrades

keepitsimpleengineer · 2016-02-04 16:51:04

I have two archlinux x86_64 systems, my workstation (Intel) and a HTPC (amd) mythtv client. I use graysky's -ck kernels and also retain the archlinux kernels.

After upgrading the archlinux kernels from 4.3.3-3 to 4.4.1-2 and upgrading NVIDIA from 358.16-3 to 361.18-3, nvidia-ck* from 358.16-2 to 361.18-1, and nvidia-utils from 358.16-1 to 358.18-2, both x servers fail to run on either kernel, shutting down with no obvious error messages. The -ck kernel was not upgraded, and is 4.3.5-1-ck.

The x servers fail with both the archlinux and -ck kernels. Downgrading resolves the x server fail problem... .. .

For the HTPC (amd)...

core/linux             4.3.3-3      4.4.1-2        0.41 MiB      57.38 MiB
extra/nvidia           358.16-3     361.18-3       1.05 MiB       5.58 MiB
repo-ck/nvidia-ck-k10  358.16-2     361.18-1       1.04 MiB       5.58 MiB
extra/nvidia-utils     358.16-1     361.18-2      12.92 MiB      24.34 MiB
community/r8168        8.041.00-2   8.041.00-4     0.00 MiB       0.14 MiB

For the Intel system… .. .
Xorg.0.log @ http://pastebin.com/gK8NUYnH
xorg.conf @ http://pastebin.com/M0L8FSia
journalctl -k -b -1 @ http://pastebin.com/FQQpizmM
journalctl -b -1 @ http://pastebin.com/jx12XvNx

Unsure of what to do about this... .. .

Added an Xorg.0.log for successful x server start @ http://pastebin.com/inhq57BE

Last edited by keepitsimpleengineer (2016-02-05 21:51:54)

jasonwryan · 2016-02-04 16:58:56

On the Intel machine at least (I didn't look at the other log), X runs perfectly fine: look at the last line of the log. Your issue is whatever it is supposed to be doing; running a DM, presumably.

Not a Kernel issue, moving to Apps and DEs...

keepitsimpleengineer · 2016-02-05 22:08:21

Looking at the journalctl and Xorg.0.log files, it can be seen where the divergence started for the failed start of the x server. Here extracted from the pastebin and a successful start with downgraded packages.
Notes: This system boots to the console, where the x server is started with "startxfce4"
and there is from time to time a second keyboard connected to the system
and on the HTPC (amd) system which also failed the hardware stays the same.

FAIL  xorg.0.log
Feb 03 11:20:10 KISE-005 kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  361.18  Sat Jan  9 20:45:38 PST 2016
Feb 03 11:20:10 KISE-005 kernel: nvidia-modeset: Allocated GPU:0 (GPU-e29f907a-f2c7-1b05-54e8-62dfb4296781) @ PCI:0000:01:00.0
Feb 03 11:20:10 KISE-005 kernel: nvidia-modeset: Allocated GPU:1 (GPU-4b22ebfa-3957-c64f-ba91-0964fe217b71) @ PCI:0000:02:00.0
<---------------What happened here?------->
Feb 03 11:20:12 KISE-005 kernel: nvidia-modeset: Freed GPU:0 (GPU-e29f907a-f2c7-1b05-54e8-62dfb4296781) @ PCI:0000:01:00.0
Feb 03 11:20:12 KISE-005 kernel: nvidia-modeset: Freed GPU:1 (GPU-4b22ebfa-3957-c64f-ba91-0964fe217b71) @ PCI:0000:02:00.0

SUCCEED Xorg.0.log
Feb 05 13:01:26 KISE-005 kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  358.16  Mon Nov 16 
Feb 05 13:01:26 KISE-005 kernel: nvidia-modeset: Allocated GPU:0 (GPU-e29f907a-f2c7-1b05-54e8-62dfb4296781) @ PCI:0000:01:00.0
Feb 05 13:01:26 KISE-005 kernel: nvidia-modeset: Allocated GPU:1 (GPU-4b22ebfa-3957-c64f-ba91-0964fe217b71) @ PCI:0000:02:00.0
<---------------Normal start proceeding----------->
Feb 05 13:01:27 KISE-005 dbus-daemon[452]: Activating service name='org.xfce.Xfconf'

FAIL    journalctl
[    16.402] (**) Option "config_info" "udev:/sys/devices/platform/eeepc-wmi/input/input17/event14"
[    16.402] (II) XINPUT: Adding extended input device "Eee PC WMI hotkeys" (type: KEYBOARD, id 10)
[    16.402] (**) Option "xkb_rules" "evdev"
[    16.403] (II) config/udev: Adding input device PC Speaker (/dev/input/event5)
[    16.403] (II) No input driver specified, ignoring this device.
[    16.403] (II) This device may have been added with another device file.
<------------- What happened here?---------->
[    16.542] (II) evdev: Eee PC WMI hotkeys: Close
[    16.542] (II) UnloadModule: "evdev"
[    16.542] (II) systemd-logind: releasing fd for 13:78
[    16.552] (II) evdev: LITEON Technology USB Keyboard: Close
[    16.552] (II) UnloadModule: "evdev"
[    16.552] (II) systemd-logind: releasing fd for 13:68
[    16.565] (II) evdev: Razer  Razer Abyssus: Close
[    16.565] (II) UnloadModule: "evdev"
[    16.565] (II) systemd-logind: releasing fd for 13:66
[    16.578] (II) evdev: Power Button: Close
[    16.578] (II) UnloadModule: "evdev"
[    16.578] (II) systemd-logind: releasing fd for 13:64
[    16.584] (II) evdev: Power Button: Close
[    16.584] (II) UnloadModule: "evdev"
[    16.584] (II) systemd-logind: releasing fd for 13:65
[    18.187] (II) NVIDIA(GPU-0): Deleting GPU-0
[    18.187] (II) NVIDIA(GPU-1): Renaming GPU-1 to GPU-0
[    18.187] (II) NVIDIA(GPU-0): Deleting GPU-0
[    18.259] (II) Server terminated successfully (0). Closing log file.

SUCCEED journalctl
[    17.250] (II) config/udev: Adding input device Eee PC WMI hotkeys (/dev/input/event14)
<----------------This is a 2nd keyboard occasionally on the system--------->
[    17.250] (**) Eee PC WMI hotkeys: Applying InputClass "evdev keyboard catchall"
[    17.251] (II) systemd-logind: got fd for /dev/input/event14 13:78 fd 35 paused 0
[    17.251] (II) Using input driver 'evdev' for 'Eee PC WMI hotkeys'
[    17.251] (**) Eee PC WMI hotkeys: always reports core events
[    17.251] (**) evdev: Eee PC WMI hotkeys: Device: "/dev/input/event14"
[    17.251] (--) evdev: Eee PC WMI hotkeys: Vendor 0 Product 0
[    17.251] (--) evdev: Eee PC WMI hotkeys: Found keys
[    17.251] (II) evdev: Eee PC WMI hotkeys: Configuring as keyboard
<-------------------finished 2nd keyboard------>
[    17.251] (**) Option "config_info" "udev:/sys/devices/platform/eeepc-wmi/input/input17/event14"
[    17.251] (II) XINPUT: Adding extended input device "Eee PC WMI hotkeys" (type: KEYBOARD, id 10)
[    17.251] (**) Option "xkb_rules" "evdev"
[    17.251] (II) config/udev: Adding input device PC Speaker (/dev/input/event5)
[    17.251] (II) No input driver specified, ignoring this device.
[    17.251] (II) This device may have been added with another device file.
<-----------------Thus is start of successful x server----------->
[    19.386] (--) NVIDIA(GPU-0): CRT-0: disconnected
[    19.386] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
[    19.386] (--) NVIDIA(GPU-0): 
[    19.388] (--) NVIDIA(GPU-0): CRT-1: disconnected
[    19.388] (--) NVIDIA(GPU-0): CRT-1: 400.0 MHz maximum pixel clock
[    19.388] (--) NVIDIA(GPU-0): 
[    19.401] (--) NVIDIA(GPU-0): HP LP3065 (DFP-0): connected
[    19.401] (--) NVIDIA(GPU-0): HP LP3065 (DFP-0): Internal TMDS
[    19.401] (--) NVIDIA(GPU-0): HP LP3065 (DFP-0): 330.0 MHz maximum pixel clock
[    19.401] (--) NVIDIA(GPU-0): 
[    19.401] (--) NVIDIA(GPU-0): DFP-1: disconnected
[    19.401] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[    19.401] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[    19.401] (--) NVIDIA(GPU-0): 
[    19.403] (--) NVIDIA(GPU-0): DFP-2: disconnected
[    19.403] (--) NVIDIA(GPU-0): DFP-2: Internal TMDS
[    19.403] (--) NVIDIA(GPU-0): DFP-2: 330.0 MHz maximum pixel clock
[    19.403] (--) NVIDIA(GPU-0): 
[    19.482] (--) NVIDIA(GPU-0): CRT-0: disconnected
...and more not shown

I could sure use some help figuring this out... .. .

keepitsimpleengineer · 2016-02-05 23:13:57

From Xorg.0.log; could this be the problem?

Apparentlythe "libglvnd: the GL Vendor-Neutral Dispatch library" is a new feature in nvidia drivers,
https://github.com/NVIDIA/libglvnd/blob … x11glvnd.h

[    16.262] (II) Loading sub module "x11glvnd"
[    16.262] (II) LoadModule: "x11glvnd"
[    16.262] (WW) Warning, couldn't open module x11glvnd
[    16.262] (II) UnloadModule: "x11glvnd"
[    16.262] (II) Unloading x11glvnd
[    16.262] (II) x11glvnd Loading

keepitsimpleengineer · 2016-02-06 00:30:11

Ran /usr/bin/nvidia-bug-report.sh which produced this extract:

nvidia-settings -q all:


ERROR: libGLX.so.0: cannot open shared object file: No such file or
       directory
       libGLX.so.0: cannot open shared object file: No such file or
       directory
       libGLX.so.0: cannot open shared object file: No such file or
       directory
       libGLX.so.0: cannot open shared object file: No such file or
       directory


ERROR: A problem occured when loading the GUI library. Please check your
       installation and library path. You may need to specify this library
       when calling nvidia-settings. Please run `nvidia-settings --help`
       for usage information.

Update: Bug report filed: https://bugs.archlinux.org/index.php?do … k_id=48053

Last edited by keepitsimpleengineer (2016-02-08 15:32:44)

Scimmia · 2016-02-06 06:00:19

Sounds like a partial update to me.

kord · 2016-02-13 18:30:49

Hi,

Sorry for hijacking the thread but I am facing the same issue - after upgrading Nvidia (allong with needed packages) my X fails to start. This happens both on 361.18 and 361.28 regardless of kernel I am using (tested on 4.3 and 4.4). For the sake of testing I've even tried running Nvidia-beta from AUR, still same issue.. When I am trying to invoke X manually, it throws error that could not connect to display, connection refused.. I'm on KDE with sddm, but even if I disable sddm and try to invoke X with startkde in xinitrc issue is still the same.. If i downgrade Nvidia + kernel X is working fine again.. I am not sure why thou, as I don't see any difference in the config that would cause this kind of issue.. Below are my xorg log and journalctl:

journalctl -b -1 http://pastebin.com/g6hkBady
journalctl -k -b -1 http://pastebin.com/msjbbXCv
Xorg.0.log http://pastebin.com/9JBFKTL1

I would appreciate any kind of help..

Arch Linux

#1 2016-02-04 16:51:04

X servers fail to start after nvidia 361.18 & other upgrades

#2 2016-02-04 16:58:56

Re: X servers fail to start after nvidia 361.18 & other upgrades

#3 2016-02-05 22:08:21

Re: X servers fail to start after nvidia 361.18 & other upgrades

#4 2016-02-05 23:13:57

Re: X servers fail to start after nvidia 361.18 & other upgrades

#5 2016-02-06 00:30:11

Re: X servers fail to start after nvidia 361.18 & other upgrades

#6 2016-02-06 06:00:19

Re: X servers fail to start after nvidia 361.18 & other upgrades

#7 2016-02-13 18:30:49

Re: X servers fail to start after nvidia 361.18 & other upgrades

Board footer