Kodi Community Forum

All in - since a very long time :-) will become live with final release of version 17. Btw. I think I have written that in the first post - didn't I?

Edit: Millhouse ships it in his V8 builds

Looking now I believe you did: :-)
>Now we install xbmc-nightly Krypton v17

Hmm.

I've had this up and running using 16.04 and this guide since the June or so. Has been working beautifully, but I just ran into a problem today.

I had been lazy and not updated the Kodi box for a while, so I did a full update using apt-get (which installed a TON of stuff).

Upon reboot I'm faced with a graphical login screen and an error message "Unable to start session".

Does anyone know what might have been wrong? I'm thinking something in the update might have overwritten one of the config files? (though I was never prompted for this)

I appreciate any suggestions.

Thanks,
Matt

(2016-11-26, 23:53)mattlach Wrote: [ -> ]Hmm.

I've had this up and running using 16.04 and this guide since the June or so. Has been working beautifully, but I just ran into a problem today.

I had been lazy and not updated the Kodi box for a while, so I did a full update using apt-get (which installed a TON of stuff).

Upon reboot I'm faced with a graphical login screen and an error message "Unable to start session".

Does anyone know what might have been wrong? I'm thinking something in the update might have overwritten one of the config files? (though I was never prompted for this)

I appreciate any suggestions.

Thanks,
Matt

I think I found the problem.

Something in the update changed the /etc/systemd/system/display-manager.service symlink to point to /lib/systemd/system/lightdm.service instead of the /etc/systemd/system/kodi.service as shown in the guide.

Going to reset the symlink back to the where it is in the guide, reboot and see if this fixes it.

>I've had this up and running using 16.04 and this guide since the June or so.
Me too Brah!

>so I did a full update using apt-get (which installed a TON of stuff)
Can you get a debug file?
Might be difficult in the state of your box.

(2016-11-27, 00:02)mattlach Wrote: [ -> ]

(2016-11-26, 23:53)mattlach Wrote: [ -> ]Hmm.

I've had this up and running using 16.04 and this guide since the June or so. Has been working beautifully, but I just ran into a problem today.

I had been lazy and not updated the Kodi box for a while, so I did a full update using apt-get (which installed a TON of stuff).

Upon reboot I'm faced with a graphical login screen and an error message "Unable to start session".

Does anyone know what might have been wrong? I'm thinking something in the update might have overwritten one of the config files? (though I was never prompted for this)

I appreciate any suggestions.

Thanks,
Matt

I think I found the problem.

Something in the update changed the /etc/systemd/system/display-manager.service symlink to point to /lib/systemd/system/lightdm.service instead of the /etc/systemd/system/kodi.service as shown in the guide.

Going to reset the symlink back to the where it is in the guide, reboot and see if this fixes it.

Yep, that solved it.

Not sure why this symlink was overwritten but some update did it on all three of my HTPC's.

Luckily it is easy to fix, if anyone else has the problem.

1.) Either SSH in or locally do CTRL-ALT-F1 to go to first text console

2.) Log in using your credentials

3.) issue following command


Note the added "f", this means "force" and overwrites the incorrect symlink.

4.) Reboot.

After this you should be back in business.

(2016-11-27, 00:13)oshan Wrote: [ -> ]>I've had this up and running using 16.04 and this guide since the June or so.
Me too Brah!

>so I did a full update using apt-get (which installed a TON of stuff)
Can you get a debug file?
Might be difficult in the state of your box.

Already solved it. See above!

The recent update marked Tvheadend pvr client incompatible. I guess a fix will come soon. Are there still so significant changes in Kodi v17 beta that makes pvr add ons incompatible from time to time?

EDIT: the new nightly from fernet"s ppa fixed the PVR issue, now it is working again.

Sent from my Xperia Z3 Compact

With the last nightly update I have some issues.
1. After update kodi started in windowed mode -> fixed it with "Settings > System > Video output full"
2. When I play a movie it just stop after ~10 min. The TV Screen get black (TV shows "no signal") and no Sound. Kodi.bin process is still runing when I check from shell.

