Rockchip

I'm trying to get desktop showing thru USB-C connector with appropriate usb-c to hdmi cable. I don't find errors in Xorg.0.log, but still I get no signal to my TV. I've installed desktop via armbian-config. Never done USB-C to any display, so I think I need some pointers to debug and get it to work... Did not find howtos or alike.

If anyone in the US is looking for a Helios64 but don't want to wait for the next batch, I'm prolly selling mine. I ended up using an older windows desktop to build a server; took all of an hour to set up. I wanted to use this because it uses a lot less power and I wanted the computer for another project, but I don't have the time to screw with it trying to get it to actually function. If no one wants it, I'm just going to strip the case down as a HDD enclosure and cut my losses.

Object: Enable OTG serial console capability( It was enabled by default I think ) What I was checked/tested: g_serial on /etc/modules ttyGS0 on /etc/securetty serial-getty@ttyGS0.service enabled dwc3-0-host enabled/disabled Windows 10 1809 host g_serial recognized R2S as 0525:A4A7(rev0509) Behavior: OrangePi-Zero: Works well( g_serial recognized as same VID/PID but rev0419 ) <== There are no problems on Windows host driver or configurations[ELMO GMAS(5/4/2014, v2.0.0.1) / usbser.sys(v10.0.17763.1)] NanoPi-R2S: Connection fail. Even manual configure 9600 through 115200 bauds. => Putty alerts few m…

I've got my helios64 recently, and I wonder what type of FS to choose for main storage. I have five 4TB disk drives. I've installed OMV, made raid5 and format it with XFS. I use XFS because I work with this FS on Centos on my x86 servers, I don't use ext4 because I don't like when sometimes it starts to check filesystem during boot process. My setup is working perfect for a couple of weeks. I don't have any reboots or freezes or any issues that I've read on this forum. Now I think about migrating from XFS to BTRFS or ZFS. The main reason is to have file check-summing and scrub. Does anybody have btrfs with raid5 or ZFS with raidz1 on Helios64? Do you have any problems wit…

If anyone is interested, I've created a shell script that can be run with cron to check A/C and battery status, and do a graceful shutdown when a battery threshold is met. It also logs power outages, battery drain when off A/C, and when it posts a shutdown (if any). This is a simple script, nothing fancy, but works for me. It has a granularity of one minute (cron is limited to one minute intervals), but I've been able to keep the system up on heavy load for 4-5 minutes before the script generates a shutdown on low battery. The script is generous -- it waits for 916mV or less before a shut-down. This value was provided by the KOBOL team on their Wiki as the…

Last FriendlyElec nanopi-r2s image has hardware rng, what about adding it to Armbian? For my nanopi-r2s I patched dtb, compiled kernel module with dkms and managed to make it work with rngd. Amount of enthropy increased from ~2000 with haveged/jitterenthropy to ~4000. The only problem is FIPS failures so I had to run rngd with --ignorefail flag. Here is links to FE github: https://github.com/friendlyarm/kernel-rockchip/blob/2ea3d37e1de559b9af2cd24a71bb538dddc1365a/arch/arm64/boot/dts/rockchip/rk3328.dtsi#L250-L259 https://github.com/friendlyarm/kernel-rockchip/blob/2ea3d37e1de559b9af2cd24a71bb538dddc1365a/arch/arm64/boot/dts/rockchip/rk3328-nanopi-…

I ran the 5.8/5.9 kernel for weeks without any issues (no RAM unstability, no crash, no ethernet issue). Now I reinstalled the thing and came back to a 4.4 kernel to have USB-C support. The thing is… Once every hours, the 1GBps Ethernet disconnects. Once connected through serial port, I can check the port status and it's shown as `Unknown`. I can `ip link set down eth0; ip link set up eth0` to set it back up. Am I the only one with this issue ? Is it well known on 4.4 and solved on 5.9 ?

Hello, I received my Helios NAS last week, I installed armbian on eMMC with no issues. But I have a issue with my ssd and hdd. When I plug in my 5 HDD + my SSD, I only see 4 HDD ... But when I remove my SSD I can see the 5 HDDs ... So my question is stupid but it's "normal" ? I have a doubt, there is not a limitation with the GPT?

hi, i have only one fan that spin, i have set the systemctl stop fancontrol and checked the pwm1 the value is 255, and only one who spin i can turn off the only fan spinning with value 0, but i can't control the seconds fan at all, i have verified the connectique on the board and everything is fine, when i opened it and checked without disk , and i saw that both fan was spinning, so i thought it was fine, when i closed the board and disk's are on, i again have the same issue, i can control only 1 fan, it's always the same one. any idea how to fix this issue? is it a software related?

I built a version of Buster with the legacy kernel (4.4). when I try to install the media-buster-legacy-rk3328 package on the system, I get an error - unsatisfied dependencies on the kodi-rk package. I tried installing the Kodi-rk package manually, but it has an unsatisfied dependency on kodi-rk-bin. The kodi-rk-bin package is available and installed, but its version does not correspond to the links with Kodi-rk. Perhaps packages were updated in the repository, but dependencies do not work because of a complex package name (the alphabetical comparison condition is not met) ?

After dist-upgrade, I got seg fault when using wget. Spoiler root@nanopi-r2s:~/lepup# cat /etc/debian_version 10.6 root@nanopi-r2s:~/# uname -a Linux nanopi-r2s 5.9.11-rockchip64 #20.11.1 SMP PREEMPT Fri Nov 27 21:59:08 CET 2020 aarch64 GNU/Linux root@nanopi-r2s:~/# apt-get install wget Reading package lists... Done Building dependency tree Reading state information... Done wget is already the newest version (1.20.1-1.1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root@nanopi-r2s:~/# strace -o /tmp/wget.tr wget Segmentation fault root@nanopi-r2s:~/# cat /tmp/wget.tr execve("/usr/bin/wget", ["wget"], 0xffffcfbd4160 /* 23 vars */)…

