This page contains a number of general issues that may crop up when running RISC OS on the Raspberry Pi.
Please note: This page makes frequent reference to the BREAK key. On some keyboards, the BREAK key is marked PAUSE. If your keyboard has neither key, see Beginners FAQ:Hardware Support for how to configure another key as BREAK.
Yes you can. If you’re installing from scratch, see Installing RISC OS on the Raspberry Pi 4?.
If you’re already running RISC OS 5.28 on an older model of Raspberry Pi, make the following checks:
With those changes applied, the SD card should work in a Pi 4, although you may run into DHCP problems – see below.
Short answer: No.
This is for architectural reasons. The big show-stopper is that the Cortex-M CPU (used in the Pi Pico) only supports the Thumb instruction set, whereas RISC OS uses the A32 instruction set. Getting RISC OS to run on the Pi Pico would thus entail a complete rewrite of the RISC OS kernel. Sorry.
For the record, “RISC OS Pico” – now discontinued – was a completely separate product.
This can happen if you are using the latest hardware revisions of the Pi 4B or Pi 400, which RISC OS does not yet support.
It can also happen if you had previously used the SD card to boot another Raspberry Pi. The Pi 4 has a different Ethernet adapter to earlier Pi models, so RISC OS will be looking for the wrong Ethernet adapter. The clue in this case is that the message will read “Contacting DHCP server using Ethernet over USB interface” when on the Pi 4 it should list a different type of Ethernet interface (e.g. “Broadcom GENET”).
Fix: Press ESC to reach the desktop (click Cancel on the dialogue box that appears). Now go to Configure > Networking > Internet > Interfaces, select a suitable interface (e.g. “Broadcom GENET”) and click on “Configure”. In the “Obtain IP address” section, choose “via DHCP” and click on “Set”. You will be prompted to reboot: this reboot should proceed to the desktop without any error.
If the “Interfaces” page does not contain any physical interfaces at all (i.e. only “Serial PPP” is listed) you will have to disable networking instead (untick “Enable TCP/IP Protocol Suite” on the Internet configuration window). This is not ideal but at least it gives you a starting point.
By default, the Pi 4 will only display a 3840×2160 picture at 30Hz, but most 4K monitors expect 3840×2160 at 60Hz. In these circumstances, RISC OS will fall back to a “safe” (i.e. low-resolution) screen display.
You have two options:
hdmi_enable_4kp60=1
to config.txt – see config.txt (Raspberry Pi) for more information. This will allow 3840×2160 at 60Hz, but will increase the operating temperature of the Pi 4, so additional cooling may be required.
When using RISC OS, HDMI sound is only available on the left-hand HDMI port. If you connect to the other HDMI port you will get a picture but no sound.
On the Pi 400, use the HDMI port closest to the SD card slot.
Since RISC OS 5.28 was originally released, new hardware revisions of the Pi 4B and Pi 400 have appeared. Because older releases of RISC OS 5.28 don’t recognise the hardware, the GPIO pins (and hence most HATs) will be inaccessible.
To check whether your hardware is affected, issue the command *ROMModules
and look for the GPIO entry. If all is well, this will have a status of “Active”. If the GPIO module is shown as “Dormant”, you will need to install the latest (February 2022) version of RISC OS 5.28 or RISC OS Pi, available from the Downloads page.
The Pi Zero 2 W was launched in October 2021, long after the original release of RISC OS 5.28. While older releases of RISC OS 5.28 will run on the Pi Zero 2 W, the GPIO pins will be inaccessible.
The fix is to install the latest (February 2022) version of RISC OS 5.28 or RISC OS Pi, available from the Downloads page. If you are still experiencing problems, upgrade the firmware (use firmware dated February 2022 or later).
As for card capacity, the full RISC OS Pi distribution takes up less than half the space on a 2GB card, so a 16GB card would provide plenty of room for additional files. Remember that you’ll need SystemDisc to use all of a 16GB card.
Yes, but you’ll have to reformat them first. SDXC cards are supplied in exFAT format, which RISC OS cannot handle at present. Reports suggest that 64GB and 128GB cards1 will work with the Raspberry Pi after reformatting to FAT32.
When reformatting the card, you must use Master Boot Record (MBR) partitioning. If you select “GUID partition table”, RISC OS will be unable to read the card.
In any case, SD is a poor choice for Filecore storage. The quoted SD speeds are for “sequential burst” writes, not the random read/write operations that Filecore typically performs. Cards with an A1 (app performance) rating will be slightly better in this respect, but may cost more than an ordinary card. In addition, the SD card doesn’t “understand” Filecore format, so the wear-levelling algorithms won’t work, leading to a much reduced operating life.
You might wish to consider an external (USB connected) HDD instead. For a slight increase in power consumption you should see a vast improvement in media longevity. For example, a 500GB USB-connected HDD costs about as much as a 128GB SDXC card and will last longer (provided you’re not exposing it to significant mechanical shocks).
1 Older models of Raspberry Pi cannot use SDXC cards larger than 256GB: this is a hardware restriction. In any case, RISC OS FileCore maxes-out at 256GB, so you cannot use the extra space on a 512GB card in the SD slot.
Yes you can. Detailed instructions are on this page.
You can do it on the Pi 3 and Pi 4, but it’s not recommended. Here are some of the issues you would encounter:
configure filesystem scsi
configure scsifsdrive 0
savecmos scsi::0.$.!Boot.Loader.CMOS
configure filesystem scsi
configure scsifsdrive 4
savecmos scsi::4.$.!Boot.Loader.CMOS
This list is not exhaustive. You may experience other problems besides those mentioned above.
Users wishing to reduce SD card wear-and-tear would be better advised to continue booting from the SD card, but to move the !Boot directory to a USB drive, as described here.
2 If you have a Pi 400, press and hold Fn-F10 for 10 seconds to power-off. Wait a few seconds, then press Fn-F10 to power on. This should boot into RISC OS.
There are several possible reasons for this. Here are the “top four”:
*SaveCMOS sdfs:$.!Boot.Loader.CMOS
DOSFS understands long file names, but if you rename a file such that its name isn’t long any more, only the “long file name” entry is changed: the 8.3 name still points at the “long file name” entry.
The Pi bootstrap loader will only check the 8.3 filename (not the “long file name”) when looking for a file whose name fits in the 8.3 format.
The practical upshot is that if you rename RISCOS/IMG to old-RISCOS/IMG and then rename it back to RISCOS/IMG, the Pi bootstrap loader will no longer be able to find it.
Workaround: If you want to change the name of a file inside !Boot.Loader, use Copy instead of Rename.
The Pi does not have a real-time clock. Hence, when the Pi boots up, it will not be aware of the correct time.
The fix is to run an Ethernet cable from the Pi to your broadband router (or equivalent network port with access to the Internet). The Pi will then be able to update its clock from the network.
Note: “Real-time clock” add-ons are available for the Raspberry Pi, but some may require custom software to work with RISC OS.
When using PackMan, you might get scary “file clash” messages when you try to update an application. This is most likely to happen if the application was updated outside of PackMan (e.g. by downloading a new version from a website).
The fix is to click on the Backup button. This will move the “unexpected” files into a Backup directory: the update should then progress normally. After the update is complete, you can see a list of backed-up files in the Advanced section of PackMan’s icon bar menu, and delete or restore them as you wish.
For further information, see the PackMan User's Guide.
RISC OS does not currently support WiFi on any platform. Adding WiFi support to RISC OS is a major undertaking, but it is on the roadmap so will eventually appear.
If your Raspberry Pi hasn’t got an Ethernet port, you can use a USB-to-Ethernet adapter, but you need to ensure that the chipset is supported.
Your best bet is one with an Asix AX88172 or Asix AX88772 chipset.
Other chipsets known to work include:
Don’t get an adapter with a Realtek chipset – at present they are not supported under RISC OS.
Remember that RISC OS can use the built-in Ethernet port on the “Model B” and “Model B+” variants of the Pi 1, Pi 2, Pi 3 and Pi 4, so you won’t always need a USB adapter.
USB drives – especially flash memory sticks – don’t write all the data to the drive immediately: some of it is delayed (in the expectation that the user will be writing more data). This is done for efficiency – and media longevity – reasons: the fewer separate write operations performed, the better. The data will eventually be written after a timeout, which could be several seconds.
This is exacerbated by the fact that many USB devices don’t action dismount requests3. Instead of immediately flushing all delayed writes to the media in the expectation that a power-off is about to happen, the delayed writes remain pending until the timeout (mentioned above) occurs in the normal course of events. If the device is unplugged immediately after issuing the dismount but before the delayed writes have been actioned, data will be lost.
So the “wait 15 seconds” rule will hopefully allow for all but the most tardy of these delayed writes to actually happen, thus minimising the risk of data corruption.
3 RISC OS is obviously doing the dismount “wrongly”, but no one has yet worked out exactly what is “wrong”.
First things first: are you doing Shift-Break properly? You should hold down Shift, press and release Break, then continue to hold down Shift until the reboot finishes.
There are several reasons why Shift-Break (and Shift power-on) may not work on the Raspberry Pi:
Another problem relates to the keyboard itself. On some keyboards, holding down a key when power is applied will cause the keyboard to misinterpret it as a “stuck key” so will not signal that it is being pressed.
Workarounds:
*Configure NoBoot
*Configure Boot
4 If you don’t know what NOOBS is, you probably aren’t using it. For the record, the Raspberry Pi Foundation removed it from their download page in 2020.
RISC OS Pico was a cut-down version of RISC OS (no GUI) that was put together for a one-off special event (the 50th anniversary of the BASIC programming language in 2014). Updates ceased in 2017: it will not run on anything newer than a Pi 3B. In addition, there is the possibility of confusion with the Raspberry Pi Pico, which RISC OS does not support.
Hence RISC OS Pico is no longer available from the Downloads page.
To get the “RISC OS Pico” experience from a RISC OS 5.28 build:
disable_mode_changes disable_gamma
*Unplug BootFX
*Configure Language 19
*Configure Mode 7
*Configure NoBoot
RC stands for release candidate, a software build typically produced for acceptance testing in the run-up to general release. While based on the corresponding development build, it may omit some untested or problematic components in an effort to improve stability.
The RISC OS release cycle does not generate RC builds as a matter of course, but several RC builds of RISC OS for the Raspberry Pi have been produced: the most recent being RC16 (June 2020)5.
5 The previous RC build was RC15 (April 2017). This should give you some idea of how often they appear.