Rockchip

Got this error this morning doing apt upgrade! Not sure what the issue is, there seems to be plenty of space. _ _ ____ _ __ __ _ ___ ______ | \ | | _ \(_) | \/ | || \ \ / /___ \ | \| | |_) | | | |\/| | || |\ \ / / __) | | |\ | __/| | | | | |__ _\ V / / __/ |_| \_|_| |_| |_| |_| |_| \_/ |_____| Welcome to Armbian 21.08.5 Focal with Linux 5.10.63-rockchip64 Calculating upgrade... Done The following packages will be upgraded: armbian-bsp-cli-nanopim4v2 armbian-config armbian-firmware linux-libc-dev 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 9,657 k…

Hi together, iam realy desperate and hope someone can help me with my problem. I think something crashed while I disconnected the USB-Cable in U-Boot Mode with helios64. Now Iam not able to see my m.2 SATA SSD in U-Boot Mode as USB Storage in my PC. I use the U-Boot mode from a SD-Card with a boot image. When I start some armbian System from SD-Card the m.2 SSD is visible and ready to use. I dont know what kind of logs do you need for my Problem. Sorry for that. :-( The only thing I want to do is to use my SATA m.2 SSD as armbian system drive with OpenMediaVault again. best regards sommer11 Infos to my device: https:…

I was wondering if anybody had an STL or the like for the drive sleds. I haven't broken one yet, but was thinking about making some in different colors on my 3D printer if they're available. Thanks.

Hi folks, I am puzzled. When I am away for a few days I usually shut down my nas. It does indeed shut down but over night comes up again. Now I would like to know what triggers that unwanted restart here... I am currently on 21.08.3 Buster with Linux rockchip64 5.10.63 and do have OMV running... I could unplug the battery next time but I'd rather solve the issue the correct way. It's strange to me because I did not change any system parameters in OMV or via SSH. I do believe that an update to the latest kernel did mess things up. Where do I have to have a look?

Greetings ! I am new to Armbian , I am using Rockpi4B for our development . I have successfully built and checked the working of the image. We have few developed application and service files . How can I include these applications and service files as a part of Armbian image. Thanks in Advance

Hi! I'm having trouble with hdmi display and armbian focal on rock64. All works with simple office hdmi displays but fails with an open frame display connected using hdmi->dvi cable. Even the boot messages do not display and the display goes into power saving mode. Here are some of the outputs: rock64@rock64:~$ cat /sys/class/drm/card0/card0-HDMI-A-1/status connected rock64@rock64:~$ cat /sys/class/drm/card0-HDMI-A-1/status connected rock64@rock64:~$ dmesg | grep hdmi [ 4.484419] dwhdmi-rockchip ff3c0000.hdmi: Detected HDMI TX controller v2.11a with HDCP (inno_dw_hdmi_phy2) [ 4.485826] dwhdmi-rockchip ff3c0000.hdmi: registe…

Kia ora. I am aware that the external USB ports on the Helios are able to deliver up to 900mA per port. I am wondering whether it is possible to find a power source inside the Helios64 that would be able to deliver, say, 2.5A at 5v? Maybe somewhere quite soon after the 12v power in...? 🤔 Jon

Hi there, i'm trying to getting Armbian working on my RockPi 4B. Installation and everything went fine. Even my Intel 660 2TB NVMe SSD was detected as I booted the SD card Image (created with Etcher). But as I booted the image from eMMC (flashed the image via dd if=image.img of=/dev/mmcblk1); it booted fine so far, but it doesn't detect the NVMe SSD... If I return to uSD Boot, it is detected again... Here is the log output of dmesg | grep nvme from "Boot from eMMC" root@rockpi-4b:~# dmesg | grep nvme [ 2.754457] nvme nvme0: pci function 0000:01:00.0 [ 2.754688] nvme 0000:01:00.0: enabling device (0000 -> 0002) [ 64.489438] …

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

Hello all, I have a question today regarding ARMBIAN - Linux and the configuration of the ZRAM .... Under the ARMBIAN for RockPI 4 I have a ZRAM for the SWAP and a ZRAM for /var/log. Is it possible that I change this configuration and use the eMMC memory for these two areas? Because the big problem with /var/log is that it is simply too small and thus constantly runs into "ERROR" -> volume full. Thank you very much and I am looking forward to constructive contributions to solve my problem. Kind regards

Hello together, I have a RockPI 4B board with the extension for M.2 SSD applications. I wanted to install a 120 GB SSD disk, but unfortunately I cannot find it under "fdisk -l". Can anyone help me here with what I can do? Are there any tricks or the like to make this work? Kind regards Z. Matthias

Hi folks, I am wondering if somebody with a mac enviroment has a decent / performant samba connectivity? After I upgraded to Big Sur I have severe issues with the samba protocol when accessing my shares on the helios running openmediavault. I know that Apple had made some changes with samba but there might be some users that dug a little bit deeper and could give me a hint. I did try it with different settings in the extra options over the past weeks but with no luck so far. Sidenote: Also NFS is terribly slow and laggy. I am back with AFP connection now that does the job perfectly and fast.

Hi, I need some guide and steps required (and if possible) to enable hardware acceleration using FFmpeg. Is the only thing I need since the idea is to use this SBC as Surveillance platform (for example, with Motion+Motioneye or Shinobi). Currencly without hardware accel, using 3 rtsp cams uses each 100% of a core (which translate to 300%). I've searching a lot, but I saw hwaccel with others apps, but not in particular with ffmpeg. I already managed to compile it with --enable-rkmpp (h264_rkmpp hevc_rkmpp vp8_rkmpp vp9_rkmpp) and available hwaccels: vdpau cuda vaapi drm opencl. Any help will be much appreciated. Currently fresh inst…

Last night I shutdown my Helios 64 (sudo shutdown now) but when i went to boot it this morning, after startup it looks to be hung, all blue lights solidly on. It's set to run from the micro SD card, so wondering if i hit a R/W limit on that. Serial log below, it doesn't progress beyond "starting kernel" I can mount the MicroSD on my ubuntu box and read the file structure DDR Version 1.24 20191016 In channel 0 CS = 0 MR0=0x18 MR4=0x2 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! channe…

pi@rockpi-4b:~$ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: rockchipes8316c [rockchip,es8316-codec], device 0: ff880000.i2s-ES8316 HiFi ES8316 HiFi-0 [ff880000.i2s-ES8316 HiFi ES8316 HiFi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: HDMICODEC [HDMI-CODEC], device 0: ff8a0000.i2s-i2s-hifi i2s-hifi-0 [ff8a0000.i2s-i2s-hifi i2s-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 pi@rockpi-4b:~$ How is it possible to turn on the sound on HDMI? There is sound on the 3.5mm socket. But when I click on the speaker in the top right, then Volume Control. Only "Analog Output" can be selected as output devices.

Hello everyone, I’m starting this message by apologizing for my poor English (I am French) and also by informing you that I am a newbie with Linux. I have a big problem with my NAS Helios64. At first, I thought this problem was caused by OMV. So I went to the OMV forum to explain my situation. I created the following topic: https://forum.openmediavault.org/index.php?thread/40252-many-problems-after-an-update/&pageNo=1 . There, a kind moderator (macom) asked me to enter some instructions to try to pinpoint the root of the problem. After giving him some outputs, he told me: "For me it looks like your SD card is dead." My i…

Hello, target : nanopi R4S/4Gb I downloaded the last image from the armbian site for the friendlyelec nanopi RS4. I flashed an A1 SD card of 32GB. I only see one partition (after a 17MB offset). When I try to use it on my R4S, the red power led lights up, then nothing, even after several minutes. I opened the router and connected a serial converter on the console, in this case also there is no sign of life after the power on... I have flashed on another SD card an ubuntu image from the friendlyelec site. This image boots, but it seems that the configuration of the console is not the usual default one => the speed 115200 does not w…

Hi guys, I have checked the Buster image and stuck in following issue: On Rockpis, tty2 and (the only working) spi2 sharing the same PINs. Due to this reason, SPI is not functional . from dmesg: [ 1.598230] rockchip-pinctrl pinctrl: pin gpio1-22 already requested by ff0c0000.serial; cannot claim for ff140000.spi [ 1.598269] rockchip-pinctrl pinctrl: pin-54 (ff140000.spi) status -22 [ 1.598287] rockchip-pinctrl pinctrl: could not request pin 54 (gpio1-22) from group spi2-miso on device rockchip-pinctrl [ 1.598304] rockchip-spi ff140000.spi: Error applying setting, reverse things back I try to switch back tty2 to tty0 in dts and also…

Hello I need to change a drive in the Helios64, and so I bought a new WD 2TB drive. Using a WD My Book 111D USB enclosure, I have partitioned, formatted and copied the data from the old drive. But when I change the drives to put the new one in the Helios64, the drive appears unformatted. See below. I can't understand what's happening, when I plug it back through USB everything is back to normal. Does the partitioning through USB differ somehow??? It appears as if the partition table "stays in the USB enclosure", which doesn't make sense for me. Is there something to try? Do I have to start again the process in the NAS enclosure? I…

Hello, I am working with "Armbian_21.08.1_Nanopineo4_focal_current_5.10.60" on a nanopi Neo4. During the initial boot, the (HDMI) monitor shortly displayed some text (went to fast to read) and then went blank and the monitor turned off. However, output came through the serial debug port (USB2) and I was able to complete the initial setup. Now, I can now connect with SSH, but it would be nice to be able to work directly. How can I redirect the output to the HDMI monitor? Cheers, John

Edit: This is a duplicate already reported and a pull request in place. mods please delete The solution is to revert a patch related to power management. Symptoms are that ethernet link comes up, but no ip, dhcp, cannot assign ip address. the following patch resolves the issue on my system. I did not raise this in bug tracker since its not allowed to put things in there that are not supported. Unsure what else to do with info, hopefully it will help someone else. From ad63cb5d37f9634fc097249ddda4240c10f041d7 Mon Sep 17 00:00:00 2001 From: Dan Johansen <strit@manjaro.org> Date: Tue, 7 Sep 2021 16:26:09 +0200 Subject: [PATCH] Revert "net: stmmac…

Sold on Reddit. Hello, looking at selling my Helios64. Mostly looking at getting a price check (what's the device still worth) and gauging interest. Device is in pristine condition, standard fans were swapped for Noctua NF-A8. (standard fans will be included) I'd prefer to keep this EU only as shipping is going to be a pain.

Last night my Neo3 seems to have died. As I checked it earlier today the heartbeat was gone and the SoC (with glued heat sink on) was hot. After power cycle it refuses to boot again. Wrote the same known to work image I used yesterday to boot it on a fresh sd and got this from serial which was the same as the other sd: DDR version 1.16 20190528 ID:0x805 N In DDR4 333MHz Bus Width=32 Col=10 Bank=4 Bank Group=2 Row=15 CS=1 Die Bus-Width=16 Size=1024MB ddrconfig:14 OUT Boot1 Release Time: May 13 2019 17:34:36, version: 2.50 ChipType = 0x11, 248 mmc2:cmd1,20 emmc reinit mmc2:cmd1,20 emmc reinit mmc2:cmd1,20 SdmmcInit=2 1 mmc0:cmd5,20 That's it. No further o…

Hello. So, really sorry to hear that Team Kobol are disbanding. Many thanks to all who worked so hard to put the Helios64 together. I am really pleased with my Helios64, and am grateful for being able to get hold of one of these. Thank you! 🙏 What with one thing an another, I never got hold of a UPS battery; the battery couldn't be shipped with the original shipment, due to restrictions on shipping Li-Ion batteries; and then the additional postage costs for sending the battery seperately were prohibitive for Team Kobol, which I completely understand, so I chose not to pay the extra for the battery. However, it would be really useful for me to build…

Oh,I fixed this problem spend 2 weeks,I finally heard sound from 3.5 mm jack (this jack is OMTP otherwise need keep press headphone button) I see this topic,and I compair https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/sound/soc/codecs/rt5640.c and https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/sound/soc/codecs/rt5651.c,this rt5651 not enable mclk and orangepi4"s rt5651 linked i2s1,the i2s1's SCLK_I2S_8CH parent not SCLK_I2S1_8CH defult and need set alsamixer in following(also use alsactl save this alsamixer state): amixer set 'HPO L' on amixer set 'HPO R' on amixer set 'HPOVOL L' on amixer set 'HPOVOL R' on…

Hi all, a new RK3399 board appeared, it is called RockPi4 I have two of these beasts here already, and they works nicely - I like the small details about it (nice eMMC fixture, all heat plates on the bottom side for simple cooling, and an M.2 PICe slot for my second network card Do you see any chance to get Armbian working on that beast, and if so, what can *I* do (with my limited experience in kernel programming)? Debian is working on it already, in case you need more specific information please let me know. Any help is appreciated. So far, Michael

I have 2 issues in LibreOffice installed by default in Armbian, running on RockPi 4B. First: special characters aren't working. Second: filenames or folders using special characters are not recognized - therefore I can't access or edit my files, and even can't save files with special characters... anyone has a tip to solve these two issues? Thanks a lot

Hello, I have tried the procedure described on this topic (https://forum.armbian.com/topic/15431-helios64-support/page/9/) but it doesn't work for me. armbian is installed on an SSD, I have no micro SD card in my Helios64. Today, i can no longer start armbian :/ This is what the serial console shows me: Spoiler DDR Version 1.24 20191016 In channel 0 CS = 0 MR0=0x18 MR4=0x2 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 1 CS = 0 MR0=0x18 MR4=0x2 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 …

Hello, I bought myself a NanoPi M4V2 and 4x SATA HAT for NanoPi M4, hoping to make a small home made server with some docker containers. I installed Armbian buster 5.10.21, downloaded from your site and managed to boot the OS from an attached SATA drive. I have some experience with linux (mostly Ubuntu/Debian), I own and I’ve played with Raspberry boards and I wrote small python scripts to work with GPIO on raspberry pi (how to blink a led or how to connect and display some text on an I2C 16x2 LCD). I thought that might be a nice project if I could connect an I2C LCD to nanopi and display some text text from python script, but here where I hit a bric…

Hello, I'm trying to use the NanoPi M4v2 SPI however it doesn't seem to work. I used armbian-config to enable the gpio overlay: [ ] dwc3-0-host [ ] i2c7 [ ] i2c8 [*] pcie-gen2 [ ] rk3328-opp-1.4ghz [ ] rk3328-opp-1.5ghz [ ] rk3399-opp-2ghz [ ] spi-jedec-nor [*] spi-spidev [ ] uart4 [ ] w1-gpio And the SPI isn't showing up on /dev: ls /dev/spi* ls: cannot access '/dev/spi*': No such file or directory Wasn't this enough to be able to use the SPI1 on this board? SBC: NanoPi M4V2 System: 5.10.35-rockchip64 #21.05.1 SMP PREEMPT Fri May 7 13:53:11 UTC 2021 aarch64 GNU/Linux Thank you.

Hey, I have uninstalled cron from my system completely, but I just thought I might help contribute, even just a little, by making some services and timer files to replace the ones in these folders: /etc/cron.d /etc/cron.daily /etc/cron.hourly /etc/cron.weekly Now keep in mind that I have not fully tested any of these yet! I would appreciate feedback in testing these, since most of these I won't even use on my system. I barely even use the armbian-config utility at all, so... yeah... The files in question are these. Let me know if I should add more: armbian-truncate-logs armbian-updates armbian-ram-logging The…

This happened out of the blue, without indication of anything else being wrong. I just noticed that NFS stalled, and realized that the server is not on the network. The system on the box was running fine, but there were no lights on the network connector (it is connected with the upper, 1Gb, adapter). I replugged the cable into the 2.5G socket and it went online. Then I powered the box off and on again, with the cable in the 1G socket, and it came online normally. This is what I found in dmesg/syslog: Aug 31 09:31:39 localhost kernel: [379809.423687] NETDEV WATCHDOG: eth0 (rk_gmac-dwmac): transmit queue 0 timed out Aug 31 09:31:39 localhost kernel: [379809.424…

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.

Last week I updated the Armbian on my NanoPi M4V2 to the latest version (Armbian 21.08.1 Buster with Linux 5.10.60-rockchip64) and started noticing some issues with my Zigbee2MQTT local install. With the help of the Zigbee2MQTT main developer, we managed to confirm that the issue was reproducible on 5.10.60, but everything was working fine on previous kernels like 5.4. Other users not on Armbian (Raspbian) also confirmed that they were experiencing this problem with the latest kernel but was working fine on previous versions. We realized a bug was introduced for the CH341 driver in 5.10.60, that seems to have been fixed now on 5.10.62. …

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 have bricked my system by installing the rk3399 legacy multmedia framework. It was installed on emmc. I was able to recover my system by using the P11 jumper to skip the boot on emmc, as explained in the doc, and now my system runs on a SDCard. The problem is, it seems that I cannot access the EMMC anymore -- it does not show up /dev. My intuition is that the P11 jumper disables the EMMC altogether. Am I write and if so, how can I access the EMMC again? I would like to be able to read it again (I had important data, notably unison synchronization files) and reinstall a fresh OS on it. Any help would be welcome!

Hi, I'd like to control ws2812 led's via gpio spi. I'm using this octoprint build by ldiaz: I checked /boot/armbianEnv.txt and there's overlay_prefix=rock64 and after enabling spi via armbian-config also overlays=spi-spidev. Then I rebooted but ls /dev/spi* shows nothing. Can anyone help?

Hi, Ever since updating to kernel version 5.10.60 (#21.08.1), I have been getting these weird kernel error messages. Such error messages pop up constantly when doing certain operations, like: mmc2: running CQE recovery And also some of these: EXT4-fs warning (device mmcblk2p1): ext4_end_bio:349: I/O error 10 writing to inode 256 starting block 968704) As well as these: kernel: print_req_error: 47 callbacks suppressed kernel: blk_update_request: I/O error, dev mmcblk2, sector 7716864 op 0x1:(WRITE) flags 0x4000 phys_seg 8 prio class 0 kernel: Buffer I/O error on device mmcblk2p1, logical block 954373 A…

There are a number of modifications that have been suggested that people implement to address certain issues. The ones I can find are: - In /boot/armbianEnv.txt: extraargs=libata.force=3.0 - If doing debugging, also add: verbosity=7 console=serial extraargs=earlyprintk ignore_loglevel - In /boot/boot.cmd regulator dev vdd_log regulator value 930000 regulator dev vdd_center regulator value 950000 and then run: mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr - In /etc/default/cpufrequtils: ENABLE=true MIN_SPEED=408000 MAX_SPEED=1800000 GOVERNOR=ondemand (or 1200000 instead of 1800000) …

Hi! In the Kobol wiki, there are 2 supported kernels : 4.4 and 5.10 In the armbian-build GIT repo, I see also patches for 5.13. What is the status of the 5.13 patches for the Helios64? Kind regards, Xavier Miller

My Rock Pi S logs a NULL pointer dereference in the ext4 module after running for 1 to 3 hours. Subsequently existing processes continue to run but it appears that new processes can't start (eg I can't ssh in). The filesystem is on a new Sandisk Ultra Plus microSD card. As a test, I remounted the root filesystem read/write and the board ran flawlessly for 10 hours. When I get time I will try rebuilding the image with the root filesystem on F2FS. Aug 31 09:31:27 rockpi-s kernel: [ 1944.993824] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000f8 Aug 31 09:31:27 rockpi-s kernel: [ 1944.994681] Mem abort info: Aug 31 …

I seem to have hit another problem with my Helios64. It seems that overnight, HDs 4 and 5 disappeared and no longer seem to be powered. I've disconnected all the other drives and tried it with just 4, and it seems to be a power problem as the drive activity light seems to light up for a short while, but not at full prightness. Also I note that SATA 4 and 5 are on a separate power line to the other 3. Anyone seen this before? Is it fixable?

Hi, Just got my Helios64 crashed: red error led is blinking. I had a raspberry pi left logging on the USB-C and caught the crash: [567513.689265] rk_gmac-dwmac fe300000.ethernet eth0: Link is Down [567519.833508] rk_gmac-dwmac fe300000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off [567828.048254] rk_gmac-dwmac fe300000.ethernet eth0: Link is Down [567834.198593] rk_gmac-dwmac fe300000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off [568870.455100] rk_gmac-dwmac fe300000.ethernet eth0: Link is Down [568876.599602] rk_gmac-dwmac fe300000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off [647513.282616] Unable to handle kerne…

Hello! Id like to use UART1 in NanoPi R2s , but i cant turn on it in armbian-config. There is only UART4.

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.

Hi All, My helios64 died the other day - well failing to boot. It had been solid for quite some time, then I might have made the mistake of updating it.... This is from putty on booting: 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 Siz…

I have a strange problem with my R2S. I grabbed latest buster and focal images, burned them using Balena Etcher onto a pair of 32GB SanDisk Extreme Cards and neither is booting. Serial console shows that boot process gives up waiting for root file system and drops me into initramfs shell. Looking into /dev, I see no mmcblk0 device (or any other block device apart from loops). If I now eject and re-insert the card, the device shows up. If I do it during boot process, while the board is still waiting for rootfs, boot process continues correctly. Reboots are fine, but if I unplug the board for longer than a second it's back to initramfs for me. …

I understand that this problem is not related to armbian. I tries asking NexDock but they don't know how to make it. So, I just wonder anybody knows how to let armbian on Rock PI4B work with NexDock 360's keyboard ? I know when using Raspberry PI, I can add a line dtoverlay=dwc2,dr_mode=host to /boot/config.txt. But when using armbian, there is no config.txt in /boot. Thanks.

Dear Armbian supporters, Using kernel 5.10.21-rockchip64 on Rock Pi 4 (and 5.10.21-sunxi on Lime2), I am not able to mount a LUKS-encrypted drive. Changing the kernel to 5.10.16-rockchip64/5.10.16-sunxi I am able to mount the LUKS-encrypted drive again. Error message when trying to mount the drive is: "No key available with this passphrase". Which change could have introduced this bug? Greetings a5s397

This is something hopefully suitable to become a 'Board Bring up' thread. The NanoPC T4 was the smallest RK3399 board around featuring full set of interfaces (Rock960 was smaller but there you can't use GbE without a proprietary expander) but in the meantime he got two smaller siblings: NanoPi M4 and the cute NEO4. Pros: Another RK3399 board so software support is already pretty mature Rich set of interfaces (2 x USB2 without shared bandwidth, 2 x USB3, triple display output and so on) No powering hassles due to 12V (2A) PSU requirement 16GB superfast eMMC 5.1 Usable and performant Wi-Fi (dual band and dual antenna so…

I finally assembled my Helios 64 today. Went well, just took a while. I'm reading the Kobol Wiki page for installing the OS on the internal EMMC and am a bit confused. Hoping someone can point me in the right direction. I usually boot a SBC the first time from an SD card to do some testing. Then I'll use Armbian config to install the OS onto the EMMC when I am ready. The Kobol Wiki talks about first installing uboot from an SD card. Is that actually needed? Also, do I really need to set up a serial terminal session? I usually just SSH into the box (I know find the IP address via my DHCP server) and configure everything from there.

Is there an accepted procedure for moving from using ramlog to logging to disk? I've looked but everything I can find is about setting up ramlog. I assume it's more complicated than just creating a partition (or ZFS dataset) and mounting it /var/log, disabling ramlog, and rebooting.

i found a running task on friendlyelec desktop called "pwm fan" But i found no more informations how to connect a pwm fan to the Nanopi M4 Which pins are needed to connect ? Can i use a normal 5V Fan or is a special Fan needed ? Anyone aware of this ?

Hi, sorry, prop. a stupid question - but I was so far not figuring out the answer. I have a helios64 running - pretty standard installation, including openmediavault and docker, as described on the kobol help page. I realized that there are some firewall/iptables rules are set, as example: tester@helios64:/etc# sudo iptables -L Chain INPUT (policy DROP) target prot opt source destination ACCEPT all -- anywhere anywhere ctstate RELATED,ESTABLISHED ACCEPT icmp -- anywhere anywhere state NEW,RELATED,ESTABLISHED ACCEPT tcp -- anywhere anywhere tcp d…

I checked for any available updates yesterday, and this (linux-u-boot-helios64-current 21.08.1) was applied. Can't find what was new or if it was only a version bump. By the way, nothing broke after the update.

Hi all, been trying to sort out a stability problem with what was a rock solid helios64, i moved from running armbian on the eMMC to a 256GB sandisk extreme SD card due to plex continually filling it up. currently running Armbian 21.05.6 Buster with Linux 5.10.43-rockchip64, running OMV, Plex and ZFS not much more it appears this is where things go pear shaped: Spoiler [ 6636.457621] ata1.00: exception Emask 0x2 SAct 0x3800000 SErr 0x1000400 action 0x6 [ 6636.458306] ata1.00: irq_stat 0x08000000 [ 6636.458659] ata1: SError: { Proto TrStaTrns } [ 6636.459051] ata1.00: failed command: READ FP…

I have a M4V2, and want to build a mini NAS with OpenMediaVault 5 under Armbian (OMV5 can only run under Armbiam/Debian, but not in Ubuntu) The M4V2 has a SATA hat, and it can support up to 4 hard drives (2.5 inches size), so the SATA hat is powered separately, and I guess this is why this hat always gets overheat. There is a 12V fan interface (2pin) on this SATA hat, just right biside the power button. And I found that there are already some solution in this forum, all kinds of scripts, can drive the Fan according to the CPU's temperature, or even SSD/HDD's temperature, this are so amazing. And then when I tried these scr…

I not see in Helios64 assembling guide, how should be set coolers. Where should be directed airflow? Inside or outside the case?

cancelled - power unit cable was not correctly plugged in and NAS was running on battery, hence the automated shutdowns, i think (but it's not clearly printed / displayed anywhere, i would say that it could have helped).

I've built custom Linux 5 kernel for Oprange PI 4 including only options required for this board and module drivers for peripheral devices. Long story shor: It works, it boots, it runs, it's hot. Now I _think_ I've located cause of overheat: Linux 5.*.* 08:58:34: 1800/1416MHz 2.84 50% 1% 8% 0% 40% 0% 73.3°C 0/5 08:58:40: 1800/1416MHz 2.85 28% 0% 7% 0% 20% 0% 73.3°C 0/5 08:58:45: 1800/1416MHz 3.35 62% 0% 8% 0% 53% 0% 75.6°C 0/5 08:58:50: 1800/1416MHz 3.96 48% 1% 9% 0% 37% 0% 73.9°C 0/5 08:58:55: 1800/1416MHz 4.04 42% 0% 8% 0% 33% 0% 76.9°C 0/5 08:59:00: 1800/1416MHz 4.20 71% 1% 8% 0% …

NAS was on during the night and this morning : no more RAID5 (with 5 WD HDD). After reboot, i see that two disks are missing : ``` [Sun Jul 18 11:49:11 2021] ata1: illegal qc_active transition (00000000->00000001) [Sun Jul 18 11:49:14 2021] ata2: softreset failed (device not ready) [Sun Jul 18 11:49:23 2021] ata1: illegal qc_active transition (00000000->00000001) [Sun Jul 18 11:49:24 2021] ata2: softreset failed (device not ready) [Sun Jul 18 11:49:38 2021] ata1: illegal qc_active transition (00000000->00000001) [Sun Jul 18 11:49:38 2021] ata1.00: failed to set xfermode (err_mask=0x40) [Sun Jul 18 11:49:56 2021] ata2: illegal qc…

I'm having a very weird issue. I've encrypted a 5TB USB drive on my computer with LUKS sudo cryptsetup luksFormat /dev/sda1 And it works great on my computer. But when I plug in into my Helios64 and try to use it: sudo cryptsetup luksOpen /dev/sda1 secret Enter passphrase for /dev/sda1: No key available with this passphrase. It just refuses. And if I try to encrypt the drive from the Helios64 using cryptsetup it never finishes, the command runs forever. Anyone had similar issues? Any ideas?

Hello, I've got my Helios64 since a few week now and enjoying it a lot. I've installed k3s on it with various applications. The next step is to install home assistant to control my home. Previously, I've already had a setup with a RaspberryPi with a Arduino Mega connected, that is running the rflink firmware. That way I, can control cheap 433Mhz power switches. The problem is, when I connect the Arduino (acting as a serial input device) to my Helios64, the system does not startup anymore. The following error message is printed on the serial console: WARN halted endpoint, queueing URB anyway. Unexpected XHCI event TRB, skipping... (f5f5deb…

Is anyone having issues with the Cinnamon desktop version restarting the desktop when using the menu app launcher? Can be repeated by launching with super key and typing anything for search or just launching any application. Happens with all 3 major menu app launchers. menu, cinnamenu and cinnstark Pinebook pro

I have two Rock64 single-board computers running Focal Fossa. One is stable and the other gets segmentation faults when compiling and sometimes a kernel oops. After some searching, my understanding is this can be fixed by slowing down the memory speed by installing rk3328_ddr_333MHz_v1.13.bin from the ayufan-rock64 GitHub repository into uboot along with possibly rk3328_miniloader_v2.46.bin as well. Unfortunately, I'm clueless how to do this. I'm running the latest Armbian Focal Fossa Server from August 19 with the 5.7.17 kernel. Do I need to build a new image or can I patch an existing SD card? I'm sorry if I there is already a thread on this.…

Hi, my company have commissioned at an external company ti develop a device based on rk3399. The external company have returned a device with a Debian 10 Linux image for the device. We are not satisfied about its the Debian distro maded by the external company because the UI it is not perfect. Sometimes, by moving forms, a little part of the display is not repainted correctly or sometimes a portion of a form disappear. So the question is: wich is the right way to build a Debian distro ourself? I have tryed ubuntu fiendlyarm. The os starts, I can enter by ssh but nothing appear on the display so, wich is the righ way to manage the hardware configuration of a custom d…

I've been hopelessly trying to get Armbian(Buster) and OMV to work together properly. But alas no luck. I decided to start over using a fresh and latest image on the SD card. I believe I may have unwittingly screwed up the eMMC boot process because I added an M.2 SATA drive in yesterday and have since removed it. Hence my quest to simply get the SBC up and running from the SD card. I have tried everything this morning, I cannot get an image to load at all. One of my questions is; do the hard drives need to be installed just to get the SBC working? I have tried with them in and out to no avail. Are there some lingering config files residing on the HDs th…

U-boot defaults to "In: serial" and also listens for packets (its assumed that its a keyboard/terminal) so that a keypress can stop autoboot. I am successfully using /dev/ttyS2 after modifying /boot/armbianEnv.txt (Console=Display) and masking the gettyS2 service. The device/system I have connected to UART2 (/dev/ttyS2) periodically sends bytes. Thus, if a remote restart or a cold boot is performed (power glitch or power reset) while that system is connected to UART2, it triggers the abort of Autoboot. Requiring the other system/device to be disconnected from UART2, a cold boot of the RockPi4 and then reconnection of the system/device to UART2. I…

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

Hey, posting this in hopes that someone might have an ideas as to why this is happening. I've been dealing with an issue with my ZFS pool for a while now where the pool gets suspended but there are no other error indicators. WARNING: Pool 'rpool' has encountered an uncorrectable I/O failure and has been suspended. I'm using ZFS on top of LUKS and used to have problems with my drives resetting due to SATA errors, but I haven't really seen that issue since I started using my own SATA cables and limiting SATA speed to 3 Gbps. My working theory for last week has been that it's a problem with the CPU, perhaps some handover between big.LITTLE. So I've t…

Hi guys, I am using Orange Pi 4 (RK3399) and put in a SD card Armbian buster (and other time bionic) from the official web site but nothing happens. I have tried so many times using dd command from my debian OS and windows tools to write image on SD card but nothing again. When I start the board with Android the SD card could be read by android, but when I reboot just the red led shines and the screen of monitor doesn't show nothing. I would like some help because I would use my board in my project of postgraduate. Nowadays I am so disappointed with this problem. Best regards.

Hi all, So if a lot of you maybe know is a heatsink and fan a must for the OrangePi 4. With my temporarly installed fan makes a lot of noise i maked yesterday the step to order a Noctua NF-A4x20 5V PWM. The price was arround €17,- not the cheapest but te reviews are amazing. Even on full speed its a lot more silence then the 20x20 mini fan but with a good air flow. But as you could read did i choose for a PWM variant so i could control the rpm´s with a PWM GPIO pin. And amazingly it did work! I have the PWM pin connected to pin 7 of the OrangePi 4. Commands to start pwm for the first time: cd /sys/class/pwm/pwmchip1/ echo 0 …

The second USB port of NanoPI R4s is not working -- the logs were created with a USB disk inserted in port 2. # lsusb -t /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M |__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=pl2303, 12M If I remove and swap the USB devices: # lsusb -t /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M Other user…

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…

Hello together, I'm using this board inclusive PoE - Board with the ARMBIAN - Image. Now I have a question about the FAN on this PoE - Board. Does anyone know, how can I enable the FAN permanently, because the heat from the CPU is to high and I don't want to kill this board with overheating..... Best regards Matthias

My Helios64 setup has been running stable for months now (except for one MOSFET that failed and had to be replaced), however after recent updates using the OMV5 package manager I am unable to transfer files to my computer (SMB shares). When trying to transfer to a Windows computer the transfer speed immediately plummets to 0, stays there forever or File Explorer crashes/stops responding. When transferring to an Ubuntu system the transfer time outs. I can browse the files on the SMB share, I can play them (movies, music, etc) or run them directly with no issues. I can transfer files using scp with no problem (just at much reduced speed/bandw…

I've been having HDD/SATA issues with my zfs pool, as have many others. Now my HDDs will not spin up or be recognized when on slot 1 or 2. What's wrong, how to check and what to check? Any help appreciated.

My Helios has been running well for the most part stable for the past few weeks however last night i noticed when looking at my file systems in omv that my 14 GiB eMMC drive which houses my ambian install is at 13.13GiB and looks to be growing. Normally this sits around the 5 GiB. I have checked my docker install for anything suspicious but my plex docker is only taking up about 400mb. looking at my system logs i am getting a repeated this error which is new and might be related however i am not really sure what program is casing it. Jun 10 17:32:27 localhost rsyslogd: [origin software="rsyslogd" swVersion="8.1901.0" x-pid="1322" x-info="https://www.r…

Hi there, Just got OPi4 after some problem from Chineses... Problem: - no at all output at HDMI (connected to HDMI-VGA converter and 1920x1024 VGA LCD display, works with OPi PC+), - if Eth connected device gots (after few minutes) IP from DHCP. - no server running on that IP (tried telnet, ssg, WWW), PING works. uSD card with Armbian Buster for OPi4. What to check next? Console? What speed? 115200 or 1.500.000?

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.

If someone of you likes karaoke I highly can recommend running UltraStar Deluxe (OpenSource SingStar clone) on the Rock Pi 4. https://github.com/UltraStar-Deluxe/USDX I‘ve used the Focal gnome desktop 5.10 image and built UltraStar Deluxe as described. Performance is very good!!! Even with 1080p videos I can‘t see a difference compared to my desktop pc. With the original wireless PS3 SingStar microphones this is a pretty nice and portable setup.

Hello, today i try a USB C to HDMI Adapter and i get some picture on tv but it´s really unreadable and my log is full of this: rockchip-vop ff8f0000.vop: [drm:vop_plane_atomic_update [rockchipdrm]] *ERROR* Maximum dst width (3840) exceeded it is possible to restrict the resolution in the terminal? i think this error ocure because to high resolution or wrong detection Thank you

Fresh install of Armbian_21.05.1_Rockpi-4b_buster_current_5.10.35 Ran apt update/upgrade Reboot arm-config>softy>install linux headers It seems to be affecting the latest release only. Tested with Armbian_21.02.3_Rockpi-4b_buster_current_5.10.21 and it works until it's upgraded. I also tried disabling kernel upgrades before upgrading and still received this error.

hi all. I recently updated my Kurnel and rebooted my Helios64. when it loaded in to OMV i noticed my raid drive is missing. i can still see the disks just not the raid drive . Checking on the array i can see it failed with an error 524. Would love some suggestions on how to repair the array. below is the details i was able to get,.. sorry for the large info dump root@helios64:~# mdadm --run /dev/md0 mdadm: failed to start array /dev/md0: Unknown error 524 root@helios64:~# mdadm -D /dev/md0 /dev/md0: Version : 1.2 Creation Time : Mon Dec 14 16:49:07 2020 Raid Level : raid0 Raid …

Hello, i did an update of the system (apt dist-upgrade), and after the system doesn't start anymore. I use internal MMC, so I tryed to use last Armbian buster (Armbian_21.02.3_Helios64_buster_current_5.10.21.img) from sd card and it works. I mounted the MMC, fsck and finally chrooted into it and did an apt update and dist-upgrade, I atach the console log, the system hangs on Starting Kernel. helios64_20210514.txt

This is the uart output of the latest image Armbian_21.05.1_Nanopct4_focal_current_5.10.35.img.xz DDR Version 1.24 20191016 In Channel 0: LPDDR3, 800MHz CS = 0 MR0=0x58 MR1=0x58 MR2=0x58 MR3=0x58 MR4=0x2 MR5=0x1 MR6=0x5 MR7=0x0 MR8=0x1F MR9=0x1F MR10=0x1F MR11=0x1F MR12=0x1F MR13=0x1F MR14=0x1F MR15=0x1F MR16=0x1F CS = 1 MR0=0x58 MR1=0x58 MR2=0x58 MR3=0x58 MR4=0x3 MR5=0x1 MR6=0x5 MR7=0x0 MR8=0x1F MR9=0x1F MR10=0x1F MR11=0x1F MR12=0x1F MR13=0x1F MR14=0x1F MR15=0x1F MR16=0x1F Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=32 Size=2048MB Channel 1: LPDDR3, 800MHz CS = 0 MR0=0x58 MR1=0x58 MR2=0x58 MR3=0x58 MR4=0x2 MR5=0x1 MR6=0x5 MR7=0x0 MR8=0x1F MR9=0x1F …

Dear all, I am highly interested in the Helios64 and registered for the next batch. Here are a few questions, I hope that your guys can answer. The OS is Embedded Debian I assume. Questions are quite simple: 1) Hard drive numbering on startup Under Debian, the hard drives in a RAID array are renumbered on each startup by random: /dev/sda, /dev/sdb, etc ... This means that if drive /dev/sdb fails ... it is not necessarily the second hard drive in the bay. I already lost a RAID server extracting the wrong disc in an array. Then I migrated to a Synology NAS and notices that this problem had been fixed as dis…

Hi. I am going to be crazy with this bad SBC (it is not the RsbPi killer!!). Armbian recognize Bluetooth and the PCIe M.2 drive but not the mDP, that I want because the HDMI one is not well soldered. I need the NVME disk too. But I am writing because in the Radxa forum they said that there is a patch to solve this mDP issue. They told me that it is simple to solve!!! But I did not understand what I can do with these codes. I send the link that they gave to me. Thanks for the help. Patch_github

@Igor Kernel enabled Bootsplash works great on the recent 20.08 on Orange Pi 4. However there is a delay of around 20 - 30 seconds before this Bootsplash comes up. Is is possible to enable bootsplash on u-boot also on this image? I built a custom image 20.08-trunk with option "Kernel enabled bootsplash' disabled however could not see u-boot bootspalsh on this image. -Rajesh

I'm working on a new distro which is an ARM port of slackware64-15.0 beta. The cooked image is here: http://mirrors.aptalaska.net/slackware/slarm64/images/helios64/ This image is built using the build scripts at https://gitlab.com/sndwvs/images_build_kit/-/tree/arm/ The high level view is that it's downloading the kernel from git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git (linux-5.12.y) then applying the patches found at https://gitlab.com/sndwvs/images_build_kit/-/tree/arm/patch/kernel/rk3399-next then builds the kernel with config https://gitlab.com/sndwvs/images_build_kit/-/blob/arm/config/kernel/linux-rk3399-next.config…

I originally installed Armbian witk Kernel 4.4 on my Nanopi.m4 and later upgraded it to 5.10 via armbian-config. Things work fine but whenever I got a new update via apt update, things get messed up a bit the /boot/Image got linked to vmlinux-4.4.213-rk3399 instead of vmlinuz-5.10.35-rockchip64 while others uInitrd -> uInitrd-5.10.35-rockchip64 dtb -> dtb-5.10.35-rockchip64 The result's the board couldn't boot-up, when I restarted it. And, I need to correct the Image -> vmlinuz-5.10.35-rockchip64 and doing mkimage -C none -A arm -T script -d boot.cmd boot.scr from another linux machine to the SDCard. It works fine …

Despite this being the supported image advertised for the board, it just does not boot on this board, whereas the "current" image does boot (but with limited hardware support). I'm booting with just the serial console connected, to limit interferences On serial console with default config I get: Found U-Boot script /boot/boot.scr 3185 bytes read in 4 ms (777.3 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 117 bytes read in 3 ms (38.1 KiB/s) 7861795 bytes read in 361 ms (20.8 MiB/s) 20770824 bytes read in 941 ms (21.1 MiB/s) 104363 bytes read in 11 ms (9 MiB/s) 2698 bytes read in 7 ms (376 KiB/s) Applying kernel provided DT fixup…

Hi, hopefully my english and my linux skills are good enough (little bit experience with raspi and odroid i´ve setup Rock Pi 4 C with nvme boot from spi (first mmc) Armbian 21.02.3 Buster with Linux 5.10.21-rockchip64 after some difficulties to setup boot from nvme it is running on ADATA SX6000PNP when i perform reboot - mostly no reboot after disconnect power and reconnect no boot until i wait > 1 minute during the day i try sudo armbianmonitor - u and i get a link now when i use this command there is no more link serial console - i get no output but i can log in after a while Thanks

Armbian (I try a lot of versions include Armbian Focal xfce mainline based kernel 5.10.y) fails on Orange Pi 4B. 1. Orange Pi 4B booting normal, I try to do hard job and... it restarting every time after try to do hard job like build Qt or running benchmark and never boot normal again while powered. I need off power supply, on power supply and Armbian boot normal again and goto 1. I use Orange Pi 4B (on pcb v 1.4) with Ubuntu 18 from xunlong (Linux 4.4.179-g4cac54c6-dyrty). It works ok even I build big apps like Qt or run benchmarks. I also building my own Ubuntu 18 using xunlong script and it also working ok. Why I can't use Armbian fo…

Note that I want to use Hardware acceleration also later, but the issue is that it seems there's no HA for ffmpeg on the chip as you can see here. Thanks in advance!

Hello, Followed instructions and installed zfs, rebooted, installed all updated via apt update and apt upgrade, rebooted and situation is like this: root@helios64:~# zpool status The ZFS modules are not loaded. Try running '/sbin/modprobe zfs' as root to load them. root@helios64:~# modprobe zfs modprobe: FATAL: Module zfs not found in directory /lib/modules/5.10.21-rockchip64 root@helios64:~# apt install zfsutils-linux Reading package lists... Done Building dependency tree Reading state information... Done zfsutils-linux is already the newest version (2.0.3-1~bpo10+1). 0 upgraded, 0 newly installed, 0 to remove a…

Hi everyone! I bought a while a go few Rock Pi 4's for as a testing purpose and today while doing some laaarge malloc's it failed in really interesting manner; run out of memory. I did some stumbling with the code and did not find any bugs, so i looked for htop and was a very much suprised to see that my 2GB model has only 1GB total, /proc/meminfo reports same! Is this somekind of arm-specific thing that i do not just know? Memory chips (there is two of them) on the board is: NCLD4C1MA256M32 https://dl.vamrs.com/products/rock960/docs/hw/datasheets/FORESEE_LPDDR4_200ball_NCLD4CXMAXXXM32_10x14.5_VFBGA_Spec_B1_20170802.pdf 256Mb…

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 …

Hi all! Is it possible to configure Orange Pi 4 wifi to work in AP mode ? Will both 5ghz and 2.4 ghz be supported ? Thanks for advance in answer.

I notice the Helio64 hardware supports WOL, but I can't see anything in the Wiki about it (only Helios4) The Helio64 can draw some power with 5 spinning disks, I would love to have it sleep until needed. Is there any information on setting this up? I can see Autoshutdown plugin for OMV, but there is options for: Shutdown Hibernate Suspend Hybrid Sleep Suspend then Hibernate Does Helios64 support all these methods? Then once the unit is in some form of shutdown or sleep state, how can I make use to WOL to wake it up? Thanks.