setterm -blank 0 added to the GRUB boot command typically is ignored by the kernel and I find myself having to use the arrow-up function
to type it again quickly over and over. It seems to work after
entering the command 15 or 20 times from a root terminal. I enter it as quickly as I can strike the 2 keys necessary (i.e., up arrow followed by the Enter key) and I usually can get a terminal to remain open.
Be advised that closing a terminal artificially held open via the
setterm -blank 0 command` seems to be interpreted by the kernel as a totally erroneous "indication" that is has permissions to go independently into sleep/hibernation mode. I recommend that you start a root terminal in, say, tty2 or tty3, and leave it running. As long as the terminal program remains active, on my system at least, it does appear that I may be permitted to keep my console monitor up and running.
setterm -blank 0 does not address the problem of who gave the system permissions to go independently into sleep/hibernation mode and how I can get control of my system back. It's important to me that my file server should be on-line and available at all times. To keep my serer running, I am personally rewriting some kernel modules. After I get those mods in place I will permanently disable software updates and my problem will be solved, at least until I purchase some newer hardware that requires a newer kernel, and then, in order to keep my server running, I will be forced to rewrite parts of the kernel again.