What's the incantation to turn on screen blanking on 64 bit RasPiOS?

There's a config button in Preferences > RasPi config > display,
but the button is ambiguous; light grey vs dark grey.

It's also possible to set screen blanking in raspi-config, that's
unambiguous and it's on.

The screen doesn't blank no matter what I do. Are there yet more
switches that I've overlooked?

At the moment xset -q reports:
eyboard Control:
auto repeat: on key click percent: 0 LED mask: 00000000
XKB indicators:
00: Caps Lock: off 01: Num Lock: off 02: Scroll Lock: off
03: Compose: off 04: Kana: off 05: Sleep: off
06: Suspend: off 07: Mute: off 08: Misc: off
09: Mail: off 10: Charging: off 11: Shift Lock: off
12: Group 2: off 13: Mouse Keys: off
auto repeat delay: 500 repeat rate: 33
auto repeating keys: 00ffffffdffffbbf
fadfffefffedffff
9fffffffffffffff
fff7ffffffffffff
bell percent: 50 bell pitch: 400 bell duration: 100
Pointer Control:
acceleration: 20/10 threshold: 10
Screen Saver:
prefer blanking: yes allow exposures: yes
timeout: 0 cycle: 600
Colors:
default colormap: 0x20 BlackPixel: 0x0 WhitePixel: 0xffffff
Font Path:
built-ins
DPMS (Energy Star):
Server does not have the DPMS Extension

Thanks for reading!

bob prohaska

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On a sunny day (Thu, 19 Jan 2023 01:12:19 -0000 (UTC)) it happened bob
prohaska <bp@www.zefox.net> wrote in <tqa5dj$14e8m$1@dont-email.me>:

What's the incantation to turn on screen blanking on 64 bit RasPiOS?

I dunno, but I always use xset from a terminal in Linux:

xset s 300
blanks the sceen after 300 seconds.

xset s 0 stops any blanking

see man xset for more good stuff

Put it in your startup script?
Works on my 32 bit Pi4 8GB, just tested
and on all my Linux computahs ;-)

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

Jan Panteltje <pNaonStpealmtje@yahoo.com> wrote:

On a sunny day (Thu, 19 Jan 2023 01:12:19 -0000 (UTC)) it happened bob prohaska <bp@www.zefox.net> wrote in <tqa5dj$14e8m$1@dont-email.me>:

What's the incantation to turn on screen blanking on 64 bit RasPiOS?

I dunno, but I always use xset from a terminal in Linux:

xset s 300
blanks the sceen after 300 seconds.

xset s 0 stops any blanking

see man xset for more good stuff

Put it in your startup script?
Works on my 32 bit Pi4 8GB, just tested
and on all my Linux computahs ;-)

I tried using xset s 30 in interactive mode. It changed
the timeout value for xset q, so I think it "took", but
the screen still doesn't blank.

This is a 64 bit system, might that be the trouble?
Must the command be issued when the x serter is started?

Thanks for writing!

bob prohaska






--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

panteltje <alien@comet.invalid> wrote:

Maybe enable DPMS?
What does
xset q
say about DPMS?

Screen Saver:
prefer blanking: yes allow exposures: yes
timeout: 30 cycle: 600
Colors:
default colormap: 0x20 BlackPixel: 0x0 WhitePixel: 0xffffff
Font Path:
built-ins
DPMS (Energy Star):
Standby: 600 Suspend: 600 Off: 600
DPMS is Enabled
Monitor is On


As of last night blanking didn't work. This morning, it does.
The only change was killing the chromium browser. When I restarted
the browser blanking still worked.

I'm thoroughly puzzled. When first set up the machine didn't blank,
then I turned blanking on and it worked. After an update/upgrade
cycle it stopped blanking, after repeated attempts to set blanking
on and rebooting it still didn't blank. Just now, a little while
after stopping chromium, blanking resumed.

I'll do nothing and watch how it behaves after a few reboots.

Thanks for writing!

bob prohaska

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On a sunny day (Fri, 20 Jan 2023 15:42:04 -0000 (UTC)) it happened bob
prohaska <bp@www.zefox.net> wrote in <tqecoc$24ag9$2@dont-email.me>:

As of last night blanking didn't work. This morning, it does.
The only change was killing the chromium browser. When I restarted
the browser blanking still worked.

I'm thoroughly puzzled. When first set up the machine didn't blank,
then I turned blanking on and it worked. After an update/upgrade
cycle it stopped blanking, after repeated attempts to set blanking
on and rebooting it still didn't blank. Just now, a little while
after stopping chromium, blanking resumed.

I'll do nothing and watch how it behaves after a few reboots.

Thanks for writing!

Good it works,
I reminds me of something.
If the system thinks something is running it won't blank.
I think I did see that with for example mplayer playing movies.
Maybe chromium had some URL with video or similar content selected?

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

panteltje <alien@comet.invalid> wrote:

On a sunny day (Fri, 20 Jan 2023 15:42:04 -0000 (UTC)) it happened bob prohaska <bp@www.zefox.net> wrote in <tqecoc$24ag9$2@dont-email.me>:

As of last night blanking didn't work. This morning, it does.
The only change was killing the chromium browser. When I restarted
the browser blanking still worked.

I'm thoroughly puzzled. When first set up the machine didn't blank,
then I turned blanking on and it worked. After an update/upgrade
cycle it stopped blanking, after repeated attempts to set blanking
on and rebooting it still didn't blank. Just now, a little while
after stopping chromium, blanking resumed.

I'll do nothing and watch how it behaves after a few reboots.

Thanks for writing!

Good it works,
I reminds me of something.
If the system thinks something is running it won't blank.
I think I did see that with for example mplayer playing movies.
Maybe chromium had some URL with video or similar content selected?

Yes, that seems to be the problem. Chromium had a New York Times
front page open tab, which contained a video clip that didn't stop
looping. There doesn't seem to be a visible way to turn it off.

Is there some way to make the screen blanker ignore HDMI traffic
and only react to mouse and keyboard? The default behavior is self
defeating and seemingly counterproductive.

Thanks for reading!

bob prohaska

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On a sunny day (Tue, 7 Feb 2023 22:39:14 -0000 (UTC)) it happened Jim Jackson <jj@franjam.org.uk> wrote in <slrntu5koi.jvc.jj@iridium.wf32df>:

On 2023-02-07, Jan Panteltje <alien@comet.invalid> wrote:

On a sunny day (Thu, 19 Jan 2023 05:19:48 GMT) it happened Jan Panteltje >><pNaonStpealmtje@yahoo.com> wrote in <tqak6b$1a72k$1@dont-email.me>:

On a sunny day (Thu, 19 Jan 2023 01:12:19 -0000 (UTC)) it happened bob >>>prohaska <bp@www.zefox.net> wrote in <tqa5dj$14e8m$1@dont-email.me>:

What's the incantation to turn on screen blanking on 64 bit RasPiOS?

I dunno, but I always use xset from a terminal in Linux:

xset s 300
blanks the sceen after 300 seconds.

xset s 0 stops any blanking

see man xset for more good stuff

Put it in your startup script?
Works on my 32 bit Pi4 8GB, just tested
and on all my Linux computahs ;-)

Maybe it would make sense if Raspberry P4 came with something like
Type F1 for BIOS setup
on power-up.
\
Now that is HAS EEPROM?

Because whether it does screen blanking/screen saver is nothing to do
with a "BIOS"?

Sorry replied to the wrong posting it seems
Still a normal type F1 for BIOS setup would be a good thing.
It was intended for the boot sequence sdcard versus USB thread
any normal BIOS allows you to select that.

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)