I agree. This can be frustrating… especially when attempting to monitor a fully automated install with no keyboard attached. (I have a bluetooth keyboard that doesn’t activate until the end of my install 45-55 minutes later…)
I believe that this issue is further upstream in the kernel (framebuffer module is my guess), though.
There may be a config.txt or module parameter setting that can be changed, though. I’ll take a peak into the settings and see.
basically, edit /etc/kbd/config
and set
BLANK_TIME=0
POWERDOWN_TIME=0
then reboot or /etc/init.d/kbd restart
I’m at work right now, so I haven’t tested this yet. I’ll do some preliminary testing tonight. I don’t think that it’s a good idea to make this a default change, but, perhaps set it during dietpi-software installs then reset it before the reboots…
Dan,
Do you think there would be an issue with adding this to the dietpi-software automated install logic?
like, around line dietpi-software:4630, if we are entering automation, disable screen blanking until next reboot…
hmm, if you will do, please only for RPi. It may work (not tested), but not on all other devices.
root@Odroid-C2:~# setterm -blank 0 -powersave off
setterm: terminal xterm does not support --blank
setterm: cannot (un)set powersave mode: Unpassender IOCTL (I/O-Control) für das Gerät
Good idea Rob, never thought of it. I think it would be best placed at the start and inside of Run_Installations function. I’ve created a Git ticket for this, your more than welcome to add this in if you like https://github.com/Fourdee/DietPi/issues/277