All Activity

Hello, i'am struggling to add bluetooth support. Perhaps this will need to be described in the device tree? Enabling rk805-1 (with conf3 overlay) has a positive effect, but this overlay unfortunately also disables wifi on sdio. It appears my board is similar to rk3328-evb, which is correctly described in the mineline kernel in compact way. Can you give me some advice on how to create the correct device tree for my board?

Based on this, you are not using Armbian. You are using a fork of Armbian. The maintainers of this fork use the Armbian name without permission. They do not participate in Armbian development, nor do they participate in these forums. Either use Armbian (Armbian com), or get support for what you are using from where you downloaded it from.

Most of the patches are in the kernel mailing lists. ffmpeg patches have been taken from mainline LibreELEC project.

You should first try to disable xfce compositing, which is very taxing and pretty useless. Without composition, videos should be much smoother, but take note that rk3228 is very limited in terms of resources so windowed playback is acceptable perhaps up to 1080p25/1080p30, anything above won't work well and even 1080p may have some smoothness issues. 8bit/10bit should not matter though.

@helix hello, those "errors" are actually ok for brcmfmac driver. The clm blob is not always necessary and not available for some chips, the .bin file error is an attempt to look for a nvram file, but the driver will later look for other alternative nvram files and does not tell you that finally has found one.

Hello, to avoid this error, you can disable strict mode in the pin controller driver https://elixir.bootlin.com/linux/v6.7.12/source/drivers/pinctrl/sunxi/pinctrl-sun50i-h616.c But I'm not sure that the driver for this touchscreen can work on allwinner processors without changes, because their "gpio_in" and "irq" are different multiplexer states I think they cannot work simultaneously, so something similar is needed

Hello everyone! I'm compiling firmware for orangepizero3，then you want to customize the bootlogo. I tried to replace my bootlogo with armbian-logo-png in xx, but the compiled firmware did not change, so I would like to ask you how to modify it My compile command:./compile.sh BOARD=orangepizero3 BRANCH=current BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_APPGROUPS_SELECTED='browsers multimedia' DESKTOP_ENVIRONMENT=xfce DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base KERNEL_CONFIGURE=no RELEASE=bookworm PLYMOUTH=yes build

a20-olinuxino-Lime-e16Gs16M this one doesn't support anymore why?

Hi, I managed to make w1-GPIO work in Orange Pi Zero v3 for, for example, the DS18B20 sensor. However, I have some doubts about setting the GPIO flags for w1-gpio. Many examples provide flags in the form gpios = <&pio 0 7 (GPIO_ACTIVE_HIGH|GPIO_OPEN_DRAIN)>; but in the dts file when I use this form it does not work (syntax error) so I have to provide the flags in digital form. A description of flags and bits is here https://elixir.bootlin.com/linux/v6.6.30/source/include/dt-bindings/gpio/gpio.h If I would like to set GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN then the digital value for these bits will be for set bits: 0110000 = 48 because GPIO_OPEN_DRAIN it is (GPIO_SINGLE_ENDED | GPIO_LINE_OPEN_DRAIN) Please help me and confirm whether I understood it correctly I wanted to get rid of the message in the logs for w1-gpio [ 4.994183] gpio-74 (onewire@0): enforced open drain please flag it properly in DT/ACPI DSDT/board file which understands that I need to set the GPIO flag GPIO_OPEN_DRAIN in the dts file I see one problem with this source https://www.kernel.org/doc/Documentation/devicetree/bindings/gpio/gpio.txt where a number of bits to set is 6 in source https://elixir.bootlin.com/linux/v6.6.30/source/include/dt-bindings/gpio/gpio.h number of bits to set is 7 I hope I posted this question in the right section, if not please move it

I am using Armbian, so I install all the dependencies manually, and the compilation process all runs ok. However, GPU still does not work.

