Pi 3 shutting down-ish

As far as I can tell, there were three “big” releases between those dates:

• BCMVideo 0.49
• Boot 1.26
• Kernel 5.95

If I have some free time (and that’s a big if!) I might do a test build with BCMVideo 0.48 but the updated Kernel, and see what happens. Or maybe the other way around; Kernel 5.94 but the latest BCMVideo.

Of course, Boot won’t be the problem since it’s not in ROM; I’ve just listed it for completeness.

Here is the 07-Mar-18 ROM but with BCMVideo 0.48 instead of 0.49. I’ve only done minimal testing, but since it’s intermittent, the more the merrier!

It’s been a few days and I haven’t had a single problem since rolling back to BCMVideo 0.48. It looks like 0.49 could indeed be the culprit here.

My experience has been pretty much the same. No lock-ups.

Thanks for the detective work Chris.

I have not seen any further problems since installing the bcm048 test ROM

Thanks Chris.

Edit Link to test ROM added.

since installing the bcm048 test ROM.

Available where? TIA.

Available where?

A few posts up, and here

Link added to my previous post.

Looking at the download stats, it seems that 15 people are A) running an affected post-RC15 ROM in the first place and B) care enough about it to download a custom ROM. It does seem that there’s a problem here!

If some of the other downloaders could post back with success/failure reports then that could be beneficial.

Did not yet use the bmc048 test ROM, but I activated a few days ago the ROM that triggered the issue. Just know I experienced the problem again. All I can say is that I was in the middle of reading an help file, maybe for 10 seconds after scrolling to the section I was interested in, when it blanked the screen and when unresponsive.

I will install the bmc048 ROM next and see if the problem can be triggered on that version.

A softload of BCMVideo 0.48 in PreDesk seems to help. The new RPi3B+ does require a later ROM than the custom bcm048 build.

I got delayed for a week, but I finally had the time to use the custom ROM build for 3-4 days and so far no shutdown issue. That said it could still be a little too soon since with the normal ROM I only triggered the issue twice in the same period.

One thing I mentioned in another thread about the normal ROM, still occurs with every boot of the custom ROM: the first action with the mouse button systematically goes wrong: dragging does not stop when you release the mouse button, a SELECT click opens a menu, that kind of things. It sounds to me like the initial state of buttons is incorrect (uninitialized state in the Wimp or the USB driver ?).

I have uploaded a firmware upgrade for users of the RC15 (and earlier) SD card image. This updates firmware to 27 Mar 2018 and includes an up to date ROM, but with BCMVideo reverted to 0.48 to avoid issues with the Pi model 3 B+.

Instructions here.

I see that BCMVideo 0.50 is now in CVS and while the change log doesn’t explicitly mention this issue, it does point out that the old version was unnecessarily changing the GPU mode or doing a “hardware pointer shutdown” in some cases. It might be worth stress testing this new version (although note that as of this moment the autobuilt ROM is not yet available).

The change in 0.50 is only there to mitigate a issue with screen resolution changes when RISC OS is in full control of the monitor (i.e. the new method, without the disable_mode_changes option): on most current LCD monitors the screen blacks out for a few seconds during the change. This is annoying and occurs even for simple cases like returning to the desktop from the command line (*F12), changing the number of colours in the desktop. The change just just prevents the mode change to be signalled to the monitor if there is no real change.

Since I use the disable_mode_changes option and the shutdown issue occurs for me, there is no need to try out the new version.

It might be worth stress testing this new version (although note that as of this moment the autobuilt ROM is not yet available).

Patience :)
The time stamp on the nightly tends to be around 08:30 – 08:40 and that’s GMT, if memory serves correctly, so probably some time in the next 15 minutes if I’ve got it right.

The change in 0.50 is only there to mitigate a issue with screen resolution changes when RISC OS is in full control of the monitor

Thanks for the explanation. A useful change, but still a pity.

Patience :)

I wasn’t complaining (for want of a better word) about it; I was just alerting readers before they rushed off and downloaded the older version by mistake :)

The change in 0.50 is only there to mitigate a issue with screen resolution changes when RISC OS is in full control of the monitor

I had already tried a PreDesk softload of a home built BCMVideo 0.50 and had a shutdown. A softload of 0.48 has so far evaded the problem.

Since I use the disable_mode_changes option and the shutdown issue occurs for me, there is no need to try out the new version.

Is disable_mode_changes part of this. I have now removed it. Can’t play Hopper any more though.

BCMVideo 0.50 has not made into the Beta Pi ROM yet, the last build is 2018-04-02. There is a source code archive for today, 2018-04-07, but BCMVideo 0.50 is not in that either.

Hello

Just wanted to mention I also have this issue on a Raspberry Pi 3B running the lastes firmware and beta rom of 5.23, 8-Apr-2018.
It is a Samsung EVO+ 32GB SD Card and I used !SystemDisk 1.04 to install RiscOS on it.

Hopefully, this issue does not happen too often.

Regards

François

At 6:43 – It just happened again…
I know why I always come back to my BeagleBoard-xM… Despite its screen resolution limitation, RiscOS is amazingly stable on it…

I am going to use the same SDCard within my Raspberry Pi 1B e few days to see if the problem also occurs on this verqion of rpi.

I have uploaded a firmware upgrade for users of the RC15 (and earlier) SD card image. This updates firmware to 27 Mar 2018 and includes an up to date ROM, but with BCMVideo reverted to 0.48 to avoid issues with the Pi model 3 B+.

This update now contains 10 April 2018 firmware, recent firmware (March 2018) had a bug which prevented serial port usage.

Instructions here

Hi

So far so good… Since yesterday, I am using my Raspberry Pi 1B with the same SD card causing the screen to switch off with the RPi 3B and I did not encounter the problem yet.
Could it be that this issue is only occuring on RPi3?
I read s.o. had this issue wih a RPi2. But is it the RPi 2B or the RPi2 B V1.2 using the same SoC as RPi3 (BCM2837).
Is this issue related to this SoC?

Regards

It’s apparently a firmware issue, but I’m not sure whether it’s specific to the 2837.

this issue is being actively investigated – notably with the Raspberry Pi firmware developers.

Hello

In the thread referred by Chris, Steve Revill wrote

If you mean the issue where on a Raspberry Pi with gamma correction, the video stops working after a few hours, then this issue is being actively investigated – notably with the Raspberry Pi firmware developers. At present, it is not considered a blocking issue because the easy work-around is to disable gamma correction.

How can I disable gamma correction?

Regards

François

The impression I got – and I may be mistaken – is that it’s done at build time and would therefore be disabled in 5.24 if the firmware isn’t ready by then. There’s nothing listed in the BCMVideo 0.49 change log about disabling gamma at run time.

I read s.o. had this issue wih a RPi2. But is it the RPi 2B or the RPi2 B V1.2 using the same SoC as RPi3 (BCM2837).

That’ll be me. It is an old RPi2, BCM2836. It was just the once on the RPi2, I haven’t seen it again on that. The fault is certainly much more apparent on both RPi3’s.

Do all the Pi’s use the same GPU?

How can I disable gamma correction?

The workaround is to use the pre-gamma BCMVideo module 0.48, either as a PreDesk softload or in a custom ROM. See Chris Hall’s post above for the latter.

Hi,

After running a few days on my Raspberry Pi 1B, I have not encountered the issue, despite daily work on it.
On the contrary, it happens every time on my Raspberry Pi 3B (with the same sd card), sometimes after more than an hour, sometimes after 10-15 minutes.

Regards