Are screensavers working with current ROM builds?

Hi guys,

For those of you that run current ROM builds (ie. downloaded from ROOL on a last-few-days basis), could you check if Screensavers are working, please? Double click !Boot, go to Screen, select a screensaver and click “try”.

I’m asking because I was testing a bunch of things on an ARMBook this morning, and after months of it happily dimming the screen when idle, it, erm wasn’t. When I checked other screensavers, I couldn’t trigger any of them.

I’d just like to establish whether this is something in the current ROMs, or whether it it something specific to this build or my machine.

Working here with original RPi2 running 5.27 of today.

Use DPMS normally, but tried DeskBall which worked as expected.

Working here on RISC OS 5.27 (31-Aug-19) RPi3B.

(Esp. when you remember to change the blank delay value – face palm!)

For the record, I get a blank screen, but it never switches the monitor off. By design I presume.

Thanks for this, everyone. Very helpful.

Followup – can those who have it working please do *help scrsaver and let me know version number please.

It seems there are several different versions in the tree with conflicting dates vs version numbers. Git teething trouble!

let me know version number please

Module is: ScrSaver 0.14 (01 Aug 2015) 1.9.2.4

Original RPi2 running 5.27 of today.

Module is: ScrSaver 0.14 (01 Aug 2015) 1.9.2.4

ditto, in the downloaded ROM, or a local build from a source code archive.

But in git https://gitlab.riscosopen.org/RiscOS/Sources/Video/UserI/ScrSaver/blob/master/VersionNum 0.22 (14 Jan 2012).

OK, I think that explains it :)

That’s the same version that’s running successfully on my ARMX6, and on the older ARMBook ROM.

Git has a version 0.22 in it, but with an older date (2012) so clearly there’s something very odd going on.

Now I’m getting paranoid… what other little version gremlins are there in the Git tree (gulp!)

what other little version gremlins

Shhh! Don’t invoke nemo!

Module is: ScrSaver 0.14 (01 Aug 2015) 1.9.2.4

If you look on CVS, that’s from the Ursula branch (i.e. not MAIN).
https://www.riscosopen.org/viewer/view/apache/RiscOS/Sources/Video/UserI/ScrSaver/VersionNum?
It’s in the Ursula branch on GitLab as well:
https://gitlab.riscosopen.org/RiscOS/Sources/Video/UserI/ScrSaver/commits/Ursula

OK, I’m not even going to ask what a module badged for Ursula (RO 3.8 aka 4) is doing being used in preference in a RO5 ROM. That’s all kinds of nemo-baiting wrong (and I’d be joining him on his battle-wagon)!

Seems like there are about three other modules in similar boats, so this was good work – this Git migration has been a bit traumatic behind the scenes! ;)

Git has a version 0.22 in it, but with an older date (2012) so clearly there’s something very odd going on.

ScrSaver is one of a handful of components where we don’t use the master branch. You want the Ursula branch

https://gitlab.riscosopen.org/RiscOS/Sources/Video/UserI/ScrSaver/blob/Ursula/VersionNum

I think the correct way of updating the submodule to point to the right place would be:

cd RiscOS/Sources/Video/UserI/ScrSaver
git checkout Ursula
cd ../../../../../
git config -f .gitmodules submodule.RiscOS/Sources/Video/UserI/ScrSaver.branch Ursula

And then commit those changes (should show up as a change to .gitmodules, and the ScrSaver submodule).

The ‘git config -f’ command could also be handled by hand-editing the .gitmodules file.

*help scrsaver
==> Help on keyword ScrSaver
Module is: ScrSaver 0.14 (01 Aug 2015) 1.9.2.4

RISC OS 5.27 (31-Aug-19) RPi3B

“I’ve got all the right version numbers…”

For the record, I get a blank screen, but it never switches the monitor off. By design I presume.

If you’re on a Pi then you need hdmi_blanking=1 in config/txt. I don’t know why it’s not set by default.

If you’re on a Pi then you need hdmi_blanking=1 in config/txt. I don’t know why it’s not set by default.

According to the Raspberry Pi documentation “this feature may cause issues when using applications which don’t use the framebuffer” which may explain why it’s not the default.

Perhaps there’s more of an argument that it should be added to the standard config.txt settings for RISC OS. I can feel a wiki update coming on…

If you’re on a Pi then you need hdmi_blanking=1 in config/txt. I don’t know why it’s not set by default.

Thanks, put it in, but not rebooting as in the middle of something, I’ll post again if it doesn’t work!