(2017-03-23, 17:20)BaGRoS Wrote: [ -> ]When I updated Python then still have 200 GB free space.
My syslog was huge 80GB from yesterday.
Code:
http://paste.ubuntu.com/24234825/
nuc xinit[1015]: extern "Python": function Cryptography_rand_status() called, but @ffi.def_extern() was not called in the current subinterpreter. Returning 0.
(2017-03-23, 17:01)fritsch Wrote: [ -> ]Delete .xsession-errors file - this is an ubuntu bug.
I dont have this file.
https://github.com/pyca/cryptography/issues/3282 <- please use the forum search for Cryptography - it's an ubuntu bug and upgrading the package will fix it.
Read through that:
http://forum.kodi.tv/showthread.php?tid=...yptography
I nicely asked for sources and information to make use of these great things under arch linux, since there are only binaries for ubuntu but got no answer. Effectively this leaves me with "Use ubuntu or live without the features.
There is no special things needed for arch linux at all. Just install kodi and use the provided systemd service to get it up and running.
This is a howto for Ubuntu. Not a "Ubuntu is the only choice" howto.
Yes, but to get it to run properly one needs the patched kernel, since the intel driver has a bug in the treatment of the video levels. Also changing the levels with xrand only affects the gui, not the played video. I suppose, this is where the patch comes into play.
I am currently build a player to achieve correct colors using 3Dluts. Might it be, you just didn't see my posts above?
I think you did not read what the howto provides. We don't change kernels by default. All kernels manually to be installed are "mainline kernels" build for Ubuntu.
If you are interested in my personal kernel patches:
https://github.com/fritsch/linux/commits/4.6-master pick it, build it and be happy.
Did nothing but reading for days. Post #2 actually says:
"I want to use fritsch's home build kernel with the Video 16:235 mode and I understand what it does."
That's me!
..although to fully understand it I am eager to try and see what actually happens to my output. I cannot find a mode where everything "falls into place" as I am used to. I have to fiddle around with brightness and contrast, something I never needed to. I have a JVC X3, so that is actually quite up to specs.
Thx for the link, I will try it right away.
Btw. a normal kernel should and will influence those values. My patch is not needed at all. I just verified with a out of the box 4.10.3 kernel without any patches. I also verified video.
You know: Our VAAPI code in v17, with Render Output VAAPI prefered is totally X unaware. It transfers the surfaces via DRM / EGL. If the TV resets on mode change. Try without "Adjust Refreshrate" and see what happens. Also you did not provide any of the logs in the first post - so I cannot even say if your have a kernel with a known bug.
To be more precise:
"Full" and "Limited 16:235" are fully and 100% mainline. My patches don't change that, it just adds an additional mode to signal Limited Ranged (like the Limited 16:235), but does not scale / clamp color output.
And something else: L
inux gives you a choice. But it does not serve you stuff on the silver tablet. It was made for people digging into stuff and then use free to use open software the way they want it. It has nothing to do with the couch potatoe is running out of burgers and french fries - just to be clear here.
Well, using linux for nearly 20 years, at work and at home, so I guess I am good to go..
So your patch signals "limited range" to my Projector, in case it might react faulty? Than I would not need the patch at all, since my projector can only be switched manually between "normal" and "extended" range.
So as I exprected the video is directly rendered out, good to know. Does this mean, the behaviour I am seeing is "correct"? I am seeing a change in Kodis interface when using xrandr to change the video level, but there is absolutely no change in a playing video. Used a gray ramp to verify that. I was hoping your patch would change that. Strangely I was seing this behaviour with and without vaapi. Confirmed that using the codec information. SW or HW, no difference. Might have been late last night, so I will fire that up again and have a closer look.
No - the behaviour you are seeing is absolutely not correct. The RGB modes are applied after all the rendering has been done. Latest level in kernel, no influence from userspace on these.
If you don't get a difference with SW playback then your projector might do "auto contrast" or something.
And if you don't start posting logfiles I will simply ignore your posts. You highjack a VAAPI howto for Ubuntu thread and refuse the post the mandatory information.
Yep, absolutely no differenc when playing video. Difference clearly visible in the GUI.
Playing a ramp of black levels 2-25 I can see all of them flashing when I turn up the brightness.
Commands are:
DISPLAY=:0 xrandr --output DP1 --set "Broadcast RGB" "Limited 16:235"
DISPLAY=:0 xrandr --output DP1 --set "Broadcast RGB" "Full"
DISPLAY=:0 xrandr --output DP1 --set "Broadcast RGB" "Limited 16:235"
DISPLAY=:0 xrandr --output DP1 --set "Broadcast RGB" "Full"
Lemme get the logs...
yaourt -Ss mesa | grep installed | pastebinit
http://pastebin.com/iqppdjYz
DISPLAY=:0 vainfo | pastebinit
libva info: VA-API version 0.39.4
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_39
libva info: va_openDriver() returns 0
http://pastebin.com/UzLFAvcJ
..ouch! - guess I might need that one?
cat ~/.kodi/temp/kodi.log | pastebinit
http://pastebin.com/8YHnD37M
dmesg | pastebinit
http://pastebin.com/GVAEMPhz
id | pastebinit
http://pastebin.com/354RdyWJ
and since there is no amixer:
jack_lsp -tcp | pastebinit
http://pastebin.com/X8PbF8rP
Will go and get me a bottle of wine now, I won't be long...
I exactly run the same versions you do. Same vaapi 1.7.3, same kernel, same xorg drivers. I have no explanation for your problem.
Set your projector to Limited, Disable Adjust Refreshrate To match video. Set kodi to limited. Set xrandr to full. Make sure Prefer VAAPI Render Method is enabled.
Stupid me, just looked closer now, vainfo finds the library, so that looks ok to me..
(2017-03-23, 21:45)fritsch Wrote: [ -> ] (2017-03-23, 21:43)BaGRoS Wrote: [ -> ] (2017-03-23, 20:25)fritsch Wrote: [ -> ]https://github.com/pyca/cryptography/issues/3282 <- please use the forum search for Cryptography - it's an ubuntu bug and upgrading the package will fix it.
Read through that: http://forum.kodi.tv/showthread.php?tid=...yptography
Yes, I thank You
In my post I wrote
Quote:Code:
https://answers.launchpad.net/ubuntu/+question/447828
lsb_release -a; uname -a; grep ppa /etc/apt/sources.list /etc/apt/sources.list.d/*.list; apt-cache policy python-cryptography python-openssl ->
Code:
http://paste.ubuntu.com/24234933/
After updating the Python libraries and rebooting, everything is working as it should. I hope. The Kodi plugins started working again.
No idea.
I write that everything works. I did exactly the same thing with Python but the solution I found on another site.