Raspberry Pi 3

I too, seem to have RPi3 running Netsurf now.
Thanks.

Hmm – I’ve had no joy with Netsurf-gcc—3436. Modules installed, system upgraded and Boot upgraded, but double clicking on the Netsurf icon I get nothing. No crash – I can continue to use the machine – but no Netsurf :-(.

Please try NetSurf CI build #3460 or later

I’ve had no joy with Netsurf-gcc—3436

Hmm – I read that as 3463 when I fetched it…I will double check later – hopefully I have made exactly the error above!

Sorted. (face palm)

Time to roll your own by changeing two Lines in BuildSys.Components.ROOL.BCM2835
Change (1)
#Kernel -at 0xFC010000
Kernel -at 0xFC010000 -options ASFLAGS=“-PD \”HiProcVecs SETL {FALSE}\""

Change (2)
#FPEmulator -options FPE_APCS=3/32bit FPEANCHOR=High
FPEmulator -options FPE_APCS=3/32bit
This will build a Non ZPP version of the rom

Hmmm! my kernel line is slightly different:

Kernel                -at 0xFC010000 -options ASFLAGS="-PD \"HiProcVecs SETL {FALSE}\" -PD \"CMOS_Override SETS \\\"= FileLangCMOS,fsnumber_SDFS,CDROMFSCMOS,&C0\\\"\""

I would be grateful if someone could write down a step-by-step procedure for getting a Pi 3 to work under RiscOS. I have tried to follow the various instructions on this website but have failed – obviously there is something I am not doing properly. (RC14 loading is OK- it is what to do next). Thanks.

On another matter, there is now a working Forth to download, with examples, from: www.rforth.uk
It includes SPI and IIC usage, including ‘bit-banging’ of the latter. Happy Forthing to those that like that sort of thing.

Why has the RC14 image not been updated to resolve all these Pi3 headaches?

I sort-of asked this a while ago. I was wondering what needs to be done? Who needs help? I am reluctant to hang the table and demand something from volunteers, but it would be nice to know if/how we can help.

Best practical effort I have seen so far is Chris Hall’s update pack.

As an alternative to using RC14 I wrote a procedure elsewhere on this forum for a minimal installation of ROOL’s nightly beta ROM and HardDisc4 image. For the RPi3 RC14 is obsolete, this suggestion does install up to date RPi3 compatible components. Note that it is a minimal installation, RC14 has a lot of third party software that is not present here, but what the user requires can be obtained later.

https://www.riscosopen.org/forum/forums/4/topics/6400?page=4#posts-57312

An SD card and a USB memory stick or drive are need to start with.

I am reluctant to hang the table and demand something from volunteers, but it would be nice to know if/how we can help.

is probably a better way of approaching than

Why has the RC14 image not been updated to resolve all these Pi3 headaches?

such an ungrateful way of phrasing to the unpaid rool-ers

such an ungrateful way of phrasing to the unpaid rool-ers

Indeed. How’s about those with a Pi3 who want an updated image report on what fails and if/where updates may be found?

Indeed. How’s about those with a Pi3 who want an updated image report on what fails and if/where updates may be found?

“The update” just needs someone to decide on a RISC OS image to use and add the RPi boot loader stuff. Nobody needs to report anything. It just needs to be done. The whole 3rd party stuff can be added later.

ISTR that the plan was to make an official RISC OS release (5.24) for the RPi (back then: RPI 1 & 2; now obviously also Zero and 3), and then provide a ready-made image without the “RC” label, and also supplying the stuff to the Noobs providers. Personally, I think that waiting for a release version of RISC OS is the wrong thing to do. Just look at the forum how much confusion the current situation creates – people are wasting too much time.

On the other hand, writing a simple HowTo on how to construct your own image is something that would be useful anyway. The posting by David is a very good start.

I’m very happy with the current situation. The R14 image is stable – the more recent overnight builds certainly aren’t. I’ve got two SD cards, one with the stable R14 that I use for things that don’t work with a recent overnight build, and the other for the things that work better with the overnight build.

Until people are pretty confident that most stuff will work satisfactorily with a more recent build, let’s keep the current R14 as it is.

As an alternative to using RC14 I wrote a procedure elsewhere on this forum

May I suggest that you put it in the wiki?

May I suggest that you put it in the wiki?

May I suggest that you reference the wiki?

The R14 image is stable

The point is that RC14 does not work on the RPi3 and that has to be addressed.

things that don’t work with a recent overnight build

What specifically fails with the overnight builds, it seems good here. If there are issues they need to be reported otherwise how do they get fixed.

Steffen has it right , people are trying to use RISC OS on RPi3s now.

The RPi3 has a much bigger problem than just RC14 not working, UnixLib!!

Cheap 4GB micro SD cards £2.70. I have two of these already and have ordered more before they disappear.

The R14 image is stable – the more recent overnight builds certainly aren’t.

Do you have more details about the instability of more recent builds? I did quite a lot of stuff recently using an end-of-August build, and everything was fine.

Yeah, that sounds like a plan.

Personally, I use a vanilla beta ROM and HardDisc4 setup, with a few extras (StrongEd, NetSurf etc.). But I made it in quite a convoluted way, starting with Rc14. I found the process a bit geeky, so something without the DOS image might be simpler.

I expect the big effort in rc14 is getting the 3rd party stuff tested and updated. Maybe this is where a ‘pure’ image with just the ROM and HardDisc4 would be easier?

Speaking of harddisc4, I cannot recall… how easy is it to grab PackMan, Store and/or NetSurf? Maybe so!e sort of mini downloader app could be bundled?

I did quite a lot of stuff recently using an end-of-August build, and everything was fine.

It’s possible that I’ve failed to do something in my installation of the overnight build that’s causing trouble (something to do with ZeroPain, perhaps?) so I’m reluctant to hassle people about the things that aren’t working for me, as they might well be working if I’d done everything right. As I’ve got it installed, !Draw works a treat, and Netsurf works on some sites, but crashes on others – in particular, it crashes as soon as I try to access the ROOL site, or Google. This is on a Pi B 2, with the latest NetSurf.

An old NetSurf (that came with R14 in 2013) works fine with both Google and ROOL.

If it’s actually useful, I can save the log file when NetSurf crashes – onto my local hard drive – then start up the old R14 image to email it to someone. But I strongly suspect it’s my own failure to implement everything I should have done when installing the overnight build. Perhaps a full R14 type installation of a recent overnight build would sort all my issues, I don’t know.

wiki

As a start I have put a reference here – see the second “Note”.

Press the blue info icon by the RC14 SD image download that is.

I will put in directly into the wiki as some point, I have a few more things to try yet.

Netsurf works on some sites, but crashes on others – in particular, it crashes as soon as I try to access the ROOL site, or Google. This is on a Pi B 2, with the latest NetSurf.

NetSurf #3712 is good with both ROOL’s and Google’s sites on an RPi3, ROM (14-Sep-16). It’s always easy to say something works here and it does not help much, but I am at a loss to explain why that might new going wrong.

The other thing I tried that crashed was FontEd, but perhaps that would work if I had a more recent FontEd and/or had ZeroPain installed? FontEd starts up, but then crashes as soon as you try to load a font into it. It works okay on the R14 installation. I haven’t worked out what ZeroPain is all about, or what to do with it, yet; nor have I tracked down a more recent FontEd.

And of course this is NOT on a RPi3 – I’ve got a RPiB2. But I use the more recent overnight build to enable screen resolutions more than 1920×1200.

What I’m doing is working for me. Obviously it would be nice if everything worked well on the same installation, but it’s manageable as it is, and getting my head round all the things involved in moving forward is a big hassle for me. I’m impressed by, and very grateful for, those of you who (a) have patience with the likes of me, and (b) actually make this stuff work.

AIUI Release candidates are there to be tested and I believe it is known that RC14 has some problems, many of which relate to the large range of bundled software. I suspect there is no one available to chase all the original authors for updates. Even removing 3rd party software takes time.

perhaps that would work if I had a more recent FontEd and/or had ZeroPain installed?

IME ZeroPain is essential if you want to use a high-vector ROM version on a Pi2 for actual work (as opposed to testing/experimentation etc, etc). You can find a home-rolled version here www.riscosopen.org/forum/forums/11/topics/6381 courtesy of Chris Hall (Aug 8-10 2016 posts) which I use myself. I haven’t come across any software that worked under RC14 which fails under HV/ZeroPain apart from 26-bit-only stuff like Rhapsody or Eureka, requiring Aemulor (which doesn’t work at all on a HV ROM). Apologies if this has already been covered – I haven’t followed the whole thread.