RISC OS bugs specific to the Raspberry Pi (Rev #7, changes)
Showing changes from revision #6 to #7:
Added | Removed | Changed
category: RaspberryPi
This page lists the bugs in RISC OS that affect the Raspberry Pi only.
This is NOT a list of all bugs in RISC OS. For bugs applicable to all platforms, see the Bug tracker page and the Bugs forum.
Bugs in the current stable release (RISC OS 5.24 5.28) onwards
Some of these bugs are long-standing and will affect earlier releases of RISC OS 5.24 as was well the as first 5.28 stable itself. release for the Raspberry Pi. Bugs in earlier (development) releases are not listed here.
| Symptoms: | |
| |
|
| |
|
| |
When taking a copy of the |
| Workaround: | Use an external USB hub for all USB1.1 devices (but see “Keyboard not recognised during boot” below). |
| Symptoms: | |
| |
|
| |
The full-size |
| Versions affected: | All |
| Fixed in: | (No fix available) |
| Workaround: | If you want to use Shift-Break, temporarily unplug the USB hub and connect the keyboard to a built-in USB port on the Pi. The USB hub can be reconnected once the reboot is complete. N.B. Some keyboards (including the “Raspberry Pi Official Keyboard”) have their own USB hub. You will have to use a different type of keyboard if you want to use Shift-Break on the Pi 1, Pi 2 or Pi 3. |
| Pi 3A+ GPIO layout | |
|---|---|
| Symptoms: | The GPIO layout of the Pi 3A+ is not properly enumerated (read off end of table). This can make controlling the Pi 3A+ GPIO pins anywhere from difficult to impossible. |
| Version affected: | 5.26 |
| Fixed in: | 5.27 builds dated 2018-12-02 and later. |
1 You will only see this message on the Pi 4 if you have a hub attached to the USB-C (power input) port and have connected the keyboard to that hub. Workaround is to connect the keyboard to one of the four full-size USB ports on the Pi 4.
| Symptoms: | |
| |
|
| Versions affected: | All |
| Fixed in: | (No fix available) |
| Workaround: | Pi 4: Press ESC to reach the desktop, then go to “Configure > Network > Internet > Interfaces” and choose the “Broadcom GENET” interface. Now click on “Configure”, choose “via DHCP” and click on “Set”. You will be prompted to reboot. |
| Keyboard not recognised during boot | |
|---|---|
| Symptoms: | On the Pi 1, Pi 2 and Pi 3, the message “No keyboard present – autobooting” appears on the screen during boot. Also, trying to use Shift-Break to reboot to the command line won’t work: RISC OS will always boot to the desktop. |
| Cause: | This will happen if you boot-up the Pi with an external USB hub attached. It is the mere presence of the hub that causes the problem: it will still happen if you move the keyboard to a built-in port but leave the hub attached. |
| Note: | The Raspberry Pi 4 does not suffer from this bug. |
| Versions affected: | 5.24, 5.25, 5.26, 5.27 |
| Fixed in: | (No fix available) |
| Workaround: | If you want to use Shift-Break, temporarily unplug the USB hub and connect the keyboard to a built-in USB port on the Pi. The USB hub can be reconnected once the reboot is complete. N.B. Some keyboards (including the “Raspberry Pi Official Keyboard”) have their own USB hub. The stated workaround will – obviously – not work with this type of keyboard. |
2 This is most likely to happen if you adjusted the configuration of the Ethernet interface on the older Pi (e.g. to specify a static IP address).
| Symptoms: | On the Pi |
| |
|
| Versions affected: | All |
| Fixed in: | (No fix available) |
| Workaround: | None. |
| Selecting a 256-colour mode results in a blank screen | |
|---|---|
| Symptoms: | On selecting a 256-colour screen mode, the screen goes blank but the mouse pointer is still visible. If you press F12, blind-type *wimpmode X800 Y600 C16M and press Enter twice, the screen display reappears. |
| Note: | This can also happen at boot-up (e.g. a monitor type of “Auto” will default to 640×480 pixels, 256 colours). |
| Version affected: | 5.27 |
| Fix: | Upgrade the Pi firmware (bootcode.bin, fixup.dat, start.elf). Firmware versions from January 2019 onwards will fix the problem. |
| Screen goes blank at a random time | |
|---|---|
| Symptoms: | After a period of normal operation (ranging from a few seconds to several hours) the screen will abruptly go blank. The only way of restoring a display is to power off and power on again. |
| Note: | This can be distinguished from the previous case because (a) it can happen at any time, not just at a mode change, and (b) the mouse pointer disappears as well. See this forum thread for more details. |
| Versions affected: | 5.25, 5.27 |
| Fixed in: | (No fix available) |
| Workaround: | Add disable_gamma to the first line of cmdline.txt |
For bugs applicable to all platforms (including the Raspberry Pi) see the Bug tracker page and the Bugs forum.
A Bugs note affecting on previous stable releases (RISC OS 5.27 5.24 and 5.26) only
RISC OS 5.27 5.24 is was the current first development stable release. release It for is the nature Raspberry of Pi. software Bugs development in that earlier individual releases builds may introduce bugs that are swiftly not fixed listed (or here. sometimes not-so-swiftly fixed). Developers who wish to know what changes were made on what dates are advised to consult theGitLab repository rather than relying on this wiki.
| Built-in USB ports | |
|---|---|
| Symptoms: | USB1.1 devices (e.g. keyboards, mice) can misbehave if you mix USB1.1 and USB2 devices on the built-in USB ports. |
| Note: | Does not affect models with only one USB port (e.g. Pi 3A+). |
| Versions affected: | 5.24, 5.26 |
| Fixed in: | 5.28 |
| Workaround: | Use an external USB hub for all USB1.1 devices |
| Lightning symbol | |
|---|---|
| Symptoms: | The Pi 3B+ may flash the “lightning” (low voltage warning) symbol during heavy SD card access. |
| Version affected: | 5.26 |
| Fixed in: | 5.28 |
| Pi 3A+ – cannot control GPIO pins | |
|---|---|
| Symptoms: | The GPIO layout of the Pi 3A+ is not properly enumerated (read off end of table). As a result it may not be possible to control some of the GPIO pins on the Pi 3A+. |
| Version affected: | 5.26 |
| Fixed in: | 5.28 |
Bugs affecting development builds only
| Screen goes blank at a random time | |
|---|---|
| Symptoms: | After a period of normal operation (ranging from a few seconds to several hours) the screen will abruptly go blank. The only way of restoring a display is to power off and power on again. See this forum thread for more details. |
| Note: | Stable builds are not affected, as gamma is disabled by default. |
| Versions affected: | 5.25, 5.27, 5.29 |
| Fixed in: | (No fix available) |
| Workaround: | Add disable_gamma to the first line of cmdline.txt |
For bugs applicable to all platforms (including the Raspberry Pi) see the Bug tracker page and the Bugs forum.
A note on RISC OS 5.29
RISC OS 5.29 is the current development release. It is the nature of software development that individual builds may introduce bugs that are swiftly fixed (or sometimes not-so-swiftly fixed). Developers who wish to know what changes were made on what dates are advised to consult the GitLab repository rather than relying on this wiki.
Social
Follow us on
and
and
ROOL Store
Buy RISC OS Open merchandise here, including SD cards for Raspberry Pi and more.