[SOLVED] slarm64 (aarch64 unofficial slackware)

sndwvs · 01-08-2021, 04:30 AM

Quote:

Originally Posted by akschu

Update.... looks like a race condition as one boot ago it called it mmcblk1, reboot and it's mmcblk0 again.

I need to head out for my trip, but I'll know more next week.

updated the kernel with a fix for the loading order of the sdcard.

akschu · 01-13-2021, 02:07 AM

Hello Sndwvs, just got back from traveling, I was able to test the latest image...

Everything worked fine. You can't see anything on the HDMI until late in the boot, but it does work. I might load petiboot on my HC4 and see if the image still works, as that would start a console on the screen much earlier in the boot.

I noticed that the HC4 sata interface doesn't show up by default, but once I changed fdtfile=meson-sm1-odroid-c4.dtb to fdtfile=meson-sm1-odroid-hc4.dtb in /boot/uEnv.txt and rebooted it worked fine and even caused the fan to work. Perhaps it makes sense to note this in your readme so that people know that the image also works on the HC4 with an update to uEnv.txt.

I was able to compile openzfs 2.0.1 without issue and mount a ZFS volume on a sata disk. This makes the HC4 ideal for a backup host as ZFS allows you to snapshot then send the blocks over SSH to another zfs pool on another host. I am now able remote backup my file server to my HC4.

sndwvs · 01-13-2021, 02:13 AM

Hi akschu,

Thanks for testing. I will note in README.TXT regarding HC4.

akschu · 01-14-2021, 03:30 PM

I recommend the following for the README.TXT

Code:

Installation
------------------
Unpack the IMAGE file and copy the image an SD card: (assuming SD card at /dev/mmcblk0):

  # zstd -d slarm64-current-*-base-rootfs-*-build-*.img
  # dd if=slarm64-current-*-base-rootfs-*-build-*.img of=/dev/mmcblk0 bs=1M

or unpack directly to the card

  # zstdcat slarm64-current-*-base-rootfs-*-build-*.img.zst > /dev/mmcblk0


Default Login
------------------
login: root
password: password


Odroid-HC4 Support
------------------
After first boot, edit /boot/uEnv.txt and change:
  fdtfile=meson-sm1-odroid-c4.dtb 
to 
  fdtfile=meson-sm1-odroid-hc4.dtb


Note:
------------------
It may take a while before you see the login as HDMI isn't initialized until late in the boot
and because the first boot resizes the root filesystem to the size of the SD card.

sndwvs · 01-15-2021, 03:25 AM

Thanks akschu, changed.

akschu · 01-15-2021, 10:29 AM

I'm working on the Kobol Helios64 box now. The first issue is that the boot.scr doesn't have any prefix var, so uEnv.txt is never loaded because prefix isn't set to '/boot/'.

On the HC4 it was easy to get around as we were using the boot.ini, but on the Helios it's harder because I need to run mkimage but I've never worked with that before, so I'm sorting through the issues. More soon...

sndwvs · 01-15-2021, 11:08 AM

and what does env say when the bootloader stops.

akschu · 01-15-2021, 04:25 PM

Quote:

Originally Posted by sndwvs

and what does env say when the bootloader stops.

All I get is "Starting kernel ..."

The kernel isn't putting out much information because the loglevel is set too low, but setting it in eEnv.txt doesn't help because it's loaded with:

Code:

if load ${devtype} ${devnum} ${load_addr} ${prefix}uEnv.txt; then
    env import -t ${load_addr} ${filesize}
fi

Where prefix isn't set.

It's the same problem as the HC4 we worked on two weeks ago, the boot.scr needs prefix set to "/boot/". The difference is that the HC4 used boot.ini which I can just edit, while the Helios64 uses boot.scr, which apparently needs to be built with mkimage, which I haven't sorted out yet.

akschu · 01-15-2021, 05:59 PM

So far what I've found is that boot.scr needs:

1. Prefix set to '/boot/'
2. Serial is on ttyS2 not ttyS1.

Now I can see the kernel boot, but it never shows me any userspace. I changed /etc/inittab to have the console on ttyS2 but still nothing. I'll play with it more this weekend.

akschu · 01-15-2021, 08:34 PM

These changes cause the Kobol Helios64 to boot:

Code:

--- ./boot.cmd.orig
+++ boot.cmd
@@ -10,6 +10,7 @@
 setenv console "both"
 setenv rootfstype "ext4"
 setenv earlycon "off"
+setenv prefix "/boot/"

 echo "Boot script loaded from ${devtype} ${devnum}"

@@ -17,8 +18,8 @@
     env import -t ${load_addr} ${filesize}
 fi

-if test "${console}" = "display" || test "${console}" = "both"; then setenv consoleargs "console=ttyS1,1500000n8"; fi
-if test "${console}" = "serial" || test "${console}" = "both"; then setenv consoleargs "${consoleargs} console=tty1"; fi
+if test "${console}" = "display" || test "${console}" = "both"; then setenv consoleargs "console=tty1"; fi
+if test "${console}" = "serial" || test "${console}" = "both"; then setenv consoleargs "console=ttyS2,1500000 ${consoleargs}"; fi
 if test "${earlycon}" = "on"; then setenv consoleargs "earlycon ${consoleargs}"; fi

 setenv bootargs "root=${rootdev} ro rootwait rootfstype=${rootfstype} init=/sbin/init ${consoleargs} consoleblank=0 loglevel=${verbosity} usb-storage.quirks=${usbstoragequirks} ${extraargs}"

