On Mon, 21 Jul 2008 10:16:12 -0500 nobody <annonymous at (no spam) none.com> wrote:

| I'm running suse 11.0 w/kde4.1 beta & have the screensaver on BUT the
| "screensaver" never activates (had set the saver to display the torus)
| thingy. The monitor still "blanks"; & my monitor led power light shows
| yellow instead of green for "on". The yellow is displayed when the
| monitor is not getting a signal.
|
| Is this, then, a hardware triggered energy/power/screen saver applied
| by something?

Some number of minutes after mine blanks out, my monitor does the yellow light
thing. It doesn't get sync anymore. So I presume something turned it off.
The monitor has shutdown most of its circuitry, especially the backlight. So
it is saving energy.

But there are times when I want to have it stay on, such as when I have the
weather radar display full screen during stormy weather.

I sure hope it isn't a case of some magic subset and in a specific order that
is required to do this. There should be a setting somewhere that controls
how long with no input before blanking or running the screen saver. Maybe if
that value is set to 0 it would disable.

I'm also finding that on text console, this command that should prevent the
blanking there, sometimes does not (e.g. sometimes it blanks out anyway):

setterm -blank 0

I also tried this inside xterm to see if xterm would "know what to do". No
such luck.

If the monitor itself has a menu, you might be able to disable power

On Tue, 22 Jul 2008 20:50:08 GMT Bill Marcum <marcumbill at (no spam) bellsouth.net> wrote:
| On 2008-07-21, phil-news-nospam at (no spam) ipal.net <phil-news-nospam at (no spam) ipal.net> wrote:
|
|> I sure hope it isn't a case of some magic subset and in a specific order that
|> is required to do this. There should be a setting somewhere that controls
|> how long with no input before blanking or running the screen saver. Maybe if
|> that value is set to 0 it would disable.
|
|> I'm also finding that on text console, this command that should prevent the
|> blanking there, sometimes does not (e.g. sometimes it blanks out anyway):
|
|> setterm -blank 0
|
|> I also tried this inside xterm to see if xterm would "know what to do". No
|> such luck.
|
| If the monitor itself has a menu, you might be able to disable power
| saving there.

It's not the power saving I'm trying to disabled. The screen goes blank/black.
I want the image (weather radar) to stay on the screen all the time. Imagine
it as a kiosk or as a video feeder to a cable TV weather radar channel (which
reminds of me of a few times I have seen a MS Windows blue screen on some
cable text channels).

On 23 Jul 2008 13:38:46 GMT Niklaus Kuehnis <kuehnik_0505 at (no spam) gmx-topmail.de> wrote:
| phil-news-nospam at (no spam) ipal.net wrote:
|> On Tue, 22 Jul 2008 20:50:08 GMT Bill Marcum <marcumbill at (no spam) bellsouth.net> wrote:
|> | On 2008-07-21, phil-news-nospam at (no spam) ipal.net <phil-news-nospam at (no spam) ipal.net> wrote:
|> |
|> |> I sure hope it isn't a case of some magic subset and in a specific order that
|> |> is required to do this. There should be a setting somewhere that controls
|> |> how long with no input before blanking or running the screen saver. Maybe if
|> |> that value is set to 0 it would disable.
|> |
|> |> I'm also finding that on text console, this command that should prevent the
|> |> blanking there, sometimes does not (e.g. sometimes it blanks out anyway):
|> |
|> |> setterm -blank 0
|> |
|> |> I also tried this inside xterm to see if xterm would "know what to do". No
|> |> such luck.
|> |
|> | If the monitor itself has a menu, you might be able to disable power
|> | saving there.
|
|> It's not the power saving I'm trying to disabled. The screen goes blank/black.
|> I want the image (weather radar) to stay on the screen all the time. Imagine
|> it as a kiosk or as a video feeder to a cable TV weather radar channel (which
|> reminds of me of a few times I have seen a MS Windows blue screen on some
|> cable text channels).
|
| Just an idea: Could you send a periodic keyboard event, e.g. with
| xvkbd or maybe with expect?

I don't know what xvkbd is. How would expect send a keyboard event? If I
stuff one in to an xterm pty it won't be seen by X as an input, but only as
xterm output. I have tried stuffing keyboard events into /dev/tty10 but the
X server running on tty10 doesn't see it (I'm assuming because it accesses
the keyboard at a lower level so it sees the ups and downs, not just the
ASCII queue). Maybe I need to write a kernel patch to inject keyboard events
at a lower level (e.g. key scan code and up/down).

But I still think it is better to identify what bit of code in some component
of the X window system is futzing with the screen blanking and make it stop.

Have you checked the "/etc/sysconfig/powersave/....." to see if any of the

On Thu, 24 Jul 2008 14:37:27 -0500 nobody <annonymous at (no spam) none.com> wrote:
| On 2008-07-24, phil-news-nospam at (no spam) ipal.net <phil-news-nospam at (no spam) ipal.net> wrote:
|> On 23 Jul 2008 13:38:46 GMT Niklaus Kuehnis <kuehnik_0505 at (no spam) gmx-topmail.de> wrote:
|>| phil-news-nospam at (no spam) ipal.net wrote:
|>|> On Tue, 22 Jul 2008 20:50:08 GMT Bill Marcum <marcumbill at (no spam) bellsouth.net> wrote:
|>|> | On 2008-07-21, phil-news-nospam at (no spam) ipal.net <phil-news-nospam at (no spam) ipal.net> wrote:
|>|> |
|>|> |> I sure hope it isn't a case of some magic subset and in a specific order that
|>|> |> is required to do this. There should be a setting somewhere that controls
|>|> |> how long with no input before blanking or running the screen saver. Maybe if
|>|> |> that value is set to 0 it would disable.
|>|> |
|>|> |> I'm also finding that on text console, this command that should prevent the
|>|> |> blanking there, sometimes does not (e.g. sometimes it blanks out anyway):
|>|> |
|>|> |> setterm -blank 0
|>|> |
|>|> |> I also tried this inside xterm to see if xterm would "know what to do". No
|>|> |> such luck.
|>|> |
|>|> | If the monitor itself has a menu, you might be able to disable power
|>|> | saving there.
|>|
|>|> It's not the power saving I'm trying to disabled. The screen goes blank/black.
|>|> I want the image (weather radar) to stay on the screen all the time. Imagine
|>|> it as a kiosk or as a video feeder to a cable TV weather radar channel (which
|>|> reminds of me of a few times I have seen a MS Windows blue screen on some
|>|> cable text channels).
|>|
|>| Just an idea: Could you send a periodic keyboard event, e.g. with
|>| xvkbd or maybe with expect?
|
|> I don't know what xvkbd is. How would expect send a keyboard event? If I
|> stuff one in to an xterm pty it won't be seen by X as an input, but only as
|> xterm output. I have tried stuffing keyboard events into /dev/tty10 but the
|> X server running on tty10 doesn't see it (I'm assuming because it accesses
|> the keyboard at a lower level so it sees the ups and downs, not just the
|> ASCII queue). Maybe I need to write a kernel patch to inject keyboard events
|> at a lower level (e.g. key scan code and up/down).
|
|> But I still think it is better to identify what bit of code in some component
|> of the X window system is futzing with the screen blanking and make it stop.
|
| Have you checked the "/etc/sysconfig/powersave/....." to see if any of the
| scripts is doing the blanking?; expecially when not using gnome or kde.

/etc/sysconfig: No such file or directory

I've never seen Slackware create any such directory. Is that an X thing?

Even this command comes up empty: find /etc /var -print | fgrep -i sysconfig