@satmandu, re your comment #32: 5.11.22-9021-raspi is supposed to go along with current hirsute linux-firmware-raspi2 4-0ubuntu3. We don't want to bump the FW on hirsute. Also, the DTBS are provided by the kernel and not the firmware package.
And: $ dpkg -i linux-image-5.11.22-9021-raspi_... $ flash-kernel --force 5.11.22-9021-raspi $ md5sum /boot/dtb-5.11.22-9021-raspi /boot/firmware/bcm2711-rpi-4-b.dtb f2f90ac1a0c075d3961914c2d345d4ae /boot/dtb-5.11.22-9021-raspi f2f90ac1a0c075d3961914c2d345d4ae /boot/firmware/bcm2711-rpi-4-b.dtb
The DTBs are identical.
I'm not sure what you're trying to proof, especially since in comment #31 you claim that 5.11.22-9021-raspi works for you.
Can you do your testing without overclocking?
@satmandu, re your comment #32: 5.11.22-9021-raspi is supposed to go along with current hirsute linux-firmware- raspi2 4-0ubuntu3. We don't want to bump the FW on hirsute. Also, the DTBS are provided by the kernel and not the firmware package.
And: 5.11.22- 9021-raspi_ ... 5.11.22- 9021-raspi /boot/firmware/ bcm2711- rpi-4-b. dtb 3961914c2d345d4 ae /boot/dtb- 5.11.22- 9021-raspi 3961914c2d345d4 ae /boot/firmware/ bcm2711- rpi-4-b. dtb
$ dpkg -i linux-image-
$ flash-kernel --force 5.11.22-9021-raspi
$ md5sum /boot/dtb-
f2f90ac1a0c075d
f2f90ac1a0c075d
The DTBs are identical.
I'm not sure what you're trying to proof, especially since in comment #31 you claim that 5.11.22-9021-raspi works for you.
Can you do your testing without overclocking?