I have done an as fast as possible (for me) 'install' of 2026-07-04-raspios-trixie-nightly-arm64.img.xz
I used a sort of pseudo script I posted earlier on this forum, it is primarily running btrfs-convert on the second partition and then doing some changes to boot methods (using grub-efi as the HW is not an RPi but other Aarch64 platform and uses vanilla Debian sid 7.0.x kernel). Would be much easier in a KVM, but I was curious about the state of GPU/driver issues.
The changes compared to 9 months ago are:
touch /etc/cloud/cloud-init.disabled
rm /etc/netplan/*.yaml
Those are the whole reason I did this experiment; Can I safely use and/or re-enable raspi.sources without ruining network setup? Besides that I had to use raspi-config to set X11 (all via serial console) it initially worked. Note that is with undefined content found in /boot/firmware/, as I initially only mounted rootfs on a partition 6 of an NVME, the boot partition is from a Debian installation, so a /EFI/boot/bootaa64.efi and /EFI/boot/grub.cfg making sure correct rootfs is used.
After reboot and various file copies etc, the usual things went wrong. Until I did sudo apt purge --autoremove cloud-init
It is especially running raspi-config and still cloud-init installled that let things fail as I remember I have seen often on this forum. It likely has to do with not finding expected content in /boot/firmware/ as original Canonical cloud-init only deals with rootfs, at least that is what I remember from Ubuntu about 6 years ago on RPI4.
So I more or less feel sorry for the NM advice; I switched to systemd-networkd for several RPi's and so also did apt purge --autoremove network-manager netplan.io
So far works all fine, should have done that way earlier, a year ago, so that I would not have wasted my time on netplan issues and the forced dependency in Raspbian/RPiOS64 and NM.
To be clear: "Trixie NetworkManager" is fine if OS is Debian Trixie (ARMv7, ARMv8, x86-64) and also other distros that have it delivered without a dependency on netplan.io, so this one when 64-bit ARM:
# apt list network-manager
network-manager/stable,now 1.52.1-1 arm64 [installed]
I used a sort of pseudo script I posted earlier on this forum, it is primarily running btrfs-convert on the second partition and then doing some changes to boot methods (using grub-efi as the HW is not an RPi but other Aarch64 platform and uses vanilla Debian sid 7.0.x kernel). Would be much easier in a KVM, but I was curious about the state of GPU/driver issues.
The changes compared to 9 months ago are:
touch /etc/cloud/cloud-init.disabled
rm /etc/netplan/*.yaml
Those are the whole reason I did this experiment; Can I safely use and/or re-enable raspi.sources without ruining network setup? Besides that I had to use raspi-config to set X11 (all via serial console) it initially worked. Note that is with undefined content found in /boot/firmware/, as I initially only mounted rootfs on a partition 6 of an NVME, the boot partition is from a Debian installation, so a /EFI/boot/bootaa64.efi and /EFI/boot/grub.cfg making sure correct rootfs is used.
After reboot and various file copies etc, the usual things went wrong. Until I did sudo apt purge --autoremove cloud-init
It is especially running raspi-config and still cloud-init installled that let things fail as I remember I have seen often on this forum. It likely has to do with not finding expected content in /boot/firmware/ as original Canonical cloud-init only deals with rootfs, at least that is what I remember from Ubuntu about 6 years ago on RPI4.
So I more or less feel sorry for the NM advice; I switched to systemd-networkd for several RPi's and so also did apt purge --autoremove network-manager netplan.io
So far works all fine, should have done that way earlier, a year ago, so that I would not have wasted my time on netplan issues and the forced dependency in Raspbian/RPiOS64 and NM.
To be clear: "Trixie NetworkManager" is fine if OS is Debian Trixie (ARMv7, ARMv8, x86-64) and also other distros that have it delivered without a dependency on netplan.io, so this one when 64-bit ARM:
# apt list network-manager
network-manager/stable,now 1.52.1-1 arm64 [installed]
Statistics: Posted by redvli — Mon Jul 06, 2026 7:49 am
