Can you check if you can pass drm.debug=0x4 to the kernel command line and see if you get more info ? If yes, paste here the boot log.

Thanks for the hint Sirmalinton. Today, I could solve the problem. Here is a short summary that might be of use for people running into similar issues. Running lspci -k shows the "Non-Volatile memory controller" but it does not show the line "Kernel driver in use: nvme". Hence, I ran echo nvme > /sys/bus/pci/devices/0002\:01\:00.0/driver_override echo 0002:01:00.0 > /sys/bus/pci/drivers_probe where 0002:01:00.0 is from the output of lspci -k. That worked and made the disk appear as files /dev/nvme0*. To have a solution that works after reboot, I created a udev rule /etc/udev/rules.d/99-nvme-override.rules with the content: ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x144d", ATTR{device}=="0xa80d", ATTR{driver_override}="nvme" The vendor and device IDs are from lspci -nn. To trigger the probe, I created a systemd service /etc/systemd/system/nvme-rebind.service with the content: [Unit] Description=Rebind NVME controller to driver after override After=udev.service [Service] Type=oneshot ExecStart=/bin/sh -c "echo 0002:01:00.0 > /sys/bus/pci/drivers_probe" [Install] WantedBy=multi-user.target The service can be enabled via systemctl enable nvme-rebind.service. Maybe one reason it does not work in the first place is because /lib/systemd/system/nvmefc-boot-connections.service is not started. The reason is that the condition ConditionPathExists=/sys/class/fc/fc_udev_device/nvme_discovery is not met. Another reason, I can imagine is that the vendor/device ID combination is not registered to the nvme driver in the current kernel. As I mentioned before, it did work out of the box when I installed Armbian at first.

Well, since this same edid file I use on the Libre Renegade board works perfectly fine with this same monitor, I think the file is ok. This link you provide is the one I followed, I tried most of the things in there, as well as a bunch of stuff I found from other users. Again, since this works on U-Boot, this points at something defective on Armbian and how the edid communication happens. This Armbian kernel that came with the armbian image I downloaded it from the armbian github as a part of the image I use on my device. I did not build it. I would think it was the Armbian team, correct?

More like a kernel issue than Armbian. The Armbian supplied edid bin file probably does not match your monitor's. Take a look here on how to get the actual edid and force it: https://wiki.archlinux.org/title/Kernel_mode_setting#Forcing_modes_and_EDID

Yes, The 1920x1080.bin file comes with Armbian. I use the multitool to flash https://github.com/armbian/community/releases/download/25.8.0-trunk.309/Armbian_community_25.8.0-trunk.309_Rk322x-box_bookworm_current_6.12.35_minimal.img.xz , this is the latesst build. On a Libre Renegade board I have (rk3328 CPU instead of rk3228 for this TV box), I have the same issue where it reverts to 1024x768, and adding the line extraargs=drm.edid_firmware=edid/1920x1080.bin to armbianEnv.txt fixes the issue, with the Armbian provided 1920x1080.bin file. To me, since it works fine under U-Boot, this hints at an Armbian bug.