Delete me: Upgrading your Raspberry Pi to RISC OS 5.27 (Rev #4, changes)

Showing changes from revision #3 to #4: Added | Removed | Changed

Introduction

This page details the process for upgrading an already-working RISC OS installation on a Raspberry Pi to RISC OS 5.27.

Please note: RISC OS 5.27 is a development release that contains untested, work-in-progress software. Some components may be unfinished and/or contain serious bugs: that is what development is about! You should only use RISC OS 5.27 if you are willing to accept the risks involved and have a suitable backup strategy in place.

Having said that, many builds of RISC OS 5.27 do work well. It may simply be a matter of trying a few different daily builds until you find one that meets your needs.

Prerequisites

At You a minimum, you will need to download the following software:

• The Beta ROM image from the Raspberry Pi downloads page.
• The Beta HardDisc4 image from the Miscellaneous downloads page.
• Updated Raspberry Pi firmware suitable for RISC OS 5.27.

A certain level of RISC OS knowledge is assumed, including how to use the command line, how to use the !Configure application and how to edit text files.

What release are you upgrading from?

The exact procedure to follow depends on the release of RISC OS you are currently running. Choose the appropriate entry from this list:

• RISC OS 5.24, 5.25 or 5.26
• RISC OS 5.23 (RC15)
• RISC OS 5.21 (RC11, RC12, RC12a, RC14)
• RISC OS 5.19 (RC10 or earlier)

Disc upgrades and monitor settings

Starting with releases prior to RISC OS 5.24

These releases – with the possible exception of RC15¹ – are too old to retain the existing !Boot as it stands, so you will have to build a new !Boot directory based on the 5.27 version of !Boot. The process is as follows:

• Go to the RISC OS Upgrade page and follow the section titled Procedure for upgrading from RISC OS 5.19 or earlier² to rebuild !Boot and upgrade the disc-based applications – use the Beta HardDisc4 image, not the “stable” image mentioned on the page. DON’T upgrade the OS ROM just yet.

Once you have confirmed that !Boot – and the other applications in the Beta HardDisc4 image – still work properly, go to Monitor configuration checks below.

¹ With RC15 it is theoretically possible to download the 5.24 stable disc image and run the “InSituBootUpdate” file inside that archive – you might then be able to go to the RISC OS 5.24 section on this page to complete the upgrade. This is completely untested with RC15 and you would do so at your own risk.

² Avoiding a rebuild of !Boot with older releases is, at best, difficult. For builds based on 5.21 (i.e. Pi releases RC11 to RC14) you would need to run the InSituBootUpdate supplied with the 5.22 HardDisc4 image followed by the InSituBootUpdate supplied with the 5.24 HardDisc4 image (and finding a copy of the 5.22 HardDisc4 image can be rather tricky). If you are upgrading from RISC OS 5.19 (Pi releases up to RC10) you cannot use the InSituBootUpdate process at all.

Starting with RISC OS 5.24 or later

• Use the “Boot merge” facility (!Configure > Boot > Install) to install the new version of !Boot from the Beta HardDisc4 image. Reboot and fix anything that’s broken.³

• Replace all the ordinary applications (i.e. the contents of every directory except !Boot) from the Beta HardDisc4 image. Simply delete the old application of the same name (e.g. !Maestro) and copy the new application across.

³ “Boot Merge” saves all replaced files in the !Boot.Backup directory – this will allow you to retrieve any changes you may have made to !Boot components (e.g. amendments to a built-in monitor definition file) if they have been overwritten.

Monitor configuration checks

MonitorType and WimpMode

At RISC OS 5.27, two CMOS RAM configuration settings – “MonitorType” and “WimpMode” – must hold valid information. Releases up to RISC OS 5.26 are rather forgiving of unusual values in these two fields, but from RISC OS 5.27 they must be correct or the monitor may not display a picture.

To check the settings:

• Open a Task window (ctrl-F12) and enter the following two commands:
  *Status MonitorType
*Status WimpMode
  

• If the MonitorType is set to a number between 0 and 8, you must change it:
  *Configure MonitorType Auto
  If the monitor type is “Auto” or “EDID” you do not need to change it.

• If the WimpMode is set to a number, you must change it:
  *Configure WimpMode Auto

“disable_mode_changes” (Optional setting)

In early releases of RISC OS 5 for the Raspberry Pi, the monitor pixel resolution chosen at boot-up was controlled by two settings supplied to the Raspberry Pi bootloader (the “hdmi_group” and “hdmi_mode” lines in config.txt).

From RISC OS 5.24 onwards, RISC OS will by default select a monitor pixel resolution according to the settings chosen in the “Screen” section of the !Configure application, thus ignoring the “hdmi_group” and “hdmi_mode” settings.

If you want RISC OS to continue using the “hdmi_group” and “hdmi_mode” settings⁴ you should add disable_mode_changes to CMDLINE/TXT inside !Boot.Loader. If the file doesn’t exist, create it.

⁴ For example, you may be using a display that only supports a specific pixel resolution, or perhaps you want to use the “AnyMode” utility.

Restart to check new monitor settings

• If you have changed any of the monitor settings, shut down and restart the machine.

• After the restart, you may find that the RISC OS desktop is displayed at a lower resolution than usual. To correct this, use the !Configure application to select a screen resolution more to your liking. For example, to use the monitor’s EDID settings, choose a monitor type of “Auto(your-monitor-name-here)” (e.g. “Auto(L225W)”) and a resolution of “Native”.⁵

⁵ If the menu option says “Auto(Unidentified)” it means that EDID has not worked. In this instance you should choose another monitor type from the list. list, or consider usingdisable_mode_changes until you install the 5.27 ROM.

Upgrading the RISC OS ROM

We recommend you continue using your updated !Boot for a week or two, so as to flush out any lurking problems before you upgrade the ROM. This gives you time to grab a selection of Beta ROM images of different dates⁶ – just in case a serious bug was accidentally introduced in a daily build. You should also check the Bugs and Community Support forums to see if there are any problems with recent daily builds.

⁶ The build date is mentioned immediately below the download link itself. Although listed as daily builds, the average build frequency is closer to “once every 3-4 days”.

Preparing for the upgrade

• Edit the file called CMDLINE/TXT inside !Boot.Loader (if it doesn’t already exist, create it) so that the text disable_gamma appears on the first line of the file.
  For example, if the file already contains “disable_mode_changes”, you would edit the first line to read:
  disable_mode_changes disable_gamma

• Check that !Boot.Loader contains a file called “CMOS”. If it doesn’t exist, use the *SaveCMOS command to create it:
  *SaveCMOS !Boot.Loader.CMOS

• Check that “CONFIG/TXT” (inside !Boot.Loader) contains – at minimum – the following lines:
  fake_vsync_isr=1
framebuffer_swap=0
gpu_mem=64
init_emmc_clock=100000000
ramfsfile=CMOS
ramfsaddr=0x508000
kernel=RISCOS.IMG
  If any lines are missing missing, – particularly “ramfsfile” and “ramfsaddr” – you should add them.Do not remove any entries at this stage.

• Copy the existing versions of RISCOS/IMG, BOOTCODE/BIN, START/ELF and FIXUP/DAT from !Boot.Loader to another location, in case you need to regress to the old ROM version.

Installing the 5.27 ROM

• Install the updated firmware (BOOTCODE/BIN, START/ELF, FIXUP/DAT) into !Boot.Loader.

• Install the Beta ROM (RISCOS/IMG) into !Boot.Loader.

• Reboot.

After rebooting on RISC OS 5.27

• Go to !Boot.Choices.Boot.Predesk and delete the !!ZeroPain directory (if present). If you want to continue using ZeroPain, install the latest version from the Beta ROM archive. Note that RISC OS 5.27 will run happily without ZeroPain.

• Make a backup copy of your CMOS settings (either via “CMOS > Save” under !Configure, or by using *SaveCMOS) as some of the settings may have changed during the upgrade.⁷

• If you have upgraded from RC14 or earlier, you may want to edit use CONFIG EDID/⁸ but previously added “disable_mode_changes” to CMDLINE/TXT , now is the time to remove any it. no-longer-needed Your entries (e.g. “hdmi_group” and “hdmi_mode” are only needed if you’re running AnyMode).CMDLINE/TXT should now read:
  disable_gamma

⁷ If you have upgraded from RC10 or earlier, none of your old “saved CMOS” files will work at RISC OS 5.27, so you will need a fresh backup anyway.

Common problems with the upgrade

• The mouse pointer is visible but the rest of the screen is black (either on boot or when selecting a 256-colour screen mode)
  You upgraded the ROM but didn’t upgrade the firmware (bootcode.bin, start.elf, fixup.dat).

• Monitor doesn’t display a picture on boot
  EITHER: You didn’t set MonitorType and WimpMode to “Auto”,
  OR: you didn’t put “disable_gamma” on the first line of cmdline.txt.

• Desktop is displayed at a lower resolution than usual
  Use “Configure > Screen” to change the monitor settings. To use EDID, choose a monitor type of “Auto(your-monitor-name-here)” (e.g. “Auto(L225W)”) and a resolution of “Native”.

• Configuration changes don’t survive a reboot
  (1) CONFIG/TXT (inside !Boot.Loader) may be missing the lines that load the CMOS file on boot. Check that the following lines are present:
  ramfsfile=CMOS
ramfsaddr=0x508000
  (2) The CMOS file (inside !Boot.Loader) is missing/corrupted/read-only, or you have another file calledCMOS also exists in the root directory of the Filecore partition. partition Delete (i.e. any you wayward have file(s), a then file issue: called $.CMOS in addition to $.!Boot.Loader.CMOS). Delete any wayward file(s), then issue:
  *SaveCMOS !Boot.Loader.CMOS

• Unexpected behaviour in applications after installing the 5.27 ROM
  This can happen if you installed the
  • This can happen if you installed the ROM without upgrading !Boot (or perhaps the attempted upgrade of !Boot didn’t go as well as you had hoped).
  • Alternatively, there may be a bug in the specific ROM build you chose, in which case you should replace the ROM with another 5.27 daily build to see if that is any better.
  • A third possibility is that one or more modules are unplugged (enter *Unplug to check status). If any modules are unplugged, use *RMReinit to reinstate them (e.g. you would use *RMReinit GPIO to reinstate the GPIO module).
  ROM without upgrading !Boot (or perhaps the attempted upgrade of !Boot didn’t go as well as you had hoped). Alternatively, there may be a serious bug in the specific ROM build you chose, in which case you should replace the ROM with another 5.27 daily build to see if that is any better.