Re: [gentoo-user] skylake and x265 movie display
On 6/27/19 4:46 PM, Adam Carter wrote: 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. Ok confirmed that 8 bit HEVC is low CPU and doesn't skip frames, so that's that. Well, at least that's been sorted out. I guess Intel made some changes with the newer NUCs. Way back when I set mine up I found a thread on Intel's forums mentioning not all hardware is fully available in Legacy boot mode. No reasons why (maybe they didn't bother testing it so they didn't provide access?) At least you don't have to mess around with UEFI - but as I mentioned earlier firmware updates can help performance with the video as board and gpu firmware get updated. The problem is newer firmware on some devices remove legacy boot support. It's UEFI or nothing. Dan
Re: [gentoo-user] skylake and x265 movie display
> > 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. > > Ok confirmed that 8 bit HEVC is low CPU and doesn't skip frames, so that's that.
Re: [gentoo-user] virtual eselect - how to
Am Mittwoch, 26. Juni 2019, 15:05:27 CEST schrieb Helmut Jarausch: > 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. I have the feeling you're mixing ::science and ::gentoo packages. Since openblas is only in the ::science overlay, I presume you are using that. The version of virtual/blas in ::science *does* include openblas already, so you shouldn't have needed to modify it, and you should be using eselect::science, too. eselect-blas is *not* enough (and I don't even have it installed). If you want to be sure to use packages from ::science, append "::science" to packages in your world file or set definition(s). > How does eselect get the list of alternatives? I don't know, sorry. > Many thanks for a hint, > Helmut BTW, the thread Dale mentioned is part of an effort to get the BLAS/LAPACK alternatives handling done properly (or at least more robustly). The way it's handled in the ::science overlay currently will likely not be merged into the main portage tree. HTH -- Marc Joliet -- "People who think they know everything really annoy those of us who know we don't" - Bjarne Stroustrup signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: What the devil?!! [or Plasma teething problems Ia.]
On Thursday, 27 June 2019 10:55:16 BST Mick wrote: > The next thing to try: > > I don't have elogind starting up as a boot level rc service, because it is > launched when needed by dbus or pam. Perhaps if elogind is running as a > background service sddm will (re)launch differently? I just tried it and it works. :-) With elogind running as a boot service, sddm launches with the Shutdown/Reboot buttons shown and they work as expected. However, as I do not have a /usr/ bin/loginctl, all I can assume is irrespective of the HaltCommand path specified in the default sddm config, when launched sddm searches all paths and eventually finds /bin/loginctl, which it runs when a button is pressed. As we've established with no -elogind +consolekit the commands specified in the default sddm config file are different. Also, with consolekit being a default rc service, it is running at the time sddm is launched. Thank you all for your responses. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: What the devil?!! [or Plasma teething problems Ia.]
On Thursday, 27 June 2019 02:18:05 BST Mike Gilbert wrote: > 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 Yes! It seems elogind affects the commands in file /usr/share/sddm/ sddm.conf.d/00default.conf to use a different HaltCommand and RebootCommand: $ egrep -i 'Halt|Reboot' /usr/share/sddm/sddm.conf.d/00default.conf # Halt command HaltCommand=/usr/bin/loginctl poweroff # Reboot command RebootCommand=/usr/bin/loginctl reboot Here's a kicker: I do not have '/usr/bin/loginctl' in this (openrc + elogind, but -consolekit, -systemd) system: $ which loginctl /bin/loginctl $ ls -la /usr/bin/loginctl ls: cannot access '/usr/bin/loginctl': No such file or directory $ /usr/bin/loginctl poweroff -bash: /usr/bin/loginctl: No such file or directory NOTE: Running '/bin/loginctl poweroff' from a console works. So perhaps this explains why I also do not have Shutdown/Reboot buttons showing up on the default theme at the top RH corner? Errm ... not so! Please walk through this test case with me: 1. I log out, or reboot. The sddm DM screen shows no Shutdown/Reboot buttons. Consequently, I have no means of shutting down or rebooting from the DM screen. 2. I log out, drop into a console, stop the xdm rc service and restart it. The sddm screen launches and it now presents Shutdown/Reboot buttons as it should! Question: if /usr/bin/loginctl is not present, what commands do the buttons operate/which config file they read, to shutdown/reboot? NOTE: If I login/out, or reboot, the buttons are gone again. :-/ 3. I use KDE's systemsettings 'Startup and Shutdown/Login Screen (SDDM)' to change the default theme. This creates a new /etc/sddm.conf file, with the new Theme entry I selected, but the Halt/Reboot commands are empty. I logout or reboot and the buttons are absent again, or when shown in the new theme they are either greyed out and do not work (Breeze) or not greyed out and still not work. I have not tried setting up a config file in /etc/ and modifying it comprehensively, i.e. specifying my own theme, Halt/Reboot commands, etc., but I do not have a coherent theory why the above behaviour is observed. The next thing to try: I don't have elogind starting up as a boot level rc service, because it is launched when needed by dbus or pam. Perhaps if elogind is running as a background service sddm will (re)launch differently? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: virtual eselect - how to
Mick wrote: > On Wednesday, 26 June 2019 22:13:30 BST David Haller wrote: >> 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 > In this case, if neither of the above set up a link to openblas (I don't have > blas here to check) it's time for a chat with the package maintainer. > I just saw a thread on -dev mentioning blas. The title is: [gentoo-dev] [PATCH 0/2] RFC: Introducing ldso switching to BLAS/LAPACK It mentions switching which is what eselect does but reading it, I'm not sure if it is related or not. Dale :-) :-)
Re: [gentoo-user] Re: virtual eselect - how to
On Wednesday, 26 June 2019 22:13:30 BST David Haller wrote: > 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 In this case, if neither of the above set up a link to openblas (I don't have blas here to check) it's time for a chat with the package maintainer. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: What the devil?!! [or Plasma teething problems Ia.]
On Wednesday, 26 June 2019 16:16:36 BST 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? :-) # grep Halt /usr/share/sddm/sddm.conf.d/00default.conf # Halt command HaltCommand=/sbin/shutdown -h -P now (I hadn't seen this message when I replied just now.) -- Gentoo testing system gcc 9.1.0, sys-kernel/gentoo-sources 5.1.15 QT 5.12.3, KDE frameworks 5.59.0, KDE plasma 5.16.2 KDE apps 19.04.2 incl KMail 19.04.2-r1 (5.11.2), akonadi 19.04.0 dev-db/mariadb-10.3.16 x11-drivers/xf86-video-amdgpu 19.0.0 dev-libs/amdgpu-pro-opencl 18.20.684755
Re: [gentoo-user] Re: fdm fails during ./configure: libssl not found
On Thu, 27 Jun 2019 00:47:20 + (UTC), Bryant Morrow wrote: > 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! If all you need to do is apply a patch between unpack and configure, you can drop the patch file into /etc/portage/patches/$CAT/$PKG/ and emerge will apply it with no need for a modified ebuild. You can add the version to $PKG to apply it to that version only. -- Neil Bothwick Obscenity is the crutch of inarticulate motherfuckers. pgpUFSyHbCCqk.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Re: [Was: What the devil?!!] sddm shutdown & reboot
On Wednesday, 26 June 2019 20:18:55 BST Mick wrote: > All this has left me confused and I'm thinking startx in a terminal is not > such a bad idea after all ... Have you tried the value I gave you? It works fine here. HaltCommand=/sbin/shutdown -h -P now -- Regards, Peter.
