today came the fee provided by Radxa Team and jack.
I will test and add to the script a transfer to eMMC.
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.
update kernel 5.9.13
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!
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.
update kernel 5.13.6
update kernel 5.16.9
After a year of not using my Rock Pi E, I downloaded your 20220214 image to it and booted. I found its ip address, ssh to it as firstname.lastname@example.org and tried to log in, using ‘root’ as password. It did not work. What is the password, or what am I doing wrong?
In the first image, the first login login is set by the user (it is unnecessary to enter any password), but it is at UART comnsole.
And I think it’s easier to make chroot and set a password.
Hi, thanks for your reply. However I do not understand.
I tried it without a password (just hit enter), but that did not work either.
Do you mean that I can’t log in via ssh?
What is a UART console?
Do I need first to mount the SD card at another linux machine, and set the password unsing chroot?
Sorry to be a bit obtuse
Yes, on another aarch64 system, mount the card and set a password in the chroot.
Or configure ssh for root access without a password:
mount the sdcard and change the ssh settings in /etc/ssh/sshd_config
I fixed this problem, I will post a new image with the kernel 5.17.y