Hello, When I comment device via USB 3.0 I see it: ender3@ender3:~$ lsusb Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 004 Device 002: ID 1d50:614e OpenMoko, Inc. Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub However with pins GND, DP1, DM1, +5V Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID …

Hi What is the appropriate method to upgrade to a new release (20.11) without reimaging the SD card? I have not attempted this before as I have mainly used Ubuntu which provides sudo do-release-upgrade Note I am not using a VM or Docker. Can I upgrade the kernel using the downloaded Helios64 image? sudo apt install ./linux-image-<flavour> Is there a way to do it using armbian-config (like there is for raspi-config) Or do I need to download the armbian source and then compile ./compile.sh

Hi all, Something to share for those who use the USB-C serial console from another Linux host. Install and use 'tio' to connect to the serial console instead of minicom. This supports both 1500k baud and also can be easily used inside GNU screen (minicom gets a meta key conflict per default; CTRL-A is default meta key for both GNU screen and minicom). Minicom resulted in regular errors posted in syslog by the ftdi_sio kernel module. Did not run any strace to find out what syscall is causing it, but in short, tio appears to not treat the tty as a modem: no errors are popping up in syslog. Hopefully the serial consoles will remain up now. One caveat: I did not fin…

I have the Helios with two 10T disks mounted as a BTRFS raid 1 array. This setup is stable, although I have not stressed it a lot, except for when I do a btrfs scrub. It is using the 20.11.1 Buster image on SDcard. The disks have about 900GB of files. A btrfs scrub causes a crash with the following kernel output. Is this a known bug? Spoiler [351424.849687] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP [351424.850193] Modules linked in: rfkill governor_performance r8152 zstd snd_soc_hdmi_codec snd_soc_rockchip_i2s hantro_vpu(C) snd_soc_core rockchip_vdec(C) leds_pwm v4l2_h264 panfrost rockchip_rga snd_pcm_dmaengine videobuf2_dma_contig s…

hello, while i am copy files on my server and start 1 or 2 torrent i see that my memory gett less. Yes thats only buffer and caches but he eat faster then he get free so that he starts swapping (what cost cpu and speed) a litte search and i see that cat > /proc/sys/vm/swappiness is 100 and look on my other systems it is set to 60 now woth change this value he dont start swapping and free up faster the memory. can someone explane me why this here is set to 100? thank you

Hello, good morning from Spain. My sincere congratulations to the Kobol and Helios64 team. A really good and well designed product. I have a question about the compatibility of a hard drive with the Helios64 NAS. My hard drive is ---> https://www.senetic.es/product/0F38459 <--- ( Wd Ultrastar 18TB) With a capacity of 18TB, my question is: Is that hard drive (18TB) compatible with the Nas Helios64? I think that in the Nas Helios64 technical description, it only accepts a maximum capacity of 16 Tb hard drives Thank you very much for the information and help.

We are facing some issue while interfacing 5" MIPI display to RK3399.

Hi I try ro install and use Armbian on my NanoPi NEO 3. But when I do a first boot, I stuck at Generate Locale step. How can I fix it? Thank you very much. .

During installing Helios64 with the latest image I experienced several times that the system did not come up. Now that it is fully installed with OMV enabled, I sometimes do a reboot, and the system does not come up. Unfortunately I cannot see anything on the console level (on MacOS). After pressing the reboot button (around one or two times) the system comes up as nothing happened ever. What can I do to have the system reboot in a stable manner? Since it will sit in the basement soon, I don't want to run down every time I see that it does not reboot properly.

Hi, I run Armbian Buster 20.11.1 and today, without any important network traffic, eth1 interface has crashed. Here is dmesg : After ifdown & ifup eth1, interface is up again. What's wrong ? I can see driver 2.13 is used, and Realtek has issued a 2.14 version, but only usable up to 5.6 kernel So I can't compile it.

Hello, I am quite new to this topic, and I have found it to be quite complex. I primarily work with tiny MCUs and RTOSes, but I am enjoying the Linux space so far. In essence I would like to use the Mali GPU that is embedded within the RK3399 of the Helios64 for hardware transcoding. This isn't a novel idea, as shown by these sources: https://forum.armbian.com/topic/9272-development-rk3399-media-script/ https://emby.media/community/index.php?/topic/66675-36078-transcoding-rockpro64/ I am using Jellying, and in so FFMPEG to decode/encode the data streams. It seems that V4L2 is supported for hardware ecoding/decoding in the FFMPEG p…

I've been trying to get OMV setup on the Helios prior to adding my hard drives and I keep getting errors and communication failures when I try to do pretty much anything. I like OMV for it's GUI, but honestly, I've never been a fan of it functionally. Is there anything comparable to it that works with the Helios64? Anyone have any suggestions how to fix it? I have logs but I don't see a place to attach them.

Hi, Not sure if anyone has seen the same as I have been seen on my box; the HDD status LEDs are cycling in brightness, from 0% to 100% and back to 0% continuously. It's a smooth transition, no flashy circus. I might have triggered this myself, but no idea how? Is this is a new feature? I tried to make some video of it, but it is quite difficult to see. Groetjes,

With Armbian v20.11 one can write mainline u-boot image to board's SPI and enjoy booting nvme drives without any mmc devices. Prerequisities: ROCK Pi 4(A/B/C) v1.4 or 1.3 with SPI soldered in (v1.3 comes without SPI flash from the factory). If you already have Radxa's u-boot written to SPI you need to short pins 23 and 25 for Armbian to boot Boot fresh image of Armbian v20.11.x for ROCK Pi 4(A/B/C) Add the following lines to /boot/armbianEnv.txt overlays=spi-jedec-nor param_spinor_spi_bus=1 Reboot If you shorted 23-25 pins in 1.) then: disconnect them after the ROCK Pi 4 fully boot's …

