David C. Rankin wrote:
On 05/23/2018 12:23 PM, Per Jessen wrote:
Per Jessen wrote:
Peter Suetterlin wrote:
But this is only screenblank - DPMS might need setterm --powersave on
Yes, I'm just testing that. I'm waiting to see if my older systems will do a monitor suspend. (which I believe they did/should do).
Hmm, on the first attempt, I don't see any monitor suspend. Nor on the 2nd with a Leap15 system (setterm --blank 60 --powersave on).
TBH, it's not a major problem, we only have a few monitors in the datacentre, we're just not use to seeing them on all the time. Still, now that I've looked into it, having them suspend would be nice. (they can on for weeks and months).
This is frustrating has hell, and I think it is kernel related more than anything else. This problem showed up on Arch several months ago.
Ah, that's interesting.
The default console just stopped blanking itself. I don't recall if it was with 4.16 or one of the .1, .2 --- releases since. I just got to the point I leave the monitors turned off.
I know, the easiest solution. Except you have to reemember to do it :-(
If you find a solution, I'm interested. I can't believe crap just breaks that has been working fine for 15 years and isn't fixed before it gets released.
I have to agree, it's a bit annoying. Testing it is not so easy though. We've had Leap15 running for maybe 2 months, yet it was only yesterday I noticed this. It's one of these "exotic" things that many people have no reason to use. Well, as for a solution - I'll keep digging to see if I can have a monitor put into suspend, but the consoleblank default setting has to be in the kernel somewhere. -- Per Jessen, Zürich (15.2°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org