going

Дмитрий, пожалуйста предоставьте дополнительную информацию. uname -r dmesg | grep -E 'hdmi|gpu|drm|codec' What brand of monitor and its resolution are used? My samsung 2k monitor cannot be detected by some linux kernels, for example. Although other users noted good performance at 1920x1080 resolution.

@robertoj Please check the kernel configuration on the working version. And which modules are present. Then compare with the non-working option.

Do we need this one?

There are no changes in the driver between kernel versions 6.10 and 6.12. I think this patch can be added to the current (6.12) kernel. In your opinion, what else can be added or which parts should I pay special attention to?

patch/kernel/archive/sunxi-6.1 It will be deleted tomorrow. patch/kernel/archive/sunxi-6.6 This is frozen on version v6.6.75 as stable. It will be moved to LEGACY tomorrow and will no longer be supported.

@Stephen Craig For kernel 6.13, I had to make these changes:

This indicates that the hardware decoding is not working properly. It is very strange that this driver is writing a message. There is no compatible sun50i-h616 line in it. That's my doubt.

But will the system installed from the package work? I can't verify it. The internet is not working on my board. In other words. If you just install the necessary packages.

Related topic x264-hw-encoding-on-orange-pi-zero-2w

It seems to me that everything is more complicated. I found this option: https://patchwork.kernel.org/project/linux-clk/patch/20241023075917.186835-6-ryan@testtoast.com/ I'll try to use it. It is marked as not applicable and sent to the archive. I meant the video codec. [ 11.669847] sunxi_cedrus: module is from the staging directory, the quality is unknown, you have been warned. [ 11.672804] cedrus 1c0e000.video-codec: Device registered as /dev/video0 If you try to watch a movie in a video player.

Maybe that's the problem: sound/soc/sunxi/sun4i-i2s.c#L1647

GNOME also works well. XFCE is lame at scaling the screen. For a 1:1 ratio, the letters are large, as if the resolution is set to be less than the actual 2560х1440. Violation of the synchronization frequency. The driver is doing something wrong. Is video hardware decoding working on your device?

The driver is present. You can test this by downloading the packages from the link above.

sunxi-6.12: leo@bananapim4berry:~$ uname -r 6.12.19-current-sunxi64 leo@bananapim4berry:~$ dmesg | grep -iE 'audio|ahub|video|codec|hdmi|drm' [ 0.099396] /soc/hdmi@6000000: Fixed dependency cycle(s) with /soc/tcon-top@6510000 [ 0.099455] /soc/tcon-top@6510000: Fixed dependency cycle(s) with /soc/hdmi@6000000 [ 0.104244] /soc/hdmi@6000000: Fixed dependency cycle(s) with /soc/tcon-top@6510000 [ 0.104620] /soc/hdmi@6000000: Fixed dependency cycle(s) with /soc/tcon-top@6510000 [ 0.104780] /soc/tcon-top@6510000: Fixed dependency cycle(s) with /soc/hdmi@6000000 [ 0.107433] /soc/hdmi@6000000: Fixed dependency cycle(s) with /connector [ 0.107516] /connector: Fixed dependency cycle(s) with /soc/hdmi@6000000 [ 1.946257] sun4i-drm display-engine: bound 1100000.mixer (ops 0xffff80008119ae90) [ 1.946454] sun4i-drm display-engine: bound 6510000.tcon-top (ops 0xffff80008119fc60) [ 1.946768] sun4i-drm display-engine: bound 6515000.lcd-controller (ops 0xffff800081197ab0) [ 1.947062] sun8i-dw-hdmi 6000000.hdmi: Detected HDMI TX controller v2.12a with HDCP (DWC HDMI 2.0 TX PHY) [ 1.949760] sun8i-dw-hdmi 6000000.hdmi: registered DesignWare HDMI I2C bus driver [ 1.950030] sun4i-drm display-engine: bound 6000000.hdmi (ops 0xffff800081199f58) [ 1.950535] [drm] Initialized sun4i-drm 1.0.0 for display-engine on minor 0 [ 1.950566] sun8i-dw-hdmi 6000000.hdmi: read_hpd result: 1 [ 2.438265] sun8i-dw-hdmi 6000000.hdmi: EVENT=plugin [ 4.012109] sun4i-drm display-engine: [drm] fb0: sun4i-drmdrmfb frame buffer device [ 9.311566] systemd[1]: Starting modprobe@drm.service - Load Kernel Module drm... [ 9.583263] systemd[1]: modprobe@drm.service: Deactivated successfully. [ 9.590683] systemd[1]: Finished modprobe@drm.service - Load Kernel Module drm. [ 11.222612] [drm] Initialized panfrost 1.2.0 for 1800000.gpu on minor 1 [ 11.336128] videodev: Linux video capture interface: v2.00 [ 11.672804] cedrus 1c0e000.video-codec: Device registered as /dev/video0 [ 36.607644] sun8i-dw-hdmi 6000000.hdmi: EVENT=plugin [ 37.501202] sun8i-dw-hdmi 6000000.hdmi: EVENT=plugin [ 39.278755] hdmi-audio-codec hdmi-audio-codec.5.auto: Only one simultaneous stream supported! [ 39.278791] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22 [ 39.278816] ahub_plat-i2s-hifi: ASoC: error at __soc_pcm_open on ahub_plat-i2s-hifi: -22 [ 57.559744] hdmi-audio-codec hdmi-audio-codec.5.auto: Only one simultaneous stream supported! [ 57.559772] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22 [ 57.559789] ahub_plat-i2s-hifi: ASoC: error at __soc_pcm_open on ahub_plat-i2s-hifi: -22 pkg for test: sunxi64-6.12.19