Note that I fixed display to affect the display and console to affect the console and changed the console to ttyS2.

Code:

--- ./uEnv.txt.orig
+++ ./uEnv.txt
@@ -1,4 +1,4 @@
 verbosity=4
 console=both
 fdtfile=rk3399-kobol-helios64.dtb
-rootdev=/dev/mmcblk1p1
+rootdev=/dev/mmcblk0p1

Code:

--- ./fstab.orig
+++ fstab
@@ -12,4 +12,4 @@
 #/dev/#EXT4FS_ROOT#    /               ext4     errors=remount-ro                0      1
 #/dev/#EXT4FS_HOME#    /home           ext4     defaults                         0      2

-/dev/mmcblk1p1    /          ext4    noatime,nodiratime,data=writeback,errors=remount-ro       0       1
+/dev/mmcblk0p1    /          ext4    noatime,nodiratime,data=writeback,errors=remount-ro       0       1

Code:

--- ./inittab.orig
+++ inittab
@@ -57,7 +57,7 @@
 c6:12345:respawn:/sbin/agetty 38400 tty6 linux

 # Local serial lines:
-s0:12345:respawn:/sbin/agetty ttyS1 1500000 vt100
+s0:12345:respawn:/sbin/agetty ttyS2 1500000 vt100
 #s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100
 #s2:12345:respawn:/sbin/agetty -L ttyS1 9600 vt100

That gets me up and running, but I still need to test out the fan, leds, and some other device specific stuff.

schu

sndwvs · 01-16-2021, 01:16 AM

I added fixes, although uEnv.txt should be readable with / and with /boot/

sndwvs · 01-16-2021, 04:41 AM

Hi schu,
please check, and option without prefix /boot/ in boot.src

akschu · 01-16-2021, 03:16 PM

Quote:

Originally Posted by sndwvs

Hi schu,
please check, and option without prefix /boot/ in boot.src

Confirmed, the image you made today doesn't need the prefix set in boot.scr. I was able to comment it out and have the system boot fine.

Another thing that popped up is that the 5.10.7 kernel wants to find the SD card at mmcblk1 instead of mmcblk0 where the old 5.9.9 kernel looked for it. Because of this the system wouldn't boot until I fixed it in boot.scr (or uEnv.txt), and also in fstab.

Also, I can't seem to get it to install ca-certificates through slackpkg. Any ideas why?

Code:

root@helios64:/etc/ssl/certs# slackpkg install ca-certificates

Looking for ca-certificates in package list. Please wait... DONE

No packages match the pattern for install. Try:

	/usr/sbin/slackpkg reinstall|upgrade

akschu · 01-16-2021, 06:12 PM

Something else that I'm struggling with is getting ZFS compiled on Helios64. I didn't have any issues on the Odriod HC4 nor do I have any issues on the Helios64 while running Armbian, but slarm64 on the Helios results in:

Code:

  CC       algs/aes/aes_impl_x86-64.lo
  CC       algs/aes/aes_impl.lo
  CC       algs/aes/aes_modes.lo
  CC       algs/edonr/edonr.lo
  CC       algs/modes/modes.lo
  CC       algs/modes/cbc.lo
  CC       algs/modes/gcm_generic.lo
  CC       algs/modes/gcm_pclmulqdq.lo
  CC       algs/modes/gcm.lo
  CC       algs/modes/ctr.lo
  CC       algs/modes/ccm.lo
  CC       algs/modes/ecb.lo
  CC       algs/sha1/sha1.lo
during GIMPLE pass: alias
../../module/icp/algs/sha1/sha1.c: In function ‘SHA1Transform’:
../../module/icp/algs/sha1/sha1.c:422:1: internal compiler error: Segmentation fault
  422 | SHA1Transform(SHA1_CTX *ctx, const uint8_t blk[64])
      | ^~~~~~~~~~~~~
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://gcc.gnu.org/bugs/> for instructions.
make[3]: *** [Makefile:1118: algs/sha1/sha1.lo] Error 1
make[3]: Leaving directory '/home/schu/packages/zfs/zfs-2.0.1/lib/libicp'
make[2]: *** [Makefile:678: all-recursive] Error 1
make[2]: Leaving directory '/home/schu/packages/zfs/zfs-2.0.1/lib'
make[1]: *** [Makefile:883: all-recursive] Error 1
make[1]: Leaving directory '/home/schu/packages/zfs/zfs-2.0.1'
make: *** [Makefile:744: all] Error 2

Any thoughts on this?

sndwvs · 01-17-2021, 06:16 AM

Quote:

Originally Posted by akschu

Also, I can't seem to get it to install ca-certificates through slackpkg. Any ideas why?

Code:

root@helios64:/etc/ssl/certs# slackpkg install ca-certificates

Looking for ca-certificates in package list. Please wait... DONE

No packages match the pattern for install. Try:

	/usr/sbin/slackpkg reinstall|upgrade

what says

Code:

slackpkg info ca-certificates

also what is the current time on the board.