DreamDreams

@dfahren My box is some what smooth than yours. But only GUI part. I don't see much laggy. Mouse cursoe, dragging windows all work fine. But I still don't get smooth web video decoding. There is nothing special, just make sure you have correct package and kernel mod installed. root@h96-tvbox-3566:~# lsmod|grep panf panfrost 73728 0 gpu_sched 36864 1 panfrost drm_shmem_helper 16384 1 panfrost root@h96-tvbox-3566:~# lsmod|grep hantr hantro_vpu 249856 0 v4l2_vp9 20480 1 hantro_vpu v4l2_jpeg 12288 1 hantro_vpu v4l2_h264 16384 2 hantro_vpu,rockchip_vdec2 videobuf2_dma_contig 20480 2 hantro_vpu,rockchip_vdec2 v4l2_mem2mem 24576 3 hantro_vpu,rockchip_rga,rockchip_vdec2 videobuf2_v4l2 20480 4 hantro_vpu,rockchip_rga,rockchip_vdec2,v4l2_mem2mem videodev 237568 5 videobuf2_v4l2,hantro_vpu,rockchip_rga,rockchip_vdec2,v4l2_mem2mem videobuf2_common 53248 8 videobuf2_dma_contig,videobuf2_v4l2,hantro_vpu,rockchip_rga,videobuf2_dma_sg,rockchip_vdec2,v4l2_mem2mem,videobuf2_memops mc 53248 6 videodev,videobuf2_v4l2,hantro_vpu,videobuf2_common,rockchip_vdec2,v4l2_mem2mem root@h96-tvbox-3566:~# dpkg -l|grep mesa ii glx-alternative-mesa 1.2.2 arm64 allows the selection of MESA as GLX provider ii libegl-mesa0:arm64 25.0.1-2 arm64 free implementation of the EGL API -- Mesa vendor library ii libgl1-mesa-dri:arm64 25.0.1-2 arm64 free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-glx:arm64 22.3.6-1+deb12u1 arm64 transitional dummy package ii libglu1-mesa:arm64 9.0.2-1.1+b3 arm64 Mesa OpenGL utility library (GLU) ii libglx-mesa0:arm64 25.0.1-2 arm64 free implementation of the OpenGL API -- GLX vendor library ii libosmesa6:arm64 25.0.1-2 arm64 Mesa Off-screen rendering extension ii mesa-drm-shim:arm64 25.0.1-2 arm64 DRM shim libraries ii mesa-libgallium:arm64 25.0.1-2 arm64 shared infrastructure for Mesa drivers ii mesa-opencl-icd:arm64 25.0.1-2 arm64 free implementation of the OpenCL API -- ICD runtime ii mesa-utils 9.0.0-2+b1 arm64 Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:arm64 9.0.0-2+b1 arm64 Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:arm64 25.0.1-2 arm64 Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:arm64 25.0.1-2 arm64 Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:arm64 25.0.1-2 arm64 Mesa Vulkan graphics drivers

@Hqnicolas Thanks for the reminder. I patched the dts, now I can see network card in u-boot.

I'd like to netboot from u-boot, but found that there is no network driver enabled. I tried to compile u-boot by myself, attatched is my .config file. With this config u-boot still can't detect network card. Any idea which driver I should use? h96.config

For anyone who wants to force enable mesa vulkan driver, put following two lines to /etc/environment.d/99-vk.conf and reboot VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/panfrost_icd.aarch64.json PAN_I_WANT_A_BROKEN_VULKAN_DRIVER=1

I upgraded my mesa to 25.0.1-2, now my glmark2-es2-wayland scrore is down to 200, it used to be 450+. I'm using h96 tv box with rk3566 and latest Armbian trixie with Gnome. Also I force enabled mesa vulkan driver, vulkaninfo can see it. But Chromium stopped working. When I try to start chromium it will hang the whole GUI. Guess I'll have to wait a while until all these stablelize. BTW, my kernel version is 6.14.0-rc4-edge-rockchip64.

Another question, do we have to use Joshua Riek's u-boot? Should u-boot from Aribian just work? And the steps you mentioned above only affects u-boot right? What about kernel config and dts/dtb?

This shell script doesn't have any patch in it. Do you mean this dts patch file? @Hqnicolas

I'd like to try Joshua Riek's image, but not sure how. @Hqnicolas, your link in previous post is 404 now. I tried to boot kernel linux-image-vendor-rk35xx with rk3566-h96-tvbox.dtb but got instant kernel panic.

Is RK3399 more expansive? I was missled by my purchase price. And on paper, RK3399's Mali T860 is much weaker than RK3566's Mali G52.

Now I'm very disapointed with this box. Comparing to my Firefly-rk3399, it has 2x memory, newer CPU/GPU, but performance is worse. glmark2-es2-wayland score: RK3399 1100, RK3566 500 ffmpeg -hwaccel drm -benchmark on same AVC/H264 video, RK3399 40X, RK3566 10X And GUI smothiness is much worse than RK3399. I can feel the difference, and it is very obvious. Kernel version are both 6.12 mainline.

