[SOLVED] slarm64 (aarch64 unofficial slackware)

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

Quote:

Originally Posted by akschu

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?

it could be anything, usually hardware (overclocking). if you collect something else there are similar errors?

ricky_cardo · 02-15-2021, 10:25 AM

I'm trying to test out the odroid-hc4. I zstdcat'd my microsd

Code:

zstdcat /home/rich/Documents/odroid_HC4/slarm64-current-aarch64-base-odroid_c4-5.10.5-build-20210107.img.zst > /dev/mmcblk0

(I mounted to host system and modified /boot/uEnv.txt to fdtfile=meson-sm1-odroid-hc4.dtb )

but I consistently get

Code:

sh: can't access tty: job control turned off

(I'm new to this so bear with me) Should I do something to petiboot? (was there a 1st step I missed?)

I noticed if I boot up to petiboot (without the sd inserted)
then exit, insert the sd and relaunch petiboot I can see the SD [NOLABEL]

althought selecting it caused "sh: can't access tty: job control turned off"

I saw mention of adjusting the mmcblk1 should I give this a try?

sndwvs · 02-15-2021, 10:52 AM

Hi ricky_cardo,

as far as I remember, you need to erase the bootloader from SPI.

ricky_cardo · 02-15-2021, 12:28 PM

Erased petaboot and works great.

flash_eraseall /dev/mtd0
flash_eraseall /dev/mtd1
flash_eraseall /dev/mtd2
flash_eraseall /dev/mtd3

Thanks

mralk3 · 03-09-2021, 06:51 PM

I managed to save the wrong settings with u-boot to the SPI FLash on a RockPro64 (aarch64). Now it only looks for a tftp network boot. I was trying out a kernel and ramdisk and ran "saveenv" when I shouldn't have. Is there some way I can easily set u-boot to boot from the SD Card first? I have slarm64 installed and now I cannot boot it!

aaditya · 03-10-2021, 10:11 AM

Quote:

Originally Posted by mralk3

I managed to save the wrong settings with u-boot to the SPI FLash on a RockPro64 (aarch64). Now it only looks for a tftp network boot. I was trying out a kernel and ramdisk and ran "saveenv" when I shouldn't have. Is there some way I can easily set u-boot to boot from the SD Card first? I have slarm64 installed and now I cannot boot it!

You should be able to disable SPI while booting: https://wiki.pine64.org/wiki/ROCKPro...ile_booting.29

Lockywolf · 03-10-2021, 11:31 PM

Is there a package shipping dtoverlay (and maybe some other tools) from the official raspberry pi "userland"?

(https://github.com/raspberrypi/userland.git)?

I tried building it myself, and some of it builds fine, but some doesn't.

So if there is a package, I would prefer it, before jumping into writing the slackbuild myself.

(I am using this mirror: http://mirrors.aptalaska.net/slackwa...arm64-current/)

sndwvs · 03-11-2021, 12:02 PM

additional packages are included in the assembly
rpi-eeprom-20210212_2fec47b-aarch64-1mara.txz
rpi-userland-20210111_4a0a19b-aarch64-1mara.txz
build script rpi-eeprom rpi-userland

sndwvs · 03-14-2021, 10:44 AM

slarm64-riscv64-current-riscv64-rootfs-20210314.info.txt
slarm64-riscv64-current-riscv64-rootfs-20210314.tar.xz

Lockywolf · 03-15-2021, 11:00 PM

How do I enable bootlogd on slarm64?

On slackware64, I vaguely remember enabling it by just adding a line to /etc/inittab:

/etc/inittab:lg:S:sysinit:/sbin/bootlogd -c -s -p /var/lock/subsys/bootlogd.pid , and it was enough.

But this doesn't seem to work on pi. Any ideas?

sndwvs · 03-16-2021, 12:02 PM

Quote:

Originally Posted by Lockywolf

How do I enable bootlogd on slarm64?

On slackware64, I vaguely remember enabling it by just adding a line to /etc/inittab:

/etc/inittab:lg:S:sysinit:/sbin/bootlogd -c -s -p /var/lock/subsys/bootlogd.pid , and it was enough.

But this doesn't seem to work on pi. Any ideas?

what I looked at about bootlogd does not depend on the architecture in any way, here is one of the solutions.

mralk3 · 03-21-2021, 06:47 AM

please add kpartx from slackwarearm-current. it was added to the main tree:

http://slackware.uk/slackwarearm/sla.../ChangeLog.txt

Code:

Tue Mar 16 08:08:08 UTC 2021

..snip..

d/kpartx-0.8.5-arm-2.txz:  Added.
  Moved from /extra.
  This is being used for building the Slackware AArch64's boot
  environment.

Thanks for your hard work!

sndwvs · 03-21-2021, 01:16 PM

Quote:

Originally Posted by mralk3

please add kpartx from slackwarearm-current. it was added to the main tree:

http://slackware.uk/slackwarearm/sla.../ChangeLog.txt

Code:

Tue Mar 16 08:08:08 UTC 2021

..snip..

d/kpartx-0.8.5-arm-2.txz:  Added.
  Moved from /extra.
  This is being used for building the Slackware AArch64's boot
  environment.

Thanks for your hard work!

kpartx - this package is not in the main branch of Slackware64-current, it repeats the functionality of the existing partx programs, partprobe.

mralk3 · 03-22-2021, 10:14 AM

Quote:

Originally Posted by sndwvs

kpartx - this package is not in the main branch of Slackware64-current, it repeats the functionality of the existing partx programs, partprobe.

Ok no problem. I did google it to see if this was true: https://unix.stackexchange.com/quest...rtx-and-kpartx

However, ONLY kpartx is being built on aarch64. Not the full suite.

EDIT: I should mention that I am using it on slarm64 without issue.

Lockywolf · 03-22-2021, 10:54 PM

Quote:

Originally Posted by sndwvs

what I looked at about bootlogd does not depend on the architecture in any way, here is one of the solutions.

Well, that solution suggests that 'CONFIG_LEGACY_PTYS' should be enabled in the kernel. For some reason, at least on the sarpi64 5.9.12 kernel it is not enabled. I will try to update to the latest 5.10 in slarm64 and check.