Hqnicolas

what we need to find? ~taken from a working kernel 6.6 mainline~ dmesg: rfkill: journalctl -b | grep Bluetooth gpioinfo

can you list the improvements? sudo apt-get update sudo apt-get upgrade

Updating some HDMi Audio fix K510 V7, no HDMi audio until now Found this HDMI fix sudo systemctl status ap6335-bluetooth gpioinfo rfkill Full dmesg journalctl -b | grep Bluetooth

Updating some bluetooth fix K610 V12, doesn't work, but it was there on HCi Line talking.... sudo systemctl status ap6335-bluetooth gpioinfo rfkill Full dmesg journalctl -b | grep Bluetooth

Updating here some bluetooth fix K610 V11, doesn't work, but it was there.... gpioinfo Full dmesg rfkill journalctl -b | grep Bluetooth sudo systemctl status ap6335-bluetooth Found some answer in other forums: Could be Pull down or Pull Up pins on UART

Tencent box Aurora 5 Pro was probably a better experience than H96MAX could give you H96MAX V58 = more expensive than an open source SBC H96MAX V58 = not reliable EMMC or RAM chips

Can Somebody help? Wifi works, but, bluetooth dont... This is the Kernel 6.1 image V11

If the board is not detected on your PC, try pressing the reset button behind the audio jack connector, and keeping it pressed for two seconds while giving power to the board and then try again with the male-to-male cable.

Can Somebody help? Wifi works, but, bluetooth dont... $ rfkill ID TYPE DEVICE SOFT HARD 0 bluetooth hci0 blocked unblocked 1 wlan phy0 unblocked unblocked 2 bluetooth hci1 blocked unblocked dmesg

it will never happend.... I promess you. my next project will be RK3576 rk3588 desnt make sense for a TV box.... cheap EMMC, Cheap WIFI, cheap RAM, and big price.

UEFI Release today https://github.com/hqnicolas/h96v56_uefi/releases/tag/v1.2.1

Today I Build the UEFI for this board https://github.com/hqnicolas/h96v56_uefi/releases/tag/v1.2.1 edit: It doesn't worth the effort.... This board isn't made with UEFI in mind, it's too limited

this part of the story I know, this is from where i came from 3318 -> 3328 -> 3566 ... I never went through this transition from nand to emmc

I don't have this board. in my mind https://github.com/armbian/build/tree/v22.08 will build for armhf.... I parachuted in here, and I've learned a few things already.... I'll let the professionals answer.

nand is really necessary, but I wanted to understand why SD cards didn't suffer from the lack of FTL software. I was thinking of why we couldn't just run NAND as sdhci but SD cards have cotroller inside.....

Build legacy it with v22.08 armbian https://github.com/armbian/build/blob/v22.08/patch/kernel/rockchip64-legacy git clone --depth 1 --branch v22.08 https://github.com/armbian/build cd build ./compile.sh

this is what I call "son of a rockchip" they promess functions that contains proprietary software they make a kernel and abandon it, they don't put things in the mainline for legacy. Without Armbian developing these rockchip devices they will go down in history as industrial waste

no, because the kernel can't see nand devices, this is why it cant find the UUID the device dont exist for kernel mainline My opinion = SDCARD K6.6 > NAND k4.4

wow! thats unespected.

you can run the command: $lsblk $blkid when the image was mounted on your linux desktop computer and take the UUID from the loop ROOTFS partition i think the command fdisk -l disk_image.img wont return the correct UUID of partition inside Disc image

ok..... you can edit your image file before drop on multitool unzip the file and rename it to disk_image.img mount the image to a temp folder with the following commands: sudo losetup --partscan /dev/loop14 disk_image.img mkdir /tmp/disk_image sudo mount /dev/loop14p1 /tmp/disk_image ####### EDIT all files you want inside /tmp/disk_image/boot ########## sudo fstrim -v /tmp/disk_image sudo umount /tmp/disk_image sudo losetup --detach /dev/loop14 zip files back to small size and drop to muititool

open the SD card on other linux computer and edit boot/armbianEnv.txt boot args to your UUID $lsblk $ blkid

🏆 Become a sponsor, help to add other boards in armbian standart, you don't need to be a programmer to help the community, just need a copy of the ARM BOARD and a x86 computer to compile new versions. If you like what you see here and want to help: Donate Armbian the like button only costs a few dollars. Armbian Needs you help! Product Specification: Chipset: Rockchip RK3576 Octa Core ARM Mali G52 MC3 WIFI: WiFi6 11ax 1x1 80 MHz wifi controller: AP6275P RAM: DDR4 4GB/8GB ROM: eMMC 32GB/64GB/128GB OS: Android 14.0 || Armbian Vendor 6.1 Ethernet: 1000M Standard RJ-45 Bluetooth: BT 5.0 The RK3576 is indeed a lower-cost SoC but features four Cortex-A72 and four Cortex-A53 cores instead Android Base Files: H96-RK3576-ANDROID.dts H96-RK3576-ANDROID.dts H96-RK3576-BOX.dtb H96-RK3576-BOX.dtb RK3576_MiniLoaderAll.bin Mainline status: Verify wifi controller: AP6275P Wifi Driver: https://drive.google.com/file/d/1n6x4tg5Xh24nWllOTJTq1ldVyDkK8W2Q/view?usp=sharing Flashing Tools: https://drive.google.com/file/d/1nLgPCBN0qmbzufWDFmISYc92JUpvwMPc/view?usp=sharing build_armbian.csc: https://drive.google.com/file/d/1VNR5QJlPylPsce9PI9O2TB3wOpshK2Bh/view?usp=sharing @hzdm Stock Firmware: method https://drive.google.com/file/d/1zLGvIxLE6vf8iSTjsyEr-Ly4MZ6ZahBB/view?usp=sharing Flashing Firmware Tutorial Factory Firmware for H96 Max M9 https://disk.yandex.ru/d/pWGEtRel0P9ejg https://drive.google.com/drive/folders/1g63F8fGSLEA9iK2_Mqzd6F0xfaTRnGlm?usp=sharing Factory Firmware for H96 Max M9S https://disk.yandex.ru/d/H17eGTYCjgmCsg https://drive.google.com/drive/folders/1Q360l5XbTVsWIvWkqy2xJ0sLpqHRSApM?usp=sharing TTL debug: RX TX GND pins: Force board Maskrom Mode Maskrom Pins:

I dont have this board, but i think you can check your vp routing and vop &vp0 { rockchip,plane-mask = <(1 << ROCKCHIP_VOP2_CLUSTER0 | 1 << ROCKCHIP_VOP2_ESMART0 | 1 << ROCKCHIP_VOP2_SMART0 | 1 << ROCKCHIP_VOP2_CLUSTER1 | 1 << ROCKCHIP_VOP2_ESMART1 | 1 << ROCKCHIP_VOP2_SMART1)>; rockchip,primary-plane = <ROCKCHIP_VOP2_SMART0>; }; &hdmi_in_vp0 { status = "okay"; }; &hdmi_in_vp1 { status = "okay"; };

@paradigman had trouble finding the official Armbian images for H96 max I want to make it clear to everyone that now The H96 MAX Became Full supported by armbian Mainline 31/05/2024 Latest Release: https://github.com/armbian/community/releases/tag/24.8.0-trunk.6