Skip to main content
Topic: Aarch64 image (Read 1310 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic. Redirected from MOVED: Porting to other architectures

Aarch64 image

Hi all!
I became owner of Orange Pi PC2 and i want to use it as router. I installed Arch on it and made all needed hardware work but configuring systemd is just a hell.
What is the basic list of packages (aside from init system, eudev and elogind) which should be rebuild to make system work without systemd?

Re: Porting to other architectures

Reply #1
Hi all!
I became owner of Orange Pi PC2 and i want to use it as router. I installed Arch on it and made all needed hardware work but configuring systemd is just a hell.
What is the basic list of packages (aside from init system, eudev and elogind) which should be rebuild to make system work without systemd?
What you listed pretty much covers it. Just keep in mind that some packages are built against systemd libs and that you might need the systemd dummy packages to get some things working.
Chris Cromer

Re: Porting to other architectures

Reply #2
The image can boot now (runit is used as init) but every second i get messages from dmesg:
elogind: Failed to fully start up daemon: No such file or directory
elogind: Failed to connect to system bus: No such file or directory

Dbus service is at least added to default runlevel. Are there any ideas how to fix this error or at least suppress these messages?


Re: Porting to other architectures

Reply #4
The problem with elogind is caused by dbus error: /usr/share/dbus-1/system.conf is empty and it cannot start
The bigger problem is that most of curses programs don't work and print error: cannot open terminal: linux
So, there is much work to configure

Re: Porting to other architectures

Reply #5
The image seems to work now. I will clean it from logs, .pacnew files and probably some packages and upload it somewhere nearest days.

Re: Porting to other architectures

Reply #6
This is it: https://yadi.sk/d/AkiIC1B2Q2hC8g
Runit is used as init system. Root password=user name=user password: artixarm. The image mostly corresponds to Arch one, but:
-haveged is installed but not started
-wired interface is configured with init script
-dkms, nfs client and wpa_supplicant are included
-Artix repos are included to install scripts. Though it may cause architecture conflict on update
-user has full sudo access
Some extra notes:
-to rebuild most of Artix packages it is enough to add aarch64 to arch list in PKGBUILD. This doesn't work for kernel and mkinitcpio-busybox
-be careful installing dkms modules: most of dkms packages don't have real aarch64 support. This can be fixed with manual patching
-there may occur problems if you try to unpack image on non-ext4 filesystem
I hope this will work on any aarch64 device

Re: Porting to other architectures

Reply #7
Good work, @phoenix_king_rus. Moved and pinned to software development. Please, change the topic to a more descriptive title (e.g. Artix aarch64 image for Orange Pi).

Re: Aarch64 image

Reply #8
For those who wants to migrate to Artix from ArchARM i publish here archive with rebuilt packages. It containes runit as init system and some other packages:
https://yadi.sk/d/GDk0dITtRa1s4Q
Unfortunately, most of them are outdated and i can't say when i will update them