MichaIng

Not sure how the service could be running (and failing), which is only started when selecting "Apply", which is not part of your steps to reproduce. However, "Reset" will now...

Many thanks for your report. Please fill the bug report template, so we get the required information about your hardware and software. Please also add `dmesg -l emerg,alert,crit,err` or, if...

Any news from your end, regarding the info we'd need to help you?

I'll mark it as closed for now (cleanup), please reopen when you find time to come back to this issue 🙂.

For all features to work, I'd currently prefer to stay with FriendlyELEC's kernel, but probably the device tree from your build works with it. I'm not able to extract it...

See here for getting Ethernet LED triggers t work: #5679 Sadly with the manually generated device tree, the manually generated image with single partition but FriendlyELEC kernel + bootloader still...

Matches my results so far: It denies to boot without the original GPT partitioning. Will try to check and set the U-Boot configs with [fw_printenv/fw_setenv](https://packages.debian.org/bullseye/libubootenv-tool), maybe the defaults are hardcoded...

The multiple partitions are mentioned here: https://github.com/friendlyarm/uboot-rockchip/blob/nanopi5-v2017.09/include/configs/nanopi5.h R5S support was added with this commit: https://github.com/friendlyarm/uboot-rockchip/commit/8c91d15 In the config: ``` # CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR is not set CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION=y ... # CONFIG_ISO_PARTITION is not...

@pyavitz I tried to flash the U-Boot of your recent Debian Bullseye onto my debootstrapped R5S image with single ext4 partition, vendor kerne/dtb and `/boot/extlinux/extlinux.conf`, via: ```sh dd 'if=/root/idbloader.bin' "of=$1"...

I'll try to boot with your U-Boot build and vendor kernel. When I find time I'll also try to play with the vendor U-Boot configs and compiling them.