I found 2 methods to stop that Blanking one is definitely recommended the other definitely not recommended!!
1st method is here:
Help needed on Opensuse 11.4! Step-by-step NOBLANK power management
This does work for 12.1 too.
The screensaver ran for 2 hours with this way.
2nd method was something I tried before I found the above way. THIS WAY IS NOT RECOMMENED It is only here if the above way does not work for you.
1)Kickoff>Configure Desktop>Statrup and Shutdown
2)Select Service Manager
3)In the lower right pane uncheck Power Management
4)Click apply
I ran my screensaver for 2 hours this way as well. BUT
The reason I say this is not recommended is because there’ll be a big red “X” over Power Management. I really don’t know what long term effects of that would be. I’m relatively sure that very few here want to find out the hard way.
Acknowledgments:
To jdmcdaniel3 for his script
To deano_ferrari who has written so many posts on this that I ran a search on all his posts & found the post for method 1.
Thanks Again dude I would’ve never found that script without Ya’ !
I am normally not annoyed by the blanking. However, there are occasions:
I have just selected that line, and clicked stop. After the video has finished, I repeat and click start to restore the normal blanking. That works pretty well. I never did unckeck that box, so that if I forgot to restart then it would restart on the next login.
Let me say that while the terminal command can work: xset s noblank -dpms, it does not seem to work all of the time automatically even when run on startup. I often find that I must open a terminal session, after startup, and run this command several times and then the blanking does seem to stop. Further, I don’t think it is a KDE thing only as I have had gnome go blank as well. Anyway, I have not found a reliable method using the terminal command as it did work properly under openSUSE 11.4 or why this oddity has returned using openSUSE 12.1.
Thank You,
Jim,
I also found this out just today. Do you think it might for 12.1 anyway related to sysetmd?
So I think that anything is possible and sysemd could be the cause. Thing is, we need to learn to live with and and fix any issues going on with systemd. So, right now I am using openSUSE 12.1 with an Intel i7 and nVIDIA graphics & KDE desktop. All day, I would get a blank screen when gone for more than 10 minutes. I have my old autostarted ssreset script installed. I tried running **xset s noblank -dpms **a single time twice in terminal and closed the terminal window but it never made any difference.My PC had been running ten hours since first boot before my dinner break. Just before supper, I opened up a terminal session and ran the command: xset s noblank -dpms seven times [size=2]and closed the terminal window[/size].. I then went and ate Thanksgiving Turkey dinner with the wife and was gone from the computer for two hours. When I got back, my screen saver was running normally. So, the fix does not seem to work when ran automatically on startup but does work, sort of. Now indeed this might be blamed on systemd some how. But, when I would open up a terminal session and run the command once, it did nothing. So, why does seven times make any difference? Perhaps only five will do, but really, the whole thing is kind of dumb for someone used to a more scientific solution than the one that is working for me now. Also I was not swinging a chicken over my head at the time and don’t intend on trying that one either.
Thank You,
Interesting findings James. I hope we get to have a better understanding of this behaviour in the near future. It would be interesting to see ‘xset q’ output after each invocation of the command, although it would probably reflect the change after the first invocation. Clearly though, it is not necessarily being applied, or it is being actively re-enabled again soon after, perhaps by Xorg?
Interesting findings James. I hope we get to have a better understanding of this behaviour in the near future. It would be interesting to see ‘xset q’ output after each invocation of the command, although it would probably reflect the change after the first invocation. Clearly though, it is not necessarily being applied, or it is being actively re-enabled again soon after, perhaps by Xorg?
Running xset q after a restart and presumable the ssreset script has run shows that blanking and dpms is not disabled. So, something not working on a restart. Is that due to systemd or to shells not being loaded? I don’t know. Running the xset command once in terminal and checking its status shows that blanking and dpms is disabled even though it makes no difference. Running it seven times was just something I thought might be the number of virtual terminals plus one which has nothing to do with it as far as I can tell. The fact is, doing nothing but disabling blanking in power management and making sure the screen saver is not blanking still results in your screen going blank just as it did way back when with openSUSE 11.4, before it went into final release. I don’t what was done to get rid of it then and I don’t know for sure what gets rid of it now. Though, swinging a chicken over your head is easier to understand when required.
Thank You,
This mumbo jumbo had me scratching me head 
Screen Blanking? My screen never goes blank.
The fact is, doing nothing but disabling blanking in power management and making sure the screen saver is not blanking still results in your screen going blank just as it did way back when with openSUSE 11.4, before it went into final release. I don’t what was done to get rid of it then and I don’t know for sure what gets rid of it now.
Sounds like a bug report is required…
Though, swinging a chicken over your head is easier to understand when required.
LOL
This mumbo jumbo had me scratching me head
Screen Blanking? My screen never goes blank.
Mine neither, but I’m running 11.4 with ‘Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02]’. IIRC, my old laptop with Radeon X300 chipset did suffer from this, until I added ‘xset -dpms s off’ in startup script.
12.1 here and it’s working as it did in 11.4
My settings though are the screensaver is off
and: http://dl.dropbox.com/u/10573557/SUSE%20Misc/powersettings.jpeg
So the problem is real for me and happens in a VM and a normal installation. Since I have but one real installation, its hard to say what is at fault except that more than one person has indicated they have seen the problem. Since we we all have our own setups we use, it could be due to one of things we do not set by default, but not sure what that might be at present. I shall keep looking for a better solution. If anyone else has noticed their screen going blank when it should not, please pipe in and let us know about it along with information about your hardware and openSUSE installation details.
Thank You,
This has been plaguing me with 12.1 64bit. Dell Studio with i5, and fglrx driver. With 11.4, I could simply disable dpms. 12.1 doesn’t seem to honor this. When I issue “xset s noblank -dpms”, dpms and blanking are off, but the screen still goes blank after 5-10 minutes of screen saver time. I will try doing it seven times later and report back;)
Well, for me that 2nd method I wrote about? It just gave up the ghost too.
So to go with JD I’ve just installed the nvidia 290.15 drivers it still persists.
Now an odd thing the other PC in my sig which uses the unichrome drivers doesn’t seem to have this problem.
Is this an Nvidia thing?
I’d love to know if anyone with ATI or Intel drivers have this as well.
Before i leave one more thing I’ve also tried adding the following
Added this to the /etc/x11/xorg,conf.d/50-monitor,conf
Option "BlankTime" "0"
Option "StandbyTime" "0"
Option "SuspendTime" "0"
Option "OffTime" "0"
All I got with this was no x at all. By removing the Option “OffTime” “0” with a live cd I got x back but the blanking goes on.
Well OK it’s not an nvidia thing!
So the latest nVIDIA version is 290.10 I think. So, this might be an nVIDIA issue I suppose, but when in a Virtual Session, it still blanks, but is that the Host or Guest that is blanking. It kind of blows my mind.
Thank You,
Hey guys I found this from here:
linux - Disable screen blanking on text console - Unix and Linux - Stack Exchange
The only permanent solution is to add consoleblank=0 to the kernel command-line. You can view the value (which defaults to 600 seconds) in:
/sys/module/kernel/parameters/consoleblank
(note that the file is read-only). The only way to change the value of consoleblank is to reboot with the new kernel command-line option.
Because in my quest to find an answer to this I checked into /sys/module/kernel/parameters/consoleblank & sure enough there is a txt file there that is read only called consoleblank. The only item written inside 600. Which from what I’ve read is in seconds meaning the 10 minutes that’s getting under our skins.
The way to change it can be done by kernel command-line option.
As seen from the /usr/src/linux/Documentation/kernel-parameters.txt file.
In that txt file I found this:
consoleblank= [KNL] The console blank (screen saver) timeout in
seconds. Defaults to 10*60 = 10mins. A value of 0
disables the blank timer.
I personally don’t know how to do a kernel command-line how would one do that?
Add the kernel boot option to the relevant boot entry in /boot/grub/menu.lst
You could try it temporarily first, by typing the option at the grub menu screen
consoleblank=0
So, after seeing your great find Sagemta, I opened up my /boot/grub/menu.lst file and added in the kernel load option consoleblank=0 to the normal openSUSE startup line as below, just like using the nomodeset option required to install the nVIDIA proprietary video driver.
Alt-F2: kdesu kwrite /boot/grub/menu.lst
kernel /boot/vmlinuz-3.2.0-rc2-1.2-desktop root=/dev/disk/by-id/ata-INTEL_SSDSA2M080G2GC_CVPO037603KN080JGN-part1 resume=/dev/disk/by-id/ata-Hitachi_HDS723020BLA642_MN1221F305BDDD-part2 splash=silent quiet nomodeset **consoleblank=0** showopts vga=0x314
I saved the modified file and restarted openSUSE. I waited for 20 minutes and looked back at the openSUSE 12.1 PC and sure enough my normal screen saver was running and was not being blanked. You can make this a permanent addition by editing the bootloader file (/etc/sysconfig/bootloader) as root, find the line that starts with DEFAULT_APPEND= and add in the **consoleblank=0 command. ** Here is my example …
Alt-F2: kdesu kwrite /etc/sysconfig/bootloader
DEFAULT_APPEND="resume=/dev/disk/by-id/ata-Hitachi_HDS723020BLA642_MN1221F305BDDD-part2 splash=silent quiet showopts nomodeset consoleblank=0"
Way to go Sagemta!!!
Thank You,
Thanks guys! I’m going to try it now.