You are not logged in.

#1 2018-05-27 17:13:11

ranjak
Member
Registered: 2014-10-16
Posts: 9

[SOLVED] kodi standalone service broken by xorg-1.20?

EDIT 2018.06.03: this was solved by xorg-server 1.20.0-5. Original post below.

Hi,

I have a unit file that I use to run kodi-standalone under a dedicated user on its own vt, it's basically the same as https://aur.archlinux.org/packages/kodi … e-service/ except I set it to tty3 instead of tty1 (because it's on my desktop machine and I want it to coexist with my DE).

It seems the update to xorg-1.20 has broken it, now X fails to start with "no screens found" when starting the service.

By the looks of it, the crux of the problem is here:

[  1071.581] (++) using VT number 3

[  1071.581] (--) controlling tty is VT number 3, auto-enabling KeepTty
[  1071.584] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c6
[  1071.584] (II) xfree86: Adding drm device (/dev/dri/card0)
[  1071.585] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 paused 1
[  1071.585] (EE) Error systemd-logind returned paused fd for drm node
[  1071.585] (II) systemd-logind: releasing fd for 226:0
[  1071.587] (--) PCI:*(1@0:0:0) 10de:1c02:3842:6160 rev 161, Mem @ 0xfa000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/131072

whereas a successful run of X (my usual desktop login) looks like that:

[    64.548] (++) using VT number 2

[    64.551] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c5
[    64.551] (II) xfree86: Adding drm device (/dev/dri/card0)
[    64.552] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 12 paused 0
[    64.553] (**) OutputClass "nvidia" ModulePath extended to "/usr/lib/nvidia/xorg,/usr/lib/xorg/modules,/usr/lib/xorg/modules"
[    64.553] (**) OutputClass "nvidia" setting /dev/dri/card0 as PrimaryGPU
[    64.554] (--) PCI:*(1@0:0:0) 10de:1c02:3842:6160 rev 161, Mem @ 0xfa000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/131072

The failing X run doesn't get to the OutputClass thing, I guess as a result of

[  1071.585] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 paused 1
[  1071.585] (EE) Error systemd-logind returned paused fd for drm node

I did some digging, but the stuff I found seemed unrelated.

Here's the full Xorg log generated when the service starts:

[  1071.580] 
X.Org X Server 1.20.0
X Protocol Version 11, Revision 0
[  1071.580] Build Operating System: Linux Arch Linux
[  1071.580] Current Operating System: Linux hector-pc 4.16.11-1-ARCH #1 SMP PREEMPT Tue May 22 21:40:27 UTC 2018 x86_64
[  1071.580] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=879122d3-df53-496a-9001-c24258434ff6 rw quiet
[  1071.580] Build Date: 16 May 2018  05:24:07PM
[  1071.580]  
[  1071.580] Current version of pixman: 0.34.0
[  1071.580] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[  1071.580] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  1071.580] (==) Log file: "/var/lib/kodi/.local/share/xorg/Xorg.2.log", Time: Sun May 27 18:35:59 2018
[  1071.580] (==) Using config directory: "/etc/X11/xorg.conf.d"
[  1071.580] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  1071.580] (==) No Layout section.  Using the first Screen section.
[  1071.580] (==) No screen section available. Using defaults.
[  1071.580] (**) |-->Screen "Default Screen Section" (0)
[  1071.580] (**) |   |-->Monitor "<default monitor>"
[  1071.580] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[  1071.580] (==) Automatically adding devices
[  1071.580] (==) Automatically enabling devices
[  1071.580] (==) Automatically adding GPU devices
[  1071.580] (==) Automatically binding GPU devices
[  1071.580] (==) Max clients allowed: 256, resource mask: 0x1fffff
[  1071.580] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi".
[  1071.580] 	Entry deleted from font path.
[  1071.580] 	(Run 'mkfontdir' on "/usr/share/fonts/100dpi").
[  1071.580] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi".
[  1071.580] 	Entry deleted from font path.
[  1071.580] 	(Run 'mkfontdir' on "/usr/share/fonts/75dpi").
[  1071.580] (==) FontPath set to:
	/usr/share/fonts/misc,
	/usr/share/fonts/TTF,
	/usr/share/fonts/OTF,
	/usr/share/fonts/Type1
