hehe... One of those annoyances I'm just gonna have to live with then!.. this is the output of xset q : Keyboard Control: auto repeat: on key click percent: 0 LED mask: 00000002 auto repeat delay: 500 repeat rate: 30 auto repeating keys: 00ffffffdffffbbf fadfffdfffdfe5ef ffffffffffffffff ffffffffffffffff bell percent: 50 bell pitch: 400 bell duration: 100 Pointer Control: acceleration: 2/1 threshold: 4 Screen Saver: prefer blanking: yes allow exposures: yes timeout: 0 cycle: 0 Colors: default colormap: 0x20 BlackPixel: 0 WhitePixel: 16777215 Font Path: /home/ubuntu/.gnome2/share/cursor-fonts,/usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,/home/ubuntu/.gnome2/share/fonts Bug Mode: compatibility mode is disabled DPMS (Energy Star): Standby: 0 Suspend: 0 Off: 0 DPMS is Enabled Monitor is On File paths: Config file: /etc/X11/xorg.conf Modules path: /usr/lib/xorg/modules Log file: /var/log/Xorg.0.log So unless theres anything there that helps, gonna just have to stick to turning the monitor off by the switch at night... Cheers anyways Alex On Thu, Feb 19, 2009 at 6:59 PM, Jan T. Kim <j.kim@uea.ac.uk> wrote:

On Thu, Feb 19, 2009 at 06:33:22PM +0000, Chris Glover wrote:

...

Alex Scotton wrote:

...

Hi All,

As a result of not being able to define in a google-able way whats wrong with my setup at the moment, I have resorted to mailing you guys... As I have seen hundred of problems solved by you guys..

My problem is a simple, yet annoying one... Whenever my system (Ubuntu 8.10 | Kernel 2.7.11) is IDLE for long enough to turn the monitor "off", the monitor goes into standby fine (green light turns to orange light) but every so often the monitor will boot up again, and flash up on the screen "No Signal" and go back to standby mode... there seems to be no consistency to it, it is very random.. However as I dual boot with windows, I was able to identify that the monitor works fine in windows, and I haven't had these problems before..

Further Specs if required are available but you may have to tell me where to find those stats (as am still learning the basics)

However I can tell you that it is a ViewSonic VP191b on a Nvidia geforce 6150SE using the proprietary drivers!

Any help will be much appreciated, and to all readers the wishes of a good day!

Peace!

Alex

Hi Alex,

Viewsonic monitors are notorious for having iffy power management implementations. My VX2435wm will goto sleep when being driven by Linux and not wake up again. Works fine with everything else though.

Basically its the monitor firmware!

Two choices, either buy a new monitor or stop being green :-)

just as a random guess, could there be any process that triggers that flicker? A screensaver might be a likely suspect, disabling that might be worth a try. Also taking a look at the output of ``xset q'' might be of interest.

As yet another story about silly monitor behaviour, I've found that my Asus flatscreen preserves its colour intensity settings only if it's "switched off" using the button on the monitor but remains connected to mains power. If I switch off the power at the mains socket, the display will start up with colours maxed out. It does remember my settings, though, and starts using them when I navigate to the on-screen control panel for changing them...

Best regards, Jan -- +- Jan T. Kim -------------------------------------------------------+ | email: j.kim@.uea.ac.uk | | WWW: http://www.cmp.uea.ac.uk/people/jtk | *-----=< hierarchical systems are for files, not for humans >=-----*

_______________________________________________ main@lists.alug.org.uk http://www.alug.org.uk/ http://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!

SOLVED!!!!!!!!! Thanks to Jan T Kim (much thanks)

I think the standby, suspend and off values should be non-zero, the xset man page says that "a value of zero disables a particular mode", so all modes seem disabled here. So ``xset dpms 10 20 30'' might be worth trying (well, for testing, you'll want longer times in the long run).

Ok, these values are seconds right?.. because i just unticked that Activate screensaver tick, and the monitor is turning off very quickly hehe.. Ok so after realising what you had asked me to do, i started debugging, and i beleive if this sounds likely that the flikering off and on begins in the 2nd stage of suspend, after setting dpms to 10 20 30, 10 30 60, 10 60 120, and recognising it was doing it after the 2nd alloted amount of seconds.... so I have now set to 60 0 0 and there are no problems whatsoever... Regards this "xset" is it launched the same time the screensaver is?? So could I see it to DPMS 60 0 0 and then to turn screensaver on after 10mintues will it be 11minutes and then the screen will go into standby?? or should i set it to 660 0 0? ----------> Just to answer the questions in order for correct debugging of what causes the problem (and because I had wrote all this before playing around and realising the true potential of the xset dpms command)

Are you using DVI or VGA?

VGA currently as upgraded my motherboard and no DVI port :(

Do you use GNOME. There was an issue with GNOME and Debian

I use gnome and not using debian (officialy) as I am using Ubuntu 8.10 (which I know is based on debian, but I am right in saying im not using debian right ;) )

You said later you are still learning whereas this kernel version number, unless Ubuntu have invented their own numbering scheme, is a development work-in-progress and therefore for people developing the kernel and the brave. The latest stable version is 2.6.28.6.

Ha ha sorry was in windows at the time, and was trying to remember this number from grub.. it is actually 2.6.27-11-generic Thanks an bunch guys Alex

On Fri, Feb 20, 2009 at 03:32:03PM +0000, Alex Scotton wrote:

SOLVED!!!!!!!!! Thanks to Jan T Kim (much thanks)

...

I think the standby, suspend and off values should be non-zero, the xset man page says that "a value of zero disables a particular mode", so all modes seem disabled here. So ``xset dpms 10 20 30'' might be worth trying (well, for testing, you'll want longer times in the long run).

Ok, these values are seconds right?..

yes, indeed.

because i just unticked that Activate screensaver tick, and the monitor is turning off very quickly hehe.. Ok so after realising what you had asked me to do, i started debugging, and i beleive if this sounds likely that the flikering off and on begins in the 2nd stage of suspend, after setting dpms to 10 20 30, 10 30 60, 10 60 120, and recognising it was doing it after the 2nd alloted amount of seconds.... so I have now set to 60 0 0 and there are no problems whatsoever...

It generally seems that the settings of your X server (which you control using xset) and the ideas that your screensaver has about these settings are not quite consistent. Personally I use xscreensaver and I've never seen such phenomena so far, as far as I can tell xscreensaver just displays its fancy animations and does not interfere with the DPMS stuff. Perhaps the gnome screensaver is different.

Regards this "xset" is it launched the same time the screensaver is??

This again depends on the window manager or desktop you use. The initial values for standby, suspend, and switch off time come from the xorg.conf file (options StandbyTime, SuspendTime and "OffTime, respectively), xset is just a program to change these parameters on a running X server.

So could I see it to DPMS 60 0 0 and then to turn screensaver on after 10mintues will it be 11minutes and then the screen will go into standby?? or should i set it to 660 0 0?

It all depends what you want. If you switch to standby before the screensaver kicks in, you'll never get to see the screensaver's fancy animations. If you use the screen saver for locking the screen, rather than just "saving" it, locking the X screen after putting the LC display on standby may make sense, though. Notice that with the "660 0 0" you'll never get the suspend or off modes. I don't know whether that's a problem, but just to test whether off mode works for you and it's really just the suspend mode that ends up in flicker, I'd try ``xset 60 0 60''. Best regards, Jan -- +- Jan T. Kim -------------------------------------------------------+ | email: j.kim@.uea.ac.uk | | WWW: http://www.cmp.uea.ac.uk/people/jtk | *-----=< hierarchical systems are for files, not for humans >=-----*