c0rnelius

Can you provide a dmesg of the randomly freezing unit, when running on that kernel? Thanx. EDIT: Not 6.0, as its not a good frame of reference with what may be happening on 6.1 and up.

The R2 uses a diff wifi module lsmod | grep "8723ds" 8723ds 1355776 0 cfg80211 331776 1 8723ds https://github.com/lwfinger/rtl8723ds.git

I've seen that in there too, but I've never been able to get a subvolume to boot without using a boot partition. There is also CONFIG_CMD_BTRFS and I could be completely off here, but my thought was maybe a command needs to be executed with a boot script in order for the subvolume to be read/found? I normally use extlinux and with CONFIG_FS_BTRFS & CONFIG_CMD_BTRFS enabled it has always been a no go for me. Maybe someone else here has a thought on the subject? EDIT I tried 3 times getting this working using a Radxa Zero and it was a no-go for a single partition. Once I added a boot partition, it booted right up. radxazero: ~ $ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mmcblk0 179:0 0 29.7G 0 disk ├─mmcblk0p1 179:1 0 253M 0 part /boot └─mmcblk0p2 179:2 0 29.5G 0 part / mmcblk1 179:32 0 14.6G 0 disk ├─mmcblk1p1 179:33 0 253M 0 part └─mmcblk1p2 179:34 0 14.3G 0 part mmcblk1boot0 179:64 0 4M 1 disk mmcblk1boot1 179:96 0 4M 1 disk zram0 253:0 0 1G 0 disk [SWAP] radxazero: ~ $ findmnt /boot; findmnt / TARGET SOURCE FSTYPE OPTIONS /boot /dev/mmcblk0p1 ext4 rw,relatime TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2[/@] btrfs rw,noatime,compress=lzo,ssd,space_cache=v2,subvol

This is a pretty easy add. Basically after creating the btrfs filesystem, mount the LOOP and create the subvolume, now unmount the LOOP and remount it with the correct flags. Lets pretend these are the variables. P_ROOTFS="/mnt/p1" IMAGE_LOOP_DEV_ROOTFS="/dev/loop1p1" mkfs.btrfs -f -L ROOTFS ${IMAGE_LOOP_DEV_ROOTFS} mount "${IMAGE_LOOP_DEV_ROOTFS}" ${P_ROOTFS} btrfs subvolume create ${P_ROOTFS}/@ umount ${P_ROOTFS} mount -o compress=lzo,noatime,subvol=@ ${IMAGE_LOOP_DEV_ROOTFS} ${P_ROOTFS} Where all this would reside in the Armbian framework, I'm not really sure? But in general it wouldn't take that much effort to introduce. One issue I can see popping up, is that U-Boot "last I checked?" doesn't support BTRFS subvolumes. So if subvolumes were an option, the image would require a VFAT or EXT4 BOOT partition.

If you have never built an image, I don't recommend getting your feet wet trying on a tv box. I bricked one of my boxes a couple times before getting this u-boot right, so unless you know how to unbrick it, it is not something you should be playing with. I posted the patches for those who may be interested in adding the support.

I use mainline u-boot on my X96-AIR GBIT. It being a TVBOX, I'm not gonna help people brick their unit, but for those in the know and or willing to try, these are the bits I use. Firmware Image Package can be found here: https://github.com/pyavitz/debian-image-builder/releases/download/amlogic-boot-fip/amlogic-boot-fip-master.tar.gz I also have a kernel patch set. Although its modded for use with the jl2xx1 ETH module. NOTE: The u-boot patches should work with v2023.01 / 04. The vendor 'ANDROID' u-boot needs to be purged from the eMMC: dd if=/dev/zero of="/dev/${node}" bs=32768 count=32768 https://paste.debian.net/1277482/ 001-u-boot-v2023.04-x96-air-gbit-support.patch 002-meson64-boot-target-usb.patch

Absolutely. This has nothing to do with bluetooth. It's related to wifi and the error can be seen on all modern linux kernels. Creating a symlink will make it go away. With that said, the error doesn't break anything and it's just telling you the file is missing.

Although it was initially for use on Raspbian it works on Debian, Devuan and Ubuntu all the same. So it should work fine on Armbian. There is also Bluez hack that the Foundation and Ubuntu use to make sure the firmware is found and loaded during boot, but this can be avoided by simply creating a symlink `ln -s /lib/firmware /etc/firmware`.

Is the pi-bluetooth package installed? The package its self is just a set of scripts, rules and services: https://github.com/RPi-Distro/pi-bluetooth https://packages.ubuntu.com/jammy/pi-bluetooth Interestingly enough, this isn't required when using a mainline kernel. But that's a topic for another day.

HDMI sudo amixer -c 0 set 'TOHDMITX' 'on' sudo amixer -c 0 set 'TOHDMITX I2S SRC' 'I2S B' sudo amixer -c 0 set 'TDMOUT_B SRC SEL' 'IN 0' sudo amixer -c 0 set 'FRDDR_A SRC 2 EN' 'on' sudo amixer -c 0 set 'FRDDR_A SINK 1 SEL' 'OUT 0' sudo amixer -c 0 set 'FRDDR_A SINK 2 SEL' 'OUT 1' sudo amixer -c 0 set 'FRDDR_A SINK 3 SEL' 'OUT 2' sudo amixer -c 0 set 'ACODEC' '85%' # not needed for the C4 sudo alsactl store ANALOG sudo amixer -c 0 set 'TOACODEC OUT EN' 'on' sudo amixer -c 0 set 'TOACODEC SRC' 'I2S B' sudo amixer -c 0 set 'TDMOUT_B SRC SEL' 'IN 0' sudo amixer -c 0 set 'FRDDR_A SRC 2 EN' 'on' sudo amixer -c 0 set 'FRDDR_A SINK 1 SEL' 'OUT 0' sudo amixer -c 0 set 'FRDDR_A SINK 2 SEL' 'OUT 1' sudo amixer -c 0 set 'FRDDR_A SINK 3 SEL' 'OUT 2' sudo amixer -c 0 set 'ACODEC' '85%' sudo alsactl store

Can you up ur build to v2022.07? It's actually missing from the defconfig in that revision. I needed to manually add it to get vid output.

I'm fairly certain removing this `CONFIG_DM_RESET=y` from the uboot defconfig will stop video output on the tinker during initial boot. https://lore.kernel.org/u-boot/20230106165229.GZ3787616@bill-the-cat/

I've been using: https://github.com/jethome-ru/rtl88x2cs.git

More than likely the /boot is a vfat partition and as it suggests creating a hard link isn't supported. The initrd is still getting updated.