Active threads

@jock Please help. Worst TV-box PCB I've ever seen in my life. Hardware: H96 Max "8K Ultra HD" (round case) PCB: RK3528_DDR3_8X4_V12 SoC: Rockchip RK3528 4GB DDR3 (8x Samsung K4B4G0446B) 64GB eMMC Samsung KLMCG2KETM WiFi: SKYWB8800 / SG-WB800E (AIC8800) Android 13, kernel 5.10.157, build RZX.V01.20240924.1740 I have TWO boards (same PCB revision, same markings). Both have DEBUG pads clearly labeled TX / GND / RX. UART completely silent in all combinations. Tried two different adapters: FTDI FT232 (ID 0403:6001) Silicon Labs CP2102 (ID 10c4:ea60) Both show up in dmesg fine, /dev/ttyUSB0 created, picocom opens. When powering device on — silence or garbage at all baud rates (115200, 230400, 460800, 921600, 1000000, 1152000, 1500000, 2000000, 3000000). Soldering done by a professional, crossover connection: adapter TX → board RX adapter RX → board TX GND ↔ GND VCC NOT connected (device powered separately) Loopback test on adapters works — adapters are OK. Devices are alive — Android boots normally, AIDA64 shows everything fine. Tested on both boards with both adapters — silence everywhere. Only garbage appears when physically jiggling wires (clearly body static, not device signal). My hypotheses: Vendor disabled UART output in stock loader/TPL for boot speed TX/RX pads repurposed as GPIO (LED / IR / etc.) DEBUG pads are actually NOT UART but JTAG/something else UART works but on some non-standard baud rate In fensoft U-Boot defconfig (https://github.com/fensoft/rk3528-tvbox) I see: CONFIG_BAUDRATE=1500000 CONFIG_DEBUG_UART_BASE=0xff9f0000 CONFIG_DEBUG_UART_CLOCK=24000000 Meaning fensoft uses this UART on similar boards. Why doesn't mine work? Background: spent 3 days trying to PXE boot Armbian. U-Boot (Ilya's + fensoft) works, TFTP/NFS works, kernel loads, initrd loads, DTB loads. But after booti the kernel dies instantly, so I need UART to see panic message. Tried many DTBs: evb1-ddr4, evb2-ddr3, android-native, nanopi-zero2, armsom-sige1, vontar-dq08, even stock Android DTB extracted from boot.img — all silent. Anyone experienced this on H96 Max RK3528 DDR3? Any way to force UART enable via some fastboot/adb command on Android before reboot? Attaching photos: PCB with RK3528_DDR3_8X4_V12 marking Close-up of DEBUG pads with soldered wires SG-WB800E WiFi module Thanks in advance for anyone who reads this!

Help needed (previous update): What should be edited is this file? sudo pico arch/arm64/boot/dts/allwinner/sun50i-h313-x96q-lpddr3.dts Thanks in advance.

@xuyitao Did your build pass? Can the NPU handle Ollama?

As a workaround I installed Armbian_community_26.2.0-trunk.732_Orangepi3b_trixie_vendor_6.1.115_minimal .img.xz and USB is OK, anyway ethernet is functional.

@fensoft I am using your current image 3.0.0_r2 in H96 Max M1 with USB Hub + USB to Ethernet adapter successfully. Its really energy efficient solution which can run 24 x 7 without costing much. However I am trying to set this up on a dq08 box with 4 GB/64 GB Model. I am able to install dq08_ha_supervised_3.0.0_r2.zip without any issue. However due to recent support changes from the application, I am unable to continue further with the setup. I tried to install docker version to set this up but getting error "invalid argument: in-kernel BTF is malformed (1 line(s) omitted)". Not seeing much on this error in the interwebs but there are suggestions that this could be due to old kernels/. Is there a way we can update this kernel and OS to Armbian Trixie or will it brick the dq08? Have you got a chance to look at the updated installer image?

same here: RADXA 4SE

Okay so then we have some issues here This is clearly wrong since these packages come from upstream Debian and cannot/will not work with Armbian kernels. This shall be reported here: https://github.com/armbian/configng/ Then you were lucky some working headers were present https://docs.armbian.com/Developer-Guide_Build-Preparation/ Or in very short: git clone the repo ./compile.sh BOARD=rockpi-4bplus BRANCH=current kernel Check output/debs for your packages Install via dpkg -i on the target board

Aiee! Installed my old "Noble" image. Updating will remove kernel 6.18.18 and install 6.6.99 and also has the error in the firmware package as decribed above by @VBB. Also, that funny "cli.github.com/packages" repo does not work. While that kernel downgrade is probably caused by linux-image-current-spacemit moved from 6.6.99 to 6.18.x recently (and the Armbian repos are out of date somehow) that firmware package should update without any errors. Will need time to sort this out. Anyhow, the "Noble" image works with GPU-activated Gnome desktop as long as you do not update (downgrade)...

I published my Vontar H618 bring-up patch set here: https://github.com/aco-art/vontar-h618-armbian-patche It includes the Armbian userpatches, U-Boot/kernel changes, and diagnostics tools I used for this box. Tested on my 4 GiB DDR3 Vontar H618 unit and shared in case it helps with similar H618/H616-class TV boxes. On my tested unit, Wi-Fi, Bluetooth, LAN, HDMI output, and the basic GPU/display path are working with this baseline.

I'm having the same issue after upgrading. I do backups on an HDD via USB for the two drives on my HC4 I was on Bullseye this year and was planning on moving up to Bookworm for a bit, but was hit with the issue. I decided to jump then into Trixie in the hopes that a more recent kernel would fix it, but I'm still facing it. kernel: Linux odroidhc4 6.18.10-current-meson64 dmesg error msg: usb usb1-port2: connect-debounce failed

The orange pi zero 2w is configured to only start u-boot from the microSD in the built-in microSD. You would have to: * recompile that uboot to load the initramfs and the kernel from your alternative storage (did you really mean HDD? which connector would you use?) or * load initramfs and kernel from the typical microsd /boot partition, but configure the kernel argument line to accept the HDD as the rootfs (make sure that the initramfs contains the kernel modules, and the hdd name is in the /etc/fstab file) or https://jamesachambers.com/orange-pi-zero-2-usb-ssd-boot-guide/

@lsdlsd88 hello! Thanks for sharing the photos and the serial logs; it looks like the stock firmware did not pick up the sdcard at all. The sdcard seems to be detected, but for some reason the rockchip miniloader of the stock firmware does not it as first source. Are you able to retrieve the first 100-200 megabytes of the original firmware via serial? You should be able to use dd even within Android. edit: ah-ha ok, I understand! there is misconfiguration in the webserver and the link changes; thanks, I updated it!

Yes, you can completely resize it. You can also turn it to ZFS volume, and boot off of it. Just rebuild u-boot with ZFS support. Or ask, and I will provide patches required to have it.

It is. Before I managed to rebuild u-boot with ZFS support, I had to boot off of EMMC. I shrunk first partition with kernel, initrd etc, and then made another one with actual FS. Temporary solution for me back then. But gave me time to rebuild everything and enable native ZFS boot. Since then, I use EMMC only as a ZFS volume (another one in the mirror is NVME drive). never used armbian-config though - I am old-schooler, so I had to build whole stack myself to get what I wanted.

Use armbian imager for flashing it, arduino flasher cli is not compatible

current_6.6.99_minimal (desktop build has the snd-usb-audio module)

@Vinicius Guastala Thank you for your feedback. Your patches have already been merged into my repository.

@KhanhDTP are you using esync of wine? NTsync is available on 6.18+ rk3588 kernels. I think that may give a performance improvement.

I have just turned my machines on today and now does the PWM signal on node 3 work, but it is still behaving weird. It is running around 3000 RPM with a pwm1 value of 3, where node 1 need a pwm1 value around 70. The pwm1 was working for 2 hours after that full speed I am currently focusing on fix node 3 (Healthy) which are running the same kernel as node 1 (Healthy) . I checked the dtb files using a sha256sum and that matched on both machines. I did also validate the kernel checksum which also match.

I want to give it a try on MeCool KM6 Deluxe, just started researching.

Thank you for any information... when I have more time I will try with the help of AI... because I don't have enough knowledge myself 🙂 regards

Using our XR expertise, Collabora created a standalone XR experience for our 1% for the Planet partner, SOMAR, to showcase the direct impact of underwater noise pollution on marine life. View the full article

You need to look into github changes then, everything is traceable, but certainly not an easy and quick thing to do.

rk3588-pcie_bifurcation_2x2-uboot.patchrk3588-pcie_bifurcation_2x2.patch Attached are two patches I've prepared. One for uBoot (to correctly recognize split pcie3x4 to two independent controllers, pcie3x4 and pcie3x2), and one for DT of NanoPC T6. This basically allows you to use trimmed-down bifurcation adapter. The adapter in question must be trimmed down/cut to fit on the back of the board. Tested with 2x NVME, and 1xNVME and QCNFA765 wireless card. I'll post photos later once I'll disconnect the board again from my setup. BEWARE!!! If you'd plan to use more than one ath11k wireless card, you'd need QRTR patch. Since the SBL enums changed in recent kernel 6.18.18+, I am also preparing modified kernel patch (originally for OpenWRT by Hauke Mehrtens and Robert Marko) to allow for more than one ath11k wireless to be installed. Will post later with new patch for it. root@ap-voyager:~# lspci -nn 0000:00:00.0 PCI bridge [0604]: Rockchip Electronics Co., Ltd RK3588 [1d87:3588] (rev 01) 0000:01:00.0 Network controller [0280]: Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter [17cb:1103] (rev 01) 0001:10:00.0 PCI bridge [0604]: Rockchip Electronics Co., Ltd RK3588 [1d87:3588] (rev 01) 0001:11:00.0 Non-Volatile memory controller [0108]: Shenzhen Longsys Electronics Co., Ltd. Lexar NM610 PRO NVME SSD (DRAM-less) [1d97:1202] (rev 01) 0002:20:00.0 PCI bridge [0604]: Rockchip Electronics Co., Ltd RK3588 [1d87:3588] (rev 01) 0002:21:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) 0003:30:00.0 PCI bridge [0604]: Rockchip Electronics Co., Ltd RK3588 [1d87:3588] (rev 01) 0003:31:00.0 Network controller [0280]: Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter [17cb:1103] (rev 01) 0004:40:00.0 PCI bridge [0604]: Rockchip Electronics Co., Ltd RK3588 [1d87:3588] (rev 01) 0004:41:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) root@ap-voyager:~#