Active threads

ok, thx

It's enabled by default. I believe that you have the wires swapped. There's a topic here about it where I also added a overlay to adjust what speed at which temperature. I'm not sure if the overlay is still compatible, but since you've already found the source you can change it accordingly.

mihanson@armbi400:~$ sudo poweroff Broadcast message from root@armbi400 on pts/0 (Thu 2025-09-04 07:29:16 PDT): The system will power off now! mihanson@armbi400:~$ [41893.451514] reboot: Power down [41893.454658] ------------[ cut here ]------------ [41893.459337] Voluntary context switch within RCU read-side critical section! [41893.459354] WARNING: CPU: 0 PID: 1 at kernel/rcu/tree_plugin.h:331 rcu_note_context_switch+0x4e0/0x530 [41893.475859] Modules linked in: sg rfcomm cmac aes_arm64 algif_hash algif_skcipher af_alg bnep zram zsmalloc binfmt_misc hci_uart btbcm bluetooth ecdh_generic ecc bcm2835_codec(C) bcm2835_v4l2(C) bcm2835_isp(C) bcm2835_mmal_vchiq(C) v4l2_mem2mem vc_sm_cma(C) videobuf2_dma_contig videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_bcm2835(C) videodev snd_pcm videobuf2_common snd_timer mc raspberrypi_hwmon snd raspberrypi_gpiomem i2c_dev drm drm_panel_orientation_quirks backlight fuse bonding ipv6 brcmfmac_wcc brcmfmac cfg80211 rfkill brcmutil uio_pdrv_genirq uio nvmem_rmem [41893.527454] CPU: 0 UID: 0 PID: 1 Comm: systemd-shutdow Tainted: G C 6.12.44-current-bcm2711 #1 [41893.537603] Tainted: [C]=CRAP [41893.540606] Hardware name: Raspberry Pi 400 Rev 1.0 (DT) [41893.545989] pstate: 600000c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [41893.553048] pc : rcu_note_context_switch+0x4e0/0x530 [41893.558080] lr : rcu_note_context_switch+0x4e0/0x530 [41893.563112] sp : ffff80008002b770 [41893.566466] x29: ffff80008002b770 x28: ffff2262c6ffb3c0 x27: ffff2262c0c5f8c0 [41893.573707] x26: ffff2262c0260000 x25: ffffcc22d85831f4 x24: 0000000000000000 [41893.580947] x23: 0000000000000000 x22: ffff2262c0260000 x21: ffffcc22d98b3070 [41893.588187] x20: 0000000000000000 x19: ffff22637b779fc0 x18: 0000000000000006 [41893.595426] x17: ffffcc22d97fb000 x16: 00000000a53a0512 x15: ffff80008002b0d0 [41893.602666] x14: 0000000000000000 x13: 216e6f6974636573 x12: 206c616369746972 [41893.609905] x11: 6320656469732d64 x10: ffffcc22d96d7a28 x9 : ffffcc22d7724ed8 [41893.617145] x8 : 00000000ffffefff x7 : ffffcc22d96d3960 x6 : 00000000000002b3 [41893.624384] x5 : 00000000000002b4 x4 : 40000000fffff2b3 x3 : 0000000000000000 [41893.631623] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff2262c0260000 [41893.638863] Call trace: [41893.641336] rcu_note_context_switch+0x4e0/0x530 [41893.646016] __schedule+0xb4/0xe70 [41893.649463] schedule+0x3c/0x148 [41893.652733] schedule_timeout+0x98/0x1a0 [41893.656709] wait_for_completion_timeout+0x80/0x160 [41893.661653] mbox_send_message+0xf8/0x140 [41893.665716] rpi_firmware_property_list+0x104/0x298 [41893.670662] rpi_firmware_property+0x78/0xc8 [41893.674988] rpi_exp_gpio_get_polarity+0x68/0x100 [41893.679760] rpi_exp_gpio_dir_out+0x6c/0x120 [41893.684089] gpiod_direction_output_raw_commit+0x6c/0x348 [41893.689562] gpiod_direction_output+0xa8/0x1b8 [41893.694065] gpio_poweroff_do_poweroff+0x2c/0xd0 [41893.698747] sys_off_notify+0x48/0x80 [41893.702458] notifier_call_chain+0x80/0x140 [41893.706699] atomic_notifier_call_chain+0x44/0x70 [41893.711468] do_kernel_power_off+0x5c/0x80 [41893.715618] machine_power_off+0x40/0x58 [41893.719594] kernel_power_off+0x88/0x98 [41893.723479] __do_sys_reboot+0x1e0/0x240 [41893.727452] __arm64_sys_reboot+0x2c/0x40 [41893.731514] invoke_syscall+0x50/0x120 [41893.735314] el0_svc_common.constprop.0+0x48/0xf0 [41893.740083] do_el0_svc+0x24/0x38 [41893.743441] el0_svc+0x38/0x120 [41893.746622] el0t_64_sync_handler+0x120/0x130 [41893.751037] el0t_64_sync+0x190/0x198 [41893.754745] ---[ end trace 0000000000000000 ]--- 25.8.1 Trixie Armbian image and EXT4 FS. Does not happen on reboot, just poweroff. The below also produce the same result. $ sudo shutdown -H now $ sudo systemctl poweroff mihanson@armbi400:~$ armbianmonitor -u Collecting info and sending to paste.armbian.com, wait... Failed grabbing info (pipe 3 result 22) and sending to server paste.armbian.com. Collecting info and sending to paste.next.armbian.com, wait... https://paste.next.armbian.com/oxawoposil Please post the URL in the forum where you've been asked for.

