Rockchip

After Seeing all that spi nmve boot hype for the other boards and some time left i took the effort to level up the Orange Pi boards because they are the same as the rest it has a rk3399. The Uboot was a mess so i matched it with the kerenel dts a lot and corrected some issues. Dts debug is not the friendliest debug it compiles or not And after some trial and error (a lot ) and finding a spi nor flash wich is supported (or you add one of your own) it costs a esp8266 has 4mb spi flash or a old printer who had a 4mb and 8mb i got a boot from spi so . and with reading the armbian forum i saw 150balbes talked about usb boot and didnt know …

When there is a kernel panic the fans stop which causes the HDD and CPU temperatures to rise unchecked. I've just come back to find my board has crashed again and the HDD temperatures had risen above 60c which is not good. Is there a watchdog or boot setting to automatically reset the processor after a kernel panic ?

That newsletter indicated that USB-C to HDMI cables promised were still delayed. Is there an update on that? Thanks!

Thought I'd download the latest image in the hope that it might be more stable ... kernel panic on reboot, booted second time and then whlst trying to update kernel panic again. This board seems to be so unstable it's bascially unuseable

I have installed Armbian 21.02 Ubuntu 20.04 Focal with Linux kernel 5.10.16 and OpenZFS 2.0.1-1 on my Helios64. Created a three-disk encrypted RAIDZ pool with the following command: sudo zpool create -f -o ashift=12 -O compression=lz4 -O atime=off -O acltype=posixacl -O xattr=sa -O encryption=aes-256-gcm -O keylocation=prompt -O keyformat=passphrase tank raidz1 /dev/disk/by-id/foobar1 /dev/disk/by-id/foobar2 /dev/disk/by-id/foobar3 Then I did a single sequential read benchmark with fio on /tank: cd /tank sudo fio --name=single-sequential-read --ioengine=posixaio --rw=read --bs=1m --size=16g --numjobs=1 --iodepth=1 --runtime=60 --time_based …

Hello together, i experienced network problems with Helios64 and latest Debian Buster Image. I cannot setup a static ip address after installation of OMV5, moreover it crashes on install. I double checked it on a fresh image without any changes and an immediate installation of OMV over softy. The result is the same. After the crash OMV is in fact available, but the network configuration is broken and a static setup doesnt work over the OMV UI, nor armbian-config, also the boot takes about 2-5 minutes due to whatever reason. armbianmonitor http://ix.io/2PPJ

Hi, everyone. The Kobo site is kind of difficult to navigate if you're looking for relevant information, but I came to the conclusion that this is the right place for support. Forgive me if I'm mistaken. I was wondering if someone could help me interpret these bootlogs from serial term when trying to boot my Helios64 from the EMMC. Following the instructions on Kobol's site, I flashed their u-boot image to an sd card, booted the Helios64 off of said sd, fetched the latest image of Armbian, unpacked that image, and flashed it from my laptop to the Helios64 via usbc to what I presume is the correct interface. Could it be that I messed up? Here's a quick example …

Hello all, I have this board running in a k3s kubernetes cluster, and almost everyday, different time, the board reboots. Please, could you help me to figure out which is the problem? The armbianmonitor output is bellow: http://ix.it/2OOZ Many Thanks,

I am trying to enable sound with RT5651 audio codec on SoM-RK3399v2. Hardware is integrated on the board (on i2c1 bus, address 0x1a), worked with official FriendlyElec Linux (4.4 kernel IIRC) and tests were run with powered speakers (which work when connected to PC). I used this patch to patch my current device tree: https://github.com/armbian/build/blob/master/patch/kernel/rockchip64-dev/board-nanopi-m4v2-dts-add-sound-card.patch I did not use Kconfig file from the patch as it seems that my kernel have has built that modules. page 19 of NanoPI M4V2 and page 7 of SoM-RK3399 schematic shows that same audio codec (rt5651 on the same busses (I2S1 and I2C1…

Hi ! I spent several hours looking for the solution, here and elsewhere, I didn't find. The Radxa wiki speaks about 2 SPI: 1 and 2 The device tree README speaks about 4 SPI: SPI 0 pins (MOSI, MISO, SCK, CS): GPIO3_A5, GPIO3_A4, GPIO3_A6, GPIO3_A7 SPI 1 pins (MOSI, MISO, SCK, CS): GPIO1_A7, GPIO1_B0, GPIO1_B1, GPIO1_B2 SPI 2 pins (MOSI, MISO, SCK, CS): GPIO1_C0, GPIO1_B7, GPIO1_C1, GPIO1_C2 SPI 3 pins (MOSI, MISO, SCK, CS): GPIO2_B2, GPIO2_B1, GPIO2_B3, GPIO2_B4 So, the correspondence seems to be: radxa SPI 1 <=> DT SPI 1 radxa SPI2 <=> DT SPI 3 With the latest kernel (5.10.12-rockchip64, Deb…

Hi. I am faced with the problem of installing overlays on Orange Pi 4. I need to use SPI and I use the following settings: verbosity=1 bootlogo=false overlay_prefix=rockchip rootdev=UUID=946e374a-7ca8-488d-ad86-ab38ccfc7cc1 rootfstype=ext4 overlays=spi-spidev param_spidev_spi_bus=0 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u As far as I know, after connecting the overlays, the devices should appear in the list / div, but this does not happen. New devices will not appear also when installing overlays w1-gpio or uart1 I also have problems with Ethernet connection if I use param_spidev_spi_bus=0, but if i use param_spidev_spi_bus=…

