Rock Pi E Slarm64 (aarch64 unofficial slackware)

added board support, please check if it works, there is no board to check.
README.TXT
kernel 5.8.3

slarm64-current-aarch64-base-rootfs-20200628-5.8.3-rock_pi_e-build-20200827.img.zst
slarm64-current-aarch64-base-rootfs-20200628-5.8.3-rock_pi_e-build-20200827.img.zst.md5

1 Like

today came the fee provided by Radxa Team and jack.


I will test and add to the script a transfer to eMMC.

1 Like

And so the new tested image is loaded from the SDcard if there is an installed eMMC module. Also fixed transfer to eMMC after loading from card.

slarm64-current-aarch64-base-rootfs-20200901-5.8.9-rock_pi_e-build-20200916.img.zst
slarm64-current-aarch64-base-rootfs-20200901-5.8.9-rock_pi_e-build-20200916.img.zst.md5

update kernel 5.9.6
slarm64-current-aarch64-base-rootfs-20201023-5.9.6-rock_pi_e-build-20201106.img.zst
slarm64-current-aarch64-base-rootfs-20201023-5.9.6-rock_pi_e-build-20201106.img.zst.md5

1 Like

update kernel 5.9.13

slarm64-current-aarch64-base-rootfs-20201115-5.9.13-rock_pi_e-build-20201210.img.zst
slarm64-current-aarch64-base-rootfs-20201115-5.9.13-rock_pi_e-build-20201210.img.zst.sha256

update kernel 5.11.13
slarm64-current-aarch64-base-rock_pi_e-5.11.13-build-20210410.img.zst
slarm64-current-aarch64-base-rock_pi_e-5.11.13-build-20210410.img.zst.sha256

update kernel 5.12.1
slarm64-current-aarch64-base-rock_pi_e-5.12.1-build-20210503.img.zst
slarm64-current-aarch64-base-rock_pi_e-5.12.1-build-20210503.img.zst.sha256

Hi mara,

I installed slarm64-current-aarch64-base-rock_pi_e-5.11.13-build-20210410.img on my Rock Pi E, and it boots and runs fine. Forgive me my ignorance, I am still a bit confused about the package management in Slackware, and Pat Volkerding says ‘just install everything’. I know this is not the case with slarm64, especially on a board that does not have a graphics port, like the Rock Pi E, and ment to be used headless (although one could run a VNC server on it). So I understand why, and even prefer that the X server and GUI parts were left out because it results in a lot smaller image. However, I don’t understand the choices of packages that were included, and some that were left out. In my particular case, I intend to use the Pi E for a server, and a router. For these, the essential packages necessary are iptables, samba, dhcp, and maybe openvpn. I started with my setup process, but I was not even able to mount a samba share. I installed the cifs package for that to work. To make samba work took a lot more package installs: libcap-ng, iptables, libpcap, lignutls, libgnutls, gnutls, talloc, tevent, icuuc, gnupg2, icu4, icu4c, libunwind, p11-kit, nettle, cyrus-sasl, jansson. And a few more, for other basic functionality: git, python-pip, nghttp2, brotli, python3, python-setuptool.

Could these packages be included in your next image? Or, is there some special consideration that made them to be left out?

The ARM platform is new to me, and I am just trying to find my way. I also have a Rock64 with Slackware on it. That one had fewer missing packages. I also have a Raspberry Pi 3B with Slackware on it, with the full install.

Thank you for your work!

Karl

Thanks @boltran for the message,

The base system (base) is the minimum working image to boot. The rest of the choice of packages is up to the user.

The basic set (both slarm64 and slackwarearm) of packages is the same for all boards.

it makes sense to change the edition from base to server.

you can try changes in the package base.
slarm64-current-aarch64-server-rock_pi_e-5.12.1-build-20210506.img.zst
slarm64-current-aarch64-server-rock_pi_e-5.12.1-build-20210506.img.zst.sha256