fossxplorer

Members
  • Content Count

    73
  • Joined

  • Last visited

About fossxplorer

  • Rank
    Advanced Member

Recent Profile Visitors

1017 profile views
  1. Anyone tried to run k8s/k3s on these? Last time i tried, it lacked some kernel cgroup features IIRC.
  2. I wonder the same since Google couldn't tell me that's this is can be bought as of today.
  3. Thanks for your advises @NicoD I have several use cases, which i've bought a couple of HP thin clients to see if they can cover my needs. This because i really got fed up with the I/O options of the boxes i've played with. Anyway, my uses cases are different, one of them being NAS, and i've seen a 4 port SATA NAS HAT by @mindee somewhere here i look forward to being tested/reviewed. Will that HAT work with this board? And based on your video review, i really like this board as i probably don't need to deal with heat dissipation due to the nice heatsink. Being able to feed it with current from power bank is a plus for me as i'm gonne bring this "computer" to south asia where power comes and goes :)
  4. @nicoD Fantastic video you made for this board. I really really want to order one after watching your video! Thanks a lot!
  5. Nice to see a low cost ARM SBC with BMC, pretty amazing. If the BMC will be reviewed working, i'll get one. Also, the I/O ability on this board seems fantastic! Seems $149 for the 4GB version.
  6. It's actually specified in the item ad: Power supply interface (5.5*2.5 standard interface) 12V 4A, which makes sense to be able to deliver 2A at max for 3.5" HDD startup power.
  7. Sorry i quoted the wrong link. The link is from your post at OMV site: https://www.ebay.ca/itm/HD622-PCBA-Board-USB-3-0-to-Dual-SATA-Adapter-Card-for-2-5-or-3-5inch-HDD-SSD/122211050288 I was thinking about the barrel DC in on this board and what kind of PSU i'd need. I really like these adapter as it saves me a lot of other adapters i've been buying lately to build a NAS from ARM SBC boards.
  8. Any suggestion to a PSU for this adapter board which seems pretty nice? I'm not sure about how that board would handle 12v/5v to the drives.
  9. I have been happy user of Vscission V88 Piano board for some months running Armbian and ZFS, but yesterday after some trouble rebooting like 20x after the box hang during an attempt to clone a Corsair 32GB USB drive, i can't get it to boot Armbian any longer! I've verified i'ts' not the SDcard nor the content in it (correct dtb.img etc) and i even downloaded another image from dl.armbian.com and tested a new SD card with no luck. It boots Android just fine when SD card is not inserted, but when inserted i see a red light and nothing on the screen. Sad since this one has enough RAM to run a lot of stuff. What could this be?
  10. I have 2 RK3288 devices, is it possible to test this off an SD-card before overwriting the eMMC? Edit: Never mind. README.txt gave me some more info and this script can only be installed once you have a running system. Now i need to find an image for my RK3288 TV-box!
  11. Thanks a lot @Jason Fisher Based on your feedback and invaluable hints and tips, i was finally able to get ZFS to compile/build on my V88 RK3328 box. I also did switch to experimental kernel (beta) and things went fine. Thank you very much!
  12. Amazing results of RK3399. Thx for sharing such details with us. I'd like to order RockPro64 when it comes available again.
  13. @balbes150 i'm trying to run Kubernetes using your kernel, but it seems to lack some cgroup support such as freeer, and other kernel support for ip_nf and netfilter_xt. + some other missing kernel support too, please see below marked in bold. Possible to get these into the next version? root@amlogic:~# kubeadm join --token 82e7a9.543a20d2e1b46566 192.168.1.105:6443 --discovery-token-ca-cert-hash sha256:030150ccecdfd2139bd3f532b92153870ea01f9cf319b1fb8954dab76357fb45[preflight] Running pre-flight checks. [preflight] The system verification failed. Printing the output from the verification: KERNEL_VERSION: 4.14.0-rc2-next-20170929-amlogics905x CONFIG_NAMESPACES: enabled CONFIG_NET_NS: enabled CONFIG_PID_NS: enabled CONFIG_IPC_NS: enabled CONFIG_UTS_NS: enabled CONFIG_CGROUPS: enabled CONFIG_CGROUP_CPUACCT: enabled CONFIG_CGROUP_DEVICE: enabled CONFIG_CGROUP_FREEZER: not set CONFIG_CGROUP_SCHED: enabled CONFIG_CPUSETS: enabled CONFIG_MEMCG: enabled CONFIG_INET: enabled CONFIG_EXT4_FS: enabled CONFIG_PROC_FS: enabled CONFIG_IP_NF_TARGET_REDIRECT: not set CONFIG_NETFILTER_XT_MATCH_COMMENT: not set CONFIG_OVERLAY_FS: enabled CONFIG_AUFS_FS: not set - Required for aufs. CONFIG_BLK_DEV_DM: not set - Required for devicemapper. DOCKER_VERSION: 17.12.1-ce OS: Linux CGROUPS_CPU: enabled CGROUPS_CPUACCT: enabled CGROUPS_CPUSET: enabled CGROUPS_DEVICES: enabled CGROUPS_FREEZER: missing CGROUPS_MEMORY: enabled [WARNING SystemVerification]: docker version is greater than the most recently validated version. Docker version: 17.12.1-ce. Max validated version: 17.03 [WARNING FileExisting-crictl]: crictl not found in system path [preflight] Some fatal errors occurred: [ERROR SystemVerification]: unexpected kernel config: CONFIG_CGROUP_FREEZER CONFIG_IP_NF_TARGET_REDIRECT CONFIG_NETFILTER_XT_MATCH_COMMENT [ERROR SystemVerification]: missing cgroups: freezer [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...` root@amlogic:~#
  14. Thanks for that info! root@rock64:~/tmp/spl-spl-0.7.6# find /usr/src/linux-headers-4.4.115-rk3328/ -iname 'gcc-wrapper*' /usr/src/linux-headers-4.4.115-rk3328/scripts/gcc-wrapper.py root@rock64:~/tmp/spl-spl-0.7.6# mv /usr/src/linux-headers-4.4.115-rk3328/scripts/gcc-wrapper.py /tmp/ root@rock64:~/tmp/spl-spl-0.7.6# ./autogen.sh .. # went fine root@rock64:~/tmp/spl-spl-0.7.6# ./configure .. checking whether dpkg-buildpackage is available... yes (1.18.4.) checking whether alien is available... yes (8.95) checking spl config... all checking kernel source directory... /usr/src/linux-headers-4.4.115-rk3328 checking kernel build directory... /usr/src/linux-headers-4.4.115-rk3328 checking kernel source version... 4.4.115 checking kernel file name for module symbols... Module.symvers checking whether debugging is enabled... no checking whether basic kmem accounting is enabled... no checking whether detailed kmem tracking is enabled... no checking whether modules can be built... no configure: error: *** Unable to build an empty module. Any more hints would be welcome