Re: [gentoo-user] skylake and x265 movie display
On Thu, Jun 27, 2019 at 11:22 AM Adam Carter wrote: > Missed this, you can use `vainfo` and it should tell you the profiles it >> supports. >> > > $ vainfo > libva info: VA-API version 1.4.0 > X Error of failed request: BadRequest (invalid request code or no such > operation) > > The error was because i ran it in a remote shell. Running it locally now and it shows HEVC. I don't have any 8 bit HEVCs files so i'm transcoding one to 8bit now. libva info: VA-API version 1.4.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib64/va/drivers/i965_drv_video.so libva info: Found init function __vaDriverInit_1_4 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.4 (libva 2.4.0) vainfo: Driver version: Intel i965 driver for Intel(R) Skylake - 2.3.0 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Simple: VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP VAProfileH264ConstrainedBaseline: VAEntrypointFEI VAProfileH264ConstrainedBaseline: VAEntrypointStats VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointEncSliceLP VAProfileH264Main : VAEntrypointFEI VAProfileH264Main : VAEntrypointStats VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264High : VAEntrypointEncSliceLP VAProfileH264High : VAEntrypointFEI VAProfileH264High : VAEntrypointStats VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileVP8Version0_3 : VAEntrypointVLD VAProfileVP8Version0_3 : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice
Re: [gentoo-user] skylake and x265 movie display
> > Missed this, you can use `vainfo` and it should tell you the profiles it > supports. > $ vainfo libva info: VA-API version 1.4.0 X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 154 (DRI2) Minor opcode of failed request: 1 (DRI2Connect) Serial number of failed request: 11 Current serial number in output stream: 11
Re: [gentoo-user] Re: What the devil?!! [or Plasma teething problems Ia.]
On Wed, Jun 26, 2019, 7:30 PM Neil Bothwick wrote: > On Wed, 26 Jun 2019 18:00:22 -0500, »Q« wrote: > > > > In an OpenRC system there is no loginctl. Consequently, unless we > > > define a separate config in /etc/ to use shutdown (with sudo?) it > > > won't work. This systemd-ism may be worth a bug report. > > > > In /usr/share/sddm/sddm.conf.d/00default.conf I have > > > > HaltCommand=/sbin/shutdown -h -P now > > > > RebootCommand=/sbin/shutdown -r now > > > > I just checked it with sddm-0.18.0, then upgraded to 0.18.1-r1, and it > > stayed the same, I guess because I have USE="-systemd". > > And on a systemd setup, I have > > HaltCommand=/usr/bin/systemctl poweroff > > so where did Mick's loginctl option come from? > elogind >
Re: [gentoo-user] Re: fdm fails during ./configure: libssl not found
Aha! Thank you for that, I didn't see those bug reports in my Google searches. Now I know to check the bugtracking projects directly. I've set up a local portage repo with a modified fdm-1.9 ebuild using the patch given in that link, and fdm builds without issue. Thank you! On Tue, 25 Jun 2019 10:04:19 +0100, (Nuno Silva) wrote: > On 2019-06-24, Bryant Morrow wrote: > > > --- > > > > fdm-1.9 consistently fails to build, with configure citing a lack of > > libssl as the reason. I have openssl installed, and > > /usr/lib64/libssl.so (symlink to /usr/lib64/libssl.so.1.1) exists. > > I've looked for similar problems online, with no luck. It originally > > seemed to be related to a broken version of openssl being unmasked > > along with the use of ~amd64 in ACCEPT_KEYWORDS, but resolving that > > made no difference. It seems to me that fdm's config scripts simply > > can't find libssl, but they appear to be looking in all of the correct > > places. I had it installed and working in the past, but it was removed > > due to a stupid (on my part) accident with emerge --depclean and now > > fails to reinstall. > > > > Output of emerge -pqv 'net-mail/fdm-1.9::gentoo': > > http://dpaste.com/2B1YBPZ //emerge -pqv > > > > Output of emerge --info 'net-mail/fdm-1.9::gentoo': > > http://dpaste.com/0D1PK0E //emerge --info > > > > Contents of build.log: http://dpaste.com/1CFZF87 //build.log > > > > Contents of portage environment file: http://dpaste.com/2XJD461 > > //environment > > This looks like bug 677484 - the problem would indeed be the way this > config script tries to detect libssl. > > I don't use fdm, but from what I read in the bug report, I suppose you > could try downgrading openssl to 1.0.*, or change the fdm ebuild to > apply the patch from comment 9. > > https://bugs.gentoo.org/show_bug.cgi?id=677484 > > -- > Nuno Silva
Re: [gentoo-user] Re: What the devil?!! [or Plasma teething problems Ia.]
On Wed, 26 Jun 2019 18:00:22 -0500, »Q« wrote: > > In an OpenRC system there is no loginctl. Consequently, unless we > > define a separate config in /etc/ to use shutdown (with sudo?) it > > won't work. This systemd-ism may be worth a bug report. > > In /usr/share/sddm/sddm.conf.d/00default.conf I have > > HaltCommand=/sbin/shutdown -h -P now > > RebootCommand=/sbin/shutdown -r now > > I just checked it with sddm-0.18.0, then upgraded to 0.18.1-r1, and it > stayed the same, I guess because I have USE="-systemd". And on a systemd setup, I have HaltCommand=/usr/bin/systemctl poweroff so where did Mick's loginctl option come from? -- Neil Bothwick By the time you can make ends meet, they move the ends. pgpLgBtyOXhSI.pgp Description: OpenPGP digital signature
[gentoo-user] Re: What the devil?!! [or Plasma teething problems Ia.]
On Wed, 26 Jun 2019 11:20:20 +0100 Mick wrote: > On Tuesday, 25 June 2019 17:09:55 BST »Q« wrote: > > On Mon, 24 Jun 2019 21:19:09 +0100 > > > > Mick wrote: > > > Also, the sddm DM shutdown/reboot buttons now do not work. O_O > > > > Those have never worked for me. > > I just looked at another installation. The default sddm > configuration file (/ usr/share/sddm/sddm.conf.d/00default.conf) > shows this: > > [General] > # Halt command > HaltCommand=/usr/bin/loginctl poweroff > > In an OpenRC system there is no loginctl. Consequently, unless we > define a separate config in /etc/ to use shutdown (with sudo?) it > won't work. This systemd-ism may be worth a bug report. In /usr/share/sddm/sddm.conf.d/00default.conf I have HaltCommand=/sbin/shutdown -h -P now RebootCommand=/sbin/shutdown -r now I just checked it with sddm-0.18.0, then upgraded to 0.18.1-r1, and it stayed the same, I guess because I have USE="-systemd".
Re: [gentoo-user] Re: virtual eselect - how to
Hello,
On Wed, 26 Jun 2019, Ian Zimmerman wrote:
>On 2019-06-26 14:51, Mick wrote:
>
>> > I have installed openblas but 'eselect blas list' doesn't know about
>> > this.
>>
>> I assume it doesn't know about it because there is no eselect module
>> for blas.
>
>There definitely is, I have run across this problem as well.
# eix app-eselect/ |grep blas
[I] app-eselect/eselect-blas
[I] app-eselect/eselect-cblas
HTH,
-dnh
--
sh -c 'set 2 1 0 / . - + ^ : , ! %;y=70;for a in $* $*;do x=54;while [ \
${#s} -lt 79 ];do r=0;i=0;for b in % $*;do [ $(((q=r*r)+(t=i*i))) -ge 9\
999 ]&i=$((y+(r*i)/32));r=$((x+(q-t)/64));done;s=$b$s;x=$((x-2))\
;done;y=$((y-6));echo $s;s=;done;'
Re: [gentoo-user] skylake and x265 movie display
On 6/25/19 4:57 PM, Adam Carter wrote: My skylake (i3-6100U) system drops frames when watching x265 movies (in mpv and kodi), with all cores at 100% CPU. I've re-run through https://wiki.gentoo.org/wiki/Intel and tried changing from the intel driver to modsetting, and it appears to use less CPU for x264 at least. Still maxed out for x265 so I cant tell if there's a difference for that. I'm going through the USE flags for kodi, mpv and ffmpeg, which flags are the most important? Is there some way to run a simple movie playback benchmark to assess the impact of changes? Missed this, you can use `vainfo` and it should tell you the profiles it supports. Dan
Re: [gentoo-user] skylake and x265 movie display
On 6/25/19 11:53 PM, Adam Carter wrote: This wouldn't happen to be a 10-bit encoded x265, would it? If it is, 10-bit hardware decoding is only supported in Kaby Lake or newer (this could explain it decoding in software/on CPU instead of GPU.) That's possible. Is there an easy way to tell? Looked through the output of ffmpeg and found; Stream #0:0: Video: hevc (Main 10), yuv420p10le(tv, bt2020nc/bt2020/smpte2084), 3840x1600 [SAR 1:1 DAR 12:5], 23.98 fps, 23.98 tbr, 1k tbn, 23.98 tbc (default) So it is a 10bit file. Another tip: I found upgrading the NUC's firmware helped a lot. However, be warned that Intel has been removing support for Legacy booting in newer firmware. So you might want to get yours to boot in UEFI first, then try new firmware. I suspect it's a hardware limitation, but you never know. Dan
Re: [gentoo-user] Re: What the devil?!! [or Plasma teething problems Ia.]
On 6/26/19 8:16 AM, Mick wrote: On Wednesday, 26 June 2019 15:22:45 BST Peter Humphrey wrote: On Wednesday, 26 June 2019 11:20:20 BST Mick wrote: I just looked at another installation. The default sddm configuration file (/usr/share/sddm/sddm.conf.d/00default.conf) shows this: [General] # Halt command HaltCommand=/usr/bin/loginctl poweroff In an OpenRC system there is no loginctl. Consequently, unless we define a separate config in /etc/ to use shutdown (with sudo?) it won't work. This systemd-ism may be worth a bug report. Here, it shows 'HaltCommand=/sbin/shutdown -h -P now'. Where 'here' is ... where? :-) Your own /etc/sddm/ configuration file, or the default installed under /usr/ share/sddm/sddm.conf.d/ ? The sddm package no longer installs a config file in etc. The user may do so if desired/required and modify it accordingly. However, the sample file offered by sddm has the above mentioned incongruity in it, which means the shutdown and reboot commands issued by its interface invariably do not work in openrc and it seems the same applies to systemd. I'll check a couple more of my installations here to see if they differ. I don't have any /etc/sddm.conf - it's all default config and mine is working with no tweaking (OpenRC). Same as mentioned above in the default config file: HaltCommand=/sbin/shutdown -h -P now Dan
Re: [gentoo-user] Re: [Was: What the devil?!!] sddm shutdown & reboot
On Wednesday, 26 June 2019 16:49:11 BST Arve Barsnes wrote: > On Wed, 26 Jun 2019 at 17:13, Neil Bothwick wrote: > > > Could it be loginctl is there to confirm if a local button operation > > > can run / sbin/poweroff, rather than actually running the command as > > > shown in the sddm config file? > > > > No, not when I tried it > > > > % loginctl poweroff > > Unknown operation poweroff. > > > > This is confirmed by the list of commands in the loginctl man page. > > On the other hand, poweroff and reboot are valid arguments to > /bin/loginctl, installed by elogind > > Regards, > Arve OK, I got this partly wrong. 1. There is a /bin/loginctl installed by elogind in openrc, but there is no / usr/bin/loginctl, which is what the sddm default settings file mentions. 2. Running '/bin/loginctl poweroff' from a console, while logged in as a user works fine. 3. Despite the above, some installations of mine do not react to sddm button presses to shutdown/reboot, but an older installation does. On some installations which I suspect are running some (older) default sddm theme there are no shutdown/reboot buttons shown at all. :-/ 4. The installation which has buttons showing and reacts to it is an old installation, which has been hacked to death. At some point in its life it had an /etc/sddm/ config file, modified to do stuff which the default settings would not do. This file is no longer there, so sddm should be reading the default settings under /usr/share/sddm/ but I don't know if some settings were cached by sddm and this is why this PC works as it should, but others don't. All this has left me confused and I'm thinking startx in a terminal is not such a bad idea after all ... -- Regards, Mick signature.asc Description: This is a digitally signed message part.
[gentoo-user] Amazon Corretto JDK?
Has anybody tried out (or made an ebuild for) the Amazon Corretto jdk package? https://aws.amazon.com/corretto/ This looks like an interesting alternative that is no-cost and promises long term support. It will also be used for almost all AWS java deployments, so it should be well tested and stable.
Re: [gentoo-user] Re: [Was: What the devil?!!] sddm shutdown & reboot
On Wed, 26 Jun 2019 at 17:13, Neil Bothwick wrote: > > Could it be loginctl is there to confirm if a local button operation > > can run / sbin/poweroff, rather than actually running the command as > > shown in the sddm config file? > > No, not when I tried it > > % loginctl poweroff > Unknown operation poweroff. > > This is confirmed by the list of commands in the loginctl man page. On the other hand, poweroff and reboot are valid arguments to /bin/loginctl, installed by elogind Regards, Arve
[gentoo-user] Re: virtual eselect - how to
On 2019-06-26 14:51, Mick wrote: > > I have installed openblas but 'eselect blas list' doesn't know about > > this. > > I assume it doesn't know about it because there is no eselect module > for blas. There definitely is, I have run across this problem as well. -- Please don't Cc: me privately on mailing lists and Usenet, if you also post the followup to the list or newsgroup. To reply privately _only_ on Usenet and on broken lists which rewrite From, fetch the TXT record for no-use.mooo.com.
Re: [gentoo-user] Re: What the devil?!! [or Plasma teething problems Ia.]
On Wednesday, 26 June 2019 15:22:45 BST Peter Humphrey wrote: > On Wednesday, 26 June 2019 11:20:20 BST Mick wrote: > > I just looked at another installation. The default sddm configuration > > file (/usr/share/sddm/sddm.conf.d/00default.conf) shows this: > > > > [General] > > # Halt command > > HaltCommand=/usr/bin/loginctl poweroff > > > > In an OpenRC system there is no loginctl. Consequently, unless we define > > a > > separate config in /etc/ to use shutdown (with sudo?) it won't work. This > > systemd-ism may be worth a bug report. > > Here, it shows 'HaltCommand=/sbin/shutdown -h -P now'. Where 'here' is ... where? :-) Your own /etc/sddm/ configuration file, or the default installed under /usr/ share/sddm/sddm.conf.d/ ? The sddm package no longer installs a config file in etc. The user may do so if desired/required and modify it accordingly. However, the sample file offered by sddm has the above mentioned incongruity in it, which means the shutdown and reboot commands issued by its interface invariably do not work in openrc and it seems the same applies to systemd. I'll check a couple more of my installations here to see if they differ. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: [Was: What the devil?!!] sddm shutdown & reboot
On Wed, 26 Jun 2019 15:15:37 +0100, Mick wrote: > > > [General] > > > # Halt command > > > HaltCommand=/usr/bin/loginctl poweroff > > > > > > In an OpenRC system there is no loginctl. Consequently, unless we > > > define a separate config in /etc/ to use shutdown (with sudo?) it > > > won't work. This systemd-ism may be worth a bug report. > > > > It won't work on systemd either, loginctl has no poweroff command, it > > should be systemctl poweroff, which is symlinked to /sbin/poweroff > > here so setting it to that should work for modern and ancient systems > > alike :P > > Could it be loginctl is there to confirm if a local button operation > can run / sbin/poweroff, rather than actually running the command as > shown in the sddm config file? No, not when I tried it % loginctl poweroff Unknown operation poweroff. This is confirmed by the list of commands in the loginctl man page. -- Neil Bothwick C Error #029: Well! I'm impressed pgpqQaSUjMiYV.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Re: What the devil?!! [or Plasma teething problems Ia.]
On Wednesday, 26 June 2019 11:20:20 BST Mick wrote: > I just looked at another installation. The default sddm configuration file > (/ usr/share/sddm/sddm.conf.d/00default.conf) shows this: > > [General] > # Halt command > HaltCommand=/usr/bin/loginctl poweroff > > In an OpenRC system there is no loginctl. Consequently, unless we define a > separate config in /etc/ to use shutdown (with sudo?) it won't work. This > systemd-ism may be worth a bug report. Here, it shows 'HaltCommand=/sbin/shutdown -h -P now'. -- Regards, Peter.
[gentoo-user] Re: [Was: What the devil?!!] sddm shutdown & reboot
On Wednesday, 26 June 2019 11:34:47 BST Neil Bothwick wrote: > On Wed, 26 Jun 2019 11:20:20 +0100, Mick wrote: > > I just looked at another installation. The default sddm configuration > > file (/ usr/share/sddm/sddm.conf.d/00default.conf) shows this: > > > > [General] > > # Halt command > > HaltCommand=/usr/bin/loginctl poweroff > > > > In an OpenRC system there is no loginctl. Consequently, unless we > > define a separate config in /etc/ to use shutdown (with sudo?) it won't > > work. This systemd-ism may be worth a bug report. > > It won't work on systemd either, loginctl has no poweroff command, it > should be systemctl poweroff, which is symlinked to /sbin/poweroff here > so setting it to that should work for modern and ancient systems alike :P Could it be loginctl is there to confirm if a local button operation can run / sbin/poweroff, rather than actually running the command as shown in the sddm config file? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] skylake and x265 movie display
On 6/25/19 11:42 PM, Adam Carter wrote: What about USE flags for mesa and libva? x11-libs/libva-2.4.0:0/2::gentoo USE="X drm opengl -utils -vdpau -wayland" media-libs/mesa-19.1.1::gentoo USE="classic dri3 egl gallium gbm gles2 llvm vaapi -d3d9 -debug -gles1 (-libglvnd) -lm_sensors -opencl -osmesa -pax_kernel -pic (-selinux) -test -unwind -valgrind -vdpau -vulkan -vulkan-overlay -wayland -xa -xvmc" This wouldn't happen to be a 10-bit encoded x265, would it? If it is, 10-bit hardware decoding is only supported in Kaby Lake or newer (this could explain it decoding in software/on CPU instead of GPU.) That's possible. Is there an easy way to tell? I also had to boot with UEFI or no hardware decoding happened at all. Mine was old enough to give you a choice but video performance suffered in BIOS boot mode. Damn - this is in BIOS mode... Very odd that makes a difference. Nice find. When I got my celeron-based NUC I discovered that just because the CPU has some hardware offloading doesn't mean software will use it. :( This box is a NUC (NUC6i5SYB) that im using for a media PC. Mine's an older Celeron. It struggled with 1080p video. I found back then (maybe six years ago?) a thread stating Intel locks out some hardware in BIOS mode so performance will suffer. All I did at the time was grind my teeth and fight it to get it to boot in UEFI mode, and I could see the hardware offload on 1080p was working correctly. I see from your other reply it is a 10-bit file, that would explain why hardware offloading doesn't work - it's not supported on that CPU. Have you tried an 8-bit encoded file to see if the hardware offloading works? Dan
Re: [gentoo-user] virtual eselect - how to
On Wednesday, 26 June 2019 14:05:27 BST Helmut Jarausch wrote: > Hi, > what is the relationship of a virtual package and eselect. > E.g. > I have installed openblas but 'eselect blas list' doesn't know about > this. I assume it doesn't know about it because there is no eselect module for blas. > I have even modified virtual/blas to include openblas. Virtual packages are there to make sure at least one of alternative packages satisfying dependency requirements will be installed. So, some package you installed requires a database. A virtual/ will be installed to make sure at least one of the database packages to satisfy the dependency requirement is installed. > How does eselect get the list of alternatives? > > Many thanks for a hint, > Helmut My understanding is package devs will have to create a corresponding eselect module, in order manage the symlinks for the various versions of said package which are available in the tree at any time. In absence of an eselect module, you can create any desired symlinks yourself. I often forget there are so many eselect modules these days. I found myself using rm and 'ln -s' to change profiles, only to recall eselect does this in a single incantation. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
[gentoo-user] virtual eselect - how to
Hi, what is the relationship of a virtual package and eselect. E.g. I have installed openblas but 'eselect blas list' doesn't know about this. I have even modified virtual/blas to include openblas. How does eselect get the list of alternatives? Many thanks for a hint, Helmut
Re: [gentoo-user] Re: What the devil?!! [or Plasma teething problems Ia.]
On Wed, 26 Jun 2019 11:20:20 +0100, Mick wrote: > I just looked at another installation. The default sddm configuration > file (/ usr/share/sddm/sddm.conf.d/00default.conf) shows this: > > [General] > # Halt command > HaltCommand=/usr/bin/loginctl poweroff > > In an OpenRC system there is no loginctl. Consequently, unless we > define a separate config in /etc/ to use shutdown (with sudo?) it won't > work. This systemd-ism may be worth a bug report. It won't work on systemd either, loginctl has no poweroff command, it should be systemctl poweroff, which is symlinked to /sbin/poweroff here so setting it to that should work for modern and ancient systems alike :P -- Neil Bothwick Nothing is foolproof to a sufficiently talented fool. pgpvmhIqFbV8R.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Re: What the devil?!! [or Plasma teething problems Ia.]
On Tuesday, 25 June 2019 17:09:55 BST »Q« wrote: > On Mon, 24 Jun 2019 21:19:09 +0100 > > Mick wrote: > > Can someone please explain how the removal of the 'wireless' USE flag > > from powerdevil ends up with no buttons for Suspend-to-RAM, > > Hibernation, Reboot or Shutdown under the Leave tab of the KMenu? > > What does wireless have to do with those functions which should work > > regardless? > > I have the wireless flag on, and I'm sometimes missing those buttons. > I've never figured out why, but they usually return after I log out of > KDE and back in -- sometimes it takes a reboot. I've come across the same symptoms on various installations of mine. However, I thought in all cases this was because I was in the middle of an update. Anyway, after a prolonged revdep-rebuild, which reinstalled dbus plus another 21 packages, it seems all buttons are back and I can shutdown and hibernate. I have no idea why a revdep-rebuild wanted to rebuild all these packages ... but clearly something I did (like uninstalling/reinstalling plasma-meta, or changing package specific USE flags?) meant all these needed to be rebuilt. I didn't expect this - thank you Dale for nudging me in the right direction and thank you all for your suggestions. :-) Next time I login I'll also check if the missing Power Management module mentioned in systemsettings has resolved itself. > > Also, the sddm DM shutdown/reboot buttons now do not work. O_O > > Those have never worked for me. I just looked at another installation. The default sddm configuration file (/ usr/share/sddm/sddm.conf.d/00default.conf) shows this: [General] # Halt command HaltCommand=/usr/bin/loginctl poweroff In an OpenRC system there is no loginctl. Consequently, unless we define a separate config in /etc/ to use shutdown (with sudo?) it won't work. This systemd-ism may be worth a bug report. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] skylake and x265 movie display
> > This wouldn't happen to be a 10-bit encoded x265, would it? If it is, > >> 10-bit hardware decoding is only supported in Kaby Lake or newer (this >> could explain it decoding in software/on CPU instead of GPU.) >> > > That's possible. Is there an easy way to tell? > Looked through the output of ffmpeg and found; Stream #0:0: Video: hevc (Main 10), yuv420p10le(tv, bt2020nc/bt2020/smpte2084), 3840x1600 [SAR 1:1 DAR 12:5], 23.98 fps, 23.98 tbr, 1k tbn, 23.98 tbc (default) So it is a 10bit file.
Re: [gentoo-user] skylake and x265 movie display
> What about USE flags for mesa and libva? > x11-libs/libva-2.4.0:0/2::gentoo USE="X drm opengl -utils -vdpau -wayland" media-libs/mesa-19.1.1::gentoo USE="classic dri3 egl gallium gbm gles2 llvm vaapi -d3d9 -debug -gles1 (-libglvnd) -lm_sensors -opencl -osmesa -pax_kernel -pic (-selinux) -test -unwind -valgrind -vdpau -vulkan -vulkan-overlay -wayland -xa -xvmc" > This wouldn't happen to be a 10-bit encoded x265, would it? If it is, > 10-bit hardware decoding is only supported in Kaby Lake or newer (this > could explain it decoding in software/on CPU instead of GPU.) > That's possible. Is there an easy way to tell? > > I also had to boot with UEFI or no hardware decoding happened at all. > Mine was old enough to give you a choice but video performance suffered > in BIOS boot mode. > > Damn - this is in BIOS mode... Very odd that makes a difference. Nice find. > When I got my celeron-based NUC I discovered that just because the CPU > has some hardware offloading doesn't mean software will use it. :( > This box is a NUC (NUC6i5SYB) that im using for a media PC.
