The WiFi issue with DebianTrixie was because apt-get got confused because same firmware blob file paths but different version and package origin. There might also be a license issue, but all those can be fixed although not permanent, so every update you get problems.
Besides that, the Pi4 WiFi module is SPI connected and cannot do 2 bands at the same time and also no MiMO. Still nice for a simple 2.4GHz remote access point with camera and GPIO and so on, but not for a more performant MIMO multiband with bandsteering, roaming, etc. Besides that, if USB connected, you can easily allocate the complete USB device identified by its IDs to a guest virtual machine. And as you say, you can make it work on x86_64 PC then port to Aarch64 Pi4.
Your initial picture is very clear; I did not look into the details of dnsmasq. I remember there was once an issue with DNS / resolveconf when dist-upgrade some Debian machine, but was with unreleased Bookworm. Should be fixed now I guess. Ubuntu takes things from Debian Testing, so it might contain old/wrong methods/issues. RaspberryPi has several HW aspects you won't see in x86_64 space, like SPI connected WiFI. That is a risk that things won't work and only RPL cares to fix it and they will do it in their own modified Debian (=RPiOS), mainly kernel+firmware. An LTS release like 22.04 won't take. You can compile new RPi kernel yourself and put it together with matching firmware on your Ubuntu rootfs+bootfs.
I know from Opensuse Tumbleweed that it can take a lot of time to get it correct. Same as Canonical, Suse uses its own thing for handling networks, by far not the same as Debian, so you might hit some area where it simply won't work. netplan is designed so Canonical can manage all their various versions and network handling tools more easily I understood, but you are not Canonical, you have just your Pi4. So that is why I removed that cloud-init/netplan stuff. Same for snap, I use Ubuntu at CLI level for a complex build environment, don't care about firefox latest or so.
Besides that, the Pi4 WiFi module is SPI connected and cannot do 2 bands at the same time and also no MiMO. Still nice for a simple 2.4GHz remote access point with camera and GPIO and so on, but not for a more performant MIMO multiband with bandsteering, roaming, etc. Besides that, if USB connected, you can easily allocate the complete USB device identified by its IDs to a guest virtual machine. And as you say, you can make it work on x86_64 PC then port to Aarch64 Pi4.
Your initial picture is very clear; I did not look into the details of dnsmasq. I remember there was once an issue with DNS / resolveconf when dist-upgrade some Debian machine, but was with unreleased Bookworm. Should be fixed now I guess. Ubuntu takes things from Debian Testing, so it might contain old/wrong methods/issues. RaspberryPi has several HW aspects you won't see in x86_64 space, like SPI connected WiFI. That is a risk that things won't work and only RPL cares to fix it and they will do it in their own modified Debian (=RPiOS), mainly kernel+firmware. An LTS release like 22.04 won't take. You can compile new RPi kernel yourself and put it together with matching firmware on your Ubuntu rootfs+bootfs.
I know from Opensuse Tumbleweed that it can take a lot of time to get it correct. Same as Canonical, Suse uses its own thing for handling networks, by far not the same as Debian, so you might hit some area where it simply won't work. netplan is designed so Canonical can manage all their various versions and network handling tools more easily I understood, but you are not Canonical, you have just your Pi4. So that is why I removed that cloud-init/netplan stuff. Same for snap, I use Ubuntu at CLI level for a complex build environment, don't care about firefox latest or so.
Statistics: Posted by redvli — Tue Dec 26, 2023 8:12 am
