grep fam /proc/cpuinfo
-> 21 = 15h
-> 22 = 16h
> > $ dmesg | grep -i micro
> > [0.622441] [drm] Loading ARUBA Microcode
> > [5.763242] [drm] Loading hainan Microcode
> > [6.653025] microcode: CPU0: patch_level=0x06001119
> > [6.657962] microcode: CPU1: patch_level=0x06001119
> > [6.658890] microcode: CPU2:
On Fri, 2019-07-12 at 09:01 -0700, Ian Zimmerman wrote:
> On 2019-07-11 21:28, Nuno Silva wrote:
>
> > vlock -n -a
>
> Does vlock work from an XWindow session? Or would I have to use it
> on
> top of whatever I do to lock the XWindow session -
> xscreensaver/i3lock
> etc?
>
> (I browsed to
On 2019-07-12 13:18, Mick wrote:
> $ dmesg | grep -i micro
> [0.622441] [drm] Loading ARUBA Microcode
> [5.763242] [drm] Loading hainan Microcode
> [6.653025] microcode: CPU0: patch_level=0x06001119
> [6.657962] microcode: CPU1: patch_level=0x06001119
> [6.658890] microcode:
I think it can only be started from a VT. But what's the problem? I have an
xsession going, plus tmux, plus perhaps something else going in one or more
VT
All I have to do is call vlock -a from a virtual terminal.
Now to access any terminal VT or xsession - you have to unlock this VT
first.
But I
On 2019-07-11 21:28, Nuno Silva wrote:
> vlock -n -a
Does vlock work from an XWindow session? Or would I have to use it on
top of whatever I do to lock the XWindow session - xscreensaver/i3lock
etc?
(I browsed to the vlock README page on github but it doesn't answer this
question.)
--
Please
On Fri, 2019-07-12 at 07:18 +0300, Nikos Chantziaras wrote:
> On 11/07/2019 20:59, Alan Grimes wrote:
> > 'ey, I have the 2.3 months into an 8-month computation blues...
> > [...]
> > So basically all gentoo updates will have to be done at the end of
> > this
> > run, I'm not really sure when,
On 2019-07-12 07:12, Nikos Chantziaras wrote:
> > What is the cleanest way to handle the situation when a new sysctl knob
> > is introduced by a kernel release and I want to use it, but I also have
> > older kernels around?
>
> What's the point of that?
What's that? :-)
--
Please don't Cc:
On Mon, 8 Jul 2019 02:41:01 +0300
Nikos Chantziaras wrote:
> Qt was upgraded from 5.12.3 to 5.12.4 and as a result some
> applications (Clementine and qBittorrent) become invisible when you
> minimize them and then restore them. They only become visible again
> when you resize their window, and
I'm looking at dmesg output which on my Intel CPUS of various vintages shows
"microcode updated early ..." but two different AMD APUs of mine do not show
the same, despite AMD apparently releasing microcode updates going back to
2011:
I've been using
vlock -a
for years ... it works.
Il giorno ven 12 lug 2019 alle ore 03:18 Laurence Perkins <
lperk...@openeye.net> ha scritto:
>
> > So the solution is to just use "xscreensaver" by jwz. Which can be
> > configured to just blank the screen etc. as wanted by the op. See
> > also
11 matches
Mail list logo