Hi everyone, I have installed openmediavault and zfs. Since yesterday I have this error: Failed to execute command 'export PATH = / bin: / sbin: / usr / bin: / usr / sbin: / usr / local / bin: / usr / local / sbin; export LANG = C.UTF-8; zfs list -H -t snapshot -o name, used, refer 2> & 1 'with exit code' 1 ': The ZFS modules are not loaded. Try running '/ sbin / modprobe zfs' as root to load them. Click "show details" Error # 0: OMV \ ExecException: Failed to execute command 'export PATH = / bin: / sbin: / usr / bin: / usr / sbin: / usr / local / bin: / usr / local / sbin; export LANG = C.UTF-8; zfs list -H -t snapshot -o name, us…

Hello, I've bought 3 new identical drives and put 2 of them in the Helios64 and 1 onto my desktop. I ran smartctl longtest+shortest on both drives simultanously but all of them were aborted/interupted by host. `# /usr/sbin/smartctl -a /dev/sda` Output: http://ix.io/2OLt On my desktop the longtest from smartctl succeeds without error and all 3 drives received the same care, I just bough them and installed them, so unlikely the drives are physically damaged. The complete diagnostic log: http://ix.io/2OBr So anyone got an idea why are my SMART extended tests being canceled? Note: I've tried ev…

NVMe hard disk is not recognized anymore after last firmware/image update. localhost kernel: rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout! localhost kernel: rockchip-pcie: probe of f8000000.pcie failed with error -110

