You are not logged in.

#1 2015-10-18 08:10:33

_pheinrich_
Member
Registered: 2014-05-26
Posts: 53

kodi.service fails on boot

Hi,

I have set up my new HTPC and installed kodi. Everything is good so far.
I have not installed a DE.

After that I have installed the kodi-standalone-service from AUR.
Starting that with

sudo systemctl start kod

brings up kodi. But enabling it and restarting the machine does not work.
I get some X lines flickering and see a login prompt.

[     0.981] X Protocol Version 11, Revision 0
[     0.981] Build Operating System: Linux 4.0.4-2-ARCH x86_64 
[     0.981] Current Operating System: Linux ARCH_MEDIA 4.2.3-1-ARCH #1 SMP PREEMPT Sat Oct 3 18:52:50 CEST 2015 x86_64
[     0.981] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=9c410d04-1401-4b97-9803-c189ec7c2875 rw quiet
[     0.981] Build Date: 17 July 2015  05:38:19PM
[     0.981]  
[     0.981] Current version of pixman: 0.32.8
[     0.981]    Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
[     0.981] Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[     0.981] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Oct 18 11:40:32 2015
[     0.981] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[     0.982] (==) No Layout section.  Using the first Screen section.
[     0.982] (==) No screen section available. Using defaults.
[     0.982] (**) |-->Screen "Default Screen Section" (0)
[     0.982] (**) |   |-->Monitor "<default monitor>"
[     0.982] (==) No monitor specified for screen "Default Screen Section".
        Using a default monitor configuration.