[  1071.580] (**) ModulePath set to "/usr/lib/nvidia/xorg,/usr/lib/xorg/modules"
[  1071.580] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[  1071.580] (II) Module ABI versions:
[  1071.580] 	X.Org ANSI C Emulation: 0.4
[  1071.580] 	X.Org Video Driver: 24.0
[  1071.580] 	X.Org XInput driver : 24.1
[  1071.580] 	X.Org Server Extension : 10.0
[  1071.581] (++) using VT number 3

[  1071.581] (--) controlling tty is VT number 3, auto-enabling KeepTty
[  1071.584] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c6
[  1071.584] (II) xfree86: Adding drm device (/dev/dri/card0)
[  1071.585] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 paused 1
[  1071.585] (EE) Error systemd-logind returned paused fd for drm node
[  1071.585] (II) systemd-logind: releasing fd for 226:0
[  1071.587] (--) PCI:*(1@0:0:0) 10de:1c02:3842:6160 rev 161, Mem @ 0xfa000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/131072
[  1071.587] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[  1071.587] (II) LoadModule: "glx"
[  1071.587] (II) Loading /usr/lib/nvidia/xorg/libglx.so
[  1071.591] (II) Module glx: vendor="NVIDIA Corporation"
[  1071.591] 	compiled for 4.0.2, module version = 1.0.0
[  1071.591] 	Module class: X.Org Server Extension
[  1071.591] (II) NVIDIA GLX Module  390.59  Wed May  9 21:54:15 PDT 2018
[  1071.591] (==) Matched nouveau as autoconfigured driver 0
[  1071.591] (==) Matched nv as autoconfigured driver 1
[  1071.591] (==) Matched modesetting as autoconfigured driver 2
[  1071.592] (==) Matched fbdev as autoconfigured driver 3
[  1071.592] (==) Matched vesa as autoconfigured driver 4
[  1071.592] (==) Assigned the driver to the xf86ConfigLayout
[  1071.592] (II) LoadModule: "nouveau"
[  1071.592] (WW) Warning, couldn't open module nouveau
[  1071.592] (EE) Failed to load module "nouveau" (module does not exist, 0)
[  1071.592] (II) LoadModule: "nv"
[  1071.592] (WW) Warning, couldn't open module nv
[  1071.592] (EE) Failed to load module "nv" (module does not exist, 0)
[  1071.592] (II) LoadModule: "modesetting"
[  1071.592] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[  1071.593] (II) Module modesetting: vendor="X.Org Foundation"
[  1071.593] 	compiled for 1.20.0, module version = 1.20.0
[  1071.593] 	Module class: X.Org Video Driver
[  1071.593] 	ABI class: X.Org Video Driver, version 24.0
[  1071.593] (II) LoadModule: "fbdev"
[  1071.593] (WW) Warning, couldn't open module fbdev
[  1071.593] (EE) Failed to load module "fbdev" (module does not exist, 0)
[  1071.593] (II) LoadModule: "vesa"
[  1071.593] (WW) Warning, couldn't open module vesa
[  1071.593] (EE) Failed to load module "vesa" (module does not exist, 0)
[  1071.593] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[  1071.765] (WW) Falling back to old probe method for modesetting
[  1071.765] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[  1071.765] (EE) Screen 0 deleted because of no matching config section.
[  1071.766] (II) UnloadModule: "modesetting"
[  1071.766] (EE) Device(s) detected, but none match those in the config file.
[  1071.766] (EE) 
Fatal server error:
[  1071.766] (EE) no screens found(EE) 
[  1071.766] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[  1071.766] (EE) Please also check the log file at "/var/lib/kodi/.local/share/xorg/Xorg.2.log" for additional information.
[  1071.766] (EE) 
[  1072.027] (EE) Server terminated with error (1). Closing log file.