moved

@LanMarc77, I think you meant to tag @laibsch there What you're saying sounds like it could be a good option.

Actually, the connections on the cable harness appear to be good as well as all the capacitors. They are not expanded and they are not leaking--and no, I am not certain. I did not consider that it might be a board issue because I sniffed the board, there were no unusual odors when the system is powered up. Visually nothing appeared burnt. The failure occurred randomly after functioning for 4+ years. It has always been connected to an Online UPS that supports AVR, and Pure Sinewave on my server rack. I am not proficient at soldering, nor do I have a microscope, soldering iron or any of the required accessories to attempt a repair. For testing purposes, yesterday, I supplied power using an external power source from a USB enclosure and it worked. SATA Ports 1 and 2 are both functional, it is definitely related to power. I am meeting with my CEO tomorrow to discuss purchasing a new NAS type system. Leaning towards an HPE MicroServer Gen11. Going from a fantasic little affordable unit to an actual server that is going to cost around CAD$4,000 (price includes HDDs). YIkes. Thank you to everyone that took the time to read and reply though. I appreciate you, your time, and your suggestions. I was hoping I could just buy a cable and move on lol.

Well I tried everything to make it work, including switching from PoE to a proven USB power supply, nothing worked. The only thing that worked is flashing back the latest Radxa bullseye image with 5.10.110 kernel, and upgrading to bookworm. I have a lot of errors at boot, so I might consider updating the kernel at some point, but I have absolutely no idea how to do that without flashing a new image. Considering 5.10.110 is the last kernel available from Radxa, I think I'm stuck... I suppressed the radxa apt in the sources.list as there is no bookworm apt, only bullseye. Could I still use the bullseye radxa apt with a bookworm debian? [ 59.024477] ramoops ramoops: failed to locate DT /reserved-memory resource [ 59.084556] fiq_debugger fiq_debugger.0: IRQ fiq not found [ 59.084581] fiq_debugger fiq_debugger.0: IRQ wakeup not found [ 59.084597] fiq_debugger_probe: could not install nmi irq handler [ 60.711536] rockchip-usb2phy ff770000.syscon:usb2-phy@e450: IRQ index 0 not found [ 60.714528] rockchip-usb2phy ff770000.syscon:usb2-phy@e460: IRQ index 0 not found [ 60.723981] rkvdec_init:1230: failed on clk_get clk_hevc_cabac [ 60.724074] mpp_rkvdec ff660000.rkvdec: shared_video_hevc_cabac is not found! [ 60.724090] rkvdec_init:1261: No hevc cabac reset resource define [ 60.746975] rockchip-vop ff8f0000.vop: missing rockchip,grf property [ 60.747264] rockchip-vop ff900000.vop: missing rockchip,grf property [ 60.750685] no ATF memory for init [ 60.763340] no ATF memory for init [ 60.767736] rk_gmac-dwmac fe300000.ethernet: cannot get clock clk_mac_speed [ 61.067311] vcc_cam: failed to get the current voltage: -EPROBE_DEFER [ 61.067671] vcc_mipi: failed to get the current voltage: -EPROBE_DEFER [ 61.090893] vcc_sdio: unsupportable voltage range: 3300000-3000000uV [ 61.094146] rockchip-dmc dmc: Failed to get ddr_leakage [ 61.094884] rockchip-dmc dmc: could not find power_model node [ 61.099683] rksfc_base v1.1 2016-01-08 [ 61.695258] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout! [ 61.695324] rockchip-pcie f8000000.pcie: deferred probe failed [ 69.217783] rk-multicodecs es8316-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length is not even [ 69.309154] rk-multicodecs es8316-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length is not even [ 69.456788] debugfs: File 'Left Hp mixer' in directory 'dapm' already present! [ 69.456983] debugfs: File 'Right Hp mixer' in directory 'dapm' already present! [ 69.457046] debugfs: File 'HPCP L' in directory 'dapm' already present! [ 69.457078] debugfs: File 'HPCP R' in directory 'dapm' already present! [ 69.457127] debugfs: File 'HPVOL L' in directory 'dapm' already present! [ 69.457157] debugfs: File 'HPVOL R' in directory 'dapm' already present! [ 70.938277] udc fe800000.usb: failed to start radxa-otgutils: -19 [ 81.008640] ieee80211 phy0: brcmf_escan_timeout: timer expired [ 89.540144] hdmi-audio-codec hdmi-audio-codec.5.auto: hdmi_codec_startup doesn't support capture [ 89.540187] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22 [ 89.540706] hdmi-audio-codec hdmi-audio-codec.5.auto: hdmi_codec_startup doesn't support capture [ 89.540728] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22 [ 89.541174] hdmi-audio-codec hdmi-audio-codec.5.auto: hdmi_codec_startup doesn't support capture [ 89.541195] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22 [ 6419.589939] hdmi-audio-codec hdmi-audio-codec.5.auto: hdmi_codec_startup doesn't support capture [ 6419.589981] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22 [ 6419.590499] hdmi-audio-codec hdmi-audio-codec.5.auto: hdmi_codec_startup doesn't support capture [ 6419.590521] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22 [ 6419.590978] hdmi-audio-codec hdmi-audio-codec.5.auto: hdmi_codec_startup doesn't support capture [ 6419.591003] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22

