6.5 is an odd branch to choose. 6.5 hit EOL as soon as 6.6.0 was released.
6.1 and 6.6 are the long term support (LTS) branches from mainline, and the ones that Raspberry Pi focus on supporting.
https://www.kernel.org/category/releases.html
If you're getting " Bogus possible_crtcs: [ENCODER:31:DSI-31] possible_crtcs=0x0 (full crtc mask=0x0)" then you've messed something up in DT big time, quite possibly linked to failing to load vc4-kms-v3d.
You can add "dtdebug=1" to /boot/firmware/config.txt, and then "sudo vclog -m" will give you far more detail over what the firmware did in DT during the early phase of boot.
Push your branch to Github so that others can pull it and build it, and then it's possible to advise. Just looking at logs is far harder.
6.1 and 6.6 are the long term support (LTS) branches from mainline, and the ones that Raspberry Pi focus on supporting.
https://www.kernel.org/category/releases.html
If you're getting " Bogus possible_crtcs: [ENCODER:31:DSI-31] possible_crtcs=0x0 (full crtc mask=0x0)" then you've messed something up in DT big time, quite possibly linked to failing to load vc4-kms-v3d.
You can add "dtdebug=1" to /boot/firmware/config.txt, and then "sudo vclog -m" will give you far more detail over what the firmware did in DT during the early phase of boot.
Push your branch to Github so that others can pull it and build it, and then it's possible to advise. Just looking at logs is far harder.
Statistics: Posted by 6by9 — Wed Feb 28, 2024 4:41 pm