Search the Community

Hi I have here Banana Pi M2 Berry and I want to use it now as web server, plus few more things, ftp, plex, pi-hole and later also for use some sensors on it. What the best the best OS for it? Armbian is always made for Ultra not Berry and most versions make problems 🙄😒😉 The GUI itself is so !SLOW!, maybe the driver for video are also not right? Can someone give me a link to a proper Armbian for Banana Pi M2 Berry ??? Or advice what for alternative OS?

pipeline: inventory all board vars; add not-eos-with-video; introduce TARGETS_FILTER_INCLUDE pipeline: inventory all board vars; add not-eos-with-video; introduce TARGETS_FILTER_INCLUDE How to use: ./compile.sh inventory - does just the board inventory; look for output in output/info ./compile.sh targets-dashboard - does inventory, targets compositing, and images info; look for output in output/info, read the instructions output by the command if you want to load the OpenSearch dashboards. ./compile.sh targets - does the full targets compositing and artifacts, look for output in output/info If you don't have a userpatches/targets.yaml, one will be provided for you defaulting to Jammy minimal CLI and Jammy xfce desktop, for all boards in all branches. You can pass filters via TARGETS_FILTER_INCLUDE=... to narrow. board JSON inventory: more generic regex parsing of variables from board files: all top-level (non-indented) variables are parsed and included in the JSON board inventory this allows us to add new variables to the board files without having to update the parser variables can be bare, export or declare -g, but must be quoted (single or double) and UPPER_CASE some special treatment for certain variables: KERNEL_TARGET is parsed as a comma-separated list of valid BRANCH'es BOARD_MAINTAINER is parsed as space-separated list of valid maintainer GH usernames as BOARD_MAINTAINERS: [...] in the JSON script complains if BOARD_MAINTAINER is not set in core boards. Empty is still allowed. HAS_VIDEO_OUTPUT="no" causes BOARD_HAS_VIDEO: false in the JSON (for desktop-only inventorying, see below) introduce not-eos-with-video in items-from-inventory at the targets compositor the same as not-eos, but with added BOARD_HAS_VIDEO: true filter, see above introduce TARGETS_FILTER_INCLUDE for targets compositor this filters the targets after compositing (but before getting image info), based on the board inventory data it's a comma-separated list of key:value pairs, which are OR-ed together new virtual info BOARD_SLASH_BRANCH post-compositing inventory for filtering of a specific BOARD/BRANCH combo (e.g. odroidhc4/edge) some interesting possible filters: TARGETS_FILTER_INCLUDE="BOARD:odroidhc4": only build a single board, all branches. JIRA AR-1806 TARGETS_FILTER_INCLUDE="BOARD_SLASH_BRANCH:odroidhc4/current": only build a single board/branch combo TARGETS_FILTER_INCLUDE="BOARD:odroidhc4,BOARD:odroidn2": only build two boards, all branches. TARGETS_FILTER_INCLUDE="BOARD_MAINTAINERS:rpardini": build all boards and branches where rpardini is a maintainer TARGETS_FILTER_INCLUDE="BOARDFAMILY:rockchip64": build all boards and branches in the rockchip64 family image-info-only variables like LINUXFAMILY is not available for filtering at this stage rename config/templates targets-all-cli.yaml to targets-default.yaml this is used when no userpatches/targets.yaml is found new default includes all boards vs branches for non-EOS boards also desktop for all boards that don't have `HAS_VIDEO_OUTPUT='no`` introduce simplified targets-dashboard CLI: does only inventory, compositing, and image info, but not artifact reducing, etc. ignore desktop builds in the OpenSearch indexer update the OpenSearch Dashboards, including new information now available invert the logic used for CLEAN_INFO and CLEAN_MATRIX defaults to yes now, so new users/CI don't get hit by stale caches by default repo pipeline CLI stuff is usually run on saved/restored artifacts for output/info, so don't clean by default via the CLI View the full article

I am trying to stream multiple USB cameras in Orange pi 5+, but I am getting the error: ffmpeg -f v4l2 -input_format mjpeg -video_size 640x480 -i /dev/video3 -c:v copy output2.mp4 # One process successfully started, but calling this a second time doesn't work: ... [video4linux2,v4l2 @ 0xaaab1ddcdbc0] ioctl(VIDIOC_STREAMON): No space left on device /dev/video3: No space left on device dmesg displays this: [696321.331182] usb 5-1.3.2: Not enough bandwidth for new device state. [696321.331189] usb 5-1.3.2: Not enough bandwidth for altsetting 7 I initially assumed that this was a hardware issue, but the device is able to successfully stream camera's maximum resolution 1920x1080 in raw video format, but fails to stream 2 cameras at 640x480 in MJPEG resolution. It is clear that number of bits that the bus can transfer per second is not the cause of the issue. Does anyone know what the issue may be?

Hi all. Here my review video about the Mixtile Blade 3. An RK3588 ARM SBC with a special connector to make it possible to connect multiple of these boards in a cluster. But it can also be used well as desktop or server device. It has all the bells and whistle's an RK3588 can have like dual 2.5GbE, m-PCIe, NVMe, HDMI-out + 2 x DP on USB-C and HMDI-in, ... Here is my video : Greetings, NicoD

So after more the one week working on legacy kernel, I decided to switch to mainline kernel (now using 6.6.2-edge-rockchip64). Removed the liujianfeng1994 repository and installed packeges of the v4l2request repository. Regarding this bug: bug: Lima driver (Mali 400/450) shows a red/pink tint when video is played in X11/Wayland (see https://github.com/mpv-player/mpv/issues/12968) I found that forcing MESA to a different GL core profile can solve the pinkish problem: export MESA_GL_VERSION_OVERRIDE=3.2COMPAT export MESA_GLSL_VERSION_OVERRIDE=320 mpv your-video.mkv Now I have HW accelerated video with mpv . Still have tu study how to get Kodi acceleration working.

I've installed Armbian_v22.05.2_Rockpi-4cplus_jammy_current_6.1.33_minimal and whatever I try to play a 1080p video via the performance is horrible with very slow refresh, totally unusable. Normally loki gives me acceptable performance on SBCs of similar performance but not in this case. The Rock 4c plus is quite powerful so I'm really shocked at how badly it's performing. Let me be clear, I understand that the issue I see is not that the Rock 4c plus isn't cable of playing video, clearly it is and I'm not complaining about the hardware of the device. It's just that the software being used clearly needs to be optimised for it and most things out there don't seem to be. So is there an optimised video player or a way of improving performance with configuration or patched software ?

Hello! Has anyone tried to play straight unconverted hevc video from a GoPro 11? Iv'e tried ffplay and gst-play but I'm just getting a static image and a bunch of these errors, [swscaler @ 0x7f49d399c0] [swscaler @ 0x7f49d47a50] deprecated pixel format used, make sure you did set range correctly I have successfully played example jellyfish videos of hevc and hevc 10bit formats, ffmpeg reports the following details from the GoPro footage, Stream #0:0[0x1](eng): Video: hevc (Main) (hvc1 / 0x31637668), yuvj420p(pc, bt709), 3840x2160 [SAR 1:1 DAR 16:9], 119725 kb/s, 119.88 fps, 119.88 tbr, 120k tbn (default) Any suggestions? Cheers!

In fact, this is a good TV box for porting linux. Almost all the work has already been done. Video acceleration is working, cvbs is working. USB 3.0 and 2.0 are working. While there are problems with HDMI, you need to turn on the TV or monitor only after U-boot has started. And there is a problem with porting the OS to emmc. TV boxes are in high demand than SBC: they are cheaper, already with a case and a power supply, an HDMI cable, and a remote control. I always advise buying a TV box instead of an SBC. In addition, more and more SBC remain without armbian support.

Collabora's engineers presented six talks over the course of the weekend, with topics including a review of recent improvements to GStreamer, a look at the state of video offloading on the Linux desktop, and more. View the full article

First of all, I would like to congratulate and thank you all for the effort put in this initiative. Besides @Gunjan Gupta , special thanks to @pixdrift for making available a test image that we can play with, thus hiding the complexity of compiling the image ourselves. Having said that, and with the intention of giving some testing feedback as you requested, here are some comments. I own a 4GB orange pi Zero 3 with extension board. I started playing with the first image a bit until you uploaded the second image, with which I played a little bit more. With any of both images I did not seem to have good hdmi output initially. By "good" I mean that my monitor detected "something" but I suspect it was not able to synchronize properly. Unplugging the cable and plugging it again seemed to force some recognition and I was able to see the login prompt, but with a lot of flicker and unstability. I remember having similar problems when I played with the miniarch image. With your second image I believe it was worst and I was not able to see anything. So I logged in using the serial connection (see attachment for the boot log over serial). I followed the initial configuration steps and then here the two images seemed to behave differently. While I think the first image started the desktop environment after that, I had to run armbian-config with the second image to activate it. In the first image, once the desktop environment started, I got a good signal through HDMI, albeit in 600x800. I was able to change the resolution but after rebooting I lost the signal again. Getting into armbian-config, deactivating the desktop and activating it again seemed to fix the issue, probably because it activated also the autologin functionality. No browser seemed to be installed, so I installed chromium and I checked the playability of some videos in youtube and they were quite unplayable (not that I expected much, anyway). With the second image, as I said, I had to go to armbian-config to activate the desktop. I selected xfce and it took a while to download and install the packages. After rebooting, nothing was displayed on the monitor. Again I tried the trick of disabling and enabling the desktop to activate the autologin and I was able to have a nice desktop on my monitor, although I had to wait maybe more than one minute until something was shown, and by default I had more than 10 display configuration windows already opened that I had to close (I know, really weird). The usb ports on the expansion board worked nicely and the wifi was also working fine. I was not able to activate bluetooth, though. Maybe I was missing something there. Anyway, I saw that firefox was installed and tried to run it, but it stayed on the task bar without being able to get maximized or anything. So I installed chromium and it behaved much better. It was much snappier than with the previous image. So I checked youtube and to my surprise the videos seemed to be quite playable. I installed then vlc, had to configure it in preferences-video to use xvideo output (xbc) and tested some 1080p sample videos at https://oliverx.link/samples/ . Two samples showed very few lost frames, while using a reasonable amount of CPU, which make me believe they were HW decoded: V206 AVI – MPEG-4 24fps – MP3 and V207 TS – AVC 24fps – AAC So far so good. And I'd say this looks very promising. Thank you again for the effort put in this. armbian serial log.txt

Engineers have widely adopted GStreamer to build video analytics pipelines, and while many companies have indeed built their machine learning analysis framework around GStreamer, no one had made the effort to contribute upstream, until now. View the full article

Im trying to play video on CLI interface. Banana pi M1 im using.I installed VLC, MPV, mplayer but not successful. please help. my video is in pendrive.

Thanks for the suggestion Igor, but I haven't tried it, because I decided to switch to Bookworm before I read it, and then was too late. When I installed the Armbian_23.11.3_Rpi5b_bookworm_current_6.1.68_cinnamon_desktop.img I did not get the complaint about the acceleration. I installed the MESA v23.2, it went without a glitch! Unfortunately, a vcgencmd cmd fails the same way as in Jammy (i.e. VCHI initialization failed). I depend on vcgencmd to measure CPU temperature for cooling fan control, so I'll have to switch to some other way for fan control. Thanks for your help!

I've been playing around with the 3d hardware acceleration on jammy, so I can use KODI without stuttering. And that works fine although the KODI version is a bit outdated. So I installed it doing this, under root: add-apt-repository ppa:liujianfeng1994/panfork-mesa add-apt-repository ppa:liujianfeng1994/rockchip-multimedia apt update apt dist-upgrade apt install mali-g610-firmware rockchip-multimedia-config but how do I revert: apt purge --yes mali-g610-firmware rockchip-multimedia-config apt autoremove --yes apt dist-upgrade --yes add-apt-repository --yes --remove ppa:liujianfeng1994/panfork-mesa add-apt-repository --yes --remove ppa:liujianfeng1994/rockchip-multimedia I tried this, but its not a 100%, because I'm having issues with firefox playing videos after. If anyone knows, I'm all ears

Hi On fresh installed Armbian_23.5.1_Odroidn2_jammy_current_6.1.30_xfce_desktop when starting chromium-browser I get odroidn2:~$ chromium-browser Gtk-Message: 20:49:33.686: Failed to load module "xapp-gtk3-module" libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null) [18372:18372:0625/204934.172288:ERROR:gpu_init.cc(537)] Passthrough is not supported, GL is egl, ANGLE is [18372:18372:0625/204934.232251:ERROR:gl_display.cc(508)] EGL Driver message (Error) eglQueryDeviceAttribEXT: eglQueryDeviceAttribEXT [18372:18372:0625/204934.232523:ERROR:gl_angle_util_vulkan.cc(189)] Failed to retrieve vkGetInstanceProcAddr [18372:18372:0625/204934.232712:ERROR:vulkan_instance.cc(91)] Failed to get vkGetInstanceProcAddr pointer from ANGLE. MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to open zink: /usr/lib/dri/zink_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib/aarch64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri) failed to load driver: zink MESA-LOADER: failed to open kms_swrast: /usr/lib/dri/kms_swrast_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib/aarch64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri) failed to load driver: kms_swrast MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib/aarch64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri) failed to load swrast driver After that browser starts and runs normally. Are there any suggestions to fix this?

Ok...Too long of a video, mostly skipped through the same and didn't watched till the end. I think you need to add CONFIG_MMC_SUNXI_SLOT_EXTRA=2 in your devices uboot config. You can either do that by adding a patch for your uboot defconfig file or by using post_config_uboot_target hook in your board config file. For the latter see - config/boards/cubieboard2.csc for example

@Gunjan Gupta To answer your question which option I picked during the Armbian-Install I made a video. Here is the link to it.

Hi ag123, I did take a look at this. The sunxi-cedrus module is already present in my Armbian image and loaded, you can confirm this from the lsmod output from the build I posted above. From the docs, cedrus looks to be specifically for video encoding/decoding acceleration not display. I don't believe it's related to my display issue. Regarding mainline support listed in: https://linux-sunxi.org/Linux_mainlining_effort H616 is listed with '?' for the HDMI elements, which is 'status unknown' not explicitly unsupported, and HDMI Video (assuming this is video output) for the H6 shows '5.0', so there may be some hope there. My goal at the moment is to replicate the HDMI output that is in the Orange Pi SDK build (even if it requires kernel patching) in the clean Armbian build, I can confirm this works (just figuring out _how_ it works). I have looked through the Orange Pi SDK Linux/u-boot source and haven't found anything specific yet.. I will keep looking

Thanks for posting those links @ag123, I will read them tomorrow. Only a quick update from me. I booted the Orange Pi released version of Debian Bookworm (Orangepizero3_1.0.2_debian_bookworm_server_linux6.1.31) for a comparison, and it has HDMI out, at least for the framebuffer... not currently looking at acceleration... just any video output on HDMI from the Armbian build tool build. These are the dmesg lines related to HDMI from the Orange Pi Debian image [ 0.032022] platform 6000000.hdmi: Fixed dependency cycle(s) with /soc/tcon-top@6510000 [ 0.034437] platform 6000000.hdmi: Fixed dependency cycle(s) with /connector [ 1.436612] sun8i-dw-hdmi 6000000.hdmi: supply hvcc not found, using dummy regulator [ 1.436839] sun8i-dw-hdmi 6000000.hdmi: Detected HDMI TX controller v2.12a with HDCP (DWC HDMI 2.0 TX PHY) [ 1.437282] sun8i-dw-hdmi 6000000.hdmi: registered DesignWare HDMI I2C bus driver [ 1.437669] sun4i-drm display-engine: bound 6000000.hdmi (ops 0xffff800008e84f08) This is the lsmod output orangepi@orangepizero3:~$ uname -a Linux orangepizero3 6.1.31-sun50iw9 #1.0.2 SMP Thu Sep 28 12:01:45 CST 2023 aarch64 GNU/Linux orangepi@orangepizero3:~$ lsmod Module Size Used by overlay 126976 0 algif_hash 16384 1 algif_skcipher 16384 1 af_alg 24576 6 algif_hash,algif_skcipher bnep 28672 2 hci_uart 135168 1 btqca 24576 1 hci_uart btrtl 28672 1 hci_uart btbcm 20480 1 hci_uart btintel 40960 1 hci_uart bluetooth 712704 29 btrtl,btqca,btintel,hci_uart,btbcm,bnep ecdh_generic 16384 2 bluetooth ecc 32768 1 ecdh_generic sunrpc 286720 1 lz4hc 16384 0 lz4 16384 0 sprdbt_tty 36864 2 polyval_ce 16384 0 polyval_generic 16384 1 polyval_ce sunxi_cedrus 45056 0 sunxi_cir 20480 0 videobuf2_dma_contig 24576 1 sunxi_cedrus dw_hdmi_cec 16384 0 rc_core 49152 2 sunxi_cir v4l2_mem2mem 36864 1 sunxi_cedrus videobuf2_memops 20480 1 videobuf2_dma_contig videobuf2_v4l2 24576 2 sunxi_cedrus,v4l2_mem2mem videobuf2_common 49152 5 sunxi_cedrus,videobuf2_dma_contig,videobuf2_v4l2,v4l2_mem2mem,videobuf2_memops videodev 204800 4 sunxi_cedrus,videobuf2_v4l2,videobuf2_common,v4l2_mem2mem mc 53248 5 sunxi_cedrus,videodev,videobuf2_v4l2,videobuf2_common,v4l2_mem2mem display_connector 20480 0 zram 28672 3 binfmt_misc 24576 1 sprdwl_ng 352256 0 sunxi_addr 20480 1 sprdwl_ng cfg80211 372736 1 sprdwl_ng rfkill 36864 7 sprdbt_tty,bluetooth,cfg80211 uwe5622_bsp_sdio 208896 2 sprdbt_tty,sprdwl_ng fuse 126976 1 dm_mod 131072 0 motorcomm 24576 1 dwmac_sun8i 28672 0 mdio_mux 16384 1 dwmac_sun8i Interestingly, for the images I tested, one of my monitors complained about the HDMI input timing of the signal coming from the Orange Pi Zero 3, so I re-validated with the monitor that was happy to display the output (and confirmed again the image I built with Armbian build tool doesn't have HDMI output.. yet). After looking at bit closer at the patches that were being applied in Armbian (15 in total, with 1 set to ignore), I found the following, which I think may be relevant. /patch/u-boot/u-boot-sunxi/allwinner-h616-GPU-enable-hack.patch This looks to specifically enable the GPU on H616 boards and is enabled for any build that passes the CONFIG_MACH_SUN50I_H616 option, which the Orange Pi Zero 3 configuration does (in the defconfig file). The hack is only a single call to a write function, but I am wondering if the h616 and h618 SoCs may differ enough (like the DRAM timing configuration) that this value needs to be configured specifically for h618 boards.. I will chase this up and see if I can find an answer. + /* enable GPU */ + writel(0, 0x7010254);

Powered by Rust, the video codec stack on ARCVM is now bringing faster and more reliable video decoding on ChromeOS. Here's how Collabora has been helping shape video virtualization for Chromebooks, and what it means for end users. View the full article

Could someone make an update image that already has Wayland pre-installed, with working acceleration?

@Tusc wrote: they are not quite yet ready for 'prime time', check out the rolling releases: https://github.com/armbian/os/releases/latest https://github.com/armbian/os/releases/tag/24.2.0-trunk.519 expand the 'Assets' flap, use your web browser's in page search and look for 'zero3'. still in 'bleeding edge' (technology) stage, try it/them out feedback on what works, issues etc. @Gunjan Gupta curiously in the most recent trunk.526 https://github.com/armbian/os/releases/latest a text search for 'zero3' draws a blank, but it is there in 519

I never searched for that. It's not among those recommended in the video. And if you want to help you could paste a link of the right one to choose Thanks

Dear Armbian Community, Here are the latest news! Documentation We recently held a productive meeting to revamp our Build framework documentation. Our primary focus is on making the build framework internal help the ultimate source of truth. The existing pull request draft with hard-coded entries will be transformed into a JSON format, laying the foundation for comprehensive technical documentation. (meeting video) Build Framework features Explore the power of our build framework feature “extensions” – an easy yet robust way to create custom-builds with pre-installed applications. We’ve started providing Armbian with Home Assistant Supervised for selected boards, offering a hassle-free automated pre-installation for a full-blown experience. Mobile-Friendly Desktop Environments With an expanding array of hardware, we are on the lookout for developers interested in bringing up and maintaining mobile-friendly desktop environments such as Gnome mobile, Phosh, KDE mobile, etc. If you’re passionate about this, please get in touch for potential collaboration. Geolocation Router Upgrade In the past few weeks, we upgraded our Geolocation router to a JSON-driven system. We are actively addressing politically induced access issues, particularly in Ukraine/Russia regions. We aim to resolve these problems swiftly and continue providing a seamless service. In case you want to implement it for your services or just to peek how it works, sources are available. Upcoming Release: 24.02 We are gearing up for the 24.02 release, focusing on bug fixes and strategic decisions on board support. Our revised board support rules aim to narrow our focus, ensuring better support for selected hardware. Stay tuned for an improved Armbian experience. Vendor Appreciation We believe in acknowledging vendors who support non-profit open-source movements. A heartfelt thank you to our partners: Khadas, Sinovoip, Ampere Computing, BiQu, Texas Instrument, Mekotronics, JetHome, LibreComputer, Pine64, Mixtile, for their ongoing support, all small supporters from Forums, GitHub and LiberaPay sponsors. We extend our gratitude to the entire Armbian team, volunteers, and professional staff for their dedication and hard work. Stay connected, stay open-source! Best Regards, The Armbian Team View the full article