Re: screenblanker vs login
On Wednesday 14 February 2018 10:42:11 Alan Corey wrote:
> It could partly be the monitor's fault. According to
> https://www.x.org/releases/X11R7.7/doc/libXext/dpmslib.pdf "The actual
> effects of this mode are implementation defined, but
> in the case of DPMS compliant hardware, it is implemented by shutting
> off the horizontal sync signal, and pulsing the vertical sync signal."
> So there aren't special control lines or anything.
>
> This is all programming level stuff I think, not something you can do
> from a command line:
> apropos dpms
> DPMSCapable (3) - returns the DPMS capability of the X server
> DPMSDisable (3) - disables DPMS on the specified display
> DPMSEnable (3) - enables DPMS on the specified display
> DPMSForceLevel (3) - forces a DPMS capable display into the
> specified power... DPMSGetTimeouts (3) - retrieves the timeout values
> used by the X server for ... DPMSGetVersion (3) - returns the
> version of the DPMS extension implemented ... DPMSInfo (3) -
> returns information about the current DPMS state DPMSQueryExtension
> (3) - queries the X server to determine the availability o...
> DPMSSetTimeouts (3) - permits applications to set the timeout values
> used by...
>
All I really know about it is that on the jessie install on the
pi3b "xset dpms force off" will cycle the monitor off, for just long
enough to notice the blink, and its right back on. I don't recall if
I've ever tried that on the stretch install. And I need to go out and
restart the rock64, it must have gotten too warm doing a make -j3 in a
realtime kernel tree, as ssh is telling me the write pipe failed. Its
possible the garage has become too warm as its 58F out. and one of the
heaters has lost most of its smart temp controls. Percolating along in
low might be too much for today.
And I'm fighting with a knee, the opposite of the known bad one the last
2 days. Might have to go get some h. acid shots in it. So I'm not
exactly running any 100 yard races. Don't get old folks, the so-called
golden years are actually /not/ fun.
> Yes, for DPMSInfo your program has to include the header
> X11/extensions/dpms.h and link to the library Xext.
>
> On 2/14/18, Gene Heskett <gheskett@shentel.net> wrote:
> > On Wednesday 14 February 2018 00:25:11 Alan Corey wrote:
> >> I've been trying on and off for a year or so to get it so the
> >> monitor was powered off, or at least the backlight was turned off.
> >> Pretty much gave up. I think Windows manages to do it. It's
> >> supposed to be in the DPMS stuff.
> >
> > Keyword "supposed" to be. On the pi, I would not be surprised if the
> > hardware path wasn't there since all it has is a limited palette
> > frame buffer, but on this rock64, its probably up to the mali gfx
> > drivers, which still need diapers from what I've read.
> >
> > What they have can do 4k60hz so even tho its being pushed as a media
> > server, there doesn't seem to be any real clean room effort to write
> > an opensource driver to exploit the mali hardware on the SoC. Lack
> > of both info from the mali people, and manpower I'd guess.
> >
> >> On 2/13/18, Gene Heskett <gheskett@shentel.net> wrote:
> >> > On Tuesday 13 February 2018 09:34:44 Wookey wrote:
> >> >> On 2018-02-05 12:12 -0500, Gene Heskett wrote:
> >> >> > How do I shut the screenblanker off on an arm64.
> >> >>
> >> >> It's no different on arm than any other arch SFAIK. This is
> >> >> probably a debian-user question really.
> >> >>
> >> >> > I have looked around in the xfce menu's looking for blanker
> >> >> > timing and such, but they aren't there. xset gets reset to its
> >> >> > defaults , which is way too fast, on a reboot.
> >> >> >
> >> >> > So how do I completely disable this so I can actually get
> >> >> > something done? 450 seconds is not enough to get logged in
> >> >> > even.
> >> >>
> >> >> You can set screen blank times for XFCE in 'Settings'->'Power
> >> >> Manager', 'Display tab. or run xfce4-power-manager-settings.
> >> >> There you can set times, or just tell it not to blank or
> >> >> power-down at all.
> >> >>
> >> >> It is possible that you _also_ have something like xscreensaver
> >> >> installed, whcih may be trying to manage the screen too. You can
> >> >> just uninstall that.
> >> >>
> >> >> > And nothing related to ssh works until xfce is up and running.
> >> >>
> >> >> The openssh dameon is independent of the desktop and will start
> >> >> first. If you don't start the desktop ssh should still work.
> >> >>
> >> >> Wookey
> >> >
> >> > None of that is any real help with the problem, which is once
> >> > locked, not even John the ripper can find a working password to
> >> > let you back in.
> >> >
> >> > But I did fix it, with my usual damn the topedo's attitude, I
> >> > removed the exec perms from both of the light-locker utilities,
> >> > and killed those in memory. Now the blanker kicks in but does
> >> > not invoke dpms to turn the monitor off (I won't say it ever did)
> >> > , and I can walk back over to it, touch the mouse or the spacebar
> >> > on the keyboard, and I am instantly looking at a screen ready to
> >> > go back to work. Sure beats having to hit the reset to reboot it
> >> > in the middle of a longer job, like building a realtime kernel.
> >> >
> >> > dpms, FWIW, doesn't work on a jessie install on a pi-3b either.
> >> > The blanker does blank, but does not power down the monitor.
> >> >
> >> > --
> >> > Cheers, Gene Heskett
> >> > --
> >> > "There are four boxes to be used in defense of liberty:
> >> > soap, ballot, jury, and ammo. Please use in that order."
> >> > -Ed Howdershelt (Author)
> >> > Genes Web page <http://geneslinuxbox.net:6309/gene>
> >
> > --
> > Cheers, Gene Heskett
> > --
> > "There are four boxes to be used in defense of liberty:
> > soap, ballot, jury, and ammo. Please use in that order."
> > -Ed Howdershelt (Author)
> > Genes Web page <http://geneslinuxbox.net:6309/gene>
--
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
Reply to: