Search the Community

Hi all, First post here. I have been running Armbian on my original Bananapi Pro for a long while now, and thought that it's time to upgrade from Bullseye to Bookworm finally. There were some complications with UsrMerge that I had to resolve manually (I think some boot files from the original Buster installation were both in /lib and /usr/lib), but apart from that the upgrade appears to have worked: All userspace stuff is on Bookworm. # lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Armbian 24.5.0-trunk.530 bookworm Release: 12 Codename: bookworm However, the kernel seems to be stuck on 5.15: # uname -a Linux bananapi 5.15.43-sunxi #22.05.1 SMP Sat May 28 08:17:47 UTC 2022 armv7l GNU/Linux This version number appears to be inconsistent with the contents of armbian-image-release: # cat /etc/armbian-image-release # PLEASE DO NOT EDIT THIS FILE BOARD=bananapipro BOARD_NAME="Banana Pi Pro" BOARDFAMILY=sun7i BUILD_REPOSITORY_URL=https://github.com/armbian/build BUILD_REPOSITORY_COMMIT=85080ff3 VERSION=5.99.191113 LINUXFAMILY=sunxi BRANCH=dev ARCH=arm IMAGE_TYPE=nightly BOARD_TYPE=eos INITRD_ARCH=arm KERNEL_IMAGE_TYPE=zImage IMAGE_UUID=1b7fd79e-803f-4438-8b4c-5e9287a7b86c I saw on the download page that a current download of Armbian Bookwork for the Bananapi Pro would include Kernel 6.6.29, so there should be a newer kernel available. Can you help me troubleshooting what is holding my system back from upgrading to a newer kernel? Various posts on the forum suggest anything from "apt-get upgrade will update your kernel" to "use armbian-config". Using the latter, I tried switch between nightly and stable, which didn't offer any updated kernel to apt. The "Switch to other kernels" option retrieves some files, then shows the "Yes, I understand" screen but then immediately goes back to the main "System settings" screen, which makes me think that something is broken here. How can I find out what exactly is broken?

This is just one issue out of thousands and we operate all this with budget that is very close to zero. This should be picked by maintainer, if exists. We support them from our business deals, but still, they come and go and in between, we have nobody. For a month and half, there is nobody and I can't cover, its too expensive. Since none of board maintainer is full time, but they should be, this can easily take weeks, or more ... But luckily: automated builds makes it half way. Its there, even smoke tested, where problems are not detected. one can build combo on their own. its open source. You can fix bugs too. we need to push new release by the end of the month. And yes, I heard there are some problems with Rpi kernels. Which will just make us more damages and headaches. Rpi foundation has almost 2 mio EUR yearly budget to fight problems ... Its not Armbian that is making bugs, but you expect us to pay to fix them. I tried to help you with hints. Here I have to stop. Out on vacations.

Did you reboot before (re)installing headers? If yes and still not ok ... beta repository certainly has matched kernel / headers combo. IMO its pretty safe to upgrade to daily builds, but then freeze kernel (can be done in armbian-config).

I think you were dead-on in your previous post - the armbian-bsp-cli-bananapipro package was not installed anymore. After installing that, the "Switch to other kernels" option started working again, and I have a choice of three kernels now! But before I proceed and install the new kernel - I noticed that the linux-u-boot-bananapipro-current package is also not installed. I'm not sure how critical that is, and if just installing the new kernel would be enough. Should I install it manually before proceeding?

Thank you for your reply. I suppose you mean the "Switch to other kernels" option? As said, it doesn't seem to be working, and I think I have a hunch now why that might be the case: Running "dpkg -l | grep linux-image", the output is completely empty. Or is this option looking for something completely different?

Looks like you have the vendor kernel package installed. If you want mainline kernel, then you need to install the current kernel package. Run armbian-config and see what it tells you are the available kernels for you. Now realize that going from vendor to mainline kernel you might loose some functionality (there is an FAQ item on this), but you can always switch back to vendor kernel if it is important.

okok, i do one pass with my setting and if not crash, i try GOVERNOR=ondemand after, my pattern test during 36-40hours, keep in touch after this time if i not crash/freeze before

Hi, okok, i test with my pattern test My brother have Helios64 also, he use it with many Docker Container and freeze everyday with default settings, same stabilty problem, he pass to 1200 1200 performance this day and test this setting for moment... if work better to my side with your file, my brother test your file on his helios Your file is on my helios, 400-1800 schedutil echo check > /sys/block/md0/md/sync_action -> running btrfs check --check-data-csum --readonly --progress /dev/disk/by-uuid/XXXXXXXXXXXXX -> running Freeze Crash... Not Freeze Crash... Keep in touch

