Jump to content

Search the Community

Showing results for tags 'rockpi-4b'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Armbian
    • Armbian project administration
  • Community
    • Announcements
    • SBC News
    • Framework and userspace feature requests
    • Off-topic
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Standard support
    • Amlogic meson
    • Allwinner sunxi
    • Rockchip
    • Other families
  • Community maintained / Staging
    • TV boxes
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Support

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start






Website URL







  1. I loaded both the Raxda Debian OS and the Armbian OS on the Rock Pi 4A+ (4GB RAM / 32GB eMMC) integrated eMMC chip and both boot fine. I then ran the Phoronix pts/scikit-learn benchmark and got a big discrepancy in performance: https://openbenchmarking.org/result/2112285-NE-2112281NE08 The Raxda Debian OS (noted as rockpi4a+raxdadebian in the benchmark) performs basically the same as the Rock Pi 4A version (noted as rockpi4-rk3399 running Armbian), as expected. The Armbian OS (tested multiple times as rockpi4a-emmc, rockpi4a+, rockpi4a+governor, and rockpi4a+armbian) all perform terribly. Thoughts?
  2. 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] nvme nvme0: I/O 0 QID 0 timeout, disable controller [ 64.597365] nvme nvme0: Device shutdown incomplete; abort shutdown [ 64.598050] nvme nvme0: Identify Controller failed (-4) [ 64.598064] nvme nvme0: Removing after probe failure status: -5 Here is the log output of dmesg | grep nvme from "Boot from SD" root@rockpi-4b:~# dmesg | grep nvme [ 2.218883] nvme nvme0: pci function 0000:01:00.0 [ 2.218955] nvme 0000:01:00.0: enabling device (0000 -> 0002) [ 2.470965] nvme nvme0: 6/0/0 default/read/poll queues [ 2.473631] nvme0n1: p1 p2 Any idea what went wrong and how to fix it?
  3. 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
  4. 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
  5. 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.
  6. mboehmer

    Rock PI 4

    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
  7. 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
  8. 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.
  9. 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
  10. Problem: No usb power on all ports except for OTG port on Rock Pi 4C. Images: Ubuntu Bionic Legacy Desktop, Ubuntu Focal Legacy, Ubuntu Focal Current Desktop Monitoring information: Ubuntu Bionic Legacy Desktop - http://ix.io/2wlL Ubuntu Focal Current Desktop: http://ix.io/2wlZ
  11. 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 don't see any standard way to reconfigure things to avoid use of UART2 during U-boot and of course its useful for dealing with real issues to be able to interrupt autoboot and then interactively control what happens. Hence the best solution I can see would be for there to be a change to the armbian u-boot to look for a specific key or key sequence rather than just any old key/byte that hits the UART2 RX. Perhaps there could even be a parameter added for use in armbianEnv.txt that allows the abort Autoboot key or key sequence to be defined/redefined ? Thanks for any/all assistance
  12. 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
  13. 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.
  14. 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.
  15. 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
  16. 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
  17. 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 * 32 / 8 * 2 would be 2048MB right? I'm very interested of what my 4GB version has to say about it's memory size. :D Just wtf?
  18. Hi Distro Debian Buster, Linux rockpi-4b 5.10.21-rockchip64 #21.02.3 SMP PREEMPT Mon Mar 8 01:05:08 UTC 2021 aarch64 GNU/Linux I trying run HDMI-CSI bridge (auvidea B101) with board RK3399. Driver is loaded but dmesg not see any communications. root@rockpi-4b:/home/stream# lsmod |grep tc tc358743 40960 0 v4l2_dv_timings 36864 1 tc358743 v4l2_fwnode 28672 1 tc358743 videodev 299008 8 rockchip_vdec,v4l2_fwnode,videobuf2_v4l2,hantro_vpu,rockchip_rga,videobuf2_common,tc358743,v4l2_mem2mem mc 61440 7 rockchip_vdec,videodev,videobuf2_v4l2,hantro_vpu,videobuf2_common,tc358743,v4l2_mem2mem cec 73728 4 drm_kms_helper,dw_hdmi_cec,dw_hdmi,tc358743 root@rockpi-4b:/home/stream# root@rockpi-4b:/home/stream# dmesg | grep tc [ 0.000000] DMA zone: 261632 pages, LIFO batch:63 [ 0.000000] DMA32 zone: 262144 pages, LIFO batch:63 [ 0.043434] alternatives: patching kernel code [ 0.074404] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers. [ 1.251179] clocksource: Switched to clocksource arch_sys_counter [ 1.385194] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes, linear) [ 2.715888] rk808-rtc rk808-rtc: registered as rtc0 [ 2.716455] rk808-rtc rk808-rtc: setting system clock to 2021-03-16T14:28:55 UTC (1615904935) [ 2.729422] dw_wdt ff848000.watchdog: No valid TOPs array specified [ 4.090369] rk_gmac-dwmac fe300000.ethernet: Enable RX Mitigation via HW Watchdog Timer [ 6.540539] systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch when bootsplash is active being skipped. [ 8.278563] Console: switching to colour frame buffer device 240x67 [ 8.567718] Bluetooth: hci0: BCM4345C5 'brcm/BCM4345C5.hcd' Patch root@rockpi-4b:/home/stream# What is wrong, how this run? Bonmis
  19. Hi ! I spent several hours looking for the solution, here and elsewhere, I didn't find. The Radxa wiki speaks about 2 SPI: 1 and 2 The device tree README speaks about 4 SPI: SPI 0 pins (MOSI, MISO, SCK, CS): GPIO3_A5, GPIO3_A4, GPIO3_A6, GPIO3_A7 SPI 1 pins (MOSI, MISO, SCK, CS): GPIO1_A7, GPIO1_B0, GPIO1_B1, GPIO1_B2 SPI 2 pins (MOSI, MISO, SCK, CS): GPIO1_C0, GPIO1_B7, GPIO1_C1, GPIO1_C2 SPI 3 pins (MOSI, MISO, SCK, CS): GPIO2_B2, GPIO2_B1, GPIO2_B3, GPIO2_B4 So, the correspondence seems to be: radxa SPI 1 <=> DT SPI 1 radxa SPI2 <=> DT SPI 3 With the latest kernel (5.10.12-rockchip64, Debian buster I tried these configurations: overlays=spi-dev param_spidev_spi_bus=3 and overlays=spi-dev spi-add-cs1 param_spidev_spi_bus=1 param_spidev_spi_cs=1 The first doesn't boot and the second gives the error: [ 2.500481] rockchip-spi ff1d0000.spi: cs1 >= max 1 [ 2.500499] spi_master spi1: spi_device register error /spi@ff1d0000/spidev [ 2.500516] spi_master spi1: Failed to create SPI device for /spi@ff1d0000/spidev I didn't tried the SPI1 because I boot on NVME (SPI1 flash). But this is not mandatory. I could use an SD card or eMMC to boot if it is necessary. Please, how can I achieve the desired configuration: activate GPIO SPI ? Regards
  20. Hello, i want to use a NRF24L01 on my Rock PI 4B. I found out that i cannot enable spidev0.0 because this is corresponding with the network interface. Linux rockpi 5.4.32-rockchip64 #20.02.11 SMP PREEMPT Tue Apr 14 17:30:19 CEST 2020 aarch64 GNU/Linux Linux version 5.4.32-rockchip64 (root@builder) (gcc version 8.3.0 (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36))) #20.02.11 SMP PREEMPT Tue Apr 14 17:30:19 CEST 2020 My armbianENV looks like this: verbosity=1 overlay_prefix=rockchip overlays=spi-add-cs1 spi-spidev param_spidev_spi_bus=1 rootdev=UUID=3c50a1d1-71a5-4a0f-9899-099b17a1050b rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u When i set param_spidev_spi_bus=0 then the board boots up without eth0 (no ethernet) when i use bus=1 then it works. My Problem is i want to use Mysensors, i get no errors but my NRF does not receive any signal. Has someone ever done this before?
  21. It is my first RockPi 4 board and first Armbian install - board working OK with official Radxa image (Debian 9) and eMMC drive. Since my plan is to use just CLI I'm trying to install Armbian Buster images. Unforunately both "current" and "legacy" versions are not booting up. I have used SDFormatter (just in case) and Balena (as usual) on 16B Transcend Premim and 32GB SanDisk Ultra (A1) cards - same result: board is powered on but nothing happened at all. Only green diode is lighting but no signs from SD card (red diode is not showing up). eMMC card not connected in both cases. I have checked other topics (i.e. ROCK64) but can not find a good solution how to proceed - your help is much appreciated.
  22. Hello, With the new version for rockpi 4 (Buster Kernel 5.X). I put in my armbianEnv.txt: overlays=uart2 console=display my ttyS2 has a very weird permission compared to other, (on the other hand I don't have this problem at all on a 4.X kernel) crw-rw---- 1 root dialout 4, 64 Dec 23 14:00 /dev/ttyS0 crw-rw---- 1 root dialout 4, 65 Dec 23 14:00 /dev/ttyS1 crw--w---- 1 root tty 4, 66 Dec 23 14:01 /dev/ttyS2 crw-rw---- 1 root dialout 4, 67 Dec 23 14:00 /dev/ttyS3 crw-rw---- 1 root dialout 4, 68 Dec 23 14:00 /dev/ttyS4 crw-rw---- 1 root dialout 4, 69 Dec 23 14:00 /dev/ttyS5 crw-rw---- 1 root dialout 4, 70 Dec 23 14:00 /dev/ttyS6 crw-rw---- 1 root dialout 4, 71 Dec 23 14:00 /dev/ttyS7 how do i get my uart2 to work properly? Namely that I have already tested adding the tty groups to my user. made a chmod 660 on the S2 but it does not hold. Tks ;)
  23. 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. 2.2 Board boots normally from NVME drive (as always with a long delay after power up). apt-get update, apt-get upgrade. Kernel 5.4.49 -> 5.8.12 2.3 Reboot. Board does not want to reboot. 3.1 get Armbian_20.08.1_Rockpi-4b_buster_current_5.8.6.img.xz and write it to NVME drive. Does not touched armbianEnv.txt as it's already have fdtfile=rockchip/rk3399-rock-pi-4b.dtb line. 3.2 Board does not boots. As a conclusion from these experimenst I see, that Armbian works perfectly with EMMC module and any versions of the kernel. But new kernels (5.8.x) does not allows Armbian boots from NVME drive. Right now I don't have access to serial adapter, so I can't get boot log :( But this problem can be reproduced very easyly for some minutes with clean 20.05.3 install on NVME drive: just run apt-get update && apt-get upgrade && reboot and system will die.
  24. Title pretty much summs it up! I had a few problems getting my RockPi 4 to boot anything from SSD, but I did mangage too by compiling the current buster branch as a minimal image. I also created a thread on the radxa forum: https://forum.radxa.com/t/trouble-booting-armbian-from-nvme-ssd/4362 With the current image on the website (buster - server - 5.8.y) my bootlog looks like this: BUT! The minimal image I compiled works just fine ... aslong as I dont install webmin. Webmin is a web dashboard to configure and administer a server and I love to use it for my small Raspberry server. But for some strange reason, armbian just wont boot after I install webmin and restart. I tried installing all the dependencies first and rebooting, that works just fine. Installing webmin itself does not. The bootlog ends exactly the same: So, my best guess is both the default image and webmin configure something that causes these issues. Any ideas?
  25. 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.
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines