The same as the collaboration between EndeavourOS x86_64 and Arch Linux.
To find if Archlinux ARM has a base image for a ARM SBC: Go to https://archlinuxarm.org then hover the mouse cursor over “Platforms”. Then hover over “ARMv8”, then “Amlogic” then “Odroid-N2” (which is my preferred SBC)
Following these instructions will install a Archlinux ARM base install on the micro SD card or eMMC card. This basically the same as installing a x86_64 base Archlinux install the Arch way, except it’s for ARM.
Now that we have a Arch Linux Arm base install, what EndeavourOS provides is a script that will install an EndeavourOS style Operating System very similar to the EndeavourOS Calamares install. The script installs as much as possible, the same packages as Calamares, offers a choice of the following DEs
none
xfce4
mate
kde
gnome
cinnamon
budgie
lxqt
i3wm
exactly as Calamares does, except that Archlinux Arm does not support Deepin at this time. The script also installs the EndeavourOS repository with the Endeavour goodies such as welcome, and etc. After the script install, an EndeavourOS Arm Gnome install will look pretty much like an EndeavourOS Calamares Gnome install.
Archlinux Arm is doing a wonderful job of maintaining all the base install images. They do not need nor probably want any help. The only thing EndeavourOS has to support is one script. That should be doable for the staff we have available, especially since @alenbasic has offered his support for which we are very appreciative.
We are not going to support images that you can burn to a micro SD card or eMMC card and end up with an OS and DE for a specific SBC device. The combinations would be endless and not doable for our staff. We are and will continue to make the script install as user friendly and doable as possible. Between the Archlinux Arm base install and the EndeavourOS script we hope to provide acceptable results.
What we are doing is in accordance with the EndeavourOS credo. A terminal-centric distro with a dynamic and friendly community in its core.
From what I understand, this isn’t the usual way of provisioning an SBC; from what I’ve read you normally write a full prepared system image across to the SD/MMC rather than a write a base image and then install packages. I could be wrong, though.
I would not presume to speak for the core group of devs and admins on this. We don’t do things that way here. I’m not trying to troll or be snarky, but may I ask what collaboration existed between Manjaro and Arch Linux / Arch Linux Arm. I’m just curious.
Yes that is how Ubuntu. Manjaro, and others are doing it. That is a lot like installing Fedora Workstation. You get what they decide you need like it or not. This approach allows the user to have more say in their install. Plus as stated earlier we do not have the manpower to offer full blown images for every platform combined with every DE available.
This approach isn’t for everyone. In fact ARM in general is not for everyone. But I think it falls in line with the tinkerer’s mentality of the Raspberry Pi and other Arm SBC users.
Coming from your voice of experience, I respect and take seriously your offered advice. Thank you for your concern about EndeavourOS’s future. I have definitely taken notice.
Yeah, it really depends on the manpower behind the project. For example, ALARM (who’re the base of EOSARM) do not provide images. The discussion of providing some images (say for the devices owned by the team) is ongoing so if the community would like images for certain devices in particular I’m sure we’ll take it on board and see what we can do with the resources we have.
Just to check here, it’s not up to ALARM to contact EnOS for collaboration, it’s the other way around. If EnOS is using ALARM then it’s in the interests of EnOS to ensure ALARM has what it needs to operate.
I will do what I can, though not having an ARM device might make that tricky.
sure, we do just starting with ARM, and it will also depend on what we can offer, what i mean is that we are not in the state to have anything to contribute now, we do simple use aarm as the base to get EndeavourOS installed on such devices.
But i am registered on the forum too we will see what we can do.
qemu can emulate that
And the devices are not expensive, my idea is to find out if such odroid-N2+ could be used as a machine for all the daily tasks, and it could work for sure, i do have some downs on support for the + one, as aarm still not have a kernel for it and the GPU driver needs some tweaking too.
look at this building kernel and gpu driver at the same time:
The Archlinux Arm group just released a 64 bit image for the Raspberry Pi 4b. A little background. The Raspberry Pi 4b can run a 32 bit OS or 64 bit OS. Previously Arch Arm only offered a 32 bit OS, so when the 64 bit image came out I just had to try it. To kill two birds with one stone I installed @joekamprad 's i3 setup I wanted to check out.
It’s amazing how quickly I forgot most of what I knew about i3!
Thank you for the proposed idea, we will look into that after the launch. I am going to work on other things to bring the project to the next level in October anyway. (At the moment I have a lot on my plate at work.)
Word of advice if you go the RPi4, get a fast memory card. You may not think it’ll make a difference (like I stupidly did) but it definitely does and makes the experience much more pleasant and usable. If you can afford it, also get a decent case with good passive cooling (I own the flirc which you see above, around $15USD) and you’ll be able to overclock it some and get some extra oomph out of it
I hear with a firmware upgrade, you can USB boot the pi. So if you had a nice USB 3 based hard drive, you could probably make the pi quite fast without worrying about SD speeds.
