hi @MichaIng
No worries about my reported issues, in particular about the ethernet issues. I’ve encountered them pretty seriously, but that if you review my tests, it essentially confirms a hardware problem with possibly the ethernet PHY YT8531 chip. However, as I’m testing it from a limited environment i.e. my desktop and I’m testing with a single piece, it isn’t known for sure if others observe the same unless they feedback on the same.
And that hardware issues are hardware issues, and unrelated to DietPi images. In fact, I’m liking DietPi for being ‘raw’, no NetworkManager or things ‘in between’ and it makes the hardware issues upfront when they surfaced, nearly bare metal. unlike in the vendor’s images, etc I’ve originally wondered why did Network Manager disable an interface, as I’ve had to enable that manually if network manager is used. In the case of DietPi, it is simply ip link, ethtool, ifup etc, right down bare. and dmesg and nothing between.
In addition, there is a way to overcome the current ethernet PHY issues, I’m resorting to buying a usb-ethernet adapter and using that. Hope it’d overcome the ethernet PHY hardware defect in my case.
I’d hope other users test other use cases for Diet Pi, e.g. other apps,. it seemed there is one related to hardware rng (e.g. rngd ?) that may need to be looked into e.g. that there is after all no hardware rng, but I’m not sure about it.
If that they are reasonably free of issues, my guess is ‘Test’ can reasonably be promoted to ‘supported’ .
Among the things ,I think video may not work. But that my use case is strictly server or simply the network and Wifi interfaces. Hence, others has to test that if it matters to them. At least to document what ‘doesn’t work’ - it is a feature, not a bug. It’d be good to maintain a ‘release notes’ documenting the source of the kernel e.g. from vendor images for version 6.1 kernel, the failures discovered e.g. a possibly bad ethernet PHY, UWE5622 wifi issues etc. these would be ‘known features’ as related to the present state-of-the-art 
As new kernels etc become available e.g. the 6.6 versions and some works on uboot, I’ve not tested them myself, hopefully at some point those could be ‘mainlined’ i.e. from stock kernel and uboot.
Today the UWE5622 drivers are not in mainline as well, and hopefully that gets into the mainline kernel as well.
Apparently Orange Pi use UWE5622 Wifi as well as the PHY YT8531 on several of their boards. And so do some other board manufacturers notably Bigtreetech CB1 for the UWE5622
Those progress at the ‘bleeding edge’ could hopefully help to make the path ‘forward’ for more ‘streamlined’ supports for these boards (in (near) future).
an intresting sidenote, I randomly checked around for boards having Wifi and Ethernet, decent cpu and generous amount of ram. Because I had so much issues with the (possibly) bad ethernet PHY (note that when it works well I’ve witnessed >100 Mbps (mega bits per seconds) throughput on the wifi hotspot across UWE5622 Wifi and ethernet on Orange Pi Zero 3, that is good performannce), but that it is simply unstable.
And as I searched around for boards to replace Orange Pi Zero 3 as a Wifi AP hotspot, it turns out the competitors are either the Raspberry Pis - for stability and this Orange Pi Zero 3 being the lowest cost among the rivals say running Allwinner chips etc,. And many of Orange Pi’s rivals simply don’t have a good combination of having both Wifi (with antenna) (and can run as an AP) and high speed ethernet. but just bad that Orange Pi Zero 3 isn’t as stable and robust as like the Raspberry Pi’s, in both codes and hardware.
