No luck, see kernel panic above. The missing command can be seen below; `Unknown command 'kaslrseed' - try 'help'`:
U-Boot 2022.07-armbian (Aug 22 2023 - 15:26:42 +0000)
SoC: Rockchip rk3399
Reset cause: POR
DRAM: 3.9 GiB
PMIC: RK808
Core: 339 devices, 31 uclasses, devicetree: separate
SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
MMC: mmc@fe320000: 1, mmc@fe330000: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Model: Helios64
Revision: 1.2 - 4GB non ECC
Net: dw_dm_mdio_init: mdio node is missing, registering legacy mdio busNo ethernet found.
scanning bus for devices...
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
3252 bytes read in 5 ms (634.8 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 1
166 bytes read in 4 ms (40 KiB/s)
24417797 bytes read in 1036 ms (22.5 MiB/s)
29792768 bytes read in 1264 ms (22.5 MiB/s)
86670 bytes read in 12 ms (6.9 MiB/s)
2698 bytes read in 8 ms (329.1 KiB/s)
Applying kernel provided DT fixup script (rockchip-fixup.scr)
## Executing script at 09000000
Unknown command 'kaslrseed' - try 'help'
Moving Image from 0x2080000 to 0x2200000, end=3f00000
## Loading init Ramdisk from Legacy Image at 06000000 ...
Image Name: uInitrd
Image Type: AArch64 Linux RAMDisk Image (gzip compressed)
Data Size: 24417733 Bytes = 23.3 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
Booting using the fdt blob at 0x1f00000
Loading Ramdisk to f4794000, end f5edd5c5 ... OK
Loading Device Tree to 00000000f4716000, end 00000000f4793fff ... OK
Starting kernel ...
Sorry, the line about disabling was just to make sure you disable the armbian-zram-config service by setting ENABLED to false.
As a warning, though, I found some problems with this if you log to a zfs share. It seems you have to make sure zfs gets loaded before the logging starts up, otherwise you can get a kernel panic on occasion. I didn't really dig into how to fix this, so I just log and swap to a usb drive instead now.
RK3399 has a single PCIe 2.1 x 4 lanes port, you can't split the lanes for multi interfaces unless you use a PCIe switch which is an additional component that would increase a lot the board cost.
That's clearly the intention, we don't want either to restart form scratch the software and documentation :P
Yes this will be fixed, it was a silly design mistake. We will also make the back panel bracket holder with rounder edges to avoid user to scratch their hands :/
We will post soon how to manage fan speed based on HDD temperature (using hddtemp tool), that would make more sense than current approach.
You can already find an old example : https://unix.stackexchange.com/questions/499409/adjust-fan-speed-via-fancontrol-according-to-hard-disk-temperature-hddtemp
The design is awesome so I'd definitely not change it!
I would have liked to have WoL working, that is an important feature for those who don't plan on having it on 24/7. (I know, a NAS is intended to be on 24/7, but to have something more environmental friendly, the ability to turn it off and on without physically touching the device is a must)
Other than that, I'd also add the option to disable or at least deem the front leds (can't place it in a visible place it near the TV).
and ECC ram would also be very welcome.
ZFS was just upgraded to v2.0.1 https://armbian.atlassian.net/browse/AR-614 which is a preparation for pushing a kernel on and above 5.10.y. Upgrade was tested on Armbian Buster/Bullseye/Focal/Hirsute. My test ZPOOL was always loaded without any troubles.
We only support upgrade troubles - for ZFS functional problems, please check / file a bug report here https://github.com/openzfs/zfs/issues
Shared lines are not uncommon even on x86 mainboards. For example: https://www.asrock.com/mb/intel/fatal1ty z97 killer/#Specification
Take note at Storage and Slots sections:
That is to mention as addition to @tommitytom.
You can try to sell it in forums. I already noticed a few people who did this successfully here. However if I were a potential buyer I'd consider a person with such an attitude not necessarily trustworthy
Seems like the mistake is yours. It's made pretty clear that the port is shared (it's even mentioned twice on the front page of kobol.io), it's not exactly a secret.
I added zfs zfs-dkms_0.8.5-2~20.04.york0_all to our repository so at least Ubuntu version works OOB (apt install zfs-dkms). I tested installation on Odroid N2+ running 5.9.11
* packaging mirrors need some time to receive updates so you might get some file-not-found, but it will work tomorrow. Headers must be installed from armbian-config.
Patch versions are reserved for emergency fixes, but we don't necessarily update all kernels. We need to test things before pushing out update to minimize unpleasant surprises.
A major update (20.11) is around the corner and things will be updated then.
To fellow zfs users, I just saw that the 0.8.5 release is out with many compatibility patches, we should wait until this version lands in the repos to use it on the Helios64