>From the following >https://unix.stackexchange.com/questions/4466/screen-turns-on-automatically-xset-dpms-force-off
is this awful hack: I used cron with this set to run every 5 mins (enter crontab -e from the command-line as your X11 logged in user): */5 * * * * /usr/bin/env DISPLAY=:0.0 xset -dpms Or even worse: If non of the above worked for you. I had the same problem on a 64bit linux mint machine. The only thing that worked for me was this python script : import sys, select, subprocess while True: p = subprocess.Popen(['xset', 'dpms', 'force', 'off'], stdout=subprocess.PIPE, stderr=subprocess.PIPE) if sys.stdin in select.select([sys.stdin], [], [], 0)[0]: break Of course, he also did misspell the word "none" LOL I feel there is something smelly in the garbage when you have to write a frigging program to slap down what the eco-greenie warriors feel justified in forcing on you. Sigh. Ted -----Original Message----- From: PLUG <plug-boun...@pdxlinux.org> On Behalf Of bri...@pounceofcats.com Sent: Monday, May 1, 2023 8:52 PM To: Portland Linux/Unix Group <plug@pdxlinux.org> Subject: Re: [PLUG] the dreaded hang Hi, Problem is verified. xset -dpms and i can leave it on all night and no problem. don't do that and the display goes away at some point. I did verify it's only the video card as I was logged in remotely. The second part of this question would be how can I kill and restart the X server from the ground up ? I'm using linux mint and it's not particularly straightforward. I managed to figure out how to restart the display manager but I realized that's not good enough and that I really need to restart the x-server (after killing it) and see if it will recover. Not even sure that will work, it probably needs to reinitialize the video card which may only happen at boot. Brian On Mon, 17 Apr 2023 03:36:32 +0000 Ted Mittelstaedt <t...@portlandia-it.com> wrote: > X and friends have insisted on actuating the screensaver for a long time now > and they use dpmi > > I have found this does lock up some hardware. Not just on Linux I've had > Windows lock up various laptop hardware as well attempting to "save the LCD > screen from burn in" (I wasn't aware LCD screens burned but what do I know > LOL) > > For some reason X makes it damn near impossible to shut the screensaver off > on boot so that the machine will just boot to the login screen and leave it > on forever. When the system is on a KVM it does NOT need a screensaver. Nor > does it need to be wasting CPU cycles on drawing "pipes" or other nonsense. > > Various xset invocations once you login seem to disable the "screensaver" > > Ted > > -----Original Message----- > From: PLUG <plug-boun...@pdxlinux.org> On Behalf Of bri...@pounceofcats.com > Sent: Sunday, April 16, 2023 7:21 PM > To: Portland Linux/Unix Group <plug@pdxlinux.org> > Subject: [PLUG] the dreaded hang > > Hi, > > So i just finished putting together a new PC AMD K7/Asus MB. > > if i leave it alone for some indeterminate amount time, on the order of 1 to > 2 hours, it decides to lock up - sort of. The caps lock key is still working, > for example, but the monitor doesn't see a signal. > > A few things that i've checked: > > 1 set the display shut-off to a few minutes and sat there and watched it shut > off the display. Not a problem. > > 2 suspended it, unsuspended it, and it recovered. that was a shocker. suspend > mode and linux have never worked for me. not ever. > > Regardless i have suspend mode time set to never and i just now changed the > display shut-off time to never. Even though i watched it shut-off without a > problem I'm still suspicious that it may be the problem (for example, maybe > it has to stay in display shut off for a few minutes). > > A couple of things i would like to do. > > Is there a way to enable more detailed kernel tracing so i could look at a > log file and see if can figure out if there's a particular activity preceding > the problem ? > > One thing that occurs to me as i'm typing this is that I did not try to SSH > in and see if things were working - it could simply be a video card driver > problem (AMD video card). > > The odd thing is that it's running 100% reliably when i'm sitting at the > computer > > Any other things I might try to narrow down the problem ? > > > -- Brian