hey guys! nice to meet y'all the reason that brought me here is Zero 2W and tv-out issue any recommendations how can I adapt these patches to h618? or maybe someone is already working on that? or maybe there are other options how to turn on tv-out for Zero 2W? I've tried different distros with 6.1 & 6.6 kernels and no luck with tv ;( many thanks in advance!

...and i reproduce twice same freeze with cryptosetup to unlock my raid... freeze network... access usb is ready... but terribely slow... i tape my login and password and i waiting... but no response... picocom v3.1 port is : /dev/ttyUSB0 flowcontrol : none baudrate is : 1500000 parity is : none databits are : 8 stopbits are : 1 escape is : C-a local echo is : no noinit is : no noreset is : no hangup is : no nolock is : no send_cmd is : sz -vv receive_cmd is : rz -vv -E imap is : omap is : emap is : crcrlf,delbs, logfile is : none initstring : none exit_after is : not set exit is : no Type [C-a] [C-h] to see available commands Terminal ready helios64 login: root Password: I type CTRL-C and... ^C _ _ _ _ __ _ _ | | | | ___| (_) ___ ___ / /_ | || | | |_| |/ _ \ | |/ _ \/ __| '_ \| || |_ | _ | __/ | | (_) \__ \ (_) |__ _| |_| |_|\___|_|_|\___/|___/\___/ |_| Welcome to Armbian-unofficial 24.2.1 Bookworm with Linux 6.6.29-current-rockchip64 No end-user support: built from trunk System load: 3% Up time: 11 min Local users: 2 Memory usage: 7% of 3.77G IP: 10.0.0.155 CPU temp: 41°C Usage of /: 46% of 14G RX today: 53.8 MiB [ General system configuration (beta): armbian-config ] Web console: https://helios64:9090/ You have no mail. I type CTRL-C ^C And no prompt.... full freeze or lost control I back to ENABLE=true MIN_SPEED=408000 MAX_SPEED=1200000 GOVERNOR=schedutil until you explain me where and how use your file

Hello... and i'm crying... freeze today with raid10 srubbing during btrfs check... But something is strange... network ssh is dead... but access with usb cable to console is working but very very very extremely slow I have this and... waiting very long time to have prompt picocom v3.1 port is : /dev/ttyUSB0 flowcontrol : none baudrate is : 1500000 parity is : none databits are : 8 stopbits are : 1 escape is : C-a local echo is : no noinit is : no noreset is : no hangup is : no nolock is : no send_cmd is : sz -vv receive_cmd is : rz -vv -E imap is : omap is : emap is : crcrlf,delbs, logfile is : none initstring : none exit_after is : not set exit is : no Type [C-a] [C-h] to see available commands Terminal ready helios64 login: root Password: _ _ _ _ __ _ _ | | | | ___| (_) ___ ___ / /_ | || | | |_| |/ _ \ | |/ _ \/ __| '_ \| || |_ | _ | __/ | | (_) \__ \ (_) |__ _| |_| |_|\___|_|_|\___/|___/\___/ |_| Welcome to Armbian-unofficial 24.2.1 Bookworm with Linux 6.6.29-current-rockchip64 No end-user support: built from trunk System load: 183% Up time: 1 day 21:18 Local users: 3 Memory usage: 84% of 3.77G Zram usage: 34% of 5.88G IP: 10.88.0.1 10.0.0.155 CPU temp: 43°C Usage of /: 46% of 14G RX today: 52.5 MiB [ General system configuration (beta): armbian-config ] Web console: https://helios64:9090/ You have no mail. root@helios64:~#

I have an OrangePi PC with armbian installed on it. Today, probably because of my stupidity, the board couldn't boot after upgrading a bunch of stuff. When I opened the sd card on my pc, I found that there were no kernel files in /boot and there were broken symlinks. I tried to replace these with the files from the current minimal image armbian is available for the board, but encountered a UUID mismatch. I then used files from a september 2021 backup, which did allow me to boot into a functional system. It had Linux 5.10.43-sunxi. But before my attempts to fix the issue, my system had Linux 6.1.11-sunxi installed, so I am concerned about this mismatch and would like to safely remove the old kernel files and bring it back to 6.1.11, after which I would like to proceed updating the system to Bookworm (the system still says it's Armbian Buster). How do I reinstall the linux kernel and initrd files in /boot and remove the files of other kernels in /boot? I really want to keep this system going because I don't want to reconfigure and setup again everything that's running on it. Soon I'm getting a new Pi board which would be a proper replacement and for which I am willing to set up all the stuff again, to start clean.