[     0.982] (==) Automatically adding devices
[     0.982] (==) Automatically enabling devices
[     0.982] (==) Automatically adding GPU devices
[     0.983] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[     0.983]    Entry deleted from font path.
[     0.983] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[     0.983]    Entry deleted from font path.
[     0.983]    (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[     0.983] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[     0.983]    Entry deleted from font path.
[     0.983]    (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[     0.984] (==) FontPath set to:
        /usr/share/fonts/misc/,
        /usr/share/fonts/TTF/,
        /usr/share/fonts/OTF/
[     0.984] (==) ModulePath set to "/usr/lib/xorg/modules"
[     0.984] (II) The server relies on udev to provide the list of input devices.
        If no devices become available, reconfigure udev or disable AutoAddDevices.
[     0.984] (II) Loader magic: 0x817d60
[     0.984] (II) Module ABI versions:
[     0.984]    X.Org ANSI C Emulation: 0.4
[     0.984]    X.Org Video Driver: 19.0
[     0.984]    X.Org XInput driver : 21.1
[     0.984]    X.Org Server Extension : 9.0
[     0.984] (EE) systemd-logind: failed to get session: PID 255 does not belong to any known session
[     0.985] (--) PCI:*(0:1:0:0) 10de:05e2:10de:0585 rev 161, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, 0xf4000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[     0.985] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[     0.985] (II) LoadModule: "glx"
[     0.987] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[     1.068] (II) Module glx: vendor="NVIDIA Corporation"
[     1.068]    compiled for 4.0.2, module version = 1.0.0
[     1.068]    Module class: X.Org Server Extension
[     1.068] (II) NVIDIA GLX Module  340.93  Wed Aug 19 16:23:51 PDT 2015
[     1.069] (==) Matched nouveau as autoconfigured driver 0
[     1.069] (==) Matched nv as autoconfigured driver 1
[     1.069] (==) Matched modesetting as autoconfigured driver 2
[     1.069] (==) Matched fbdev as autoconfigured driver 3
[     1.069] (==) Matched vesa as autoconfigured driver 4
[     1.069] (==) Assigned the driver to the xf86ConfigLayout
[     1.069] (II) LoadModule: "nouveau"
[     1.069] (WW) Warning, couldn't open module nouveau
[     1.069] (II) UnloadModule: "nouveau"
[     1.069] (II) Unloading nouveau
[     1.069] (EE) Failed to load module "nouveau" (module does not exist, 0)
[     1.069] (II) LoadModule: "nv"
[     1.069] (WW) Warning, couldn't open module nv
[     1.069] (II) UnloadModule: "nv"
[     1.069] (II) Unloading nv
[     1.069] (EE) Failed to load module "nv" (module does not exist, 0)
[     1.069] (II) LoadModule: "modesetting"
[     1.069] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[     1.070] (II) Module modesetting: vendor="X.Org Foundation"
[     1.070]    compiled for 1.17.2, module version = 1.17.2
[     1.070]    Module class: X.Org Video Driver
[     1.070]    ABI class: X.Org Video Driver, version 19.0
[     1.070] (II) LoadModule: "fbdev"
[     1.070] (WW) Warning, couldn't open module fbdev
[     1.070] (II) UnloadModule: "fbdev"
[     1.070] (II) Unloading fbdev
[     1.070] (EE) Failed to load module "fbdev" (module does not exist, 0)
[     1.070] (II) LoadModule: "vesa"
[     1.070] (WW) Warning, couldn't open module vesa
[     1.070] (II) UnloadModule: "vesa"
[     1.070] (II) Unloading vesa
[     1.070] (EE) Failed to load module "vesa" (module does not exist, 0)
[     1.070] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[     1.070] (++) using VT number 7

[     1.070] (--) controlling tty is VT number 7, auto-enabling KeepTty
[     1.082] (WW) Falling back to old probe method for modesetting
[     1.082] (EE) Screen 0 deleted because of no matching config section.
[     1.082] (II) UnloadModule: "modesetting"
[     1.082] (EE) Device(s) detected, but none match those in the config file.
[     1.082] (EE) 
Fatal server error:
[     1.082] (EE) no screens found(EE) 
[     1.082] (EE) 
Please consult the The X.Org Foundation support 
         at http://wiki.x.org
 for help. 
[     1.082] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[     1.082] (EE) 
[     1.106] (EE) Server terminated with error (1). Closing log file.

I dont know if it has to do with the "systemd-logind" error showing up. Maybe the automatic login process is failing?

Offline

#2 2015-10-18 08:33:21

byte
Member
From: Düsseldorf (DE)
Registered: 2006-05-01
Posts: 2,046

Re: kodi.service fails on boot

The reason is Xorg can't find a driver.
You have nvidia-340xx-utils, nvidia-340xx-libgl and nvidia-340x installed?
Did you rebuild your initramfs with 'mkinitcpio -P'? Perhaps the nouveau module doesn't get blacklisted properly.


1000

Offline

#3 2015-10-18 08:53:15

_pheinrich_
Member
Registered: 2014-05-26
Posts: 53

Re: kodi.service fails on boot

Hey thanks for your reply.

I have a nvidia GTX 260 and if I start the xserver via startx I get the default 3 windows of xorg-twm.

And yes the nvidia packages are installed

[root@ARCH_MEDIA ~]# pacman -Qs nvidia
local/libvdpau 1.1.1-1
    Nvidia VDPAU library
local/nvidia-340xx 340.93-3
    NVIDIA drivers for linux, 340xx legacy branch
local/nvidia-340xx-libgl 340.93-1
    NVIDIA drivers libraries symlinks
local/nvidia-340xx-utils 340.93-1
    NVIDIA drivers utilities
local/opencl-nvidia-340xx 340.93-1
    OpenCL implemention for NVIDIA

I will try rebuilding the initramfs

----------------------
Edit 1

I have tested the kodi.service with my laptop (Intel i7 HD3000 only) and everything was working.
On this laptop KDE is installed. Maybe I am missing some dependency.

The other idea is that my mainboard (asus p8h77-m le) is causing the problem.
There are two grafic options. The onboard i5 and the PCIe one.
I am using the PCIe one (nvidia) but maybe xinit has some trouble to decide and fails.

On the other hand "startx" successfully brings up an xorg-twm session sad

Do I have to install bumblebee?

Anybody?

-----------------------
Edit 2

Now I have remove the nvidia stuff and installed xf86-video-intel using my i5 HD3000 grafic.
With that setup the kodi.service is comming up.

Now I need to know why xinit fails with the nvidia driver.

Last edited by _pheinrich_ (2015-10-22 07:09:21)

Offline

Board footer

Powered by FluxBB