RISC OS Direct 5.31 upgrade with Wifi and Web Browser
|
I haven’t tried to reproduce this error and its circumstances, but there seems to be a problem with Access (or the ShareFS filer). Just booting RODirect fresh and letting it idle for a while leads to an Address Exception and termination of the ShareFS filer. Standard wired DHCP networking. Happens on Pi4 1 GiB as well as Pi400. But I also have a lot of stability problems atm with ROOL 5.30 and ROD 5.31 and it looks like the KVM Switch is the problem. And it looks like my old config.txt to enforce 4K@30Hz no longer works, the entries lead to non-booting – and removing them does not restore the previously working thing – just as if the Fat32 structure of Boot partition gets somehow corrupt. Does not matter if I change the file from within RISC OS or from Windows. Anyone seen something like this? I have already wasted too much time on this. |
|
The downloads on the RISC OS Direct website have been updated to resolve a many of the things arising from this thread. The basic v2 download is now 7.3 GB (thanks David Pitt) and various niggles mentioned by Steffen and others, plus those that we observed at the Wakefield meeting have been addressed. The 640×480 problem reported by Steffen has been reproduced with a monitor here, and a possible solution has been found, but it requires some coding time to provide a graceful handling. Finally, the groundwork for the complete disc image has been laid, so hopefully that will be ready next week. |
|
Many thanks for the improvement and quick take-up of the various suggestions and bug reports. Nice to see quick progress here. Now if someone could slightly improve the RODev website – I am constantly irritated by the “only one project in the Projects menu”, when you have to click on the menu itself instead of the entry to get to the full list of projects. Providing an explicit list of projects with proper links on the Home page would also be a good idea for a quick overview. And why “The real RISC OS Cogwheel” is amongst the projects, I don’t know. Just provide a “Resources” thing somewhere. |
|
OK, that seems to be discussed in the “Bugs” forum here , so a well-known problem. Strange, I hadn’t seen it much during the first RISC OS version I put onto Pi4 machines, but I always saw it with Titanium. What was the first RO version compatible with the RPi4? 5.28? So I probably had a rather stable 5.27 from perhaps mid-2020 running? |
|
If you use this url https://m.youtube.com/?app=m&persist_app=1 youtube should no longer be blank. The search works OK in !Iris. Here it is in action, |
|
Steffen – what is doubly odd is that the main change in 5.31 vs 5.30 was that the KVM fixes from earlier in the year are pre-compiled into that build. I think they have gone through some minor tweaks in the last week or so once ROOL got to approving themm, but otherwise AFAIK that functionality should be present in Direct 5.31. Direct is fully ROOL compatible ROM-wise, so you can pop in a newer nightly beta to see if it favours your KVM. If you have time, feel free to follow it up with me at andrew at riscosdev.com – always happy to troubleshoot things. Only thing you’ve requested that I can’t do is alter the main wordpress website as that’s not in my control. |
|
Thanks Andrew – free time is very “variable” at the moment, so no promises that I will be able to test things. My next plan is to use Direct on a Pi3 to see if what I see is XHCI-related. One thing I can say for sure that, amongst all the probably KVM-induced troubles I have seen with RISC OS, the ARMX6 has been rock-stable. So despite its relative slowness CPU-wise, it is still my go-to RISC OS system if the emulators won’t cut it. |
|
More results. The RO Direct 5.31 seems to be 100% stable on a RPi3B+ and a new 8 GiB RPi 4, but not on an older (probably one of the first batch) RPi 4. All on my KVM switch, I don’t know if the switching produces the hang or if it already hangs before. The RO Direct 5.29 seems to be not booting on the new 8 GiB RPi 4 – probably the firmware inside the image is too old for this model. Which means that mere users without deeper knowledge cannot apply the 5.31 update. |
|
I tried RISC OS Direct on my Raspberry Pi 4 – and had the same “fun” as detailed earlier on this thread: It simply does not boot using the Image you offer on https://www.riscosdev.com/direct/. Are there any plans to offer a RISC OS Direct image that is compatible with a more or less current Pi 4 (mine is over a 1.5 years old) as well as one that incorporates the updates since at the time being it seems the only option for me to get the current RISC OS Direct to run on my Pi probably would be to Seriously? A user new to RISC OS will probably simply run. An experienced user will probably opt for the ROOL image and just check if some apps of interest might be found on the Direct image… perhaps… |
|
All those complaining this is awkward to install could maybe do with reading the above line from the original announcement and waiting for the full release to come out? |
|
Maybe you missed the important point. The Direct v2 image is still distributed without any warning that it will not run on later Pi4 models – all it says is “v2 supports Pi4/400” which is, in the light of this new insight (or at least it was new to me), misleading. The original post also promised a fresh complete disc image “after the show”. Well, it is still “after the show”, so technically, this is not wrong, because we don’t know which show this relates to. But it takes possibly 30mins to produce such an image, so…maybe it is still uploading via a typical German internet upstream. |
|
A RISC OS related website that’s out of date? No, it’s all too much! |
|
The site does HTTPS, with HSTS enabled, an in-date certificate and no weak ciphers |
|
Go on then. |
|
Yes please go for it … it would take an experienced user quite a bit longer than some 30 mins if the only suitable Pi at hand is a Pi 4 on which the v2 image does not boot at all… so that the aforementioned detour using a ROOL image etc. is needed :-) |
|
Since I am not sure if I would be allowed to distribute the resulting image, no. Surely not. Distributing a collection of software with such a variety of licenses and distribution allowances are a complete nightmare. Add to that the possible problem of usage of the “RISC OS Direct” name and logos – complete no-go area. For me personally, I of course have such an image for my numerous Pis. That’s why I know it takes about 30min. |
|
In a surprise turn of events, I just found out the following…the old RISC OS version is not the problem with the no-boot of the RODirect v2 image on new Pi4 revisions. It is the Pi firmware stuff. Just replace it with something more modern, and RISC OS boots just fine, and you can continue to upgrade things to RO Direct 5.31 and enjoy Iris and Wifi. |
|
Ah! Well, that’s good news. Now we know that, it should be possible, in Direct, to check the version of the firmware and advise the user accordingly if it’s not recent enough. |
|
In case you haven’t noticed yet, a full v3 download is now available from https://www.riscosdev.com/projects/ (the other page – https://www.riscosdev.com/direct/ – hasn’t been updated yet). At first glance it looks to be bootable on most Pi Zero/1//2/3/4 models, although owners of the Pi 3A+ rev 1.1 may still need to upgrade the firmware (I haven’t got a Pi 3A+ rev 1.1 so I am unable to check this). |
|
So let me see if Ive got this right…? RiscOS Devs /Home/ page or /News and Events/ page doesnt even mention it (but it tells us about an upcoming show from last month) Im just glad Im not a new RiscOS user looking for the best possible RiscOS experience. Because I think Id still be looking. |
|
Just installed the 5.31 update, it went smoothly after reading the directions. I wasn’t happy with having to re-add my pinboard shortcuts. Everything else seems to be working fine. Getting used to the new pinboard. |
|
The newly revised Direct OS 5.31 v3 disc image (scroll down a bit) installed and ran on the RPi4 straight out of the box. I noticed that eeprom update files are still present in the Loader partition. A closer look at the Pi showed that the installed eeprom had been reverted to an older version and that USB boot priority settings had been lost. Before the ROD installation. *vcgencmd bootloader_version 2024/10/21 15:24:54 ... *vcgencmd bootloader_config [all] BOOT_UART=0 WAKE_ON_GPIO=1 POWER_OFF_ON_HALT=0 USB_MSD_DISCOVER_TIMEOUT=5000 BOOT_ORDER=0xf14 After the ROD installation. *vcgencmd bootloader_version 2024/04/15 14:12:14 ... *vcgencmd bootloader_config [all] BOOT_UART=0 WAKE_ON_GPIO=1 POWER_OFF_ON_HALT=0 The eeprom updater files have been removed from Direct’s Loader directory here to ensure my Pi stays as I set it up. It is just a minor point, the bigger picture is that Direct v3 now does run out now the box on the RPi4. |
|
Has anyone got direct V3 to work on a RPi Zero W ? I was hoping to be able to use wifi on the pi zero w but it keeps coming up with an internal error – suspect it may be a firmware issue ? Tried copying the loader partition from my working (on Rpi Zero with USB networking) Direct v2 image across to the v3 image but it didn’t like it. Will try an upgrade of the v2 to v3 image in next couple of days but suspect will have same issue. will do more testing when get the chance and post back, but if anyone else has already been down the road any tips appreciated |
|
the image works OK just not the networking (ie it does not see the wifi) |
|
I just tried it on my 400, and it gets stuck on the DHCP stage. Am I out of luck, since I don’t see mention in the announcement? |