I have the same issue and spent a bit of time to figure out how to correct it. There may be a better way, but this is how I did it and it seems to survive package updates.
You can update the DTBs in /boot to test and see if it resolves the issue. If it does fix the problem, you can instruct flash-kernel to always use the correct DTB. While booted into the correct DTB, get the device tree model: $ cat /proc/device-tree/model Take that value and write it to: /etc/flash-kernel/machine So for my VisionFive 2: $ cat /etc/flash-kernel/machine StarFive VisionFive 2 v1.2A After doing that, trigger a reconfiguration with dpkg-reconfigure on the kernel package(s) to get all the triggers to run and you should notice it use the correct DTB firmware in stdout. There may be a quicker method, but this worked for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2017357 Title: Wrong DTB for StarFive VisionFive 2 v1.2a board To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2017357/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
