Salamandar
Members
-
Joined
-
Last visited
Reputation Activity
-
Salamandar got a reaction from gprovost in Feature / Changes requests for future Helios64 board or enclosure revisionsI added voting options, please revote !
EDIT: crap… We can't edit our votes, I did not expect that
-
Salamandar got a reaction from clostro in Feature / Changes requests for future Helios64 board or enclosure revisionsWeird, that's not something I decided when setting up the post.
Well I'll just add "support announced features" Also the 2.5GB connector is already fixed in batch 2.
I have a zraid (4 HDD), never had an issue. You may need to contact Kobol on this.
True, I didn't think of that. Thanks.
-
Salamandar got a reaction from clostro in Feature / Changes requests for future Helios64 board or enclosure revisionsI added voting options, please revote !
EDIT: crap… We can't edit our votes, I did not expect that
-
Salamandar got a reaction from gprovost in Feature / Changes requests for future Helios64 board or enclosure revisionsHi everyone !
I'm really happy with my Helios64, running fine with no major issues.
BUT
This product can obviously be improved with future revisions, while keeping the same base. The Kobol guys told me to open a thread here to discuss what would be great improvement or new features.
I'm starting with things off my mind, but please ask me to add things to this list. An explanation would be great in the comments.
-
Effectively there was an issue with /boot partition behind too small, it has been fixed in future build https://github.com/armbian/build/pull/2425
-
Salamandar got a reaction from iav in unable to build zfs module on buster rockchip64Hi,
I'm still unable to build the module correctly. The ZFS kernel module is build for kernel '4.4.213-rockchip64' (the headers version name) but the kernel is '4.4.213-rk3399'.
spl: version magic '4.4.213-rockchip64 SMP mod_unload aarch64' should be '4.4.213-rk3399 SMP mod_unload aarch64'
I'm not sure this can be fixed without editing kernel headers, either :
/usr/src/linux-headers-4.4.213-rockchip64/include/config/kernel.release /usr/src/linux-headers-4.4.213-rockchip64/include/generated/utsrelease.h
@ShadowDance Are you using the "current" 5.9 kernel ? Maybe this has been fixed for this kernel ?
BTW as the procedure is a bit tiring to do by hand, I wrote some scripts to automate this (build module on Ubuntu, utils on Buster) : https://github.com/Salamandar/armbian_zfs_compiler/
MOD EDIT: Above is third party script, as always, make sure you understand what is going on before running it on your system.
Having gotten that disclaimer out of the way, thanks for your contribution, @Salamandar!
I took the liberty of marking this as solution. I also made note of the link to refer others to, later.
Cheers,
TRS-80
-
Salamandar got a reaction from TRS-80 in unable to build zfs module on buster rockchip64Hi,
I'm still unable to build the module correctly. The ZFS kernel module is build for kernel '4.4.213-rockchip64' (the headers version name) but the kernel is '4.4.213-rk3399'.
spl: version magic '4.4.213-rockchip64 SMP mod_unload aarch64' should be '4.4.213-rk3399 SMP mod_unload aarch64'
I'm not sure this can be fixed without editing kernel headers, either :
/usr/src/linux-headers-4.4.213-rockchip64/include/config/kernel.release /usr/src/linux-headers-4.4.213-rockchip64/include/generated/utsrelease.h
@ShadowDance Are you using the "current" 5.9 kernel ? Maybe this has been fixed for this kernel ?
BTW as the procedure is a bit tiring to do by hand, I wrote some scripts to automate this (build module on Ubuntu, utils on Buster) : https://github.com/Salamandar/armbian_zfs_compiler/
MOD EDIT: Above is third party script, as always, make sure you understand what is going on before running it on your system.
Having gotten that disclaimer out of the way, thanks for your contribution, @Salamandar!
I took the liberty of marking this as solution. I also made note of the link to refer others to, later.
Cheers,
TRS-80
