Jump to content

Search the Community

Showing results for tags 'rockpro64'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Community
    • Announcements
    • Feature Requests
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Upcoming Hardware (WIP)
    • News
    • Odroid M1
    • ROCK 5B
    • Orange Pi 5
  • Maintained Hardware
    • Board does not start
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Unmaintained (CSC/EOL/TVB) / Other
    • TV boxes
    • Off-topic
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start






Website URL







  1. First off this is not a Rockpro64 it is a Rock64 Ver. 2 which the tags field would not let me enter. A couple years ago when I first started playing with the Rock64, I briefly used armbian as the OS. The flickering video was annoying so later I tried Manjaro which worked fairly well. Recently the (Manjaro/Arch) updates (as well as latest images) completely break the HDMI output. Since the system was rendered usless, I downloaded the latest Armbian Jammy hoping for better results. The image loaded from SD fine, I did updates manually fine, and it rebooted fine. The only problem I experience is that that anoying HDMI video flicker. It's worse when there is any system activity, IE: if the mouse is rolled over an Icon, or if that icon is clicked, the screen becomes a blur of random horizontal lines as the screen jumps. I've looked but havn't found a comprehensive solution to this issue; much of what is out there is "old news" can anyone steer me in the right direction to fix this?
  2. Hello! I'm trying to get Armbian jammy latest to boot on my new RockPro64. I've tried both the CLI and XFCE images, flashed with Balena to a good SanDisk uSD card. Both boot into U-Boot but then fail to find a partition on mmc 1. Checking the SD card there's only 1 Linux partition and no FAT one. I tested with a Debian image on the same SD card (DOS + Linux Partition) and it booted into the installer no problem. Any ideas? Thanks! (Also asked on Pine 64 Forums, I will update/close this if they resolve it or vice/versa.)
  3. armbian-config has a way to update the kernel within a major version but can one upgrade from 5.15 to 6.1 (current/edge). I assume if not then I have to build my own image? What I am after is jammy or bullseye with 6.1 kernel to support some hardware not supported in 5.15. I know the rolling releases (Lunar/Sid) have this kernel but I need a LTS release with 6.1.
  4. I've got jammy running but I have a dsi display for the board and I'd like that to work (well the tp port too) with jammy. Looking at armbian config I see no setting for it. I know the display works fine as if I load an aryufan android image it works as it is set to use DSI by default. Does this kernel know about the DSI port? Do I have to build a custom kernel? If not then what boot env line will get it going?
  5. Hello, I've installed the 22.11 version with the 5.15 kernel on the microSD card. I've a rockpro64 with the SSD adapter and a WD black 250GB nvme. The system doesn't recognizes this drive. I've tested the latest stable ayufan image (kernel 4.4) and it recognises it perfectly. Should I downgrade the kernel to the 4.4 branch? Any help would be appreciated. Thanks,
  6. IT'S FINALLY HERE... THE OFFICIAL ROCKCHIP-LEGACY MULTIMEDIA INTEGRATION After two years of using a separate script to enable the multimedia features in RK3399 Legacy Kernel, the whole framework has been incorporated to the official Armbian packaging system. The choice distro for this integration is Debian Buster (see FAQ at the end of this post about the reasons). I. Installation Download a Armbian Buster Legacy Desktop image for your board, and install it with the standard Armbian method. Install the complete multimedia solution with sudo apt update && sudo apt upgrade sudo apt install media-buster-legacy-rk3399 --install-recommends The switch "--install-recommends" will add the whole Kodi binary addons collection (retro-gaming cores, music visualizations, screensavers, additional media decoders/encoders, vfs, etc.), plus the GLES-to-OpenGL wrapper "gl4es". II. Features Accelerated GLES/EGL X desktop: No action needed. Accelerated Chromium, with WebGL and video display acceleration: No action needed Desktop video player capable of smooth 4K HEVC-HDR: Use the "Rockchip Gst Player" from the Multimedia menu, or choose it with right-click on the media file. Command-line 4K playing is also possible with "gst-play-1.0 --videosink=kmssink". RKMPP-accelerated MPV: Use normally for standard operation (windowed with mouse-operated GUI). For fullscreen, keyboard-operated mode, use the command line switch "--gpu-context=drm" (this will allow you to play smooth 4K). - See instructions below, in the next post, for playing YouTube videos up to 4K with this MPV. ISP Camera with real-time h.264/1080p HW encoding: Using the Gstreamer Plugin. Check this wiki for instructions on how to use it. Most of it applies to Armbian, except for the selection of ov5647/imx219 camera, which must be done using DT overlays. OpenCL 1.2 support: It will be fully functional, no further action needed. You can download some tests and examples from this link. Kodi 18.9 Leia with full RKMPP+GBM acceleration, 4K-HDR capable: You can start it from LightDM menu as your user account: Alternatively, you can also run it as a system service with these command lines: sudo systemctl disable lightdm sudo systemctl enable kodi-gbm sudo reboot Full collection of Kodi binary add-ons: Includes retrogaming cores, media encoders and decoders, PVR, screensavers, vfs and audio visualizations. They are all installed with the package "kodi-addons-full", but are disabled by default. They need to be enabled individually within the Kodi GUI. OpenGL 2.1 support through the gl4es wrapper: It is installed with the package "gl4es", with no further action needed. III. Sources This is the list of the sources used for the packages: IV. FAQ ¿Why did you use Debian Buster as a base for this implementation? It was the most appropriate for several reasons. Upstream Rockchip-Linux developers use Debian buster, so the software could be ported with less modifications than if we chose a different distro. Besides, it is a completely stable distro, unlike Bullseye, which is a moving target as of today. It also has Chromium as a package, unlike Focal that uses snap instead. For last, it has a good backports repo, with several libs that would otherwise need to be compiled and maintained if we chose, for example, Focal. ¿Why Legacy instead of Mainline? This is an implementation based on the vendor's BSP kernel. It has been tested and is reliable, which many people will prefer rather than having a bleeding-edge, less stable implementation. In addition to that, Mainline upstream multimedia support is still a WIP, and lacks many features that are only present on Legacy kernels. ¿Will you add new features to this implementation? No, this implementation will only receive bug fixes if necessary. From now on, all multimedia work will be focused on Mainline and recent distros (like Focal or Bullseye). All new features will go there.
  7. Dear Armbian community, Yesterday morning, after apt upgrade my Rockpro64 not boot (the white and red led stayed lit). After some tries I managed to get a boot again but I now have a "init not found" error, as you can see on the screenshot. What have been done so far : - Install an Ubuntu as "debug" platform - Follow the recovery steps from Armbian website - Put on eMMC storage a 5.15.63 by copying the files from Armbian - Check if UUID was consistent between partition, boot config, ... ==> this is the case - Made a fsck : no errors found ==> I would like to try this : https://askubuntu.com/questions/910218/sbin-init-no-such-file-or-directory-not-able-to-boot-ubuntu-desktop, but need to have a boot prompt (how to get it ?) If somebody has any other hint... I would take it I have spent hours on the setup of my Rockpro64, I would avoid to reinstall it. Regards.
  8. is it possible to get edp on rockpro64 working with armbian
  9. Hi all, I am a newbie here. Is there a way to install ZFS on RockPro64 RK3399 with the latest Armbian release (doesn't matter if it is bionic, buster or focal)?
  10. Hi guys I have experienced a lot of system instability with the rockpro64 on debian and armbian as explained here: https://forum.pine64.org/showthread.php?tid=17083 and here: https://github.com/monero-project/monero/issues/8473 I think the solution lies in what the guys are discussing here: https://forum.pine64.org/showthread.php?tid=7387 Can someone please give me a clear set of instructions on how to create an image to boot with with lowered ddr clock frequency? Presumably from the files listed here?: https://github.com/rockchip-linux/rkbin/tree/master/bin/rk33 i.e.: files such as rk3399pro_ddr_666MHz_v1.27.bin rk3399pro_miniloader_v1.26.bin Thanks!
  11. Im looking for a functioning, easy to install fan script for my RockPro64 installed with Armbian Jammy. Iv searched around and found a few unmaintained projects but Its not something iv ever done before so wanted to ask what others use. Although I do have some experience in the terminal I'm still relatively new to it so im hoping there is something with good step by step documentation. If anyone can assist Id be appreciative. Many thanks.
  12. I'm trying to get this rockpro64 board to boot off of pxe/nfs. I'm able to get it to boot into armbian and to the point where it asks for the new root password. But something happens on the device where the network gets disabled which stops the NFS connectivity and the rest of the system with it. All traffic stops on the device and it becomes unreachable. NFS traffic stops, it no longer responds to pings, etc. It's not entirely frozen, for example it prints kernel messages to console if the ethernet is pulled. And after a few minutes the nfs connection times out and it starts printing this over and over. It always happens about 75 seconds after boot. It leads me to think there's some job or process that's running on the base OS install that somehow interrupts the connection. this is the pxe config file I'm using. and I'm using the current bullseye server image from Aug 31, 2022 default l0 menu title U-Boot menu prompt 0 timeout 50 label 10 menu default kernel root/boot/Image fdt root/boot/dtb/rockchip/rk3399-rockpro64.dtb initrd root/boot/uInitrd append loglevel=8 root=/dev/nfs ip=dhcp rootwait rw earlyprintk nfsroot=
  13. Hi everyone. I’ve been facing some issues with my RockPro64 lately, running on a dedicated version of Ambian for this sbc. Earlier, I was using a USB Bluetooth module with it for playing audio on my speakers (via Logitech Bluetooth adapter), and it worked perfectly fine. I wanted to save some USB ports so I decided to replace the module with a ROCKPro64 1*1 Dual Band WIFI 802.11 AC/BLUETOOTH 5.0 MODULE. But ever since I’ve done that, the audio quality is choppy and inconsistent. Receiver and transmitter are located closely, so I don’t think it’s a signal issue. It seems like a hardware or a software issue, but I’m not sure what could it be. I’d appreciate any help with troubleshooting or diagnostics. Thanks in anticipation!
  14. Hi, Has anyone tried compiling zfs? According to google it should work out of the box? However, when I try to install, zfs dkms is saying that the module will not be compiled due to missing kernel headers. Fine, but where are the headers? I'm using a fresh install from https://www.armbian.com/rockpro64/ armbian-config - Software - headers_install does nothing, installing linux-headers-current-rockchip64 installs 22.05.4, not 22.08.1 that I have, and "compiling headers", whatever that might be, fails how do I get a matching kernel and headers, any version? root@rockpro64:~# dpkg -l | fgrep rockchip ii linux-dtb-current-rockchip64 22.08.1 arm64 Armbian Linux DTB, version 5.15.63-rockchip64 current ii linux-image-current-rockchip64 22.08.1 arm64 Linux kernel, armbian version 5.15.63-rockchip64 current root@rockpro64:~# apt upgrade -y linux-headers-current-rockchip64 Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: linux-headers-current-rockchip64 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 12.1 MB of archives. After this operation, 80.2 MB of additional disk space will be used. Get:1 http://armbian.hosthatch.com/apt jammy/main arm64 linux-headers-current-rockchip64 arm64 22.05.4 [12.1 MB] Fetched 12.1 MB in 2s (6,470 kB/s) Selecting previously unselected package linux-headers-current-rockchip64. (Reading database ... 42002 files and directories currently installed.) Preparing to unpack .../linux-headers-current-rockchip64_22.05.4_arm64.deb ... Unpacking linux-headers-current-rockchip64 (22.05.4) ... Setting up linux-headers-current-rockchip64 (22.05.4) ... Compiling headers - please wait ... scripts/sign-file.c: In function ‘display_openssl_errors’: scripts/sign-file.c:89:9: warning: ‘ERR_get_error_line’ is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations] 89 | while ((e = ERR_get_error_line(&file, &line))) { | ^~~~~
  15. I am able to boot and install with an sd card, but am unable to get through first boot with the image on an emmc card. The failure on the emmc card is between /scripts/local-premount and /scripts/local-block it fails with gave up waiting for root file system device ... alert! UUID=ed78b... does not exist. dropping to shell! and I am at a busybox shell in (intramfs) I was wondering if booting from the emmc card was expected to work, or if anyone could remember what needs to be tweaked for the kernel to find the root filesystem on the emmc card. Cheers
  16. Myy

    Mainline VPU

    So, I tried to adapt @Kwiboo and @jernej patches on my 5.6 branch, but this made the kernel fail to boot for no visible reason. Since I were able to boot it without the VPU patches, I'm convinced that it's their readaptation that broke something. The patches applied are here : https://github.com/Miouyouyou/RockMyy64 If someone wants to play with them and determine which one break the boot process.
  17. Hello, Armbian 22.02 images doesn't boot on rockpro64. I have tried: Armbian 22.02 Bullseye Armbian 22.02 Jammy XFCE It doesn't boot (not blinking white led). Previous builds works correctly: Armbian_21.08.1_Rockpro64_bullseye_current_5.10.60
  18. I've tried the latest CLI and GUI images. I tried different microSD cards but the result is the same. Both images get to Booting using the fdt blob and never progress. Is there anything I can try to get this working?
  19. Only "chirps and chips" come through during extended playback. Only hdmisound device is affected, not analog. Duplicate of improperly "resolved" thread Armbian 22.02 Bullseye Kernel 5.15.25-rockchip64 Armbian 22.02 Bullseye Kernel 5.16.16-rockchip64 working in 5.10.60-rockchip64 steps to reproduce: aplay -D plughw:1,0 /usr/share/sounds/alsa/Front_Right.wav dmesg | grep es83 [ 10.077582] es8316 1-0011: Failed to get IRQ 0: -22 card 0: Analog [Analog], device 0: ff890000.i2s-ES8316 HiFi ES8316 HiFi-0 [ff890000.i2s-ES8316 HiFi ES8316 HiFi-0] Subdevices: 0/1 Subdevice #0: subdevice #0 card 1: hdmisound [hdmi-sound], device 0: ff8a0000.i2s-i2s-hifi i2s-hifi-0 [ff8a0000.i2s-i2s-hifi i2s-hifi-0] Subdevices: 0/1 Subdevice #0: subdevice #0
  20. Hello, I would like to know more informations about this test made with the Asus XG-C100C Network Adapter or, generally, how to optimize the speed from a 10GbE PCIe Network Adapter in the RockPro64. Which version to use of Armbian and how to get that version to have so good performances? Which version of the Adapter driver to use? Were the drivers included in the Kernel or did you use the Asus driver recompiled? I would be very grateful if you will help me. Thank you.
  21. I have installed clean CLi option of Armbian_21.08.1_Rockpro64_focal_current_5.10.60.img from the archives I have fully apt updated/upgrade OS and now am at 5.15.25-rockchip64 I noticed there was no sound coming out of the HMDI only from 3.5mm Jack Alsamixer has: (volume bar with up/down instead of 1 increments jumps 0>28>56>100 - I d like to fix this) Pulsemixer (CLi) solved my problem by simply while playing an audio stream/file I swapped (made default the bottom Built-in Audio Stereo) Also on Cards tab (use tab to move keys F1-F3 didnt work for me neither on Tinker nor here) i have. Sound now comes out of HDMI fine. Jack I swap back to top option I guess
  22. In Alsamixer its missing the master volume. In older legacy images it was there and driver seemed to be a tinker rockchip driver? Any idea how to enable the master volume slider? If I increase volume in USB sound card (headphones) then no sound comes out at HDMI and only way to restore is to purge deb of pulseaudio and alsa and re-install. There are some errors also the moment i log into cli if I do above. If reproduced ill post here (update). Similar error posted on another topic/board If i test `aplay /usr/share/sounds/alsa/Front_Center.wav` its ok. After any change to alsamixer nothing comes out The errors that started after changing alsamixer volume as per above are:
  23. Hello, using the image provided at https://www.armbian.com/rockpro64/ the board works when booted via uSD card but not via MMC. There appears to be no device mode USB drivers installed. I pulled the kernel sources with `armbian-config` and compiled them myself making sure to select dual-mode support for the DWC2 and DWC3 drivers. The kernel boots after install, but I still see nothing in /sys/class/udc and am unable to see any dwc2/3 drivers (save dwc2_pci and some dwc3 i3c drivers). I'm able to load libcomposite, the configfs driver, but that does not pull in a USB device mode driver. I'm unable to attach armbian monitor status right now but will update my post with it.
  24. Hi, I have had some issues trying to boot from eMMC with the last version of Armbian (kernel v5.4) while it's working perfectly on Armbian with a v4.4 kernel. Images not working: https://dl.armbian.com/rockpro64/archive/Armbian_20.05.2_Rockpro64_bionic_current_5.4.43.img.xz https://dl.armbian.com/rockpro64/archive/Armbian_20.05.4_Rockpro64_focal_current_5.4.46.img.xz Working image: https://dl.armbian.com/_old/rockpro64/archive/Armbian_5.98_Rockpro64_Debian_buster_default_4.4.192.7z I though I messed up with the SPI or the eMMC card but after trying all I could, it finally worked using an old version of Armbian. The new images are working on a SD-Card but it's much slower to boot. On a eMMC card it get completely stuck (see attached file), I managed to get the "Done" displayed waiting much longer (just after the "Running /scripts/local-premount" step but nothing more). The CPU is becoming super hot while it stuck. I have the same issue on two different RockPro64 cards and with two different eMMC cards. I have tried the "Disable SPI while booting" step but it didn't help: https://wiki.pine64.org/index.php/ROCKPro64#Disable_SPI_.28while_booting.29 It would be great if I could have a kernel 5.4 running on eMMC on those cards, please let me know if I can help. Kind regards, Baptiste
  25. I was trying to enable i2c on my RockPro64, and when looking at the documentation in the overlay directory, it states this: rockchip (Rockchip) ### Provided overlays: - i2c7, i2c8, pcie-gen2, spi-spidev, uart4, w1-gpio ### Overlay details: ### i2c7 Activates TWI/I2C bus 7 I2C7 pins (SCL, SDA): GPIO2-B0, GPIO2-A7 GPIO1-C5, GPIO1-C4 ### i2c8 Activates TWI/I2C bus 8 I2C8 pins (SCL, SDA): GPIO1-C5, GPIO1-C4 Note that the "GPIO1-C5, GPIO1-C4" from i2c8 is accidentally included on the i2c7 pins line. I would submit a PR for this change, but ... I'm not sure where this document actually lives, and it's not easy to figure out. I see that @Igor is listed as the maintainer of the package, but that's not helping me find the source to submit changes. Also, for clarity, it would be nice to include that i2c8 is the pi-connector, and i2c7 is the Digital Video Port Happy to submit changes if somebody can point me to the right place. Thanks
  • Create New...