Note that the

[  1071.580] (**) ModulePath set to "/usr/lib/nvidia/xorg,/usr/lib/xorg/modules"

is something I manually added to /etc/X11/xorg.conf.d as a dirty fix attempt inspired by https://bugs.archlinux.org/task/53090, which is likely unrelated anyway, but obviously it didn't help.

I'd appreciate any help please smile

Last edited by ranjak (2018-06-03 16:50:13)

Offline

#2 2018-05-28 00:08:25

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 9,527
Website

Re: [SOLVED] kodi standalone service broken by xorg-1.20?

Please let me know when you identify a solution and if the package needs to be tweaked.


CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs • 1.21 JIGOWATTS!

Offline

#3 2018-05-28 01:28:47

loqs
Member
Registered: 2014-03-06
Posts: 5,473

Re: [SOLVED] kodi standalone service broken by xorg-1.20?

Is the issue still present with xorg-server 1.20.0-5 from testing?

Offline

#4 2018-06-02 09:47:52

ranjak
Member
Registered: 2014-10-16
Posts: 9

Re: [SOLVED] kodi standalone service broken by xorg-1.20?

loqs wrote:

Is the issue still present with xorg-server 1.20.0-5 from testing?

It is, and the logs are basically the same as before, so I guess the cause of the failure hasn't changed.
There is one difference though: now the Xorg.2.log is located in /var/log instead of the .local/share/xorg directory in the home dir of my kodi user.

Offline

#5 2018-06-02 15:40:28

loqs
Member
Registered: 2014-03-06
Posts: 5,473

Re: [SOLVED] kodi standalone service broken by xorg-1.20?

Offline

#6 2018-06-03 16:48:04

ranjak
Member
Registered: 2014-10-16
Posts: 9

Re: [SOLVED] kodi standalone service broken by xorg-1.20?

Never mind, 1.20.0-5 actually fixed the problem.
I had to remove the "vt3" argument at the end of the command line in my unit file.

ExecStart=/usr/bin/xinit /usr/bin/kodi-standalone -- :2 -nolisten tcp

instead of

ExecStart=/usr/bin/xinit /usr/bin/kodi-standalone -- :2 -nolisten tcp vt3

I originally didn't have that "vt3" prior to xorg 1.20, I had removed it from the original unit file, but I added it back for testing when the service broke with 1.20. And I had forgotten why I had removed it in the first place... I really should use git to track my unit files, config files and such roll

So, problem solved as far as I'm concerned. Thanks for your help!

Offline

#7 2018-06-03 20:57:57

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 9,527
Website

Re: [SOLVED] kodi standalone service broken by xorg-1.20?

@ranjak - The service ships with this line:

ExecStart=/usr/bin/xinit /usr/bin/kodi-standalone -- :0 -nolisten tcp vt1

I received a report of another user running nvidia-340xx who has a broken system with the new xorg packages.  Can you please post the entire kodi.service you modified that works with your setup?

Last edited by graysky (2018-06-10 13:04:56)


CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs • 1.21 JIGOWATTS!

Offline

#8 2018-06-10 12:47:06

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 9,527
Website

Re: [SOLVED] kodi standalone service broken by xorg-1.20?

@ranjak - Any word?


CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs • 1.21 JIGOWATTS!

Offline

#9 2018-06-10 15:07:56

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 4,981

Re: [SOLVED] kodi standalone service broken by xorg-1.20?

@graysky nvidia-340xx was in general broken with Xorg 1.20, a fixed driver is currently in testing.

Offline

#10 2018-06-10 16:20:23

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 9,527
Website

Re: [SOLVED] kodi standalone service broken by xorg-1.20?

@V1del - Thanks for the info.  The person who reported it issue to me took your advice and confirmed the fix with those packages.


CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs • 1.21 JIGOWATTS!

Offline

Board footer

Powered by FluxBB