Yes, you need to install matching kernel and headers, otherwise it won't work. Remove CURRENT kernels by hand, install LEGACY and then proceed with headers installation. This will work.

If your userspace is also still Bullseye, you have to provide more info or just figure out yourself. I updated my BananaPi-M1 earlier this week, but runs Bookworm. I need to look-up what U-Boot I have installed, but I have a serial console cable permanently connected to another SBC, so in case it does not come online (no IP connection), I look at what the serial console port spits out. That is what you also need to do I guess. Kernel 6.6.75-current-sunxi work fine for me, was unattended upgrade+reboot.

This is custom hardware world, not general purpose Linux. There are 15 x Bananapi https://www.armbian.com/download/?tx_maker=sinovoip and every device has its own firmware. There are similarities, sure, which help, but if one boots and works fine, perhaps others won't. We keep images for those too, as some still might work. Trunk = development branch, changes daily. There was never ever support for that. This is for developers and experienced users, which are able to fix the problems as such. And even when "standard support" is declared, when whole SW stack is stabilized to some degree, it means "high level of software maturity" and you are welcome to share your frustration with everyone. Nobody can provide warranty on software support where users contribute less then 0.5% of costs for making it usable. In general. For specific - you need to share all data and logs, and then maybe someone will have a clue on what is happening here.

Thank you for the github release link Igor, and bringing attention to the issue ArmOnJetson! Using 24.11.0-trunk.351 also solved my boot issue (originally I tried with 25.5.0 -- which was leading to a black screen after the Nvidia logo).

Hi Igor; thanks for your fast answer and sorry for the wrong section!! Not sure if I got this right ... do you mean that my banana-pi isnt supported or the trunk I use is not supported? ... I checked this and dont see any repo like untested or nightly build. Its configured to just use main and stable as I see.