Current kernel 6.6.29 uses the lowest frequencies 400 and 600 MHz also for the big cores, contrary to linux 6.6.8, where the lowest frequency used by the big cores is 800 MHz. So I would assume from what you say that linux 6.6.29 should be more stable. However, I was puzzled why this is not the case with my system: actually none of the kernels 6.6.x (x>8) was stable on my system until I tried 6.6.29 with the 75mV bump for all states of the big cores ! The explanation I have for that is that the jump from the lowest state 408 to 1.8 GHz is somewhat larger than from 800 MHz and that the correct voltage feeded to the cores becomes more critical in those cases. So with the 75 mV bump for all states of the big cores, that source of instability seems to have vanished now: 6.6.29 is stable so far (at least on my system). # cat /etc/default/cpufrequtils ENABLE=true MIN_SPEED=408000 MAX_SPEED=1800000 GOVERNOR=ondemand # transition tables, linux 6.6.29 # cat /sys/devices/system/cpu/cpufreq/policy4/stats/trans_table From : To : 408000 600000 816000 1008000 1200000 1416000 1608000 1800000 408000: 0 1705 141 1 5 1 1 394 600000: 1695 0 7 2 0 3 0 120 816000: 137 8 0 2 3 3 2 21 1008000: 2 1 5 0 0 0 0 1 1200000: 5 1 2 0 0 2 3 4 1416000: 2 0 3 0 3 0 3 4 1608000: 1 0 0 1 1 3 0 5 1800000: 407 111 18 3 5 3 2 0 # cat /sys/devices/system/cpu/cpufreq/policy0/stats/trans_table From : To : 408000 600000 816000 1008000 1200000 1416000 408000: 0 2951 7 3 2 1547 600000: 2865 0 2 2 2 139 816000: 8 2 0 1 1 7 1008000: 4 0 1 0 4 4 1200000: 1 1 1 1 0 21 1416000: 1633 55 8 6 16 0

Kernel Vendor 6.1.43 sudo apt-get install armbian-config sudo armbian-config # SYSTEM # FREEZE sudo add-apt-repository ppa:liujianfeng1994/panfork-mesa sudo add-apt-repository ppa:liujianfeng1994/rockchip-multimedia sudo apt update sudo apt dist-upgrade sudo apt install mali-bifrost-firmware rockchip-multimedia-config sudo apt install libv4l-rkmpp -y sudo apt install v4l-utils -y sudo apt install ffmpeg -y sudo apt install glmark2-es2-wayland -y I think I will need to compile an legacy kernel to this device, since this fixes are linked to rk3588 I made this file to compile Armbian Vendor 6.1: https://drive.google.com/file/d/1TXaKyQt1-fDlDWE1gzTqfsoY-3_YSuHv/view?usp=drive_link I made this file to compile Armbian Vendor 5.1: https://drive.google.com/file/d/1HFRYTETFcyT_fiSPY_NzLbbFZ6dAfdRK/view?usp=sharing

