All Activity

Works with an apt update && upgrade. missing DTB is present, and boots ok. Thank you for the fast fix team.

I finally got around to trying things out again. Here is the armbianmonitor -U (https://pastebin.com/7GUqZ2aP) before upgrading/updating on the 21.05.1 release. Setup a swap and going to try the upgrade now.

Just wondering if anyone would be interested in running a helios4 NAS still today? Or maybe you might need a spare board as a potential replacement? I have a decommissioned one at home that has been replaced with an x86 machine. The helios4 still works just fine and it would be quite a waste to just throw it away. It is the full kit: Case, board, cables and power adapter. Happy to send it (I am based in Germany) to whoever wants it as long as you cover the cost. Please send me a direct message if interested, thanks!

Thank you for replying. I run xscreensavers-gl in a window and it always gets 30FPS with <10% CPU in my opiz3, I even show 3D models in F3D... so I am getting 3D MESA acceleration in HDMI and SPI-LCD displays. If the video decoding in my opiz3 is using ARM NEON instructions, then I am fortunate I have that, at least (note: this is possible without needing ffmpeg-v4l2request) I will have to re-check how I was successful with 1080P H264 acceleration last year (I was even getting temporary glitches and pink hues sometimes).

Ok, I finally built armbian 25.5.1, to get Linux-edge 14.7 Bookworm + XFCE for my opiz3... and this time copy/pasted the whole build log to verify that: * the new patches mentioned in Pull Request 8086 were applied * the affected C files are compiled to .o files And then I tried the new ffmpeg-v4l2request with Bookworm's MPV, following the instructions in the original post.... I got the same result: 1080P plays smoothly, but with 100% CPU in all 4 cores. There's no error message of "unsupported hwdec=drm"... but there isn't any confirmation message from MPV either. (same behavior as with plain ffmpeg, from previous experiments)

Okay partially solved, its the Linux rockchip64 kernel version. On 6.12.32-current-rockchip64 the display is failing, 6.12.22-current-rockchip64, and 6.12.17-current-rockchip64 the display is working fine. 6.15.1-edge-rockchip64 is also working fine. 6.16.0-rc3-edge is not even booting, with BananaPi-M7. @amazingfate Would it be possible to look into this please.

Hi Guillame, unfortuantely there is a file size limit and my SD image breaks the upload limit. If you dm me your email address I can look to send you the image via wetransfer or something similar. Kind regards, Mark

If you plan to start from scratch and you don't want to wait hours until repository is updated, yes, rather download and use latest image. Upcoming fix will solve this problem for everyone that still use old image.

Or should I download a new .img image and re-flash ?

Ok, thanks all for your feedback. I will wait a few hours and try an apt update & apt upgrade, and let you know.

Packages are in the update process - few hours from now it will be ok.

Have the same issue, who has a ideas ?

You could attempt to recover ur current install by adding the required DTB to the SDCARD and see if the unit boots. Once booted, mount the eMMC and again copy the DTB to the required dir. DTB DIR: /boot/dtb/rockchip/ rk3566-nanopi-r3s-lts.dtb

According to ur log. It's pulling down an older kernel. This kernel does not have the DTB required so it's failing to boot. After purging the kernel on the current IMG available and installing the kernel from apt. https://paste.armbian.com/orokufexik The result is a missing DTB. root@nanopi-r3s-lts:~# ls /boot/dtb/rockchip/rk3566-nanopi-* /boot/dtb/rockchip/rk3566-nanopi-r3s.dtb

Cannot reproduce. Also R3S LTS /w 2G memory and eMMC. apt update && apt upgrade went through. Reboot just fine. https://paste.armbian.com/usakitotak

How to debug boot issues: https://debug.armbian.de

Hello there ! - nanopi R3S 2GB ram / 32 GB SD card and 32GB MMC here. - Image running: Armbian_25.5.1_Nanopi-r3s-lts_noble_current_6.12.33 An upgrade (armbian-upgrade or apt-get upgrade), both on SD card or MMC, breaks boot of the system, reboot or cold start fails, stuck in system red-light. Both SD or MMC boot at broken. Need to reflash the SD and boot + reinstall. See attached some logs. Thanks ! nan0r r3s-armbian-apt-upgrade.log r3s-armbian-armbian-upgrade.log

This past May, we met with the community at the GStreamer Spring Hackfest in Nice, France, and were able to make great strides, including the integration of AI/ML workflows in GStreamer. View the full article

@usual user thanks for the info!

oops, I missed reading that 100% cpu, but it is ok it is a a53 after all 😅 videos I'd guess is still 'difficult' on z3, accordingly there is some support for gpu vector graphics but I'd guess mostly just triangles. video decoding can be done with just neon (vector computation) , but i'd guess there is still limited access to video decoding hardware. using neon is likely to give that 100% cpu reading as the cpu is busy literally, using real video hardware would be 'invisible' in a sense, the cpu usage may look low but that one won't see that the video hardware itself may after all be reading 100%.

Copying the file over from my rpi zero 2w didn't work. I may try compiling on a different OS on the opi tomorrow to see if that will compile fully.

@laibsch It would be good to get this solved as there are a lot of boards out there and they are expensive kit, also this effects both Armbian Ubuntu as well as Debian. I was hapilly running my own Ubuntu Plucky Armbian Unofficial and had desktop functioning fine on my BananaPi-M7 for several apt-get upgrades. I use ssh mainly as I run it as a server for development purposes, but like to use desktop for dev purposes too. Then suddenly the screen went blank and looked like it was continually trying to start up. On reinstalling Armbian Ubuntu Nobel, then Plucky again I worked out that Gnome had been running as v46, but at some point Ubuntu had reverted to v44. I am not sure if this was the breaking change but it seems to at least be parallel. i.e. it was working and I can demonstrate it working and not working repeatedly. Hi @Cesar R. I will run through your repo mods tomorrow and see if I can replicate. It would be good to get this fixed for both Ubuntu and Debian on BananaPi-M7 and Radxa Rock 5B+ and the other boards for Armbian. As I say theres a lot of boards out there and they are expensive. Maybe some of the board manufacturers would pay towards the fix also ? I am just in it for the solution as I need the boards for dev work.

Been a bit but posting just in case. Doing exactly this with the same image you have downloaded (vendor kernel armbian cinnamon). OBS in bookworm is actually a bit too old (there is a segfault on opening the HDMI In), and the newest version does not run on Bookworm because of a too old ffmpeg. I got this setup working by updating the image to Trixie and compiling OBS myself. OBS (in any capacity) on the Panfrost driver can be launched by setting the GL mode manually using: PAN_MESA_DEBUG=gl3 obs

I've just be trying again and have managed to get X running on my Nano. But not very well I fear. My first problem is that the Nano can't read the screen EDID. I get lots of "transfer timed out" errors for i2c-1 in the log. I believe this is the ddc connection to the HDMI port. Has anybody here seen this issue and found a solution ? The killer I hit before was that Xorg would hang when first checking the ports (e.g. /sys/class/drm/card0-HDMI-A-1). What I have found is that removing /dev/dri/* before starting X avoids this hang and I do get my desktop and all works. But it seems awfully risky to delete files such as /dev/dri/* and I'm hoping there's a better way. The hang could be an Xorg bug because the same hang happens on a Raspberry Pi 5 when running a 64-bit system but not when running a 32-bit system. As the Nano can't read the EDID it will default to 1024x768 mode. If I force an EDID using drm.edid_firmware=xxx in the kernel command line I can get 1920x1080 on a small HD screen but not on other 1920x1080 screens I've tried. What could confuse the issue here is that I'm running a custom 6.6.87 kernel and use sysvinit rather than systemd. So perhaps my problems are partially self-inflicted. But I have managed to get my 4GB Nano running X with one monitor. The video driver is only the fbdev driver so how well it works with videos etc. remains to be seen. Cheers, Steven

Regarding video acceleration in H618: Can you try the latest armbian with linux edge? https://forum.armbian.com/topic/32449-repository-for-v4l2request-hardware-video-decoding-rockchip-allwinner/#findComment-216587 (the announcement refers to 6.13, but I don't know if it applies to 6.14 or 6.15) ... I think armbian 25.5.1 with linux edge option, builds linux 6.13.x https://github.com/armbian/build/releases/tag/v25.5.1 (and it seems that minimal images de-activates v4l2) I see the patches in my armbian build folder, I compiled in many ways, but I didn't get video acceleration. I didn't get new kernel modules that seem to be related to the patch source code. Perhaps I needed to check that the specific patches are activated or find the linux config option=m Update: you can see that the Linux source files are applied, right before the compilation stage... copy paste the entire terminal scrolled text (or find the appropriate output/log/... file)... search the patch file names I couldn't get acceleration, but hopefully someone else can, and share the method.