Raspberry Pi 4

So RISC OS works… with the help of Linux
https://github.com/TimothyEBaldwin/RISC_OS_Linux_Source/tree/Linux2
:)

There is a bit of a snag, the RPi4 never shows a mouse pointer

You can get the mouse pointer to show by putting ‘disable_mode_changes’ in cmdline/txt.

On the 4GB RPi4 the full amount of memory now shows up in ‘Tasks’. Currently there is 3756536K free memory with !Iris running.

You can get the mouse pointer to show by putting ‘disable_mode_changes’ in cmdline/txt.

Many thanks, I have now found the pointer.

Ah! I see – you are running RISC OS under emulation under Linux. I am waiting for a RISC OS ROM image to be made available. It’s takinh much longer than expected…

I see – you are running RISC OS under emulation under Linux

To be fair, I don’t think he is. I think he’s running RISC OS natively on a Pi4. My guess, in preparation for having a stab at similar this weekend, is he set up a Pi3* to use a Wifi HAT to automatically connect to the network, and has also installed a VNC server to run on boot.

He’s then moving the card to a Pi4 and it all runs nicely, albeit without USB or Ethernet. But because the VNC server is running over wireless, it’s possible to connect and control the Pi4.

At least that’s what I’m going to attempt when the WiFi HAT arrives! The only difference I’ll make is to use Thomas Milius’s KMSwitch which allows sharing of a keyboard and mouse from a different computer on the same network.

To be fair, I don’t think he is. I think he’s running RISC OS natively on a Pi4. My guess, in preparation for having a stab at similar this weekend, is he set up a Pi3* to use a Wifi HAT to automatically connect to the network, and has also installed a VNC server to run on boot.

Yes, that is what is going on here. I only have the one WiFi HAT so the initial setup was done on a RPi3B then both the SD card and HAT are transferred to the RPi4. (The RPi4 ROM does run on the RPi3.)

The only difference I’ll make is to use Thomas Milius’s KMSwitch which allows sharing of a keyboard and mouse from a different computer on the same network.

That is working here now, thanks for the tip BTW.

KMSwitch + Wifi Hat+ Pi 3 for control: really a lot of money, but a lot of fun too.

It gives me some ideas.
https://www.riscosopen.org/forum/forums/5/topics/15009

I hadn’t realised that the Pi3 ROM would run on the Pi4 by using a WiFi hat. Without USB and Internet it gets over the problem of there being no Pi4 rrom available. Now I understand.

I hadn’t realised that the Pi3 ROM would run on the Pi4 by using a WiFi hat.

Who said that?

The RPi3 ROM most definitely does not run on the RPi4.

it gets over the problem of there being no Pi4 rrom available.

An RPi4 ROM can be built.

An RPi4 ROM can be built.

Are you sure? ROOL haven’t succeeded yet.

An RPi4 ROM can be built.

Are you sure? ROOL haven’t succeeded yet.

I think you will find that David is correct, but hasn’t been precise enough to indicate that various features are missing.
Perhaps it would please people more to read the phrase “a RPi4 compatible development ROM with various features missing can be built”
Progress is slow, at least as far as the reports show

An RPi4 ROM can be built.

Sadly, I don’t have the wherewithal to roll my own. Is anyone prepared to upload one for a short period for testing purposes? Got the HAT and the Pi4 but not the ingenuity to build the ROM.

@andym

email me pittdj at pittdj dot co dot uk

Just building the latest, including today’s commits.

SD card setup notes are “here”.https://gitlab.riscosopen.org/RiscOS/Sources/HAL/HAL_BCM2835/merge_requests/2

Just add fixup4.dat and start4.elf plus add this to the end of config/txt

[pi4]
enable_gic=1

@andym

gmail Plusnet, just got to fail hasn’t it.

Sent again from a different account. Hasn’t bounced (yet?).

I found adding ‘disable_gamma’ to cmdline/txt fixes the overly bright screen.

disable_mode_changes disable_gamma

With all the workarounds it’s possible to get a fully funtional RPI 4 running RISC OS natively.

Elesar WI-FI Hat for networking
KMSwitch running on another RISC OS Machine to enable keyboard and mouse. Needs the above change to cmdline/txt so the mouse pointer appears.

The only thing not working is sound.

I found adding ‘disable_gamma’ to cmdline/txt fixes the overly bright screen.

disable_mode_changes disable_gamma

If I added this to my standard cmdline/txt file used on earlier Pis, would this be OK? Would it be ignored if not relevant/required? Or might it mess stuff up?

As a future-proofing, that is!

The only thing not working is sound.

And I’m sure that that will eventually be fixed by the assiduous efforts of the main contributors!

I found adding ‘disable_gamma’ to cmdline/txt fixes the overly bright screen.

disable_mode_changes disable_gamma

If I added this to my standard cmdline/txt file used on earlier Pis, would this be OK? Would it be ignored if not relevant/required? Or might it mess stuff up?

As a future-proofing, that is!

The only thing not working is sound.

And I’m sure that that will eventually be fixed by the assiduous efforts of the main contributors!

I found adding ‘disable_gamma’ to cmdline/txt fixes the overly bright screen.

disable_mode_changes disable_gamma

If I added this to my standard cmdline/txt file used on earlier Pis, would this be OK? Would it be ignored if not relevant/required? Or might it mess stuff up?

As a future-proofing strategem, that is!

The only thing not working is sound.

And I’m sure that that will eventually be fixed by the assiduous efforts of the main contributors, to whom we will continue to be grateful!

If I added this to my standard cmdline/txt file used on earlier Pis, would this be OK? Would it be ignored if not relevant/required? Or might it mess stuff up?

disable_gamma – You’ll probably want this anyway if you’re running RISC OS 5.27. It is ignored at RISC OS 5.26.

disable_mode_changes – If you’re not using AnyMode, this will lock you to the screen resolution selected at startup. This may not be what you want.

disable_gamma – You’ll probably want this anyway if you’re running RISC OS 5.27. It is ignored at RISC OS 5.26.

I don’t already have this. What difference will it make on earlier versions?

disable_mode_changes – If you’re not using AnyMode, this will lock you to the screen resolution selected at startup. This may not be what you want.

I am, so not a problem?

PS – I do realise that the CMDLINE/TXT commands should all be on a single line with no Returns! Just to help others.

I don’t already have this. What difference will it make on earlier versions?

It was introduced in RISC OS 5.25 as a workaround for this screen-blanking bug. RISC OS 5.24 (and all earlier releases) did not have gamma correction enabled, and RISC OS 5.26 (being in essence a rebuild of 5.24) also had gamma disabled.

I am, so not a problem?

If you’re using AnyMode, you will probably have disable_mode_changes there already.

To give an idea of how mauch faster the RPi4 is. Here’s a screenshot showing !Iris, !RPCEmu, !MPlayer and !GPXSee running at the same time. !MPlayer is playing a 1080p24 movie. !RPCEmu is idling around 16mips. The screen resolution is 3840×2160 @60Hz. Still plenty of free memory.

To enable 4k at 60Hz hdmi_enable_4kp60=1 needs adding to config.txt

Fantastic

Fantastic

Thanks to David, I’ve got it up and running, but I’m still not seeing the cursor. I’ve put disable_mode_changes in cmdline/txt (along with disable_gamma) and it has disabled modes, but there’s still no cursor. Is there something else I need to do?