Bro, I want to give up now. I have checked in the documentation of Debian. All the requirements that GPU works normally have been fulfilled, I have no idea why GPU still does not work. 1. Panfrost [ 4390.653912] panfrost ff9a0000.gpu: clock rate = 500000000 [ 4390.657185] panfrost ff9a0000.gpu: mali-t860 id 0x860 major 0x2 minor 0x0 status 0x0 [ 4390.657223] panfrost ff9a0000.gpu: features: 00000000,00000407, issues: 00000000,24040400 [ 4390.657240] panfrost ff9a0000.gpu: Features: L2:0x07120206 Shader:0x00000000 Tiler:0x00000809 Mem:0x1 MMU:0x00002830 AS:0xff JS:0x7 [ 4390.657260] panfrost ff9a0000.gpu: shader_present=0xf l2_present=0x1 [ 4390.660559] [drm] Initialized panfrost 1.2.0 20180908 for ff9a0000.gpu on minor 1 2. Mesa name of display: :1.0 display: :1 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: Mesa/X.org (0xffffffff) Device: llvmpipe (LLVM 15.0.6, 128 bits) (0xffffffff) Version: 22.3.6 Accelerated: no Video memory: 3860MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.5 Max compat profile version: 4.5 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 OpenGL vendor string: Mesa/X.org OpenGL renderer string: llvmpipe (LLVM 15.0.6, 128 bits) OpenGL core profile version string: 4.5 (Core Profile) Mesa 22.3.6 OpenGL core profile shading language version string: 4.50 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL version string: 4.5 (Compatibility Profile) Mesa 22.3.6 OpenGL shading language version string: 4.50 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL ES profile version string: OpenGL ES 3.2 Mesa 22.3.6 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 3. Device Tree &gpu { status = "okay"; mali-supply = <&vdd_gpu>; };

debug.armbian.de

Hello, everyone. @jock Thank you very much for the tutorial that allowed me to experience video acceleration in h618. Then I would like to know where the V4L2 patch is approximately, interested in this

Armbian-unofficial 24.5.0-trunk Jammy with Linux 6.6.26-current-sunxi

You should not put a custom dtb in this location. When you upgrade the kernel it will delete this directory and replace it with the contents of the new kernel 's dtbs. And then your box will fail to boot at the dtb file referenced in your extlinix.conf file will be missing. To answer your original question don't expect wifi to work on any TV box running amlogic build. I have about 6 different boxes and wifi doesn't work on any of them. This is mentioned in the FAQ: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first It would be easier to buy a USB dongle for wifi if you need it.

Narrowed the issue down by testing older Armbian builds - Armbian 23.02 with 5.15.96 Kernel -> x4 link working - Armbian 23.8 with 6.1.50 Kernel -> x4 link working Comparing the patches between 6.1 and 6.6 shows a new patch related to PCIe: https://github.com/armbian/build/blob/main/patch/kernel/archive/rockchip64-6.6/rk3399-fix-pci-phy.patch Building an image without this patch indeed fixes the issue: Linux rockpro64 6.6.30-current-rockchip64 LnkSta: Speed 2.5GT/s (downgraded), Width x4 (ok) So this patch does not work as expected but simply removing it is probably not an acceptable solution. Can anyone with more understanding of PCI have a look into it? Edit: I also commented on the pull request that introduced the patch: https://github.com/armbian/build/pull/6057

Description fix issue #6531 by disabling "command-not-found" apt hook during build-time (which takes ages under qemu) and re-enabling after succesfully creating rootfs No impact for end user as command-not-found will create/update its internal db natively on SBC transparently during first sudo apt update Jira reference number [AR-2128](https://armbian.atlassian.net/browse/AR-2128) How Has This Been Tested? [x] Build vanilla trixie for opi03 [x] Build vanilla trixie for opi5-plus Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code View the full article

Thank you @ebin-dev for the dtb file. I just reinstalled my NAS with the 6.6.30 kernel and the bookwork image. The dtb file is the only change I've made to configuration. Haven't had any issues yet - so far recompiling ZFS KMOD 2.2.4 to run with new kernel hasn't crashed - MAX CPU freq. for the BIG cores is 1.8GHz NFS and SMB are working fine. sbc-bench is stable as well.

Any idea how I can fix this ??

Hi, I've bought Orange Pi Prime from the second hand. I've also bought 5V 3A power supply. It it was booting with Debian and Armbian. I was using Kingston SDHC cards. Suddenly my board stopped booting from mmc card. I also tried to boot it from Sandisk A1 class card but with no success. Do ypu think it is hardware malfunction or something else?