@dale looking at the openvfd_x98h.dtso file you shared, openvfd uses these pins: openvfd_gpio_clk = <&pio 2 7 0>; openvfd_gpio_dat = <&pio 2 2 0>; openvfd_gpio_stb = <&pio 2 12 0>; So you should try with their equivalent: mosi-gpios = <&pio 2 2 GPIO_ACTIVE_HIGH>; /* mosi is the same as openvfd_gpio_dat */ sck-gpios = <&pio 2 7 GPIO_ACTIVE_HIGH>; /* sck is the same as openvfd_gpio_clk */ cs-gpios = <&pio 2 12 GPIO_ACTIVE_LOW>; /* cs is the same as openvfd_gpio_stb */

That will definitely make you not get hardware accelerated video Make sure to follow the 3 commands to install the custom repo, its certificate and higher priority: sudo wget http://apt.undo.it:7242/apt.undo.it.asc -O /etc/apt/trusted.gpg.d/apt.undo.it.asc . /etc/os-release && echo "deb http://apt.undo.it:7242 $VERSION_CODENAME main" | sudo tee /etc/apt/sources.list.d/apt.undo.it.list $ echo -e "Package: *\nPin: release o=apt.undo.it\nPin-Priority: 600" | sudo tee /etc/apt/preferences.d/apt-undo-it sudo apt update Then check that the new custom dpkgs are available for install/upgrade apt list ffmpeg-whatever Here's how I force install a specific version: sudo apt install packagename=nn.nn.n

