Search the Community

Showing results for tags 'rockpro64'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Community
    • Announcements
    • Feature Requests
  • Using Armbian
    • Beginners
    • Advanced users - Development
  • Upcoming Hardware (WIP)
    • Tech News
    • Khadas VIM4
    • Radxa Zero 2
    • Odroid M1
  • Supported boards
    • Board does not start
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Unsupported (CSC/EOL/TVB) / Other
    • TV boxes
    • Off-topic
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Old bug tracker - read only
    • Old bug tracker - read only
  • TV Boxes's General Chat
  • TV Boxes's Reviews/Tutorials
  • TV Boxes's FAQ
  • TV Boxes's TV Boxes running Armbian
  • TV Boxes's Rockchip CPU Boxes
  • TV Boxes's Amlogic CPU Boxes
  • TV Boxes's Allwinner CPU Boxes
  • Android's Forums
  • Gaming on ARM's Reviews
  • Gaming on ARM's Issues

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP


Skype


Github


Location


Interests

  1. 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
  2. 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
  3. 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:
  4. 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.
  5. 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
  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. 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
  8. 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.
  9. 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
  10. Hi, I am looking at investing in a RockPro64 NAS setup using the Pine64 Desktop casing and other necessary accessories. I'm hoping to run OpenMediaVault on it and have 2 3.5" HDDs attached. The entire setup would be configured to be a backup of my operational NAS (Helios4) in a different location (i.e. different room of the house). My reading of the forum and the armbian download section has me a bit confused. The download section indicates that the board is supported, but the forum indicates it's a WIP. Just trying to understand the status/stability of the board for what I'm planning on using it for and whether it would be a good investment or a waste of money. Also wondering whether this post regarding updating the CPU governor is related - and will be a benefit - to the RockPro64 as both the NanoPi M4 and RockPro64 share the same SoC RK3399. Thanks
  11. U need ixgbe to run my Intel X550T 10G Ethernet NIC. That module seems to be a part of linux-modules-$(uname -r) package. My kernel version is 5.10.60-rockchip64. However, I do not have linux-modules-5.10.60-rockchip64 available via apt. # apt install linux-modules-$(uname -r) Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package linux-modules-5.10.60-rockchip64 E: Couldn't find any package by glob 'linux-modules-5.10.60-rockchip64' I have apt downloaded linux-modules of some greater kernel release to make sure it provides ixgbe.ko. It does: # apt install --download-only linux-modules-5.11.0-40-generic # dpkg --contents /var/cache/apt/archives/linux-modules-5.11.0-40-generic_5.11.0-40.44~20.04.2_arm64.deb | grep ixgbe drwxr-xr-x root/root 0 2021-10-26 15:50 ./lib/modules/5.11.0-40-generic/kernel/drivers/net/ethernet/intel/ixgbe/ -rw-r--r-- root/root 665577 2021-10-26 15:50 ./lib/modules/5.11.0-40-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko drwxr-xr-x root/root 0 2021-10-26 15:50 ./lib/modules/5.11.0-40-generic/kernel/drivers/net/ethernet/intel/ixgbevf/ -rw-r--r-- root/root 148153 2021-10-26 15:50 ./lib/modules/5.11.0-40-generic/kernel/drivers/net/ethernet/intel/ixgbevf/ixgbevf.ko How do I get ixgbe for my actual kernel? Thanks, - Aleksandr
  12. Hello, I installed Armbian Hirsute xfce bleeding edge kernel 5.13.y on my RockPro64 4GB and updated it right after that. After restarting after the update, ethernet doesn't work anymore. (Wifi connecting icon is shown and no connection to ethernet) dsmesg says that the link is up. armbianmonitor: https://paste.ubuntu.com/p/9Yz8SJVrzS/ apt/history.log: https://paste.ubuntu.com/p/GQbfZp3Xch/ For apt history only the last two operations seem relevant. I assume the previous ones are made by whoever/whatever created the image.
  13. Hi, I'm not sure if it is a bug as by board seems to work correctly, however I thought I should post it. In the latest version (5.10.60-rockchip64) I'm getting a few errors in dmesg: debugfs: Directory 'power-domain' with parent 'pm_genpd' already present! I hadn't seen these errors in the previous version (5.10.43) Logs are here: http://ix.io/3yY5 Regards,
  14. After last apt upgrade (v21.05.4), lightdm on a RockPro64 does not start anymore. rockpro64:~:# systemctl status lightdm.service ● lightdm.service - Light Display Manager Loaded: loaded (/lib/systemd/system/lightdm.service; indirect; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2021-06-20 16:13:01 CEST; 21min ago Docs: manlightdm(1) Process: 1877 ExecStartPre=/bin/sh -c [ "$(basename $(cat /etc/X11/default-display-manager 2>/dev/null))" = "lightdm" ] (code=exited, status=0/SUCCESS) Process: 1880 ExecStart=/usr/sbin/lightdm (code=exited, status=1/FAILURE) Main PID: 1880 (code=exited, status=1/FAILURE) Jun 20 16:13:01 rockpro64 systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 5. Jun 20 16:13:01 rockpro64 systemd[1]: Stopped Light Display Manager. Jun 20 16:13:01 rockpro64 systemd[1]: lightdm.service: Start request repeated too quickly. Jun 20 16:13:01 rockpro64 systemd[1]: lightdm.service: Failed with result 'exit-code'. Jun 20 16:13:01 rockpro64 systemd[1]: Failed to start Light Display Manager. and trying to start manually as root rockpro64:~:# systemctl start lightdm.service Job for lightdm.service failed because the control process exited with error code. See "systemctl status lightdm.service" and "journalctl -xe" for details. rockpro64:~:# journalctl -xe Jun 20 16:36:33 rockpro64 systemd[1]: Failed to start Light Display Manager. -- Subject: A start job for unit lightdm.service has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit lightdm.service has finished with a failure. -- -- The job identifier is 1583 and the job result is failed. Jun 20 16:36:33 rockpro64 systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 5. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Automatic restarting of the unit lightdm.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Jun 20 16:36:33 rockpro64 systemd[1]: Stopped Light Display Manager. -- Subject: A stop job for unit lightdm.service has finished -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A stop job for unit lightdm.service has finished. -- -- The job identifier is 1648 and the job result is done. Jun 20 16:36:33 rockpro64 systemd[1]: lightdm.service: Start request repeated too quickly. Jun 20 16:36:33 rockpro64 systemd[1]: lightdm.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- The unit lightdm.service has entered the 'failed' state with result 'exit-code'. Jun 20 16:36:33 rockpro64 systemd[1]: Failed to start Light Display Manager. -- Subject: A start job for unit lightdm.service has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit lightdm.service has finished with a failure. -- -- The job identifier is 1648 and the job result is failed. running lightdm as root with debug enabled rockpro64:~:# lightdm --debug [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log [+0.00s] DEBUG: Starting Light Display Manager 1.30.0, UID=0 PID=3791 [+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-guest.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-log-backup.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/60-lightdm-gtk-greeter.conf [+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration dirs from /var/lib/flatpak/exports/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration dirs from /root/.local/share/flatpak/exports/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf.d/10-slick-greeter.conf [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf.d/11-armbian.conf [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf [+0.00s] DEBUG: Registered seat module local [+0.00s] DEBUG: Registered seat module xremote [+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager [+0.19s] DEBUG: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ?gio-vfs? [+0.20s] DEBUG: Monitoring logind for seats [+0.20s] DEBUG: New seat added from logind: seat0 [+0.20s] DEBUG: Seat seat0: Loading properties from config section Seat:* [+0.20s] DEBUG: Seat seat0: Starting [+0.20s] DEBUG: Seat seat0: Creating greeter session [+0.20s] DEBUG: Seat seat0: Failed to find session configuration slick-greeter [+0.20s] DEBUG: Seat seat0: Failed to create greeter session [+0.20s] DEBUG: Failed to start seat: seat0 Any ideas how to drill further down the problem?
  15. Hey folks... We are trying to use a DHT22 sensor on rockpro64 using armbian (buster)... Is there something we need to know about GPIO pin ? We are trying to compile and use this code as a starter... https://github.com/ayufan-pine64/dht22-pine64.git But we got a segfault when using it... thanks
  16. Hi everyone, I tried the 20.11.3 version of Armbian, I have manually updated the SPI with U-boot using armbian-config (after an apt update && apt upgrade), but it doesn't start from a PCIe NVME SSD :-/ Is there something that I have missed? Any idea is more than welcome ! Here is my serial - USB console output: Kind regards, Baptiste
  17. Hello, I own a RockPro64 and I'm using Armbian Legacy Buster 4.4.213-rockchip64. Everything mostly works, although I've had a pretty annoying issue. Reboot just doesn't work. Every time I do a 'sudo reboot' (or any equivalent for that matter, as for example 'sudo shutdown -r now') it doesn't work. Although it apparently reboots, the TV monitor to which my box it's connected via HDMI lose connection and all, nothing actually happens. Both the red and the white leds of the RP64 turn on and keep on all time (instead of just one of them blinking, as expected) and then it will work only if I poweroff and on again, either by unplugging the power cable or pushing the reset button. That's pretty annoying, since for obvious reasons I can't remotely reboot the machine... I noticed that it only happens with the legacy kernels (I've tried Armbian and Ayufan, both have the exact same behavior). Current kernels work properly, but I really need, at least for now, keep using legacy (I'm trying to use the tool provided by the developer JMCC in order to use Kodi and it doesn't work on mainline so fat). I've googled for a while for this specifc issue and used the search from this forum but found nothing. Any help would be very appreciated.
  18. 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!
  19. Board is RockPro64, legacy kernel - 4.4.213-rockchip64. The issue is this: [ 1451.681339] ohci-platform fe3a0000.usb: frame counter not updating; disabled [ 1451.681972] ohci-platform fe3a0000.usb: HC died; cleaning up [ 1451.682516] usb 8-1: usbfs: usb_submit_urb returned -19 [ 1451.682569] usb 8-1: USB disconnect, device number 2 It happens only on the USB2.0 ports with different keyboards, mice, custom USB HID device, webcam. The other 2x USB 3.0 ports are working fine with the same devices. Tried fixes so far - turning usbcore.autosuspend option off, adding usbhid.quirks for every device. extraargs=usbcore.autosuspend=-1 usbhid.quirks=0x10c4:0x85d4:0x00000400 The problem seems to be fixed in mainline kernel, as 24/7 test with continuous transfers to a custom USB HID device passes for 3 days that I tested. I cannot use mainline kernel since I need the VPU and GPU accelerated X with EGL. Any advice on fixing this in the legacy kernel is appreciated.
  20. THE MEDIA SCRIPT IS DEPRECATED, IN FAVOR OF THE LEGACY MULTIMEDIA INTEGRATION. PLEASE REFER TO THIS TOPIC: So finally we have the first version of: The UN-official, UN-supported, etc... RK3399 MEDIA TESTING SCRIPT This is the first release of the RK3399 media testing script. The script provides a functionality similar to its RK3288 equivalent: Installing all the libraries and system configurations necessary for GPU accelerated X desktop, Chromium WebGL, full VPU video play acceleration up to 4k@60 10-bit HEVC (the maximum supported by the SoC), and GLES 3.2 / OpenCL 1.2 support. Three video players supporting full VPU acceleration (RKMPP) and KMS display (GBM or a X11 DRM "hack", as described by the authors), namely: MPV, Gstreamer and Kodi. Two example programs using the OpenCL functionality: Examples form the Arm Compute Library, and a GPU crypto miner (an old version, but small and simple). A library that will act as an OpenGL to OpenGL-ES wrapper, allowing you to run programs that use OpenGL 1.5-2.0. Two additional features, that have no big interest from the Armbian development prospective, but I find them interesting to play with: Chromium browser with support for Flash and DRM-protected commercial web video streaming (tested with Amazon Prime, should also work with Netflix, Hulu, etc.), and a simple Pulseaudio GTK equalizer using LADSPA. Here is a more thorough documentation: >>> DOWNLOAD LINK <<< Prerequisites: You need a fresh Armbian Bionic desktop image with legacy kernel installed. Instructions: Download the file above Untar it: tar xvf media-rk3399_*.txz cd media-script ./media-rk3399.sh Notes: This script is not officially supported by the Armbian project. It is just a community effort to help the development of the main build, by experimenting with a possible implementation of the media capabilities of this particular SoC. Therefore, questions about the script should not be laid out as support requests, but as commentaries or community peer-to-peer assistance. That being said, all commentaries/suggestions/corrections are very welcome. In the same way, I will do my best to help solve any difficulty that may arise regarding the script. Enjoy!
  21. Is it just me .... all the time I start to use the Armbian web browser ...including simply loading this forum the whole RockPro64 OS locks up and I have to reset,. Typically its when I load Media web sites like the BBC ,.... but it even occurs when I load this forum!! I am trying to develop some C GPIO library to help the rockPro64 community, but its hopeless. I have to work on console and web brows on a laptop. I have ordered a KVM to help but this is really frustrating. Because the HW locks up I can not detect any issues in the logs and I don't know how to set up a HW trace in the graphics drivers. I have eliminated any Power issues. I have a pico cluster case and decent heatsink ... I have ordered some Heatsink fans but CPU is in the 40 Deg C. Any Ideas how I find out why the HW just freezes ? It must have something to do with the mali drivers ? Any ideas welcome
  22. hi all, I am wondering if there's any reason that CEC is not built into legacy kernel for RK3399. In https://github.com/armbian/build/blob/master/config/kernel/linux-rk3399-legacy.config, module dw-hdmi-cec is not enabled. # CONFIG_DRM_DW_HDMI_CEC is not set If no special reason, I can make a PR for this. Thank you!
  23. Hi, I have two rockpro64 boards. One board runs Debian buster with a slightly extended ayufan 5.4.0-rc1 kernel where as the other runs a Armbian (Debian) buster with the current project supplied 5.4.0-rc1 kernel. On the Debian on I have installed the nice ats solution (https://github.com/tuxd3v/ats#install) On the Armbian one the fan is running all the time. I tried to install ats there as well but I failed. Also I found that basically the /sys/devices/platform/pwm-fan/hwmon is not there, only upto pwm-fan I have. Is there some module I need to load or compile into the kernel to get ats working on the Armbian based one as well? Any hints are highly appreciated. Kind Regards Martin
  24. Hi! I just booted Armbian_20.08_Rockpro64_focal_current_5.7.15.img via sdcard , but HDMI output seems to stop after "Starting Kernel". Just after that I see some yellow/black vertical lines on my monitor and then the screen goes black, no more HDMI input on the monitor. Logging into Armbian on the RockPRO then works fine via ssh, can do the setup, update etc. So it looks like a problem with HDMI output? Anyone ideas how to solve this? Would like to have console terminal access via HDMI as last resort Thanks in advance! p.s. Just tried the Armbian_20.08_Rockpro64_focal_current_5.7.15_desktop which seems to have the same issue
  25. 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)?