Hello everyone, I've recently started migrating a project for Banana Pi M5 from Debian 10 Buster to Armbian, because I've found that the latest versions of it now support the GPU, Mali G31, and come with Panfrost OpenGL driver, which is crucial for this project. Everything was perfect until I had to implement two features: operating with TV via CEC and showing boot logo. Quickly about the last one - as I've understood, we have to use Plymouth, but I didn't really get how to do it, I've tried to activate it but had no success (how exactly see under paragraph). However, it doesn't work on Server Images (even on those that were compiled with build tools and activated option BOOT_LOGO in kernel conf), but in GUI Images everything is fine with it. Also I've tried using uBoot logo (boot-logo.bmp.gz), but also no success. # Adding "splash quiet loglevel=0 logo.nologo" to extraargs in "/boot/armbianEnv.txt" # Activating bootlogo in "/boot/boot.cmd" (am I even supposed to edit this file?) sudo plymouth-set-default-theme -R customtheme # It contains our logo # sudo update-initramfs -c -u # In fact, it runs automatically sudo reboot # ... sudo plymouthd sudo plymouth --show-splash Now about CEC. I've made some observations: CEC Under Debian # Sorry, there is no support for Shell syntax highlighting apparently. pi@TEST:~$ uname -a Linux TEST 4.9.312-BPI-M5 #1 SMP PREEMPT Wed Mar 1 01:44:35 UTC 2023 aarch64 GNU/Linux pi@TEST:~$ cec-client -l libCEC version: 4.0.4, compiled on Linux-4.9.0-8-arm64 ... , features: P8_USB, DRM, P8_detect, randr, Exynos, AOCEC Found devices: 1 device: 1 com port: AOCEC vendor id: 0000 product id: 0000 firmware version: 5 type: unknown pi@TEST:~$ ls -l /dev/*cec* crw-rw-rw- 1 root root 503, 0 Feb 14 2019 /dev/aocec pi@TEST:~$ echo 'standby 0' | cec-client -s -d 1 opening a connection to the CEC adapter... pi@TEST:~$ # Works fine. pi@TEST:~$ echo 'on 0' | cec-client -s -d 1 opening a connection to the CEC adapter... pi@TEST:~$ # Works fine. pi@TEST:~$ sudo lsmod | grep cec pi@TEST:~$ sudo find /lib/modules/ -name "*cec*" pi@TEST:~$ # No CEC module in lsmod or modules overall, but works fine. pi@TEST:~$ It uses AOCEC on 4.9 Linux kernel. Works flawlessly. All the parts in "/boot/boot.ini" concerning CEC: ... ### voutmode : hdmi or dvi setenv voutmode "hdmi" # setenv voutmode "dvi" # HPD enable/disable option setenv disablehpd "false" # Enable/Disable CEC setenv cec "true" ... ### Normal HDMI Monitors if test "${display_autodetect}" = "true"; then hdmitx edid; fi if test "${hdmimode}" = "custombuilt"; then setenv cmode "modeline=${modeline}"; fi if test "${cec}" = "true"; then setenv cec_enable "hdmitx=cec3f"; fi ... # Boot Args setenv bootargs "...${cec_enable} sdrmode=${sdrmode}" ... If I set cec "false" this happens: pi@TEST:~$ cec-client -l libCEC version: 4.0.4, compiled on Linux-4.9.0-8-arm64 ... , features: P8_USB, DRM, P8_detect, randr, Exynos, AOCEC Found devices: 1 device: 1 com port: AOCEC vendor id: 0000 product id: 0000 firmware version: 5 type: unknown pi@TEST:~$ ls -l /dev/*cec* crw-rw-rw- 1 root root 503, 0 Feb 14 2019 /dev/aocec pi@TEST:~$ echo 'standby 0' | cec-client -s -d 1 opening a connection to the CEC adapter... unable to open the device on port AOCEC ERROR: [ 2233] AllocateLogicalAddresses - failed to allocate device '0', type 'recording device' ERROR: [ 2233] failed to find a free logical address for the client ERROR: [ 2233] failed to register the new CEC client - cannot allocate the requested device types ERROR: [ 2233] failed to register a CEC client pi@TEST:~$ # Doesn't work pi@TEST:~$ Here, "/dev/aocec" doesn't sweep away when setting CEC to false. It just becomes unaccesible. CEC Under Armbian pi@TEST:~$ uname -a Linux TEST 6.6.8-edge-meson64 #1 SMP PREEMPT Wed Dec 20 16:02:07 UTC 2023 aarch64 GNU/Linux pi@TEST:~$ cec-client -l libCEC version: 6.0.2, compiled on Linux ... , features: P8_USB, DRM, P8_detect, randr, Exynos, Linux, AOCEC Found devices: NONE pi@TEST:~$ ls -l /dev/*cec* ls: cannot access '/dev/*cec*': No such file or directory pi@TEST:~$ echo 'standby 0' | cec-client -s -d 1 autodetect FAILED pi@TEST:~$ echo 'on 0' | cec-client -s -d 1 autodetect FAILED pi@TEST:~$ sudo lsmod | grep cec pi@TEST:~$ sudo find /lib/modules/ -name "*cec*" /lib/modules/6.6.8-edge-meson64/kernel/drivers/media/cec /lib/modules/6.6.8-edge-meson64/kernel/drivers/media/cec/usb/pulse8/pulse8-cec.ko /lib/modules/6.6.8-edge-meson64/kernel/drivers/media/cec/usb/rainshadow/rainshadow-cec.ko /lib/modules/6.6.8-edge-meson64/kernel/drivers/media/cec/platform/cec-gpio /lib/modules/6.6.8-edge-meson64/kernel/drivers/media/cec/platform/cec-gpio/cec-gpio.ko /lib/modules/6.6.8-edge-meson64/kernel/drivers/media/cec/platform/meson/ao-cec.ko /lib/modules/6.6.8-edge-meson64/kernel/drivers/media/cec/platform/meson/ao-cec-g12a.ko /lib/modules/6.6.8-edge-meson64/kernel/drivers/gpu/drm/bridge/synopsys/dw-hdmi-cec.ko pi@TEST:~$ sudo modprobe cec pi@TEST:~$ sudo modprobe cec-gpio pi@TEST:~$ sudo modprobe ao-cec pi@TEST:~$ sudo modprobe ao-cec-g12a pi@TEST:~$ sudo modprobe dw-hdmi-cec pi@TEST:~$ sudo modprobe pulse8-cec pi@TEST:~$ sudo modprobe rainshadow-cec pi@TEST:~$ sudo lsmod | grep cec rainshadow_cec 16384 0 pulse8_cec 24576 0 dw_hdmi_cec 12288 0 ao_cec_g12a 12288 0 ao_cec 16384 0 cec_gpio 12288 0 pi@TEST:~$ # cec.ko isn't in libs so in lsmod there is no such module, but why "modprobe cec" gives no error? pi@TEST:~$ ls -l /dev/*cec* ls: cannot access '/dev/*cec*': No such file or directory pi@TEST:~$ # And activating modules just doesn't help, there is still no any "/dev/*cec*" device pi@TEST:~$ It doesn't use any of CEC on 6.6.8 Bleeding Edge Linux kernel (I've tested it before on stable 6.1 kernel, but it didn't work as well, I've activated some modules concerning CEC in kernel config and built using the latest possible kernel, thinking it will change something). Just doesn't work. AOCEC module is compiled and launched though, but it doesn't use it at all since there is no "/dev/*cec*" device. All the parts in "/boot/boot.cmd" concerning CEC: ... setenv sdrmode "auto" setenv voutmode "hdmi" setenv disablehpd "false" setenv cec "false" ... if test -e ${devtype} ${devnum} ${prefix}zImage; then ... setenv bootargs "...${cec_enable} sdrmode=${sdrmode}" ... Somehow, it misses the part where we should set "cec_enable" variable. What if I restore it and set to true? But I don't really think it will change something, as "/dev/aocec" existed on Debian even when CEC was disabled. That didn't work, as well as adding "hdmitx=cec3f" to extraargs in "/boot/armbianEnv.txt". There is just no CEC device in "/dev/", I don't know which type of problem is that - module, overlay, kernel?? Yes, I've used v4l, and it also fails because it doesn't find any "/dev/*cec*". Anyway, I hope this problem can be resolved and thanks to everyone for attention, have a happy new 2024 year!