boot> grep -n CEDRUS config-* 7001:CONFIG_VIDEO_SUNXI_CEDRUS=m leo@bananapim4berry:~$ dmesg | grep cedrus [ 11.499288] sunxi_cedrus: module is from the staging directory, the quality is unknown, you have been warned. [ 11.522089] cedrus 1c0e000.video-codec: Device registered as /dev/video0 leo@bananapim4berry:~$ ls -al /dev/video0 crw-rw----+ 1 root video 81, 0 �м�а�р 18 11:53 /dev/video0 leo@bananapim4berry:~$ uname -r 6.13.7-edge-sunxi64 leo@bananapim4berry:~$ lsmod | grep cedrus sunxi_cedrus 49152 0 v4l2_mem2mem 28672 1 sunxi_cedrus videobuf2_dma_contig 20480 1 sunxi_cedrus videobuf2_v4l2 20480 2 sunxi_cedrus,v4l2_mem2mem videodev 249856 3 sunxi_cedrus,videobuf2_v4l2,v4l2_mem2mem videobuf2_common 53248 5 sunxi_cedrus,videobuf2_dma_contig,videobuf2_v4l2,v4l2_mem2mem,videobuf2_memops mc 53248 5 sunxi_cedrus,videodev,videobuf2_v4l2,videobuf2_common,v4l2_mem2mem P.S. add more

Greetings to all participants. Before configuring the software, we need to properly configure the hardware nodes on the chip that are responsible for video/audio processes. Turn on the power, make a reset, adjust the clock, etc. This should be done by the kernel driver. Currently, in the sunxi(64) family for h616-h618 chips, I see a mess in the drivers. There are several of them for the same thing. They were added by different people at different times. Today, these drivers do not want to work correctly. On at least one BPI-m4-berry (h618) board. I'm trying to fix this situation right now. Please write here whatever you think is necessary to speed up the process. After applying all the sunxi-6.12 patches, the core looks like sunxi-6.12-rebase sunxi-6.13-rebase

