•   
  • 1
  • 107
  • 108
  • 109(current)
  • 110
  • 111
  • 339
  •   
Intel VAAPI howto with Leia v18 nightly based on Ubuntu 18.04 server
(2015-10-11, 18:12)fritsch Wrote:
(2015-10-11, 14:29)icebaer Wrote: Hi there,

I'm running the PPA version from post#1 (Xubuntu with Openbox session on N3150). All looks fine and the image quality is remarkably good!Cool

But i'm having an issue with changing refresh rates. Adjust display refresh rate is set to "On start/stop". Sometimes kodi won't change the refresh rate, but stay in default mode (60Hz).
Currently I can reproduce it, by just booting into kodi, selecting any movie and playing it. After starting several other movies or by entering settings menu, sometimes the correct refresh rate will be used. But up to now, I could'n find any condition/action, which would activate the refresh rate again. To me it looks more of being random.

Logs are:
dpkg -l |grep mesa > http://paste.ubuntu.com/12750045/
cat ~/.kodi/temp/kodi.log > http://paste.ubuntu.com/12750051/
dmesg > http://paste.ubuntu.com/12750053/

(booting in kodi and opening "How_To_Train_Your_Dragon_2_t04.mkv", which is in 24p and sometimes also played in 24p)
See the kernel discussion. Install a 4.3-rc4 or the kernel 4.2 I provided.
Installed the current 4.3-rc5. But the problem still exists.
Refresh rates won't change, though set it to "on start/stop"

Is there anyrhing else i can provide.
Reply
Yes your kodi Debug Log as always :-)

And DISPLAY=:0 /usr/lib/kodi/kodi-xrandr | pastebinit
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
Log is linked in the above post. Since i changed "only" kernel without any visible change in behavior regarding this issue, i did not post a new log. But I will.
When executing the DISPLAY command i get an error when calling it in a ssh session. What do i have to do to execute xrandr from ssh or within kodi session?
Reply
It's not a Debug Log ...

and the dmesg is from the old kernel

it's a one liner:
DISPLAY=:0 /usr/lib/kodi/kodi-xrandr | pastebinit
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
Sorry for being a n00b, but I'm having trouble with that gpu dump. I can't seem to find the created txt file.........
My XBMC / Kodi history.
XBMC for XBOX -> XBMC for Windows -> XBMC for Android -> Kodi for Android - > Kodi v16 OE (Amlogic) -> Kodi v17 LE (NUC 2x) -> Kodi v18.5 LE (NUC 2x)
Reply
After this:
Code:
cat /sys/class/drm/card0/error > ~/mypersonalgpuhang.txt
bzip2 ~/mypersonalgpuhang.txt

It is in your home directory as mypersonalgpuhang.txt.bz2 - this one you can upload to the bugreport. Obviously you need to reproduce the crash one time, before you can capture this error state.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
Yes, no debug log no help. You're right ;o)

Here we go.... hopefully....

kodi.log > http://paste.ubuntu.com/12765890/
mesa > http://paste.ubuntu.com/12765877/
dmesg > http://paste.ubuntu.com/12765892/
xrandr > http://paste.ubuntu.com/12765896/

Been playing two other files now. Both normally play fine in 24p.
Reply
(2015-10-12, 21:39)fritsch Wrote: After this:
Code:
cat /sys/class/drm/card0/error > ~/mypersonalgpuhang.txt
bzip2 ~/mypersonalgpuhang.txt

It is in your home directory as mypersonalgpuhang.txt.bz2 - this one you can upload to the bugreport. Obviously you need to reproduce the crash one time, before you can capture this error state.

Thanks, just found it. Didn't think of looking in the storage folder. I reproduced before creating the dmesg log and gpu dump.

#LearnedSomethingNew Wink

bugreport @freedesktop : https://bugs.freedesktop.org/show_bug.cgi?id=92441
My XBMC / Kodi history.
XBMC for XBOX -> XBMC for Windows -> XBMC for Android -> Kodi for Android - > Kodi v16 OE (Amlogic) -> Kodi v17 LE (NUC 2x) -> Kodi v18.5 LE (NUC 2x)
Reply
@IceBear: Please upgrade to tomorrow's kodi build - it fails to switch refreshrates in deed ... I run latest master and it works so I think it's already fixed after ppa will be rebuild.

Edit:
Quote:21:21:49 T:140464150071360 INFO: Output 'HDMI3' has 1 modes
21:21:49 T:140464150071360 INFO: ID:0x4b Name:1920x1080 Refresh:60.000000 Width:1920 Height:1080
21:21:49 T:140464150071360 INFO: Pixel Ratio: 0.994500

Something is wrong here ... Do you use it was I told it via the howto or do you start it from your desktop? I cannot see that exactly - if kodi is run from desktop, you need to add --standalone so that it allows refreshrate switching
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
@fritsch

have you planed to build an isengard version with latest master ? I have the same problem like IceBear.
Reply
Not possible at all ... Isengard uses a fully different code path for refreshrate switching and such things ... this has not changed since several months. OE 6.0 will be broken on Braswell anyways - but this is as said a kernel issue.

Edit: Post your Debug Log and show me "the same" issue and the other guy is running Ubuntu with Jarvis Alphas
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
(2015-10-12, 21:52)fritsch Wrote:
Quote:21:21:49 T:140464150071360 INFO: Output 'HDMI3' has 1 modes
21:21:49 T:140464150071360 INFO: ID:0x4b Name:1920x1080 Refresh:60.000000 Width:1920 Height:1080
21:21:49 T:140464150071360 INFO: Pixel Ratio: 0.994500

Something is wrong here ... Do you use it was I told it via the howto or do you start it from your desktop? I cannot see that exactly - if kodi is run from desktop, you need to add --standalone so that it allows refreshrate switching
Only 1 mode indeed is not very much Huh
Though xrandr shows me more valid modes. But i ran it in a XFCE-user-session, not an openbox-kodi session. Don't know if it makes any difference.

Kodi will be started as described in the howto. With an openbox session and an autostart script like this
Code:
DISPLAY=:0 xrandr --output HDMI3 --set "Broadcast RGB" "Full"
/usr/bin/kodi --standalone
openbox --exit
Reply
Okay -> System -> Settings -> Video Hardware Output: Can you change refreshrate there?

If not - check to see if you can change the "Display" in that config. I have seen heads added twice in there, but only one with multiple refreshrates.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
Gonna check that this evening.
Because i had one learning this morning... connecting via VNC doesn't work, if no physical display is connected Confused Wink
Reply
(2015-10-13, 08:59)icebaer Wrote: Gonna check that this evening.
Because i had one learning this morning... connecting via VNC doesn't work, if no physical display is connected Confused Wink

This can be workarounded with drm_kms_helper and an initrd hack. I let that document in the old radeon oss thread. This in combination with forcing the Display to digitally on Big Grin will make it work, even when booting without screen. There exists a nice OpenELEC howto in the OE wiki, also.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
  •   
  • 1
  • 107
  • 108
  • 109(current)
  • 110
  • 111
  • 339
  •   



Logout Mark Read Team Forum Stats Members Help
Intel VAAPI howto with Leia v18 nightly based on Ubuntu 18.04 server18
This forum uses Lukasz Tkacz MyBB addons.