Yes I have tried the Zunlong images for orangepizero3 and they work. Unfortunately those images are for a Linux 6.1 kernel and the zero3 and 2w were only officially implemented into linux with 6.6. The challenge is to get the Zunlong code into Armbian with the newer kernels.

@RobArmbian remember to also select the option to ❄️freeze❄️ the kernel so that apt won't update it back to 🔥6.6🔥

I am using 6.6.8 with the modified dtb (cache awareness, emmc with hs400, 75 mV bump for the big cores). It works perfectly fine. For your convenience I attach the dtb. Since Helios64 is used throughout the day by several people - time for tests is very limited. Everybody is invited to test kernels and provide feedback here. rk3399-kobol-helios64.dtb-6.6.8-L2-hs400-opp

sudo apt-get install armbian-config sudo armbian-config # SYSTEM # FREEZE wayland.sh #!/bin/bash sudo apt update sudo apt dist-upgrade sudo apt install libv4l-rkmpp -y sudo apt install v4l-utils -y sudo apt install ffmpeg -y sudo apt install glmark2-es2-wayland -y sudo glmark2-es2-wayland Go to chrome://flags Search "Preferred Ozone platform" Set it to "Wayland" ozone-platform-hint auto Restart I can't run videoplayback with V4L2 enabled this is a mess sudo nano .profile # add to the bottom line: export MOZ_ENABLE_WAYLAND=1 # or just: env MOZ_ENABLE_WAYLAND=1 /snap/bin/firefox export MOZ_ENABLE_WAYLAND=1 Open the firefox and text: about:config in Firefox. Search for the media.ffmpeg preference and set it to true. Restart Firefox.