Had my Helios up and running for a few months now running off SD card, but there was a message (can't remember where) to not make the install you 'final' setup as things were still in development. I've been keeping track of the 'what works and doesn't' , but as there are no updates in 6 weeks, is the general consensus that we've reached stability and its time to transfer to the eMMC?

Just applied the latest update to my Helios64, here is what apt reported: The following packages will be upgraded: armbian-config armbian-firmware base-files device-tree-compiler file iproute2 libcairo2 libgnutls30 libgnutls30:armhf libmagic-mgc libmagic1 libnss-myhostname libpam-systemd libsystemd0 libudev1 linux-buster-root-current-helios64 linux-dtb-current-rockchip64 linux-image-current-rockchip64 linux-u-boot-helios64-current systemd systemd-sysv udev unzip This went just fine until it tried to setup systemd, the Helios then lost all network connection: Spoiler Fetched 57.9 MB in 1min 51s (523 kB/s) Preconfiguring packa…

Hello, I update my Orange PI 4 with the update Armbian 21.02.1 Focal and I was surprided to see the maximum CPU (A72) frequency is now limited to 1.8GHz. In previous version, this maximum frequency was 2GHz. Is it normal or is it a regression ? Thank you in advance for your help !

I thought I'd rebuild the NAS with the latest image in the hope that it would be more stable. Unfortunately my hopes were in vain. I was in the middle of doing an rsync and it crashed with a kernel panic. Had a look on the forum and implemented the two suggestions of limiting the cpu to 1200MHz and tweaking the voltages. CPU @ 50c as reported in the login header. Anyway after updating the setting I reboot it and it crashed immediately ! The same SMP issue that seems to have been plaguing this board since release

Hi, I'm very pleased with my Helios 64, but since I updated to Armbian 20.11.6 (from 20.08.11 or 21, not really sure) it reboots at random times: it can run fine for over two weeks and reboot twice in 36 hours, always when idling. It's running OMV as well a multiple Docker containers: PiHole, Wireguard, Nginx, Transmission, restic-server and n8n. Is it a common issue? What fixes do you recommend? What should I look for to diagnose the issue? Thank you. Edit: forgot to mention that I'm using SnapRAID and mergerFS, as well as NFS shares.

Hi there, I love my Helios64 to death. I'm running MooseFS CE and MooseFS PRO. The problem is I'm absolutely hammering it with I/O and it's consistently hard crashing, and no fix I've tried helps. Should I revert to the older kernel version or something? Or is this a useful test case...

Hi~ After "sudo poweroff" , my OPI4 does not boot anymore.(p.s. when i use "sudo reboot" ,it works.) I had looked over some topics，but i still get how to fix uboot . Can someone help me?Thanks!!!!! p.s I try to use "armbian-config"/"install" to fix the problem,but there was no "boot from sd"

Hi, Just noticed image " Linux rockpi-4a 5.9.14-rockchip64 #20.11.4 SMP PREEMPT Tue Dec 15 08:52:20 CET 2020 aarch64 GNU/Linux " my rockpi4a runs at 2Ghz. To radxa overclocking is possible so that 2GHz is not a real surprise ... Though checked " armbianEnv.txt " but did not find any "overlays" option present overlocking this board, neither any other files in /boot ( or /boot/dtb/rockchip/overlay ). However building a custom image ( kernel 5.10 ) it is running at 1,8GHz again, how can I set this to 2GHz ? ( as a side note - tehre is no need to enable panfrost BTW as I run this as a headless server ) Thanks

Hi, I'm using a RockPi 4 B as a wifi access point. Everything is working fine with good performances until the Wifi stop working, usually after 3-4 days. When that happens, dmesg is flooded with these logs : [221057.075187] ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110 [221057.075202] ieee80211 phy0: brcmf_cfg80211_get_station: GET STA INFO failed, -110 [221124.657840] ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110 [221127.217786] ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110 [221127.217806] ieee80211 phy0: brcmf_cfg80211_get_stat…

Hello. I'm using a NanoPi M4V2 with 4GB of LPDDR4. Before installing Armbian, I tried FriendlyElec and the total amount of 4GB of RAM was detected. When moving to Armbian Buster with kernel 5.9.14-rockchip64, the system is detecting only 2GB of RAM (MemTotal: 1964780 kB). I searched the forum to see if anyone else was having this problem but strangely I found no more reports of this issue. I also tried Armbian Focal, but the problem remains. Thank you.

Hello, I installed OMV on my Helios64 and created a share. The device stays online and works well for hours and then at some point eth0 goes offline and no longer communicates. The only way to restore connectivity is with a reboot. I looked at the logs and dont see anything jumping out at me as to why this happens but I could very easily be missing something or the log didnt capture the event. I have not yet tried to console in through the USBc port when this occurs but will try next time. Has anyone else seen this issue or fixed it?

Hello ! i'm trying to enable the SPI interface on a OrangePi4B board using Focal latest stable build, so I edit `/boot/armbianEnv.txt` to add these lines : overlays=spi-spidev param_spidev_spi_bus=0 But after rebooting, I'm unable to access to the board anymore (No IP address is assigned to the board by the DHCP server). What's wrong ? Is there any additionnal steps ? FYI, I also tried to enable SPI using armbian-config tool but it doesn't work neither. As this tool doesn't even specify the `param_spidev_spi_bus` parameters which is required according to the overlay README.

I have run into this issue multiple times and the process flow is this: Flash image "Armbian_20.11.6_Helios64_buster_current_5.9.14.img" to a micro SD card. Run through the config (installing OMV with SAMBA) Kick over to the OMV to configure the share / media so its available on my network Runs for some time (this last install was running for maybe a few weeks before it triggered a Kernel panic) Power off. Power on. Board boots, hangs on "Starting Kernel..." Is there some trick I am missing to get this thing to actually boot / reboot correctly? Troubleshooting info: No jumpers are shorted. I had a…

Hello everybody, im experiencing a similar problem. Sometimes my WD RED 12 TB HDD is not recognized in that slot its in, when i change it to any other it works again. Nevertheless it seems this problem doesnt only apply to one specific slot, but is changing from time to time. EDIT: The LED of that slot doesnt turn on, yet the drive starts and runs Do anybody experience the same problem, or know any help? Thank you in advance. Best Regards.

Hi 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.

Hi guys, My Helios64 keeps going offline, it has this red light come on the front panel but i am not sure what it means exactly. This happens once every few weeks, the system is fine after a reboot. What does this red light mean exactly? Is there anything i can do to prevent these breakdowns? Cheers,

Hello all, I get the message "qemu kvm_arm_vcpu_init failed: Invalid argument" which I refer to the source file code "https://git.qemu.org/?p=qemu.git;a=blob;f=cpus.c;hb=refs/ heads / stable-2.11 # l1122" and "https://github.com/qemu/qemu/blob/master/accel/kvm/kvm-all.c " Row 444. I don't know which vCPU feature is expected ... #cat /proc/cpuinfo processor : 0 BogoMIPS : 48.00 Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part : 0xd03 CPU revision : 4 .... is it currently or later even p…

Hi all Been playing with this rockpi s bluetooth . I noticed debian kernel 5.x and bluetoothctl, just hangs. No issues with debian kernel 4.x. Anyone else had this, and able to get it to work?

Trying to understand this issue. If I ONLY need the 1Gbs (LAN1) ethernet connection and DO NOT need the 2.5Gbs (LAN2) connection, do I need to perform the "Fix" for this issue? I'll be using Armbian Buster for this device.

Hello everybody, Is it possible to use the box with another card (odroid n2 for example)? Thanks a lot

Today I updated and upgraded my system, and after a reboot 'apt list' did no longer work. It shows 'Listing... done', and then uses 100% CPU on a single core, without producing anything. According to strace it's looping on reading a file: openat(AT_FDCWD, "/var/lib/apt/lists/deb.debian.org_debian_dists_buster_main_binary-arm64_Packages.lz4", O_RDONLY) = 28 read(28, "\4\"M\30@@\300\206z\0\0\370\377\31Package: 0ad-data\n"..., 65536) = 65536 read(28, "ta$E\17p\2+\377\21c376d3f140540d9424753d"..., 65536) = 65536 read(28, "a5180e3e2d3f503ddcb5dd7b93\201\2\2\275\0\17"..., 65536) = 65536 read(28, "\2\3700071880bc23623a4ea3664b773a1b6"..., 65536) = 65536 read(28, "\f1'da?\2Jd…

What am I missing ? Just flashed Armbian_20.11.7_Nanopim4v2_buster_legacy_4.4.213_desktop on a SD card and the NanoPi does not boot. I get a steady red led and no flashing green and nothing on the HDMI. I don't get that problem when Flashing the eMMC...the problem is that I don't have that eMMC anymore and I am looking for a way to install Armbian on my NanoPi's NVMe SSD drive from the SD card. Any hints would be appreciated.

I literally registered to post this complaint here. How STUPID it is to have a M.2 SATA SHARED WITH HDD1!! IT DEFEATS THE WHOLE PURPOSE OF THIS ENCLOSURE. PERIOD!!!! My mistake was that I did not know what it meant that M.2 was SHARED before I purchased this enclosure and now, I have a need to expand beyond the measly 16GB of your eMMC and I found out THE PAINFUL WAY that IT IS NOT POSSIBLE because of the shared SATA port. IT"S BEYOND FRUSTRATION. YOU CANNOT EVEN IMAGINE HOW STUPID THIS DECISION OF YOURS IS. IT JUST LITERALLY DOWNGRADED YOUR NAS FROM AN EXCELLENT ENCLOSURE TO AN OVERPRICED JUNK THAT I HAD TO WAIT FOR FOR MORE THAN 6 …

I haven't been able to find any specs on the eMMC module in the helios64. I've found some posts online indicating that it is a samsung KLMAG1JETD-B041, but I haven't been able to find any info on the write endurance of this module (not sure if it is standard for eMMC vendors to provide that information like SSD vendors). I have been able to run `mmc extcsd read /dev/mmcblk1`, which shows that the emmc life time estimation is between 0 and 10%, but since this value is in 10% increments, its not very helpful. I've had issues with the default ramlog-based /var/log, so I had to turn it off. I've increased the size to 250MB but it regularly fills up b…

Hello everyone, If anyone would like to have a helios64 without having to wait for the next batch, mine is for sale. This is the complete bundle, it's in very good condition. I will post pictures very soon. I live in France, it would be better if you are in Europe so that the shipping costs remain reasonable...

hi, I am running newest armbian for NEO3. I've noticed that when I issue poweroff command armbian shuts down correctly, but the CPU (with heatsink) remains hot. I left my board for 2 days in poweroff state and it remained 'warm' all the time. Is there something that can be done to put CPU to sleep before shutting down system (or some low power state) ?

My Helios64 is "far away" and I am afraid to change network configuration, because if I miss something I could lose connectivity to the box. I would like to attach COM-to-IP adapter so that I always had serial console available, but... what actually do I need? "Normal" com-to-ip adapter provides COM port. Helios64 has COM-in-USB. So...? How to convert Helios'es serial console to anything accessible via LAN?

I tried a lot few days to driver a 3.5" TFT(the display ic is ST7701S,touch ic is FT5316) MIPI DSI color display panel on Orange Pi 4 with kernel 5.10.y . but I unexpected found it worked on linux 4.4 legacy kernel ( but I don't want use legacy kernel ),that below: But on kernel 5.x have some serious error in dmesg: [ 6.135383] rockchip-drm display-subsystem: bound ff940000.hdmi (ops dw_hdmi_rockchip_ops [rockchipdrm]) [ 6.136150] rockchip-drm display-subsystem: bound ff960000.mipi (ops dw_mipi_dsi_rockchip_ops [rockchipdrm]) [ 6.405472] dw-mipi-dsi-rockchip ff960000.mipi: failed to write command FIFO [ 6.427829] dw-mipi-dsi-rockchip…

Hello Guys, I would like to have question maybe unwise but it's hard to find information about it. I would like to prevent somehow my Helios64 or it's power supply to minimize risk of fire. Do you have any propositions to minimize that risk? Thank you for your help in advance

Hi, I think I may have posted about this in a few places, but I'm not sure where most are looking to discuss helios64 issues. The problem I am having is that the fans do not turn at all. As per the wiki, I've tried setting fancontrol off, and checking that the pwm value goes to 255, which it does but still no movement. I am using the fans supplied in the kit. There is nothing obstructing the fans, and sometimes if I disconnect and reconnect them from the board they will twitch a bit, or spin for a short while (until the connector is fully down against the board), but nothing otherwise. I've also tried heating the cpu up to ~85C (e.g `cat /dev/rando…

I got the Helios64 and was running it from an external SD card so far since when I first installed it, the other options where not available, yet. I'm running openmediavault 5.5 (Armbian 20.11.6 Buster with Linux 5.9.14-rockchip64). Now, I wanted to move the system to a SSD and installed a "Crucial MX500 1TB CT1000MX500SSD4" according to https://wiki.kobol.io/helios64/m2/ Unfortunately, the SSD is not detected by the system, see output of dmesg below. For ata1, it only shows SATA link down. Is there anything I can do to figure out what the problem is? Or is there any reason why this particular SSD would not work? ~$ dmesg | grep ata [ 0.000000] M…

Hi, I have major issues with my helios64 / ZFS setup - maybe anyone can give me a good hint. I'm running the following system: Linux helios64 5.9.14-rockchip64 #20.11.4 SMP PREEMPT Tue Dec 15 08:52:20 CET 2020 aarch64 GNU/Linux I have a three WD 4TB Plus disk - on each disk is encrypted with luks. The three encrypted disks are bundled into a raidz1 zpool "archive" using zfs. Basically this setup works pretty good, but with rather high disc usage, e.g. during a scrub, the whole pool degrades due to read / crc errors. As example: zpool status -x pool: archive state: DEGRADED status: One or more devices are faulted in response to persisten…

Hello I was finishing setting up my Helios64 (system installed on emmc) with Openmediavault (luks + snapraid + mergerfs + samba) on 3 disks, everything was working and I thought I should reboot to make sure that it is indeed the case (especially making sure that luks locked disks would not be an issue). An what a surprise, after booting up I couldn't ssh in so I connect the serial to log in as root. It seems that all services are dead like below. # service ssh status ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enab Active: inactive (dead) Docs: man:sshd(8) man:sshd_co…

Anyone know a solution for this? Linux vlib2 5.9.14-rockchip64 #20.11.4 SMP PREEMPT Tue Dec 15 08:52:20 CET 2020 aarch64 aarch64 aarch64 GNU/Linux Jan 08 14:27:05 vlib2 systemd[2481]: Starting Timed resync... Jan 08 14:27:05 vlib2 profile-sync-daemon[11324]: WARNING: Do not call /usr/bin/profile-sync-daemon as root. Jan 08 14:27:05 vlib2 systemd[2481]: psd-resync.service: Main process exited, code=exited, status=1/FAILURE Jan 08 14:27:05 vlib2 systemd[2481]: psd-resync.service: Failed with result 'exit-code'. Jan 08 14:27:05 vlib2 systemd[2481]: Failed to start Timed resync.

I know that WOL is currently not supported from the thread in kernel 5.x However, the specs of Helios64 showed and still shows that the interfaces have WOL support: * https://wiki.kobol.io/helios64/intro/#board * https://kobol.io under Multi-Gigabit Ethernet section What is missing ? How can we help ?

Hi All, since i had many problem with my old OPI R1 (without PLUS) I just ordered the newer Model with 1 Gig Ram, RK3328 CPU and two Gigabit Ports. There Is a debian Image available on their Google Drive Share right now, I'll certainly try that out, but Is there a generic Armbian Image as well, I can take? Should be pretty straigt forward Device, I tink.... HDMI Out is not available, only USB Gigabit Ethernet and Rockchip Gigabit Ethernet. Would be great if Hardware encryption for IPSec is also availaibe. Any thoughts? Cheers Ford Prefect

My plan is as follows: - Insert SD card. - Make a clone / back-up of boot and system using armbian-config whenever I'm about to do something major. (boot and system are both on eMMC) - "unclick" SD card and leave it in the back. - (repeat, until something breaks, and then just insert it and restore using armbian-config if something goes wrong.) I am confused by the eMMC to SD card path though. Here's some context: ❯ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:0 0 86.6M 1 loop /snap/core/10578 loop1 7:1 0 178.2M 1 loop /snap/microk8s/1866 loop2 7:2 0 86.6M 1 loop /s…

Hi! Does anyone have experience comparing ZFS performance on different operating systems on the same hardware. It is very interesting to compare the performance on FreeBSD and Linux.

Had anyone tested DAS mode performance with Capture One? Or could someone explain to me how it works? Also, would C1 show the DAS mode and NAS mode as seperate volumes or is it smart enough to show up as the same one? Background: Capture One doesn't work well with network drives. Editing images, moving raw files, even saving catalog backups is dramatically slower on a NAS than a DAS or internal drive. It doesn't matter how fast the drive or network is. Its a long standing bug they're always quick to say they aren't prioritizing fixing. I've looked at other NAS's that do a DAS mode by running a 10GBE connection over thunderbolt and that's a great solution in ev…

Hello I'm running a Plex server on my Helios64 and when I turn on subtitles it buffers every other second making the movie unwatchable. Is this a known issue with a fix? Sincerely Magnus Nygren

Hi. My helios64 always crashes with this method : [environment] 1TB m.2 sata ssd for system 16TB seagate exos on data drive 18TB WD Ultrastar DC550 on data drive Linux helios64 5.9.14-rockchip64 #20.11.4 SMP PREEMPT Tue Dec 15 08:52:20 CET 2020 aarch64 aarch64 aarch64 GNU/Linux about 620,000 files on data drive. [method1] #sync #sysctl -w vm.drop.caches = 3 #ls -CFR [datadir] > [tmp dir] #ls -1lFR [datadir] > [tmp dir] #zip -j [tmpdir] filelist.zip #sync >>>>>>> Crash (blinking Red LED) [method2] (First step) via…

Hi Guys, i'm selling my helios64. No harddisks and 2 Adapter for 2,5 zoll included. Possible shipping in Europe with insurance. Please send me DMs Pics comes later... Greetings Daniel

Hi all, Happy New year! I have a 7" IPS 1024X600 touch screen that I finally got it to work on Raspberry PI with the following configuration: hdmi_cvt:1=1024 600 60 3 0 0 0 # uncomment to force a specific HDMI mode (this will force VGA) hdmi_group:1=2 hdmi_mode:1=87 hdmi_drive:1=2 The product link is here: https://www.amazon.com/dp/B07VNX4ZWY/ When I plug this item into Armbian, the screen just flashes ON and OFF, but for some reason, the login screen works with about 1" black border on either side. When I type in log in password, the screen starts flashing again. I tried cvt 1024 600 60, but nothing c…

is there any way to send audio through displayport? i installed kodi, just as a database updater, but it fills the log with errors related to the audio system, and i see that aplay doesn't show any audio device, so another question is, is there any way to emulate an audio device? thanks

I have installed OMV via armbian-config (software). After that I tried to install Nextcloud the same way. In the process I noticed that Apache2 does not start due to a port mismatch (port 80). I was able to determine that obviously the web server nginx is already installed and used for OMV. Can someone please explain to me if this is intentional or if I made a mistake during the installation? Is it possible not to install OMV and Nextcloud in parallel? How can I solve this?

I've been watching! Whether to sell in China? When will the next batch be pre-ordered?

ok, so my flaming new helios finally arrived (after Christmas, what a pity) and, after spending some time assembling it (it's not the easiest thing in the world, expecially if you want to attach the mainboard BEFORE connecting all the cables, as specified within the instructions) I started configuring it. As i don't like the easy way (I'd have bought something else, if i would have) I went for a daily build with Groovy (i don't need OMV for my purpose and am quite accostumed to the ubuntu way), and the first thing i did was to make it a rolling release, putting devel in the place of groovy in sources.list, so that now i run hirsute (even if with a groovy userspace, a…

I have nfs server. Whenever I do "systemctl stop nfs-kernel-server" I can see this in dmesg: lockd: couldn't shutdown host module for net f00000a1! Later when I do "systemctl start nfs-kernel-server" I see this: NFSD: starting 90-second grace period (net f00000a1) Of course "systemctl restart" gives me both messages in a row. Any idea what does it mean? What the hell is this "f00000a1"? Except strange messages everything seems to work fine...

It is my first RockPi 4 board and first Armbian install - board working OK with official Radxa image (Debian 9) and eMMC drive. Since my plan is to use just CLI I'm trying to install Armbian Buster images. Unforunately both "current" and "legacy" versions are not booting up. I have used SDFormatter (just in case) and Balena (as usual) on 16B Transcend Premim and 32GB SanDisk Ultra (A1) cards - same result: board is powered on but nothing happened at all. Only green diode is lighting but no signs from SD card (red diode is not showing up). eMMC card not connected in both cases. I have checked other topics (i.e. ROCK64) but can not find a good solution how to proceed -…

Hi, i have successfully installed my new helios64 and enabled zfs. Everythings works so far, but it seems I'm missing something "important" in regards to ZFS. I did the following tests: I took one of my WD 4TB Plus drives (in slot 3) and formatted the disk with a) ext4 (mkfs.ext4 /dev/sdc) b) btrfs (mkfs.btrfs /dev/sdc) and c) zfs (zpool create test /dev/sdc). Based on these 3 formats I did a "dd if=/dev/zero of=test2.bin bs=1GB count=5" to measure write performance and a "dd if=test2.bin of=/dev/null" to get the read performance (all tests were done 3 times, results averaged) The results I got look like this: a) ext4 ...…

Are there any plans to offer a 2-bay version of Helias64? Whould it be possible to purchase the board only - without case?

Hello Guys, i'm positiv with Corona and in quaratine in my sleeping room while the rest of the family stays in the other rooms. So i can't backup my system with the MicroSD-Card... Can i install the latest updates? 20.11.4? And the other stuff showing? armbian-config/buster,buster 20.11.4 all [aktualisierbar von: 20.11.3] linux-buster-root-current-helios64/buster 20.11.4 arm64 [aktualisierbar von: 20.11.3] linux-dtb-current-rockchip64/buster 20.11.4 arm64 [aktualisierbar von: 20.11.3] linux-image-current-rockchip64/buster 20.11.4 arm64 [aktualisierbar von: 20.11.3] linux-u-boot-helios64-current/buster 20.11.4 arm64 [aktualisierbar von: 2…

Hello, i have a litte problem with my armbian/helios. I use a usb hdd for "backup" (snapraid parity) that only need to run every 2 days so that i unmount the drive and put this in standby (hdparm -y /dev) All goes well but after some time the drive awake again (without mount) and i dont know how i can prefent this. does anyone have an idea where I can look thanks for help.

Greetings everyone, I am new to the forum. I have recently completed an initial boot of Armbian 20.11.3 (stable) which appeas to be Debian Buster under the skin. I have a Sabrent 256GB NVME ready to go (works on other Rk3399 boards and my Pinebook Pro). I am booting from a 64GB uSD card. Using Armbian-config, I was able to update my board's SPI u-boot to mainline and rebooted to confirm I didn't mangle the SPI. The next step was to run the nand-sata-install.sh script to get it to copy the root and boot filesystems onto the NVME drive. While everything has worked so far and I copied the latest nand-sata-install.sh script from Github yesterday (when…

Hello, With the new version for rockpi 4 (Buster Kernel 5.X). I put in my armbianEnv.txt: overlays=uart2 console=display my ttyS2 has a very weird permission compared to other, (on the other hand I don't have this problem at all on a 4.X kernel) crw-rw---- 1 root dialout 4, 64 Dec 23 14:00 /dev/ttyS0 crw-rw---- 1 root dialout 4, 65 Dec 23 14:00 /dev/ttyS1 crw--w---- 1 root tty 4, 66 Dec 23 14:01 /dev/ttyS2 crw-rw---- 1 root dialout 4, 67 Dec 23 14:00 /dev/ttyS3 crw-rw---- 1 root dialout 4, 68 Dec 23 14:00 /dev/ttyS4 crw-rw---- 1 root dialout 4, 69 Dec 23 14:00 /dev/ttyS5 crw-rw---- 1 root dialout 4, 70 Dec 23 14:00 /dev/tt…

I have just put my Helios64 into operation. I have 5 HDD with 10TB each. Three HDD I mounted with ZFS (0.86) to a raidz1. the other two disks I mounted individually, formatting one disk with XFS and the last disk already had NTFS as filesystem. On this disk (NTFS) I have some very large *.vhdx files which I only use for copy tests. I use the console with the Mitnight Commander for this. The copying from the NTFS disk to the XFS disk reached a speed of about 130 MB/s. Copying from the XFS disk to the ZFS raid reached a speed of about 100 - 110 MB/s. I cannot do anything with these values alone. Can someone please tell me if these speeds fi…

Good day, I'm looking for help adding touchscreen support to the ROCKPI 4 Legacy Kernel and correct screen configuration settings. Im new to SBC development so I'm still learning the build system. I have taken the time to track down, what I believe, are the commits to add basic support for the "Raspberry Pi 7" Touchscreen" to the kernel. I believe their will be changes needed to rootfs so that the display manager recognizes it and sets it up properly. ARMBIAN_BUILD_BRANCH: Legacy Kernel --> https://github.com/ayufan-rock64/linux-kernel/tree/release-4.4.202 RADXA_BUILD_BRANCH: Kernel --> https://github.com/radxa/kernel/releases/tag/4.4.154-110-rock…

I’m helping my friend set up Helios64 with OpenMediaVault as a media server. We’d manage to set it up as per your documentation mentioned on your wiki page but are stuck on SD-Card to eMMC migration. As after migrating with no error so far we’re still unable to boot the system without the SD-Card in Helios64. We still couldn’t figure out what could be the problem? Can you guys help?

is it intended to integrate openzfs-2.0.0 and if so, is the timing already known?

Focal / root on eMMC / ZFS on hdd / LXD / Docker I received my Helios64 yesterday, installed the system, and decided to write down my steps before I forget them. Maybe someone will be interested. :-) Preparation: Assembly your box as described here. Download Armbian Focal image from here and flash it to SD card. You may use Ether. Insert the SD card to your Helios64 and boot. After 15-20s the box should be accessible via ssh. (Of course you have to find out it's IP address somehow. For example check your router logs or use this.) First login: ssh root@IP Password: 1234 After prompt - change passw…

Setup: Helios64 with Armbian 20.08.8 Buster with Linux 4.4.213-rk3399. Will change to Linux 5.8 soon though. 5 x 8 TB drives. Not using battery. I’ve had this issue ever since beginning to use my Helios. It first happened when I tried building a RAID with OpenMediaVault: It would crash and reboot while building. Sometimes after only 10 minutes, sometimes after 8+ hours of working. The same is true for video transcoding nowadays: it will sometimes crash after a little while, sometimes after a few consecutive hours of working, but it will never be able to work much longer than 12 hours on such a task. Copying large files from the internet has a similar risk of c…

I don't know if it's of any use. Just noticed this issue of reboot not working on Buster legacy. Seems to be hdmi related. When I pull out hdmi for a few seconds then it does start booting. I remember this used to be the same on bionic mainline. Don't know why it's here now. I'm on NanoPi M4V2.

Anybody have an idea what these message being written to dmesg?! Linux Hell64 5.9.11-rockchip64 #20.11.1 SMP PREEMPT Fri Nov 27 21:59:08 CET 2020 aarch64 GNU/Linux -snip- [Wed Dec 9 04:37:51 2020] NOHZ: local_softirq_pending 08 [Wed Dec 16 22:54:43 2020] NOHZ: local_softirq_pending 08 [Thu Dec 17 02:35:38 2020] NOHZ: local_softirq_pending 08 Anything to be alarmed about?

My NAS do very little overnight so my NAS4 shuts down in the evening and shortly afterwards a physical time switch cuts the power - reinstating power in the morning at which time the NAS4 automatically reboots. I want to do the same with the NAS64 - but even though I've read this (https://wiki.kobol.io/helios64/auto_poweron/) I'm not sure how to go about it. I can't understand if it only works if the UPS has died, or if I have to run a script before shutdown or both. Could you please clarify? Thx ... Nick

Hi!, I am playing around with customizing my boot script (to install later my custom distro), and I am fighting with the Recovery. I took a long time to understand I have to press the recovery button during a "long time", then release it very quickly to get the UMS mode and not falling into the Maskrom mode. Indeed, when U-Boot detects the recovery button keypress, it proposes UMS, then very shortly after the Maskrom mode. Is it possible to configure U-Boot to wait longer on the UMS mode, let's say 5 seconds, and after that delay switch to Maskrom mode as latest failover? For info: I have Armbian running on EMMC, and I…

To try the new goodies I've tried to install Buster Legacy on my M4V2 but it always hung on [---] A start job is running for Bluetooth Rockpi (many minutes / no limit) https://redirect.armbian.com/region/EU/nanopim4v2/Buster_legacy_desktop I downloaded it multiple times and no change. I'll try the mainline image and then regress kernel to legacy.

Hello everyone, I've been running my Helios64 for about 2 months now. My system is installed on the eMMC and i'm running a few docker containers (all from linuxserver.io) Radarr Sonarr Bazarr Transmission Jackett Jellyfin I'm having difficulties with Jellyfin and my media library. When lauching tv shows or movies, the CPU rockets to ~97-99% use and the media is constantly stopping to load. I would like to know what I can do to ease the strain on the CPU and be finally able to use Jellyfin. Has anyone been able to use hardware acceleration with docker ? What info can I give you to shade li…

Hello! I have OrangePi4 and it works quite well out of the box with Armbian desktop latest. However there were some minor problems, this is the first one: Video resolution was incorrect by default in console framebuffer. The screen is 1920x1080, but default was 1280x720. The solution is adding extraargs=video=1920x1080@60 To /boot/armbianEnv.txt . The part after first = is passed to the Kernel command line and kernel enables the resolution. This have fixed my problem mostly, however, the video output is enabled only during late boot. This is not a big problem, but it would be better if the screen lit up immediately after the computer is powere…

IT'S FINALLY HERE... THE OFFICIAL ROCKCHIP-LEGACY MULTIMEDIA INTEGRATION After two years of using a separate script to enable the multimedia features in RK3399 Legacy Kernel, the whole framework has been incorporated to the official Armbian packaging system. The choice distro for this integration is Debian Buster (see FAQ at the end of this post about the reasons). I. Installation Download a Armbian Buster Legacy Desktop image for your board, and install it with the standard Armbian method. Install the complete multimedia solution with sudo apt update && sudo apt upgrade sudo apt install media-buster-legacy-rk33…

I got my box yesterday and assembled it (looks gorgeous, and reasonably easy to assemble). Without external power and with battery connected, green led 1 is on. With external power, orange led 9 in addition to that. FTDI chip is recognized regardless of power status, I can connect to the console. After pressing power button, green LEDs 2 and 3 and blue LEDs 4 and 5 light up immediately, and after that nothing else happens. Nothing on the serial console, no LEDs change status. Tried disconnecting the battery. Then without external power, all LEDs are dark (but FTDI chip is still visible), with external power orange LED 9 blinks, the rest is exactly the …

Hi there, So I'm having a problem connecting the helios to the router. I try different lan cables and different ports. It was working everything fine yesterday, I did a reboot and no more connection. I'm completely new to this. I was installing home assistance and plex before this happened but I believe I didn't mess with anything to do with network. Don't know what I might have done. I can connect to helios via putty and after logging in the part where ip should be there is none. Any advise would be most appreciated. Again I'm completely new to this.

Hello, Sorry for my bad english, I'm French, I'm using "Armbian_20.11.4_Helios64_buster_current_5.9.14.img.xz" During the startup sequence I get the following errors: GPT 0x3380ec0 signature is wrong recovery gpt... GPT 0x3380ec0 signature is wrong recovery gpt fail! LoadTrust Addr:0x4000 No find bl30.bin No find bl32.bin Load uboot, ReadLba = 2000 Load OK, addr=0x200000, size=0xdd6b0 RunBL31 0x40000 NOTICE: BL31: v1.3(debug):42583b6 NOTICE: BL31: Built : 07:55:13, Oct 15 2019 NOTICE: BL31: Rockchip release version: v1.1 INFO: GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3 …

Hi, I bought a 2-pin piezo buzzer to use for alarm messages. It is connected to the P4 header on the board. When I execute the "beep" command in the console I only get short click noises. Are special kernel drivers necessary for a correct function?

Thank you for sharing the link. Inspired me to write an overlay for my NanoPC-T4. Now I can attach an additional monitor via my Delock 63959 USB-C to VGA / HDMI / DVI / DisplayPort Adapter with 5.10.0.

I followed in detail the installation tutorial but I'm stuck at the installation of OMV. I can't access after the installation using the ip address or the generic link helios.local. I did try to reinstall the configuration. To go through a boot on the Micro SD... I don't know if there would be a command line to verify that OMV is installed? Or another way to install it?

After installing the hardware and software, my hdd 1 is inactive. I swapped my disk 1 and 5, 1 is still inactive. I checked my connections in the box but I don't see any problems. Could this be due to a software error?

Hello, I recently updated my Helios64 board from 5.9.11 to 5.9.14 using `apt upgrade` and since then I'm unable to boot my board which is stuck on `Starting kernel ...`. Here is the log of the what got upgraded. Spoiler shepard@helios64's password: _ _ _ _ __ _ _ | | | | ___| (_) ___ ___ / /_ | || | | |_| |/ _ \ | |/ _ \/ __| '_ \| || |_ | _ | __/ | | (_) \__ \ (_) |__ _| |_| |_|\___|_|_|\___/|___/\___/ |_| Welcome to Armbian 20.11.1 Buster with Linux 5.9.11-rockchip64 No end-user support: work in progress System load: 2% Up time: 14 days 13:18 Memory usage: 14% of 3.71G Zram usage:…

After upgrade to Armbian 20.11.3 Buster with Linux 5.9.14-rockchip64 eth1 has vanished. ❯ sudo ip link show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000 link/ether 64:62:66:d0:06:18 brd ff:ff:ff:ff:ff:ff Any ideas? http://ix.io/2I2U

Few days ago i saw an issue after i added rule to auto-reboot device once a day, every time it's reboot it's losses connection with sata hat - no more sata controler after typing "lspci" and some nasty output after "dmesg | grep pcie". I tried reboot manually, when i reboot just after powering on (like up to 2 min), pcie goes back up and there is no issue, but if device stay on for longer and i reboot it then there is pcie training issue and mervell sata controller don't get recognized anymore, further rebooting don't fix the problem, i even tried to connect drives power straight through SATA Hat, but it had changed nothing. The only fix is to shutdown device instead …

I have an Orange Pi 4B. The board as the only USB 3.0 port has the USB-C type. I connect the USB-C x USB-A adapter. I connect the USB flash drive and it doesn't work. Power from the port is coming out properly. Is there any chance that this port will work properly with an external drive?

HI all I just received my Helios64 and built it this weekend. I followed the instruction and everything was going well. After installing OMV i tried to access it via the network and realised that my unit wasnt connecting over lan. I have tried both ports on the back and i am unable to connect just get the flashing orange light (no green light). I have tried using different cable and different ports on the router, a network restart, system restart but noting. If anyone can offer a suggestion of what else to try it would be appreciated.

In both Buster and Focal 20.11.1 on helios64 commands directed to a disk increment fields in /proc/diskstats This is incorrect and does not occur in the x86 version of xubuntu Focal. Specifically (see https://www.kernel.org/doc/Documentation/iostats.txt for field descriptions.): Check Power Mode increments "number of reads completed" Smart Return Status, Smart Read Data, and Smart Read Log increment "number of reads completed" and "number of sectors read" The smartd disk monitor uses these commands which makes the disk appear to be active to programs like hd-idle. I hope this is the correct place to report this bug. …

My Helios64 has been running without issue for quite a while -- at least a month. Now -- no power. Last logs on the SD card looked to be early in the morning yesterday. D9 is solid amber with battery, flashing without. No other LEDs on the board are illuminated. I've removed from the case and disconnected the previously attached drives just in case. On initial power the fans spin briefly and then ... nothing further. I've tapped and held various combinations of power and reset, etc -- no change. Can confirm with a voltmeter the original supply is making +12v. Can confirm a separate known working ATX supply on J10 has a constant +12V and …

I'm using Armbian 20.11.1 Focal (5.9.11-rockchip64) on my Helios64. When there's heavier load via ethernet (SFTP to a SATA Ultrastar 12TB disk) for something like more than an hour, the entire system will freeze. Not sure if it actually does freeze but I lose all SSH connections and cannot connect anymore via SSH unless I restart the Helios64. Happened today 4 times and it's totally reproducible. Haven't tested another drive yet. What makes this difficult to debug is that under /var/log/syslog or kern.log or faillog nothing relevant is being written as to in what state the device is. Is this a known issue? How can I find out what the problem i…

What is the current pcie link speed set for stable Armbian 5.9.x release? I know stock kernels from orange pi have it set to Gen 1 speed. Need to test some Gen 2 hardware and see if it works.

Dear Forum! If you are using Emmc as boot device, a M.2-ssd as system device and OMV is installed. You can backup with the OMV given image-backup (dd, fsarchiver). But how you can restore the backup? You need to boot from Sdcard (boot and system from sd)? And after that you can switch again back to emmc-boot and ssd-system without any issue? Is there any other easier way i.e. with CloneZilla to image-backup/restore? How you can do this?