Active threads

@Ryzer attached is the lightly redacted log (removed user and hostname; one mount point now shows as $HOME, because I simply used this instead of manual manipulations: gzip -ckd /var/log/armbian-hardware-monitor.log.1.gz|sed "s|$HOME|\$HOME|g; s|$USER|username|g; s|$(hostname)|host|g; s|$(hostname -s)|host|g" armbian-hardware-monitor.log.gz

This would be very very hard. Would likely take years and would likely never achieve full functionality. If you have access to the source code for the firmware that comes on the device you would have a chance.

My Banana Pi M2+ is running quite fine but something is amiss with bluetooth. bluetoothctl never shows any devices even when scanning for them and there are plenty of devices within arm's length. I am hoping for your help in diagnosing and ultimately fixing the issue. Logs:

Right, judging by only one instance in the topwise a721 dts: [ 3.446799] sun4i-drm display-engine: No panel or bridge found... RGB output disabled I am inclined to think that is configuring the panel. This can be validated by checking ls /sys/devices/platform/display-engine/drm/card0 or looking for simple-panel in lsmod. I suspect it may be a pin-muxing issue where the pins are not being set. now what these are set depends on the lcd panel type which could be LVDS or a parallel panel. I believe it should be LVDS but just wanted to confirm. Now the A10's pin controller section within the dtsi does not map out as many function as that of the A20 dtsi, so within the topwise a721 dts a pio node will be need to map out the pins that will later be requested and there function. Secondly attach the pin control handle to tcon0.

A few days ago I had an issue with a successfully running Armbian installation running from the NVME of my Orange Pi 5 that suddenly developed an issue with nothing being shown on my TV. So after seemingly not being to identify the problem, I started again, wrote the image to an SD card and then moved the installation to the NVME drive using armbian-config utility. So now that I have a set-up that works again, I want to instigate a more belt and braces approach and create an image of the NVME installation using GZIP to compress the image file and decided to use the DD option from terminal. Having tried well over a hundred different combinations of commands, I am unable to get things to work. I either get errors of Not a directory, No such file or directory or Is a directory The output of lsblk is NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mtdblock0 31:0 0 16M 0 disk mmcblk1 179:0 0 59.5G 0 disk └─mmcblk1p1 179:1 0 59.5G 0 part zram0 252:0 0 3.9G 0 disk [SWAP] zram1 252:1 0 50M 0 disk /var/log zram2 252:2 0 0B 0 disk nvme0n1 259:0 0 238.5G 0 disk └─nvme0n1p1 259:1 0 238.5G 0 part /var/log.hdd So in order to create the copy of the NVME installation, that is only taking up 13gb of the 238Gb total, to the root of a 64Gb SD card, completely empty and formatted to EXT4 via gparted, using the information above, can anybody see where I am going wrong. A few typical examples of command structures that I have tried are: sudo dd if=/dev/nvme0n1 of=/dev/mmcblk1/armbian.gz conv=sync bs=64K | gzip --stdout > bs=4M status=progress dd if=/dev/nvme0n1 conv=sync bs=64K | gzip --stdout > of=/dev/mmcblk1/armbian.gz dd if=/dev/nvme0n1p1 conv=sync bs=64K | gzip --stdout > of=/dev/mmcblk1p1/armbian.gz bs=4M status=progress This is the general template that I initially followed from a website dd if=/dev/SOURCE conv=sync bs=64K | gzip --stdout > /path/to/file.gz I've researched the use of the DD command until I am cross eyed.

dear Comose your are in the wrong topic this is not about rk3528 , please look at armbian forum for right please of rk3528 hallo Comose du bist hier am falschen ort , dies hier ist über rk322x board und nicht rk3528 , biite schaue in den anderen Bereichen nach rk35xx (Rk3518 / Rk3528)

I can do that but it does not provide any useful information on the subject in my opinion. Is there a way to downgrade to 25.8.0-trunk.313? According to this post, it might be useful to set the kernel option nvme_core.default_ps_max_latency_us resp. the DT overlay parameter pciex1_gen=3. How can the kernel (cmdline) option be set in Armbian? Regarding the DT overlay parameter pciex1_gen, should I follow this part of the documentation?

So, there is nothing more we can do here I think. Wait for rockchip to correct upstream.

Since U-Boot v2025.04 works very well on Orange Pi Zero v3 and has a shorter boot process time, if there was a possibility to switch to U-Boot v2504 for Orange Pi Zero V1, I would be grateful, as would probably other users of this SBC Regards

The issue appears to be two things. These two patches and the current defconfig(s) being used. drv-rtc-sun6i-support-RTCs-without-external-LOSCs.patch drv-rtc-sun6i-Add-Allwinner-H616-support.patch When I disable those patches and use my own defconfig everything works as it should. https://paste.armbian.com/tixixocubu The hard part here would be figuring out exactly what in the defconfig(s) are either breaking things or missing. Also if I disable those patches, what does it break on other units? I'm under the impression these patches were rejects from the original h616 bring up in mainline. But I could be wrong?

If you need hdmi support use vendor or edge kernel. 6.12 was released with a bare minimum of support for rk3588 so nonworking hdmi is kind a expected.

I added a patch that activates the gpu. https://lore.kernel.org/linux-sunxi/20250706025625.2707073-1-iuncuim@gmail.com A ready to install kernel is available for manjaro. But it's worth realizing that without output it will be useless at the moment.

v4l2loopback-dkms 0.12.7-2 fails to build make.log: DKMS make.log for v4l2loopback-0.12.7 for kernel 6.12.32-current-rockchip64 (aarch64) Sat Jul 5 09:16:17 PM CDT 2025 Building v4l2-loopback driver... make -C /lib/modules/6.12.32-current-rockchip64/build M=/var/lib/dkms/v4l2loopback/0.12.7/build modules make[1]: Entering directory '/usr/src/linux-headers-6.12.32-current-rockchip64' CC [M] /var/lib/dkms/v4l2loopback/0.12.7/build/v4l2loopback.o /var/lib/dkms/v4l2loopback/0.12.7/build/v4l2loopback.c: In function ‘vidioc_querycap’: /var/lib/dkms/v4l2loopback/0.12.7/build/v4l2loopback.c:717:9: error: implicit declaration of function ‘strlcpy’; did you mean ‘strncpy’? [-Werror=implicit-function-declaration] 717 | strlcpy(cap->driver, "v4l2 loopback", sizeof(cap->driver)); | ^~~~~~~ | strncpy cc1: some warnings being treated as errors make[3]: *** [scripts/Makefile.build:229: /var/lib/dkms/v4l2loopback/0.12.7/build/v4l2loopback.o] Error 1 make[2]: *** [/usr/src/linux-headers-6.12.32-current-rockchip64/Makefile:1945: /var/lib/dkms/v4l2loopback/0.12.7/build] Error 2 make[1]: *** [Makefile:224: __sub-make] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-6.12.32-current-rockchip64' make: *** [Makefile:43: v4l2loopback.ko] Error 2 Edit: I had the wrong make.log contents. The old one was after I tried to fix it and failing. The actual build error is missing strlcpy().

I've gone round in circles with this one and it seems that there might not be a solution, so will set it up again on the NVME drive. Thanks for all the help offered.

Pull Request submitted: https://github.com/armbian/build/pull/8360

I hadn't done an upgrade but a fresh install; (v25.5.1 for Raspberry Pi 3 Model B running Armbian Linux 6.12.28-current-bcm2711) Realised that I had the same problem, only channel 2 was present; though I only realised something was missing when I'd tried RaspberryOS on a Pi Zero with the same i2c device. Adding to the /boot/config.txt didn't of itself solve the issue; adding the i2c1 to the armbian-config overlays also didn't see. However I did find the `/boot/firmware/config.txt` that has a lot more settings, and seems to be where armbian-config edits Note the `dtparam-i2c_arm=on` line... which was commented out. Adding that back and it works... (well after figuring out I needed to level shift the i2c device but that's another story) # For more options and information see # http://rptl.io/configtxt # Some settings may impact device functionality. See link above for details # Uncomment some or all of these to enable the optional hardware interfaces dtparam=i2c_arm=on #dtparam=i2s=on #dtparam=spi=on # .. dtoverlay=dwc2 i2c0 i2c1 i2c-gpio vc4-kms-v3d

Remote backup maybe only as data ... e.g. restic / rsync programs In my opinion it is best to make a backup of the SD card in linux connect miniSD card and make a backup in terminal: fdisk -l if your SD card is: sda / sda1.... then choose sda ! and then make a backup: dd if=/dev/sda of=/path_to_backup.img status=progress Restoring the image to the SD card with the same size: dd bs=4M if=/path_to_copy.img of=/dev/sdb status=progress If you want to burn the image to a smaller capacity SD card because, for example, the system is only 30% occupied, use the program:PiShrink https://github.com/Drewsif/PiShrink it works great for me for Armbian 🙂 sudo pishrink.sh /path_to_backup.img / /new_backup-Pishrink.img

I use the Station M2 image with dtb joined. Adapt fdtfile entry in /boot/armbianEnv.txt as needed. rk3566-box-demo_x96x6_24-custom.dtb

please show the output of "apt policy zfs-dkms" but essentially, this looks the same as your other rodeo/struggle with this board and dkms. As mentioned there, you are much better off with btrfs instead of zfs on your SBC.

I confirm that this repository ffmpeg works for me: * Orange Pi Zero 3 * self built image with Debian Trixie and Xfce desktop * Linux Edge 6.15.0 * Login in Xfce X11 mode * follow all the instructions in original post * mpv plays most mp4s VERY SMOOTHLY * some resolutions will crash mpv with "Segmentation Fault" and cause a kernel crash shortly after Then, to make it work with an ili9488 LCD, I needed to change these: * install LCD DTS, firmware, remove plymouth (see my ili9488 thread) * I can't make X11 work with my LCD driver and panel-mipi-dbi-spi recently... (still investigating why it worked before) * but I can make it work with labwc and sway * install seatd (authorization library), labwc (I only have experience with labwc) and foot (wayland terminal) * Choose labwc instead of xfce in lightdm login * from SSH session: DISPLAY=:0 foot& * in foot: mpv videofile.mpv * it plays most mp4s VERY SMOOTHLY * some resolutions will crash mpv with "Segmentation Fault" and cause a kernel crash shortly after

Whatever garbage ones I can find on ebay for cheap. In this case: KIOXIA 256GB SSD BG5 M.2 2230 NVMe PCIe Gen4 x4 KBG50ZNS256G https://www.ebay.com/itm/176432690192

Good to meet a fellow armbian android tv box fan. We need a logo or shorthand alias for fans 🤣. ZFS - was easy but not clear. Inside armbian-config under System/Storage is a script to install ZFS support. I did this and it didn't work... then undid it and then installed it a second time and it worked. Somewhere in there I also ran the standard commands for install: sudo apt install zfsutils-linux sudo apt install zfs-fuse Probably after the first uninstall... but the commands indicate failure. But then installing the second time seemed to work. Did that on both of these boxes I have working. Thanks for the ethtool command. Here's my results on box1 ports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Link partner advertised pause frame use: Symmetric Receive-only Link partner advertised auto-negotiation: Yes Link partner advertised FEC modes: Not reported Speed: 1000Mb/s Duplex: Full Auto-negotiation: on master-slave cfg: preferred slave master-slave status: slave Port: Twisted Pair PHYAD: 0 Transceiver: external MDI-X: Unknown netlink error: Operation not permitted Current message level: 0x0000003f (63) drv probe link timer ifdown ifup Link detected: yes Not an expert and first time reading this command but looks like 1000 is the answer. Crazy thing - box 2 does not have the line "MDI-X: Unknown" shown towards the bottom and "Port: MII" instead of "Port: twisted pair" but is otherwise identical. Posting in case it helps anyone else - but these are beyond me. If you confirm that the above = 1000 I will update both my box running posts. By the way - Another favorite is Software/Management/Cockpit. Easy to see how the server is doing. Plus it has a built in terminal and file manager. Add that to Tailscale and you can check on the server or grab a file while out of the house. curl -fsSL https://tailscale.com/install.sh | sh Those are my favorites. What are yours?

The way I understand it is that you only need the full firmware package in a few exceptional circumstances. What is the wifi chipset on your SBC? Do you have the wireless-regdb package installed? "dpkg -l wireless-regdb"

Thank you for sharing. Would be good to have your findings corroborated by some of official documentation. Thanks again for sharing.

If they boot, I wouldn't worry about any difference.