drm GPU hang
#16
I followed the instruction on http://forum.kodi.tv/showthread.php?tid=165707.
When I now restart the HTPC, I get a login window for the user xbmc, where I should enter the password.
How could I do the user to auto login with the XBMC Frontend?
I think all necessary processes are started:

Code:
root      1124  0.0  0.1  86160  3948 ?        Ss   18:48   0:00 su -c xinit /usr/bin/kodi --standalone -- /usr/bin/X -nolisten tcp :0 xbmc
xbmc      1285  0.0  0.0  16008   916 ?        Ss   18:48   0:00  \_ xinit /usr/bin/kodi --standalone -- /usr/bin/X -nolisten tcp :0
root      1286  0.0  0.4 148244 15052 tty8     S<sl+ 18:48   0:00      \_ /usr/bin/X :0 -nolisten tcp :0
xbmc      1296  0.0  0.0   4452   680 ?        S    18:48   0:00      \_ /bin/sh /usr/bin/kodi --standalone
xbmc      1305  0.3  1.3 810720 46468 ?        Sl   18:48   0:00          \_ /usr/lib/kodi/kodi.bin --standalone
Reply
#17
Which parts did you do exactly?
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#18
I reinstall XBMCBuntu at the moment, because of broken setup.
After installation is finished, I would do the following:

First:
Code:
apt-get remove xbmc*
apt-get purge xbmc*

After that I would follow your instruction.
The user I've choosed in the XBMCbuntu installation is also called xbmc, so that the auto login should work.

0.) Basic Installation and script tuning
After the mini iso is installed, continue with the following steps:

Code:
Code:
sudo apt-get update
sudo apt-get install ssh python-software-properties software-properties-common udisks upower xorg alsa-utils mesa-utils git-core librtmp0 lirc libmad0 lm-sensors libmpeg2-4 avahi-daemon libnfs1 consolekit pm-utils libva1 vainfo libva-intel-vaapi-driver linux-firmware
sudo apt-get dist-upgrade

Allow every user (everyone) to start X11
Code:
Code:
sudo dpkg-reconfigure x11-common

Create the xbmc user and it add it the relevant groups. If you have created the xbmc user during installation only do the usermod part.
Code:
Code:
sudo adduser xbmc
sudo usermod -a -G cdrom,audio,video,plugdev,users,dialout,dip xbmc


To use the following upstart procedure you need to create /etc/init/xbmc.conf to start xbmc via upstart. That scripts does only wait for your HDMI device, if you want to wait for networking, you have to add that.
Code:
Code:
# xbmc-upstart
# starts XBMC on startup by using xinit.
# by default runs as xbmc, to change edit below.
env USER=xbmc

emits xbmc-started
description     "XBMC-barebones-upstart-script"
author          "Matt Filetto"

start on (filesystem and stopped udevtrigger)
stop on runlevel [016]

# tell upstart to respawn the process if abnormal exit
respawn
respawn limit 10 5
limit nice 21 21

script
exec su -c "xinit /usr/bin/kodi --standalone -- /usr/bin/X -nolisten tcp :0" $USER
# the following two are to get an idea, if you want to user a window manager
# sudo apt-get install fluxbox and comment the above exec line
# only one exec line is allowed.
#   exec su -c "xinit /usr/bin/fluxbox -- /usr/bin/X -nolisten tcp :0" $USER
end script
# remove all those to set Full rgb range make sure to change HDMI2 to match your device
# starting from the next line, including end script
# post-start script
# sleep 1
# DISPLAY=:0 xrandr --output HDMI2 --set "Broadcast RGB" Full
# end script

edit /etc/security/limits.conf and add before the end. remember xbmc is the username, not the application. This will allow your user to get the audio thread a bit more priority.
Code:
Code:
xbmc             -       nice            -1

Last thing is missing some permissions to shutdown, suspend the computer, therefore create the file /etc/polkit-1/localauthority/50-local.d/custom-actions.pkla with the following content (don't introduce line breaks, especially the Action= line must be exactly one line (especially no linebreaks or auto ".." in freedesktop.udisks.*), verify this):
Code:
Code:
[Actions for xbmc user]
Identity=unix-user:xbmc
Action=org.freedesktop.upower.*;org.freedesktop.consolekit.system.*;org.freedesk​top.udisks.*;org.freedesktop.login1.*
ResultAny=yes
ResultInactive=yes
ResultActive=yes

[Untrusted Upgrade]
Identity=unix-user:xbmc
Action=org.debian.apt.upgrade-packages;org.debian.apt.update-cache
ResultAny=yes
ResultInactive=yes
ResultActive=yes


1.) Installation of the repository and the new packages
Code:
Code:
sudo apt-add-repository ppa:team-xbmc/unstable (* this can be changed after helix final)
sudo apt-add-repository ppa:wsnipex/vaapi (see *)
sudo apt-get update
sudo apt-get install kodi kodi-bin
sudo apt-get dist-upgrade


1. Will this work?
2. Is there are need to install kernel 3.18 for Kodi too?
3. While removing xbmc*, does this touch the LIRC setup?
Reply
#19
No, it won't.

You now have lightdm _and_ an custom upstart script. Remove /etc/init/xbmc.conf again

and it should be back to what it was before.

Concerning 1. 2. 3. let's stop here. I don't think you understood a single thing of what I said -> OpenELEC 4.97.3 will have that fix and you can easily use that one.