As stated in my comments here (but it seems no one is reading this blog post comments anymore ...) : https://blog.kobol.io/2020/10/27/helios64-software-issue/ - With 5.8.17 i have kernel panics. - With 5.8.14 i have freeze. So what to do in order to have a stable situation ?! It seems to be "under load" (one freeze during RAID array being built, and several ones (with .14 or .17 kernels) while files were being copied through the 1Gb/s network interface). - System newly installed and running on fresh SSD card. - 5*3.5" WD HDD plugged in / RAID5 mdadm array (so no M.2, ...) - nothin…

Some of you may be interested to not only store your data on Helios64 but to also run other services on it - such as home automation. One of the popular platforms for home automation in Europe - and in Germany in particular - is "Homematic". They opened up their ecosystem some time ago and allow others to implement their own components (some excellent examples from Jérôme are here). As of yesterday - with the latest commit - it is possible to run a virtualised "ccu3" base station for that platform, called pivccu, with support for a detached antenna module (RPI-RF-MOD) coupled to Helios64 (and Armbian 20.11 kernel 5.9.10) through a tcp/ip network using a dedic…

If you want the fans of your Helios64 to start spinning earlier, look no further. This will allow the fans to spin at a constant speed from the earliest stage of initrd until fancontrol is started by the system. My use-case is for full disk encryption and recovery in initramfs, sometimes I can have the machine powered on for quite a while before fancontrol starts. Or, if the boot process encounters an error the fans may never start, this prevents that. Step 1: Tell initramfs to include the pwm-fan module echo pwm-fan | sudo tee -a /etc/initramfs-tools/modules Step 2: Create a new file at /etc/initramfs-tools/scripts/init-top/fan with the followin…

Hi, I’m using the Helios64 with Armbian 20.11 Buster ( 5.9.10-rockchip64) On every reboot the SMART counter for “Unexpected_Power_Loss (174)” / “POR_Recovery_Count (235)” incresses by one. I’ve seen this unexpected behaviour on Samsung, WD and Crusical SSDs … Rebooting the box with sync && echo 1 > /sys/block/sdX/device/delete && reboot turns the disk friendly off, but shouldn’t this be done in systemd/kernel?

Last night we lost power to the whole house, I had to manually start the NAS and when I tried to access my data there was nothing but empty shares. After checking OpenMediaVault Web UI and checking around, the file system status shows as "missing" and there is nothing under RAID Management and all the disks show properly under Storage > Disks. The NAS is set up as a Raid 6 on ext4 with five 12 TB drives. For starters, I wonder why the internal battery did not graciously shut down Helios64 as to avoid this from happening given that power outages are a rather common issue. Then, how do I get my file system back? After browsing some for…