dpkg -l |grep mesa | pastebinit
http://paste.ubuntu.com/23544630/

cat ~/.kodi/temp/kodi.log | pastebinit
http://paste.ubuntu.com/23544638/

dmesg | pastebinit
http://paste.ubuntu.com/23544642/

id | pastebinit
http://paste.ubuntu.com/23544645/

amixer | pastebinit
http://paste.ubuntu.com/23544654/

edit: ok I found the culprit, this is the HDMI cable inside the wall from the projector to the AVR that makes everything wrong....now when i look at both ends of that cable and those 19 little cables inserted into the hdmi plugs, I want to scream, it's a gigantic mess, but truth is that it doesn't seem so easy to do that cleanly, I wish i could do it myself....

greetings,
any movie I play the image flickers, stutter ?, jumps, on worst days screen can go black for like 5 seconds, sometimes blue, but I can still hear the sound.
In this log, during "bug's life" play, the display went full black, then blue i lost the video output then get it back after like 20s.
Faulty hardware ?
I had the issue before installing this fresh install, tried a few kernels, I'd be glad to try and test things !

Last login: Tue Nov 29 09:28:51 2016
kodi@bhtpc:~$ dpkg -l |grep mesa | pastebinit
http://paste.ubuntu.com/23552372/
kodi@bhtpc:~$ cat ~/.kodi/temp/kodi.log | pastebinit
http://paste.ubuntu.com/23552374/
kodi@bhtpc:~$ dmesg | pastebinit
http://paste.ubuntu.com/23552376/
kodi@bhtpc:~$ id | pastebinit
http://paste.ubuntu.com/23552377/
kodi@bhtpc:~$ amixer | pastebinit
http://paste.ubuntu.com/23552379/
kodi@bhtpc:~$ DISPLAY=:0 vainfo | pastebinit
libva info: VA-API version 0.39.2
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_39
libva info: va_openDriver() returns 0
http://paste.ubuntu.com/23552412/
kodi@bhtpc:~$

(2015-11-01, 18:35)fritsch Wrote: [ -> ]As I needed edid overwriting myself today here is a short howto on how to boot completely without TV / AVR but having correct EDID information. This will work for intel and radeon:

Fritsch, the howto to boot with TV off will prevent Intel N3150 to turn on my TV when a system restarts? Right now I have a Pulse-Eight CEC adapter connected to the N3150 box running on Ubuntu Server 16, and if I do a system restart, then my TV is turned ON. I'm not sure if this is normal or related to CEC or to this howto?

EDIT: Just saw that the latest LibreELEC test builds by Milhouse are based on Kodi v18. If I use the ppa:team-xbmc/xbmc-nightly then I will also update to Kodi v18 or stay on v17?

No idea.

Hi,

i just installed Ubuntu 16.04 and followed your instructions on first page. It's all working :-) however it's not possible to change to 2160p with a refresh rate of 50Hz. As you can see on the Attachements the TV and the system itself is able to process that (made that screenshot on the same system on Windows 10). However in Linux no 50Hz possible.

I installed the Intel driver and also setup this repository to update:
sudo apt-add-repository ppa:wsnipex/vaapi

It upgraded the driver but did not help -- no 50Hz possible.

Is there maybe another driver from Intel that is capable to do this? Or is this a general issue from Linux? With 1080P no problem I can change to any refresh rate.
The System is connected with HDMI 2.0 no adapter or long cable used.

Thanks

Alex

Too old kernel for your hardware. Use drm-intel-nightly and latest and greatest you can find somewhere, including newest intel drivers.

We don't support that hardware as we don't have it and therefore have no idea what bits are missing exactly.

Hi,

ok thanks fritsch for your help. In the meantime I found an article here: http://www.arunviswanathan.com/node/53

I installed an ubuntu desktop (also 16.04 with same kernel) and tried these steps and it worked. Unfortunately it looses this settings after reboot.
So the driver in gerneral is capable to do that only the monitor is not recognized properly.

So maybe it's easier than I thought...I just have to add a custom mode permanently. Do you have an idea how to do that?

Thanks

Alex