MichaIng
MichaIng
Yes, the caching mode warning is common in combination with USB-attached drives, definitly not related. Hmm a serial console / UART adapter would be very helpful indeed to know for...
I answered on the other issue where it fits better: https://github.com/MichaIng/DietPi/issues/5634#issuecomment-1258440165 Different SBC means very different possible issues 😉.
Many thanks. To not bloat the already lengthy Proxmox instructions further, at which step did the error occur? You did assure that the VM ID was set correctly?
Many thanks for your report. How did you enable it in the ".dtb file"? Usually one would use a device tree overlay then, not sure if there is one present...
I'll mark this as closed. Feel free to reopen if required.
Many thanks for your report. `/sys/class/leds/*_led/trigger` is set to something functional by default, isn't it? So we can add a udev rule to our R5S image which sets `device_name` and...
Added with: https://github.com/MichaIng/DietPi/commit/ce358db Image will be rebuild after release within the next two hours.
Please show the output of: ```sh lsattr /usr/bin/obfs4proxy ```
Great, so no own image is required but we need to update ours for R4S. Long overdue anyway for the NanoPi's, to add them to our image generation CI.
Are kernel/bootloader/firmware DEB packaged?