sudo apt-get install armbian-config sudo armbian-config # SYSTEM # FREEZE @pocosparc You will need to edit the DTS or try to enable it via openvfd fddis_dev { compatible = "fddis_dev"; fddis_gpio_clk = <gpio0 RK_PB3 &pcfg_pull_none>; fddis_gpio_dat = <gpio0 RK_PB4 &pcfg_pull_none>; status = "okay"; }; fddis_dev { fddis_gpio_clk { rockchip,pins = <0 RK_PB3 RK_FUNC_GPIO &pcfg_pull_none>; fddis_gpio_dat { rockchip,pins = <0 RK_PB4 RK_FUNC_GPIO &pcfg_pull_none>; };

Orange Pi 5 plus. It seems that in the 'edge' kernels, ssh is disabled by default. Since HDMI doesn't function this is a problem. I used the debugging UART and after setup I got the message "ssh.service is disabled" I enabled the service and all is well. Any reason why ssh would be disabled?

Greetings Armbian Community, We’re thrilled to share our latest strides in enhancing partnerships, expanding support, and advancing innovations within the Armbian ecosystem. Here’s a roundup of recent developments: 1. Strengthening Partnerships in Shenzhen: We’ve embarked on a mission to fortify our collaborations with partners in Shenzhen, aimed at fostering better support for our community. During our visit, we engaged with both existing and potential partners to deepen our ties and enhance the services we offer to you. Read more 2. Platinum Support and Giveaway for Bananapi M7: We’re excited to announce the launch of platinum support and a special giveaway for the latest Bananapi M7, a collaborative effort between Bananapi and ARMSOM. This initiative aims to provide unparalleled assistance and rewards to our valued users. Learn more 3. Expansion of Community Build Framework: Our community interaction has led to the integration of several new boards, including SakuraPi and H96 TV box, into our build framework. Additionally, we’ve upgraded u-boot on 32-bit Rockchip devices and successfully ported Khadas Edge 2 to kernel 6.1. Moreover, FriendlyElec NAS now runs on mainline-based kernels, enriching our ecosystem with more versatile options. 4. Ongoing Upgrades and Future Ventures: In the pipeline, we have several exciting upgrades underway. We’re working on upgrading the Odroid XU kernel to version 6.6 and adding support for Orangepi 5 PRO. Furthermore, we’re introducing mainline kernel support for Orangepi Zero 2W, and our team is eagerly diving into the development of the new Radxa Rock 5 ITX board and Rock 5C. Stay tuned for more updates as we continue to elevate the Armbian experience! Best regards, The Armbian Team View the full article

Bookworm is latest stable. You can only upgrade to unstable ... which is not recommended for production. You could upgrade kernels, but we don't provide them anymore for bullseye. That is correct. This is the list of packages per distribution: https://fi.mirror.armbian.de/apt/content.html Bullseye only has some files, probably by mistake. It should be just empty as its not supported anymore. Change tags in armbian.list from bullseye to bookworm and update. Should be fine .... at least as far as from Armbian perspective. We can't vouch for packages that are coming from Debian repository as they might come into some conflicts between each other. This is the problem we observe on older releases and have no capacity nor wish to address.

Hello, I find armbian awesome and my problem is because of the manufacurers. I basically want to play accelerated video (because I need 4k). I tried amlogic, but it is not still supported (https://linux-meson.com/hardware.html) the status is partial for the chips I tried. I don't what "partial" means but I can hardware decoding. I also tried allwinner, several chips. In this page https://linux-sunxi.org/Sunxi-Cedrus I see that it is supported but I tried with new kernels, old kernels... Nothing worked. I always reach a point that stops me (like segmentation fault when loading sunxi modules, system freeze when using vdpau, compilation errors due incompatibility between version...) I was thinking of try some rockchip but I think that I will suffer the same pain so this is why I want to ask you guys because I am a bit lost and I am starting to think that everything I try is worthless. Can someone bring me some light? Any tip about what chips are more "friendly" with video acceleration and, if mainline kernel or not, player to use... All the documentation/posts I found are outdated or incomplete and this is the reason I am writing this post, because I am not able to find more information. I know that the manufacturers does not help and everything we have is due the awesome work of the community. It is complicated stuff. Any kind of information will be very helpful. Thanks

Hi, to my side same: root@helios64:~# cat /var/log/syslog | grep mdadm root@helios64:~# and, for moment not crash/freeze to my helios64...