@ebin-dev@mtlmarko189 Not sure if this issue can be resolved. I've been running tests with different chip versions and discovered that the first batch of Helios64 devices includes an unreliable chip. Take a look at this: root@helios64:~# lsusb -v -d 0bda:8156 | grep bcdDevice bcdDevice 30.00 bcdDevice 31.04 According to cnx-software 30.00 corresponds to RTL8156 31.00 corresponds to RTL8156B 31.04 correspond to the third version, RTL8156BG So far, the RTL8156BG has been working better with Linux kernel 6.12.42. P.S. The workaround suggested by @ebin-dev helps reduce the symptoms, but the NIC is still sending corrupted packets.

Thank you for your work, @dg4gg8cb9s

This is an H96Max Factory default work around, no TV box device really turn off, it's the way the factory deal with the "remote control" power on function, the device is always waiting for a IR remote control to trigger. You can find a way around it on the pmic section from DTS. Thats a problem caused by BOM of materials in the factory, they start to use a new wifi card because of chip shortages. You can work around it using this method

You will need to flash an android "Update image" first, into EMMC, to go back to factory defaults. https://wiki.youyeetoo.com/en/YY3568/unpack https://drive.google.com/drive/folders/11BrqafnkEyFaM-D0gaPFhrmnRM47JAEU MaskRom mode upgrade firmware First of all, make sure that you have entered the MaskRom upgrade mode, and then perform the following firmware upgrade operations. Upgrade firmware in loader mode Open the AndroidTool tool, the board enters the upgrade mode, and a LOADER device will be found on the AndroidTool. Then perform the following upgrade firmware operation.

From @fevangelou 1. Install the "rkdeveloptool" tool first, as instructed in: https://docs.radxa.com/en/zero/zero3/low-level-dev/rkdeveloptool?host-os=debian sudo apt-get update sudo apt-get install -y libudev-dev libusb-1.0-0-dev dh-autoreconf pkg-config libusb-1.0 build-essential git wget git clone https://github.com/rockchip-linux/rkdeveloptool cd rkdeveloptool autoreconf -i ./configure make -j $(nproc) sudo cp rkdeveloptool /usr/local/sbin/ At the time of writing, this installed version 1.32. If you installed "rkdeveloptool" from Ubuntu's repos, it would install version 1.0 which may work, but let's be on the safe side here... 2. Connect and boot the device to loader/maskrom mode 2.1 While pressing the reset button (back/right) with a pin, connect the USB 2.0 port (back/left) and the power cable. Gotta be careful here not to miss the reset button pressing while connecting the cables. 2.2 Use the rkdeveloptool tool to identify the device and the mode it is on ("loader" or "maskrom"). $ rkdeveloptool ld ...should show the connected device if point 2.1 was successful - e.g. on my 8GB RAM device it printed this: DevNo=1 Vid=0x2207,Pid=0x350a,LocationID=304 Loader Or after I had already flashed Armbian, it would show: DevNo=1 Vid=0x2207,Pid=0x350a,LocationID=304 Maskrom (If you installed "rkdeveloptool" from Ubuntu's repo, the command is "rkdeveloptool list" if I recall correctly - every other "rkdeveloptool" command following though is the same) Now grab the latest release of Armbian for this device. At the time of writing it was: https://github.com/armbian/community/releases/download/25.11.0-trunk.106/Armbian_community_25.11.0-trunk.106_H96-tvbox-3566_bookworm_current_6.12.44_minimal.img.xz (the name of the device is on the filename) Extract the included .img file with (sudo apt install xz-tools): $ unxz Armbian_community_25.11.0-trunk.106_H96-tvbox-3566_bookworm_current_6.12.44_minimal.img.xz 2.2.1 If in "loader" mode (see the last part of the command's output above), simply flash Armbian directly. E.g. $ sudo rkdeveloptool wl 0x0 Armbian_community_25.11.0-trunk.106_H96-tvbox-3566_bookworm_current_6.12.44_minimal.img (if you attempt to flash the attached bootloaders, you'll get a "device not supported" error - Armbian already contains a bootloader) 2.2.2 If in "maskrom" mode (e.g. if you are re-flashing Armbian), flash the bootloader first: # For the 8GB RAM device use the attached (in this post) H96-MAX-8gb-MiniLoaderAll.bin file $ sudo rkdeveloptool db H96-MAX-8gb-MiniLoaderAll.bin # For the 4GB RAM device use the attached (in this post) H96-MAX-4gb-MiniLoaderAll.bin file $ sudo rkdeveloptool db H96-MAX-4gb-MiniLoaderAll.bin ...and then re-flash Armbian as you did the first time: $ sudo rkdeveloptool wl 0x0 Armbian_community_25.11.0-trunk.106_H96-tvbox-3566_bookworm_current_6.12.44_minimal.img 2.3 Reboot the device with: $ sudo rkdeveloptool rd Done! If all goes well, once you reboot the device you will be asked to set a root password and optionally a sudo user. Rebooting afterwards you should now be greeted with: _ _ _ _ _ /_\ _ _ _ __ | |__(_)__ _ _ _ __ ___ _ __ _ __ _ _ _ _ (_) |_ _ _ / _ \| '_| ' \| '_ \ / _` | ' \ / _/ _ \ ' \| ' \ || | ' \| | _| || | /_/ \_\_| |_|_|_|_.__/_\__,_|_||_|_\__\___/_|_|_|_|_|_\_,_|_||_|_|\__|\_, | |___| |__/ v25.11 rolling for h96-tvbox-3566 running Armbian Linux 6.12.44-current-rockchip64 Packages: Debian stable (bookworm), possible distro upgrade (trixie) Updates: Kernel upgrade enabled and 2 packages available for upgrade Support: for advanced users (rolling release) IPv4: (LAN) 192.168.1.10 (WAN) 1.2.3.4 Performance: Load: 3% Uptime: 2 min Memory usage: 2% of 7.50G CPU temp: 40°C Usage of /: 3% of 57G Commands: Configuration : armbian-config Upgrade : armbian-upgrade Monitoring : htop Last login: Sat Aug 30 12:47:54 2025 Key points: - If you do this the first time, it's obviously a matter of just flashing the latest Armbian image directly. - You don't need to open the device or compile Armbian.

