On Sun, 2021-08-08 at 08:52 -0400, Gene Heskett wrote: > On Sunday 08 August 2021 07:35:29 Valerio Bellizzomi wrote: > > > On Sun, 2021-08-08 at 07:17 -0400, Gene Heskett wrote: > > > On Sunday 08 August 2021 02:53:25 Valerio Bellizzomi wrote: > > > > I would like to see Bullseye included in the standard LinuxCNC > > > > upgrade > > > > so that I can avoid redoing the settings and configs like > > > > QtPyVCP > > > > that > > > > I did outside of the standard upgrade procedure. > > > > > > That would be nice, but there is also a downside, figuring out > > > how > > > to get > > > rid of the power management stuff so it doesn't hibernate in the > > > middle > > > of a job. I'd still like a screen blanker that works to turn off > > > the > > > monitor, but it MUST be configurable with xset, this fixed 5 > > > minute > > > shutdown if dpms is enabled at all, has got to go. Setting longer > > > times > > > is ignored. Or was the last time I tried. Disabling System > > > Hibernation > > > needs to be tied in with starting LinuxCNC, and re-enabled by > > > stopping > > > LinuxCNC. > > > > In the Debian graphical interface there is a tool called Settings, > > there you can disable power management completely, screen blanker > > has > > separate settings from power management. > > > This is indeed 2 separate problems. > > Currently power management is turned off in my buster installs. > But setting longer times for dpms is ignored, the only thing you can > do > is disable it. Root or user makes no detectable difference. > > IMO, watching for keyboard/mouse activity to start a new timeout for > dpms, has been the wrong idea from the gitgo. ANY "attempted" screen > updates by a running program should be what is used to reset that > timer. > But how difficult that would be to implement is unk to me. I quoted > that > to call attention to the user leaving the linuxcnc workspace leaving > it > running while he has the .ngc file open on another workspace, > something > I do at least 50% of the time since I generally write my own gcode. > So if switched away from the LCNC screen, and my coffee cup runs dry, > so > I get up and go to the house to refill my cup, by the time I get > back > the @%^ blanker has shut down the monitor which takes several seconds > to > power back up. Whereas if x was watching traffic to all workspaces, > it > would be aware that linuxcnc is constantly updating its workspace, > and > would not shut down the monitor. But if the job is done, and I walk > away > for the night, it should kick in and save that power till I arrive > the > next time to do something. > > I control all machine power on all my machines from LinuxCNC's motion > is > enabled signal, and if the facility in X was there, could just as > easily > disable dpms if motion is enabled. That would be quite easily done > thru > dcop, but somebody has decreed that the common user can't use dcop. > > Which is IMO odd as can be since I have a bash script that uses > inotifywait to notice incoming mail from the output of procmail, and > as > me, sends a signal to kmail by way of dcop telling kmail to go get > the > mail. So my handling of incoming mail is 100% automatic and has been > for > well over a decade. But sending that same signal from a cron script > running as me is denied. Why? IDK. > > That's my $0.02. Adjust for inflation since 1934. > > Thanks all. > > > [...] > > > > > > Cheers, Gene Heskett > > > > _______________________________________________ > > Emc-developers mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/emc-developers > > Cheers, Gene Heskett
I never has to touch dpms, I just changed the power management/display settings in Debian, my screens are always on, pc always on. _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
