5.30 Stable

Congratulations to all those involved.

I copied !Boot on my Pi 4 and completed the insitu boot update. I rebooted, and it was all good. I then copied the new ROM files; again, no issues.

Thank you for the update.

Not near a machine at the moment. Will the Insitu script work with the last version of 5.29 or only 5.28?

Will the Insitu script work with the last version of 5.29 or only 5.28?

Just needs to be >= 5.28. The script only adds/modifies/removes those changes you’d need assuming you have at least 5.28 to start with.

If, for example, you had 5.27 you’re out of luck because each script only has the tables of changes from the last even number (in that instance you’d need to do the in situ update to 5.28 first, reboot, then apply the in situ update to 5.30 second).

On my Iyonix, the InSitu script errored out with a “Missing ENDIF” in the BASIC bit.

I don’t seem to have a “Desktop” file to be altered, so the IF statement didn’t have a matching ENDIF.
Having added the errant ENDIF, at the end, the renaming all went wrong because none of the code above had run.

Thanks Robert.

Congratulations to all those involved.

Heartily seconded. That has to qualify as the easiest OS upgrade in my RISC OS experience over +/- 30 years. Starting with a latish (Feb ’24) 5.29 ROM and RC4 Boot sequence, I ran InSituBoot, copied the Loader files across including ROM, installed WiFi, all of which took about 2 minutes, and rebooted. All working perfectly so far. Download speeds here using WiFi are around 50% of wired speed (still very acceptable), upload speeds are around 80% of wired. 5.30 was well worth the wait IMHO.

Just needs 5.30 stable adding to the RPC (IOMD) downloads page and I think things are complete.
Bound to be a few niggles somewhere, there always are.

I dared to install 5.30 on my CM4 manually.
!Boot etc. updated on SD from HardDisc4.
Downloaded 5.30. Installed.
No Ethernet anymore:
No Module EtherGENET or something like this.
I shall try to go back to 5.29 tomorrow.

I’m am having a problem with the Titanium. I ran the install boot and reflashed the rom with 5.31. It powers up in a low res mode showing the network configuration window and an hour glass. Clicking cancel makes it boot to the desktop with the rror message Machine startup not completed successfully ‘route:unknown error:invalid argument’ Clicking cancel clears the message and the machine seems to work normally with network access OK.

I did notice that on the boot screen, before it does the DHCP bit there is only setup network and DAlimit. I can’t remember what it used to say but there were more lines.

Anny ideas? Geoff.

I meanwhile solved my problem on my CM4. It was simply enough to save the CMOS file again. After doing so and rebooting EtherGENET appeared inside module list and Ethernet was useable again. The old CMOS file was a 5.29 one.

It powers up in a low res mode showing the network configuration window and an hour glass. Clicking cancel makes it boot to the desktop with the rror message Machine startup not completed successfully ?route:unknown error:invalid argument?

I suspect you had the ROD stack installed when you ran InSituUpdate?
If so, I suggest you uninstall the ROD stack, and see if that then works ok.
If ok, then re-install the ROD stack.

Thank’s Martin, that’s fixed it. It was the ipv6 load that was missing on the boot screen. Again, many thanks.

https://www.theregister.com/2024/05/02/rool_530_is_here/

I’ve scanned this web site until my eyes bled (not literally but you get the picture) and I can’t find a step-by-step guide to carrying out the in-situ upgrade. This might be because there isn’t one (doubtful) but I’d be most grateful if someone could put me out of my misery.

Thanks.

Try RISC OS Upgrade

Also remember to uninstall any ROD addons like Pinboard2 and their Network stack first.

@Stuart. Many thanks, I’d never have thought to find it via Library → Documentation without help.

@Doug. No need to remember as I’m trying it out on a minimally set up Pi2 with no ROD add-ons. Thanks anyway.

I’ll have to postpone the upgrade for a couple of days; domestic duties call!

RPCEmu: has anyone tried running InSituBootUpdate as part of the process of upgrading to 5.30 on it? Did (would) it work?

PCEmu: has anyone tried running InSituBootUpdate as part of the process of upgrading to 5.30 on it? Did (would) it work?

Yes and yes.
Recent version of 5.29 —> 5.30
I thought I’d twiddle with a few things on the stable version before updating to 5.31 betas

I haven’t upgraded the ROM to V5.30 yet, but have run the InSituBootUpdate, and run into problems with AcornSSL when using Hermes. Hermes crashes. The log files show that this happens almost immediately after attempting a transfer as there are a few repeating lines of “Connecting to mail.mail.coop” and nothing else. The new AcornSSL module installed by InSituBootUpdate is again version 1.06, but with a more recent date and a more recent version of mbedTLS.

What to do? Replace the new version with the old version?

The Hermes error message says that Hermes has suffered a fatal error and cannot continue. Clicking OK produces a window titled “Unverified certificate chain” which is issued by R3 and to mail.mail.coop, plus some other stuff about certificates and RSA with SHA-256. You can even view the certificate, if you really, really want to.

You might just need to update the certificates.

Try this: https://davehigton.me.uk/Progs/UpdCaCert.htm

The new AcornSSL module installed by InSituBootUpdate is again version 1.06, but with a more recent date and a more recent version of mbedTLS.

That versioning on the mbedTLS SSL updates is beyond tiresome.
I would label it as idiotic, but that does a disservice to idiots.

Try this: https://davehigton.me.uk/Progs/UpdCaCert.htm

I believe that updating Internet via PackMan (which lives in the http://packages.riscosopen.org/packages/pkg/rool package source) will accomplish the same thing¹, if preferred.

¹ Well, almost. The package gets the file from ROOL, whereas Dave’s utility gets the one supplied with Curl. One may be subtly different from the other.

I downloaded the latest ROOL version of CertData only to find that it is the same version as installed on the Raspberry Pi 4 on which I encounter the problem. On my ARMX6 which has an older version of CertData, there isn’t the problem. The Boot log shows that InSituBootUpdate has installed the more recent version of CertData dated 16/03/24 and is the “Certificate data from Mozilla as of: Mon Mar 11 15:25:27 2024 GMT”.

Just a thought. What is the time and date showing? If your computer thinks it is 1970 for example.