@djurny Sorry for the super late response. Here the answers on your questions: ls -Failh /dev/rtc* 457 lrwxrwxrwx 1 root root 4 Mar 7 01:56 /dev/rtc -> rtc0 107 crw------- 1 root root 253, 0 Mar 7 01:56 /dev/rtc0 542 crw------- 1 root root 253, 1 Mar 7 01:56 /dev/rtc1 ls -Failh /sys/class/rtc/ total 0 3926 drwxr-xr-x 2 root root 0 Jan 1 1970 ./ 10 drwxr-xr-x 63 root root 0 Jan 1 1970 ../ 8295 lrwxrwxrwx 1 root root 0 Jan 1 1970 rtc0 -> ../../devices/platform/soc/1f00000.rtc/rtc/rtc0/ 21463 lrwxrwxrwx 1 root root 0 Sep 3 23:18 rtc1 -> ../../devices/platform/soc/1c2ac00.i2c/i2c-0/0-0068/rtc/rtc1/ egrep -- . /sys/class/rtc/*/name /sys/class/rtc/rtc0/name:sun6i-rtc 1f00000.rtc /sys/class/rtc/rtc1/name:rtc-ds1307 0-0068 dmesg | egrep -i -- 'rtc' [ 1.042165] sun6i-rtc 1f00000.rtc: registered as rtc0 [ 1.042235] sun6i-rtc 1f00000.rtc: setting system clock to 1970-01-01T00:00:04 UTC (4) [ 1.774229] sun4i-drm display-engine: [drm] Cannot find any crtc or sizes [ 1.776966] sun4i-drm display-engine: [drm] Cannot find any crtc or sizes [ 19.347508] rtc-ds1307 0-0068: registered as rtc1 sudo hwclock --rtc=/dev/rtc0 # per default this is the H2+ built-in RTC 2025-09-03 23:32:07.935209+10:00 ==> date set to Australia (Tasmania) sudo hwclock --rtc=/dev/rtc1 # per default this is going to be the I2C RTC 2000-01-02 15:51:14.147878+11:00 ==> ?????????? So, I clearly don't understand the system. What do I want? Just the right time when connected to a wireless network. (If not available, my system switches to being an Access Point) If my system is acting as an Access Point, the date and time needs to be correct to, that's why I thought I need an RTC module. If not needed, how do I get the right time when my system operates as an Access Point. Thanks for helping

Hey there. Thanks for the detailed tutorial. I tried following it to install Armbian Trixie minimal on my Raspberry Pi 5's nVME (I'm on a headless setup with SSH access). The SD card that boots and runs the system so far is also an Armbian Trixie minimal installation. Apparently nobody has confirmed the instructions to work for that device / setup in this thread yet. So far I also have failed. After following through all steps my device wouldn't connect via ethernet (the LEDs didn't even blink). For simplifying things and rule out a source for possible mistakes, I then repeated the whole process without encrypting the drive, again without much success. Here's what I suspect to be the problem: The Armbian minimal image for the Raspberry family comes already with two partitions: a boot partition with a number of .dtb files for each device of the Raspberry family a "root" partition with all other files Device Boot Start End Sectors Size Id Type /dev/loop0p1 8192 532479 524288 256M b W95 FAT32 /dev/loop0p2 532480 3088383 2555904 1.2G 83 Linux I suspect it to boot in a different way than the image in the example, which seems to directily have all the files which I find in my second partition of the image. So, what I tried was to just create two partitions, mimicing the ones on the Image: Device Boot Start End Sectors Size Id Type /dev/nvme0n1p1 8192 532479 524288 256M b W95 FAT32 /dev/nvme0n1p2 532480 3907029167 3906496688 1.8T 83 Linux I would then just copy the contents of each partition respectively. But even that wouldn't boot the way it did with the SD card. Of course I could just use dd to copy the image to the 2TB nVME but that would take forever (20 h aprox.) and it wouldn't result in an encrypted system. My questions are: Is it even possible to use the way of copying boot files and contents in this tutorial to achieve a bootable nVME? If the image for the Raspi family relies on its own boot partition will I ever be able to use it for decrypting an encrypted drive before booting from it at all? Can I use it for both, booting the device and decrypting the drive, or would that be principally impossible? I'll be happy for any help for making it work or hint if the described procedure cannot work for my setup. Tonight I'll also join an install party and might have the opportunity to plug a screen to my Raspi and see if it gives hints during the boot sequence. EDIT: I think I understand now that this script is probably only for SD cards …

@Nick AHow to use your code repository(https://github.com/NickAlilovic/build) to add a 1.5GB RAM patch.

Thank you all, I appreciate your patience! 🙏 I'm not sure on how deep I should go here. I started to learn about the process to address the problem that 10mpbs ethernet not is not working on my Rockpi S and I now know enough to deal with this problem. So my feeling is to not go further but focus on the functional problem to solve it 😉 Thanks again!

@SteeMani also did some commands prompted by chatgpt since it said it was manufactored by allwinner also related to cortex-a53, aida64 said it too, so i doubt that mine are using a allwinner h313 chip

Collabora is headed to Amsterdam. Meet us at Booth A63 in Hall 14 as we showcase GStreamer Analytics combined with ML, hardware-accelerated video decoding in Dante Studio using GStreamer, remote rendering for standalone XR, and more! View the full article

Context of the TV boxes section might be helpful, especially in the sticky thread re their status in Armbian.

Hi! @jwalds did yo mange to make hw decoding work with cedrus? (Note: you initially wrote cedar_ve, that's a different driver) I'm fighting with a nanopi duo2. If it works at your end I'd like to know your setup kernel version armbianEnv.txt whatelse has been installed, how could you please provide your dts / dto ? T.

That sounds very interesting. Where can I read more about this? @m11k I hope you are still active in this forum.

For debian problems, do what I do: Get the cheapest raspberry Recreate the problem Ask the question in the raspberry forum Apply solution to Armbian XD