To do this, you will need to open two sessions in the terminal. The test here is my configuration file 1 session ~/armbian$ ./compile.sh test kernel-patch ...... # build system printed: [✨] Starting [ interactive patching process for kernel ] [🌱] Creating commit to start from clean source [🌱] Patches will be created [ with the following maintainer information ] [🌱] MAINTAINER (Real name): [ The-going ] [🌱] MAINTAINERMAIL (Email): [ 48602507+The-going@users.noreply.github.com ] [🌿] If those are not correct, set them in your environment, command line, or config file and restart the process [🚸] Make your changes in this directory: [ /home/leo/armbian/cache/sources/linux-kernel-worktree/6.13__sunxi64__arm64 ] [🚸] Press <ENTER> after you are done [ editing files in /home/leo/armbian/cache/sources/linux-kernel-worktree/6.13__sunxi64__arm64 ] Press ENTER to show a preview of your patch, or type 'stop' to stop patching... The build system will apply all the patches and make a commit that will include all the changes. Leave this session alone. In the second session, you make your changes and record the results. 2 session leo@armbuild:~/armbian$ cd /home/leo/armbian/cache/sources/linux-kernel-worktree/6.13__sunxi64__arm64 ### open root session leo@armbuild:~/armbian/cache/sources/linux-kernel-worktree/6.13__sunxi64__arm64$ sudo su root@armbuild:/home/leo/armbian/cache/sources/linux-kernel-worktree/6.13__sunxi64__arm64# ls arch/arm64/boot/dts/rockchip/rk3399-* linux-kernel-worktree/6.13__sunxi64__arm64# nano arch/arm64/boot/dts/rockchip/rk3399-orangepi.dts linux-kernel-worktree/6.13__sunxi64__arm64# git add --all linux-kernel-worktree/6.13__sunxi64__arm64# git commit -m "Add a comment" ###close root session: linux-kernel-worktree/6.13__sunxi64__arm64# exit linux-kernel-worktree/6.13__sunxi64__arm64$ git format-patch -1 -o /home/leo/armbian/userpatches/ /home/leo/armbian/userpatches/0001-Add-a-comment.patch linux-kernel-worktree/6.13__sunxi64__arm64$ cat /home/leo/armbian/userpatches/0001-Add-a-comment.patch From 4dad6a3fa967235ea7eef35f81733bdafd806b53 Mon Sep 17 00:00:00 2001 From: The-going <48602507+The-going@users.noreply.github.com> Date: Tue, 18 Mar 2025 12:54:11 +0000 Subject: [PATCH] Add a comment --- arch/arm64/boot/dts/rockchip/rk3399-orangepi.dts | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm64/boot/dts/rockchip/rk3399-orangepi.dts b/arch/arm64/boot/dts/rockchip/rk3399-orangepi.dts index 2ddd4da15..29eec7e65 100644 --- a/arch/arm64/boot/dts/rockchip/rk3399-orangepi.dts +++ b/arch/arm64/boot/dts/rockchip/rk3399-orangepi.dts @@ -78,6 +78,7 @@ keys: gpio-keys { compatible = "gpio-keys"; autorepeat; + /* key-power */ key-power { debounce-interval = <100>; gpios = <&gpio0 RK_PA5 GPIO_ACTIVE_LOW>; -- 2.34.1 What should I do with the first session? Decide for yourself!!

Printed on the chip itself: SEC 913 K4F8E30 4HBMGCJ Now we know about this chip. There is a similar discussion here 25244-ram-problem/#findComment-160334 Unfortunately, Armbian will not be able to support all the variety of chips. Only the user can independently add changes for their device and test them. If you want to build the u-boot package yourself, then Configuration for your device: config/boards/orangepizero3.csc Similarly, add the following lines to your configuration file config/boards/orangepizero2w.csc#L5-L8 Place the required set of patches in the appropriate folder.

Please post the name of the memory chip. Literally what it says on it. This issue has already been raised here on the forum. Two different users had different chips soldered on the same boards. Memory chips from different manufacturers. In one case, the memory was defined as 2GB, in the other as 1GB.

This patch is not complete. A solution already seems to exist in this discussion. I will add these changes to this PR#7705 tomorrow.

Maybe you can describe the problem/goal that you want to solve using RT Core. First you need to figure out what is required. There are several real-time Cores. And each solves its own problems.

I understood. Thank you.

[ 9.527925] videodev: Linux video capture interface: v2.00 [ 9.539551] panfrost 1800000.gpu: clock rate = 432000000 [ 9.539593] panfrost 1800000.gpu: bus_clock rate = 200000000 [ 9.540215] panfrost 1800000.gpu: mali-g31 id 0x7093 major 0x0 minor 0x0 status 0x0 [ 9.540250] panfrost 1800000.gpu: features: 00000000,000027f7, issues: 00000000,00000400 [ 9.540262] panfrost 1800000.gpu: Features: L2:0x07100206 Shader:0x00000000 Tiler:0x00000209 Mem:0x1 MMU:0x00002821 AS:0xff JS:0x7 [ 9.540274] panfrost 1800000.gpu: shader_present=0x1 l2_present=0x1 [ 9.544584] [drm] Initialized panfrost 1.2.0 for 1800000.gpu on minor 1 Thank you for the information provided! A simple clarification. Does it work on an h616 processor with the patch disabled? For the h618 processor, I was unable to get the GPU to work with or without this patch. It remains to be seen whether this patch plays a positive role for the h6 processor. If there is no positive effect, then I'd better turn it off.

Is the GPU node enabled for your board?

Try to set the disabled status for the GPU node. or temporarily disable this patch: patch/kernel/archive/sunxi-6.12/series.conf#L472