Iperf3 performance using my 8821cu drivers peaked at ~135 Mbps. For experiments I bought a Fenvi AX1800 adapter. Speed with this adapter reaches 220 Mbps with Iperf3. I would have expected better, but can see the following: It seems the adapter does not connect USB3, but USB2 speed, so that might be an explanation. G root@orangepi5-2:~# iperf3 -c 192.168.1.80 Connecting to host 192.168.1.80, port 5201 [ 5] local 192.168.1.169 port 47482 connected to 192.168.1.80 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 28.4 MBytes 238 Mbits/sec 0 3.45 MBytes [ 5] 1.00-2.00 sec 24.5 MBytes 206 Mbits/sec 0 3.71 MBytes [ 5] 2.00-3.00 sec 26.6 MBytes 223 Mbits/sec 0 4.11 MBytes [ 5] 3.00-4.00 sec 25.9 MBytes 217 Mbits/sec 0 4.11 MBytes [ 5] 4.00-5.00 sec 25.9 MBytes 217 Mbits/sec 0 4.66 MBytes [ 5] 5.00-6.00 sec 26.0 MBytes 218 Mbits/sec 0 4.66 MBytes [ 5] 6.00-7.00 sec 26.0 MBytes 218 Mbits/sec 0 6.49 MBytes [ 5] 7.00-8.00 sec 25.8 MBytes 216 Mbits/sec 0 6.49 MBytes [ 5] 8.00-9.00 sec 25.6 MBytes 215 Mbits/sec 0 7.66 MBytes [ 5] 9.00-10.01 sec 26.9 MBytes 224 Mbits/sec 0 7.66 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.01 sec 262 MBytes 219 Mbits/sec 0 sender [ 5] 0.00-10.06 sec 259 MBytes 216 Mbits/sec receiver iperf Done. root@orangepi5-2:~# lsusb -t /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci-hcd/1p, 480M /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci-hcd/1p, 5000M /: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=ehci-platform/1p, 480M |__ Port 001: Dev 002, If 0, Class=Vendor Specific Class, Driver=mt7921u, 480M /: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=ohci-platform/1p, 12M /: Bus 005.Port 001: Dev 001, Class=root_hub, Driver=ohci-platform/1p, 12M |__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 001: Dev 002, If 1, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 006.Port 001: Dev 001, Class=root_hub, Driver=ehci-platform/1p, 480M /: Bus 007.Port 001: Dev 001, Class=root_hub, Driver=xhci-hcd/1p, 480M /: Bus 008.Port 001: Dev 001, Class=root_hub, Driver=xhci-hcd/1p, 5000M root@orangepi5-2:~# root@orangepi5-2:~# iwconfig lo no wireless extensions. end0 no wireless extensions. wlx90de80d68879 IEEE 802.11 ESSID:"yyyyyy" Mode:Managed Frequency:5.18 GHz Access Point: xx.xx.xx.xx.xx.xx Bit Rate=720.6 Mb/s Tx-Power=3 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality=55/70 Signal level=-55 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:4 Missed beacon:0 root@orangepi5-2:~#

I have two Orange PI 5 where one is running 6.1.43, and one is running edge, currently 6.8.9. Both are connected with standard hdmi cables to a small flat-TV. Both work OK, and I get reasonable graphics, however, the TV is old, so resolution is not 4or 8 k. Is it some HDMI vs screen problem that you see, resolution for example??? G

How to change dts file to make Allwinner H618 Banana Pi M4 zero USB connector become host instead of OTG ??? usb@5100000 { compatible = "allwinner,sun50i-h616-musb\0allwinner,sun8i-h3-musb"; reg = <0x5100000 0x400>; clocks = <0x02 0x70>; resets = <0x02 0x32>; interrupts = <0x00 0x19 0x04>; interrupt-names = "mc"; phys = <0x23 0x00>; phy-names = "usb"; extcon = <0x23 0x00>; status = "okay"; # dr_mode = "peripheral"; # ????? dr_mode = "host"; phandle = <0x5f>;