After the official release of Armbian 20.11 today I would like to collect feedback if and how the firmware runs on the Helios64. Is it possible to upgrade already or should we Helios64 owners wait? apt-get lists these already... armbian-config/buster,buster 20.11 all [upgradable from: 20.08.22] armbian-firmware/buster,buster 20.11 all [upgradable from: 20.08.22] libgssapi-krb5-2/stable,stable 1.17-3+deb10u1 arm64 [upgradable from: 1.17-3] libk5crypto3/stable,stable 1.17-3+deb10u1 arm64 [upgradable from: 1.17-3] libkrb5-3/stable,stable 1.17-3+deb10u1 arm64 [upgradable from: 1.17-3] libkrb5support0/stable,stable 1.17-3+deb10u1 arm64 [upgradable f…

My Helios64 was running fine with 5 HDDs for a couple of weeks, then I suddenly couldn't access the shares anymore and I noticed only two HDDs were running (the rest having no indicator lights). HDD slot 3, 4 and 5 appears "dead", no power up on boot, no indicator lights. I have checked both +12V and +5V rails and they are present, everything is plugged in. I can move the HDDs from slot 3, 4 and 5 to slot 1 and 2 and they will power up just fine. The hard drives also work in other machines. I'm a bit lost as to what might be wrong, any ideas?

Hey, I think a dedicated topic for ZFS on Helios 64 is needed. Many people want to have it As we know, and many of us playing with dev builds for helios ,it is no easy to work with ZFS I wrote few scripts maybe someone of You it can help in someway. Thanks @jbergler and @ShadowDance , I used your idea for complete it. The problem is with playing with OMV and ZFS plugin. then dependencies remove our latest version of ZFS. I tested. everything survived but ZFS is downgraded to latest version from repo for example: root@helios64:~# zfs --version zfs-0.8.4-2~bpo10+1 zfs-kmod-2.0.0-rc6 root@helios64:~# uname -…

Hi, I wanted to convert my root filesystem to btrfs. This allows me to use snapper to take regular snapshops. I also use btrbk to send my snapshots to my secondary storage (also a btrfs array). My root filesystems is installed to eMMC, but there isn't any reason you couldn't do this with an sd card. These instructions are done with a laptop running Linux. I'm using Debian in this case, although any distro with a recent kernel and btrfs tools installed should work. CAVEATS: The current u-boot image (2020.08.21) doesn't support booting natively to btrfs. u-boot *does* support btrfs though. Hopefully a future build of u-boot will add btrfs…

Just got the notification to update After the reboot all seems good - iSCSI is now supported out of the box. Will wait for the official images to be pushed to the downloads page to try and setup a clean install + overlay FS to document my customizations.

Hi folks, I got my helios64, assembled it during the weekend and can’t seem to actually install it. Here are some of the things I tried (I'm on windows 10 btw, I don’t have hdd drives yet, I assume this would not be an issue): · 2 sd cards (one of which is a Samsung as recommended in the wiki), two computers (with correct com ports as visible in the device manager, driver is installed), tried both on usb2 and usb3 · USB cable has been trimmed to fit the case properly - also tried with the back panel off and directly connected to the board · the devices starts up as soon as I plug in the power cord - I then use…

Hi, How can I catch the reset button pressed. In other words, how can I change the behavior of the reset button on RK3399?

Just getting around to trying to setup my Helios 64 and I am unable to get it to appear under either Windows or OSX. I have removed the back panel and ensured the USB cable and micro SD are fully seated. Nothing appears so I can't flash the image to the internal eMMC. I tried MaskRom mode but RKDevTools fails. It does the following steps: Download Boot Start Download Boot Success Wait for Maskrom Start Wait for Maskrom Success Test Device Start Test Device Fail Not sure where to go now as I can't get anything to work on it. Your help would be greatly appreciated.

I need help with two items. 1. When directly connect to my windows 10 pro pc i get the following in device manager. ft230x. Where can I download the drivers so i can use putty to connect to the helios64. 2. One of the fans is always spinning even when i shutdown with sudo shutdown -t now. Thanks

❯ sudo iperf3 -s ----------------------------------------------------------- Server listening on 5201 ----------------------------------------------------------- Accepted connection from 192.167.0.1, port 23497 [ 5] local 192.167.0.2 port 5201 connected to 192.167.0.1 port 23498 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 163 MBytes 1.37 Gbits/sec [ 5] 1.00-2.00 sec 149 MBytes 1.25 Gbits/sec [ 5] 2.00-3.00 sec 104 MBytes 868 Mbits/sec [ 5] 3.00-4.00 sec 141 MBytes 1.19 Gbits/sec [ 5] 4.00-5.00 sec 174 MBytes 1.46 Gbits/sec [ 5] 5.00-6.00 sec 125 MBytes 1.05 Gbits/sec [ 5] 6.00-7.00 sec 106 MByte…

I once had openmediavault (nas software) and citadel-server (groupware software) running together on an x86 computer with Debian operating system. When I try this on Helios64 running armbian (Debian 10 Buster) and kernel 5.8, then the package manager does not allow it. That means, when I start with an installed openmediavault and want then to install citadel-server as well the package manager removes openmediavault first. Does anybody have an idea or a solution to the problem?

So I got my Helios64 today, built it with 2 drives, a Adata SSD on the M.2 and 2 Seagates on SATA 1 and 2. But whenever I want to boot it up, the internal blue system LED lights up + System Rail power (UPS installed) with all activity LEDs and HDD error 3 instantly with no delay. There is no Console output and nothing is to be heard spinning up. When building I noticed the cable harness having the same length for connectors 2 and 3 where 3 is too short for zip tie-ing. Help is greatly appreciated.

Hello, Since few days, my PSU makes a high-pitched noise. As my NAS is installed in my living-room, it is annoying. I have changed my PSU three weeks ago, it was good during these three weeks, but it comes suddenly noisy... Does anyone else has the same issue ? And any ideas on how to fix this ? Thanks

Hi, I noticed that on my board I didn't have notification with MOTD when updates were available and I think that I've found the culprit: In the file /usr/lib/armbian/armbian-apt-updates of the package linux-buster-root-legacy-nanopim4_20.08.17_arm64.deb, this line stop the script to go further : # give up if packages are broken [[ ! $(dpkg -l | grep ^..r) ]] && exit 0 If I remove the ! then it works (because the script, in fact, gives up if packages are not broken )

I just received my Helios64 system and built it today. The build included 3 drives, a SSD in port 1 and two HHD's on port 2 and 3. After the build, I installed Debian Kernel: 5.8 on an micro SD card. The system booted but only showed the drives in port 2 and 3. I have moved the drive in port 1 to port 4, rebooted and the SSD drive shows up. Also, a HDD in port 1 does not show up: no blue Light on the front panel and not visible in "fdisk -l" . The output from ' dmesg | grep "ata" ' results in: Spoiler [ 0.000000] Memory: 3742212K/4061184K available (14460K kernel code, 2114K rwdata, 5920K rodata, 4160K init, 572K bss, 187900K reserved, 131072K …

I just received my Helios64, I immediately checked it for the Magjack center point to ground concern, and mine tests that it is connected. Is there a revision number on the board which can be used to identify the clean point between the pre and post fix boards?

Hello, When it's planned the support of wakeonlan? I want to keep my nas powered off, and power it trough a raspberry pi when I need It. Do you think is planned on the next days or in the next mounths? Thanks

Linux Hell64 5.8.17-rockchip64 #20.08.21 SMP PREEMPT Sat Oct 31 08:22:59 CET 2020 aarch64 GNU/Linux I've been testing the performance and comparing to another NAS I have (WD PR4100) and the Helios64 performance has not been fairing well. Setup are almost identical on the same switch connected gig ethernet. Using SAMBA ,NO Raid. Testing with SATA drives HD's previously formatted for NTFS. and UAS USB 8 Bay DAS. Reading from Helios64 to Windows 10 PC I achieve expected 113MB/s and from USB attached to Helios 110MB/s. Writing speeds are very poor and as can be expected worse on the directly attached USB DAS. WIN10 -&gt…

Can you guys share your experience with disk sleep on the Helios64 + Armbian. In my case I haven't seen the disks sleep - they are always spinning (or so they seem) and never on standby. I have a standalone /dev/sda and a RAID5 array with disks /dev/sd[b-e] (created with mdadm) - and XFS formatted logical volumes on top of these. 'iotop' says that nothing is accessing the disks: 'hdparm -B /dev/sd[a-z]' after each reboot is always: sudo hdparm -B /dev/sd[a-e] /dev/sda: APM_level = 254 /dev/sdb: APM_level = off /dev/sdc: APM_level = off /dev/sdd: APM_level = off /dev/sde: APM_level = off 'hdparm -C /dev/sd[a-z]' …

I'm on the Ubuntu focal release for the Helios64: Kernel: 5.8.14-rockchip64 If I try transferring between the 2.5Gbps port and my computer, either linked at 2.5Gbps or 1Gbps, will unlink. I tried with a StarTech USB 3.0 port, linking at 1Gbps, and the same issue occurs, leading me to believe it's a software issue with the USB driver. lsusb -t, with the startech plugged in: root@helios64:/helios# lsusb -t /: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M /: Bus 03.Port 1: Dev 1, Class=r…

Getting system crashes and instability, including a loss of HD I/O, during very large file transfers. This happens over the network, whether using SCP, FTP, or SMB. I'm a hobbyist, and am no coder or developer, so other than Googling, I have no practical knowledge to pull on. When the problem started occuring, I opened two PuTTY SSH interfaces as root - one with htop, and another with "dmesg --follow" to see what was going on with the system, and this is what happened: dmesg readout at file transfer crash (using SMB this time): Spoiler [238803.445307] ------------[ cut here ]------------ [238803.445321] kernel BUG at mm/vmscan.c:1709…

Still experiencing random kernel panic with latest build. Sometimes it boots, sometimes it doesn't , when operating from a remote location this is very frustrating. Spoiler DDR Version 1.24 20191016 In channel 0 CS = 0 MR0=0x18 MR4=0x1 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 1 CS = 0 MR0=0x18 MR4=0x1 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 0 training pass! channel 1 training pass! change freq to 416MHz 0,1 Channel 0: LPDDR4,416MHz Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB Channel 1: LPDDR4,416MHz Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus…

For anyone looking to build an iSCSI target on their new Helios64, I can confirm that it's working correctly under the test builds for Armbian 20.11. Thanks to @aprayoga for his comment on the pull request, the kernels modules related to LinuxIO have been added to all boards in the Armbian project.

Hello, How can I get a effective shutdown with the battery with legacy 4.4 (it always restarts) (2.5 Gbps OK) or How can the 2,5 Gbps performance issue be solved in 5.8 ? (that can shutdown OK) Which one is the easiest to address and solve for a beginner like me using OMV? Thank You! David

Has anybody got DAS mode working using USB-C ? Using: Armbian 20.08.21 Buster with Linux 5.8.17-rockchip64 I was not certain, I thought I read it was supported. I was hoping to use Windows 10 via USB 3.1 --> Helios64 USB-C to copy large video library. Note; using UART via COM3 is working as expected. Note; in windows I do remember seeing some USB error loading some USB driver; would it be related to some missing driver?int Any successful implementation of USB DAS interface; I would be happy to hear from you.

Hello, my nas is too noisy, do you know if it's possibile to change the fans with others that is silent? Regards.

Is it possible to boot from USB-Stick instead of micro-sd-card? I have the apprehension that the micro-sd-card-slot could break if I use it to often. If it’s possible, how can I do this? Thanks, Jaques-Ludwig

This is a continuation of ata1.00: failed command: READ FPDMA QUEUED noted by @djurny. I've experienced the same issue, and have some additional data points to provide. My observations so far: I'm using WDC WD60EFRX (68MYMN1 and 68L0BN1) drives The drives were working without issue previously behind a ASMedia ASM1062 SATA Controller, I've also used some of them behind ASM1542 (external eSATA enclosure) I can reproduce the issue on a clean install of Armbian 20.08.21 Buster and Focal I can reproduce via simple `dd` to `/dev/null` from the drive so filesystem does not seem to be the underlying cause Every drive is affected (i.e. e…

Since there is a thread about adding ZFS support to the U-Boot build, I thought I'd post a similar request for btrfs. I was looking through the helios u-boot repo a few days ago and noticed that it isn't built with btrfs support. While I could make a separate ext4 /boot partition, it would be convenient to have the entire eMMC formatted as btrfs. This allows for me to make easy and fast backups using btrfs send/receive, and also allows for snapshotting prior to upgrades (via e.g. snapper), and rolling back to a different snapshot at boot. My turris onmia router uses u-boot with btrfs native root, and I've used the snapshot rollback support a couple of times. They…

I have zero room on the root of my helios64? I literally just installed OMV made a raid 5 and setup my shares. Afterwards I setup Transmission and suspect that might be my problem. Any thoughts to locate exactly what is killing my flash memory. I tried df -h and du -sh /. this didn't point me to anything specific.

Continuing the discussion from here On a clean install of 20.08.21 im able to crash the box within a few hours of it being under load. It appears as if the optimisations are being applied root@helios64:~# cat /proc/sys/net/core/rps_sock_flow_entries 32768 The suggestion @ShadowDance made to switch to the performance governor hasn't helped. Anecdotally, I think I remember the crashes always mentioning page faults, and early on there was some discussion about memory timing. Is it possible this continues to be that issue?

Hello, Is there a way (maybe using sysfs) in Linux to manage the brightness of the LED in the front of the NAS ? I found no information about this in the wiki: https://wiki.kobol.io/helios64/led/ or https://wiki.kobol.io/helios64/front-panel/ Thanks.

To continue discussion from Helios64 Support Could you boot from micro SD card? Please use Armbian 20.08.10 image, version 20.08.13 known to have stability problem on many users. After setting up Armbian on the micro SD, reboot (to finish the setup) and login as root, you can check eMMC for filesystem error fsck -p /dev/mmcblk1p1 You can try to change the password of Armbian on the eMMC: Spoiler mkdir -p /mnt/emmc mount /dev/mmcblk1p1 /mnt/emmc mount -o bind /proc /mnt/emmc/proc mount -o bind /sys /mnt/emmc/sys mount -o bind /dev /mnt/emmc/dev mount -o bind /dev/pts /mnt/emmc/dev/pts chroot /mnt/emmc/…

To continue discussion from Helios64 Support Noted, we will enable ZFS support after Armbian 20.11 released. I will need your help to test since i don't have system with ZFS.

To continue discussion from Helios64 Support Currently there is no plan to support to disable the power but it's interesting to know such use case. If we implemented this feature, you would need to go u-boot prompt to enable and disable the power. would this acceptable for you? Under Linux device tree, the power rail declared as regulator node with regulator-always-on property. This prevent kernel (and user) to turn off the regulator. Unless we are able to create device node for the SATA port, to act as consumer of the regulator, we can't remove the regulator-always-on property.

CURRENT branch (Linux Kernel 5.10) Feature Support Status Remarks Shutdown OK Reboot OK Suspend to RAM Not Supported USB host controller refuses to enter suspend mode 2.5G Ethernet (2.5G speed) OK TX offload disabled by default, can be enabled for better performance 2.5G Ethernet (1G speed) Performance issue Requires hardware fix. Main Power/UPS status OK …

News related to Helios64 : Production Software update Wiki / Documentation update Etc...

RockPi4a. Installed busster current 5.8.6 armbian onto eMMC. Works fine. Now i figure out i need swap space (app needs more than the 1G mem i have). So i boot another image from SD an use gparted to shrink the first partition from the end to create 4GByte and create a swap partition in there. Now the board won't boot anymore (see attached file). Erased SPI, no difference. Partition table shows GPT and "MBR protective" (before and after resizing). so, whats the magic to create a bootable armbian disk if one needs different partitioning than just the "full disk one partition" layout ? Is this "uboot" hidden behind the only partition, there was a bun…

I'm trying to get a Rock64 board working with a wifi USB dongle, sold as RTL8188 and which is in fact a 8188eu. I use the latest armbian-buster as downloaded a few days ago. The dongle appears in dmesg when plugged in, but no module is loaded. I can manually load the 8188eu module and get no errors, but no wifi interface appears. Ifconfig, iwconfig and nmtui don't see anything they could use for wlan. I have installed the firmware-realtek package as well, it made no difference. I can get the module 8188eu autoloaded at boot, but that doesn't change the non-availability of a wlan interface. Any help appreciated. I have posted the armbianmonitor -u output in the…

I tried the first start at my brandnew Helios 64. U-Boot 2020.07-armbian (Oct 13 2020 - 16:49:59 +0200) SoC: Rockchip rk3399 Reset cause: POR DRAM: 3.9 GiB PMIC: RK808 SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB MMC: mmc@fe320000: 1, sdhci@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: eth0: ethernet@fe300000 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 3185 bytes…

Hello My Helios64 arrived two weeks ago, after a loooong trip through the Silk Road all the way down to South Europe. First thing I want to give a GREAT THANK YOU to the people at kobol shop support, as they have helped me with my transport/forwarded/ carrier nightmare loop: the address is in Chinese-no address specified-contact the sender-won’t give you your parcel-please call again- no address specified.... So. After reading a good slice of the wiki I couldn’t find a comprehensive manual/article about the simplest usage of the front panel. Glad if you can point me to such information. The principal source of confusion for me are the comments section of …

Hi, I am trying to setup NVME boot on RockPI 4 c. I have tried different things, but no success. First I have installed Redxa SPI last u-boot image over OTG. Download last Armbian for Rock pi 4 c. ( Own building last Armbian for Rock P4 C trunk from 10/28 5.8.16 , I had tried too ) Install image on SD Card. ( dd ) Boot from SD card. Copy Image over scp to SD Card. Copy image with dd to NVME. Shutdown and remove SD Card. Boot from NVME ( Works on ever try ). Login and change password. Add one user. Shutdown and try to reboot. The System never reboot. The serial console shows. 64.495100 nvme nvme0…

Hi guys! I would like to know why this is happening. I guess the script doesnt identify my sd card as the sd card and it erase it just like it does with emmc before clonning the sd card to the emmc. I use latest armbian focal.

Perhaps someone will be interested in this information. https://www.stationpc.com/thread-84-1-1.html

I have installed Armbian distrubution focal i am running with boot from sd and system on nvme I installed gnome disks and i did a benchmark. drive/ model number Transcend 512GB NVMe PCIe Gen3 x4 MTE220S M.2 TS512GMTE220S advertised speeds 3100 read/2100 write The results where as followed: 750 mbs read >>>inline with epectations 150 mbs >>> way below expectations for the drive is there a atch availeble?

I've got a Rock64 1GB (rk3328) running Focal with the legacy 4.4 kernel. I've compiled and installed from source various things like libmali, libdrm, mpp, ffmpeg, and gstreamer, and have successfully gotten ffmpeg and gstreamer to do hardware decoding and gstreamer doing hardware video encoding. I also managed to compile and install xserver 1.20 from the rockchip-linux Github and have it running a barebones LXDE installation. I am now setting my sights on Kodi. I have stock LibreELEC installed and working on another sdcard, but my TV only supports 50Hz, 59.96Hz, and 60Hz refresh rates, meaning that 23.976fps content does not play smoothly. I've read enough to …

Hello everyone, I have an OrangePi 4 that will serve as an interface for the electric car chargers that are produced in my company. We currently use Raspberry 3 and we want to upgrade to the OrangePi 4, mainly because it has eMMc. The problem is that the interface we have was designed to work on Raspberry. I put the SD card with the image in the OrangePi but it starts with the system that has been installed on eMMc (Armbian). Can you tell me if it will be very difficult for the image we use in Rpi to be possible to install on OrangePi? Another thing I want to do is move from the Armbian that I have currently installed on eMMc to Debian, h…

Using Armbian bionic (Ubuntu 18.04) on a Orange PI4, hostapd does not run as service. Neither at startup, nor when stopped and restarted manually. However, starting it from command line works fine? Logfiles (syslog, journalctl) do not show anything helpful. root@IA216:~# service hostapd status ● hostapd.service - LSB: Advanced IEEE 802.11 management daemon Loaded: loaded (/etc/init.d/hostapd; generated) Active: active (exited) since Sun 2020-10-18 12:54:28 CEST; 8h ago Docs: man:systemd-sysv-generator(8) Process: 31481 ExecStop=/etc/init.d/hostapd stop (code=exited, status=0/SUCCESS) Process: 31542 ExecStart=/etc/init.d/ho…

I am observing huge difference in samba speed (both ways to/from PC on Gigabit Ethernet) with Rock Pi 4B. Earlier I had Debian and Ubuntu provided by Radxa and recently speed has gone from 115 MB/s to ~12 MB/s. I moved to Armbian which is currently available for download. Before any updates I had 115 MB/s transfer speed. When I updated to Armbian 20.08.11 Focal with Linux 5.8.15-rockchip64 the speed has go down to ~15 MB/s. The bigger change that happened was kernel upgrade. I exclude problems like: PSU (it is over enough), home network (nothing has changed) and SSD speed (checked - 330 MB/s). Has anyone else also observed limited speed rec…

I have previously successfully been using the USB serial gadget as terminal on the Nanopi R2S. The last working release I have tried was: Linux 5.4.45-rockchip64 #20.05.3 SMP PREEMPT Wed Jun 10 11:47:27 CEST 2020 aarch64 aarch64 aarch64 GNU/Linux Now I am running the following version (Also tried 20.08.08) and the gadget mode does not work after boot. Linux 5.8.14-rockchip64 #20.08.10 SMP PREEMPT Tue Oct 13 16:58:01 CEST 2020 aarch64 aarch64 aarch64 GNU/Linux I have seen no warnings or error messages when running dmesg. After boot on the failing versions the log contains the following section, which I assume means that the driver …

Hi All! I've recently moved to Armbian (Debian buster server) on my Rock Pi 4B - from Ubuntu provided by Radxa (some way failed upgrade). However system is booting from eMMC which has Radxa kernel and then directly to Armbian file system on SSD connected via USB 3.0. Great is that Armbian is working with Radxa kernel, which I want to change to 5.8.14-rockchip64. My question is how should I prepare /boot folder on eMMC (which is FAT file system) to boot Armbian kernel? Is there any other way (reformat eMMC for ext4@32768 sector for /boot folder) to achieve this? Thanks.

Hello! I wrote the wrong bootloader to the emms, now the download does not happen with either emmc or micro-sd. U-Boot TPL 2020.10-00676-g9885313b9a (Oct 13 2020 - 06:24:16) sdram_init: LPDDR3 - 933MHz failed! rk3399_dmc_init DRAM init failed -22 Missing DTB Now I can't use the board in any way, how can I clear the emmc memory?

Hi everybody! I have been working for days to ensure that the MIPI-DSI output works with the Raspberry PI compatible display panel (Product OSOYOO which has a Toshiba TC358762 DSI/DP bridge chip and a I2C backlight controller as Focal FT5406). The following overlay works perfectly with the Radxa kernel 4.4.153 and unfortunately not with the Armbian kernel: Linux rockpi-4c 5.8.13-rockchip64. So far so good. Now if you look at the DTS source files of the two kernels, they have a similar structure but are very different in content. I wonder why you now get the idea to reinvent the wheel. The Radxa kernel contains everything that is needed. What is particularly ann…

After installing Arbian on Rock pi 4 c the sound on the Jack does not work because the sound card driver is. 8316 is not supported The sound goes out anyway on the HDMI of my television Would there be a solution

Hi, I was trying to load below Armbian images into NanoPi M4 (just M4, neither M4B nor M4V2). They are able to be loaded in the first place, but when I reboot the board by typing "reboot" command in the terminal, I can only see black screen showing on the monitor, no led flashing on the board even, and the board never boots up again. If I unplug the power cable and plug back again, it boots as expected. Is there any way I can reboot the board remotely? Armbian_20.08.1_Nanopim4_buster_current_5.8.6_desktop.img.xz Armbian_20.08.1_Nanopim4_buster_current_5.8.6.img.xz Armbian_20.08.1_Nanopim4_bionic_current_5.8.6.img.xz Armbi…

Hi, I'm using NanoPi M4 $ uname -a Linux nanopim4 4.4.213-rk3399 #3 SMP Mon Oct 5 15:53:54 CEST 2020 aarch64 aarch64 aarch64 GNU/Linux and wondering if I can upgrade the linux kernel to 5.8.x without reinstalling other things. I tried armbian-config -> System -> Other All available options are those 4.4.213-rk3399 with different Armbian versions 20.08.x. I'm currently on 20.08.9 Appreciated any step, pointer Thank you

I'm trying to make boot a NanoPi Neo3 from SSD connected through USB. - I installed armbian Buster 5.8.6 downloaded from armbian.com - Next, I tried with and without apt update - connected an external SSD through the USB port and and a USB 3.0->SATA box - Executed nand-sata-install and selected the option to boot from external SSD - The system prepared the SSD, copied filesystem, modified boot (and I verified that in armbianExt.txt it set the UUID of the external disk) - rebooted ... And nothing I've observed that the system not always detects the external SSD. I must unplug and plug it to be recognized (as /dev/sda …

hey, this change https://github.com/armbian/build/pull/2010/files made my rockpi-4b (with 4GB ram) finally stable some time ago DDR_BLOB='rk33/rk3399_ddr_933MHz_v1.20.bin' #instead of 1.24 After messing with rx/tx offloading, this was the solution, no more failed apt and download errors, great! It seems that this change got lost in the transition to the new u-boot / different logical structure or is not needed anymore for the 1GB models it was mentioned originally, see here: https://github.com/armbian/build/commit/f2db96252530d2f5585755b518e7fd020b5f0392#diff-18c1f509b638f24dc14854e6af5173bb Any chance to get it back for rockpi-4…

Hello, I have a problem with my OrangePi 4, if I connect it with the operating system already installed at the factory (Android 8), I can get my USB keyboard and mouse connected to work normally. However, whenever I try a new image, be it Debian, Armbian or another version of Ubuntu, I can only get the mouse to work, the keyboard never works and I get stuck in the login screen where I can't write even the username and password. Can someone help me?

This main thread has been locked. Thanks to the Armbian team, we now have our own Kobol club (kinda sub forum) dedicated to our products (Helios64 & Helios4). So now you are encourage to create individual threads for new issue, discuss feature, share setup, etc... This will help to improve overall readability. Note : Before asking a question please insure the information is not already available on Helios64 Wiki or addressed in a previous post in this forum. Latest Build : Check : https://dl.armbian.com/helios64/ Archived Build : Check : https://archive.armbian.com/helios64/archive/ …

Installed the image Armbian_20.08.1_Rockpi-4b_buster_current_5.8.6.img.xz . Then, in armbian-config -> Software, I had installed linux headers + source. I got two new directories: linux-headers-5.7.15-rockchip64 linux-source-5.7.15-rockchip64 If I execute: uname - r I get: root@pi:~# uname -r 5.8.6-rockchip64 The kernel version and installed source/headers are not the same, so they are useless. How to get the correct source/headers? EDIT: When first boot, the OS asked for locale/timezone settings, I did hit ENTER as default and it set the locale language to Slovene. When doing apt-get up…

I have Rockpi 4b v1.4 and Armbian 20.05, kernel 5.4.49, installed and booted from NVME drive. For last months survived all minor Armbian updates, but after upgrading to 20.08 ( to kernel 5.8.10) board doesn't want boot. Steps to reproduce: 1.1 get Armbian_20.05.3_Rockpi-4b_buster_current_5.4.45.img.xz and write it to EMMC. 1.2 Boot board from EMMC, apt-get update, apt-get upgrade. Kernel upgrades from 5.4.49 to 5.8.12 1.3 Reboot. Board reboots fine. 2.1 get Armbian_20.05.3_Rockpi-4b_buster_current_5.4.45.img.xz and write it to NVME drive. Add fdtfile=rockchip/rk3399-rock-pi-4.dtb and overlays=pcie-gen2 to armbianEnv.txt. …

My system has: $uname -a Linux rkpi 5.8.11-rockchip64 #20.08.4 SMP PREEMPT Wed Sep 23 17:51:13 CEST 2020 aarch64 aarch64 aarch64 GNU/Linux Sound stack seems to be loaded, but alsa/pulseaudio sees only hdmi-output device (aplay log below). How to enable analog ouput on 3.5 mm jack? $sudo aplay -lL default Playback/recording through the PulseAudio sound server null Discard all samples (playback) or generate zero samples (capture) samplerate Rate Converter Plugin Using Samplerate Library speexrate Rate Converter Plugin Using Speex Resampler jack JACK Audio Connection Kit oss Open So…

Hi, I'm new to armbian and I've started with RockPi4b board. I would like to add fan control with PWM, but adding pwm (or pwm0) overlay doesn't work. I can't also find the overlay for it at /boot/dtb-5.8.6-rockchip64/rockchip/overlay/. Is it supported? I've checked and the /sys/class/pwm/pwmchip0 is present, but accessing export, as described here : doesn't work and /sys/class/pwm/pwmchip0/pwm0 is not present. I've tried to find pwm access examples for this board, but none of it works on armbian (all are vendor builds specific). Can anybody point me in the right direction or give any hint how to enable pwm? EDIT…

Hi, I would like to know if it is possible to switch from the current branch to the legacy one as I've read that the board will be much more stable with the older kernel ? I've installed my NanopiM4 last march, and I've experienced some random freezes of my board after some time (can take weeks). It seems that one of my solutions would be to use the legacy kernel as it is much more stable - information I got by reading the forums (something I haven't done before because I'm stupid and was in a hurry...). Is it possible to downgrade only the kernel at all ? Here are the packages that (I think) I have to replace : linux-bu…

Hello everyone! I have an issue with rebooting my orangepi 4. when i use tf card, reboot is working. but when i using system in emmc, the board can't reboot. the output from debug ttl is like this: [ 41.329350] watchdog: watchdog0: watchdog did not stop! [ 42.148627] xhci-hcd xhci-hcd.5.auto: Host halt failed, -110 [ 42.170221] gpiod_set_value: invalid GPIO (errorpointer) [ 42.188751] xhci-hcd xhci-hcd.5.auto: Host halt failed, -110 [ 42.189252] xhci-hcd xhci-hcd.5.auto: Host controller not halted, aborting reset. [ 42.190309] reboot: Restarting syste

HI. I burned the latest official Rockpi4 focal kernel 5.8.x on both rockpi 4 B and C. The problem is only present on the C model. Both USB 2.0 aren't working at all.

I'm a complete noob to compiling kernels and have been struggling (and failing) for the past week to get an RT kernel compiled using Armbian build and reading various threads in the forum. Is it even possible? If so, what config options need to be set to get the correct kernel version matching the available rt patches? Thanks!

Hi, I want to know if there is another way to power the Nanopc-t4 besides the 12V input power jack. As far as I know the 12V power input is the only way but If someone have another idea or way to do power the board, it could be very helpful for me. Thanks.

First time user here. I got a Rock64 board and flashed Armbian_20.08.1_Rock64_focal_current_5.8.6_desktop.img using Etcher to an SD card. When I try to boot, nothing happens. If I examine the SD card on my Linux PC, there is only one partition on it and it appears to be a kernel image. I assumed that the .img file would have the U-Boot partition as well. Is there a different type of image file I should be using that would contain everything that I need to boot? If not, how do I create such an image?