Another question, how can I determine whter my memory is capable of 1560MHz or 1056MHz? Below is u-boot output when reset. => reset resetting ... DDR 2d653b3476 typ 24/01/20-15:04:19,fwver: v1.21 ln LP4/4x derate en, other dram:1x trefi SRX ddrconfig:7 LPDDR4X, 324MHz BW=32 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=8 Size=8192MB tdqss: cs0 dqs0: 72ps, dqs1: -72ps, dqs2: -48ps, dqs3: -144ps, tdqss: cs1 dqs0: 72ps, dqs1: -72ps, dqs2: -24ps, dqs3: -144ps,

Got it working, the cause is that config CONFIG_ENV_IS_IN_MMC is not set. After setting this, saveenv appears.

I found the binary files. On my system they have different version. I successfully compiled and burn new u-boot to my board. But saveenv is still missing. # grep SAVEENV .config CONFIG_CMD_SAVEENV=y CONFIG_SAVEENV=y U-Boot 2024.07-armbian-2024.07-S3f77-P0000-H3f52-Vc494-Bda0a-R448a (Nov 19 2024 - 15:22:24 +0800) Model: Generic RK3566/RK3568 DRAM: 8 GiB (effective 7.7 GiB) Core: 251 devices, 25 uclasses, devicetree: separate MMC: mmc@fe2b0000: 1, mmc@fe310000: 0 Loading Environment from nowhere... OK In: serial@fe660000 Out: serial@fe660000 Err: serial@fe660000 Model: Generic RK3566/RK3568 Net: No ethernet found. Hit any key to stop autoboot: 0 Scanning for bootflows in all bootdevs Seq Method State Uclass Part Name Filename --- ----------- ------ -------- ---- ------------------------ ---------------- Scanning global bootmeth 'efi_mgr': Card did not respond to voltage select! : -110 No EFI system partition No EFI system partition Failed to persist EFI variables No EFI system partition Failed to persist EFI variables No EFI system partition Failed to persist EFI variables 0 efi_mgr ready (none) 0 <NULL> ** Booting bootflow '<NULL>' with efi_mgr Loading Boot0000 'mmc 0' failed EFI boot manager: Cannot load any image Boot failed (err=-14) Scanning bootdev 'mmc@fe2b0000.bootdev': Card did not respond to voltage select! : -110 Scanning bootdev 'mmc@fe310000.bootdev': Unknown uclass 'nvme' in label Unknown uclass 'scsi' in label No USB controllers found No ethernet found. No ethernet found. No more bootdevs --- ----------- ------ -------- ---- ------------------------ ---------------- (1 bootflow, 1 valid) => => => => => <INTERRUPT> => => saveenv Unknown command 'saveenv' - try 'help'

You are right, I didn't do the first two steps. I got the base config from running "./compile.sh BOARD=h96-tvbox-3566 BRANCH=edge uboot-config". Then 'make menuconfig' and make. It's hard to find documentation for compile u-boot only. Will try your steps. But where do I find file rk3568_bl31_v1.34.elf and rk3568_ddr_1560MHz_v1.13.bin? I could find it in the source folder.

I installed u-boot to eMMC, but found that there is no saveenv command, does anybody know why? Tried to compile u-boot myself but when I run make command in u-boot source I got following error: Image 'simple-bin' is missing external blobs and is non-functional: rockchip-tpl atf-bl31 /binman/simple-bin/mkimage/rockchip-tpl (rockchip-tpl): An external TPL is required to initialize DRAM. Get the external TPL binary and build with ROCKCHIP_TPL=/path/to/ddr.bin. One possible source for the external TPL binary is https://github.com/rockchip-linux/rkbin. /binman/simple-bin/fit/images/@atf-SEQ/atf-bl31 (atf-bl31): See the documentation for your board. You may need to build ARM Trusted Firmware and build with BL31=/path/to/bl31.bin Image 'simple-bin' is missing optional external blobs but is still functional: tee-os /binman/simple-bin/fit/images/@tee-SEQ/tee-os (tee-os): See the documentation for your board. You may need to build Open Portable Trusted Execution Environment (OP-TEE) and build with TEE=/path/to/tee.bin Image 'simple-bin-spi' is missing external blobs and is non-functional: rockchip-tpl /binman/simple-bin-spi/mkimage/rockchip-tpl (rockchip-tpl): An external TPL is required to initialize DRAM. Get the external TPL binary and build with ROCKCHIP_TPL=/path/to/ddr.bin. One possible source for the external TPL binary is https://github.com/rockchip-linux/rkbin. Some images are invalid make: *** [Makefile:1126: .binman_stamp] Error 103 I got following binary files in the folder: u-boot-dtb.bin u-boot-nodtb.bin u-boot-rockchip-spi.bin u-boot-rockchip.bin u-boot.bin But none of them starts with bytes "RKNS" as in /usr/lib/linux-u-boot-edge-h96-tvbox-3566/u-boot-rockchip.bin . So I suspect that they are not the one I should burn to eMMC.