No not all cpus are affected, not by a very long shot. Only ones that have speculative execution (through a vulnerable cache design). And from what they are saying/implying it has to be more than just a little branch prediction/prefetch, meaning it needs more fetching than that. I cant see this core falling into that category. But will see I guess.
If you dont have an mmu/cache then you are certainly not vulnerable to this category of problem.
I did a test on a fresh Omega2+ and it seemed to install fine. The Editor is a relatively large package and may need a few minutes to download and install.
Make sure you are on the latest firmware by running oupgrade, and then try installing from the Console again, and if that doesn't work try following these steps:
Post some screen captures of the Console and trying to install the Editor, showing the "Please refresh the page" screen and after refreshing where it still asks to install
Login to the Omega's command line using this guide: https://docs.onion.io/omega2-docs/connecting-to-the-omega-terminal.html
Run the following commands
opkg install onion-console-editor
Run the following command and post the output:
opkg list-installed | grep onion-
The Omega uses Avahi (zeroconf) to name the Omega on your local network. Installing Bonjour will allow your windows machine to listen for zeroconf configurations on your network as @Luciano-S mentioned :)
Hi @Petr-Cermak, yup, we are working on making the console mobile friendly. We will be adding a paged layout for the icons and reducing the icon sizes, etc. It should become available in the February release of the Onion Console. Please stay tuned!
@Eduardo-Marín Oh i see what you mean. Yeah, the community site uses socket to communicate with the backend so that it has realtime communication between the backend and the front end. Since the community site uses a software that's not created by us, we don't really have an option to change the way the frontend communicates with the backend. If this is a bug, i think they should be able to address the bug in their next software update.