For your xbmcbuntu, the kodi ppa, the wsnipex ppa and the 3.18 kernel installation was enough.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#20
I now installed Ubuntu 14.04.01 LTS and followed the steps mentioned in http://forum.kodi.tv/showthread.php?tid=165707
In addition to that, I installed the kernel 3.18 and die vaapi drivers from http://forum.kodi.tv/showthread.php?tid=...pid1863722

Did not have much time testing if the problem still exists until now. But so far everything seems to work.
Before I will do that, I have to figure out an other problem.

I remotely logged in via ssh to the HTPC. In the sessions I noticed a load from 2.xx and a cpu usage from 180-200%.
For my understanding this means, that the HTPC was busy at all (2 Core CPU).
What makes me a little bit nervous is the fact, that 'sensors' say that the cpu temperature was at 79° degrees.
The HTPC was just started, which means just the kodi dashboard was started and no movie was playing.

Is the intel g3420 to weak for kodi?
Reply
#21
post:

DISPLAY=:0 vainfo | pastebinit
sensors | pastebinit

and your xbmc.log

When you used the full Ubuntu installation, then you now have again two "Xserver processes" running ... that howto was meant for a minimal setup, not a full blown ubuntu desktop.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#22
Follow _one_ howto, from the start to the end. And don't mix things.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#23
I will past this as I have access again (actually the htpc) was shutdown.
I installed ubuntu 14.04.01 LTS server version, without any graphical user interfaces.
Within the installation processes, I just installed the openssh server.
Reply
#24
Good. Then it's fine.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#25
http://paste.ubuntu.com/9569863/
http://paste.ubuntu.com/9569864/
http://paste.ubuntu.com/9569869/

Afterwards I shutdown the HTPC because of the high degree.
After reading the xbmc.log it looks like the xbmc user was removed from the video group while updating?
Checking that later
Reply
#26
Really looks like that putting the xbmc user back into the needed groups solved the problem:

sudo usermod -a -G cdrom,audio,video,plugdev,users,dialout,dip xbmc

Actually after starting xbmc the temperature is:

root@kodi:~# sensors
coretemp-isa-0000
Adapter: ISA adapter
Physical id 0: +37.0°C (high = +80.0°C, crit = +100.0°C)
Core 0: +36.0°C (high = +80.0°C, crit = +100.0°C)
Core 1: +37.0°C (high = +80.0°C, crit = +100.0°C)

Here's the xbmc.log, where the former error does not occur again:

http://paste.ubuntu.com/9578018/

I will no configure the htpc and start testing the gpu hang by playing movies.
Getting back afterwards.

EDIT:
Watching a 720p movie, I set Video Scaling method to: Lanczos3 optimized
Deinterlace Video: Auto
In Deinterlance method I could not find Motion Completion (Could choose between VAAPI Motion Adaptive and VAAPI Motion Compensated)

The other settings are:

3.) XBMC settings
System->Settings->System->Video Settings:
Vertical Sync: Let Driver decide

System ->Video->Acceleration:
Enable HQ Scalers for scaling above: 20%
Allow hardware acceleration (VDPAU): off
Allow hardware acceleration (VAAPI): On
Use Mpeg-2 VAAPI: Yes
Use Mpeg-4 VAAPI: Yes
UseVC-1 VAAPI: off
Adjust Refreshrate to match video: xx <-- could not find

If you experience kernel hangs (dmesg will tell), you can set Prefer VAAPI Render: Off that will force the swfilter even when progressive / VAAPI BOB is in use.

System -> Video -> Playback
Sync Playback to Display: On
Sync Method: Video Clock (Drop/Dupe)
Adjust display refresh rate to match video: On Start / Stop
Reply
#27
VAAPI Motion Compensated <- correct one: MCDI (Motion Compensation) DI <- Deinterlacing.

You don't get kernel hangs anymore, cause you have the 3.18 kernel running that has it fixed.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#28
Got GPU hang two more times.
Once when change system languae in Appearance and once while playback.
In addition to that, the system has problems while seeking forward. The picture and the timeline is not seeking forward after 1-2 seconds. Just when I stop forwarding, the picture and the timeline is getting the current value. Before the current value is visable, kodi is buffering.
This was the kodi logs says meanwhile:

http://paste.ubuntu.com/9587928/

For the GPU hang:

http://paste.ubuntu.com/9587932/
http://paste.ubuntu.com/9587933/
http://paste.ubuntu.com/9587947/
http://paste.ubuntu.com/9587934/
http://paste.ubuntu.com/9587935/
http://paste.ubuntu.com/9587936/
http://paste.ubuntu.com/9587941/
Reply
#29
No, you did not get the gpu hang: http://paste.ubuntu.com/9587932/

Clean. Rather looks like a network issue.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#30
Obviously, the gpu hang was not in the logs anymore.
While scrolling in a series episode list, got gpu hang again:

http://paste.ubuntu.com/9596424/
http://paste.ubuntu.com/9596425/
http://paste.ubuntu.com/9596440/ <-- made as user xbmc, instead of user root
http://paste.ubuntu.com/9596427/
http://paste.ubuntu.com/9596428/
http://paste.ubuntu.com/9596448/ <-- made as user xbmc, instead of user root
http://paste.ubuntu.com/9596438/
Reply

Logout Mark Read Team Forum Stats Members Help
drm GPU hang0